From 2e9600204fe5a820e229b9f60f3dee23a8b835ab Mon Sep 17 00:00:00 2001
From: Per Cederqvist <ceder@lysator.liu.se>
Date: Fri, 11 Jul 2014 09:33:35 +0200
Subject: [PATCH] Imported Bugzilla 2.14.
---
.cvsignore | 1 +
CGI.pl | 365 +-
CVS/Entries | 149 +-
CVS/Entries.Log | 4 -
CVS/Tag | 1 +
README | 13 +-
RelationSet.pm | 8 +-
Token.pm | 185 +
UPGRADING | 3 +
CHANGES => UPGRADING-pre-2.8 | 9 +-
backdoor.cgi | 178 -
bug_form.pl | 130 +-
buglist.cgi | 144 +-
checksetup.pl | 712 +-
colchange.cgi | 4 +
collectstats.pl | 4 +-
contrib/CVS/Entries | 22 +-
contrib/CVS/Tag | 1 +
contrib/bug_email.pl | 35 +-
contrib/mysqld-watcher.pl | 26 +-
createaccount.cgi | 17 +-
defparams.pl | 78 +-
describecomponents.cgi | 44 +-
docs/CVS/Entries | 5 +-
docs/CVS/Tag | 1 +
docs/README.docs | 68 +-
docs/html/Bugzilla-Guide.html | 15657 +++++++++++++--------
docs/html/CVS/Entries | 135 +-
docs/html/CVS/Tag | 1 +
docs/html/about.html | 2 +-
docs/html/aboutthisguide.html | 75 +-
docs/html/administration.html | 72 +-
docs/html/bonsai.html | 20 +-
docs/html/{bz30.html => bsdinstall.html} | 43 +-
docs/html/bugprobs.html | 211 -
docs/html/bzhacking.html | 231 +
docs/html/cleanupwork.html | 155 -
docs/html/cmdline.html | 73 +-
docs/html/contributors.html | 13 +-
docs/html/conventions.html | 93 +-
docs/html/copyright.html | 27 +-
docs/html/credits.html | 41 +-
docs/html/cvs.html | 34 +-
docs/html/database.html | 34 +-
docs/html/dbaseintegrity.html | 179 -
docs/html/dbdoc.html | 454 +-
docs/html/dbschema.html | 4 +-
docs/html/disclaimer.html | 52 +-
docs/html/downloadlinks.html | 6 +-
docs/html/errata.html | 273 +
docs/html/faq.html | 919 +-
docs/html/feedback.html | 11 +-
docs/html/future.html | 656 +-
docs/html/geninstall.html | 421 +
docs/html/gfdl.html | 14 +-
docs/html/gfdl_0.html | 2 +-
docs/html/gfdl_1.html | 2 +-
docs/html/gfdl_10.html | 2 +-
docs/html/gfdl_2.html | 2 +-
docs/html/gfdl_3.html | 2 +-
docs/html/gfdl_4.html | 2 +-
docs/html/gfdl_5.html | 2 +-
docs/html/gfdl_6.html | 2 +-
docs/html/gfdl_7.html | 2 +-
docs/html/gfdl_8.html | 2 +-
docs/html/gfdl_9.html | 2 +-
docs/html/gfdl_howto.html | 4 +-
docs/html/glossary.html | 466 +-
docs/html/granttables.html | 74 +-
docs/html/how.html | 842 +-
docs/html/index.html | 684 +-
docs/html/init4me.html | 341 +-
docs/html/installation.html | 203 +-
docs/html/integration.html | 14 +-
docs/html/newversions.html | 16 +-
docs/html/osx.html | 289 +
docs/html/patches.html | 44 +-
docs/html/postinstall-check.html | 431 +-
docs/html/programadmin.html | 870 +-
docs/html/quicksearch.html | 53 +-
docs/html/readme.unix.html | 1735 ---
docs/html/readme.windows.html | 755 -
docs/html/rewrite.html | 191 +
docs/html/rhbugzilla.html | 91 +-
docs/html/scm.html | 45 +-
docs/html/searching.html | 197 -
docs/html/security.html | 290 +-
docs/html/setperl.html | 68 +-
docs/html/spamlite.html | 189 -
docs/html/stepbystep.html | 2339 +++
docs/html/tinderbox.html | 8 +-
docs/html/trackingbugs.html | 193 -
docs/html/translations.html | 13 +-
docs/html/useradmin.html | 502 +-
docs/html/using.html | 52 +-
docs/html/usingbz-conc.html | 32 +-
docs/html/variant_fenris.html | 142 +
docs/html/variant_issuezilla.html | 153 +
docs/html/variant_perforce.html | 148 +
docs/html/variant_scarab.html | 148 +
docs/html/variant_sourceforge.html | 148 +
docs/html/variants.html | 73 +-
docs/html/whatis.html | 76 +-
docs/html/why.html | 81 +-
docs/html/win32.html | 1634 +++
docs/images/CVS/Entries | 7 +
docs/images/CVS/Repository | 1 +
{oracle => docs/images}/CVS/Root | 0
docs/images/CVS/Tag | 1 +
docs/images/caution.gif | Bin 0 -> 260 bytes
docs/{html => images}/dbschema.jpg | Bin
docs/images/dbschema.ps | 1733 +++
docs/images/note.gif | Bin 0 -> 226 bytes
docs/images/tip.gif | Bin 0 -> 2432 bytes
docs/images/warning.gif | Bin 0 -> 151 bytes
docs/rel_notes.txt | 291 +-
docs/sgml/Bugzilla-Guide.sgml | 233 +-
docs/sgml/CVS/Entries | 34 +-
docs/sgml/CVS/Tag | 1 +
docs/sgml/about.sgml | 465 +-
docs/sgml/administration.sgml | 2463 ++--
docs/sgml/conventions.sgml | 27 +-
docs/sgml/database.sgml | 457 +-
docs/sgml/dbschema.jpg | Bin 220048 -> 0 bytes
docs/sgml/dbschema.mysql | 309 +
docs/sgml/faq.sgml | 271 +-
docs/sgml/future.sgml | 895 +-
docs/sgml/gfdl.sgml | 24 +-
docs/sgml/glossary.sgml | 391 +-
docs/sgml/index.sgml | 20 +
docs/sgml/installation.sgml | 3097 ++--
docs/sgml/integration.sgml | 104 +-
docs/sgml/patches.sgml | 285 +-
docs/sgml/requiredsoftware.sgml | 24 +-
docs/sgml/using.sgml | 939 +-
docs/sgml/variants.sgml | 139 +-
docs/txt/Bugzilla-Guide.txt | 6229 ++++----
docs/txt/CVS/Entries | 2 +-
docs/txt/CVS/Tag | 1 +
doeditparams.cgi | 4 +-
doeditvotes.cgi | 138 +-
duplicates.cgi | 129 +-
editcomponents.cgi | 14 +-
editgroups.cgi | 92 +-
editmilestones.cgi | 14 +-
editparams.cgi | 2 +-
editproducts.cgi | 14 +-
editusers.cgi | 257 +-
editversions.cgi | 14 +-
enter_bug.cgi | 79 +-
globals.pl | 328 +-
importxml.pl | 15 +-
move.pl | 8 +-
newquip.html | 37 -
oracle/CVS/Entries | 1 -
oracle/CVS/Repository | 1 -
post_bug.cgi | 16 +-
process_bug.cgi | 679 +-
processmail | 721 +-
query.cgi | 15 +-
quicksearch.js | 174 +-
quips.cgi | 65 +
reports.cgi | 124 +-
sanitycheck.cgi | 36 +-
show_activity.cgi | 25 +-
show_bug.cgi | 33 +-
showattachment.cgi | 26 +-
showdependencygraph.cgi | 26 +-
showdependencytree.cgi | 23 +-
showvotes.cgi | 44 +-
syncshadowdb | 28 +-
template/CVS/Entries | 1 -
template/CVS/Repository | 1 -
template/CVS/Root | 1 -
token.cgi | 243 +
userprefs.cgi | 208 +-
176 files changed, 37172 insertions(+), 20676 deletions(-)
delete mode 100644 CVS/Entries.Log
create mode 100644 CVS/Tag
create mode 100644 Token.pm
create mode 100644 UPGRADING
rename CHANGES => UPGRADING-pre-2.8 (97%)
delete mode 100755 backdoor.cgi
create mode 100644 contrib/CVS/Tag
create mode 100644 docs/CVS/Tag
create mode 100644 docs/html/CVS/Tag
rename docs/html/{bz30.html => bsdinstall.html} (65%)
delete mode 100644 docs/html/bugprobs.html
create mode 100644 docs/html/bzhacking.html
delete mode 100644 docs/html/cleanupwork.html
delete mode 100644 docs/html/dbaseintegrity.html
create mode 100644 docs/html/errata.html
create mode 100644 docs/html/geninstall.html
create mode 100644 docs/html/osx.html
delete mode 100644 docs/html/readme.unix.html
delete mode 100644 docs/html/readme.windows.html
create mode 100644 docs/html/rewrite.html
delete mode 100644 docs/html/searching.html
delete mode 100644 docs/html/spamlite.html
create mode 100644 docs/html/stepbystep.html
delete mode 100644 docs/html/trackingbugs.html
create mode 100644 docs/html/variant_fenris.html
create mode 100644 docs/html/variant_issuezilla.html
create mode 100644 docs/html/variant_perforce.html
create mode 100644 docs/html/variant_scarab.html
create mode 100644 docs/html/variant_sourceforge.html
create mode 100644 docs/html/win32.html
create mode 100644 docs/images/CVS/Entries
create mode 100644 docs/images/CVS/Repository
rename {oracle => docs/images}/CVS/Root (100%)
create mode 100644 docs/images/CVS/Tag
create mode 100644 docs/images/caution.gif
rename docs/{html => images}/dbschema.jpg (100%)
create mode 100644 docs/images/dbschema.ps
create mode 100644 docs/images/note.gif
create mode 100644 docs/images/tip.gif
create mode 100644 docs/images/warning.gif
create mode 100644 docs/sgml/CVS/Tag
delete mode 100644 docs/sgml/dbschema.jpg
create mode 100644 docs/sgml/dbschema.mysql
create mode 100644 docs/txt/CVS/Tag
delete mode 100644 newquip.html
delete mode 100644 oracle/CVS/Entries
delete mode 100644 oracle/CVS/Repository
create mode 100755 quips.cgi
delete mode 100644 template/CVS/Entries
delete mode 100644 template/CVS/Repository
delete mode 100644 template/CVS/Root
create mode 100755 token.cgi
diff --git a/.cvsignore b/.cvsignore
index ce18c65ad..64432ca1e 100644
--- a/.cvsignore
+++ b/.cvsignore
@@ -1,3 +1,4 @@
+.htaccess
graphs
data
localconfig
diff --git a/CGI.pl b/CGI.pl
index 29d8f68ea..2cf6ffeca 100644
--- a/CGI.pl
+++ b/CGI.pl
@@ -20,6 +20,8 @@
# Contributor(s): Terry Weissman <terry@mozilla.org>
# Dan Mosedale <dmose@mozilla.org>
# Joe Robins <jmrobins@tgix.com>
+# Dave Miller <justdave@syndicomm.com>
+# Christopher Aillon <christopher@aillon.com>
# Contains some global routines used throughout the CGI scripts of Bugzilla.
@@ -226,6 +228,118 @@ sub CheckFormFieldDefined (\%$) {
}
}
+sub ValidateBugID {
+ # Validates and verifies a bug ID, making sure the number is a
+ # positive integer, that it represents an existing bug in the
+ # database, and that the user is authorized to access that bug.
+
+ my ($id) = @_;
+
+ # Make sure the bug number is a positive integer.
+ # Whitespace can be ignored because the SQL server will ignore it.
+ $id =~ /^\s*([1-9][0-9]*)\s*$/
+ || DisplayError("The bug number is invalid.")
+ && exit;
+
+ # Get the values of the usergroupset and userid global variables
+ # and write them to local variables for use within this function,
+ # setting those local variables to the default value of zero if
+ # the global variables are undefined.
+
+ # "usergroupset" stores the set of groups the user is a member of,
+ # while "userid" stores the user's unique ID. These variables are
+ # set globally by either confirm_login() or quietly_check_login(),
+ # one of which should be run before calling this function; otherwise
+ # this function will treat the user as if they were not logged in
+ # and throw an error if they try to access a bug that requires
+ # permissions/authorization to access.
+ my $usergroupset = $::usergroupset || 0;
+ my $userid = $::userid || 0;
+
+ # Query the database for the bug, retrieving a boolean value that
+ # represents whether or not the user is authorized to access the bug.
+
+ # Users are authorized to access bugs if they are a member of all
+ # groups to which the bug is restricted. User group membership and
+ # bug restrictions are stored as bits within bitsets, so authorization
+ # can be determined by comparing the intersection of the user's
+ # bitset with the bug's bitset. If the result matches the bug's bitset
+ # the user is a member of all groups to which the bug is restricted
+ # and is authorized to access the bug.
+
+ # A user is also authorized to access a bug if she is the reporter,
+ # assignee, QA contact, or member of the cc: list of the bug and the bug
+ # allows users in those roles to see the bug. The boolean fields
+ # reporter_accessible, assignee_accessible, qacontact_accessible, and
+ # cclist_accessible identify whether or not those roles can see the bug.
+
+ # Bit arithmetic is performed by MySQL instead of Perl because bitset
+ # fields in the database are 64 bits wide (BIGINT), and Perl installations
+ # may or may not support integers larger than 32 bits. Using bitsets
+ # and doing bitset arithmetic is probably not cross-database compatible,
+ # however, so these mechanisms are likely to change in the future.
+
+ # Get data from the database about whether or not the user belongs to
+ # all groups the bug is in, and who are the bug's reporter and qa_contact
+ # along with which roles can always access the bug.
+ SendSQL("SELECT ((groupset & $usergroupset) = groupset) , reporter , assigned_to , qa_contact ,
+ reporter_accessible , assignee_accessible , qacontact_accessible , cclist_accessible
+ FROM bugs
+ WHERE bug_id = $id");
+
+ # Make sure the bug exists in the database.
+ MoreSQLData()
+ || DisplayError("Bug #$id does not exist.")
+ && exit;
+
+ my ($isauthorized, $reporter, $assignee, $qacontact, $reporter_accessible,
+ $assignee_accessible, $qacontact_accessible, $cclist_accessible) = FetchSQLData();
+
+ # Finish validation and return if the user is a member of all groups to which the bug belongs.
+ return if $isauthorized;
+
+ # Finish validation and return if the user is in a role that has access to the bug.
+ if ($userid) {
+ return
+ if ($reporter_accessible && $reporter == $userid)
+ || ($assignee_accessible && $assignee == $userid)
+ || ($qacontact_accessible && $qacontact == $userid);
+ }
+
+ # Try to authorize the user one more time by seeing if they are on
+ # the cc: list. If so, finish validation and return.
+ if ( $cclist_accessible ) {
+ my @cclist;
+ SendSQL("SELECT cc.who
+ FROM bugs , cc
+ WHERE bugs.bug_id = $id
+ AND cc.bug_id = bugs.bug_id
+ ");
+ while (my ($ccwho) = FetchSQLData()) {
+ # more efficient to just check the var here instead of
+ # creating a potentially huge array to grep against
+ return if ($userid == $ccwho);
+ }
+
+ }
+
+ # The user did not pass any of the authorization tests, which means they
+ # are not authorized to see the bug. Display an error and stop execution.
+ # The error the user sees depends on whether or not they are logged in
+ # (i.e. $userid contains the user's positive integer ID).
+ if ($userid) {
+ DisplayError("You are not authorized to access bug #$id.");
+ } else {
+ DisplayError(
+ qq|You are not authorized to access bug #$id. To see this bug, you
+ must first <a href="show_bug.cgi?id=$id&GoAheadAndLogIn=1">log in
+ to an account</a> with the appropriate permissions.|
+ );
+ }
+ exit;
+
+}
+
# check and see if a given string actually represents a positive
# integer, and abort if not.
#
@@ -233,7 +347,7 @@ sub CheckPosInt($) {
my ($number) = @_; # the fieldname to check
if ( $number !~ /^[1-9][0-9]*$/ ) {
- print "Received string \"$number\" when postive integer expected; ";
+ print "Received string \"$number\" when positive integer expected; ";
print Param("browserbugmessage");
PutFooter();
exit 0;
@@ -590,15 +704,21 @@ sub quietly_check_login() {
sub CheckEmailSyntax {
my ($addr) = (@_);
my $match = Param('emailregexp');
- if ($addr !~ /$match/) {
+ if ($addr !~ /$match/ || $addr =~ /[\\\(\)<>&,;:"\[\] \t\r\n]/) {
print "Content-type: text/html\n\n";
+ # For security, escape HTML special characters.
+ $addr = html_quote($addr);
+
PutHeader("Check e-mail syntax");
print "The e-mail address you entered\n";
print "(<b>$addr</b>) didn't match our minimal\n";
print "syntax checking for a legal email address.\n";
- print Param('emailregexpdesc');
- print "<p>Please click <b>back</b> and try again.\n";
+ print Param('emailregexpdesc') . "\n";
+ print "It must also not contain any of these special characters: " .
+ "<tt>\\ ( ) & < > , ; : \" [ ]</tt> " .
+ "or any whitespace.\n";
+ print "<p>Please click <b>Back</b> and try again.\n";
PutFooter();
exit;
}
@@ -638,43 +758,60 @@ sub confirm_login {
# to a later section. -Joe Robins, 8/3/00
my $enteredlogin = "";
my $realcryptpwd = "";
- if (defined $::FORM{"Bugzilla_login"} &&
- defined $::FORM{"Bugzilla_password"}) {
-
- $enteredlogin = $::FORM{"Bugzilla_login"};
- my $enteredpwd = $::FORM{"Bugzilla_password"};
- CheckEmailSyntax($enteredlogin);
-
- $realcryptpwd = PasswordForLogin($::FORM{"Bugzilla_login"});
-
- if (defined $::FORM{"PleaseMailAPassword"}) {
- my $realpwd;
- if ($realcryptpwd eq "") {
- $realpwd = InsertNewUser($enteredlogin, "");
- } else {
- SendSQL("select password from profiles where login_name = " .
- SqlQuote($enteredlogin));
- $realpwd = FetchOneColumn();
- }
- print "Content-type: text/html\n\n";
- PutHeader("Password has been emailed");
- MailPassword($enteredlogin, $realpwd);
- PutFooter();
- exit;
- }
- SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " .
- SqlQuote(substr($realcryptpwd, 0, 2)) . ")");
- my $enteredcryptpwd = FetchOneColumn();
+ # If the form contains Bugzilla login and password fields, use Bugzilla's
+ # built-in authentication to authenticate the user (otherwise use LDAP below).
+ if (defined $::FORM{"Bugzilla_login"} && defined $::FORM{"Bugzilla_password"}) {
+ # Make sure the user's login name is a valid email address.
+ $enteredlogin = $::FORM{"Bugzilla_login"};
+ CheckEmailSyntax($enteredlogin);
+
+ # Retrieve the user's ID and crypted password from the database.
+ my $userid;
+ SendSQL("SELECT userid, cryptpassword FROM profiles
+ WHERE login_name = " . SqlQuote($enteredlogin));
+ ($userid, $realcryptpwd) = FetchSQLData();
+
+ # Make sure the user exists or throw an error (but do not admit it was a username
+ # error to make it harder for a cracker to find account names by brute force).
+ $userid
+ || DisplayError("The username or password you entered is not valid.")
+ && exit;
+
+ # If this is a new user, generate a password, insert a record
+ # into the database, and email their password to them.
+ if ( defined $::FORM{"PleaseMailAPassword"} && !$userid ) {
+ my $password = InsertNewUser($enteredlogin, "");
+ print "Content-Type: text/html\n\n";
+ PutHeader("Account Created");
+ MailPassword($enteredlogin, $password);
+ PutFooter();
+ exit;
+ }
+
+ # Otherwise, authenticate the user.
+ else {
+ # Get the salt from the user's crypted password.
+ my $salt = $realcryptpwd;
+
+ # Using the salt, crypt the password the user entered.
+ my $enteredCryptedPassword = crypt( $::FORM{"Bugzilla_password"} , $salt );
+
+ # Make sure the passwords match or throw an error.
+ ($enteredCryptedPassword eq $realcryptpwd)
+ || DisplayError("The username or password you entered is not valid.")
+ && exit;
+
+ # If the user has successfully logged in, delete any password tokens
+ # lying around in the system for them.
+ use Token;
+ my $token = Token::HasPasswordToken($userid);
+ while ( $token ) {
+ Token::Cancel($token, "user logged in");
+ $token = Token::HasPasswordToken($userid);
+ }
+ }
- if ($realcryptpwd eq "" || $enteredcryptpwd ne $realcryptpwd) {
- print "Content-type: text/html\n\n";
- PutHeader("Login failed");
- print "The username or password you entered is not valid.\n";
- print "Please click <b>Back</b> and try again.\n";
- PutFooter();
- exit;
- }
} elsif (Param("useLDAP") &&
defined $::FORM{"LDAP_login"} &&
defined $::FORM{"LDAP_password"}) {
@@ -831,7 +968,7 @@ Content-type: text/html
exit();
}
print "Content-type: text/html\n\n";
- PutHeader("Login", undef, undef, undef, 1);
+ PutHeader("Login");
if(Param("useLDAP")) {
print "I need a legitimate LDAP username and password to continue.\n";
} else {
@@ -839,14 +976,19 @@ Content-type: text/html
}
if (!defined $nexturl || $nexturl eq "") {
# Sets nexturl to be argv0, stripping everything up to and
- # including the last slash.
- $0 =~ m:[^/]*$:;
+ # including the last slash (or backslash on Windows).
+ $0 =~ m:[^/\\]*$:;
$nexturl = $&;
}
my $method = "POST";
- if (defined $ENV{"REQUEST_METHOD"} && length($::buffer) > 1) {
- $method = $ENV{"REQUEST_METHOD"};
- }
+# We always want to use POST here, because we're submitting a password and don't
+# want to see it in the location bar in the browser in case a co-worker is looking
+# over your shoulder. If you have cookies off and need to bookmark the query, you
+# can bookmark it from the screen asking for your password, and it should still
+# work. See http://bugzilla.mozilla.org/show_bug.cgi?id=15980
+# if (defined $ENV{"REQUEST_METHOD"} && length($::buffer) > 1) {
+# $method = $ENV{"REQUEST_METHOD"};
+# }
print "
<FORM action=$nexturl method=$method>
<table>
@@ -872,23 +1014,34 @@ Content-type: text/html
</tr>
</table>
";
- foreach my $i (keys %::FORM) {
- if ($i =~ /^Bugzilla_/) {
- next;
- }
- print "<input type=hidden name=$i value=\"@{[value_quote($::FORM{$i})]}\">\n";
+ # Add all the form fields into the form as hidden fields
+ # (except for Bugzilla_login and Bugzilla_password which we
+ # already added as text fields above).
+ foreach my $i ( grep( $_ !~ /^Bugzilla_/ , keys %::FORM ) ) {
+ print qq|<input type="hidden" name="$i" value="@{[value_quote($::FORM{$i})]}">\n|;
}
- print "
-<input type=submit value=Login name=GoAheadAndLogIn><hr>
-";
- # If we're using LDAP, we can't request that a password be mailed...
- unless(Param("useLDAP")) {
- print "
-If you don't have a password, or have forgotten it, then please fill in the
-e-mail address above and click
- here:<input type=submit value=\"E-mail me a password\"
-name=PleaseMailAPassword>
-</form>\n";
+
+ print qq|
+ <input type="submit" name="GoAheadAndLogIn" value="Login">
+ </form>
+ |;
+
+ # Allow the user to request a token to change their password (unless
+ # we are using LDAP, in which case the user must use LDAP to change it).
+ unless( Param("useLDAP") ) {
+ print qq|
+ <hr>
+ <form method="get" action="token.cgi">
+ <input type="hidden" name="a" value="reqpw">
+ If you have forgotten your password,
+ enter your login name below and submit a request
+ to change your password.<br>
+ <input size="35" name="loginname">
+ <input type="submit" value="Submit Request">
+ </form>
+ <hr>
+ If you don't have a Bugzilla account, you can <a href="createaccount.cgi">create a new account</a>.
+ |;
}
# This seems like as good as time as any to get rid of old
@@ -914,7 +1067,7 @@ name=PleaseMailAPassword>
sub PutHeader {
- my ($title, $h1, $h2, $extra, $ignoreshutdown, $jscript) = (@_);
+ my ($title, $h1, $h2, $extra, $jscript) = (@_);
if (!defined $h1) {
$h1 = $title;
@@ -926,6 +1079,16 @@ sub PutHeader {
$extra = "";
}
$jscript ||= "";
+ # If we are shutdown, we want a very basic page to give that
+ # information. Also, the page title should indicate that
+ # we are down.
+ if (Param('shutdownhtml')) {
+ $title = "Bugzilla is Down";
+ $h1 = "Bugzilla is currently down";
+ $h2 = "";
+ $extra = "";
+ $jscript = "";
+ }
print "<HTML><HEAD>\n<TITLE>$title</TITLE>\n";
print Param("headerhtml") . "\n$jscript\n</HEAD>\n";
@@ -949,7 +1112,10 @@ sub PutHeader {
print "</TD></TR></TABLE>\n";
if (Param("shutdownhtml")) {
- if (!$ignoreshutdown) {
+ # If we are dealing with the params page, we want
+ # to ignore shutdownhtml
+ if ($0 !~ m:[\\/](do)?editparams.cgi$:) {
+ print "<p>\n";
print Param("shutdownhtml");
exit;
}
@@ -963,6 +1129,20 @@ sub PutFooter {
}
+sub DisplayError {
+ my ($message, $title) = (@_);
+ $title ||= "Error";
+
+ print "Content-type: text/html\n\n";
+ PutHeader($title);
+
+ print PerformSubsts( Param("errorhtml") , {errormsg => $message} );
+
+ PutFooter();
+
+ return 1;
+}
+
sub PuntTryAgain ($) {
my ($str) = (@_);
print PerformSubsts(Param("errorhtml"),
@@ -985,12 +1165,12 @@ sub CheckIfVotedConfirmed {
"WHERE bug_id = $id");
my $fieldid = GetFieldID("bug_status");
SendSQL("INSERT INTO bugs_activity " .
- "(bug_id,who,bug_when,fieldid,oldvalue,newvalue) VALUES " .
+ "(bug_id,who,bug_when,fieldid,removed,added) VALUES " .
"($id,$who,now(),$fieldid,'$::unconfirmedstate','NEW')");
if (!$everconfirmed) {
$fieldid = GetFieldID("everconfirmed");
SendSQL("INSERT INTO bugs_activity " .
- "(bug_id,who,bug_when,fieldid,oldvalue,newvalue) VALUES " .
+ "(bug_id,who,bug_when,fieldid,removed,added) VALUES " .
"($id,$who,now(),$fieldid,'0','1')");
}
AppendComment($id, DBID_to_name($who),
@@ -1016,7 +1196,7 @@ sub DumpBugActivity {
my $query = "
SELECT IFNULL(fielddefs.name, bugs_activity.fieldid),
bugs_activity.bug_when,
- bugs_activity.oldvalue, bugs_activity.newvalue,
+ bugs_activity.removed, bugs_activity.added,
profiles.login_name
FROM bugs_activity LEFT JOIN fielddefs ON
bugs_activity.fieldid = fielddefs.fieldid,
@@ -1027,31 +1207,44 @@ sub DumpBugActivity {
SendSQL($query);
- print "<table border cellpadding=4>\n";
- print "<tr>\n";
- print " <th>Who</th><th>What</th><th>Old value</th><th>New value</th><th>When</th>\n";
- print "</tr>\n";
+ # Instead of outright printing this, we are going to store it in a $html
+ # variable and print it and the end. This is so we can explain ? (if nesc.)
+ # at the top of the activity table rather than the botom.
+ my $html = "";
+ $html .= "<table border cellpadding=4>\n";
+ $html .= "<tr>\n";
+ $html .= " <th>Who</th><th>What</th><th>Removed</th><th>Added</th><th>When</th>\n";
+ $html .= "</tr>\n";
my @row;
+ my $incomplete_data = 0;
while (@row = FetchSQLData()) {
- my ($field,$when,$old,$new,$who) = (@row);
- $old = value_quote($old);
- $new = value_quote($new);
- if ($old eq "") {
- $old = " ";
+ my ($field,$when,$removed,$added,$who) = (@row);
+ $removed = html_quote($removed);
+ $added = html_quote($added);
+ $removed = " " if $removed eq "";
+ $added = " " if $added eq "";
+ if ($added =~ /^\?/ || $removed =~ /^\?/) {
+ $incomplete_data = 1;
}
- if ($new eq "") {
- $new = " ";
- }
- print "<tr>\n";
- print "<td>$who</td>\n";
- print "<td>$field</td>\n";
- print "<td>$old</td>\n";
- print "<td>$new</td>\n";
- print "<td>$when</td>\n";
- print "</tr>\n";
+ $html .= "<tr>\n";
+ $html .= "<td>$who</td>\n";
+ $html .= "<td>$field</td>\n";
+ $html .= "<td>$removed</td>\n";
+ $html .= "<td>$added</td>\n";
+ $html .= "<td>$when</td>\n";
+ $html .= "</tr>\n";
+ }
+ $html .= "</table>\n";
+ if ($incomplete_data) {
+ print "There was a bug in older versions of Bugzilla which caused activity data \n";
+ print "to be lost if there was a large number of cc's or dependencies. That \n";
+ print "has been fixed, however, there was some data already lost on this bug \n";
+ print "that could not be regenerated. The changes that the script could not \n";
+ print "reliably determine are prefixed by '?'\n";
+ print "<p>\n";
}
- print "</table>\n";
+ print $html;
}
diff --git a/CVS/Entries b/CVS/Entries
index d764ce59b..af9f3d3dd 100644
--- a/CVS/Entries
+++ b/CVS/Entries
@@ -1,73 +1,76 @@
-/.cvsignore/1.3/Fri Dec 22 20:48:16 2000//
-/1x1.gif/1.1/Wed Aug 26 06:14:15 1998/-kb/
-/Bug.pm/1.6/Mon Feb 26 23:46:01 2001//
-/CGI.pl/1.81/Sat Mar 10 22:06:57 2001//
-/CHANGES/1.38/Tue Oct 12 16:57:57 1999//
-/README/1.48/Wed Apr 25 07:11:45 2001//
-/RelationSet.pm/1.4/Tue Apr 17 02:26:14 2001//
-/ant.jpg/1.2/Wed Aug 26 22:36:05 1998/-kb/
-/backdoor.cgi/1.14/Wed May 17 21:29:31 2000//
-/booleanchart.html/1.3/Wed Aug 16 23:07:37 2000//
-/bug_form.pl/1.64/Tue Apr 17 02:26:14 2001//
-/bug_status.html/1.11/Mon Aug 28 17:48:56 2000//
-/buglist.cgi/1.127/Sat Apr 7 03:30:59 2001//
-/bugwritinghelp.html/1.1/Tue Mar 7 17:59:38 2000//
-/bugzilla.dtd/1.2/Fri May 26 06:34:45 2000//
-/changepassword.cgi/1.19/Tue Jan 25 07:53:29 2000//
-/checksetup.pl/1.74/Fri Apr 20 14:41:44 2001//
-/colchange.cgi/1.16/Thu Aug 31 18:19:46 2000//
-/collectstats.pl/1.19/Thu Apr 19 17:35:23 2001//
-/confirmhelp.html/1.2/Mon Aug 28 17:48:58 2000//
-/createaccount.cgi/1.10/Fri Mar 9 21:41:27 2001//
-/createattachment.cgi/1.13/Tue Apr 3 20:42:58 2001//
-/defparams.pl/1.50/Sun Apr 22 16:44:10 2001//
-/describecomponents.cgi/1.5/Thu Feb 22 18:11:24 2001//
-/describekeywords.cgi/1.4/Sat Jan 22 16:51:49 2000//
-/doeditparams.cgi/1.12/Fri Sep 29 05:29:09 2000//
-/doeditvotes.cgi/1.8/Wed Jun 7 17:49:02 2000//
-/duplicates.cgi/1.8/Thu Apr 19 17:35:23 2001//
-/editcomponents.cgi/1.16/Thu Feb 22 18:11:25 2001//
-/editgroups.cgi/1.9/Tue Apr 17 02:26:15 2001//
-/editkeywords.cgi/1.7/Mon Feb 26 23:25:22 2001//
-/editmilestones.cgi/1.4/Fri Apr 6 16:47:49 2001//
-/editparams.cgi/1.11/Fri Jan 14 22:35:34 2000//
-/editproducts.cgi/1.17/Thu Aug 31 22:56:21 2000//
-/editusers.cgi/1.20/Tue Apr 17 02:26:15 2001//
-/editversions.cgi/1.6/Wed Aug 30 23:44:35 2000//
-/enter_bug.cgi/1.43/Tue Apr 17 02:26:15 2001//
-/globals.pl/1.87/Wed Apr 25 15:45:27 2001//
-/help.html/1.4/Fri Jan 21 22:01:11 2000//
-/helpemailquery.html/1.1/Tue Jan 19 00:07:45 1999//
-/how_to_mail.html/1.2/Mon Nov 1 23:33:16 1999//
-/importxml.pl/1.13/Thu Jul 13 23:12:51 2000//
-/index.html/1.12/Wed Feb 28 23:07:24 2001//
-/localconfig.js/1.1/Wed Feb 28 23:07:25 2001//
-/long_list.cgi/1.15/Mon Aug 7 22:59:55 2000//
-/move.pl/1.3/Thu Jul 13 23:12:51 2000//
-/new_comment.cgi/1.5/Thu Jul 27 20:10:16 2000//
-/newquip.html/1.3/Mon Nov 1 23:33:17 1999//
-/notargetmilestone.html/1.2/Mon Aug 28 17:48:59 2000//
-/post_bug.cgi/1.31/Mon Apr 9 19:10:43 2001//
-/process_bug.cgi/1.80/Tue Apr 17 02:26:16 2001//
-/processmail/1.61/Sat Apr 7 17:09:27 2001//
-/query.cgi/1.82/Tue Apr 10 03:49:01 2001//
-/queryhelp.cgi/1.4/Mon Apr 23 22:16:12 2001//
-/quicksearch.html/1.1/Wed Feb 28 23:07:26 2001//
-/quicksearch.js/1.2/Thu Mar 1 03:34:08 2001//
-/quicksearchhack.html/1.2/Wed Feb 28 23:08:52 2001//
-/relogin.cgi/1.10/Tue Jan 18 14:41:00 2000//
-/reports.cgi/1.45/Fri Mar 9 21:24:53 2001//
-/robots.txt/1.1/Fri Jul 28 21:28:39 2000//
-/sanitycheck.cgi/1.31/Sun Apr 8 02:33:02 2001//
-/show_activity.cgi/1.5/Fri Jan 14 22:35:45 2000//
-/show_bug.cgi/1.14/Mon Mar 12 22:35:50 2001//
-/showattachment.cgi/1.6/Tue Mar 7 19:27:41 2000//
-/showdependencygraph.cgi/1.9/Tue Mar 7 18:23:00 2000//
-/showdependencytree.cgi/1.7/Fri Jan 14 22:35:48 2000//
-/showvotes.cgi/1.7/Wed Jan 24 02:41:41 2001//
-/syncshadowdb/1.8/Tue Oct 24 01:51:56 2000//
-/userprefs.cgi/1.16/Tue Apr 17 02:26:16 2001//
-/votehelp.html/1.5/Thu Jan 25 04:56:14 2001//
-/whineatnews.pl/1.4/Mon Nov 1 23:33:22 1999//
-/xml.cgi/1.2/Mon Jun 12 06:52:41 2000//
-D
+/.cvsignore/1.4/Wed Jul 25 07:26:42 2001//TBUGZILLA-2_14
+/1x1.gif/1.1/Wed Aug 26 06:14:15 1998/-kb/TBUGZILLA-2_14
+/Bug.pm/1.6/Mon Feb 26 23:46:01 2001//TBUGZILLA-2_14
+/CGI.pl/1.100/Sun Aug 26 18:51:45 2001//TBUGZILLA-2_14
+/README/1.50/Sat Aug 11 19:56:40 2001//TBUGZILLA-2_14
+/RelationSet.pm/1.5/Fri Jun 1 02:14:23 2001//TBUGZILLA-2_14
+/Token.pm/1.3/Fri Aug 17 08:38:54 2001//TBUGZILLA-2_14
+/UPGRADING/1.1/Fri Aug 10 22:35:21 2001//TBUGZILLA-2_14
+/UPGRADING-pre-2.8/1.1/Fri Aug 10 22:35:22 2001//TBUGZILLA-2_14
+/ant.jpg/1.2/Wed Aug 26 22:36:05 1998/-kb/TBUGZILLA-2_14
+/booleanchart.html/1.3/Wed Aug 16 23:07:37 2000//TBUGZILLA-2_14
+/bug_form.pl/1.70/Fri Aug 17 11:15:04 2001//TBUGZILLA-2_14
+/bug_status.html/1.11/Mon Aug 28 17:48:56 2000//TBUGZILLA-2_14
+/buglist.cgi/1.139/Fri Aug 24 17:32:24 2001//TBUGZILLA-2_14
+/bugwritinghelp.html/1.1/Tue Mar 7 17:59:38 2000//TBUGZILLA-2_14
+/bugzilla.dtd/1.2/Fri May 26 06:34:45 2000//TBUGZILLA-2_14
+/changepassword.cgi/1.19/Tue Jan 25 07:53:29 2000//TBUGZILLA-2_14
+/checksetup.pl/1.99/Sun Aug 19 18:26:21 2001//TBUGZILLA-2_14
+/colchange.cgi/1.17/Fri Jun 1 02:07:28 2001//TBUGZILLA-2_14
+/collectstats.pl/1.20/Wed Jun 6 21:17:40 2001//TBUGZILLA-2_14
+/confirmhelp.html/1.2/Mon Aug 28 17:48:58 2000//TBUGZILLA-2_14
+/createaccount.cgi/1.11/Wed Jul 11 05:29:18 2001//TBUGZILLA-2_14
+/createattachment.cgi/1.13/Tue Apr 3 20:42:58 2001//TBUGZILLA-2_14
+/defparams.pl/1.56/Sat Aug 25 00:12:12 2001//TBUGZILLA-2_14
+/describecomponents.cgi/1.6/Wed Jun 6 04:32:45 2001//TBUGZILLA-2_14
+/describekeywords.cgi/1.4/Sat Jan 22 16:51:49 2000//TBUGZILLA-2_14
+/doeditparams.cgi/1.15/Mon Aug 13 19:11:33 2001//TBUGZILLA-2_14
+/doeditvotes.cgi/1.12/Tue Aug 28 17:55:14 2001//TBUGZILLA-2_14
+/duplicates.cgi/1.13/Tue Aug 21 00:36:54 2001//TBUGZILLA-2_14
+/editcomponents.cgi/1.17/Sat Jun 16 14:51:15 2001//TBUGZILLA-2_14
+/editgroups.cgi/1.12/Wed Jun 6 03:16:49 2001//TBUGZILLA-2_14
+/editkeywords.cgi/1.7/Mon Feb 26 23:25:22 2001//TBUGZILLA-2_14
+/editmilestones.cgi/1.5/Sat Jun 16 14:51:16 2001//TBUGZILLA-2_14
+/editparams.cgi/1.12/Mon Aug 13 19:11:33 2001//TBUGZILLA-2_14
+/editproducts.cgi/1.18/Sat Jun 16 14:51:16 2001//TBUGZILLA-2_14
+/editusers.cgi/1.23/Wed Jul 11 05:29:19 2001//TBUGZILLA-2_14
+/editversions.cgi/1.8/Tue Jun 19 01:37:02 2001//TBUGZILLA-2_14
+/enter_bug.cgi/1.50/Sun Jul 1 02:00:56 2001//TBUGZILLA-2_14
+/globals.pl/1.110/Wed Aug 29 19:52:13 2001//TBUGZILLA-2_14
+/help.html/1.4/Fri Jan 21 22:01:11 2000//TBUGZILLA-2_14
+/helpemailquery.html/1.1/Tue Jan 19 00:07:45 1999//TBUGZILLA-2_14
+/how_to_mail.html/1.2/Mon Nov 1 23:33:16 1999//TBUGZILLA-2_14
+/importxml.pl/1.18/Wed Jul 25 20:12:00 2001//TBUGZILLA-2_14
+/index.html/1.12/Wed Feb 28 23:07:24 2001//TBUGZILLA-2_14
+/localconfig.js/1.1/Wed Feb 28 23:07:25 2001//TBUGZILLA-2_14
+/long_list.cgi/1.15/Mon Aug 7 22:59:55 2000//TBUGZILLA-2_14
+/move.pl/1.6/Fri Jul 20 15:18:30 2001//TBUGZILLA-2_14
+/new_comment.cgi/1.5/Thu Jul 27 20:10:16 2000//TBUGZILLA-2_14
+/notargetmilestone.html/1.2/Mon Aug 28 17:48:59 2000//TBUGZILLA-2_14
+/post_bug.cgi/1.34/Wed Jun 27 02:31:55 2001//TBUGZILLA-2_14
+/process_bug.cgi/1.96/Sun Aug 26 22:58:34 2001//TBUGZILLA-2_14
+/processmail/1.68/Mon Aug 13 17:06:38 2001//TBUGZILLA-2_14
+/query.cgi/1.85/Mon Aug 13 19:11:35 2001//TBUGZILLA-2_14
+/queryhelp.cgi/1.4/Mon Apr 23 22:16:12 2001//TBUGZILLA-2_14
+/quicksearch.html/1.1/Wed Feb 28 23:07:26 2001//TBUGZILLA-2_14
+/quicksearch.js/1.7/Fri Jul 20 08:25:30 2001//TBUGZILLA-2_14
+/quicksearchhack.html/1.2/Wed Feb 28 23:08:52 2001//TBUGZILLA-2_14
+/quips.cgi/1.1/Tue May 29 04:01:48 2001//TBUGZILLA-2_14
+/relogin.cgi/1.10/Tue Jan 18 14:41:00 2000//TBUGZILLA-2_14
+/reports.cgi/1.47/Sun Jul 1 19:09:29 2001//TBUGZILLA-2_14
+/robots.txt/1.1/Fri Jul 28 21:28:39 2000//TBUGZILLA-2_14
+/sanitycheck.cgi/1.33/Wed Jul 11 05:29:20 2001//TBUGZILLA-2_14
+/show_activity.cgi/1.6/Fri Jun 1 13:38:01 2001//TBUGZILLA-2_14
+/show_bug.cgi/1.15/Sat Jun 2 22:02:02 2001//TBUGZILLA-2_14
+/showattachment.cgi/1.7/Wed Jun 6 18:36:25 2001//TBUGZILLA-2_14
+/showdependencygraph.cgi/1.10/Thu May 31 15:52:24 2001//TBUGZILLA-2_14
+/showdependencytree.cgi/1.8/Thu May 31 15:52:24 2001//TBUGZILLA-2_14
+/showvotes.cgi/1.9/Thu May 31 15:52:25 2001//TBUGZILLA-2_14
+/syncshadowdb/1.12/Sun Jun 10 17:38:15 2001//TBUGZILLA-2_14
+/token.cgi/1.2/Fri Aug 17 12:42:34 2001//TBUGZILLA-2_14
+/userprefs.cgi/1.20/Wed Jul 11 05:29:21 2001//TBUGZILLA-2_14
+/votehelp.html/1.5/Thu Jan 25 04:56:14 2001//TBUGZILLA-2_14
+/whineatnews.pl/1.4/Mon Nov 1 23:33:22 1999//TBUGZILLA-2_14
+/xml.cgi/1.2/Mon Jun 12 06:52:41 2000//TBUGZILLA-2_14
+D/contrib////
+D/docs////
diff --git a/CVS/Entries.Log b/CVS/Entries.Log
deleted file mode 100644
index 09ae25c15..000000000
--- a/CVS/Entries.Log
+++ /dev/null
@@ -1,4 +0,0 @@
-A D/contrib////
-A D/docs////
-A D/oracle////
-A D/template////
diff --git a/CVS/Tag b/CVS/Tag
new file mode 100644
index 000000000..c10f87310
--- /dev/null
+++ b/CVS/Tag
@@ -0,0 +1 @@
+NBUGZILLA-2_14
diff --git a/README b/README
index c628f66af..4ec17dde6 100644
--- a/README
+++ b/README
@@ -1,7 +1,3 @@
- =====================
- BUGZILLA 2.12 RELEASE
- =====================
-
* This README is no longer used to house installation instructions. Instead,
it contains pointers to where you may find the information you need.
@@ -9,7 +5,12 @@ it contains pointers to where you may find the information you need.
types available. Please refer to these documents when installing, configuring,
and maintaining your Bugzilla installation. A helpful starting point is
docs/txt/Bugzilla-Guide.txt, or with a web browser at docs/html/index.html.
-
-* Release Notes for Bugzilla 2.12 are available at docs/rel_notes.txt.
+
+* Release notes for people upgrading to a new version of Bugzilla are
+available at docs/rel_notes.txt.
* If you wish to contribute to the documentation, please read docs/README.docs.
+
+* The Bugzilla web site is at "http://www.mozilla.org/projects/bugzilla/".
+This site will contain the latest Bugzilla information, including how to
+report bugs and how to get help with Bugzilla.
diff --git a/RelationSet.pm b/RelationSet.pm
index bc31c96c7..4b778a6fd 100644
--- a/RelationSet.pm
+++ b/RelationSet.pm
@@ -32,7 +32,11 @@
use diagnostics;
use strict;
-require "globals.pl";
+# Everything that uses RelationSet should already have globals.pl loaded
+# so we don't want to load it here. Doing so causes a loop in Perl because
+# globals.pl turns around and does a 'use RelationSet'
+# See http://bugzilla.mozilla.org/show_bug.cgi?id=72862
+#require "globals.pl";
package RelationSet;
use CGI::Carp qw(fatalsToBrowser);
@@ -260,3 +264,5 @@ sub toString {
return join(',', sort(@result));
}
+
+1;
diff --git a/Token.pm b/Token.pm
new file mode 100644
index 000000000..185884c98
--- /dev/null
+++ b/Token.pm
@@ -0,0 +1,185 @@
+#!/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 Netscape Communications
+# Corporation. Portions created by Netscape are
+# Copyright (C) 1998 Netscape Communications Corporation. All
+# Rights Reserved.
+#
+# Contributor(s): Myk Melez <myk@mozilla.org>
+
+################################################################################
+# Module Initialization
+################################################################################
+
+# Make it harder for us to do dangerous things in Perl.
+use diagnostics;
+use strict;
+
+# Bundle the functions in this file together into the "Token" package.
+package Token;
+
+# This module requires that its caller have said "require CGI.pl" to import
+# relevant functions from that script and its companion globals.pl.
+
+################################################################################
+# Functions
+################################################################################
+
+sub IssuePasswordToken {
+ # Generates a random token, adds it to the tokens table, and sends it
+ # to the user with instructions for using it to change their password.
+
+ my ($loginname) = @_;
+
+ # Retrieve the user's ID from the database.
+ my $quotedloginname = &::SqlQuote($loginname);
+ &::SendSQL("SELECT userid FROM profiles WHERE login_name = $quotedloginname");
+ my ($userid) = &::FetchSQLData();
+
+ # Generate a unique token and insert it into the tokens table.
+ # We have to lock the tokens table before generating the token,
+ # since the database must be queried for token uniqueness.
+ &::SendSQL("LOCK TABLES tokens WRITE");
+ my $token = GenerateUniqueToken();
+ my $quotedtoken = &::SqlQuote($token);
+ my $quotedipaddr = &::SqlQuote($::ENV{'REMOTE_ADDR'});
+ &::SendSQL("INSERT INTO tokens ( userid , issuedate , token , tokentype , eventdata )
+ VALUES ( $userid , NOW() , $quotedtoken , 'password' , $quotedipaddr )");
+ &::SendSQL("UNLOCK TABLES");
+
+ # Mail the user the token along with instructions for using it.
+ MailPasswordToken($loginname, $token);
+
+}
+
+
+sub GenerateUniqueToken {
+ # Generates a unique random token. Uses &GenerateRandomPassword
+ # for the tokens themselves and checks uniqueness by searching for
+ # the token in the "tokens" table. Gives up if it can't come up
+ # with a token after about one hundred tries.
+
+ my $token;
+ my $duplicate = 1;
+ my $tries = 0;
+ while ($duplicate) {
+
+ ++$tries;
+ if ($tries > 100) {
+ &::DisplayError("Something is seriously wrong with the token generation system.");
+ exit;
+ }
+
+ $token = &::GenerateRandomPassword();
+ &::SendSQL("SELECT userid FROM tokens WHERE token = " . &::SqlQuote($token));
+ $duplicate = &::FetchSQLData();
+ }
+
+ return $token;
+
+}
+
+sub MailPasswordToken {
+ # Emails a password token to a user along with instructions for its use.
+ # Called exclusively from &IssuePasswordToken.
+
+ my ($emailaddress, $token) = @_;
+
+ my $urlbase = &::Param("urlbase");
+ my $emailsuffix = &::Param('emailsuffix');
+ $token = &::url_quote($token);
+
+ open SENDMAIL, "|/usr/lib/sendmail -t";
+
+ print SENDMAIL qq|From: bugzilla-daemon
+To: $emailaddress$emailsuffix
+Subject: Bugzilla Change Password Request
+
+You or someone impersonating you has requested to change your Bugzilla
+password. To change your password, visit the following link:
+
+${urlbase}token.cgi?a=cfmpw&t=$token
+
+If you are not the person who made this request, or you wish to cancel
+this request, visit the following link:
+
+${urlbase}token.cgi?a=cxlpw&t=$token
+|;
+ close SENDMAIL;
+}
+
+sub Cancel {
+ # Cancels a previously issued token and notifies the system administrator.
+ # This should only happen when the user accidentally makes a token request
+ # or when a malicious hacker makes a token request on behalf of a user.
+
+ my ($token, $cancelaction) = @_;
+
+ # Quote the token for inclusion in SQL statements.
+ my $quotedtoken = &::SqlQuote($token);
+
+ # Get information about the token being cancelled.
+ &::SendSQL("SELECT issuedate , tokentype , eventdata , login_name , realname
+ FROM tokens, profiles
+ WHERE tokens.userid = profiles.userid
+ AND token = $quotedtoken");
+ my ($issuedate, $tokentype, $eventdata, $loginname, $realname) = &::FetchSQLData();
+
+ # Get the email address of the Bugzilla maintainer.
+ my $maintainer = &::Param('maintainer');
+
+ # Format the user's real name and email address into a single string.
+ my $username = $realname ? $realname . " <" . $loginname . ">" : $loginname;
+
+ # Notify the user via email about the cancellation.
+ open SENDMAIL, "|/usr/lib/sendmail -t";
+ print SENDMAIL qq|From: bugzilla-daemon
+To: $username
+Subject: "$tokentype" token cancelled
+
+A token was cancelled from $::ENV{'REMOTE_ADDR'}. This is either
+an honest mistake or the result of a malicious hack attempt.
+Take a look at the information below and forward this email
+to $maintainer if you suspect foul play.
+
+ Token: $token
+ Token Type: $tokentype
+ User: $username
+ Issue Date: $issuedate
+ Event Data: $eventdata
+
+Cancelled Because: $cancelaction
+|;
+ close SENDMAIL;
+
+ # Delete the token from the database.
+ &::SendSQL("LOCK TABLES tokens WRITE");
+ &::SendSQL("DELETE FROM tokens WHERE token = $quotedtoken");
+ &::SendSQL("UNLOCK TABLES");
+}
+
+sub HasPasswordToken {
+ # Returns a password token if the user has one. Otherwise returns 0 (false).
+
+ my ($userid) = @_;
+
+ &::SendSQL("SELECT token FROM tokens WHERE userid = $userid LIMIT 1");
+ my ($token) = &::FetchSQLData();
+
+ return $token;
+}
+
+1;
diff --git a/UPGRADING b/UPGRADING
new file mode 100644
index 000000000..fb5e99f0d
--- /dev/null
+++ b/UPGRADING
@@ -0,0 +1,3 @@
+Please consult The Bugzilla Guide for instructions on how to upgrade
+Bugzilla from an older version. The Guide can be found with this
+distribution, in docs/html, docs/txt, and docs/sgml.
diff --git a/CHANGES b/UPGRADING-pre-2.8
similarity index 97%
rename from CHANGES
rename to UPGRADING-pre-2.8
index 6e1051a5a..3c98c2c36 100644
--- a/CHANGES
+++ b/UPGRADING-pre-2.8
@@ -1,7 +1,10 @@
-This file contains only important changes made to Bugzilla. If you
-are updating from an older verseion, make sure that you check this file!
+This file contains only important changes made to Bugzilla before release
+2.8. If you are upgrading from version older than 2.8, please read this file.
+If you are upgrading from 2.8 or newer, please read the Installation and
+Upgrade instructions in The Bugzilla Guide, found with this distribution in
+docs/html, docs/txt, and docs/sgml.
-For a more complete list of what has changed, use Bonsai
+For a complete list of what changes, use Bonsai
(http://cvs-mirror.mozilla.org/webtools/bonsai/cvsqueryform.cgi) to
query the CVS tree. For example,
diff --git a/backdoor.cgi b/backdoor.cgi
deleted file mode 100755
index f46cb6759..000000000
--- a/backdoor.cgi
+++ /dev/null
@@ -1,178 +0,0 @@
-#!/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 Netscape Communications
-# Corporation. Portions created by Netscape are
-# Copyright (C) 1998 Netscape Communications Corporation. All
-# Rights Reserved.
-#
-# Contributor(s): Terry Weissman <terry@mozilla.org>
-
-# Provides a silly 'back-door' mechanism to let me automatically insert
-# bugs from the netscape bugsystem. Other installations of Bugzilla probably
-# don't need to worry about this file any.
-
-use diagnostics;
-use strict;
-
-require "CGI.pl";
-
-# Shut up misguided -w warnings about "used only once":
-
-use vars %::versions;
-
-
-ConnectToDatabase();
-
-print "Content-type: text/plain\n\n";
-
-# while (my ($key,$value) = each %ENV) {
-# print "$key=$value\n";
-# }
-
-my $host = $ENV{'REMOTE_ADDR'};
-
-# if (open(CODE, ">data/backdoorcode")) {
-# print CODE GenerateCode("%::FORM");
-# close(CODE);
-# }
-#
-# do "/tmp/backdoorcode";
-
-SendSQL("select passwd from backdoor where host = '$host'");
-my $passwd = FetchOneColumn();
-if (!defined $passwd || !defined $::FORM{'passwd'} ||
- $passwd ne crypt($::FORM{'passwd'}, substr($passwd, 0, 2))) {
- print "Who are you?\n";
- print "Env:\n";
- while (my ($key,$value) = each %ENV) {
- print "$key=$value\n";
- }
- print "\nForm:\n";
- while (my ($key,$value) = each %::FORM) {
- print "$key=$value\n";
- }
- exit;
-}
-
-
-
-my $prod = $::FORM{'product'};
-my $comp = $::FORM{'component'};
-my $version = $::FORM{'version'};
-
-GetVersionTable();
-
-
-sub Punt {
- my ($label, $value) = (@_);
- my $maintainer = Param("maintainer");
- print "I don't know how to move into Bugzilla a bug with a $label of $value.
-If you really do need to do this, speak to $maintainer and maybe he
-can teach me.";
- exit;
-}
-
-
-# Do remapping of things from BugSplat world to Bugzilla.
-
-if ($prod eq "Communicator") {
- $prod = "Browser";
- $version = "other";
-}
-
-if ($prod eq "NSS") {
- $version = "unspecified";
-}
-
-# Validate fields, and whine about things that we apparently couldn't remap
-# into something legal.
-
-
-if (!defined $::components{$prod}) {
- Punt("product", $prod);
-}
-if (lsearch($::components{$prod}, $comp) < 0) {
- Punt("component", $comp);
-}
-if (lsearch($::versions{$prod}, $version) < 0) {
- $version = "other";
- if (lsearch($::versions{$prod}, $version) < 0) {
- Punt("version", $version);
- }
-}
-
-
-$::FORM{'product'} = $prod;
-$::FORM{'component'} = $comp;
-$::FORM{'version'} = $version;
-
-
-my $longdesc =
- "(This bug imported from BugSplat, Netscape's internal bugsystem. It
-was known there as bug #$::FORM{'bug_id'}
-http://scopus.netscape.com/bugsplat/show_bug.cgi?id=$::FORM{'bug_id'}
-Imported into Bugzilla on " . time2str("%D %H:%M", time()) . ")
-
-" . $::FORM{'long_desc'};
-
-
-$::FORM{'reporter'} =
- DBNameToIdAndCheck("$::FORM{'reporter'}\@netscape.com", 1);
-$::FORM{'assigned_to'} =
- DBNameToIdAndCheck("$::FORM{'assigned_to'}\@netscape.com", 1);
-if ($::FORM{'qa_contact'} ne "") {
- $::FORM{'qa_contact'} =
- DBNameToIdAndCheck("$::FORM{'qa_contact'}\@netscape.com", 1);
-} else {
- $::FORM{'qa_contact'} = 0;
-}
-
-
-my @list = ('reporter', 'assigned_to', 'product', 'version', 'rep_platform',
- 'op_sys', 'bug_status', 'bug_severity', 'priority', 'component',
- 'short_desc', 'creation_ts', 'delta_ts',
- 'bug_file_loc', 'qa_contact', 'groupset');
-
-my @vallist;
-foreach my $i (@list) {
- push @vallist, SqlQuote($::FORM{$i});
-}
-
-my $query = "insert into bugs (" .
- join(',', @list) .
- ") values (" .
- join(',', @vallist) .
- ")";
-
-
-SendSQL($query);
-
-SendSQL("select LAST_INSERT_ID()");
-my $zillaid = FetchOneColumn();
-
-SendSQL("INSERT INTO longdescs (bug_id, who, bug_when, thetext) VALUES " .
- "($zillaid, $::FORM{'reporter'}, now(), " . SqlQuote($longdesc) . ")");
-
-
-foreach my $cc (split(/,/, $::FORM{'cc'})) {
- if ($cc ne "") {
- my $cid = DBNameToIdAndCheck("$cc\@netscape.com", 1);
- SendSQL("insert into cc (bug_id, who) values ($zillaid, $cid)");
- }
-}
-
-print "Created bugzilla bug $zillaid\n";
-system("./processmail", $zillaid);
diff --git a/bug_form.pl b/bug_form.pl
index 0706ede99..c554cb0b0 100644
--- a/bug_form.pl
+++ b/bug_form.pl
@@ -32,6 +32,7 @@ sub bug_form_pl_sillyness {
my $zz;
$zz = %::FORM;
$zz = %::components;
+ $zz = %::proddesc;
$zz = %::prodmaxvotes;
$zz = %::versions;
$zz = @::legal_keywords;
@@ -73,46 +74,24 @@ select
sum(votes.count)
from bugs left join votes using(bug_id)
where bugs.bug_id = $id
-and bugs.groupset & $::usergroupset = bugs.groupset
group by bugs.bug_id";
SendSQL($query);
my %bug;
my @row;
-if (@row = FetchSQLData()) {
- my $count = 0;
- foreach my $field ("bug_id", "product", "version", "rep_platform",
- "op_sys", "bug_status", "resolution", "priority",
- "bug_severity", "component", "assigned_to", "reporter",
- "bug_file_loc", "short_desc", "target_milestone",
- "qa_contact", "status_whiteboard", "creation_ts",
- "groupset", "delta_ts", "votes") {
- $bug{$field} = shift @row;
- if (!defined $bug{$field}) {
- $bug{$field} = "";
- }
- $count++;
+@row = FetchSQLData();
+my $count = 0;
+foreach my $field ("bug_id", "product", "version", "rep_platform",
+ "op_sys", "bug_status", "resolution", "priority",
+ "bug_severity", "component", "assigned_to", "reporter",
+ "bug_file_loc", "short_desc", "target_milestone",
+ "qa_contact", "status_whiteboard", "creation_ts",
+ "groupset", "delta_ts", "votes") {
+ $bug{$field} = shift @row;
+ if (!defined $bug{$field}) {
+ $bug{$field} = "";
}
-} else {
- SendSQL("select groupset from bugs where bug_id = $id");
- if (@row = FetchSQLData()) {
- print "<H1>Permission denied.</H1>\n";
- if ($loginok) {
- print "Sorry; you do not have the permissions necessary to see\n";
- print "bug $id.\n";
- } else {
- print "Sorry; bug $id can only be viewed when logged\n";
- print "into an account with the appropriate permissions. To\n";
- print "see this bug, you must first\n";
- print "<a href=\"show_bug.cgi?id=$id&GoAheadAndLogIn=1\">";
- print "log in</a>.";
- }
- } else {
- print "<H1>Bug not found</H1>\n";
- print "There does not seem to be a bug numbered $id.\n";
- }
- PutFooter();
- exit;
+ $count++;
}
my $assignedtoid = $bug{'assigned_to'};
@@ -204,7 +183,7 @@ print "
make_options($::versions{$bug{'product'}}, $bug{'version'}) .
"</SELECT></TD>
<TD> </TD>
- <TD ROWSPAN=4 ALIGN=RIGHT VALIGN=TOP><B>Cc:</B></TD>
+ <TD ROWSPAN=4 ALIGN=RIGHT VALIGN=TOP><B>CC:</B></TD>
<TD ROWSPAN=4 VALIGN=TOP> $cc_element </TD>
</TR><TR>
<TD ALIGN=RIGHT><B><A HREF=\"bug_status.html\">Status:</A></B></TD>
@@ -368,19 +347,82 @@ print "
if ($::usergroupset ne '0') {
- SendSQL("select bit, description, (bit & $bug{'groupset'} != 0) from groups where bit & $::usergroupset != 0 and isbuggroup != 0 order by bit");
+ SendSQL("select bit, name, description, (bit & $bug{'groupset'} != 0) " .
+ "from groups where bit & $::usergroupset != 0 " .
+ "and isbuggroup != 0 " .
+ # Include active groups as well as inactive groups to which
+ # the bug already belongs. This way the bug can be removed
+ # from an inactive group but can only be added to active ones.
+ "and (isactive = 1 or (bit & $bug{'groupset'} != 0)) " .
+ "order by description");
+ # We only print out a header bit for this section if there are any
+ # results.
+ my $groupFound = 0;
while (MoreSQLData()) {
- my ($bit, $description, $ison) = (FetchSQLData());
- my $check0 = !$ison ? " SELECTED" : "";
- my $check1 = $ison ? " SELECTED" : "";
- print "<select name=bit-$bit><option value=0$check0>\n";
- print "People not in the \"$description\" group can see this bug\n";
- print "<option value=1$check1>\n";
- print "Only people in the \"$description\" group can see this bug\n";
- print "</select><br>\n";
+ my ($bit, $name, $description, $ison) = (FetchSQLData());
+ # For product groups, we only want to display the checkbox if either
+ # (1) The bit is already set, or
+ # (2) It's the group for this product.
+ # All other product groups will be skipped. Non-product bug groups
+ # will still be displayed.
+ if($ison || ($name eq $bug{'product'}) || (!defined $::proddesc{$name})) {
+ if(!$groupFound) {
+ print "<br><b>Only users in the selected groups can view this bug:</b><br>\n";
+ print "<font size=\"-1\">(Leave all boxes unchecked to make this a public bug.)</font><br><br>\n";
+ $groupFound = 1;
+ }
+ # Modifying this to use checkboxes instead
+ my $checked = $ison ? " CHECKED" : "";
+ # indent these a bit
+ print " ";
+ print "<input type=checkbox name=\"bit-$bit\" value=1$checked>\n";
+ print "$description<br>\n";
+ }
+ }
+
+ # If the bug is restricted to a group, display checkboxes that allow
+ # the user to set whether or not the reporter, assignee, QA contact,
+ # and cc list can see the bug even if they are not members of all
+ # groups to which the bug is restricted.
+ if ( $bug{'groupset'} != 0 ) {
+ # Determine whether or not the bug is always accessible by the reporter,
+ # QA contact, and/or users on the cc: list.
+ SendSQL("SELECT reporter_accessible , assignee_accessible ,
+ qacontact_accessible , cclist_accessible
+ FROM bugs
+ WHERE bug_id = $id
+ ");
+ my ($reporter_accessible, $assignee_accessible, $qacontact_accessible, $cclist_accessible) = FetchSQLData();
+
+ # Convert boolean data about which roles always have access to the bug
+ # into "checked" attributes for the HTML checkboxes by which users
+ # set and change these values.
+ my $reporter_checked = $reporter_accessible ? " checked" : "";
+ my $assignee_checked = $assignee_accessible ? " checked" : "";
+ my $qacontact_checked = $qacontact_accessible ? " checked" : "";
+ my $cclist_checked = $cclist_accessible ? " checked" : "";
+
+ # Display interface for changing the values.
+ print qq|
+ <p>
+ <b>But users in the roles selected below can always view this bug:</b><br>
+ <small>(Does not take effect unless the bug is restricted to at least one group.)</small>
+ </p>
+
+ <p>
+ <input type="checkbox" name="reporter_accessible" value="1" $reporter_checked>Reporter
+ <input type="checkbox" name="assignee_accessible" value="1" $assignee_checked>Assignee
+ <input type="checkbox" name="qacontact_accessible" value="1" $qacontact_checked>QA Contact
+ <input type="checkbox" name="cclist_accessible" value="1" $cclist_checked>CC List
+ </p>
+ |;
}
}
+
+
+
+
print "<br>
<INPUT TYPE=radio NAME=knob VALUE=none CHECKED>
Leave as <b>$bug{'bug_status'} $bug{'resolution'}</b><br>";
diff --git a/buglist.cgi b/buglist.cgi
index 63296a914..2b2a394bf 100755
--- a/buglist.cgi
+++ b/buglist.cgi
@@ -21,6 +21,7 @@
# Contributor(s): Terry Weissman <terry@mozilla.org>
# Dan Mosedale <dmose@mozilla.org>
# Stephan Niemz <st.n@gmx.net>
+# Andreas Franke <afranke@mathweb.org>
use diagnostics;
use strict;
@@ -33,6 +34,7 @@ use Date::Parse;
sub sillyness {
my $zz;
+ $zz = $::db_name;
$zz = $::defaultqueryname;
$zz = $::unconfirmedstate;
$zz = @::components;
@@ -45,6 +47,7 @@ sub sillyness {
$zz = @::legal_severity;
$zz = @::versions;
$zz = @::target_milestone;
+ $zz = %::proddesc;
};
my $serverpush = 0;
@@ -82,7 +85,7 @@ sub SqlifyDate {
}
my $date = str2time($str);
if (!defined $date) {
- PuntTryAgain("The string '<tt>$str</tt>' is not a legal date.");
+ PuntTryAgain("The string '<tt>".html_quote($str)."</tt>' is not a legal date.");
}
return time2str("%Y/%m/%d %H:%M:%S", $date);
}
@@ -107,6 +110,21 @@ sub GetByWordList {
return \@list;
}
+#
+# support for "any/all/nowordssubstr" comparison type ("words as substrings")
+#
+sub GetByWordListSubstr {
+ my ($field, $strs) = (@_);
+ my @list;
+
+ foreach my $word (split(/[\s,]+/, $strs)) {
+ if ($word ne "") {
+ push(@list, "INSTR(LOWER($field), " . lc(SqlQuote($word)) . ")");
+ }
+ }
+
+ return \@list;
+}
sub Error {
@@ -154,7 +172,8 @@ sub GenerateSQL {
if ($c ne "") {
if ($c !~ /^[0-9]*$/) {
return Error("The 'At least ___ votes' field must be a\n" .
- "simple number. You entered \"$c\", which\n" .
+ "simple number. You entered \"" .
+ html_quote($c) . "\", which\n" .
"doesn't cut it.");
}
push(@specialchart, ["votes", "greaterthan", $c - 1]);
@@ -224,15 +243,16 @@ sub GenerateSQL {
push(@supptables, "longdescs $table");
push(@wherepart, "$table.bug_id = bugs.bug_id");
my $ptable = "longdescnames_";
- push(@supptables,
- "LEFT JOIN profiles $ptable ON $table.who = $ptable.userid");
+ push(@supptables, "profiles $ptable");
+ push(@wherepart, "$table.who = $ptable.userid");
push(@clist, "$ptable.login_name", $type, $email);
}
if (@clist) {
push(@specialchart, \@clist);
} else {
return Error("You must specify one or more fields in which to\n" .
- "search for <tt>$email</tt>.\n");
+ "search for <tt>" .
+ html_quote($email) . "</tt>.\n");
}
}
@@ -242,7 +262,8 @@ sub GenerateSQL {
if ($c ne "") {
if ($c !~ /^[0-9]*$/) {
return Error("The 'changed in last ___ days' field must be\n" .
- "a simple number. You entered \"$c\", which\n" .
+ "a simple number. You entered \"" .
+ html_quote($c) . "\", which\n" .
"doesn't cut it.");
}
push(@specialchart, ["changedin",
@@ -294,7 +315,7 @@ sub GenerateSQL {
if (defined $value) {
$value = trim($value);
if ($value ne "") {
- push(@wherepart, "actcheck.newvalue = " .
+ push(@wherepart, "actcheck.added = " .
SqlQuote($value))
}
}
@@ -410,7 +431,8 @@ sub GenerateSQL {
if ($id) {
push(@list, "$table.keywordid = $id");
} else {
- return Error("Unknown keyword named <code>$v</code>.\n" .
+ return Error("Unknown keyword named <code>" .
+ html_quote($v) . "</code>.\n" .
"<P>The legal keyword names are\n" .
"<A HREF=describekeywords.cgi>" .
"listed here</A>.\n");
@@ -491,6 +513,18 @@ sub GenerateSQL {
}
$term = join(" OR ", @list);
},
+ ",anywordssubstr" => sub {
+ $term = join(" OR ", @{GetByWordListSubstr($ff, $v)});
+ },
+ ",allwordssubstr" => sub {
+ $term = join(" AND ", @{GetByWordListSubstr($ff, $v)});
+ },
+ ",nowordssubstr" => sub {
+ my @list = @{GetByWordListSubstr($ff, $v)};
+ if (@list) {
+ $term = "NOT (" . join(" OR ", @list) . ")";
+ }
+ },
",anywords" => sub {
$term = join(" OR ", @{GetByWordList($ff, $v)});
},
@@ -528,7 +562,7 @@ sub GenerateSQL {
push(@supptables, "fielddefs $ftable");
push(@wherepart, "$table.bug_id = bugs.bug_id");
push(@wherepart, "$table.fieldid = $ftable.fieldid");
- $term = "($ftable.name = '$f' AND $table.newvalue = $q)";
+ $term = "($ftable.name = '$f' AND $table.added = $q)";
},
",changedby" => sub {
my $table = "act_$chartid";
@@ -717,7 +751,7 @@ sub GenerateSQL {
my $suppstring = "bugs";
foreach my $str (@supptables) {
if (!$suppseen{$str}) {
- if ($str !~ /^LEFT JOIN/i) {
+ if ($str !~ /^(LEFT|INNER) JOIN/i) {
$suppstring .= ",";
}
$suppstring .= " $str";
@@ -1125,7 +1159,6 @@ my %seen;
my @bugarray;
my %prodhash;
my %statushash;
-my $buggroupset = "";
my %ownerhash;
my $pricol = -1;
@@ -1145,14 +1178,6 @@ my @weekday= qw( Sun Mon Tue Wed Thu Fri Sat );
while (@row = FetchSQLData()) {
my $bug_id = shift @row;
my $g = shift @row; # Bug's group set.
- if ($buggroupset eq "") {
- $buggroupset = $g;
- } elsif ($buggroupset ne $g) {
- $buggroupset = "x"; # We only play games with tweaking the
- # buggroupset if all the bugs have exactly
- # the same group. If they don't, we leave
- # it alone.
- }
if (!defined $seen{$bug_id}) {
$seen{$bug_id} = 1;
$count++;
@@ -1289,7 +1314,7 @@ if ($toolong) {
}
if (Param('usequip')){
- print "<HR><A HREF=newquip.html><I>$quip</I></A></CENTER>\n";
+ print "<HR><A HREF=quips.cgi><I>$quip</I></A></CENTER>\n";
}
print "<HR SIZE=10>";
print "$count bugs found." if $count > 9;
@@ -1397,6 +1422,17 @@ document.write(\" <input type=button value=\\\"Uncheck All\\\" onclick=\\\"SetCh
</TR>";
}
+ print qq{
+<TR><TD ALIGN="RIGHT"><B>CC List:</B></TD>
+<TD COLSPAN=3><INPUT NAME="masscc" SIZE=32 VALUE="">
+<SELECT NAME="ccaction">
+<OPTION VALUE="add">Add these to the CC List
+<OPTION VALUE="remove">Remove these from the CC List
+</SELECT>
+</TD>
+</TR>
+};
+
if (@::legal_keywords) {
print qq{
<TR><TD><B><A HREF="describekeywords.cgi">Keywords</A>:</TD>
@@ -1420,17 +1456,55 @@ document.write(\" <input type=button value=\\\"Uncheck All\\\" onclick=\\\"SetCh
<BR>
<TEXTAREA WRAP=HARD NAME=comment ROWS=5 COLS=80></TEXTAREA><BR>";
-if ($::usergroupset ne '0' && $buggroupset =~ /^\d+$/) {
- SendSQL("select bit, description, (bit & $buggroupset != 0) from groups where bit & $::usergroupset != 0 and isbuggroup != 0 order by bit");
+if($::usergroupset ne '0') {
+ SendSQL("select bit, name, description, isactive ".
+ "from groups where bit & $::usergroupset != 0 ".
+ "and isbuggroup != 0 ".
+ "order by description");
+ # We only print out a header bit for this section if there are any
+ # results.
+ my $groupFound = 0;
+ my $inactiveFound = 0;
while (MoreSQLData()) {
- my ($bit, $description, $ison) = (FetchSQLData());
- my $check0 = !$ison ? " SELECTED" : "";
- my $check1 = $ison ? " SELECTED" : "";
- print "<select name=bit-$bit><option value=0$check0>\n";
- print "People not in the \"$description\" group can see these bugs\n";
- print "<option value=1$check1>\n";
- print "Only people in the \"$description\" group can see these bugs\n";
- print "</select><br>\n";
+ my ($bit, $groupname, $description, $isactive) = (FetchSQLData());
+ if(($prodhash{$groupname}) || (!defined($::proddesc{$groupname}))) {
+ if(!$groupFound) {
+ print "<B>Groupset:</B><BR>\n";
+ print "<TABLE BORDER=1><TR>\n";
+ print "<TH ALIGN=center VALIGN=middle>Don't<br>change<br>this group<br>restriction</TD>\n";
+ print "<TH ALIGN=center VALIGN=middle>Remove<br>bugs<br>from this<br>group</TD>\n";
+ print "<TH ALIGN=center VALIGN=middle>Add<br>bugs<br>to this<br>group</TD>\n";
+ print "<TH ALIGN=left VALIGN=middle>Group name:</TD></TR>\n";
+ $groupFound = 1;
+ }
+ # Modifying this to use radio buttons instead
+ print "<TR>";
+ print "<TD ALIGN=center><input type=radio name=\"bit-$bit\" value=\"-1\" checked></TD>\n";
+ print "<TD ALIGN=center><input type=radio name=\"bit-$bit\" value=\"0\"></TD>\n";
+ if ($isactive) {
+ print "<TD ALIGN=center><input type=radio name=\"bit-$bit\" value=\"1\"></TD>\n";
+ } else {
+ $inactiveFound = 1;
+ print "<TD> </TD>\n";
+ }
+ print "<TD>";
+ if(!$isactive) {
+ print "<I>";
+ }
+ print "$description";
+ if(!$isactive) {
+ print "</I>";
+ }
+ print "</TD></TR>\n";
+ }
+ }
+ # Add in some blank space for legibility
+ if($groupFound) {
+ print "</TABLE>\n";
+ if ($inactiveFound) {
+ print "<FONT SIZE=\"-1\">(Note: Bugs may not be added to inactive groups (<I>italicized</I>), only removed)</FONT><BR>\n";
+ }
+ print "<BR><BR>\n";
}
}
@@ -1508,8 +1582,8 @@ if ($::usergroupset ne '0' && $buggroupset =~ /^\d+$/) {
To make changes to a bunch of bugs at once:
<ol>
<li> Put check boxes next to the bugs you want to change.
-<li> Adjust above form elements. (It's <b>always</b> a good idea to add some
- comment explaining what you're doing.)
+<li> Adjust above form elements. (If the change you are making requires
+ an explanation, include it in the comments box).
<li> Click the below \"Commit\" button.
</ol></font>
<INPUT TYPE=SUBMIT VALUE=Commit>";
@@ -1560,6 +1634,12 @@ if ($count > 0) {
print "</FORM>\n";
}
+# 2001-06-20, myk@mozilla.org, bug 47914:
+# Switch back from the shadow database to the regular database
+# so that PutFooter() can determine the current user even if
+# the "logincookies" table is corrupted in the shadow database.
+SendSQL("USE $::db_name");
+
PutFooter();
if ($serverpush) {
diff --git a/checksetup.pl b/checksetup.pl
index 2953f9b2b..4c3ab81d3 100755
--- a/checksetup.pl
+++ b/checksetup.pl
@@ -97,7 +97,6 @@ use strict;
#
# This are the --LOCAL-- variables defined in 'localconfig'
#
-
# 12/17/00 justdave@syndicomm.com - removed declarations of the localconfig
# variables from this location. We don't want these declared here. They'll
# automatically get declared in the process of reading in localconfig, and
@@ -123,7 +122,7 @@ sub trim {
# Here we check for --MODULES--
#
-print "Checking perl modules ...\n";
+print "\nChecking perl modules ...\n";
unless (eval "require 5.004") {
die "Sorry, you need at least Perl 5.004\n";
}
@@ -186,46 +185,53 @@ sub have_vers {
return $vok;
}
-unless (have_vers("DBI","1.13")) {
- die "Please install the DBI module. You can do this by running (as root)\n\n",
- " perl -MCPAN -eshell\n",
- " install DBI\n";
-}
+# Check versions of dependencies. 0 for version = any version acceptible
-unless (have_vers("Data::Dumper",0)) { # 0 = any version
- die "Please install the Data::Dumper module. You can do this by running (as root)\n\n",
- " perl -MCPAN -eshell\n",
- " install Data::Dumper\n";
-}
+my @missing = ();
+unless (have_vers("DBI","1.13")) { push @missing,"DBI" }
+unless (have_vers("Data::Dumper",0)) { push @missing,"Data::Dumper" }
+unless (have_vers("DBD::mysql","1.2209")) { push @missing,"DBD::mysql" }
+unless (have_vers("Date::Parse",0)) { push @missing,"Date::Parse" }
-unless (have_vers("Mysql",0)) { # 0 = any version
- die "Please install the Mysql database driver. You can do this by running (as root)\n\n",
- " perl -MCPAN -eshell\n",
- " install Msql-Mysql\n\n",
- "Be sure to enable the Mysql emulation!\n";
-}
+# If CGI::Carp was loaded successfully for version checking, it changes the
+# die and warn handlers, we don't want them changed, so we need to stash the
+# original ones and set them back afterwards -- justdave@syndicomm.com
+my $saved_die_handler = $::SIG{__DIE__};
+my $saved_warn_handler = $::SIG{__WARN__};
+unless (have_vers("CGI::Carp",0)) { push @missing,"CGI::Carp" }
+$::SIG{__DIE__} = $saved_die_handler;
+$::SIG{__WARN__} = $saved_warn_handler;
-unless (have_vers("Date::Parse",0)) { # 0 = any version
- die "Please install the Date::Parse module. You can do this by running (as root)\n\n",
- " perl -MCPAN -eshell\n",
- " install Date::Parse\n";
-}
-
-print "The following two modules are optional:\n";
+print "\nThe following Perl modules are optional:\n";
my $charts = 0;
$charts++ if have_vers("GD","1.19");
$charts++ if have_vers("Chart::Base","0.99");
+my $xmlparser = have_vers("XML::Parser",0);
+
+print "\n";
if ($charts != 2) {
print "If you you want to see graphical bug dependency charts, you may install\n",
"the optional libgd and the Perl modules GD-1.19 and Chart::Base-0.99b, e.g. by\n",
"running (as root)\n\n",
- " perl -MCPAN -eshell\n",
- " install LDS/GD-1.19.tar.gz\n",
- " install N/NI/NINJAZ/Chart-0.99b.tar.gz\n\n";
+ " perl -MCPAN -e'install \"LDS/GD-1.19.tar.gz\"'\n",
+ " perl -MCPAN -e'install \"N/NI/NINJAZ/Chart-0.99b.tar.gz\"'\n\n";
+}
+if (!$xmlparser) {
+ print "If you want to use the bug import/export feature to move bugs to or from\n",
+ "other bugzilla installations, you will need to install the XML::Parser module by\n",
+ "running (as root)\n\n",
+ " perl -MCPAN -e'install \"XML::Parser\"'\n\n";
+}
+if (@missing > 0) {
+ print "\n\n";
+ print "You are missing some Perl modules which are required by Bugzilla.\n";
+ print "They can be installed by running (as root) the following:\n";
+ foreach my $module (@missing) {
+ print " perl -MCPAN -e 'install \"$module\"'\n";
+ }
+ print "\n";
+ exit;
}
-
-
-
###########################################################################
@@ -276,6 +282,20 @@ sub LocalVar ($$)
# Set up the defaults for the --LOCAL-- variables below:
#
+LocalVar('create_htaccess', <<'END');
+#
+# If you are using Apache for your web server, Bugzilla can create .htaccess
+# files for you that will instruct Apache not to serve files that shouldn't
+# be accessed from the web (like your local configuration data and non-cgi
+# executable files). For this to work, the directory your Bugzilla
+# installation is in must be within the jurisdiction of a <Directory> block
+# in the httpd.conf file that has 'AllowOverride Limit' in it. If it has
+# 'AllowOverride All' or other options with Limit, that's fine.
+# If this is set to 1, Bugzilla will create these files if they don't exist.
+# If this is set to 0, Bugzilla will not create these files.
+$create_htaccess = 1;
+END
+
LocalVar('webservergroup', '
#
@@ -429,6 +449,7 @@ my $my_db_port = ${*{$main::{'db_port'}}{SCALAR}};
my $my_db_name = ${*{$main::{'db_name'}}{SCALAR}};
my $my_db_user = ${*{$main::{'db_user'}}{SCALAR}};
my $my_db_pass = ${*{$main::{'db_pass'}}{SCALAR}};
+my $my_create_htaccess = ${*{$main::{'create_htaccess'}}{SCALAR}};
my $my_webservergroup = ${*{$main::{'webservergroup'}}{SCALAR}};
my @my_severities = @{*{$main::{'severities'}}{ARRAY}};
my @my_priorities = @{*{$main::{'priorities'}}{ARRAY}};
@@ -446,14 +467,150 @@ my @my_opsys = @{*{$main::{'opsys'}}{ARRAY}};
unless (-d 'data') {
print "Creating data directory ...\n";
- mkdir 'data', 0770;
- if ($my_webservergroup eq "") {
- chmod 01777, 'data';
- }
+ # permissions for non-webservergroup are fixed later on
+ mkdir 'data', 0770;
+ mkdir 'data/mimedump-tmp', 01777;
open FILE, '>>data/comments'; close FILE;
open FILE, '>>data/nomail'; close FILE;
open FILE, '>>data/mail'; close FILE;
- chmod 0666, glob('data/*');
+}
+
+# 2000-12-14 New graphing system requires a directory to put the graphs in
+# This code copied from what happens for the 'data' dir above.
+# If the graphs dir is not present, we assume that they have been using
+# a Bugzilla with the old data format, and so upgrade their data files.
+unless (-d 'graphs') {
+ print "Creating graphs directory...\n";
+ # permissions for non-webservergroup are fixed later on
+ mkdir 'graphs', 0770;
+ # Upgrade data format
+ foreach my $in_file (glob("data/mining/*"))
+ {
+ # Don't try and upgrade image or db files!
+ if (($in_file =~ /\.gif$/i) ||
+ ($in_file =~ /\.png$/i) ||
+ ($in_file =~ /\.db$/i) ||
+ ($in_file =~ /\.orig$/i)) {
+ next;
+ }
+
+ rename("$in_file", "$in_file.orig") or next;
+ open(IN, "$in_file.orig") or next;
+ open(OUT, ">$in_file") or next;
+
+ # Fields in the header
+ my @declared_fields = ();
+
+ # Fields we changed to half way through by mistake
+ # This list comes from an old version of collectstats.pl
+ # This part is only for people who ran later versions of 2.11 (devel)
+ my @intermediate_fields = qw(DATE UNCONFIRMED NEW ASSIGNED REOPENED
+ RESOLVED VERIFIED CLOSED);
+
+ # Fields we actually want (matches the current collectstats.pl)
+ my @out_fields = qw(DATE NEW ASSIGNED REOPENED UNCONFIRMED RESOLVED
+ VERIFIED CLOSED FIXED INVALID WONTFIX LATER REMIND
+ DUPLICATE WORKSFORME MOVED);
+
+ while (<IN>) {
+ if (/^# fields?: (.*)\s$/) {
+ @declared_fields = map uc, (split /\||\r/, $1);
+ print OUT "# fields: ", join('|', @out_fields), "\n";
+ }
+ elsif (/^(\d+\|.*)/) {
+ my @data = split /\||\r/, $1;
+ my %data = ();
+ if (@data == @declared_fields) {
+ # old format
+ for my $i (0 .. $#declared_fields) {
+ $data{$declared_fields[$i]} = $data[$i];
+ }
+ }
+ elsif (@data == @intermediate_fields) {
+ # Must have changed over at this point
+ for my $i (0 .. $#intermediate_fields) {
+ $data{$intermediate_fields[$i]} = $data[$i];
+ }
+ }
+ elsif (@data == @out_fields) {
+ # This line's fine - it has the right number of entries
+ for my $i (0 .. $#out_fields) {
+ $data{$out_fields[$i]} = $data[$i];
+ }
+ }
+ else {
+ print "Oh dear, input line $. of $in_file had " . scalar(@data) . " fields\n";
+ print "This was unexpected. You may want to check your data files.\n";
+ }
+
+ print OUT join('|', map {
+ defined ($data{$_}) ? ($data{$_}) : ""
+ } @out_fields), "\n";
+ }
+ else {
+ print OUT;
+ }
+ }
+
+ close(IN);
+ close(OUT);
+ }
+}
+
+if ($my_create_htaccess) {
+ my $fileperm = 0644;
+ my $dirperm = 01777;
+ if ($my_webservergroup) {
+ $fileperm = 0640;
+ $dirperm = 0770;
+ }
+ if (!-e ".htaccess") {
+ print "Creating .htaccess...\n";
+ open HTACCESS, ">.htaccess";
+ print HTACCESS <<'END';
+# don't allow people to retrieve non-cgi executable files or our private data
+<FilesMatch ^(.*\.pl|localconfig|processmail|syncshadowdb)$>
+ deny from all
+</FilesMatch>
+END
+ close HTACCESS;
+ chmod $fileperm, ".htaccess";
+ }
+ if (!-e "data/.htaccess") {
+ print "Creating data/.htaccess...\n";
+ open HTACCESS, ">data/.htaccess";
+ print HTACCESS <<'END';
+# nothing in this directory is retrievable unless overriden by an .htaccess
+# in a subdirectory
+deny from all
+END
+ close HTACCESS;
+ chmod $fileperm, "data/.htaccess";
+ }
+ if (!-e "data/webdot/.htaccess") {
+ if (!-d "data/webdot") {
+ mkdir "data/webdot", $dirperm;
+ chmod $dirperm, "data/webdot"; # the perms on mkdir don't seem to apply for some reason...
+ }
+ print "Creating data/webdot/.htaccess...\n";
+ open HTACCESS, ">data/webdot/.htaccess";
+ print HTACCESS <<'END';
+# Allow access to nothing in this directory except for .dot files
+# and don't allow access to those to anyone except research.att.com
+# if research.att.com ever changed their IP, or if you use a different
+# webdot server, you'll need to edit this
+<FilesMatch ^[0-9]+\.dot$>
+ Allow from 192.20.225.10
+ Deny from all
+</FilesMatch>
+
+# And no directory listings, either.
+Deny from all
+END
+ close HTACCESS;
+ chmod $fileperm, "data/webdot/.htaccess";
+ }
+
}
@@ -494,6 +651,12 @@ unlink "data/versioncache";
#
# (end changes, 03/14/00 by SML)
#
+# Changes 15/06/01 kiko@async.com.br
+#
+# Fix file permissions for non-webservergroup installations (see
+# http://bugzilla.mozilla.org/show_bug.cgi?id=71555). I'm setting things
+# by default to world readable/executable for all files, and
+# world-writeable (with sticky on) to data and graphs.
#
# These are the files which need to be marked executable
@@ -517,32 +680,48 @@ sub isExecutableFile {
return undef;
}
-if ($my_webservergroup) {
- mkdir 'shadow', 0770 unless -d 'shadow';
- # Funny! getgrname returns the GID if fed with NAME ...
- my $webservergid = getgrnam($my_webservergroup);
- # chmod needs to be called with a valid uid, not 0. $< returns the
- # caller's uid. Maybe there should be a $bugzillauid, and call with that
- # userid.
- chown $<, $webservergid, glob('*');
- my @files = glob('*');
+# fix file (or files - wildcards ok) permissions
+sub fixPerms {
my $file;
+ my @files = glob($_[0]);
+ my $exeperm = 0777 & ~ $_[1];
+ my $normperm = 0666 & ~ $_[1];
foreach $file (@files) {
# do not change permissions on directories here
if (!(-d $file)) {
# check if the file is executable.
if (isExecutableFile($file)) {
- chmod 0750, $file;
+ #printf ("Changing $file to %o",$exeperm);
+ chmod $exeperm, $file;
} else {
- chmod 0640, $file;
+ #print ("Changing $file to %o", $normperm);
+ chmod $normperm, $file;
}
}
}
+}
- # make sure that contrib keeps the permissions it had (don't touch it)
- chmod 0770, 'data', 'shadow', 'graphs';
- chmod 0666, glob('data/*');
- chmod 01777, glob('data/*/'); # directories stay executable
+if ($my_webservergroup) {
+ # Funny! getgrname returns the GID if fed with NAME ...
+ my $webservergid = getgrnam($my_webservergroup);
+ # chown needs to be called with a valid uid, not 0. $< returns the
+ # caller's uid. Maybe there should be a $bugzillauid, and call with that
+ # userid.
+ chown $<, $webservergid, glob('*');
+ if (-e ".htaccess") { chown $<, $webservergid, ".htaccess" } # glob('*') doesn't catch dotfiles
+ if (-e "data/.htaccess") { chown $<, $webservergid, "data/.htaccess" }
+ if (-e "data/webdot/.htaccess") { chown $<, $webservergid, "data/webdot/.htaccess" }
+ fixPerms('*',027);
+ chmod 0644, 'globals.pl';
+ chmod 0644, 'RelationSet.pm';
+ chmod 0771, 'data';
+ chmod 0770, 'graphs';
+} else {
+ # get current gid from $( list
+ my $gid = (split " ", $()[0];
+ chown $<, $gid, glob('*');
+ fixPerms('*',022);
+ chmod 01777, 'data', 'graphs';
}
@@ -559,7 +738,11 @@ if ($my_webservergroup) {
my $db_base = 'mysql';
-use DBI;
+# No need to "use" this here. It should already be loaded from the
+# version-checking routines above, and this file won't even compile if
+# DBI isn't installed so the user gets nasty errors instead of our
+# pretty one saying they need to install it. -- justdave@syndicomm.com
+#use DBI;
# get a handle to the low-level DBD driver
my $drh = DBI->install_driver($db_base)
@@ -575,21 +758,24 @@ if ($my_db_check) {
# removed the $db_name because we don't know it exists yet, and this will fail
# if we request it here and it doesn't. - justdave@syndicomm.com 2000/09/16
my $dsn = "DBI:$db_base:;$my_db_host;$my_db_port";
- my $dbh = DBI->connect($dsn, $my_db_user, $my_db_pass);
+ my $dbh = DBI->connect($dsn, $my_db_user, $my_db_pass)
+ or die "Can't connect to the $db_base database. Is the database " .
+ "installed and\nup and running? Do you have the correct username " .
+ "and password selected in\nlocalconfig?\n\n";
printf("Checking for %15s %-9s ", "MySQL Server", "(v$sql_want)");
my $qh = $dbh->prepare("SELECT VERSION()");
$qh->execute;
my ($sql_vers) = $qh->fetchrow_array;
$qh->finish;
- my $sql_vok = ((vers_cmp($sql_vers,$sql_want) > -1)
- && ($sql_vers ne "3.23.29")); # encrypt() is broken in 3.23.29
- print (($sql_vok ? "ok: " : " "), "found v$sql_vers\n");
- unless ($sql_vok) {
- die "Your MySQL server is either too old or a known broken version.\n",
- " Bugzilla requires version $sql_want or later of MySQL.\n",
- ($sql_vers eq "3.23.29") ? "Version 3.23.29 has a broken encrypt() command. 3.23.30 fixes this.\n" : "",
- " Please visit http://www.mysql.org and download a newer version.\n";
+ # Check what version of MySQL is installed and let the user know
+ # if the version is too old to be used with Bugzilla.
+ if ( vers_cmp($sql_vers,$sql_want) > -1 ) {
+ print "ok: found v$sql_vers\n\n";
+ } else {
+ die "Your MySQL server v$sql_vers is too old./n" .
+ " Bugzilla requires version $sql_want or later of MySQL.\n" .
+ " Please visit http://www.mysql.com/ and download a newer version.\n";
}
my @databases = $dbh->func('_ListDBs');
@@ -602,7 +788,8 @@ The '$my_db_name' database is not accessible. This might have several reasons:
* MySQL is not running.
* MySQL is running, but the rights are not set correct. Go and read the
- README file of Bugzilla and all parts of the MySQL documentation.
+ Bugzilla Guide in the doc directory and all parts of the MySQL
+ documentation.
* There is an subtle problem with Perl, DBI, DBD::mysql and MySQL. Make
sure all settings in 'localconfig' are correct. If all else fails, set
'\$db_check' to zero.\n
@@ -615,7 +802,7 @@ EOF
my $connectstring = "dbi:$db_base:$my_db_name:host=$my_db_host:port=$my_db_port";
my $dbh = DBI->connect($connectstring, $my_db_user, $my_db_pass)
or die "Can't connect to the table '$connectstring'.\n",
- "Have you read Bugzilla's README? Have you read the doc of '$db_base'?\n";
+ "Have you read the Bugzilla Guide in the doc directory? Have you read the doc of '$db_base'?\n";
END { $dbh->disconnect if $dbh }
@@ -654,8 +841,8 @@ $table{bugs_activity} =
who mediumint not null,
bug_when datetime not null,
fieldid mediumint not null,
- oldvalue tinytext,
- newvalue tinytext,
+ added tinytext,
+ removed tinytext,
index (bug_id),
index (bug_when),
@@ -695,7 +882,7 @@ $table{bugs} =
product varchar(64) not null,
rep_platform enum($my_platforms),
reporter mediumint not null,
- version varchar(16) not null,
+ version varchar(64) not null,
component varchar(50) not null,
resolution enum("", "FIXED", "INVALID", "WONTFIX", "LATER", "REMIND", "DUPLICATE", "WORKSFORME", "MOVED") not null,
target_milestone varchar(20) not null default "---",
@@ -707,6 +894,10 @@ $table{bugs} =
. '
lastdiffed datetime not null,
everconfirmed tinyint not null,
+ reporter_accessible tinyint not null default 1,
+ assignee_accessible tinyint not null default 1,
+ qacontact_accessible tinyint not null default 1,
+ cclist_accessible tinyint not null default 1,
index (assigned_to),
index (creation_ts),
@@ -747,6 +938,7 @@ $table{longdescs} =
thetext mediumtext,
index(bug_id),
+ index(who),
index(bug_when)';
@@ -776,6 +968,13 @@ $table{dependencies} =
# User regexp is which email addresses are initially put into this group.
# This is only used when an email account is created; otherwise, profiles
# may be individually tweaked to add them in and out of groups.
+#
+# 2001-04-10 myk@mozilla.org:
+# isactive determines whether or not a group is active. An inactive group
+# cannot have bugs added to it. Deactivation is a much milder form of
+# deleting a group that allows users to continue to work on bugs in the group
+# without enabling them to extend the life of the group by adding bugs to it.
+# http://bugzilla.mozilla.org/show_bug.cgi?id=75482
$table{groups} =
'bit bigint not null,
@@ -783,6 +982,7 @@ $table{groups} =
description text not null,
isbuggroup tinyint not null,
userregexp tinytext not null,
+ isactive tinyint not null default 1,
unique(bit),
unique(name)';
@@ -791,7 +991,7 @@ $table{groups} =
$table{logincookies} =
'cookie mediumint not null auto_increment primary key,
userid mediumint not null,
- cryptpassword varchar(64),
+ cryptpassword varchar(34),
hostname varchar(128),
lastused timestamp,
@@ -813,13 +1013,10 @@ $table{products} =
$table{profiles} =
'userid mediumint not null auto_increment primary key,
login_name varchar(255) not null,
- password varchar(16),
- cryptpassword varchar(64),
+ cryptpassword varchar(34),
realname varchar(255),
groupset bigint not null,
- emailnotification enum("ExcludeSelfChanges", "CConly", "All") not null default "ExcludeSelfChanges",
- disabledtext mediumtext,
- newemailtech tinyint not null default 1,
+ disabledtext mediumtext not null,
mybugslink tinyint not null default 1,
blessgroupset bigint not null default 0,
emailflags mediumtext,
@@ -917,15 +1114,26 @@ $table{duplicates} =
'dupe_of mediumint(9) not null,
dupe mediumint(9) not null primary key';
+# 2001-06-21, myk@mozilla.org, bug 77473:
+# Stores the tokens users receive when they want to change their password
+# or email address. Tokens provide an extra measure of security for these changes.
+$table{tokens} =
+ 'userid mediumint not null ,
+ issuedate datetime not null ,
+ token varchar(16) not null primary key ,
+ tokentype varchar(8) not null ,
+ eventdata tinytext null ,
+
+ index(userid)';
+
+
###########################################################################
# Create tables
###########################################################################
-# The current DBI::mysql tells me to use this:
-#my @tables = map { $_ =~ s/.*\.//; $_ } $dbh->tables();
-# but that doesn't work on a freshly created database, so I still use
-my @tables = $dbh->func('_ListTables');
+# Get a list of the existing tables (if any) in the database
+my @tables = map { $_ =~ s/.*\.//; $_ } $dbh->tables;
#print 'Tables: ', join " ", @tables, "\n";
# add lines here if you add more --LOCAL-- config vars that end up in the enums:
@@ -1069,17 +1277,17 @@ AddFDef("rep_platform", "Platform", 1);
AddFDef("bug_file_loc", "URL", 1);
AddFDef("op_sys", "OS/Version", 1);
AddFDef("bug_status", "Status", 1);
-AddFDef("status_whiteboard", "Status Whiteboard", 1);
-AddFDef("keywords", "Keywords", 1);
-AddFDef("resolution", "Resolution", 1);
+AddFDef("status_whiteboard", "Status Whiteboard", 0);
+AddFDef("keywords", "Keywords", 0);
+AddFDef("resolution", "Resolution", 0);
AddFDef("bug_severity", "Severity", 1);
AddFDef("priority", "Priority", 1);
AddFDef("component", "Component", 1);
AddFDef("assigned_to", "AssignedTo", 1);
AddFDef("reporter", "ReportedBy", 1);
AddFDef("votes", "Votes", 0);
-AddFDef("qa_contact", "QAContact", 0);
-AddFDef("cc", "CC", 0);
+AddFDef("qa_contact", "QAContact", 1);
+AddFDef("cc", "CC", 1);
AddFDef("dependson", "BugsThisDependsOn", 0);
AddFDef("blocked", "OtherBugsDependingOnThis", 0);
AddFDef("attachments.description", "Attachment description", 0);
@@ -1186,7 +1394,6 @@ sub CheckEnumField ($$@)
$dbh->do("ALTER TABLE $table
CHANGE $field
$field $_");
- $::regenerateshadow = 1;
}
}
@@ -1216,7 +1423,7 @@ CheckEnumField('bugs', 'rep_platform', @my_platforms);
# that login, if it doesn't exist already, and make it a member of all groups.
sub bailout { # this is just in case we get interrupted while getting passwd
- system("stty echo"); # re-enable input echoing
+ system("stty","echo"); # re-enable input echoing
exit 1;
}
@@ -1296,15 +1503,17 @@ _End_Of_SQL_
$SIG{QUIT} = \&bailout;
$SIG{TERM} = \&bailout;
- system("stty -echo"); # disable input echoing
+ system("stty","-echo"); # disable input echoing
while( $pass1 ne $pass2 ) {
- while( $pass1 eq "" ) {
+ while( $pass1 eq "" || $pass1 !~ /^[a-zA-Z0-9-_]{3,16}$/ ) {
print "Enter a password for the administrator account: ";
$pass1 = <STDIN>;
chomp $pass1;
if(! $pass1 ) {
print "\n\nIt's just plain stupid to not have a password. Try again!\n";
+ } elsif ( $pass1 !~ /^.{3,16}$/ ) {
+ print "The password must be 3-16 characters in length.";
}
}
print "\nPlease retype the password to verify: ";
@@ -1317,19 +1526,22 @@ _End_Of_SQL_
}
}
- system("stty echo"); # re-enable input echoing
+ # Crypt the administrator's password
+ my $cryptedpassword = Crypt($pass1);
+
+ system("stty","echo"); # re-enable input echoing
$SIG{HUP} = 'DEFAULT'; # and remove our interrupt hooks
$SIG{INT} = 'DEFAULT';
$SIG{QUIT} = 'DEFAULT';
$SIG{TERM} = 'DEFAULT';
$realname = $dbh->quote($realname);
- $pass1 = $dbh->quote($pass1);
+ $cryptedpassword = $dbh->quote($cryptedpassword);
$dbh->do(<<_End_Of_SQL_);
INSERT INTO profiles
- (login_name, realname, password, cryptpassword, groupset, newemailtech)
- VALUES ($login, $realname, $pass1, encrypt($pass1), 0x7fffffffffffffff, 1)
+ (login_name, realname, cryptpassword, groupset)
+ VALUES ($login, $realname, $cryptedpassword, 0x7fffffffffffffff)
_End_Of_SQL_
} else {
$dbh->do(<<_End_Of_SQL_);
@@ -1342,6 +1554,41 @@ _End_Of_SQL_
}
+sub Crypt {
+ # Crypts a password, generating a random salt to do it.
+ # Random salts are generated because the alternative is usually
+ # to use the first two characters of the password itself, and since
+ # the salt appears in plaintext at the beginning of the crypted
+ # password string this has the effect of revealing the first two
+ # characters of the password to anyone who views the crypted version.
+
+ my ($password) = @_;
+
+ # The list of characters that can appear in a salt. Salts and hashes
+ # are both encoded as a sequence of characters from a set containing
+ # 64 characters, each one of which represents 6 bits of the salt/hash.
+ # The encoding is similar to BASE64, the difference being that the
+ # BASE64 plus sign (+) is replaced with a forward slash (/).
+ my @saltchars = (0..9, 'A'..'Z', 'a'..'z', '.', '/');
+
+ # Generate the salt. We use an 8 character (48 bit) salt for maximum
+ # security on systems whose crypt uses MD5. Systems with older
+ # versions of crypt will just use the first two characters of the salt.
+ my $salt = '';
+ for ( my $i=0 ; $i < 8 ; ++$i ) {
+ $salt .= $saltchars[rand(64)];
+ }
+
+ # Crypt the password.
+ my $cryptedpassword = crypt($password, $salt);
+
+ # Return the crypted password.
+ return $cryptedpassword;
+}
+
+
+
+
###########################################################################
# Create initial test product if there are no products present.
###########################################################################
@@ -1393,6 +1640,9 @@ sub ChangeFieldType ($$$)
#print "0: $$ref[0] 1: $$ref[1] 2: $$ref[2] 3: $$ref[3] 4: $$ref[4]\n";
my $oldtype = $ref->[1];
+ if (! $ref->[2]) {
+ $oldtype .= qq{ not null};
+ }
if ($ref->[4]) {
$oldtype .= qq{ default "$ref->[4]"};
}
@@ -1401,7 +1651,8 @@ sub ChangeFieldType ($$$)
print "Updating field type $field in table $table ...\n";
print "old: $oldtype\n";
print "new: $newtype\n";
- $newtype .= " NOT NULL" if $$ref[3];
+# 'not null' should be passed as part of the call to ChangeFieldType()
+# $newtype .= " NOT NULL" if $$ref[3];
$dbh->do("ALTER TABLE $table
CHANGE $field
$field $newtype");
@@ -1467,8 +1718,6 @@ sub TableExists ($)
return $exists;
}
-$::regenerateshadow = 0;
-
# really old fields that were added before checksetup.pl existed
# but aren't in very old bugzilla's (like 2.1)
@@ -1484,14 +1733,6 @@ AddField('components', 'description', 'mediumtext not null');
ChangeFieldType('components', 'program', 'varchar(64)');
-# 1999-05-12 Added a pref to control how much email you get. This needs a new
-# column in the profiles table, so feed the following to mysql:
-
-AddField('profiles', 'emailnotification', 'enum("ExcludeSelfChanges", "CConly",
- "All") not null default "ExcludeSelfChanges"');
-
-
-
# 1999-06-22 Added an entry to the attachments table to record who the
# submitter was. Nothing uses this yet, but it still should be recorded.
@@ -1505,7 +1746,7 @@ AddField('attachments', 'submitter_id', 'mediumint not null');
# populate
# }
#
-# For now I was too lazy, so you should read the README :-)
+# For now I was too lazy, so you should read the documentation :-)
@@ -1541,10 +1782,10 @@ AddField('products', 'votesperuser', 'mediumint not null');
# tinytext is equivalent to varchar(255), which is quite huge, so I change
# them all to varchar(64).
-ChangeFieldType ('bugs', 'product', 'varchar(64)');
+ChangeFieldType ('bugs', 'product', 'varchar(64) not null');
ChangeFieldType ('components', 'program', 'varchar(64)');
ChangeFieldType ('products', 'product', 'varchar(64)');
-ChangeFieldType ('versions', 'program', 'varchar(64)');
+ChangeFieldType ('versions', 'program', 'varchar(64) not null');
# 2000-01-16 Added a "keywords" field to the bugs table, which
# contains a string copy of the entries of the keywords table for this
@@ -1696,10 +1937,10 @@ if (GetFieldDef('bugs', 'long_desc')) {
# him or something. Invent a new profile entry,
# disabled, just to represent him.
$dbh->do("INSERT INTO profiles " .
- "(login_name, password, cryptpassword," .
+ "(login_name, cryptpassword," .
" disabledtext) VALUES (" .
$dbh->quote($name) .
- ", 'okthen', encrypt('okthen'), " .
+ ", " . $dbh->quote(Crypt('okthen')) . ", " .
"'Account created only to maintain database integrity')");
$s2 = $dbh->prepare("SELECT LAST_INSERT_ID()");
$s2->execute();
@@ -1724,8 +1965,6 @@ if (GetFieldDef('bugs', 'long_desc')) {
DropField('bugs', 'long_desc');
$dbh->do("UNLOCK TABLES");
- $::regenerateshadow = 1;
-
}
@@ -1768,14 +2007,14 @@ if (GetFieldDef('bugs_activity', 'field')) {
# record when email notifications were last sent about this bug. Also,
# added a user pref whether a user wants to use the brand new experimental
# stuff.
+# 2001-04-29 jake@acutex.net - The newemailtech field is no longer needed
+# http://bugzilla.mozilla.org/show_bugs.cgi?id=71552
if (!GetFieldDef('bugs', 'lastdiffed')) {
AddField('bugs', 'lastdiffed', 'datetime not null');
$dbh->do('UPDATE bugs SET lastdiffed = now(), delta_ts = delta_ts');
}
-AddField('profiles', 'newemailtech', 'tinyint not null');
-
# 2000-01-22 The "login_name" field in the "profiles" table was not
# declared to be unique. Sure enough, somehow, I got 22 duplicated entries
@@ -1961,8 +2200,8 @@ if (!($sth->fetchrow_arrayref()->[0])) {
# the size of the target_milestone field in the bugs table.
ChangeFieldType('bugs', 'target_milestone',
- 'varchar(20) default "---"');
-ChangeFieldType('milestones', 'value', 'varchar(20)');
+ 'varchar(20) not null default "---"');
+ChangeFieldType('milestones', 'value', 'varchar(20) not null');
# 2000-03-23 Added a defaultmilestone field to the products table, so that
@@ -1999,8 +2238,6 @@ if ( CountIndexes('cc') != 3 ) {
DropIndexes('cc');
$dbh->do("ALTER TABLE cc ADD UNIQUE (bug_id,who)");
$dbh->do("ALTER TABLE cc ADD INDEX (who)");
-
- $::regenerateshadow=1; # cc fields no longer have spaces in them
}
if ( CountIndexes('keywords') != 3 ) {
@@ -2045,93 +2282,6 @@ if (!($sth->fetchrow_arrayref()->[0])) {
$dbh->do("INSERT INTO duplicates VALUES('$dupes{$key}', '$key')");
# BugItsADupeOf Dupe
}
-
- $::regenerateshadow = 1;
-}
-
-# 2000-12-14 New graphing system requires a directory to put the graphs in
-# This code copied from what happens for the 'data' dir above.
-# If the graphs dir is not present, we assume that they have been using
-# a Bugzilla with the old data format, and so upgrade their data files.
-unless (-d 'graphs') {
- print "Creating graphs directory...\n";
- mkdir 'graphs', 0770;
- if ($my_webservergroup eq "") {
- chmod 01777, 'graphs';
- }
-
- # Upgrade data format
- foreach my $in_file (glob("data/mining/*"))
- {
- # Don't try and upgrade image or db files!
- if (($in_file =~ /\.gif$/i) ||
- ($in_file =~ /\.png$/i) ||
- ($in_file =~ /\.db$/i) ||
- ($in_file =~ /\.orig$/i)) {
- next;
- }
-
- rename("$in_file", "$in_file.orig") or next;
- open(IN, "$in_file.orig") or next;
- open(OUT, ">$in_file") or next;
-
- # Fields in the header
- my @declared_fields = ();
-
- # Fields we changed to half way through by mistake
- # This list comes from an old version of collectstats.pl
- # This part is only for people who ran later versions of 2.11 (devel)
- my @intermediate_fields = qw(DATE UNCONFIRMED NEW ASSIGNED REOPENED
- RESOLVED VERIFIED CLOSED);
-
- # Fields we actually want (matches the current collectstats.pl)
- my @out_fields = qw(DATE NEW ASSIGNED REOPENED UNCONFIRMED RESOLVED
- VERIFIED CLOSED FIXED INVALID WONTFIX LATER REMIND
- DUPLICATE WORKSFORME MOVED);
-
- while (<IN>) {
- if (/^# fields?: (.*)\s$/) {
- @declared_fields = map uc, (split /\||\r/, $1);
- print OUT "# fields: ", join('|', @out_fields), "\n";
- }
- elsif (/^(\d+\|.*)/) {
- my @data = split /\||\r/, $1;
- my %data = ();
- if (@data == @declared_fields) {
- # old format
- for my $i (0 .. $#declared_fields) {
- $data{$declared_fields[$i]} = $data[$i];
- }
- }
- elsif (@data == @intermediate_fields) {
- # Must have changed over at this point
- for my $i (0 .. $#intermediate_fields) {
- $data{$intermediate_fields[$i]} = $data[$i];
- }
- }
- elsif (@data == @out_fields) {
- # This line's fine - it has the right number of entries
- for my $i (0 .. $#out_fields) {
- $data{$out_fields[$i]} = $data[$i];
- }
- }
- else {
- print "Oh dear, input line $. of $in_file had " . scalar(@data) . " fields\n";
- print "This was unexpected. You may want to check your data files.\n";
- }
-
- print OUT join('|', map {
- defined ($data{$_}) ? ($data{$_}) : ""
- } @out_fields), "\n";
- }
- else {
- print OUT;
- }
- }
-
- close(IN);
- close(OUT);
- }
}
# 2000-12-18. Added an 'emailflags' field for storing preferences about
@@ -2162,6 +2312,164 @@ unless (-d 'data/duplicates') {
}
}
+#
+# 2001-04-10 myk@mozilla.org:
+# isactive determines whether or not a group is active. An inactive group
+# cannot have bugs added to it. Deactivation is a much milder form of
+# deleting a group that allows users to continue to work on bugs in the group
+# without enabling them to extend the life of the group by adding bugs to it.
+# http://bugzilla.mozilla.org/show_bug.cgi?id=75482
+#
+AddField('groups', 'isactive', 'tinyint not null default 1');
+
+# 2001-04-29 jake@acutex.net - Remove oldemailtech
+# http://bugzilla.mozilla.org/show_bugs.cgi?id=71552
+if (-d 'shadow') {
+ print "Removing shadow directory...\n";
+ unlink glob("shadow/*");
+ unlink glob("shadow/.*");
+ rmdir "shadow";
+}
+DropField("profiles", "emailnotification");
+DropField("profiles", "newemailtech");
+
+# 2001-06-12; myk@mozilla.org; bugs 74032, 77473:
+# Recrypt passwords using Perl &crypt instead of the mysql equivalent
+# and delete plaintext passwords from the database.
+if ( GetFieldDef('profiles', 'password') ) {
+
+ print <<ENDTEXT;
+Your current installation of Bugzilla stores passwords in plaintext
+in the database and uses mysql's encrypt function instead of Perl's
+crypt function to crypt passwords. Passwords are now going to be
+re-crypted with the Perl function, and plaintext passwords will be
+deleted from the database. This could take a while if your
+installation has many users.
+ENDTEXT
+
+ # Re-crypt everyone's password.
+ my $sth = $dbh->prepare("SELECT userid, password FROM profiles");
+ $sth->execute();
+
+ my $i = 1;
+
+ print "Fixing password #1... ";
+ while (my ($userid, $password) = $sth->fetchrow_array()) {
+ my $cryptpassword = $dbh->quote(Crypt($password));
+ $dbh->do("UPDATE profiles SET cryptpassword = $cryptpassword WHERE userid = $userid");
+ ++$i;
+ # Let the user know where we are at every 500 records.
+ print "$i... " if !($i%500);
+ }
+ print "$i... Done.\n";
+
+ # Drop the plaintext password field and resize the cryptpassword field.
+ DropField('profiles', 'password');
+ ChangeFieldType('profiles', 'cryptpassword', 'varchar(34)');
+
+}
+
+#
+# 2001-06-06 justdave@syndicomm.com:
+# There was no index on the 'who' column in the long descriptions table.
+# This caused queries by who posted comments to take a LONG time.
+# http://bugzilla.mozilla.org/show_bug.cgi?id=57350
+if (!defined GetIndexDef('longdescs','who')) {
+ print "Adding index for who column in longdescs table...\n";
+ $dbh->do('ALTER TABLE longdescs ADD INDEX (who)');
+}
+
+# 2001-06-15 kiko@async.com.br - Change bug:version size to avoid
+# truncates re http://bugzilla.mozilla.org/show_bug.cgi?id=9352
+ChangeFieldType('bugs', 'version','varchar(64) not null');
+
+# 2001-07-20 jake@acutex.net - Change bugs_activity to only record changes
+# http://bugzilla.mozilla.org/show_bug.cgi?id=55161
+if (GetFieldDef('bugs_activity', 'oldvalue')) {
+ AddField("bugs_activity", "removed", "tinytext");
+ AddField("bugs_activity", "added", "tinytext");
+
+ # Need to get fieldid's for the fields that have multipule values
+ my @multi = ();
+ foreach my $f ("cc", "dependson", "blocked", "keywords") {
+ my $sth = $dbh->prepare("SELECT fieldid FROM fielddefs WHERE name = '$f'");
+ $sth->execute();
+ my ($fid) = $sth->fetchrow_array();
+ push (@multi, $fid);
+ }
+
+ # Now we need to process the bugs_activity table and reformat the data
+ my $i = 0;
+ print "Fixing activity log ";
+ my $sth = $dbh->prepare("SELECT bug_id, who, bug_when, fieldid,
+ oldvalue, newvalue FROM bugs_activity");
+ $sth->execute;
+ while (my ($bug_id, $who, $bug_when, $fieldid, $oldvalue, $newvalue) = $sth->fetchrow_array()) {
+ # print the iteration count every 500 records so the user knows we didn't die
+ print "$i..." if !($i++ % 500);
+ # Make sure (old|new)value isn't null (to suppress warnings)
+ $oldvalue ||= "";
+ $newvalue ||= "";
+ my ($added, $removed) = "";
+ if (grep ($_ eq $fieldid, @multi)) {
+ $oldvalue =~ s/[\s,]+/ /g;
+ $newvalue =~ s/[\s,]+/ /g;
+ my @old = split(" ", $oldvalue);
+ my @new = split(" ", $newvalue);
+ my (@add, @remove) = ();
+ # Find values that were "added"
+ foreach my $value(@new) {
+ if (! grep ($_ eq $value, @old)) {
+ push (@add, $value);
+ }
+ }
+ # Find values that were removed
+ foreach my $value(@old) {
+ if (! grep ($_ eq $value, @new)) {
+ push (@remove, $value);
+ }
+ }
+ $added = join (", ", @add);
+ $removed = join (", ", @remove);
+ # If we can't determine what changed, put a ? in both fields
+ unless ($added || $removed) {
+ $added = "?";
+ $removed = "?";
+ }
+ # If the origianl field (old|new)value was full, then this
+ # could be incomplete data.
+ if (length($oldvalue) == 255 || length($newvalue) == 255) {
+ $added = "? $added";
+ $removed = "? $removed";
+ }
+ } else {
+ $removed = $oldvalue;
+ $added = $newvalue;
+ }
+ $added = $dbh->quote($added);
+ $removed = $dbh->quote($removed);
+ $dbh->do("UPDATE bugs_activity SET removed = $removed, added = $added
+ WHERE bug_id = $bug_id AND who = $who
+ AND bug_when = '$bug_when' AND fieldid = $fieldid");
+ }
+ print ". Done.\n";
+ DropField("bugs_activity", "oldvalue");
+ DropField("bugs_activity", "newvalue");
+}
+
+# 2001-07-24 jake@acutex.net - disabledtext was being handled inconsitantly
+# http://bugzilla.mozilla.org/show_bug.cgi?id=90933
+ChangeFieldType("profiles", "disabledtext", "mediumtext not null");
+
+# 2001-07-26 myk@mozilla.org bug39816:
+# Add fields to the bugs table that record whether or not the reporter,
+# assignee, QA contact, and users on the cc: list can see bugs even when
+# they are not members of groups to which the bugs are restricted.
+AddField("bugs", "reporter_accessible", "tinyint not null default 1");
+AddField("bugs", "assignee_accessible", "tinyint not null default 1");
+AddField("bugs", "qacontact_accessible", "tinyint not null default 1");
+AddField("bugs", "cclist_accessible", "tinyint not null default 1");
+
# If you had to change the --TABLE-- definition in any way, then add your
# differential change code *** A B O V E *** this comment.
#
@@ -2173,10 +2481,6 @@ unless (-d 'data/duplicates') {
#
#
# Final checks...
-if ($::regenerateshadow) {
- print "Now regenerating the shadow database for all bugs.\n";
- system("./processmail", "regenerate");
-}
unlink "data/versioncache";
print "Reminder: Bugzilla now requires version 8.7 or later of sendmail.\n";
diff --git a/colchange.cgi b/colchange.cgi
index f825228ea..f3521b7ad 100755
--- a/colchange.cgi
+++ b/colchange.cgi
@@ -23,6 +23,10 @@
use diagnostics;
use strict;
+sub sillyness { # shut up "used only once" warnings
+ my $zz = @::legal_keywords;
+}
+
require "CGI.pl";
print "Content-type: text/html\n";
diff --git a/collectstats.pl b/collectstats.pl
index e36a3ca90..4e69ab9b5 100755
--- a/collectstats.pl
+++ b/collectstats.pl
@@ -131,8 +131,8 @@ sub calculate_dupes {
# Save % count here in a date-named file
# so we can read it back in to do changed counters
# First, delete it if it exists, so we don't add to the contents of an old file
- if (<data/duplicates/dupes$today*>) {
- system("rm -f data/duplicates/dupes$today*");
+ if (my @files = <data/duplicates/dupes$today*>) {
+ unlink @files;
}
dbmopen(%count, "data/duplicates/dupes$today", 0644) || die "Can't open DBM dupes file: $!";
diff --git a/contrib/CVS/Entries b/contrib/CVS/Entries
index 7ae00ac72..8936418e7 100644
--- a/contrib/CVS/Entries
+++ b/contrib/CVS/Entries
@@ -1,12 +1,12 @@
-/BugzillaEmail.pm/1.1/Wed Mar 15 22:29:44 2000//
-/README/1.4/Sun Apr 22 18:13:40 2001//
-/README.Mailif/1.3/Wed Mar 15 23:39:03 2000//
-/bug_email.pl/1.8/Wed Sep 6 06:01:10 2000//
-/bugmail_help.html/1.1/Tue Mar 7 17:36:48 2000//
-/bugzilla.procmailrc/1.1/Wed Mar 15 23:39:09 2000//
-/bugzilla_email_append.pl/1.2/Wed Mar 15 23:39:11 2000//
-/cvs-update.sh/1.1/Wed Apr 18 18:01:28 2001//
-/gnats2bz.pl/1.5/Thu Nov 18 17:29:58 1999//
-/mysqld-watcher.pl/1.1/Sun Apr 22 17:48:12 2001//
-/yp_nomail.sh/1.1/Tue Sep 12 23:50:31 2000//
+/BugzillaEmail.pm/1.1/Wed Mar 15 22:29:44 2000//TBUGZILLA-2_14
+/README/1.4/Sun Apr 22 18:13:40 2001//TBUGZILLA-2_14
+/README.Mailif/1.3/Wed Mar 15 23:39:03 2000//TBUGZILLA-2_14
+/bug_email.pl/1.9/Fri May 25 12:48:47 2001//TBUGZILLA-2_14
+/bugmail_help.html/1.1/Tue Mar 7 17:36:48 2000//TBUGZILLA-2_14
+/bugzilla.procmailrc/1.1/Wed Mar 15 23:39:09 2000//TBUGZILLA-2_14
+/bugzilla_email_append.pl/1.2/Wed Mar 15 23:39:11 2000//TBUGZILLA-2_14
+/cvs-update.sh/1.1/Wed Apr 18 18:01:28 2001//TBUGZILLA-2_14
+/gnats2bz.pl/1.5/Thu Nov 18 17:29:58 1999//TBUGZILLA-2_14
+/mysqld-watcher.pl/1.2/Fri Jun 1 08:34:45 2001//TBUGZILLA-2_14
+/yp_nomail.sh/1.1/Tue Sep 12 23:50:31 2000//TBUGZILLA-2_14
D
diff --git a/contrib/CVS/Tag b/contrib/CVS/Tag
new file mode 100644
index 000000000..c10f87310
--- /dev/null
+++ b/contrib/CVS/Tag
@@ -0,0 +1 @@
+NBUGZILLA-2_14
diff --git a/contrib/bug_email.pl b/contrib/bug_email.pl
index e7d039919..da0f11308 100755
--- a/contrib/bug_email.pl
+++ b/contrib/bug_email.pl
@@ -37,7 +37,7 @@
#
# You need to work with bug_email.pl the MIME::Parser installed.
#
-# $Id: bug_email.pl,v 1.8 2000/09/06 06:01:10 dave%intrec.com Exp $
+# $Id: bug_email.pl,v 1.9 2001/05/25 12:48:47 jake%acutex.net Exp $
###############################################################
# 02/12/2000 (SML)
@@ -837,19 +837,11 @@ if (! CheckPermissions("CreateBugs", $SenderShort ) ) {
}
# Set QA
-SendSQL("select initialqacontact from components where program=" .
- SqlQuote($Control{'product'}) .
- " and value=" . SqlQuote($Control{'component'}));
-my $qacontact = FetchOneColumn();
-if (defined $qacontact && $qacontact !~ /^\s*$/) {
- #$Control{'qa_contact'} = DBNameToIdAndCheck($qacontact, 1);
- $Control{'qa_contact'} = DBname_to_id($qacontact);
-
- if ( ! $Control{'qa_contact'} ) {
- BugMailError( 0, "Could not resolve qa_contact !\n" );
- }
-
- #push(@bug_fields, "qa_contact");
+if (Param("useqacontact")) {
+ SendSQL("select initialqacontact from components where program=" .
+ SqlQuote($Control{'product'}) .
+ " and value=" . SqlQuote($Control{'component'}));
+ $Control{'qacontact'} = FetchOneColumn();
}
# Set Assigned - assigned_to depends on the product, cause initialowner
@@ -936,21 +928,18 @@ $Control{'component'} = $Component;
#
# Check assigned_to
-# if no assigned_to was given, generate it from the product-DB
-my $forceAssignedOK = 0;
-if ( (! defined($Control{'assigned_to'}) )
- || $Control{'assigned_to'} =~ /^\s*$/ ) {
+# If a value was given in the e-mail, convert it to an ID,
+# otherwise, retrieve it from the database.
+if ( defined($Control{'assigned_to'})
+ && $Control{'assigned_to'} !~ /^\s*$/ ) {
+ $Control{'assigned_to'} = DBname_to_id($Control{'assigned_to'});
+} else {
SendSQL("select initialowner from components where program=" .
SqlQuote($Control{'product'}) .
" and value=" . SqlQuote($Control{'component'}));
$Control{'assigned_to'} = FetchOneColumn();
- $forceAssignedOK = 1;
}
-
-# Recode Names
-$Control{'assigned_to'} = DBname_to_id($Control{'assigned_to'}, $forceAssignedOK);
-
if ( $Control{'assigned_to'} == 0 ) {
my $Text = "Could not resolve key \@assigned_to !\n" .
"If you do NOT send a value for assigned_to, the bug will be assigned to\n" .
diff --git a/contrib/mysqld-watcher.pl b/contrib/mysqld-watcher.pl
index d867c62c8..29e322771 100755
--- a/contrib/mysqld-watcher.pl
+++ b/contrib/mysqld-watcher.pl
@@ -68,19 +68,6 @@ while ( <STDIN> ) {
}
}
-# if we found anything, kill the database thread and send mail about it
-#
-if ($LONGEST[6] != 0) {
-
- system ("/usr/bonsaitools/bin/mysqladmin", "kill", $LONGEST[1]);
-
- # fire off an email telling the maintainer that we had to kill a thread
- #
- sendEmail($mail_from, Param("maintainer"),
- "long running MySQL thread killed",
- join(" ", @LONGEST) . "\n");
-}
-
# send an email message
#
# should perhaps be moved to somewhere more global for use in bugzilla as a
@@ -100,3 +87,16 @@ sub sendEmail($$$$) {
close(MTA);
}
+
+# if we found anything, kill the database thread and send mail about it
+#
+if ($LONGEST[6] != 0) {
+
+ system ("/usr/bonsaitools/bin/mysqladmin", "kill", $LONGEST[1]);
+
+ # fire off an email telling the maintainer that we had to kill a thread
+ #
+ sendEmail($mail_from, Param("maintainer"),
+ "long running MySQL thread killed",
+ join(" ", @LONGEST) . "\n");
+}
diff --git a/createaccount.cgi b/createaccount.cgi
index c2358d6fd..5b9bfb9f6 100755
--- a/createaccount.cgi
+++ b/createaccount.cgi
@@ -57,13 +57,18 @@ my $realname = $::FORM{'realname'};
if (defined $login) {
CheckEmailSyntax($login);
if (DBname_to_id($login) != 0) {
- PutHeader("Account exists");
- print "A bugzilla account for the name <tt>$login</tt> already\n";
- print "exists. If you have forgotten the password for it, then\n";
- print "<a href=query.cgi?GoAheadAndLogIn>click here</a> and use\n";
- print "the <b>E-mail me a password</b> button.\n";
+ PutHeader("Account Exists");
+ print qq|
+ <form method="get" action="token.cgi">
+ <input type="hidden" name="a" value="reqpw">
+ <input type="hidden" name="loginname" value="$login">
+ A Bugzilla account for <tt>$login</tt> already exists. If you
+ are the account holder and have forgotten your password,
+ <input type="submit" value="submit a request to change it">.
+ </form>
+ |;
PutFooter();
- exit;
+ exit;
}
PutHeader("Account created");
my $password = InsertNewUser($login, $realname);
diff --git a/defparams.pl b/defparams.pl
index d13efe89f..46a00b78f 100644
--- a/defparams.pl
+++ b/defparams.pl
@@ -145,11 +145,6 @@ DefParam("preferlists",
"b",
1);
-DefParam("prettyasciimail",
- "If this is on, Bugzilla will send email reports formatted (assuming 76 character monospace font display). If this is off, email reports are sent using the old 'one-item-per-line' format.",
- "b",
- 0);
-
DefParam("capitalizelists",
"If this is on, Bugzilla will capitalize list entries, checkboxes, and radio buttons. If this is off, Bugzilla will leave these items untouched.",
"b",
@@ -374,56 +369,33 @@ To use the wonders of Bugzilla, you can use the following:
});
-
-DefParam("changedmail",
+DefParam("newchangedmail",
q{The email that gets sent to people when a bug changes. Within this
-text, %to% gets replaced by the assigned-to and reported-by people,
-separated by a comma (with duplication removed, if they're the same
-person). %cc% gets replaced by the list of people on the CC list,
-separated by commas. %bugid% gets replaced by the bug number.
-%diffs% gets replaced by the diff text from the old version to the new
-version of this bug. %neworchanged% is "New: " if this mail is
-reporting a new bug or empty if changes were made
-to an existing one. %summary% gets replaced by the summary of this
-bug. %<i>anythingelse</i>% gets replaced by the definition of that
-parameter (as defined on this page).},
+text, %to% gets replaced with the e-mail address of the person recieving
+the mail. %bugid% gets replaced by the bug number. %diffs% gets
+replaced with what's changed. %neworchanged% is "New:" if this mail is
+reporting a new bug or empty if changes were made to an existing one.
+%summary% gets replaced by the summary of this bug. %reasonsheader%
+is replaced by an abbreviated list of reasons why the user is getting the email,
+suitable for use in an email header (such as X-Bugzilla-Reason).
+%reasonsbody% is replaced by text that explains why the user is getting the email
+in more user friendly text than %reasonsheader%.
+%<i>anythingelse</i>% gets replaced by the definition of
+that parameter (as defined on this
+page).},
"l",
"From: bugzilla-daemon
To: %to%
-Cc: %cc%
Subject: [Bug %bugid%] %neworchanged%%summary%
+X-Bugzilla-Reason: %reasonsheader%
%urlbase%show_bug.cgi?id=%bugid%
-%diffs%");
-
-DefParam("newemailtech",
-q{The way that email diffs are constructed by Bugzilla. You can revert to
-the old technology by turning this off, but this is not advised, as the old
-email tech will probably disappear in the next version of Bugzilla. Some
-features (watches, server side mail filtering) depend on newemailtech being
-set to on.},
- "b",
- 1);
+%diffs%
-DefParam("newemailtechdefault",
-q{Make "newemailtech" the default for all new accounts created. This will
-not change any existing accounts nor will it remove a users ability to go
-back to the oldmail system (requires "newemailtech" to be on as well).},
- "b",
- 1);
-
-DefParam("newchangedmail",
-q{The same as 'changedmail', but used for the newemailtech stuff.},
- "l",
-"From: bugzilla-daemon
-To: %to%
-Cc: %cc%
-Subject: [Bug %bugid%] %neworchanged%%summary%
-%urlbase%show_bug.cgi?id=%bugid%
-%diffs%");
+%reasonsbody%");
@@ -567,14 +539,14 @@ DefParam("expectbigqueries",
0);
DefParam("emailregexp",
- 'This defines the regexp to use for legal email addresses. The default tries to match fully qualified email addresses. Another popular value to put here is <tt>^[^@, ]*$</tt>, which means "local usernames, no @ allowed.',
+ 'This defines the regexp to use for legal email addresses. The default tries to match fully qualified email addresses. Another popular value to put here is <tt>^[^@]*$</tt>, which means "local usernames, no @ allowed.',
"t",
- q:^[^@, ]*@[^@, ]*\\.[^@, ]*$:);
+ q:^[^@]*@[^@]*\\.[^@]*$:);
DefParam("emailregexpdesc",
"This describes in english words what kinds of legal addresses are allowed by the <tt>emailregexp</tt> param.",
"l",
- "A legal address must contain exactly one '\@', and at least one '.' after the \@, and may not contain any commas or spaces.");
+ "A legal address must contain exactly one '\@', and at least one '.' after the \@.");
DefParam("emailsuffix",
"This is a string to append to any email addresses when actually sending mail to that address. It is useful if you have changed the <tt>emailregexp</tt> param to only allow local usernames, but you want the mail to be delivered to username\@my.local.hostname.",
@@ -583,17 +555,19 @@ DefParam("emailsuffix",
DefParam("voteremovedmail",
-q{This is a mail message to send to anyone who gets a vote removed from a bug for any reason. %to% gets replaced by a comma-separated list of people who used to be voting for this bug. %bugid% gets replaced by the bug number. %reason% gets replaced by a short reason describing why the vote was removed. %count% is how many votes got removed.%<i>anythingelse</i>% gets replaced by the definition of that parameter (as defined on this page).},
+q{This is a mail message to send to anyone who gets a vote removed from a bug for any reason. %to% gets replaced by the person who used to be voting for this bug. %bugid% gets replaced by the bug number. %reason% gets replaced by a short reason describing why the vote(s) were removed. %votesremoved%, %votesold% and %votesnew% is the number of votes removed, before and after respectively. %votesremovedtext%, %votesoldtext% and %votesnewtext% are these as sentences, eg "You had 2 votes on this bug." %count% is also supported for backwards compatibility. %<i>anythingelse</i>% gets replaced by the definition of that parameter (as defined on this page).},
"l",
"From: bugzilla-daemon
To: %to%
-Subject: [Bug %bugid%] Your vote has been removed from this bug
+Subject: [Bug %bugid%] Some or all of your votes have been removed.
-You used to have a vote on bug %bugid%, but it has been removed.
+Some or all of your votes have been removed from bug %bugid%.
-Reason: %reason%
+%votesoldtext%
-Votes removed: %count%
+%votesnewtext%
+
+Reason: %reason%
%urlbase%show_bug.cgi?id=%bugid%
");
diff --git a/describecomponents.cgi b/describecomponents.cgi
index 4353af2fc..95f5ba316 100755
--- a/describecomponents.cgi
+++ b/describecomponents.cgi
@@ -30,10 +30,50 @@ require "CGI.pl";
ConnectToDatabase();
GetVersionTable();
+quietly_check_login();
+
+######################################################################
+# Begin Data/Security Validation
+######################################################################
+
+# If this installation uses bug groups to restrict access to products,
+# only show the user products that don't have their own bug group or
+# those whose bug group the user is a member of. Otherwise, if this
+# installation doesn't use bug groups, show the user all legal products.
+my @products;
+if ( Param("usebuggroups") ) {
+ @products = grep( !GroupExists($_) || UserInGroup($_) , @::legal_product );
+} else {
+ @products = @::legal_product;
+}
+
+if ( defined $::FORM{'product'} ) {
+ # Make sure the user specified a valid product name. Note that
+ # if the user specifies a valid product name but is not authorized
+ # to access that product, they will receive a different error message
+ # which could enable people guessing product names to determine
+ # whether or not certain products exist in Bugzilla, even if they
+ # cannot get any other information about that product.
+ grep( $::FORM{'product'} eq $_ , @::legal_product )
+ || DisplayError("The product name is invalid.")
+ && exit;
+
+ # Make sure the user is authorized to access this product.
+ if ( Param("usebuggroups") && GroupExists($::FORM{'product'}) ) {
+ UserInGroup($::FORM{'product'})
+ || DisplayError("You are not authorized to access that product.")
+ && exit;
+ }
+}
+
+######################################################################
+# End Data/Security Validation
+######################################################################
+
print "Content-type: text/html\n\n";
my $product = $::FORM{'product'};
-if (!defined $product || lsearch(\@::legal_product, $product) < 0) {
+if (!defined $product || lsearch(\@products, $product) < 0) {
PutHeader("Bugzilla component description");
print "
@@ -42,7 +82,7 @@ Please specify the product whose components you want described.
<P>
Product: <SELECT NAME=product>
";
- print make_options(\@::legal_product);
+ print make_options(\@products);
print "
</SELECT>
<P>
diff --git a/docs/CVS/Entries b/docs/CVS/Entries
index 5393850d5..2863ba15e 100644
--- a/docs/CVS/Entries
+++ b/docs/CVS/Entries
@@ -1,5 +1,6 @@
-/README.docs/1.2/Thu Mar 8 06:35:25 2001//
+/README.docs/1.3/Wed Aug 22 03:44:14 2001//TBUGZILLA-2_14
+/rel_notes.txt/1.5/Wed Aug 29 19:39:01 2001//TBUGZILLA-2_14
D/html////
+D/images////
D/sgml////
D/txt////
-/rel_notes.txt/1.4/Fri Apr 27 19:37:35 2001//
diff --git a/docs/CVS/Tag b/docs/CVS/Tag
new file mode 100644
index 000000000..c10f87310
--- /dev/null
+++ b/docs/CVS/Tag
@@ -0,0 +1 @@
+NBUGZILLA-2_14
diff --git a/docs/README.docs b/docs/README.docs
index 6b5d6ed61..4ccd7044d 100644
--- a/docs/README.docs
+++ b/docs/README.docs
@@ -38,12 +38,74 @@ point, but for now they are convenient and don't hurt anything.
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:
+==========
+
+Trying to set up an SGML/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
+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.
+
+The following text is taken nearly verbatim from
+http://bugzilla.mozilla.org/show_bug.cgi?id=95970, where I gave
+these instructions to someone who wanted the greater manageability
+maintaining a document in Docbook brings:
+
+This is just off the top of my head, but here goes. Note some of these may
+NOT be necessary, but I don't think they hurt anything by being installed.
+
+rpms:
+
+openjade
+jadetex
+docbook-dtd41-sgml
+docbook-style-dsssl
+docbook-dtd31-sgml
+docbook-style-dsssl-doc
+xemacs
+psgml
+sgml-tools
+sgml-common
+
+Set up environment:
+
+in your .bashrc add this line (after installing above RPMS):
+export SGML_CATALOG_FILES=/etc/sgml/catalog
+
+Download "ldp.dsl" from the Resources page on linuxdoc.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
+locations of your docbook catalog files. I created a directory,
+/usr/share/sgml/docbook/ldp, and put the ldp.dsl file there. I then edited
+ldp.dsl and changed two lines near the top:
+<!ENTITY docbook.dsl SYSTEM "../dsssl-stylesheets-1.62/html/docbook.dsl" CDATA
+dsssl>
+...and...
+<!ENTITY docbook.dsl SYSTEM "../dsssl-stylesheets-1.62/print/docbook.dsl" CDATA
+dsssl>
+
+Note the difference is the top one points to the HTML docbook stylesheet,
+and the next one points to the PRINT docbook stylesheet.
+
+ You know, this sure looks awful involved. Anyway, once you have this in
+place, add to your .bashrc:
+export LDP_HOME=/usr/share/sgml/docbook/ldp
+
+ I suggest xemacs for editing your SGML/XML Docbook documents. The darn
+thing just works, and generally includes PSGML mode by default. You can
+download psgml at http://www.sourceforge.net/projects/psgml.
+
+==========
NOTES:
+==========
Here are the commands I use to maintain this documentation.
- You MUST have DocBook 4.1 set up correctly in order for this to work,
- but there's only a single REMARK tag that's incompatible with 3.1.
- Maybe I'll downgrade to DocBook 3.1 to make your life easier...
+ You MUST have DocBook 4.1 set up correctly in order for this to work.
Substitute your own path to "ldp.dsl" for "$LDP_HOME".
diff --git a/docs/html/Bugzilla-Guide.html b/docs/html/Bugzilla-Guide.html
index 0712a5146..ca916f417 100644
--- a/docs/html/Bugzilla-Guide.html
+++ b/docs/html/Bugzilla-Guide.html
@@ -4,7 +4,7 @@
>The Bugzilla Guide</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><META
NAME="KEYWORD"
CONTENT="Bugzilla"><META
@@ -47,7 +47,7 @@ NAME="AEN2"
><H3
CLASS="AUTHOR"
><A
-NAME="AEN5"
+NAME="AEN27"
>Matthew P. Barnson</A
></H3
><DIV
@@ -59,6 +59,21 @@ CLASS="ADDRESS"
>barnboy@trilobyte.net</P
></DIV
></DIV
+><SPAN
+CLASS="COLLAB"
+><SPAN
+CLASS="COLLABNAME"
+>Zach Lipton</SPAN
+><DIV
+CLASS="AFFILIATION"
+><DIV
+CLASS="ADDRESS"
+><P
+CLASS="ADDRESS"
+>zach AT zachlipton DOT com</P
+></DIV
+></DIV
+><BR></SPAN
><DIV
CLASS="REVHISTORY"
><TABLE
@@ -88,8 +103,8 @@ ALIGN="LEFT"
><TD
ALIGN="LEFT"
COLSPAN="3"
->Converted the README, FAQ, and DATABASE information into SGML
- docbook format.</TD
+>Converted the README, FAQ, and DATABASE information into
+ SGML docbook format.</TD
></TR
><TR
><TD
@@ -106,12 +121,13 @@ ALIGN="LEFT"
><TD
ALIGN="LEFT"
COLSPAN="3"
->Took way too long to revise this for 2.12 release.
- Updated FAQ to use qandaset tags instead of literallayout,
- cleaned up administration section, added User Guide section,
- miscellaneous FAQ updates and third-party integration information.
- From this point on all new tags are lowercase in preparation for the
- 2.13 release of the Guide in XML format instead of SGML.</TD
+>Took way too long to revise this for 2.12 release. Updated
+ FAQ to use qandaset tags instead of literallayout, cleaned
+ up administration section, added User Guide section,
+ miscellaneous FAQ updates and third-party integration
+ information. From this point on all new tags are lowercase
+ in preparation for the 2.13 release of the Guide in XML
+ format instead of SGML.</TD
></TR
><TR
><TD
@@ -128,12 +144,38 @@ ALIGN="LEFT"
><TD
ALIGN="LEFT"
COLSPAN="3"
->Things fixed this release: Elaborated on queryhelp interface, added FAQ regarding
- moving bugs from one keyword to another, clarified possible problems with the Landfill
- tutorial, fixed a boatload of typos and unclear sentence structures. Incorporated the
- README into the UNIX installation section, and changed the README to indicate the deprecated
- status. Things I know need work: Used "simplelist" a lot, where I should have used
- "procedure" to tag things. Need to lowercase all tags to be XML compliant.</TD
+>Things fixed this release: Elaborated on queryhelp
+ interface, added FAQ regarding moving bugs from one keyword
+ to another, clarified possible problems with the Landfill
+ tutorial, fixed a boatload of typos and unclear sentence
+ structures. Incorporated the README into the UNIX
+ installation section, and changed the README to indicate the
+ deprecated status. Things I know need work: Used
+ "simplelist" a lot, where I should have used "procedure" to
+ tag things. Need to lowercase all tags to be XML compliant.</TD
+></TR
+><TR
+><TD
+ALIGN="LEFT"
+>Revision 2.14.0</TD
+><TD
+ALIGN="LEFT"
+>07 August 2001</TD
+><TD
+ALIGN="LEFT"
+>Revised by: MPB</TD
+></TR
+><TR
+><TD
+ALIGN="LEFT"
+COLSPAN="3"
+>Attempted to integrate relevant portions of the UNIX and
+ Windows installation instructions, moved some data from FAQ
+ to Install, removed references to README from text, added
+ Mac OS X install instructions, fixed a bunch
+ of tpyos (Mark Harig), linked text that referenced other
+ parts of the Guide, and nuked the old MySQL permissions
+ section.</TD
></TR
></TABLE
></DIV
@@ -141,12 +183,32 @@ COLSPAN="3"
><DIV
CLASS="ABSTRACT"
><A
-NAME="AEN12"
+NAME="AEN39"
></A
><P
></P
><P
->This is the documentation for Bugzilla, the Mozilla bug-tracking system.</P
+> This is the documentation for Bugzilla, the Mozilla
+ bug-tracking system.
+ </P
+><P
+> Bugzilla is an enterprise-class set of software utilities
+ that, when used together, power issue-tracking for hundreds of
+ organizations around the world, tracking millions of bugs.
+ While it is easy to use and quite flexible, it is very
+ difficult for a novice to install and maintain. Although we
+ have provided step-by-step directions, Bugzilla is not always
+ easy to get working. Please be sure the person responsible
+ for installing and maintaining this software is a qualified
+ professional on operating system upon which you install
+ Bugzilla.
+ </P
+><P
+> THIS DOCUMENTATION IS MAINTAINED IN DOCBOOK 4.1 SGML FORMAT.
+ IF YOU WISH TO MAKE CORRECTIONS, PLEASE MAKE THEM IN PLAIN
+ TEXT OR SGML DIFFS AGAINST THE SOURCE. I CANNOT ACCEPT
+ ADDITIONS TO THE GUIDE WRITTEN IN HTML!
+ </P
><P
></P
></DIV
@@ -215,203 +277,362 @@ HREF="#CONVENTIONS"
></DD
><DT
>2. <A
-HREF="#INSTALLATION"
->Installing Bugzilla</A
+HREF="#USING"
+>Using Bugzilla</A
></DT
><DD
><DL
><DT
>2.1. <A
-HREF="#README.UNIX"
->UNIX Installation</A
+HREF="#WHATIS"
+>What is Bugzilla?</A
+></DT
+><DT
+>2.2. <A
+HREF="#WHY"
+>Why Should We Use Bugzilla?</A
+></DT
+><DT
+>2.3. <A
+HREF="#HOW"
+>How do I use Bugzilla?</A
+></DT
+><DD
+><DL
+><DT
+>2.3.1. <A
+HREF="#MYACCOUNT"
+>Create a Bugzilla Account</A
+></DT
+><DT
+>2.3.2. <A
+HREF="#QUERY"
+>The Bugzilla Query Page</A
+></DT
+><DT
+>2.3.3. <A
+HREF="#BUGREPORTS"
+>Creating and Managing Bug Reports</A
+></DT
+><DD
+><DL
+><DT
+>2.3.3.1. <A
+HREF="#BUG_WRITING"
+>Writing a Great Bug Report</A
+></DT
+><DT
+>2.3.3.2. <A
+HREF="#BUG_MANAGE"
+>Managing your Bug Reports</A
+></DT
+></DL
+></DD
+></DL
+></DD
+><DT
+>2.4. <A
+HREF="#INIT4ME"
+>Where can I find my user preferences?</A
+></DT
+><DD
+><DL
+><DT
+>2.4.1. <A
+HREF="#ACCOUNTSETTINGS"
+>Account Settings</A
+></DT
+><DT
+>2.4.2. <A
+HREF="#EMAILSETTINGS"
+>Email Settings</A
+></DT
+><DD
+><DL
+><DT
+>2.4.2.1. <A
+HREF="#NOTIFICATION"
+>Email Notification</A
+></DT
+><DT
+>2.4.2.2. <A
+HREF="#NEWEMAILTECH"
+>New Email Technology</A
+></DT
+><DT
+>2.4.2.3. <A
+HREF="#WATCHSETTINGS"
+>"Watching" Users</A
+></DT
+></DL
+></DD
+><DT
+>2.4.3. <A
+HREF="#FOOTERSETTINGS"
+>Page Footer</A
+></DT
+><DT
+>2.4.4. <A
+HREF="#PERMISSIONSETTINGS"
+>Permissions</A
+></DT
+></DL
+></DD
+><DT
+>2.5. <A
+HREF="#USINGBZ-CONC"
+>Using Bugzilla-Conclusion</A
+></DT
+></DL
+></DD
+><DT
+>3. <A
+HREF="#INSTALLATION"
+>Installation</A
></DT
><DD
><DL
><DT
->2.1.1. <A
-HREF="#AEN190"
+>3.1. <A
+HREF="#ERRATA"
>ERRATA</A
></DT
><DT
->2.1.2. <A
-HREF="#AEN204"
+>3.2. <A
+HREF="#STEPBYSTEP"
>Step-by-step Install</A
></DT
><DD
><DL
><DT
->2.1.2.1. <A
-HREF="#AEN206"
+>3.2.1. <A
+HREF="#AEN509"
>Introduction</A
></DT
><DT
->2.1.2.2. <A
-HREF="#AEN211"
+>3.2.2. <A
+HREF="#AEN515"
>Installing the Prerequisites</A
></DT
><DT
->2.1.2.3. <A
-HREF="#AEN242"
+>3.2.3. <A
+HREF="#INSTALL-MYSQL"
>Installing MySQL Database</A
></DT
><DT
->2.1.2.4. <A
-HREF="#AEN248"
+>3.2.4. <A
+HREF="#INSTALL-PERL"
>Perl (5.004 or greater)</A
></DT
><DT
->2.1.2.5. <A
-HREF="#AEN259"
+>3.2.5. <A
+HREF="#AEN602"
>DBI Perl Module</A
></DT
><DT
->2.1.2.6. <A
-HREF="#AEN296"
+>3.2.6. <A
+HREF="#AEN640"
>Data::Dumper Perl Module</A
></DT
><DT
->2.1.2.7. <A
-HREF="#AEN300"
+>3.2.7. <A
+HREF="#AEN645"
>MySQL related Perl Module Collection</A
></DT
><DT
->2.1.2.8. <A
-HREF="#AEN309"
+>3.2.8. <A
+HREF="#AEN654"
>TimeDate Perl Module Collection</A
></DT
><DT
->2.1.2.9. <A
-HREF="#AEN312"
+>3.2.9. <A
+HREF="#AEN658"
>GD Perl Module (1.8.3)</A
></DT
><DT
->2.1.2.10. <A
-HREF="#AEN318"
+>3.2.10. <A
+HREF="#AEN667"
>Chart::Base Perl Module (0.99c)</A
></DT
><DT
->2.1.2.11. <A
-HREF="#AEN321"
+>3.2.11. <A
+HREF="#AEN671"
>DB_File Perl Module</A
></DT
><DT
->2.1.2.12. <A
-HREF="#AEN324"
+>3.2.12. <A
+HREF="#AEN674"
>HTTP Server</A
></DT
><DT
->2.1.2.13. <A
-HREF="#AEN334"
+>3.2.13. <A
+HREF="#AEN692"
>Installing the Bugzilla Files</A
></DT
><DT
->2.1.2.14. <A
-HREF="#AEN343"
+>3.2.14. <A
+HREF="#AEN721"
>Setting Up the MySQL Database</A
></DT
><DT
->2.1.2.15. <A
-HREF="#AEN379"
->Tweaking "localconfig"</A
+>3.2.15. <A
+HREF="#AEN768"
+>Tweaking <TT
+CLASS="FILENAME"
+>localconfig</TT
+></A
></DT
><DT
->2.1.2.16. <A
-HREF="#AEN401"
->Setting Up Maintainers Manuall (Optional)</A
+>3.2.16. <A
+HREF="#AEN806"
+>Setting Up Maintainers Manually (Optional)</A
></DT
><DT
->2.1.2.17. <A
-HREF="#AEN410"
+>3.2.17. <A
+HREF="#AEN817"
>The Whining Cron (Optional)</A
></DT
><DT
->2.1.2.18. <A
-HREF="#AEN417"
+>3.2.18. <A
+HREF="#AEN827"
>Bug Graphs (Optional)</A
></DT
><DT
->2.1.2.19. <A
-HREF="#AEN429"
+>3.2.19. <A
+HREF="#AEN839"
>Securing MySQL</A
></DT
+></DL
+></DD
+><DT
+>3.3. <A
+HREF="#OSX"
+>Mac OS X Installation Notes</A
+></DT
+><DT
+>3.4. <A
+HREF="#BSDINSTALL"
+>BSD Installation Notes</A
+></DT
><DT
->2.1.2.20. <A
-HREF="#AEN495"
+>3.5. <A
+HREF="#GENINSTALL"
>Installation General Notes</A
></DT
-></DL
-></DD
+><DD
+><DL
+><DT
+>3.5.1. <A
+HREF="#AEN941"
+>Modifying Your Running System</A
+></DT
+><DT
+>3.5.2. <A
+HREF="#AEN948"
+>Upgrading From Previous Versions</A
+></DT
+><DT
+>3.5.3. <A
+HREF="#HTACCESS"
+><TT
+CLASS="FILENAME"
+>.htaccess</TT
+> files and security</A
+></DT
+><DT
+>3.5.4. <A
+HREF="#MOD_THROTTLE"
+><TT
+CLASS="FILENAME"
+>mod_throttle</TT
+> and Security</A
+></DT
+><DT
+>3.5.5. <A
+HREF="#CONTENT_TYPE"
+>Preventing untrusted Bugzilla content from executing malicious Javascript code</A
+></DT
+><DT
+>3.5.6. <A
+HREF="#UNIXHISTORY"
+>UNIX Installation Instructions History</A
+></DT
></DL
></DD
><DT
->2.2. <A
-HREF="#README.WINDOWS"
->Win32 (Win98+/NT/2K) Installation</A
+>3.6. <A
+HREF="#WIN32"
+>Win32 Installation Notes</A
></DT
><DD
><DL
><DT
->2.2.1. <A
-HREF="#NTVERIFIED"
+>3.6.1. <A
+HREF="#WININSTALL"
>Win32 Installation: Step-by-step</A
></DT
><DT
->2.2.2. <A
+>3.6.2. <A
HREF="#ADDLWINTIPS"
>Additional Windows Tips</A
></DT
+><DT
+>3.6.3. <A
+HREF="#BZLDAP"
+>Bugzilla LDAP Integration</A
+></DT
></DL
></DD
></DL
></DD
><DT
->3. <A
+>4. <A
HREF="#ADMINISTRATION"
>Administering Bugzilla</A
></DT
><DD
><DL
><DT
->3.1. <A
+>4.1. <A
HREF="#POSTINSTALL-CHECK"
>Post-Installation Checklist</A
></DT
><DT
->3.2. <A
+>4.2. <A
HREF="#USERADMIN"
>User Administration</A
></DT
><DD
><DL
><DT
->3.2.1. <A
+>4.2.1. <A
HREF="#DEFAULTUSER"
>Creating the Default User</A
></DT
><DT
->3.2.2. <A
+>4.2.2. <A
HREF="#MANAGEUSERS"
>Managing Other Users</A
></DT
><DD
><DL
><DT
->3.2.2.1. <A
+>4.2.2.1. <A
HREF="#LOGIN"
>Logging In</A
></DT
><DT
->3.2.2.2. <A
+>4.2.2.2. <A
HREF="#CREATENEWUSERS"
>Creating new users</A
></DT
><DT
->3.2.2.3. <A
+>4.2.2.3. <A
HREF="#DISABLEUSERS"
>Disabling Users</A
></DT
><DT
->3.2.2.4. <A
+>4.2.2.4. <A
HREF="#MODIFYUSERS"
>Modifying Users</A
></DT
@@ -420,233 +641,129 @@ HREF="#MODIFYUSERS"
></DL
></DD
><DT
->3.3. <A
+>4.3. <A
HREF="#PROGRAMADMIN"
->Product, Component, Milestone, and Version Administration</A
+>Product, Component, Milestone, and Version
+ Administration</A
></DT
><DD
><DL
><DT
->3.3.1. <A
+>4.3.1. <A
HREF="#PRODUCTS"
>Products</A
></DT
><DT
->3.3.2. <A
+>4.3.2. <A
HREF="#COMPONENTS"
>Components</A
></DT
><DT
->3.3.3. <A
+>4.3.3. <A
HREF="#VERSIONS"
>Versions</A
></DT
><DT
->3.3.4. <A
+>4.3.4. <A
HREF="#MILESTONES"
>Milestones</A
></DT
><DT
->3.3.5. <A
+>4.3.5. <A
HREF="#VOTING"
>Voting</A
></DT
><DT
->3.3.6. <A
+>4.3.6. <A
HREF="#GROUPS"
>Groups and Group Security</A
></DT
></DL
></DD
><DT
->3.4. <A
+>4.4. <A
HREF="#SECURITY"
>Bugzilla Security</A
></DT
></DL
></DD
><DT
->4. <A
-HREF="#USING"
->Using Bugzilla</A
+>5. <A
+HREF="#INTEGRATION"
+>Integrating Bugzilla with Third-Party Tools</A
></DT
><DD
><DL
><DT
->4.1. <A
-HREF="#WHATIS"
->What is Bugzilla?</A
+>5.1. <A
+HREF="#BONSAI"
+>Bonsai</A
></DT
><DT
->4.2. <A
-HREF="#WHY"
->Why Should We Use Bugzilla?</A
+>5.2. <A
+HREF="#CVS"
+>CVS</A
></DT
><DT
->4.3. <A
-HREF="#HOW"
->How do I use Bugzilla?</A
+>5.3. <A
+HREF="#SCM"
+>Perforce SCM</A
></DT
-><DD
-><DL
><DT
->4.3.1. <A
-HREF="#MYACCOUNT"
->Create a Bugzilla Account</A
+>5.4. <A
+HREF="#TINDERBOX"
+>Tinderbox/Tinderbox2</A
></DT
+></DL
+></DD
><DT
->4.3.2. <A
-HREF="#QUERY"
->The Bugzilla Query Page</A
+>6. <A
+HREF="#FUTURE"
+>The Future of Bugzilla</A
></DT
><DT
->4.3.3. <A
-HREF="#BUGREPORTS"
->Creating and Managing Bug Reports</A
+>7. <A
+HREF="#VARIANTS"
+>Bugzilla Variants and Competitors</A
></DT
><DD
><DL
><DT
->4.3.3.1. <A
-HREF="#BUG_WRITING"
->Writing a Great Bug Report</A
-></DT
-><DT
->4.3.3.2. <A
-HREF="#BUG_MANAGE"
->Managing your Bug Reports</A
-></DT
-></DL
-></DD
-></DL
-></DD
-><DT
->4.4. <A
-HREF="#INIT4ME"
->What's in it for me?</A
+>7.1. <A
+HREF="#RHBUGZILLA"
+>Red Hat Bugzilla</A
></DT
-><DD
-><DL
><DT
->4.4.1. <A
-HREF="#ACCOUNTSETTINGS"
->Account Settings</A
+>7.2. <A
+HREF="#VARIANT_FENRIS"
+>Loki Bugzilla (Fenris)</A
></DT
><DT
->4.4.2. <A
-HREF="#EMAILSETTINGS"
->Email Settings</A
+>7.3. <A
+HREF="#VARIANT_ISSUEZILLA"
+>Issuezilla</A
></DT
-><DD
-><DL
><DT
->4.4.2.1. <A
-HREF="#NOTIFICATION"
->Email Notification</A
+>7.4. <A
+HREF="#VARIANT_SCARAB"
+>Scarab</A
></DT
><DT
->4.4.2.2. <A
-HREF="#NEWEMAILTECH"
->New Email Technology</A
+>7.5. <A
+HREF="#VARIANT_PERFORCE"
+>Perforce SCM</A
></DT
><DT
->4.4.2.3. <A
-HREF="#WATCHSETTINGS"
->"Watching" Users</A
+>7.6. <A
+HREF="#VARIANT_SOURCEFORGE"
+>SourceForge</A
></DT
></DL
></DD
><DT
->4.4.3. <A
-HREF="#FOOTERSETTINGS"
->Page Footer</A
-></DT
-><DT
->4.4.4. <A
-HREF="#PERMISSIONSETTINGS"
->Permissions</A
-></DT
-></DL
-></DD
-><DT
->4.5. <A
-HREF="#USINGBZ-CONC"
->Using Bugzilla-Conclusion</A
-></DT
-></DL
-></DD
-><DT
->5. <A
-HREF="#INTEGRATION"
->Integrating Bugzilla with Third-Party Tools</A
-></DT
-><DD
-><DL
-><DT
->5.1. <A
-HREF="#BONSAI"
->Bonsai</A
-></DT
-><DT
->5.2. <A
-HREF="#CVS"
->CVS</A
-></DT
-><DT
->5.3. <A
-HREF="#SCM"
->Perforce SCM</A
-></DT
-><DT
->5.4. <A
-HREF="#TINDERBOX"
->Tinderbox</A
-></DT
-></DL
-></DD
-><DT
->6. <A
-HREF="#FUTURE"
->The Future of Bugzilla</A
-></DT
-><DD
-><DL
-><DT
->6.1. <A
-HREF="#SPAMLITE"
->Reducing Spam</A
-></DT
-><DT
->6.2. <A
-HREF="#SEARCHING"
->Better Searching</A
-></DT
-><DT
->6.3. <A
-HREF="#TRACKINGBUGS"
->Description Flags and Tracking Bugs</A
-></DT
-><DT
->6.4. <A
-HREF="#BUGPROBS"
->Bug Issues</A
-></DT
-><DT
->6.5. <A
-HREF="#DBASEINTEGRITY"
->Database Integrity</A
-></DT
-><DT
->6.6. <A
-HREF="#BZ30"
->Bugzilla 3.0</A
-></DT
-></DL
-></DD
-><DT
->A. <A
-HREF="#FAQ"
->The Bugzilla FAQ</A
+>A. <A
+HREF="#FAQ"
+>The Bugzilla FAQ</A
></DT
><DT
>B. <A
@@ -670,29 +787,28 @@ HREF="#DBSCHEMA"
HREF="#DBDOC"
>MySQL Bugzilla Database Introduction</A
></DT
+><DD
+><DL
><DT
->C.3. <A
-HREF="#GRANTTABLES"
->MySQL Permissions & Grant Tables</A
+>C.2.1. <A
+HREF="#AEN2331"
+>Bugzilla Database Basics</A
></DT
+><DD
+><DL
><DT
->C.4. <A
-HREF="#CLEANUPWORK"
->Cleaning up after mucking with Bugzilla</A
+>C.2.1.1. <A
+HREF="#AEN2360"
+>Bugzilla Database Tables</A
></DT
></DL
></DD
+></DL
+></DD
><DT
->7. <A
-HREF="#VARIANTS"
->Bugzilla Variants</A
-></DT
-><DD
-><DL
-><DT
->7.1. <A
-HREF="#RHBUGZILLA"
->Red Hat Bugzilla</A
+>C.3. <A
+HREF="#GRANTTABLES"
+>MySQL Permissions & Grant Tables</A
></DT
></DL
></DD
@@ -705,19 +821,32 @@ HREF="#PATCHES"
><DL
><DT
>D.1. <A
+HREF="#REWRITE"
+>Apache <TT
+CLASS="FILENAME"
+>mod_rewrite</TT
+> magic</A
+></DT
+><DT
+>D.2. <A
HREF="#SETPERL"
>The setperl.csh Utility</A
></DT
><DT
->D.2. <A
+>D.3. <A
HREF="#CMDLINE"
>Command-line Bugzilla Queries</A
></DT
><DT
->D.3. <A
+>D.4. <A
HREF="#QUICKSEARCH"
>The Quicksearch Utility</A
></DT
+><DT
+>D.5. <A
+HREF="#BZHACKING"
+>Hacking Bugzilla</A
+></DT
></DL
></DD
><DT
@@ -806,64 +935,83 @@ CLASS="LOT"
></DT
><DT
>2-1. <A
-HREF="#AEN646"
->Removing encrypt() for Windows NT installations</A
+HREF="#AEN307"
+>Some Famous Software Versions</A
+></DT
+><DT
+>2-2. <A
+HREF="#AEN317"
+>Mozilla's Bugzilla Components</A
></DT
><DT
>3-1. <A
-HREF="#AEN838"
->Creating some Components</A
+HREF="#AEN708"
+>Setting up bonsaitools symlink</A
></DT
><DT
>3-2. <A
-HREF="#AEN867"
->Common Use of Versions</A
+HREF="#AEN799"
+>Running checksetup.pl as the web user</A
></DT
><DT
>3-3. <A
-HREF="#AEN871"
->A Different Use of Versions</A
+HREF="#AEN1038"
+>Installing ActivePerl ppd Modules on Microsoft Windows</A
></DT
><DT
>3-4. <A
-HREF="#AEN899"
+HREF="#AEN1224"
+>Removing encrypt() for Windows NT Bugzilla version
+ 2.12 or earlier</A
+></DT
+><DT
+>4-1. <A
+HREF="#AEN1461"
+>Creating some Components</A
+></DT
+><DT
+>4-2. <A
+HREF="#AEN1490"
+>Common Use of Versions</A
+></DT
+><DT
+>4-3. <A
+HREF="#AEN1494"
+>A Different Use of Versions</A
+></DT
+><DT
+>4-4. <A
+HREF="#AEN1522"
>Using SortKey with Target Milestone</A
></DT
><DT
->3-5. <A
-HREF="#AEN937"
+>4-5. <A
+HREF="#AEN1558"
>When to Use Group Security</A
></DT
><DT
->3-6. <A
-HREF="#AEN954"
+>4-6. <A
+HREF="#AEN1575"
>Creating a New Group</A
></DT
><DT
->4-1. <A
-HREF="#AEN1095"
->Some Famous Software Versions</A
-></DT
-><DT
->4-2. <A
-HREF="#AEN1105"
->Mozilla Webtools Components</A
+>4-7. <A
+HREF="#AEN1592"
+>Bugzilla Groups</A
></DT
><DT
>D-1. <A
-HREF="#AEN1963"
+HREF="#AEN2439"
>Using Setperl to set your perl path</A
></DT
><DT
>1. <A
-HREF="#AEN2145"
+HREF="#AEN2685"
>A Sample Product</A
></DT
></DL
></DIV
->] >
-
-<DIV
+><DIV
CLASS="CHAPTER"
><HR><H1
><A
@@ -879,53 +1027,60 @@ NAME="ABOUTTHISGUIDE"
>1.1. Purpose and Scope of this Guide</A
></H1
><P
-> This document was started on September 17, 2000
- by Matthew P. Barnson after a great deal of procrastination updating the Bugzilla FAQ,
- which I left untouched for nearly half a year.
- After numerous complete rewrites and reformatting, it is the document you see today.
+> This document was started on September 17, 2000 by Matthew P.
+ Barnson after a great deal of procrastination updating the
+ Bugzilla FAQ, which I left untouched for nearly half a year.
+ After numerous complete rewrites and reformatting, it is the
+ document you see today.
</P
><P
-> Despite the lack of updates, Bugzilla is simply the best piece of bug-tracking software
- the world has ever seen. This document is intended to be the comprehensive guide to
- the installation, administration, maintenance, and use of the Bugzilla bug-tracking system.
+> Bugzilla is simply the best piece of bug-tracking software the
+ world has ever seen. This document is intended to be the
+ comprehensive guide to the installation, administration,
+ maintenance, and use of the Bugzilla bug-tracking system.
</P
><P
-> This release of the Bugzilla Guide is the <EM
->2.11</EM
-> release.
- It is so named that it may match the current version of Bugzilla.
- The numbering tradition stems from that used for many free software projects,
+> This release of the Bugzilla Guide is the
+ <EM
+>2.14</EM
+> release. It is so named that it
+ may match the current version of Bugzilla. The numbering
+ tradition stems from that used for many free software projects,
in which <EM
>even-numbered</EM
-> point releases (1.2, 1.14, etc.)
- are considered "stable releases", intended for public consumption; on the other
- hand, <EM
+> point releases (1.2,
+ 1.14, etc.) are considered "stable releases", intended for
+ public consumption; on the other hand,
+ <EM
>odd-numbered</EM
-> point releases (1.3, 2.09, etc.)
- are considered unstable <EM
+> point releases (1.3, 2.09,
+ etc.) are considered unstable <EM
>development</EM
-> releases intended
- for advanced users, systems administrators, developers, and those who enjoy
- a lot of pain.
+>
+ releases intended for advanced users, systems administrators,
+ developers, and those who enjoy a lot of pain.
</P
><P
-> Newer revisions of the Bugzilla Guide will follow the numbering conventions of
- the main-tree Bugzilla releases, available at
+> Newer revisions of the Bugzilla Guide follow the numbering
+ conventions of the main-tree Bugzilla releases, available at
<A
-HREF="http://www.mozilla.org/bugs/source.html"
+HREF="http://www.mozilla.org/projects/bugzilla"
TARGET="_top"
->Mozilla.org</A
->, with
- the exception that intermediate releases will have a minor revision number
- following a period. For instance, if the current version of Bugzilla is 4.2,
- the current "stable" version of the Bugzilla guide, in, say, it's fifth revision,
- would be numbered "4.2.5". Got it? Good.
+>http://www.mozilla.org/projects/bugzilla</A
+>. Intermediate releases will have
+ a minor revision number following a period. The current version
+ of Bugzilla, as of this writing (August 10, 2001) is 2.14; if
+ something were seriously wrong with that edition of the Guide,
+ subsequent releases would receive an additional dotted-decimal
+ digit to indicate the update (2.14.1, 2.14.2, etc.).
+ Got it? Good.
</P
><P
-> I wrote this in response to the enormous demand for decent Bugzilla documentation.
- I have incorporated instructions from the Bugzilla README, Frequently Asked Questions,
- Database Schema Document, and various mailing lists to create it.
- Chances are, there are glaring errors in this documentation; please contact
+> I wrote this in response to the enormous demand for decent
+ Bugzilla documentation. I have incorporated instructions from
+ the Bugzilla README, Frequently Asked Questions, Database Schema
+ Document, and various mailing lists to create it. Chances are,
+ there are glaring errors in this documentation; please contact
<TT
CLASS="EMAIL"
><<A
@@ -944,7 +1099,7 @@ NAME="COPYRIGHT"
>1.2. Copyright Information</A
></H1
><A
-NAME="AEN57"
+NAME="AEN70"
></A
><TABLE
BORDER="0"
@@ -961,11 +1116,13 @@ VALIGN="TOP"
WIDTH="80%"
VALIGN="TOP"
><P
-> Permission is granted to copy, distribute and/or modify this document under thei
- terms of the GNU Free Documentation License, Version 1.1 or any later version published
- by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and
- with no Back-Cover Texts. A copy of the license is included in the section entitled
- "GNU Free Documentation LIcense".
+> Permission is granted to copy, distribute and/or modify this
+ document under the terms of the GNU Free Documentation
+ License, Version 1.1 or any later version published by the
+ Free Software Foundation; with no Invariant Sections, no
+ Front-Cover Texts, and with no Back-Cover Texts. A copy of
+ the license is included in the section entitled "GNU Free
+ Documentation LIcense".
</P
></TD
><TD
@@ -988,14 +1145,9 @@ WIDTH="10%"
></TR
></TABLE
><P
-> If you have any questions regarding this document, its' copyright, or publishing this
- document in non-electronic form, please contact <TT
-CLASS="EMAIL"
-><<A
-HREF="mailto:barnboy@trilobyte.net"
->barnboy@trilobyte.net</A
->></TT
->
+> If you have any questions regarding this document, its
+ copyright, or publishing this document in non-electronic form,
+ please contact Matthew P. Barnson.
</P
></DIV
><DIV
@@ -1010,34 +1162,44 @@ NAME="DISCLAIMER"
> No liability for the contents of this document can be accepted.
Use the concepts, examples, and other content at your own risk.
As this is a new edition of this document, there may be errors
- and inaccuracies that may damage your system. Use of this document
- may cause your girlfriend to leave you, your cats to pee on your
- furniture and clothing, your computer to cease functioning, your
- boss to fire you, and global thermonuclear war. Proceed with caution.
+ and inaccuracies that may damage your system. Use of this
+ document may cause your girlfriend to leave you, your cats to
+ pee on your furniture and clothing, your computer to cease
+ functioning, your boss to fire you, and global thermonuclear
+ war. Proceed with caution.
</P
><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.
- In particular, I like to put down Microsoft(tm). Live with it.
+> 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".
- Use GNU/Linux. Love it. Bathe with it. It is life and happiness.
- I endorse it wholeheartedly and encourage you to do the same.
+> Naming of particular products or brands should not be seen as
+ endorsements, with the exception of the term "GNU/Linux". I
+ 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. Heaven knows
- it's saved my bacon time after time; if you implement any suggestion in
- this Guide, implement this one!
+> You are strongly recommended to make a backup of your system
+ before installing Bugzilla and at regular intervals thereafter.
+ Heaven knows it's saved my bacon time after time; if you
+ implement any suggestion in this Guide, implement this one!
</P
><P
-> Bugzilla has not undergone a complete security review.
- Security holes probably exist in the code.
- Great care should be taken both in the installation and usage of this software.
- Carefully consider the implications of installing other network services with Bugzilla.
+> 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 insure
+ your security needs are met.
</P
></DIV
><DIV
@@ -1049,7 +1211,10 @@ NAME="NEWVERSIONS"
>1.4. New Versions</A
></H1
><P
-> This is the initial release of the Bugzilla Guide.
+> This is the 2.14 version of The Bugzilla Guide. 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:
@@ -1081,7 +1246,8 @@ TARGET="_top"
> <A
HREF="http://www.linuxdoc.org/"
TARGET="_top"
->The Linux Documentation Project</A
+>The Linux
+ Documentation Project</A
>
</P
></LI
@@ -1090,13 +1256,11 @@ TARGET="_top"
</P
><P
> The latest version of this document can be checked out via CVS.
- Please follow the instructions available at
- <A
+ Please follow the instructions available at <A
HREF="http://www.mozilla.org/cvs.html"
TARGET="_top"
>the Mozilla CVS page</A
->,
- and check out the mozilla/webtools/bugzilla/docs/ branch.
+>, and check out the mozilla/webtools/bugzilla/docs/ branch.
</P
></DIV
><DIV
@@ -1108,10 +1272,10 @@ NAME="CREDITS"
>1.5. Credits</A
></H1
><P
-> The people listed below have made enormous contributions to the creation
- of this Guide, through their dedicated hacking efforts,
- numerous e-mail and IRC support sessions,
- and overall excellent contribution to the Bugzilla community:
+> The people listed below have made enormous contributions to the
+ creation of this Guide, through their dedicated hacking efforts,
+ numerous e-mail and IRC support sessions, and overall excellent
+ contribution to the Bugzilla community:
</P
><P
> <A
@@ -1119,44 +1283,43 @@ HREF="mailto://terry@mozilla.org"
TARGET="_top"
>Terry Weissman</A
>
- for initially converting Bugzilla from BugSplat!
- and writing the README upon which this documentation is largely based.
+ 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
+>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
+> 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
+> 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
+> 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.
+> netscape.public.mozilla.webtools</A
+> newsgroup. Without your discussions, insight, suggestions, and patches, this could never have happened.
</P
></DIV
><DIV
@@ -1168,15 +1331,12 @@ NAME="CONTRIBUTORS"
>1.6. Contributors</A
></H1
><P
-> Thanks go to these people for significant contributions
- to this documentation (in no particular order):
+> Thanks go to these people for significant contributions to this
+ documentation (in no particular order):
</P
><P
-> Zach Lipton (significant textual contributions),
- Andrew Pearson,
- Spencer Smith,
- Eric Hanson,
- Kevin Brannen,
+> Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen, Ron
+ Teitelbaum, Jacob Steenhagen, Joe Robins
</P
></DIV
><DIV
@@ -1188,15 +1348,16 @@ NAME="FEEDBACK"
>1.7. Feedback</A
></H1
><P
-> I welcome feedback on this document. Without your submissions and input,
- this Guide cannot continue to exist. Please mail additions, comments, criticisms, etc.
- to <TT
+> I welcome feedback on this document. Without your submissions
+ and input, this Guide cannot continue to exist. Please mail
+ additions, comments, criticisms, etc. to
+ <TT
CLASS="EMAIL"
><<A
HREF="mailto:barnboy@trilobyte.net"
>barnboy@trilobyte.net</A
>></TT
->. Please send flames to
+>. Please send flames to
<TT
CLASS="EMAIL"
><<A
@@ -1215,17 +1376,18 @@ NAME="TRANSLATIONS"
>1.8. Translations</A
></H1
><P
-> The Bugzilla Guide needs translators!
- Please volunteer your translation into the language of your choice.
- If you will translate this Guide, please notify the members of the mozilla-webtools mailing list at
+> The Bugzilla Guide needs translators! Please volunteer your
+ translation into the language of your choice. If you will
+ translate this Guide, please notify the members of the
+ mozilla-webtools mailing list at
<TT
CLASS="EMAIL"
><<A
HREF="mailto:mozilla-webtools@mozilla.org"
>mozilla-webtools@mozilla.org</A
>></TT
->. Since The Bugzilla Guide is also hosted on the
- Linux Documentation Project, you would also do well to notify
+>, and arrange with
+ Matt Barnson to check it into CVS.
</P
></DIV
><DIV
@@ -1242,7 +1404,7 @@ NAME="CONVENTIONS"
><DIV
CLASS="INFORMALTABLE"
><A
-NAME="AEN117"
+NAME="AEN129"
></A
><P
></P
@@ -1276,18 +1438,20 @@ CLASS="CAUTION"
></P
><TABLE
CLASS="CAUTION"
-BORDER="1"
WIDTH="100%"
+BORDER="0"
><TR
><TD
+WIDTH="25"
ALIGN="CENTER"
-><B
->Caution</B
-></TD
-></TR
-><TR
+VALIGN="TOP"
+><IMG
+SRC="../images/caution.gif"
+HSPACE="5"
+ALT="Caution"></TD
><TD
ALIGN="LEFT"
+VALIGN="TOP"
><P
>Warnings.</P
></TD
@@ -1306,13 +1470,29 @@ ALIGN="LEFT"
VALIGN="TOP"
><DIV
CLASS="TIP"
-><BLOCKQUOTE
+><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
-><B
->Tip: </B
>Hint.</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
></TD
></TR
@@ -1326,13 +1506,29 @@ ALIGN="LEFT"
VALIGN="TOP"
><DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><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
-><B
->Note: </B
>Note.</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
></TD
></TR
@@ -1350,18 +1546,20 @@ CLASS="WARNING"
></P
><TABLE
CLASS="WARNING"
-BORDER="1"
WIDTH="100%"
+BORDER="0"
><TR
><TD
+WIDTH="25"
ALIGN="CENTER"
-><B
->Warning</B
-></TD
-></TR
-><TR
+VALIGN="TOP"
+><IMG
+SRC="../images/warning.gif"
+HSPACE="5"
+ALT="Warning"></TD
><TD
ALIGN="LEFT"
+VALIGN="TOP"
><P
>Warning.</P
></TD
@@ -1500,6 +1698,8 @@ BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
+><FONT
+COLOR="#000000"
><PRE
CLASS="PROGRAMLISTING"
><TT
@@ -1509,6 +1709,7 @@ CLASS="SGMLTAG"
CLASS="SGMLTAG"
></para></TT
></PRE
+></FONT
></TD
></TR
></TABLE
@@ -1525,1250 +1726,1419 @@ CLASS="SGMLTAG"
CLASS="CHAPTER"
><HR><H1
><A
-NAME="INSTALLATION"
->Chapter 2. Installing Bugzilla</A
+NAME="USING"
+>Chapter 2. Using Bugzilla</A
></H1
+><TABLE
+BORDER="0"
+WIDTH="100%"
+CELLSPACING="0"
+CELLPADDING="0"
+CLASS="EPIGRAPH"
+><TR
+><TD
+WIDTH="45%"
+> </TD
+><TD
+WIDTH="45%"
+ALIGN="LEFT"
+VALIGN="TOP"
+><I
+><P
+><I
+>What, Why, How, & Where?</I
+></P
+></I
+></TD
+></TR
+></TABLE
><DIV
CLASS="SECTION"
-><H1
+><HR><H1
CLASS="SECTION"
><A
-NAME="README.UNIX"
->2.1. UNIX Installation</A
+NAME="WHATIS"
+>2.1. What is Bugzilla?</A
></H1
-><DIV
-CLASS="SECTION"
-><H2
-CLASS="SECTION"
-><A
-NAME="AEN190"
->2.1.1. ERRATA</A
-></H2
-><DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
><P
-><B
->Note: </B
-> If you are installing Bugzilla on S.u.S.e. Linux, or some other
- distributions with "paranoid" security options, it is possible
- that the checksetup.pl script may fail with the error:
- <SPAN
-CLASS="ERRORNAME"
->cannot chdir(/var/spool/mqueue): Permission denied</SPAN
->
- This is because your
- /var/spool/mqueue directory has a mode of "drwx------". Type
- <B
-CLASS="COMMAND"
->chmod 755 /var/spool/mqueue</B
-> as root to fix this problem.
- </P
-></BLOCKQUOTE
-></DIV
-><DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
+> Bugzilla is one example of a class of programs called "Defect
+Tracking Systems", or, more commonly, "Bug-Tracking Systems". Defect
+Tracking Systems allow individual or groups of developers to keep
+track of outstanding bugs in their product effectively. Bugzilla was
+originally written by Terry Weissman in a programming language called
+"TCL", to replace a crappy bug-tracking database used internally for
+Netscape Communications. Terry later ported Bugzilla to Perl from
+TCL, and in Perl it remains to this day. Most commercial
+defect-tracking software vendors at the time charged enormous
+licensing fees, and Bugzilla quickly became a favorite of the
+open-source crowd (with its genesis in the open-source browser
+project, Mozilla). It is now the de-facto standard defect-tracking
+system against which all others are measured.
+ </P
><P
-><B
->Note: </B
-> Release Notes for Bugzilla 2.12 are available at docs/rel_notes.txt
- </P
-></BLOCKQUOTE
-></DIV
-><DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
+> Bugzilla has matured immensely, and now boasts many advanced features. These include:
+ <P
+></P
+><UL
+><LI
><P
-><B
->Note: </B
-> The preferred documentation for Bugzilla is available in docs/, with
- a variety of document types available. Please refer to these documents when
- installing, configuring, and maintaining your Bugzilla installation.
- </P
-></BLOCKQUOTE
+> integrated, product-based granular security schema
+ </P
+></LI
+><LI
+><P
+> inter-bug dependencies and dependency graphing
+ </P
+></LI
+><LI
+><P
+> advanced reporting capabilities
+ </P
+></LI
+><LI
+><P
+> a robust, stable RDBMS back-end
+ </P
+></LI
+><LI
+><P
+> extensive configurability
+ </P
+></LI
+><LI
+><P
+> a very well-understood and well-thought-out natural bug resolution protocol
+ </P
+></LI
+><LI
+><P
+> email, XML, console, and HTTP APIs
+ </P
+></LI
+><LI
+><P
+> available integration with automated software
+ configuration management systems, including Perforce and
+ CVS (through the Bugzilla email interface and
+ checkin/checkout scripts)
+ </P
+></LI
+><LI
+><P
+> too many more features to list
+ </P
+></LI
+></UL
+>
+ </P
+><P
+> Despite its current robustness and popularity, Bugzilla faces
+ some near-term challenges, such as reliance on a single
+ database, a lack of abstraction of the user interface and
+ program logic, verbose email bug notifications, a powerful but
+ daunting query interface, little reporting configurability,
+ problems with extremely large queries, some unsupportable bug
+ resolution options, little internationalization (although non-US
+ character sets are accepted for comments), and dependence on
+ some nonstandard libraries.
+ </P
+><P
+> Some recent headway has been made on the query front, however.
+ If you are using the latest version of Bugzilla, you should see
+ a <SPAN
+CLASS="QUOTE"
+>"simple search"</SPAN
+> form on the default front page of
+ your Bugzilla install. Type in two or three search terms and
+ you should pull up some relevant information. This is also
+ available as "queryhelp.cgi".
+ </P
+><P
+> Despite these small problems, Bugzilla is very hard to beat. It
+ is under <EM
+>very</EM
+> active development to address
+ the current issues, and continually gains new features.
+ </P
></DIV
><DIV
-CLASS="WARNING"
-><P
-></P
+CLASS="SECTION"
+><HR><H1
+CLASS="SECTION"
+><A
+NAME="WHY"
+>2.2. Why Should We Use Bugzilla?</A
+></H1
><TABLE
-CLASS="WARNING"
-BORDER="1"
+BORDER="0"
WIDTH="100%"
+CELLSPACING="0"
+CELLPADDING="0"
+CLASS="EPIGRAPH"
><TR
><TD
-ALIGN="CENTER"
-><B
->Warning</B
+WIDTH="45%"
+> </TD
+><TD
+WIDTH="45%"
+ALIGN="LEFT"
+VALIGN="TOP"
+><I
+><P
+><I
+>No, Who's on first...</I
+></P
+></I
></TD
></TR
+></TABLE
+><P
+> 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.
+ </P
+><P
+> 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.
+ </P
+><P
+> But why should <EM
+>you</EM
+> use Bugzilla?
+ </P
+><P
+> 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, Loki
+ software, Linux-Mandrake, and VA Systems. Combined with systems
+ such as CVS, Bonsai, or Perforce SCM, Bugzilla provides a
+ powerful, easy-to-use solution to configuration management and
+ replication problems
+ </P
+><P
+> 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 <EM
+>something</EM
+> 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 by using Bugzilla's e-mail
+ integration features be able to follow the discussion trail that
+ led to critical decisions.
+ </P
+><P
+> 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.
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H1
+CLASS="SECTION"
+><A
+NAME="HOW"
+>2.3. How do I use Bugzilla?</A
+></H1
+><TABLE
+BORDER="0"
+WIDTH="100%"
+CELLSPACING="0"
+CELLPADDING="0"
+CLASS="EPIGRAPH"
><TR
><TD
+WIDTH="45%"
+> </TD
+><TD
+WIDTH="45%"
ALIGN="LEFT"
+VALIGN="TOP"
+><I
><P
-> Bugzilla is not a package where you can just plop it in a directory,
- twiddle a few things, and you're off. Installing Bugzilla assumes you
- know your variant of UNIX or Microsoft Windows well, are familiar with the
- command line, and are comfortable compiling and installing a plethora
- of third-party utilities. To install Bugzilla on Win32 requires
- fair Perl proficiency, and if you use a webserver other than Apache you
- should be intimately familiar with the security mechanisms and CGI
- environment thereof.
- </P
+><I
+>Hey! I'm Woody! Howdy, Howdy, Howdy!</I
+></P
+></I
></TD
></TR
></TABLE
-></DIV
-><DIV
-CLASS="WARNING"
+><P
+> Bugzilla is a large, complex system. Describing how to use it
+ requires some time. If you are only interested in installing or
+ administering a Bugzilla installation, please consult the
+ Installing and Administering Bugzilla portions of this Guide.
+ This section is principally aimed towards developing end-user
+ mastery of Bugzilla, so you may fully enjoy the benefits
+ afforded by using this reliable open-source bug-tracking
+ software.
+ </P
+><P
+> Throughout this portion of the Guide, we will refer to user
+ account options available at the Bugzilla test installation,
+ <A
+HREF="http://landfill.tequilarista.org/"
+TARGET="_top"
+> landfill.tequilarista.org</A
+>.
+ <DIV
+CLASS="NOTE"
><P
></P
><TABLE
-CLASS="WARNING"
-BORDER="1"
+CLASS="NOTE"
WIDTH="100%"
+BORDER="0"
><TR
><TD
+WIDTH="25"
ALIGN="CENTER"
-><B
->Warning</B
-></TD
-></TR
-><TR
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
><TD
ALIGN="LEFT"
+VALIGN="TOP"
><P
-> Bugzilla has not undergone a complete security review. Security holes
- may exist in the code. Great care should be taken both in the installation
- and usage of this software. Carefully consider the implications of
- installing other network services with Bugzilla.
+> Some people have run into difficulties completing this
+ tutorial. If you run into problems, please check the
+ updated online documentation available at <A
+HREF="http://www.trilobyte.net/barnsons/"
+TARGET="_top"
+>http://www.trilobyte.net/barnsons</A
+>. If you're still stumped, please subscribe to the newsgroup and provide details of exactly what's stumping you! If enough people complain, I'll have to fix it in the next version of this Guide. You can subscribe to the newsgroup at <A
+HREF="news://news.mozilla.org/netscape.public.mozilla.webtools"
+TARGET="_top"
+> news://news.mozilla.org/netscape.public.mozilla.webtools</A
+>
</P
></TD
></TR
></TABLE
></DIV
-></DIV
+> Although Landfill serves as a great introduction to
+ Bugzilla, it does not offer all the options you would have as a
+ user on your own installation of Bugzilla, nor can it do more
+ than serve as a general introduction to Bugzilla. Additionally,
+ Landfill often runs cutting-edge versions of Bugzilla for
+ testing, so some things may work slightly differently than
+ mentioned here.
+ </P
><DIV
CLASS="SECTION"
><HR><H2
CLASS="SECTION"
><A
-NAME="AEN204"
->2.1.2. Step-by-step Install</A
+NAME="MYACCOUNT"
+>2.3.1. Create a Bugzilla Account</A
></H2
-><DIV
-CLASS="SECTION"
-><H3
-CLASS="SECTION"
-><A
-NAME="AEN206"
->2.1.2.1. Introduction</A
-></H3
><P
-> Installation of bugzilla is pretty straightforward, particularly if your
- machine already has MySQL and the MySQL-related perl packages installed.
- If those aren't installed yet, then that's the first order of business. The
- other necessary ingredient is a web server set up to run cgi scripts.
- While using Apache for your webserver is not required, it is recommended.
- </P
-><P
-> Bugzilla has been successfully installed under Solaris, Linux, and
- Win32. The peculiarities of installing on Win32 (Win98+/NT/2K) are not
- included in this section of the Guide; please check out the "Win32 Installation Instructions"
- for further advice on getting Bugzilla to work on Microsoft Windows.
- </P
-><P
-> The Bugzilla Guide is contained in the "docs/" folder. It is available
- in plain text (docs/txt), HTML (docs/html), or SGML source (docs/sgml).
- </P
-></DIV
-><DIV
-CLASS="SECTION"
-><HR><H3
-CLASS="SECTION"
-><A
-NAME="AEN211"
->2.1.2.2. Installing the Prerequisites</A
-></H3
+> First things first! 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 the end-user
+ Bugzilla experience, use this URL: <A
+HREF="http://landfill.tequilarista.org/bugzilla-tip/"
+TARGET="_top"
+> http://landfill.tequilarista.org/bugzilla-tip/</A
+>
+ </P
><P
-> The software packages necessary for the proper running of bugzilla are:
- <P
></P
><OL
TYPE="1"
><LI
><P
-> MySQL database server and the mysql client (3.22.5 or greater)
- </P
-></LI
-><LI
-><P
-> Perl (5.004 or greater)
- </P
-></LI
-><LI
-><P
-> DBI Perl module
- </P
-></LI
-><LI
-><P
-> Data::Dumper Perl module
- </P
-></LI
-><LI
-><P
-> DBD::mySQL
- </P
-></LI
-><LI
-><P
-> TimeDate Perl module collection
- </P
-></LI
-><LI
-><P
-> GD perl module (1.8.3) (optional, for bug charting)
- </P
-></LI
-><LI
-><P
-> Chart::Base Perl module (0.99c) (optional, for bug charting)
- </P
+> Click the "Open a new Bugzilla account" link.
+ </P
></LI
><LI
><P
-> DB_File Perl module (optional, for bug charting)
- </P
+> Enter your "E-mail address" and "Real Name" (or whatever
+ name you want to call yourself) in the spaces provided,
+ then select the "Create Account" button.
+ </P
></LI
><LI
><P
-> The web server of your choice. Apache is recommended.
- </P
+> Within moments, you should receive an email to the address
+ you provided above, which contains your login name
+ (generally the same as the email address), and a password
+ you can use to access your account. This password is
+ randomly generated, and should be changed at your nearest
+ opportunity (we'll go into how to do it later).
+ </P
></LI
><LI
><P
-> MIME::Parser Perl module (optional, for contrib/bug_email.pl interface)
- </P
-></LI
-></OL
->
- <DIV
-CLASS="NOTE"
-><BLOCKQUOTE
+> Click the <SPAN
+CLASS="QUOTE"
+>"Log In"</SPAN
+> link in the yellow area at
+ the bottom of the page in your browser, then enter your
+ <SPAN
+CLASS="QUOTE"
+>"E-mail address"</SPAN
+> and <SPAN
+CLASS="QUOTE"
+>"Password"</SPAN
+>
+ you just received into the spaces provided, and select
+ <SPAN
+CLASS="QUOTE"
+>"Login"</SPAN
+>.
+ <DIV
CLASS="NOTE"
><P
-><B
->Note: </B
-> You must run Bugzilla on a filesystem that supports file locking via
- flock(). This is necessary for Bugzilla to operate safely with multiple
- instances.
- </P
-></BLOCKQUOTE
-></DIV
->
- <DIV
-CLASS="WARNING"
-><P
></P
><TABLE
-CLASS="WARNING"
-BORDER="1"
-WIDTH="100%"
+CLASS="NOTE"
+WIDTH="90%"
+BORDER="0"
><TR
><TD
+WIDTH="25"
ALIGN="CENTER"
-><B
->Warning</B
-></TD
-></TR
-><TR
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
><TD
ALIGN="LEFT"
+VALIGN="TOP"
><P
-> It is a good idea, while installing Bugzilla, to ensure it is not
- <EM
->accessible</EM
-> by other machines on the Internet.
- Your machine may be vulnerable to attacks
- while you are installing. In other words, ensure there is some kind of firewall between you
- and the rest of the Internet. Many installation steps require an active Internet connection
- to complete, but you must take care to ensure that at no point is your machine vulnerable
- to an attack.
- </P
+> If you ever forget your password, you can come back to
+ this page, enter your <SPAN
+CLASS="QUOTE"
+>"E-mail address"</SPAN
+>,
+ then select the <SPAN
+CLASS="QUOTE"
+>"E-mail me a password"</SPAN
+>
+ button to have your password mailed to you again so
+ that you can login.
+ </P
></TD
></TR
></TABLE
></DIV
>
-
- </P
-></DIV
-><DIV
-CLASS="SECTION"
-><HR><H3
-CLASS="SECTION"
-><A
-NAME="AEN242"
->2.1.2.3. Installing MySQL Database</A
-></H3
-><P
-> Visit MySQL homepage at http://www.mysql.org/ and grab the latest stable
- release of the server. Both binaries and source are available and which
- you get shouldn't matter. Be aware that many of the binary versions
- of MySQL store their data files in /var which on many installations
- (particularly common with linux installations) is part of a smaller
- root partition. If you decide to build from sources you can easily set
- the dataDir as an option to configure.
- </P
+ <DIV
+CLASS="CAUTION"
><P
-> If you've installed from source or non-package (RPM, deb, etc.) binaries
- you'll want to make sure to add mysqld to your init scripts so the server
- daemon will come back up whenever your machine reboots.
- You also may want to edit those init scripts, to make sure that
- mysqld will accept large packets. By default, mysqld is set up to only
- accept packets up to 64K long. This limits the size of attachments you
- may put on bugs. If you add something like "-O max_allowed_packet=1M"
- to the command that starts mysqld (or safe_mysqld), then you will be
- able to have attachments up to about 1 megabyte.
- </P
-><DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
+></P
+><TABLE
+CLASS="CAUTION"
+WIDTH="90%"
+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
-><B
->Note: </B
-> If you plan on running Bugzilla and MySQL on the same machine,
- consider using the "--skip-networking" option in the init script.
- This enhances security by preventing network access to MySQL.
- </P
-></BLOCKQUOTE
-></DIV
+> Many modern browsers include an
+ <SPAN
+CLASS="QUOTE"
+>"Auto-Complete"</SPAN
+> or <SPAN
+CLASS="QUOTE"
+>"Form
+ Fill"</SPAN
+> feature to remember the user names and
+ passwords you type in at many sites. Unfortunately,
+ sometimes they attempt to guess what you will put in
+ as your password, and guess wrong. If you notice a
+ text box is already filled out, please overwrite the
+ contents of the text box so you can be sure to input
+ the correct information.
+ </P
+></TD
+></TR
+></TABLE
></DIV
-><DIV
-CLASS="SECTION"
-><HR><H3
-CLASS="SECTION"
-><A
-NAME="AEN248"
->2.1.2.4. Perl (5.004 or greater)</A
-></H3
-><P
-> Any machine that doesn't have perl on it is a sad machine indeed. Perl
- for *nix systems can be gotten in source form from http://www.perl.com.
- </P
-><P
-> Perl is now a far cry from the the single compiler/interpreter binary it
- once was. It now includes a great many required modules and quite a
- few other support files. If you're not up to or not inclined to build
- perl from source, you'll want to install it on your machine using some
- sort of packaging system (be it RPM, deb, or what have you) to ensure
- a sane install. In the subsequent sections you'll be installing quite
- a few perl modules; this can be quite ornery if your perl installation
- isn't up to snuff.
- </P
-><DIV
-CLASS="TIP"
-><BLOCKQUOTE
-CLASS="TIP"
-><P
-><B
->Tip: </B
-> You can skip the following Perl module installation
- steps by installing "Bundle::Bugzilla" from CPAN, which includes them.
- All Perl module installation steps require you have an active Internet
- connection.
- </P
-><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->bash#</TT
->
- <B
-CLASS="COMMAND"
->perl -MCPAN -e 'install "Bundle::Bugzilla"'</B
->
- </TT
>
</P
+></LI
+></OL
><P
-> Bundle::Bugzilla doesn't include GD, Chart::Base, or MIME::Parser,
- which are not essential to a basic Bugzilla install. If installing
- this bundle fails, you should install each module individually to
- isolate the problem.
- </P
-></BLOCKQUOTE
-></DIV
+> Congratulations! If you followed these directions, you now
+ are the proud owner of a user account on
+ landfill.tequilarista.org (Landfill) or your local Bugzilla
+ install. You should now see in your browser a page called the
+ <SPAN
+CLASS="QUOTE"
+>"Bugzilla Query Page"</SPAN
+>. It may look daunting, but with this
+ Guide to walk you through it, you will master it in no time.
+ </P
></DIV
><DIV
CLASS="SECTION"
-><HR><H3
+><HR><H2
CLASS="SECTION"
><A
-NAME="AEN259"
->2.1.2.5. DBI Perl Module</A
-></H3
-><P
-> The DBI module is a generic Perl module used by other database related
- Perl modules. For our purposes it's required by the MySQL-related
- modules. As long as your Perl installation was done correctly the
- DBI module should be a breeze. It's a mixed Perl/C module, but Perl's
- MakeMaker system simplifies the C compilation greatly.
- </P
-><P
-> Like almost all Perl modules DBI can be found on the Comprehensive Perl
- Archive Network (CPAN) at http://www.cpan.org. The CPAN servers have a
- real tendency to bog down, so please use mirrors. The current location
- at the time of this writing (02/17/99) can be found in Appendix A.
- </P
-><P
-> Quality, general Perl module installation instructions can be found on
- the CPAN website, but the easy thing to do is to just use the CPAN shell
- which does all the hard work for you.
- </P
+NAME="QUERY"
+>2.3.2. The Bugzilla Query Page</A
+></H2
><P
-> To use the CPAN shell to install DBI:
- <DIV
-CLASS="INFORMALEXAMPLE"
-><A
-NAME="AEN265"
-></A
+> The Bugzilla Query Page is the heart and soul of the Bugzilla
+ user experience. It is the master interface where you can
+ find any bug report, comment, or patch currently in the
+ Bugzilla system. We'll go into how to create your own bug
+ report later on.
+ </P
><P
-></P
+> There are efforts underway to simplify query usage. If you
+ have a local installation of Bugzilla 2.12 or higher, you
+ should have <TT
+CLASS="FILENAME"
+>quicksearch.html</TT
+> available to
+ use and simplify your searches. There is also a helper for
+ the query interface, called
+ <TT
+CLASS="FILENAME"
+>queryhelp.cgi</TT
+>. Landfill tends to run the
+ latest code, so these two utilities should be available there
+ for your perusal.
+ </P
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->bash#</TT
->
- <B
-CLASS="COMMAND"
->perl -MCPAN -e 'install "DBI"'</B
->
- </TT
->
- <DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
+> At this point, please visit the main Bugzilla site,
+ <A
+HREF="http://bugzilla.mozilla.org/query.cgi"
+TARGET="_top"
+> bugzilla.mozilla.org</A
+>, to see a more fleshed-out query page.
+ </P
><P
-><B
->Note: </B
->Replace "DBI" with the name of whichever module you wish
- to install, such as Data::Dumper, TimeDate, GD, etc.</P
-></BLOCKQUOTE
-></DIV
->
- </P
+> The first thing you need to notice about the Bugzilla Query
+ Page is that nearly every box you see on your screen has a
+ hyperlink nearby, explaining what it is or what it does. Near
+ the upper-left-hand corner of your browser window you should
+ see the word <SPAN
+CLASS="QUOTE"
+>"Status"</SPAN
+> underlined. Select it.
+ </P
><P
-></P
-></DIV
+> Notice the page that popped up? Every underlined word you see
+ on your screen is a hyperlink that will take you to
+ context-sensitive help. Click around for a while, and learn
+ what everything here does. To return to the query interface
+ after pulling up a help page, use the <SPAN
+CLASS="QUOTE"
+>"Back"</SPAN
>
- To do it the hard way:
- <DIV
-CLASS="INFORMALEXAMPLE"
-><A
-NAME="AEN272"
-></A
-><P
-></P
+ button in your browser.
+ </P
><P
-> Untar the module tarball -- it should create its own directory
- </P
+> I'm sure that after checking out the online help, you are now
+ an expert on the Bugzilla Query Page. If, however, you feel
+ you haven't mastered it yet, let me walk you through making a
+ few successful queries to find out what there are in the
+ Bugzilla bug-tracking system itself.
+ </P
><P
-> CD to the directory just created, and enter the following commands:
- <P
></P
><OL
TYPE="1"
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->bash#</TT
->
- <B
-CLASS="COMMAND"
->perl Makefile.PL</B
->
- </TT
->
- </P
+> Ensure you are back on the <SPAN
+CLASS="QUOTE"
+>"Bugzilla Query
+ Page"</SPAN
+>. Do nothing in the boxes marked "Status",
+ "Resolution", "Platform", "OpSys", "Priority", or
+ "Severity". The default query for "Status" is to find all
+ bugs that are NEW, ASSIGNED, or REOPENED, which is what we
+ want. If you don't select anything in the other 5
+ scrollboxes there, then you are saying that "any of these
+ are OK"; we're not locking ourselves into only finding
+ bugs on the "DEC" Platform, or "Windows 95" OpSys
+ (Operating System). You're smart, I think you have it
+ figured out.
+ </P
+><P
+> Basically, selecting <EM
+>anything</EM
+> on the
+ query page narrows your search down. Leaving stuff
+ unselected, or text boxes unfilled, broadens your search.
+ </P
></LI
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->bash#</TT
->
- <B
-CLASS="COMMAND"
->make</B
->
- </TT
->
- </P
+> You see the box immediately below the top six boxes that
+ contains an "Email" text box, with the words "matching
+ as", a drop-down selection box, then some checkboxes with
+ "Assigned To" checked by default? This allows you to
+ filter your search down based upon email address. Let's
+ put my email address in there, and see what happens.
+ </P
+><P
+> Type "barnboy@trilobyte.net" in the top Email text box.
+ </P
></LI
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->bash#</TT
->
- <B
-CLASS="COMMAND"
->make test</B
->
- </TT
->
- </P
+> Let's narrow the search some more. Scroll down until you
+ find the box with the word "Program" over the top of it.
+ This is where we can narrow our search down to only
+ specific products (software programs or product lines) in
+ our Bugzilla database. Please notice the box is a
+ <EM
+>scrollbox</EM
+>. Using the down arrow on
+ the scrollbox, scroll down until you can see an entry
+ called "Bugzilla". Select this entry.
+ </P
></LI
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->bash#</TT
->
- <B
-CLASS="COMMAND"
->make install</B
->
- </TT
->
- </P
-></LI
-></OL
->
- If everything went ok that should be all it takes. For the vast
- majority of perl modules this is all that's required.
- </P
+> Did you notice that some of the boxes to the right changed
+ when you selected "Bugzilla"? Every Program (or Product)
+ has different Versions, Components, and Target Milestones
+ associated with it. A "Version" is the number of a
+ software program.
+ <DIV
+CLASS="EXAMPLE"
+><A
+NAME="AEN307"
+></A
><P
+><B
+>Example 2-1. Some Famous Software Versions</B
></P
-></DIV
->
- </P
-></DIV
><DIV
-CLASS="SECTION"
-><HR><H3
-CLASS="SECTION"
+CLASS="INFORMALEXAMPLE"
><A
-NAME="AEN296"
->2.1.2.6. Data::Dumper Perl Module</A
-></H3
-><P
-> The Data::Dumper module provides data structure persistence for Perl
- (similar to Java's serialization). It comes with later sub-releases of
- Perl 5.004, but a re-installation just to be sure it's available won't
- hurt anything.
- </P
+NAME="AEN309"
+></A
><P
-> Data::Dumper is used by the MySQL related Perl modules. It can be
- found on CPAN (link in Appendix A) and can be installed by following
- the same four step make sequence used for the DBI module.
- </P
-></DIV
-><DIV
-CLASS="SECTION"
-><HR><H3
-CLASS="SECTION"
-><A
-NAME="AEN300"
->2.1.2.7. MySQL related Perl Module Collection</A
-></H3
+></P
><P
-> The Perl/MySQL interface requires a few mutually-dependent perl
- modules. These modules are grouped together into the the
- Msql-Mysql-modules package. This package can be found at CPAN.
- After the archive file has been downloaded it should
- be untarred.
- </P
+> Do you remember the hype in 1995 when Microsoft
+ Windows 95(r) was released? It may have been several
+ years ago, but Microsoft(tm) spent over $300 Million
+ advertising this new Version of their software.
+ Three years later, they released Microsoft Windows
+ 98(r), another new version, to great fanfare, and
+ then in 2000 quietly released Microsoft Windows
+ ME(Millenium Edition)(r).
+ </P
><P
-> The MySQL modules are all built using one make file which is generated
- by running:
- <TT
-CLASS="PROMPT"
->bash#</TT
->
- <B
-CLASS="COMMAND"
->perl Makefile.pl</B
+> Software "Versions" help a manufacturer
+ differentiate their current product from their
+ previous products. Most do not identify their
+ products by the year they were released. Instead,
+ the "original" version of their software will often
+ be numbered "1.0", with small bug-fix releases on
+ subsequent tenths of a digit. In most cases, it's
+ not a decimal number; for instance, often 1.9 is an
+ <EM
+>older</EM
+> version of the software
+ than 1.11, but is a <EM
+>newer</EM
>
- </P
-><P
-> The MakeMaker process will ask you a few questions about the desired
- compilation target and your MySQL installation. For many of the questions
- the provided default will be adequate.
- </P
+ version than 1.1.1.
+ </P
><P
-> When asked if your desired target is the MySQL or mSQL packages
- selected the MySQL related ones. Later you will be asked if you wish
- to provide backwards compatibility with the older MySQL packages; you
- must answer YES to this question. The default will be no, and if you
- select it things won't work later.
- </P
+> In general, a "Version" in Bugzilla should refer to
+ <EM
+>released</EM
+> products, not products
+ that have not yet been released to the public.
+ Forthcoming products are what the Target Milestone
+ field is for.
+ </P
><P
-> A host of 'localhost' should be fine and a testing user of 'test' and
- a null password should find itself with sufficient access to run tests
- on the 'test' database which MySQL created upon installation. If 'make
- test' and 'make install' go through without errors you should be ready
- to go as far as database connectivity is concerned.
- </P
+></P
></DIV
-><DIV
-CLASS="SECTION"
-><HR><H3
-CLASS="SECTION"
-><A
-NAME="AEN309"
->2.1.2.8. TimeDate Perl Module Collection</A
-></H3
-><P
-> Many of the more common date/time/calendar related Perl modules have
- been grouped into a bundle similar to the MySQL modules bundle. This
- bundle is stored on the CPAN under the name TimeDate. A (hopefully
- current) link can be found in Appendix A. The component module we're
- most interested in is the Date::Format module, but installing all of them
- is probably a good idea anyway. The standard Perl module installation
- instructions should work perfectly for this simple package.
- </P
></DIV
-><DIV
-CLASS="SECTION"
-><HR><H3
-CLASS="SECTION"
-><A
-NAME="AEN312"
->2.1.2.9. GD Perl Module (1.8.3)</A
-></H3
-><P
-> The GD library was written by Thomas Boutell a long while ago to
- programatically generate images in C. Since then it's become almost a
- defacto standard for programatic image construction. The Perl bindings
- to it found in the GD library are used on a million web pages to generate
- graphs on the fly. That's what bugzilla will be using it for so you'd
- better install it if you want any of the graphing to work.
- </P
+>
+ </P
><P
-> Actually bugzilla uses the Graph module which relies on GD itself,
- but isn't that always the way with OOP. At any rate, you can find the
- GD library on CPAN (link in Appendix "Required Software").
- </P
-><DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
-><P
-><B
->Note: </B
-> The Perl GD library requires some other libraries that may or may not be
- installed on your system, including "libpng" and "libgd". The full requirements
- are listed in the Perl GD library README. Just realize that if compiling GD fails,
- it's probably because you're missing a required library.
- </P
-></BLOCKQUOTE
-></DIV
-></DIV
-><DIV
-CLASS="SECTION"
-><HR><H3
-CLASS="SECTION"
-><A
-NAME="AEN318"
->2.1.2.10. Chart::Base Perl Module (0.99c)</A
-></H3
-><P
-> The Chart module provides bugzilla with on-the-fly charting
- abilities. It can be installed in the usual fashion after it has been
- fetched from CPAN where it is found as the Chart-x.x... tarball in a
- directory to be listed in Appendix "Required Software". Note that as with the GD perl
- module, only the specific versions listed above (or newer) will work. Earlier
- versions used GIF's, which are no longer supported by the latest
- versions of GD.
- </P
-></DIV
-><DIV
-CLASS="SECTION"
-><HR><H3
-CLASS="SECTION"
+> A "Component" is a piece of a Product.
+ It may be a standalone program, or some other logical
+ division of a Product or Program.
+ Normally, a Component has a single Owner, who is responsible
+ for overseeing efforts to improve that Component.
+ <DIV
+CLASS="EXAMPLE"
><A
-NAME="AEN321"
->2.1.2.11. DB_File Perl Module</A
-></H3
+NAME="AEN317"
+></A
><P
-> DB_File is a module which allows Perl programs to make use of the facilities provided by
- Berkeley DB version 1.x. This module is required by collectstats.pl which is used for
- bug charting. If you plan to make use of bug charting, you must install this module.
- </P
-></DIV
+><B
+>Example 2-2. Mozilla's Bugzilla Components</B
+></P
><DIV
-CLASS="SECTION"
-><HR><H3
-CLASS="SECTION"
+CLASS="INFORMALEXAMPLE"
><A
-NAME="AEN324"
->2.1.2.12. HTTP Server</A
-></H3
-><P
-> You have a freedom of choice here - Apache, Netscape or any other
- server on UNIX would do. You can easily run the web server on a different
- machine than MySQL, but need to adjust the MySQL "bugs" user permissions
- accordingly.
- </P
-><P
-> You'll want to make sure that your web server will run any file
- with the .cgi extension as a cgi and not just display it. If you're using
- apache that means uncommenting the following line in the srm.conf file:
- <TT
-CLASS="COMPUTEROUTPUT"
->AddHandler cgi-script .cgi</TT
->
- </P
-><P
-> With apache you'll also want to make sure that within the access.conf
- file the line:
- <TT
-CLASS="COMPUTEROUTPUT"
-> Options ExecCGI
- </TT
->
- is in the stanza that covers the directories you intend to put the bugzilla
- .html and .cgi files into.
- </P
+NAME="AEN319"
+></A
><P
-> If you are using a newer version of Apache, both of the above lines will be
- (or will need to be) in the httpd.conf file, rather than srm.conf or
- access.conf.
- </P
-><DIV
-CLASS="WARNING"
+></P
><P
+> Mozilla's "Bugzilla" Product is composed of several pieces (Components):
+ <P
></P
><TABLE
-CLASS="WARNING"
-BORDER="1"
-WIDTH="100%"
+BORDER="0"
+><TBODY
><TR
><TD
-ALIGN="CENTER"
-><B
->Warning</B
-></TD
+><EM
+>Administration</EM
+>,
+ Administration of a bugzilla installation, including
+ <TT
+CLASS="FILENAME"
+>editcomponents.cgi</TT
+>,
+ <TT
+CLASS="FILENAME"
+>editgroups.cgi</TT
+>,
+ <TT
+CLASS="FILENAME"
+>editkeywords.cgi</TT
+>,
+ <TT
+CLASS="FILENAME"
+>editparams.cgi</TT
+>,
+ <TT
+CLASS="FILENAME"
+>editproducts.cgi</TT
+>,
+ <TT
+CLASS="FILENAME"
+>editusers.cgi</TT
+>,
+ <TT
+CLASS="FILENAME"
+>editversions.cgi,</TT
+> and
+ <TT
+CLASS="FILENAME"
+>sanitycheck.cgi</TT
+>.
+ </TD
></TR
><TR
><TD
-ALIGN="LEFT"
-><P
-> There are two critical directories and a file that should not be a served by
- the HTTP server. These are the 'data' and 'shadow' directories and the
- 'localconfig' file. You should configure your HTTP server to not serve
- content from these files. Failure to do so will expose critical passwords
- and other data. Please see your HTTP server configuration manual on how
- to do this. If you use quips (at the top of the buglist pages) you will want
- the 'data/comments' file to still be served. This file contains those quips.
- </P
-></TD
+><EM
+>Bugzilla-General</EM
+>,
+ Anything that doesn't fit in the other components, or spans
+ multiple components.
+ </TD
+></TR
+><TR
+><TD
+><EM
+>Creating/Changing Bugs</EM
+>,
+ Creating, changing, and viewing bugs.
+ <TT
+CLASS="FILENAME"
+>enter_bug.cgi</TT
+>,
+ <TT
+CLASS="FILENAME"
+>post_bug.cgi</TT
+>,
+ <TT
+CLASS="FILENAME"
+>show_bug.cgi</TT
+> and
+ <TT
+CLASS="FILENAME"
+>process_bug.cgi</TT
+>.
+ </TD
+></TR
+><TR
+><TD
+><EM
+>Documentation</EM
+>,
+ The bugzilla documentation, including anything in the
+ <TT
+CLASS="FILENAME"
+>docs/</TT
+> directory and The Bugzilla Guide
+ (This document :)
+ </TD
+></TR
+><TR
+><TD
+><EM
+>Email</EM
+>,
+ Anything to do with email sent by Bugzilla.
+ <TT
+CLASS="FILENAME"
+>processmail</TT
+>
+ </TD
+></TR
+><TR
+><TD
+><EM
+>Installation</EM
+>,
+ The installation process of Bugzilla. This includes
+ <TT
+CLASS="FILENAME"
+>checksetup.pl</TT
+> and whatever else it evolves into.
+ </TD
+></TR
+><TR
+><TD
+><EM
+>Query/Buglist</EM
+>,
+ Anything to do with searching for bugs and viewing the buglists.
+ <TT
+CLASS="FILENAME"
+>query.cgi</TT
+> and
+ <TT
+CLASS="FILENAME"
+>buglist.cgi</TT
+>
+ </TD
></TR
+><TR
+><TD
+><EM
+>Reporting/Charting</EM
+>,
+ Getting reports from Bugzilla.
+ <TT
+CLASS="FILENAME"
+>reports.cgi</TT
+> and
+ <TT
+CLASS="FILENAME"
+>duplicates.cgi</TT
+>
+ </TD
+></TR
+><TR
+><TD
+><EM
+>User Accounts</EM
+>,
+ Anything about managing a user account from the user's perspective.
+ <TT
+CLASS="FILENAME"
+>userprefs.cgi</TT
+>, saved queries, creating accounts,
+ changing passwords, logging in, etc.
+ </TD
+></TR
+><TR
+><TD
+><EM
+>User Interface</EM
+>,
+ General issues having to do with the user interface cosmetics (not
+ functionality) including cosmetic issues, HTML templates, etc.
+ </TD
+></TR
+></TBODY
></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="SECTION"
-><HR><H3
-CLASS="SECTION"
-><A
-NAME="AEN334"
->2.1.2.13. Installing the Bugzilla Files</A
-></H3
><P
-> You should untar the Bugzilla files into a directory that you're
- willing to make writable by the default web server user (probably
- 'nobody'). You may decide to put the files off of the main web space
- for your web server or perhaps off of /usr/local with a symbolic link
- in the web space that points to the bugzilla directory. At any rate,
- just dump all the files in the same place (optionally omitting the CVS
- directories if they were accidentally tarred up with the rest of Bugzilla)
- and make sure you can access the files in that directory through your
- web server.
- </P
-><DIV
-CLASS="TIP"
-><BLOCKQUOTE
-CLASS="TIP"
+></P
+>
+ </P
><P
-><B
->Tip: </B
-> HINT: If you symlink the bugzilla directory into your Apache's
- HTML heirarchy, you may receive "Forbidden" errors unless you
- add the "FollowSymLinks" directive to the <Directory> entry
- for the HTML root.
- </P
-></BLOCKQUOTE
+></P
></DIV
+></DIV
+>
+ </P
><P
-> Once all the files are in a web accessible directory, make that
- directory writable by your webserver's user (which may require just
- making it world writable). This is a temporary step until you run
- the post-install "checksetup.pl" script, which locks down your
- installation.
- </P
+> A "Milestone", or "Target Milestone" is a often a planned
+ future "Version" of a product. In many cases, though,
+ Milestones simply represent significant dates for a
+ developer. Having certain features in your Product is
+ frequently tied to revenue (money) the developer will
+ receive if the features work by the time she reaches the
+ Target Milestone. Target Milestones are a great tool to
+ organize your time. If someone will pay you $100,000 for
+ incorporating certain features by a certain date, those
+ features by that Milestone date become a very high
+ priority. Milestones tend to be highly malleable
+ creatures, though, that appear to be in reach but are out
+ of reach by the time the important day arrives.
+ </P
><P
-> Lastly, you'll need to set up a symbolic link from /usr/bonsaitools/bin
- to the correct location of your perl executable (probably /usr/bin/perl).
- Otherwise you must hack all the .cgi files to change where they look
- for perl. To make future upgrades easier, you should use the symlink
- approach.
- <DIV
-CLASS="TIP"
-><BLOCKQUOTE
-CLASS="TIP"
+> The Bugzilla Project has set up Milestones for future
+ Bugzilla versions 2.14, 2.16, 2.18, 3.0, etc. However, a
+ Target Milestone can just as easily be a specific date,
+ code name, or weird alphanumeric combination, like "M19".
+ </P
+></LI
+><LI
><P
-><B
->Tip: </B
-> If you don't have root access to set this symlink up, check out the
- "setperl.csh" utility, listed in the Patches section of this
- Guide. It will change the path to perl in all your Bugzilla files for
- you.
- </P
-></BLOCKQUOTE
-></DIV
->
- </P
-></DIV
-><DIV
-CLASS="SECTION"
-><HR><H3
-CLASS="SECTION"
-><A
-NAME="AEN343"
->2.1.2.14. Setting Up the MySQL Database</A
-></H3
+> OK, now let's select the "Bugzilla" component from its scrollbox.
+ </P
+></LI
+><LI
><P
-> After you've gotten all the software installed and working you're ready
- to start preparing the database for its life as a the back end to a high
- quality bug tracker.
- </P
+> Skip down the page a bit -- do you see the "submit query" button?
+ Select it, and let's run
+ this query!
+ </P
+></LI
+><LI
><P
-> First, you'll want to fix MySQL permissions to allow access from
- Bugzilla. For the purpose of this Installation section, the Bugzilla username
- will be "bugs", and will have minimal permissions. Bugzilla has
- not undergone a thorough security audit. It may be possible for
- a system cracker to somehow trick Bugzilla into executing a command
- such as "; DROP DATABASE mysql".
- </P
+> Congratulations! You've completed your first Query, and
+ have before you the Bug List of the author of this Guide,
+ Matthew P. Barnson (barnboy@trilobyte.net). If I'm doing
+ well, you'll have a cryptic "Zarro Boogs Found" message on
+ your screen. It is just a happy hacker's way of saying
+ "Zero Bugs Found". However, I am fairly certain I will
+ always have some bugs assigned to me that aren't done yet,
+ so you won't often see that message!
+ </P
+></LI
+></OL
><P
-> That would be bad.
- </P
+> I encourage you to click the bug numbers in the left-hand
+ column and examine my bugs. Also notice that if you click the
+ underlined links near the top of this page, they do not take
+ you to context-sensitive help here, but instead sort the
+ columns of bugs on the screen! When you need to sort your bugs
+ by priority, severity, or the people they are assigned to,
+ this is a tremendous timesaver.
+ </P
><P
-> Give the MySQL root user a password. MySQL passwords are
- limited to 16 characters.
- <P
+> A couple more interesting things about the Bug List page:
+ <P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->bash#</TT
->
- <B
-CLASS="COMMAND"
->mysql -u root mysql</B
->
- </TT
->
- </TD
+><EM
+>Change Columns</EM
+>: by selecting
+ this link, you can show all kinds of information in the
+ Bug List</TD
></TR
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->mysql></TT
->
- <B
-CLASS="COMMAND"
-> UPDATE user SET Password=PASSWORD ('new_password')
- WHERE user='root';
- </B
->
- </TT
->
- </TD
+><EM
+>Change several bugs at once</EM
+>: If
+ you have sufficient rights to change all the bugs shown in
+ the Bug List, you can mass-modify them. This is a big
+ time-saver.</TD
></TR
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->mysql></TT
->
- <B
-CLASS="COMMAND"
->FLUSH PRIVILEGES;</B
->
- </TT
->
- </TD
+><EM
+>Send mail to bug owners</EM
+>: If you
+ have many related bugs, you can request an update from
+ every person who owns the bugs in the Bug List asking them
+ the status.</TD
+></TR
+><TR
+><TD
+><EM
+>Edit this query</EM
+>: If you didn't
+ get exactly the results you were looking for, you can
+ return to the Query page through this link and make small
+ revisions to the query you just made so you get more
+ accurate results.</TD
></TR
></TBODY
></TABLE
><P
></P
>
- From this point on, if you need to access MySQL as the
- MySQL root user, you will need to use "mysql -u root -p" and
- enter your new_password. Remember that MySQL user names have
- nothing to do with Unix user names (login names).
- </P
-><P
-> Next, we create the "bugs" user, and grant sufficient
- permissions for checksetup.pl, which we'll use later, to work
- its magic. This also restricts the "bugs" user to operations
- within a database called "bugs", and only allows the account
- to connect from "localhost". Modify it to reflect your setup
- if you will be connecting from another machine or as a different
- user.
- </P
+ </P
+><DIV
+CLASS="NOTE"
><P
-> Remember to set bugs_password to some unique password.
- <P
></P
><TABLE
+CLASS="NOTE"
+WIDTH="100%"
BORDER="0"
-><TBODY
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->mysql></TT
->
- <B
-CLASS="COMMAND"
->GRANT SELECT,INSERT,UPDATE,DELETE,INDEX,
- ALTER,CREATE,DROP,REFERENCES
- ON bugs.* TO bugs@localhost
- IDENTIFIED BY 'bugs_password';</B
->
- </TT
->
- </TD
-></TR
-><TR
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
-> mysql>
- </TT
->
- <B
-CLASS="COMMAND"
-> FLUSH PRIVILEGES;
- </B
->
- </TT
->
- </TD
-></TR
-></TBODY
-></TABLE
+ALIGN="LEFT"
+VALIGN="TOP"
><P
-></P
->
+> There are many more options to the Bugzilla Query Page and
+ the Bug List than I have shown you. But this should be
+ enough for you to learn to get around. I encourage you to
+ check out the <A
+HREF="http://www.mozilla.org/bugs/"
+TARGET="_top"
+>Bugzilla Home Page</A
+> to learn about the Anatomy and Life Cycle of a Bug before continuing.
</P
-><P
-> Next, run the magic checksetup.pl script. (Many thanks to Holger
- Schurig <holgerschurig@nikocity.de> for writing this script!)
- It will make sure Bugzilla files and directories have reasonable
- permissions, set up the "data" directory, and create all the MySQL
- tables.
- <P
-></P
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H2
+CLASS="SECTION"
+><A
+NAME="BUGREPORTS"
+>2.3.3. Creating and Managing Bug Reports</A
+></H2
><TABLE
BORDER="0"
-><TBODY
+WIDTH="100%"
+CELLSPACING="0"
+CELLPADDING="0"
+CLASS="EPIGRAPH"
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->bash#</TT
->
- <B
-CLASS="COMMAND"
->./checksetup.pl</B
->
- </TT
->
- </TD
-></TR
-></TBODY
-></TABLE
+WIDTH="45%"
+> </TD
+><TD
+WIDTH="45%"
+ALIGN="LEFT"
+VALIGN="TOP"
+><I
><P
+><I
+>And all this time, I thought we were taking bugs <EM
+>out</EM
+>...</I
></P
->
- The first time you run it, it will create a file called "localconfig".
- </P
-></DIV
+></I
+></TD
+></TR
+></TABLE
><DIV
CLASS="SECTION"
><HR><H3
CLASS="SECTION"
><A
-NAME="AEN379"
->2.1.2.15. Tweaking "localconfig"</A
+NAME="BUG_WRITING"
+>2.3.3.1. Writing a Great Bug Report</A
></H3
><P
-> This file contains a variety of settings you may need to tweak including
- how Bugzilla should connect to the MySQL database.
+> Before we plunge into writing your first bug report, I
+ encourage you to read some bug-writing guidelines. If you
+ are reading this document as part of a Bugzilla CVS checkout
+ or un-tarred Bugzilla distribution, you should be able to
+ read them by clicking <A
+HREF="../../bugwritinghelp.html"
+TARGET="_top"
+>here</A
+>. If you are reading this online, check out the Mozilla.org bug-writing guidelines at <A
+HREF="http://www.mozilla.org/quality/bug-writing-guidelines.html"
+TARGET="_top"
+>http://www.mozilla.org/quality/bug-writing-guidelines.html</A
+>. While some of the advice is Mozilla-specific, the basic principles of reporting Reproducible, Specific bugs, isolating the Product you are using, the Version of the Product, the Component which failed, the Hardware Platform, and Operating System you were using at the time of the failure go a long way toward ensuring accurate, responsible fixes for the bug that bit you.
+ </P
+><P
+> While you are at it, why not learn how to find previously
+ reported bugs? Mozilla.org has published a great tutorial
+ on finding duplicate bugs, available at <A
+HREF="http://www.mozilla.org/quality/help/beginning-duplicate-finding.html"
+TARGET="_top"
+> http://www.mozilla.org/quality/help/beginning-duplicate-finding.html</A
+>.
+ </P
+><P
+> I realize this was a lot to read. However, understanding
+ the mentality of writing great bug reports will help us on
+ the next part!
</P
><P
-> The connection settings include:
- <P
></P
><OL
TYPE="1"
><LI
><P
-> server's host: just use "localhost" if the MySQL server is
- local
- </P
+> Go back to <A
+HREF="http://landfill.tequilarista.org/bugzilla-tip/"
+TARGET="_top"
+> http://landfill.tequilarista.org/bugzilla-tip/</A
+> in your browser.
+ </P
></LI
><LI
><P
-> database name: "bugs" if you're following these directions
- </P
+> Select the <A
+HREF="http://landfill.tequilarista.org/bugzilla-tip/enter_bug.cgi"
+TARGET="_top"
+> Enter a new bug report</A
+> link.
+ </P
></LI
><LI
><P
-> MySQL username: "bugs" if you're following these directions
- </P
+> Select a product.
+ </P
></LI
><LI
><P
-> Password for the "bugs" MySQL account above
- </P
+> Now you should be at the "Enter Bug" form. The
+ "reporter" should have been automatically filled out for
+ you (or else Bugzilla prompted you to Log In again --
+ you did keep the email with your username and password,
+ didn't you?).
+ </P
></LI
-></OL
->
- </P
+><LI
><P
-> Once you are happy with the settings, re-run checksetup.pl. On this
- second run, it will create the database and an administrator account
- for which you will be prompted to provide information.
- </P
+> Select a Component in the scrollbox.
+ </P
+></LI
+><LI
><P
-> When logged into an administrator account once Bugzilla is running,
- if you go to the query page (off of the bugzilla main menu), you'll
- find an 'edit parameters' option that is filled with editable treats.
- </P
+> Bugzilla should have made reasonable guesses, based upon
+ your browser, for the "Platform" and "OS" drop-down
+ boxes. If those are wrong, change them -- if you're on
+ an SGI box running IRIX, we want to know!
+ </P
+></LI
+><LI
><P
-> Should everything work, you should have a nearly empty copy of the bug
- tracking setup.
- </P
+> Fill in the "Assigned To" box with the email address you
+ provided earlier. This way you don't end up sending
+ copies of your bug to lots of other people, since it's
+ just a test bug.
+ </P
+></LI
+><LI
><P
-> The second time around, checksetup.pl will stall if it is on a
- filesystem that does not fully support file locking via flock(), such as
- NFS mounts. This support is required for Bugzilla to operate safely with
- multiple instances. If flock() is not fully supported, it will stall at:
- <SPAN
-CLASS="ERRORCODE"
->Now regenerating the shadow database for all bugs.</SPAN
->
- <DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
+> Leave the "CC" text box blank. Fill in the "URL" box
+ with "http://www.mozilla.org".
+ </P
+></LI
+><LI
><P
-><B
->Note: </B
-> The second time you run checksetup.pl, it is recommended you be the same
- user as your web server runs under, and that you be sure you have set the
- "webservergroup" parameter in localconfig to match the web server's group
- name, if any. Under some systems, otherwise, checksetup.pl will goof up
- your file permissions and make them unreadable to your web server.
+> Enter "The Bugzilla Guide" in the Summary text box, and
+ place any comments you have on this tutorial, or the
+ Guide in general, into the Description box.
</P
-></BLOCKQUOTE
-></DIV
->
- </P
-><DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
+></LI
+></OL
><P
-><B
->Note: </B
-> The checksetup.pl script is designed so that you can run it at any time
- without causing harm. You should run it after any upgrade to Bugzilla.
- </P
-></BLOCKQUOTE
-></DIV
+> Voila! Select "Commit" and send in your bug report! Next
+ we'll look at resolving bugs.
+ </P
></DIV
><DIV
CLASS="SECTION"
><HR><H3
CLASS="SECTION"
><A
-NAME="AEN401"
->2.1.2.16. Setting Up Maintainers Manuall (Optional)</A
+NAME="BUG_MANAGE"
+>2.3.3.2. Managing your Bug Reports</A
></H3
><P
-> If you want to add someone else to every group by hand, you can do it
- by typing the appropriate MySQL commands. Run '<TT
-CLASS="COMPUTEROUTPUT"
-> mysql -u root -p bugs</TT
->'
- (you may need different parameters, depending on your security settings
- according to section 3, above). Then:
- <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->mysql></TT
->
- <B
-CLASS="COMMAND"
->update profiles set groupset=0x7fffffffffffffff
- where login_name = 'XXX';</B
->
- </TT
->
- </TD
-></TR
-></TBODY
-></TABLE
+> OK, you should have a link to the bug you just created near
+ the top of your page. It should say "Bug XXXX posted", with
+ a link to the right saying "Back to BUG# XXXX". Select this
+ link.
+ </P
><P
></P
->
- replacing XXX with the Bugzilla email address.
+><OL
+TYPE="1"
+><LI
+><P
+> Scroll down a bit on the subsequent page, until you see
+ the "Resolve bug, changing resolution to (dropdown box).
+ Normally, you would "Accept bug (change status to
+ ASSIGNED)", fix it, and then resolve. But in this case,
+ we're going to short-circuit the process because this
+ wasn't a real bug. Change the dropdown next to "Resolve
+ Bug" to "INVALID", make sure the radio button is marked
+ next to "Resolve Bug", then click "Commit".
+ </P
+></LI
+><LI
+><P
+> Hey! It said it couldn't take the change in a big red
+ box! That's right, you must specify a Comment in order
+ to make this change. Select the "Back" button in your
+ browser, add a Comment, then try Resolving the bug with
+ INVALID status again. This time it should work.
+ </P
+></LI
+></OL
+><P
+> You have now learned the basics of Bugzilla navigation,
+ entering a bug, and bug maintenance. I encourage you to
+ explore these features, and see what you can do with them!
+ We'll spend no more time on individual Bugs or Queries from
+ this point on, so you are on your own there.
+ </P
+><P
+> But I'll give a few last hints!
</P
+><P
+> There is a <A
+HREF="http://bugzilla.mozilla.org/help.html"
+TARGET="_top"
+>CLUE</A
+> on the Query page that will teach you more how to use the form.
+ </P
+><P
+> If you click the hyperlink on the <A
+HREF="http://bugzilla.mozilla.org/describecomponents.cgi"
+TARGET="_top"
+>Component</A
+> box of the Query page, you will be presented a form that will describe what all the components are.
+ </P
+><P
+> Possibly the most powerful feature of the Query page is the
+ <A
+HREF="http://bugzilla.mozilla.org/booleanchart.html"
+TARGET="_top"
+>Boolean Chart</A
+> section. It's a bit confusing to use the first time, but can provide unparalleled flexibility in your queries, allowing you to build extremely powerful requests.
+ </P
+><P
+> Finally, you can build some nifty <A
+HREF="http://bugzilla.mozilla.org/reports.cgi"
+TARGET="_top"
+>Reports</A
+> using the "Bug Reports" link near the bottom of the query page, and also available via the "Reports" link at the footer of each page.
+ </P
+></DIV
+></DIV
></DIV
><DIV
CLASS="SECTION"
-><HR><H3
+><HR><H1
CLASS="SECTION"
><A
-NAME="AEN410"
->2.1.2.17. The Whining Cron (Optional)</A
-></H3
-><P
-> By now you've got a fully functional bugzilla, but what good are bugs
- if they're not annoying? To help make those bugs more annoying you can
- set up bugzilla's automatic whining system. This can be done by adding
- the following command as a daily crontab entry (for help on that see that
- crontab man page):
- <P
-></P
+NAME="INIT4ME"
+>2.4. Where can I find my user preferences?</A
+></H1
><TABLE
BORDER="0"
-><TBODY
+WIDTH="100%"
+CELLSPACING="0"
+CELLPADDING="0"
+CLASS="EPIGRAPH"
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <B
-CLASS="COMMAND"
->cd <your-bugzilla-directory> ; ./whineatnews.pl</B
->
- </TT
->
- </TD
+WIDTH="45%"
+> </TD
+><TD
+WIDTH="45%"
+ALIGN="LEFT"
+VALIGN="TOP"
+><I
+><P
+><I
+>Indiana, it feels like we walking on fortune cookies!</I
+></P
+><P
+><I
+>These ain't fortune cookies, kid...</I
+></P
+></I
+></TD
></TR
-></TBODY
></TABLE
><P
-></P
->
- </P
+> Customized User Preferences offer tremendous versatility to your
+ individual Bugzilla experience. Let's plunge into what you can
+ do! The first step is to click the "Edit prefs" link at the
+ footer of each page once you have logged in to <A
+HREF="http://landfill.tequilarista.org/bugzilla-tip/query.cgi?GoAheadAndLogIn=1"
+TARGET="_top"
+> Landfill</A
+>.
+ </P
+><DIV
+CLASS="SECTION"
+><HR><H2
+CLASS="SECTION"
+><A
+NAME="ACCOUNTSETTINGS"
+>2.4.1. Account Settings</A
+></H2
+><P
+> On this page, you can change your basic Account Settings,
+ including your password and full name. For security reasons,
+ in order to change anything on this page you must type your
+ <EM
+>current</EM
+> password into the <SPAN
+CLASS="QUOTE"
+>"Old
+ Password"</SPAN
+> field. If you wish to change your
+ password, type the new password you want into the <SPAN
+CLASS="QUOTE"
+>"New
+ Password"</SPAN
+> field and again into the <SPAN
+CLASS="QUOTE"
+>"Re-enter
+ new password"</SPAN
+> field to ensure you typed your new
+ password correctly. Select the <SPAN
+CLASS="QUOTE"
+>"Submit"</SPAN
+> button
+ and you are done.
+ </P
></DIV
><DIV
CLASS="SECTION"
-><HR><H3
+><HR><H2
+CLASS="SECTION"
+><A
+NAME="EMAILSETTINGS"
+>2.4.2. Email Settings</A
+></H2
+><DIV
+CLASS="SECTION"
+><H3
CLASS="SECTION"
><A
-NAME="AEN417"
->2.1.2.18. Bug Graphs (Optional)</A
+NAME="NOTIFICATION"
+>2.4.2.1. Email Notification</A
></H3
><P
-> As long as you installed the GD and Graph::Base Perl modules you might
- as well turn on the nifty bugzilla bug reporting graphs.
+> Here you can reduce or increase the amount of email sent you
+ from Bugzilla. Although this is referred to as
+ <SPAN
+CLASS="QUOTE"
+>"Advanced Email Filtering Options"</SPAN
+>, they are,
+ in fact, the standard email filter set. All of them are
+ self-explanatory, but you can use the filters in interesting
+ ways. For instance, some people (notably Quality Assurance
+ personnel) often only care to receive updates regarding a
+ bug when the bug changes state, so they can track bugs on
+ their flow charts and know when it is time to pull the bug
+ onto a quality assurance platform for inspection. Other
+ people set up email gateways to
+ <A
+HREF="#BONSAI"
+>Bonsai, the Mozilla automated CVS management system</A
+> or <A
+HREF="#TINDERBOX"
+>Tinderbox, the Mozilla automated build management system</A
+>, and
+ restrict which types of Bugzilla information are fed to
+ these systems..
</P
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H3
+CLASS="SECTION"
+><A
+NAME="NEWEMAILTECH"
+>2.4.2.2. New Email Technology</A
+></H3
+><DIV
+CLASS="NOTE"
><P
-> Add a cron entry like this to run collectstats daily at 5 after midnight:
- <P
></P
><TABLE
+CLASS="NOTE"
+WIDTH="100%"
BORDER="0"
-><TBODY
><TR
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->bash#</TT
->
- <B
-CLASS="COMMAND"
->crontab -e</B
->
- </TT
->
- </TD
-></TR
-><TR
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> 5 0 * * * cd <your-bugzilla-directory> ; ./collectstats.pl
- </TT
->
- </TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> This option may not be available in all Bugzilla
+ installations, depending upon the preferences of the
+ systems administrator responsible for the setup of your
+ Bugzilla. However, if you really want this functionality,
+ ask her to "enable newemailtech in Params" and "make it
+ the default for all new users", referring her to the
+ Administration section of this Guide.
+ </P
+></TD
></TR
-></TBODY
></TABLE
+></DIV
><P
-></P
->
+> Disregard the warnings about "experimental and bleeding
+ edge"; the code to handle email in a cleaner manner than
+ that historically used for Bugzilla is quite robust and
+ well-tested now.
</P
><P
-> After two days have passed you'll be able to view bug graphs from the
- Bug Reports page.
+> I recommend you enable the option, "Click here to sign up
+ (and risk any bugs)". Your email-box will thank you for it.
+ The fundamental shift in "newemailtech" is away from
+ standard UNIX "diff" output, which is quite ugly, to a
+ prettier, better laid-out email.
</P
></DIV
><DIV
@@ -2776,2768 +3146,5648 @@ CLASS="SECTION"
><HR><H3
CLASS="SECTION"
><A
-NAME="AEN429"
->2.1.2.19. Securing MySQL</A
+NAME="WATCHSETTINGS"
+>2.4.2.3. "Watching" Users</A
></H3
+><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 option may not be available in all Bugzilla
+ installations, depending upon the preferences of the
+ systems administrator responsible for the setup of your
+ Bugzilla. However, if you really want this functionality,
+ ask her to "enable watchers in Params".
+ </P
+></TD
+></TR
+></TABLE
+></DIV
><P
-> If you followed the README for setting up your "bugs" and "root" user in
- MySQL, much of this should not apply to you. If you are upgrading
- an existing installation of Bugzilla, you should pay close attention
- to this section.
+> By entering user email names into the "Users to watch" text
+ entry box, delineated by commas, you can watch bugs of other
+ users. This powerful functionality enables seamless
+ transitions as developers change projects, managers wish to
+ get in touch with the issues faced by their direct reports,
+ or users go on vacation. If any of these three situations
+ apply to you, you will undoubtedly find this feature quite
+ convenient.
</P
+></DIV
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H2
+CLASS="SECTION"
+><A
+NAME="FOOTERSETTINGS"
+>2.4.3. Page Footer</A
+></H2
+><DIV
+CLASS="NOTE"
><P
-> Most MySQL installs have "interesting" default security parameters:
- <P
></P
><TABLE
+CLASS="NOTE"
+WIDTH="100%"
BORDER="0"
-><TBODY
><TR
><TD
->mysqld defaults to running as root</TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> By default, this page is quite barren. However, go explore
+ the Query Page some more; you will find that you can store
+ numerous queries on the server, so if you regularly run a
+ particular query it is just a drop-down menu away. On this
+ page of Preferences, if you have many stored queries you can
+ elect to have them always one-click away!
+ </P
+></TD
></TR
+></TABLE
+></DIV
+><P
+> If you have many stored queries on the server, here you will
+ find individual drop-downs for each stored query. Each
+ drop-down gives you the option of that query appearing on the
+ footer of every page in Bugzilla! This gives you powerful
+ one-click access to any complex searches you may set up, and
+ is an excellent way to impress your boss...
+ </P
+><DIV
+CLASS="TIP"
+><P
+></P
+><TABLE
+CLASS="TIP"
+WIDTH="100%"
+BORDER="0"
><TR
><TD
->it defaults to allowing external network connections</TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/tip.gif"
+HSPACE="5"
+ALT="Tip"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>By default, the "My Bugs" link appears at the bottom of
+ each page. However, this query gives you both the bugs you
+ have reported, as well as those you are assigned. One of
+ the most common uses for this page is to remove the "My
+ Bugs" link, replacing it with two other queries, commonly
+ called "My Bug Reports" and "My Bugs" (but only referencing
+ bugs assigned to you). This allows you to distinguish those
+ bugs you have reported from those you are assigned. I
+ commonly set up complex Boolean queries in the Query page
+ and link them to my footer in this page. When they are
+ significantly complex, a one-click reference can save hours
+ of work.</P
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H2
+CLASS="SECTION"
+><A
+NAME="PERMISSIONSETTINGS"
+>2.4.4. Permissions</A
+></H2
+><P
+> This is a purely informative page which outlines your current
+ permissions on this installation of Bugzilla. If you have
+ permissions to grant certain permissions to other users, the
+ "other users" link appears on this page as well as the footer.
+ For more information regarding user administration, please
+ consult the Administration section of this Guide.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H1
+CLASS="SECTION"
+><A
+NAME="USINGBZ-CONC"
+>2.5. Using Bugzilla-Conclusion</A
+></H1
+><P
+> Thank you for reading through this portion of the Bugzilla
+ Guide. I anticipate it may not yet meet the needs of all
+ readers. If you have additional comments or corrections to
+ make, please submit your contributions to the <A
+HREF="mailto://mozilla-webtools@mozilla.org"
+TARGET="_top"
+>mozilla-webtools</A
+> mailing list/newsgroup. The mailing list is mirrored to the netscape.public.mozilla.webtools newsgroup, and the newsgroup is mirrored to mozilla-webtools@mozilla.org
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="INSTALLATION"
+>Chapter 3. Installation</A
+></H1
+><P
+> These installation instructions are presented assuming you are
+ installing on a UNIX or completely POSIX-compliant system. If
+ you are installing on Microsoft Windows or another oddball
+ operating system, please consult the appropriate sections in
+ this installation guide for notes on how to be successful.
+ </P
+><DIV
+CLASS="SECTION"
+><HR><H1
+CLASS="SECTION"
+><A
+NAME="ERRATA"
+>3.1. ERRATA</A
+></H1
+><P
+>Here are some miscellaneous notes about possible issues you
+ main run into when you begin your Bugzilla installation.
+ Reference platforms for Bugzilla installation are Redhat Linux
+ 7.2, Linux-Mandrake 8.0, and Solaris 8.</P
+><P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+> If you are installing Bugzilla on S.u.S.e. Linux, or some
+ other distributions with <SPAN
+CLASS="QUOTE"
+>"paranoid"</SPAN
+> security
+ options, it is possible that the checksetup.pl script may fail
+ with the error: <SPAN
+CLASS="ERRORNAME"
+>cannot chdir(/var/spool/mqueue):
+ Permission denied</SPAN
+> This is because your
+ <TT
+CLASS="FILENAME"
+>/var/spool/mqueue</TT
+> directory has a mode of
+ <SPAN
+CLASS="QUOTE"
+>"drwx------"</SPAN
+>. Type <B
+CLASS="COMMAND"
+>chmod 755
+ <TT
+CLASS="FILENAME"
+>/var/spool/mqueue</TT
+></B
+> as root to
+ fix this problem.
+ </TD
></TR
><TR
><TD
->it has a known port number, and is easy to detect</TD
+> Bugzilla may be installed on Macintosh OS X (10), which is a
+ unix-based (BSD) operating system. Everything required for
+ Bugzilla on OS X will install cleanly, but the optional GD
+ perl module which is used for bug charting requires some
+ additional setup for installation. Please see the Mac OS X
+ installation section below for details
+ </TD
></TR
><TR
><TD
->it defaults to no passwords whatsoever</TD
+> Release Notes for Bugzilla 2.14 are available at
+ <TT
+CLASS="FILENAME"
+>docs/rel_notes.txt</TT
+> in your Bugzilla
+ source distribution.
+ </TD
></TR
><TR
><TD
->it defaults to allowing "File_Priv"</TD
+> The preferred documentation for Bugzilla is available in
+ docs/, with a variety of document types available. Please
+ refer to these documents when installing, configuring, and
+ maintaining your Bugzilla installation.
+ </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
+><DIV
+CLASS="WARNING"
><P
-> To see your permissions do:
- <P
></P
><TABLE
+CLASS="WARNING"
+WIDTH="100%"
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
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/warning.gif"
+HSPACE="5"
+ALT="Warning"></TD
><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->mysql></TT
->
- <B
-CLASS="COMMAND"
->select * from db;</B
->
- </TT
->
- </TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> Bugzilla is not a package where you can just plop it in a directory,
+ twiddle a few things, and you're off. Installing Bugzilla assumes you
+ know your variant of UNIX or Microsoft Windows well, are familiar with the
+ command line, and are comfortable compiling and installing a plethora
+ of third-party utilities. To install Bugzilla on Win32 requires
+ fair Perl proficiency, and if you use a webserver other than Apache you
+ should be intimately familiar with the security mechanisms and CGI
+ environment thereof.
+ </P
+></TD
></TR
-></TBODY
></TABLE
+></DIV
+><DIV
+CLASS="WARNING"
><P
></P
->
- </P
-><P
-> To fix the gaping holes:
- <P
-></P
><TABLE
+CLASS="WARNING"
+WIDTH="100%"
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
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/warning.gif"
+HSPACE="5"
+ALT="Warning"></TD
><TD
-> FLUSH PRIVILEGES;</TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> Bugzilla has not undergone a complete security review. Security holes
+ may exist in the code. Great care should be taken both in the installation
+ and usage of this software. Carefully consider the implications of
+ installing other network services with Bugzilla.
+ </P
+></TD
></TR
-></TBODY
></TABLE
+></DIV
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H1
+CLASS="SECTION"
+><A
+NAME="STEPBYSTEP"
+>3.2. Step-by-step Install</A
+></H1
+><DIV
+CLASS="SECTION"
+><H2
+CLASS="SECTION"
+><A
+NAME="AEN509"
+>3.2.1. Introduction</A
+></H2
><P
-></P
->
- </P
+> Installation of bugzilla is pretty straightforward, particularly if your
+ machine already has MySQL and the MySQL-related perl packages installed.
+ If those aren't installed yet, then that's the first order of business. The
+ other necessary ingredient is a web server set up to run cgi scripts.
+ While using Apache for your webserver is not required, it is recommended.
+ </P
><P
-> 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
+> Bugzilla has been successfully installed under Solaris, Linux,
+ and Win32. The peculiarities of installing on Win32 (Microsoft
+ Windows) are not included in this section of the Guide; please
+ check out the <A
+HREF="#WIN32"
+>Win32 Installation Notes</A
+> for further advice
+ on getting Bugzilla to work on Microsoft Windows.
+ </P
><P
-></P
->
- </P
+> The Bugzilla Guide is contained in the "docs/" folder in your
+ Bugzilla distribution. It is available in plain text
+ (docs/txt), HTML (docs/html), or SGML source (docs/sgml).
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H2
+CLASS="SECTION"
+><A
+NAME="AEN515"
+>3.2.2. Installing the Prerequisites</A
+></H2
+><DIV
+CLASS="NOTE"
><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
+CLASS="NOTE"
+WIDTH="100%"
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
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
><TD
->FLUSH PRIVILEGES;</TD
-></TR
-></TBODY
-></TABLE
+ALIGN="LEFT"
+VALIGN="TOP"
><P
+>If you want to skip these manual installation steps for
+ the CPAN dependencies listed below, and are running the very
+ most recent version of Perl and MySQL (both the executables
+ and development libraries) on your system, check out
+ Bundle::Bugzilla in <A
+HREF="#BUNDLEBUGZILLA"
+>Using Bundle::Bugzilla instead of manually installing Perl modules</A
></P
->
- </P
+></TD
+></TR
+></TABLE
+></DIV
><P
-> Consider also:
- <P
+> The software packages necessary for the proper running of bugzilla are:
+ <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
+> MySQL database server and the mysql client (3.22.5 or greater)
+ </P
></LI
><LI
><P
-> using the --user= option to mysqld to run it as an unprivileged
- user.
- </P
+> Perl (5.004 or greater, 5.6.1 is recommended if you wish
+ to use Bundle::Bugzilla)
+ </P
></LI
><LI
><P
-> starting MySQL in a chroot jail
- </P
+> DBI Perl module
+ </P
></LI
><LI
><P
-> running the httpd in a "chrooted" jail
- </P
+> Data::Dumper Perl module
+ </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
+> Bundle::Mysql Perl module collection
+ </P
></LI
><LI
><P
-> running MySQL on a separate untrusted machine
- </P
+> TimeDate Perl module collection
+ </P
></LI
><LI
><P
-> making backups ;-)
- </P
+> GD perl module (1.8.3) (optional, for bug charting)
+ </P
+></LI
+><LI
+><P
+> Chart::Base Perl module (0.99c) (optional, for bug charting)
+ </P
+></LI
+><LI
+><P
+> DB_File Perl module (optional, for bug charting)
+ </P
+></LI
+><LI
+><P
+> The web server of your choice. Apache is recommended.
+ </P
+></LI
+><LI
+><P
+> MIME::Parser Perl module (optional, for contrib/bug_email.pl interface)
+ </P
></LI
></OL
>
- </P
-></DIV
-><DIV
-CLASS="SECTION"
-><HR><H3
-CLASS="SECTION"
-><A
-NAME="AEN495"
->2.1.2.20. Installation General Notes</A
-></H3
-><DIV
-CLASS="SECTION"
-><H4
-CLASS="SECTION"
-><A
-NAME="AEN497"
->2.1.2.20.1. Modifying Your Running System</A
-></H4
-><P
-> Bugzilla optimizes database lookups by storing all relatively static
- information in the versioncache file, located in the data/ subdirectory
- under your installation directory (we said before it needs to be writable,
- right?!)
- </P
+
+ <DIV
+CLASS="WARNING"
><P
-> If you make a change to the structural data in your database (the
- versions table for example), or to the "constants" encoded in
- defparams.pl, you will need to remove the cached content from the data
- directory (by doing a "rm data/versioncache"), or your changes won't show
- up!
- </P
+></P
+><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
-> That file gets automatically regenerated whenever it's more than an
- hour old, so Bugzilla will eventually notice your changes by itself, but
- generally you want it to notice right away, so that you can test things.
+> It is a good idea, while installing Bugzilla, to ensure it
+ is not <EM
+>accessible</EM
+> by other machines
+ on the Internet. Your machine may be vulnerable to attacks
+ while you are installing. In other words, ensure there is
+ some kind of firewall between you and the rest of the
+ Internet. Many installation steps require an active
+ Internet connection to complete, but you must take care to
+ ensure that at no point is your machine vulnerable to an
+ attack.
</P
+></TD
+></TR
+></TABLE
+></DIV
+>
+ <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
+>Linux-Mandrake 8.0, the author's test system, includes
+ every required and optional library for Bugzilla. The
+ easiest way to install them is by using the
+ <TT
+CLASS="FILENAME"
+>urpmi</TT
+> utility. If you follow these
+ commands, you should have everything you need for
+ Bugzilla, and <TT
+CLASS="FILENAME"
+>checksetup.pl</TT
+> should
+ not complain about any missing libraries. You may already
+ have some of these installed.</P
+><P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+><TT
+CLASS="PROMPT"
+>bash#</TT
+><B
+CLASS="COMMAND"
+> urpmi
+ perl-mysql</B
+></TD
+></TR
+><TR
+><TD
+><TT
+CLASS="PROMPT"
+>bash#</TT
+><B
+CLASS="COMMAND"
+> urpmi
+ perl-chart</B
+></TD
+></TR
+><TR
+><TD
+><TT
+CLASS="PROMPT"
+>bash#</TT
+><B
+CLASS="COMMAND"
+> urpmi
+ perl-gd</B
+></TD
+></TR
+><TR
+><TD
+><TT
+CLASS="PROMPT"
+>bash#</TT
+><B
+CLASS="COMMAND"
+> urpmi
+ perl-MailTools</B
+> (for Bugzilla email
+ integration)</TD
+></TR
+><TR
+><TD
+><TT
+CLASS="PROMPT"
+>bash#</TT
+><B
+CLASS="COMMAND"
+> urpmi
+ apache-modules</B
+></TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+></TD
+></TR
+></TABLE
+></DIV
+>
+
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H2
+CLASS="SECTION"
+><A
+NAME="INSTALL-MYSQL"
+>3.2.3. Installing MySQL Database</A
+></H2
+><P
+> Visit MySQL homepage at <A
+HREF="http://www.mysql.com"
+TARGET="_top"
+>www.mysql.com</A
+> and grab the latest stable release of the server. Many of the binary versions of MySQL store their data files in <TT
+CLASS="FILENAME"
+>/var</TT
+> which is often part of a smaller root partition. If you decide to build from sources you can easily set the dataDir as an option to <TT
+CLASS="FILENAME"
+>configure</TT
+>.
+ </P
+><P
+> If you install from source or non-package (RPM, deb, etc.)
+ binaries you need to add
+ <I
+CLASS="FIRSTTERM"
+>mysqld</I
+> to your
+ init scripts so the server daemon will come back up whenever
+ your machine reboots. Further discussion of UNIX init
+ sequences are beyond the scope of this guide.
+ <DIV
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>You should have your init script start
+ <I
+CLASS="GLOSSTERM"
+>mysqld</I
+> with the ability to accept
+ large packets. By default, <TT
+CLASS="FILENAME"
+>mysqld</TT
+>
+ only accepts packets up to 64K long. This limits the size
+ of attachments you may put on bugs. If you add <TT
+CLASS="OPTION"
+>-O
+ max_allowed_packet=1M</TT
+> to the command that starts
+ <TT
+CLASS="FILENAME"
+>mysqld</TT
+> (or
+ <TT
+CLASS="FILENAME"
+>safe_mysqld</TT
+>), then you will be able
+ to have attachments up to about 1 megabyte.</P
+></TD
+></TR
+></TABLE
+></DIV
+>
+
+ </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 plan on running Bugzilla and MySQL on the same
+ machine, consider using the <TT
+CLASS="OPTION"
+>--skip-networking</TT
+>
+ option in the init script. This enhances security by
+ preventing network access to MySQL.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H2
+CLASS="SECTION"
+><A
+NAME="INSTALL-PERL"
+>3.2.4. Perl (5.004 or greater)</A
+></H2
+><P
+> Any machine that doesn't have perl on it is a sad machine
+ indeed. Perl for *nix systems can be gotten in source form
+ from http://www.perl.com. Although Bugzilla runs with most
+ post-5.004 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.
+ </P
+><P
+> Perl is now a far cry from the the single compiler/interpreter
+ binary it once was. It includes a great many required modules
+ and quite a few other support files. If you're not up to or
+ not inclined to build perl from source, you'll want to install
+ it on your machine using some sort of packaging system (be it
+ RPM, deb, or what have you) to ensure a sane install. In the
+ subsequent sections you'll be installing quite a few perl
+ modules; this can be quite ornery if your perl installation
+ isn't up to snuff.
+ </P
+><DIV
+CLASS="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
+>Many people complain that Perl modules will not install
+ for them. Most times, the error messages complain that they
+ are missing a file in <SPAN
+CLASS="QUOTE"
+>"@INC"</SPAN
+>. Virtually every
+ time, this is due to permissions being set too restrictively
+ for you to compile Perl modules or not having the necessary
+ Perl development libraries installed on your system..
+ Consult your local UNIX systems administrator for help
+ solving these permissions issues; if you
+ <EM
+>are</EM
+> the local UNIX sysadmin, please
+ consult the newsgroup/mailing list for further assistance or
+ hire someone to help you out.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+><DIV
+CLASS="TIP"
+><A
+NAME="BUNDLEBUGZILLA"
+></A
+><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
+> You can skip the following Perl module installation steps by
+ installing <SPAN
+CLASS="PRODUCTNAME"
+>Bundle::Bugzilla</SPAN
+> from
+ <A
+HREF="#GLOSS_CPAN"
+><I
+CLASS="GLOSSTERM"
+>CPAN</I
+></A
+>, which
+ includes them. All Perl module installation steps require
+ you have an active Internet connection. If you wish to use
+ Bundle::Bugzilla, however, you must be using the latest
+ version of Perl (at this writing, version 5.6.1)
+ </P
+><P
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>bash#</TT
+> <B
+CLASS="COMMAND"
+>perl -MCPAN
+ -e 'install "Bundle::Bugzilla"'</B
+>
+ </TT
+>
+ </P
+><P
+> Bundle::Bugzilla doesn't include GD, Chart::Base, or
+ MIME::Parser, which are not essential to a basic Bugzilla
+ install. If installing this bundle fails, you should
+ install each module individually to isolate the problem.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H2
+CLASS="SECTION"
+><A
+NAME="AEN602"
+>3.2.5. DBI Perl Module</A
+></H2
+><P
+> The DBI module is a generic Perl module used by other database related
+ Perl modules. For our purposes it's required by the MySQL-related
+ modules. As long as your Perl installation was done correctly the
+ DBI module should be a breeze. It's a mixed Perl/C module, but Perl's
+ MakeMaker system simplifies the C compilation greatly.
+ </P
+><P
+> Like almost all Perl modules DBI can be found on the Comprehensive Perl
+ Archive Network (CPAN) at http://www.cpan.org. The CPAN servers have a
+ real tendency to bog down, so please use mirrors. The current location
+ at the time of this writing can be found in <A
+HREF="#DOWNLOADLINKS"
+>Appendix B</A
+>.
+ </P
+><P
+> Quality, general Perl module installation instructions can be found on
+ the CPAN website, but the easy thing to do is to just use the CPAN shell
+ which does all the hard work for you.
+ </P
+><P
+> To use the CPAN shell to install DBI:
+ <DIV
+CLASS="INFORMALEXAMPLE"
+><A
+NAME="AEN609"
+></A
+><P
+></P
+><P
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>bash#</TT
+>
+ <B
+CLASS="COMMAND"
+>perl -MCPAN -e 'install "DBI"'</B
+>
+ </TT
+>
+ <DIV
+CLASS="NOTE"
+><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
+>Replace "DBI" with the name of whichever module you wish
+ to install, such as Data::Dumper, TimeDate, GD, etc.</P
+></TD
+></TR
+></TABLE
+></DIV
+>
+ </P
+><P
+></P
+></DIV
+>
+ To do it the hard way:
+ <DIV
+CLASS="INFORMALEXAMPLE"
+><A
+NAME="AEN616"
+></A
+><P
+></P
+><P
+> Untar the module tarball -- it should create its own directory
+ </P
+><P
+> CD to the directory just created, and enter the following commands:
+ <P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>bash#</TT
+>
+ <B
+CLASS="COMMAND"
+>perl Makefile.PL</B
+>
+ </TT
+>
+ </P
+></LI
+><LI
+><P
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>bash#</TT
+>
+ <B
+CLASS="COMMAND"
+>make</B
+>
+ </TT
+>
+ </P
+></LI
+><LI
+><P
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>bash#</TT
+>
+ <B
+CLASS="COMMAND"
+>make test</B
+>
+ </TT
+>
+ </P
+></LI
+><LI
+><P
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>bash#</TT
+>
+ <B
+CLASS="COMMAND"
+>make install</B
+>
+ </TT
+>
+ </P
+></LI
+></OL
+>
+ If everything went ok that should be all it takes. For the vast
+ majority of perl modules this is all that's required.
+ </P
+><P
+></P
+></DIV
+>
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H2
+CLASS="SECTION"
+><A
+NAME="AEN640"
+>3.2.6. Data::Dumper Perl Module</A
+></H2
+><P
+> The Data::Dumper module provides data structure persistence for Perl
+ (similar to Java's serialization). It comes with later sub-releases of
+ Perl 5.004, but a re-installation just to be sure it's available won't
+ hurt anything.
+ </P
+><P
+> Data::Dumper is used by the MySQL-related Perl modules. It
+ can be found on CPAN (see <A
+HREF="#DOWNLOADLINKS"
+>Appendix B</A
+>) and
+ can be
+ installed by following the same four step make sequence used
+ for the DBI module.
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H2
+CLASS="SECTION"
+><A
+NAME="AEN645"
+>3.2.7. MySQL related Perl Module Collection</A
+></H2
+><P
+> The Perl/MySQL interface requires a few mutually-dependent perl
+ modules. These modules are grouped together into the the
+ Msql-Mysql-modules package. This package can be found at CPAN.
+ After the archive file has been downloaded it should
+ be untarred.
+ </P
+><P
+> The MySQL modules are all built using one make file which is generated
+ by running:
+ <TT
+CLASS="PROMPT"
+>bash#</TT
+>
+ <B
+CLASS="COMMAND"
+>perl Makefile.pl</B
+>
+ </P
+><P
+> The MakeMaker process will ask you a few questions about the desired
+ compilation target and your MySQL installation. For many of the questions
+ the provided default will be adequate.
+ </P
+><P
+> When asked if your desired target is the MySQL or mSQL packages,
+ 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.
+ </P
+><P
+> A host of 'localhost' should be fine and a testing user of 'test' and
+ a null password should find itself with sufficient access to run tests
+ on the 'test' database which MySQL created upon installation. If 'make
+ test' and 'make install' go through without errors you should be ready
+ to go as far as database connectivity is concerned.
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H2
+CLASS="SECTION"
+><A
+NAME="AEN654"
+>3.2.8. TimeDate Perl Module Collection</A
+></H2
+><P
+> Many of the more common date/time/calendar related Perl
+ modules have been grouped into a bundle similar to the MySQL
+ modules bundle. This bundle is stored on the CPAN under the
+ name TimeDate (see link: <A
+HREF="#DOWNLOADLINKS"
+>Appendix B</A
+>). The
+ component module we're most interested in is the Date::Format
+ module, but installing all of them is probably a good idea
+ anyway. The standard Perl module installation instructions
+ should work perfectly for this simple package.
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H2
+CLASS="SECTION"
+><A
+NAME="AEN658"
+>3.2.9. GD Perl Module (1.8.3)</A
+></H2
+><P
+> The GD library was written by Thomas Boutell a long while
+ ago to programatically generate images in C. Since then it's
+ become the defacto standard for programatic image
+ construction. The Perl bindings to it found in the GD library
+ are used on millions of web pages to generate graphs on the
+ fly. That's what bugzilla will be using it for so you must
+ install it if you want any of the graphing to work.
+ </P
+><P
+> Actually bugzilla uses the Graph module which relies on GD
+ itself. Isn't that always the way with object-oriented
+ programming? At any rate, you can find the GD library on CPAN
+ in <A
+HREF="#DOWNLOADLINKS"
+>Appendix B</A
+>.
+ </P
+><DIV
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> The Perl GD library requires some other libraries that may
+ or may not be installed on your system, including
+ <TT
+CLASS="CLASSNAME"
+>libpng</TT
+> and
+ <TT
+CLASS="CLASSNAME"
+>libgd</TT
+>. The full requirements are
+ listed in the Perl GD library README. Just realize that if
+ compiling GD fails, it's probably because you're missing a
+ required library.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H2
+CLASS="SECTION"
+><A
+NAME="AEN667"
+>3.2.10. Chart::Base Perl Module (0.99c)</A
+></H2
+><P
+> The Chart module provides bugzilla with on-the-fly charting
+ abilities. It can be installed in the usual fashion after it
+ has been fetched from CPAN where it is found as the
+ Chart-x.x... tarball, linked in <A
+HREF="#DOWNLOADLINKS"
+>Appendix B</A
+>. Note that
+ as with the GD perl module, only the version listed above, or
+ newer, will work. Earlier versions used GIF's, which are no
+ longer supported by the latest versions of GD.
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H2
+CLASS="SECTION"
+><A
+NAME="AEN671"
+>3.2.11. DB_File Perl Module</A
+></H2
+><P
+> DB_File is a module which allows Perl programs to make use
+ of the facilities provided by Berkeley DB version 1.x. This
+ module is required by collectstats.pl which is used for bug
+ charting. If you plan to make use of bug charting, you must
+ install this module.
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H2
+CLASS="SECTION"
+><A
+NAME="AEN674"
+>3.2.12. HTTP Server</A
+></H2
+><P
+> You have a freedom of choice here - Apache, Netscape or any
+ other server on UNIX would do. You can easily run the web
+ server on a different machine than MySQL, but need to adjust
+ the MySQL <SPAN
+CLASS="QUOTE"
+>"bugs"</SPAN
+> user permissions accordingly.
+ <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
+>I strongly recommend Apache as the web server to use.
+ The Bugzilla Guide installation instructions, in general,
+ assume you are using Apache. As more users use different
+ webservers and send me information on the peculiarities of
+ installing using their favorite webserver, I will provide
+ notes for them.</P
+></TD
+></TR
+></TABLE
+></DIV
+>
+ </P
+><P
+> You'll want to make sure that your web server will run any
+ file with the .cgi extension as a cgi and not just display it.
+ If you're using apache that means uncommenting the following
+ line in the srm.conf file:
+ <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>AddHandler cgi-script .cgi
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+ </P
+><P
+> With apache you'll also want to make sure that within the
+ access.conf file the line:
+ <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>Options ExecCGI</PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+ is in the stanza that covers the directories into which
+ you intend to put the bugzilla .html and .cgi files.
+ </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
+> Users of newer versions of Apache will generally find both
+ of the above lines will be in the httpd.conf file, rather
+ than srm.conf or access.conf.
+ </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
+> There are important files and directories that should not
+ be a served by the HTTP server. These are most files in the
+ <SPAN
+CLASS="QUOTE"
+>"data"</SPAN
+> and <SPAN
+CLASS="QUOTE"
+>"shadow"</SPAN
+> directories
+ and the <SPAN
+CLASS="QUOTE"
+>"localconfig"</SPAN
+> file. You should
+ configure your HTTP server to not serve content from these
+ files. Failure to do so will expose critical passwords and
+ other data. Please see <A
+HREF="#HTACCESS"
+>.htaccess files and security</A
+> for details
+ on how to do this for Apache. I appreciate notes on how to
+ get this same functionality using other webservers.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H2
+CLASS="SECTION"
+><A
+NAME="AEN692"
+>3.2.13. Installing the Bugzilla Files</A
+></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 <SPAN
+CLASS="QUOTE"
+>"nobody"</SPAN
+>). You may decide to put the
+ files off of the main web space for your web server or perhaps
+ off of <TT
+CLASS="FILENAME"
+>/usr/local</TT
+> with a symbolic link in
+ the web space that points to the Bugzilla directory. At any
+ rate, just dump all the files in the same place, and make sure
+ you can access the files in that directory through your web
+ server.
+ </P
+><DIV
+CLASS="TIP"
+><P
+></P
+><TABLE
+CLASS="TIP"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/tip.gif"
+HSPACE="5"
+ALT="Tip"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> If you symlink the bugzilla directory into your Apache's
+ HTML heirarchy, you may receive
+ <SPAN
+CLASS="ERRORNAME"
+>Forbidden</SPAN
+> errors unless you add the
+ <SPAN
+CLASS="QUOTE"
+>"FollowSymLinks"</SPAN
+> directive to the
+ <Directory> entry for the HTML root.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+><P
+> Once all the files are in a web accessible directory, make
+ that directory writable by your webserver's user. This is a
+ temporary step until you run the post-install
+ <TT
+CLASS="FILENAME"
+>checksetup.pl</TT
+> script, which locks down your
+ installation.
+ </P
+><P
+> Lastly, you'll need to set up a symbolic link to
+ <TT
+CLASS="FILENAME"
+>/usr/bonsaitools/bin/perl</TT
+> for the correct
+ location of your perl executable (probably
+ <TT
+CLASS="FILENAME"
+>/usr/bin/perl</TT
+>). Otherwise you must hack
+ all the .cgi files to change where they look for perl, or use
+ <A
+HREF="#SETPERL"
+>The setperl.csh Utility</A
+>, found in
+ <A
+HREF="#PATCHES"
+>Useful Patches and Utilities for Bugzilla</A
+>. I suggest using the symlink
+ approach for future release compatability.
+ <DIV
+CLASS="EXAMPLE"
+><A
+NAME="AEN708"
+></A
+><P
+><B
+>Example 3-1. Setting up bonsaitools symlink</B
+></P
+><P
+> Here's how you set up the Perl symlink on Linux to make
+ Bugzilla work. Your mileage may vary. For some UNIX
+ operating systems, you probably need to subsitute
+ <SPAN
+CLASS="QUOTE"
+>"/usr/local/bin/perl"</SPAN
+> for
+ <SPAN
+CLASS="QUOTE"
+>"/usr/bin/perl"</SPAN
+> below; if on certain other
+ UNIX systems, Perl may live in weird places like
+ <SPAN
+CLASS="QUOTE"
+>"/opt/perl"</SPAN
+>. As root, run these commands:
+ <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>bash# mkdir /usr/bonsaitools
+bash# mkdir /usr/bonsaitools/bin
+bash# ln -s /usr/bin/perl /usr/bosaitools/bin/perl
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+ </P
+><P
+> Alternately, you can simply run this perl one-liner to
+ change your path to perl in all the files in your Bugzilla
+ installation:
+ <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>perl -pi -e 's@#!/usr/bonsaitools/bin/perl@#!/usr/bin/perl@' *cgi *pl Bug.pm
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+ Change the second path to perl to match your installation.
+ </P
+></DIV
+>
+ <DIV
+CLASS="TIP"
+><P
+></P
+><TABLE
+CLASS="TIP"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/tip.gif"
+HSPACE="5"
+ALT="Tip"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> If you don't have root access to set this symlink up,
+ check out the
+ <A
+HREF="#SETPERL"
+>The setperl.csh Utility</A
+>, listed in <A
+HREF="#PATCHES"
+>Useful Patches and Utilities for Bugzilla</A
+>. It will change the path to perl in all your Bugzilla files for you.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+>
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H2
+CLASS="SECTION"
+><A
+NAME="AEN721"
+>3.2.14. Setting Up the MySQL Database</A
+></H2
+><P
+> After you've gotten all the software installed and working you're ready
+ to start preparing the database for its life as a the back end to a high
+ quality bug tracker.
+ </P
+><P
+> First, you'll want to fix MySQL permissions to allow access
+ from Bugzilla. For the purpose of this Installation section,
+ the Bugzilla username will be <SPAN
+CLASS="QUOTE"
+>"bugs"</SPAN
+>, and will
+ have minimal permissions.
+
+ <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
+> Bugzilla has not undergone a thorough security audit. It
+ may be possible for a system cracker to somehow trick
+ Bugzilla into executing a command such as <B
+CLASS="COMMAND"
+>DROP
+ DATABASE mysql</B
+>.
+ </P
+><P
+>That would be bad.</P
+></TD
+></TR
+></TABLE
+></DIV
+>
+ </P
+><P
+> Give the MySQL root user a password. MySQL passwords are
+ limited to 16 characters.
+ <P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>bash#</TT
+> <B
+CLASS="COMMAND"
+>mysql
+ -u root mysql</B
+> </TT
+>
+ </TD
+></TR
+><TR
+><TD
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>mysql></TT
+> <B
+CLASS="COMMAND"
+> UPDATE user SET Password=PASSWORD ('new_password')
+ WHERE user='root'; </B
+> </TT
+>
+ </TD
+></TR
+><TR
+><TD
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>mysql></TT
+> <B
+CLASS="COMMAND"
+>FLUSH
+ PRIVILEGES;</B
+> </TT
+>
+ </TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+> From this point on, if you need to access
+ MySQL as the MySQL root user, you will need to use
+ <B
+CLASS="COMMAND"
+>mysql -u root -p</B
+> and enter your
+ new_password. Remember that MySQL user names have nothing to
+ do with Unix user names (login names).
+ </P
+><P
+> Next, we create the <SPAN
+CLASS="QUOTE"
+>"bugs"</SPAN
+> user, and grant
+ sufficient permissions for checksetup.pl, which we'll use
+ later, to work its magic. This also restricts the
+ <SPAN
+CLASS="QUOTE"
+>"bugs"</SPAN
+> user to operations within a database
+ called <SPAN
+CLASS="QUOTE"
+>"bugs"</SPAN
+>, and only allows the account to
+ connect from <SPAN
+CLASS="QUOTE"
+>"localhost"</SPAN
+>. Modify it to reflect
+ your setup if you will be connecting from another machine or
+ as a different user.
+ </P
+><P
+> Remember to set bugs_password to some unique password.
+ <P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>mysql></TT
+>
+ <B
+CLASS="COMMAND"
+>GRANT SELECT,INSERT,UPDATE,DELETE,INDEX,
+ ALTER,CREATE,DROP,REFERENCES
+ ON bugs.* TO bugs@localhost
+ IDENTIFIED BY 'bugs_password';</B
+>
+ </TT
+>
+ </TD
+></TR
+><TR
+><TD
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+> mysql>
+ </TT
+>
+ <B
+CLASS="COMMAND"
+> FLUSH PRIVILEGES;
+ </B
+>
+ </TT
+>
+ </TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+>
+ </P
+><P
+> Next, run the magic checksetup.pl script. (Many thanks to
+ Holger Schurig <holgerschurig@nikocity.de> for writing
+ this script!) It will make sure Bugzilla files and directories
+ have reasonable permissions, set up the
+ <TT
+CLASS="FILENAME"
+>data</TT
+> directory, and create all the MySQL
+ tables.
+ <P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>bash#</TT
+>
+ <B
+CLASS="COMMAND"
+>./checksetup.pl</B
+> </TT
+>
+ </TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+> The first time you run it, it will create a
+ file called <TT
+CLASS="FILENAME"
+>localconfig</TT
+>.
+ </P
></DIV
><DIV
CLASS="SECTION"
-><HR><H4
+><HR><H2
CLASS="SECTION"
><A
-NAME="AEN502"
->2.1.2.20.2. Upgrading From Previous Versions</A
-></H4
+NAME="AEN768"
+>3.2.15. Tweaking <TT
+CLASS="FILENAME"
+>localconfig</TT
+></A
+></H2
+><P
+> This file contains a variety of settings you may need to tweak including
+ how Bugzilla should connect to the MySQL database.
+ </P
+><P
+> The connection settings include:
+ <P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+> server's host: just use <SPAN
+CLASS="QUOTE"
+>"localhost"</SPAN
+> if the
+ MySQL server is local
+ </P
+></LI
+><LI
+><P
+> database name: <SPAN
+CLASS="QUOTE"
+>"bugs"</SPAN
+> if you're following
+ these directions
+ </P
+></LI
+><LI
><P
-> The developers of Bugzilla are constantly adding new tables, columns and
- fields. You'll get SQL errors if you just update the code. The strategy
- to update is to simply always run the checksetup.pl script whenever
- you upgrade your installation of Bugzilla. If you want to see what has
- changed, you can read the comments in that file, starting from the end.
- </P
-></DIV
-><DIV
-CLASS="SECTION"
-><HR><H4
-CLASS="SECTION"
-><A
-NAME="AEN505"
->2.1.2.20.3. UNIX Installation Instructions History</A
-></H4
+> MySQL username: <SPAN
+CLASS="QUOTE"
+>"bugs"</SPAN
+> if you're following
+ these directions
+ </P
+></LI
+><LI
><P
-> This document was originally adapted from the Bonsai installation
- instructions by Terry Weissman <terry@mozilla.org>.
- </P
+> Password for the <SPAN
+CLASS="QUOTE"
+>"bugs"</SPAN
+> MySQL account above
+ </P
+></LI
+></OL
+>
+ </P
><P
-> The February 25, 1999 re-write of this page was done by Ry4an Brase
- <ry4an@ry4an.org>, with some edits by Terry Weissman, Bryce Nesbitt,
- Martin Pool, & Dan Mosedale (But don't send bug reports to them!
- Report them using bugzilla, at http://bugzilla.mozilla.org/enter_bug.cgi ,
- project Webtools, component Bugzilla).
- </P
+> You should also install .htaccess files that the Apache
+ webserver will use to restrict access to Bugzilla data files.
+ See <A
+HREF="#HTACCESS"
+>.htaccess files and security</A
+>.
+ </P
><P
-> This document was heavily modified again Wednesday, March 07 2001 to
- reflect changes for Bugzilla 2.12 release by Matthew P. Barnson. The
- securing MySQL section should be changed to become standard procedure
- for Bugzilla installations.
- </P
+> Once you are happy with the settings, re-run
+ <TT
+CLASS="FILENAME"
+>checksetup.pl</TT
+>. On this second run, it will
+ create the database and an administrator account for which
+ you will be prompted to provide information.
+ </P
><P
-> Finally, the README in its entirety was marked up in SGML and included into
- the Guide on April 24, 2001.
- </P
+> When logged into an administrator account once Bugzilla is
+ running, if you go to the query page (off of the Bugzilla main
+ menu), you'll find an <SPAN
+CLASS="QUOTE"
+>"edit parameters"</SPAN
+> option
+ that is filled with editable treats.
+ </P
><P
-> Comments from people using this Guide for the first time are particularly welcome.
- </P
+> Should everything work, you will have a nearly empty Bugzilla
+ database and a newly-created <TT
+CLASS="FILENAME"
+>localconfig</TT
+>
+ file in your Bugzilla root directory.
+ </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
+> The second time you run checksetup.pl, you should become
+ the user your web server runs as, and that you ensure that
+ you set the <SPAN
+CLASS="QUOTE"
+>"webservergroup"</SPAN
+> parameter in localconfig to
+ match the web server's group name, if any. I believe,
+ for the next release of Bugzilla, this will be fixed so
+ that Bugzilla supports a <SPAN
+CLASS="QUOTE"
+>"webserveruser"</SPAN
+> parameter in
+ localconfig as well.
+ <DIV
+CLASS="EXAMPLE"
+><A
+NAME="AEN799"
+></A
+><P
+><B
+>Example 3-2. Running checksetup.pl as the web user</B
+></P
+><P
+> Assuming your web server runs as user "apache", and
+ Bugzilla is installed in "/usr/local/bugzilla", here's
+ one way to run checksetup.pl as the web server user.
+ As root, for the <EM
+>second run</EM
+> of
+ checksetup.pl, do this:
+ <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>
+bash# chown -R apache:apache /usr/local/bugzilla
+bash# su - apache
+bash# cd /usr/local/bugzilla
+bash# ./checksetup.pl
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+ </P
></DIV
+>
+ </P
+></TD
+></TR
+></TABLE
></DIV
+>
+ </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
+> The checksetup.pl script is designed so that you can run
+ it at any time without causing harm. You should run it
+ after any upgrade to Bugzilla.
+ </P
+></TD
+></TR
+></TABLE
></DIV
></DIV
><DIV
CLASS="SECTION"
-><HR><H1
+><HR><H2
CLASS="SECTION"
><A
-NAME="README.WINDOWS"
->2.2. Win32 (Win98+/NT/2K) Installation</A
-></H1
+NAME="AEN806"
+>3.2.16. Setting Up Maintainers Manually (Optional)</A
+></H2
><P
-> These directions have <EM
->not</EM
-> been extensively tested.
- We need testers! Please try these out and post any changes to the
- newsgroup.
- </P
+> If you want to add someone else to every group by hand, you
+ can do it by typing the appropriate MySQL commands. Run
+ <B
+CLASS="COMMAND"
+> mysql -u root -p bugs</B
+> You
+ may need different parameters, depending on your security
+ settings. Then:
+ <P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>mysql></TT
+> <B
+CLASS="COMMAND"
+>update
+ profiles set groupset=0x7fffffffffffffff where
+ login_name = 'XXX';</B
+> </TT
+> (yes, that's <EM
+>fifteen</EM
+><SPAN
+CLASS="QUOTE"
+>"f"</SPAN
+>'s.
+ </TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+> replacing XXX with the Bugzilla email address.
+ </P
+></DIV
><DIV
CLASS="SECTION"
><HR><H2
CLASS="SECTION"
><A
-NAME="NTVERIFIED"
->2.2.1. Win32 Installation: Step-by-step</A
+NAME="AEN817"
+>3.2.17. The Whining Cron (Optional)</A
></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 can set up bugzilla's automatic whining
+ system. This can be done by adding the following command as a
+ daily crontab entry (for help on that see that crontab man
+ page):
+ <P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <B
+CLASS="COMMAND"
+>cd
+ <your-bugzilla-directory> ;
+ ./whineatnews.pl</B
+> </TT
+>
+ </TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+>
+ </P
><DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
+CLASS="TIP"
><P
-><B
->Note: </B
-> You should be familiar with, and cross-reference, the UNIX README
- while performing your Win32 installation. Unfortunately, Win32
- directions are not yet as detailed as those for UNIX.
- </P
+></P
+><TABLE
+CLASS="TIP"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/tip.gif"
+HSPACE="5"
+ALT="Tip"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
><P
-> The <EM
->most critical</EM
-> difference for Win32 users is
- the lack of support for a crypt() function in MySQL for Windows. It does not
- have it! All ENCRYPT statements must be modified.
+> Depending on your system, crontab may have several manpages.
+ The following command should lead you to the most useful
+ page for this purpose:
+ <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+> man 5 crontab
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
+></DIV
></DIV
><DIV
-CLASS="PROCEDURE"
-><OL
-TYPE="1"
-><LI
+CLASS="SECTION"
+><HR><H2
+CLASS="SECTION"
+><A
+NAME="AEN827"
+>3.2.18. Bug Graphs (Optional)</A
+></H2
><P
-> Install <A
-HREF="http://www.apache.org/"
-TARGET="_top"
->Apache Web Server</A
+> As long as you installed the GD and Graph::Base Perl modules
+ you might as well turn on the nifty bugzilla bug reporting
+ graphs.
+ </P
+><P
+> Add a cron entry like this to run collectstats daily at 5
+ after midnight:
+ <P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>bash#</TT
+> <B
+CLASS="COMMAND"
+>crontab
+ -e</B
+> </TT
>
- for Windows.
- </P
-><DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
+ </TD
+></TR
+><TR
+><TD
+> <TT
+CLASS="COMPUTEROUTPUT"
+> 5 0 * * * cd
+ <your-bugzilla-directory> ; ./collectstats.pl
+ </TT
+>
+ </TD
+></TR
+></TBODY
+></TABLE
><P
-><B
->Note: </B
-> You may also use Internet Information Server or Personal Web
- Server for this purpose. However, setup is slightly more
- difficult. If ActivePerl doesn't seem to handle your file
- associations correctly (for .cgi and .pl files), please
- consult the FAQ, in the "Win32" section.
- </P
+></P
+>
+ </P
><P
-> If you are going to use IIS, if on Windows NT you must be updated
- to at least Service Pack 4.
- </P
-></BLOCKQUOTE
+> After two days have passed you'll be able to view bug graphs
+ from the Bug Reports page.
+ </P
></DIV
-></LI
-><LI
+><DIV
+CLASS="SECTION"
+><HR><H2
+CLASS="SECTION"
+><A
+NAME="AEN839"
+>3.2.19. Securing MySQL</A
+></H2
><P
-> Install <A
-HREF="http://www.activestate.com/"
-TARGET="_top"
->ActivePerl</A
->
- </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
-> Please also check the following links to fully understand the status
- of ActivePerl on Win32:
- <A
-HREF="http://language.perl.com/newdocs/pod/perlport.html"
-TARGET="_top"
-> Perl Porting</A
->, and
- <A
-HREF="http://ftp.univie.ac.at/packages/perl/ports/nt/FAQ/perlwin32faq5.html"
-TARGET="_top"
-> Hixie Click Here</A
+></P
>
- </P
-></LI
-><LI
+ </P
><P
-> Use ppm from your perl\bin directory to install the following packs: DBI,
- DBD-Mysql, TimeDate, Chart, Date-Calc, Date-Manip, and GD. You may need
- to extract them from .zip format using Winzip or other unzip program first.
- These additional ppm modules can be downloaded from ActiveState.
- </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
-> The syntax for ppm is:
- <TT
+> To see your permissions do:
+ <P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+> <TT
CLASS="COMPUTEROUTPUT"
> <TT
CLASS="PROMPT"
->C:> </TT
-><B
+>bash#</TT
+>
+ <B
CLASS="COMMAND"
->ppm install <module>.ppd</B
+>mysql -u root -p</B
>
</TT
>
- </P
-><P
-> You can find ActiveState ppm modules at
- <A
-HREF="http://www.activestate.com/PPMPackages/5.6plus/"
-TARGET="_top"
-> http://www.activestate.com/PPMPackages/5.6plus</A
->
- </P
-></LI
-><LI
-><P
-> Download and install the Windows GNU tools from
- <A
-HREF="http://www.cygwin.com/"
-TARGET="_top"
->www.cygwin.com</A
->.
- Make sure the GNU utilities are in your $PATH.
- </P
-></LI
-><LI
-><P
-> Install MySQL for NT.
- <DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
-><P
-><B
->Note: </B
-> Your configuration file for MySQL <EM
->must</EM
-> be named C:\MY.CNF.
- </P
-></BLOCKQUOTE
-></DIV
->
- </P
-></LI
-><LI
-><P
-> Setup MySQL
- </P
-><OL
-CLASS="SUBSTEPS"
-TYPE="a"
-><LI
-><P
-> <TT
+ </TD
+></TR
+><TR
+><TD
+> <TT
CLASS="COMPUTEROUTPUT"
-> <TT
+> <TT
CLASS="PROMPT"
->C:> </TT
+>mysql></TT
>
- <B
+ <B
CLASS="COMMAND"
->C:\mysql\bin\mysql -u root mysql</B
+>use mysql;</B
>
- </TT
+ </TT
>
- </P
-></LI
-><LI
-><P
-> <TT
+ </TD
+></TR
+><TR
+><TD
+> <TT
CLASS="COMPUTEROUTPUT"
-> <TT
+> <TT
CLASS="PROMPT"
>mysql></TT
>
- <B
+ <B
CLASS="COMMAND"
->DELETE FROM user WHERE Host='localhost' AND User='';</B
+>show tables;</B
>
- </TT
+ </TT
>
- </P
-></LI
-><LI
-><P
-> <TT
+ </TD
+></TR
+><TR
+><TD
+> <TT
CLASS="COMPUTEROUTPUT"
-> <TT
+> <TT
CLASS="PROMPT"
>mysql></TT
>
- <B
+ <B
CLASS="COMMAND"
->UPDATE user SET Password=PASSWORD ('new_password')
- WHERE user='root';</B
+>select * from user;</B
>
- </TT
+ </TT
>
- </P
-></LI
-><LI
-><P
-> <TT
+ </TD
+></TR
+><TR
+><TD
+> <TT
CLASS="COMPUTEROUTPUT"
-> <TT
+> <TT
CLASS="PROMPT"
>mysql></TT
>
- <B
+ <B
CLASS="COMMAND"
->GRANT SELECT, INSERT, UPDATE, DELETE,
- INDEX, ALTER, CREATE, DROP, REFERENCES
- ON bugs.* to bugs@localhost
- IDENTIFIED BY 'bugs_password';</B
+>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
>
- </TT
+ </P
+><P
+> Use .htaccess files with the Apache webserver to secure your
+ bugzilla install. See <A
+HREF="#HTACCESS"
+>.htaccess files and security</A
>
- </P
-></LI
+ </P
+><P
+> Consider also:
+ <P
+></P
+><OL
+TYPE="1"
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->mysql></TT
->
- <B
-CLASS="COMMAND"
->FLUSH PRIVILEGES;</B
->
- </TT
->
- </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
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->mysql></TT
->
- <B
-CLASS="COMMAND"
->create database bugs;</B
->
- </TT
->
- </P
+> using the --user= option to mysqld to run it as an unprivileged
+ user.
+ </P
></LI
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->mysql></TT
->
- <B
-CLASS="COMMAND"
->exit</B
->
- </TT
->
- </P
+> starting MySQL in a chroot jail
+ </P
></LI
><LI
><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->C:></TT
->
- <B
-CLASS="COMMAND"
->C:\mysql\bin\mysqladmin -u root -p reload</B
->
- </TT
->
- </P
+> running the httpd in a "chrooted" jail
+ </P
></LI
-></OL
+><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
-> Configure Bugzilla. For Win32, this involves editing "defparams.pl"
- and "localconfig" to taste. Running "checksetup.pl" should create
- localconfig for you. Note that getgrnam() doesn't work, and should be
- deleted. Change this line:
- "my $webservergid = getgrnam($my_webservergroup); "
- to
- "my $webservergid = $my_webservergroup; "
- </P
+> running MySQL on a separate untrusted machine
+ </P
></LI
><LI
-><DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
><P
-><B
->Note: </B
-> There are several alternatives to Sendmail that will work on Win32.
- The one mentioned here is a <EM
->suggestion</EM
->, not
- a requirement. Some other mail packages that can work include
- <A
-HREF="http://www.blat.net/"
-TARGET="_top"
->BLAT</A
->,
- <A
-HREF="http://www.geocel.com/windmail/"
-TARGET="_top"
->Windmail</A
->,
- <A
-HREF="http://www.dynamicstate.com/"
-TARGET="_top"
->Mercury Sendmail</A
->,
- and the CPAN Net::SMTP Perl module (available in .ppm).
- Every option requires some hacking of the Perl scripts for Bugzilla
- to make it work. The option here simply requires the least.
+> making backups ;-)
</P
-></BLOCKQUOTE
+></LI
+></OL
+>
+ </P
></DIV
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H1
+CLASS="SECTION"
+><A
+NAME="OSX"
+>3.3. Mac OS X Installation Notes</A
+></H1
><P
-> Download NTsendmail, available from<A
-HREF="http://www.ntsendmail.com/"
-TARGET="_top"
-> www.ntsendmail.com</A
->. In order for it to work, you must set up some
- new environment variables (detailed on the ntsendmail home page). Figuring
- out where to put those variables is left as an exercise for the reader.
- You must have a "real" mail server which allows you to relay off it
- in your $ENV{"NTsendmail"} (which you should probably place in globals.pl)
- </P
+> There are a lot of common libraries and utilities out there
+ that Apple did not include with Mac OS X, but which run
+ perfectly well on it. The GD library, which Bugzilla needs to
+ do bug graphs, is one of these.
+ </P
><P
-> Once downloaded and installed, modify all open(SENDMAIL) calls to open
- "| c:\ntsendmail\ntsendmail -t" instead of "|/usr/lib/sendmail -t".
- </P
-><DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
+> 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/>.
+ </P
><P
-><B
->Note: </B
-> We need someone to test this and make sure this works as advertised.
- </P
-></BLOCKQUOTE
-></DIV
-></LI
-><LI
+> Follow the instructions for setting up Fink. Once it's
+ installed, you'll want to run the following as root:
+ <B
+CLASS="COMMAND"
+>fink install gd</B
+>
+ </P
><P
-> Modify globals.pl and CGI.pl to remove the word "encrypt".
- </P
-><DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
+> It will prompt you for a number of dependencies, type 'y' and
+ hit enter to install all of the dependencies. Then watch it
+ work.
+ </P
+><P
+> To prevent creating conflicts with the software that Apple
+ installs by default, Fink creates its own directory tree at
+ /sw where it installs most of the software that it installs.
+ This means your libraries and headers for libgd will be at
+ /sw/lib and /sw/include instead of /usr/lib and
+ /usr/local/include. Because of these changed locations for
+ the libraries, the Perl GD module will not install directly
+ via CPAN (it looks for the specific paths instead of getting
+ them from your environment). But there's a way around that
+ :-)
+ </P
+><P
+> Instead of typing <SPAN
+CLASS="QUOTE"
+>"install GD"</SPAN
+> at the
+ <TT
+CLASS="PROMPT"
+>cpan></TT
+> prompt, type <B
+CLASS="COMMAND"
+>look
+ GD</B
+>. This should go through the motions of
+ downloading the latest version of the GD module, then it will
+ open a shell and drop you into the build directory. Apply the
+ following patch to the Makefile.PL file (save the patch into a
+ file and use the command <B
+CLASS="COMMAND"
+>patch <
+ patchfile</B
+>:
+ </P
+><P
+> <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>
+--- GD-1.33/Makefile.PL Fri Aug 4 16:59:22 2000
++++ GD-1.33-darwin/Makefile.PL Tue Jun 26 01:29:32 2001
+@@ -3,8 +3,8 @@
+ warn "NOTICE: This module requires libgd 1.8.3 or higher (shared library version 4.X).\n";
+
+ # =====> PATHS: CHECK AND ADJUST <=====
+-my @INC = qw(-I/usr/local/include -I/usr/local/include/gd);
+-my @LIBPATH = qw(-L/usr/lib/X11 -L/usr/X11R6/lib -L/usr/X11/lib -L/usr/local/lib );
++my @INC = qw(-I/sw/include -I/sw/include/gd -I/usr/local/include -I/usr/local/include/gd);
++my @LIBPATH = qw(-L/usr/lib/X11 -L/usr/X11R6/lib -L/usr/X11/lib -L/sw/lib -L/usr/local/lib);
+ my @LIBS = qw(-lgd -lpng -lz);
+
+ # FEATURE FLAGS
+@@ -23,7 +23,7 @@
+
+ push @LIBS,'-lttf' if $TTF;
+ push @LIBS,'-ljpeg' if $JPEG;
+-push @LIBS, '-lm' unless $^O eq 'MSWin32';
++push @LIBS, '-lm' unless ($^O =~ /^MSWin32|darwin$/);
+
+ # FreeBSD 3.3 with libgd built from ports croaks if -lXpm is specified
+ if ($^O ne 'freebsd' && $^O ne 'MSWin32') {
+
+
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+ </P
><P
+> Then, run these commands to finish the installation of the perl module:
+ <P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
><B
->Note: </B
-> I'm not sure this is all that is involved to remove crypt. Any
- NT Bugzilla hackers want to pipe up?
- </P
-></BLOCKQUOTE
-></DIV
-></LI
-><LI
+CLASS="COMMAND"
+>perl Makefile.PL</B
+></TD
+></TR
+><TR
+><TD
+><B
+CLASS="COMMAND"
+>make</B
+></TD
+></TR
+><TR
+><TD
+><B
+CLASS="COMMAND"
+>make test</B
+></TD
+></TR
+><TR
+><TD
+><B
+CLASS="COMMAND"
+>make install</B
+></TD
+></TR
+><TR
+><TD
+>And don't forget to run <B
+CLASS="COMMAND"
+>exit</B
+> to get back to cpan.</TD
+></TR
+></TBODY
+></TABLE
><P
-> Change all references to "processmail" to "processmail.pl" in
- all files, and rename "processmail" to "processmail.pl"
- </P
+></P
+>
+ </P
+><P
+> Happy Hacking!
+ </P
+></DIV
><DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
+CLASS="SECTION"
+><HR><H1
+CLASS="SECTION"
+><A
+NAME="BSDINSTALL"
+>3.4. BSD Installation Notes</A
+></H1
><P
-><B
->Note: </B
-> I really think this may be a change we want to make for
- main-tree Bugzilla. It's painless for the UNIX folks,
- and will make the Win32 people happier.
- </P
-></BLOCKQUOTE
+> For instructions on how to set up Bugzilla on FreeBSD, NetBSD, OpenBSD, BSDi, etc. please
+ consult <A
+HREF="#OSX"
+>Section 3.3</A
+>.
+ </P
></DIV
-></LI
-><LI
+><DIV
+CLASS="SECTION"
+><HR><H1
+CLASS="SECTION"
+><A
+NAME="GENINSTALL"
+>3.5. Installation General Notes</A
+></H1
+><DIV
+CLASS="SECTION"
+><H2
+CLASS="SECTION"
+><A
+NAME="AEN941"
+>3.5.1. Modifying Your Running System</A
+></H2
><P
-> 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.pl" utility to speed part of this procedure,
- available in the "Patches and Utilities" section of The Bugzilla Guide.
- </P
-></LI
-><LI
+> Bugzilla optimizes database lookups by storing all relatively static
+ information in the versioncache file, located in the data/ subdirectory
+ under your installation directory.
+ </P
><P
-> In processmail.pl, add "binmode(HANDLE)" before all read() calls.
- This may not be necessary, but in some cases the read() under
- Win32 doesn't count the EOL's without using a binary read().
- </P
-></LI
-></OL
-></DIV
+> If you make a change to the structural data in your database
+ (the versions table for example), or to the
+ <SPAN
+CLASS="QUOTE"
+>"constants"</SPAN
+> encoded in defparams.pl, you will
+ need to remove the cached content from the data directory
+ (by doing a <SPAN
+CLASS="QUOTE"
+>"rm data/versioncache"</SPAN
+>), or your
+ changes won't show up.
+ </P
+><P
+> That file gets automatically regenerated whenever it's more than an
+ hour old, so Bugzilla will eventually notice your changes by itself, but
+ generally you want it to notice right away, so that you can test things.
+ </P
></DIV
><DIV
CLASS="SECTION"
><HR><H2
CLASS="SECTION"
><A
-NAME="ADDLWINTIPS"
->2.2.2. Additional Windows Tips</A
+NAME="AEN948"
+>3.5.2. Upgrading From Previous Versions</A
></H2
-><DIV
-CLASS="TIP"
-><BLOCKQUOTE
-CLASS="TIP"
-><P
-><B
->Tip: </B
-> From Andrew Pearson:
- <A
-NAME="AEN624"
-></A
-><BLOCKQUOTE
-CLASS="BLOCKQUOTE"
-><P
-> "You can make Bugzilla work with Personal Web Server for
- Windows 98 and higher, as well as for IIS 4.0. Microsoft has
- information available at
- <A
-HREF=" http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP"
-TARGET="_top"
-> http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP</A
->
- </P
-><P
-> Basically you need to add two String Keys in the
- registry at the following location:
- </P
-><P
-> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\ScriptMap
- </P
><P
-> The keys should be called ".pl" and ".cgi", and both
- should have a value something like:
- <B
-CLASS="COMMAND"
->c:/perl/bin/perl.exe "%s" "%s"</B
->
- </P
+> The developers of Bugzilla are constantly adding new tables, columns and
+ fields. You'll get SQL errors if you just update the code. The strategy
+ to update is to simply always run the checksetup.pl script whenever
+ you upgrade your installation of Bugzilla. If you want to see what has
+ changed, you can read the comments in that file, starting from the end.
+ </P
><P
-> The KB article only talks about .pl, but it goes into
- more detail and provides a perl test script.
- </P
-></BLOCKQUOTE
->
- </P
-></BLOCKQUOTE
+> 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="TIP"
-><BLOCKQUOTE
-CLASS="TIP"
-><P
-><B
->Tip: </B
->"Brian" had this to add, about upgrading to Bugzilla 2.12 from previous versions:</P
+CLASS="SECTION"
+><HR><H2
+CLASS="SECTION"
><A
-NAME="AEN634"
-></A
-><BLOCKQUOTE
-CLASS="BLOCKQUOTE"
+NAME="HTACCESS"
+>3.5.3. <TT
+CLASS="FILENAME"
+>.htaccess</TT
+> files and security</A
+></H2
><P
-> Hi - I am updating bugzilla to 2.12 so I can tell you what I did (after I
- deleted the current dir and copied the files in).
- </P
+> To enhance the security of your Bugzilla installation,
+ Bugzilla will generate
+ <I
+CLASS="GLOSSTERM"
+><TT
+CLASS="FILENAME"
+>.htaccess</TT
+></I
+> files
+ which the Apache webserver can use to restrict access to
+ the bugzilla data files. The checksetup script will
+ generate the <TT
+CLASS="FILENAME"
+>.htaccess</TT
+> files.
+
+ <DIV
+CLASS="NOTE"
><P
-> In checksetup.pl, I did the following...
- </P
-><DIV
-CLASS="PROCEDURE"
-><OL
-TYPE="1"
-><LI
+></P
><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
+CLASS="NOTE"
WIDTH="100%"
+BORDER="0"
><TR
><TD
-><PRE
-CLASS="PROGRAMLISTING"
->my $webservergid = getgrnam($my_webservergroup);
- </PRE
+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 an alternate provider of
+ <SPAN
+CLASS="PRODUCTNAME"
+>webdot</SPAN
+> services for graphing
+ (as described when viewing
+ <TT
+CLASS="FILENAME"
+>editparams.cgi</TT
+> in your web
+ browser), you will need to change the ip address in
+ <TT
+CLASS="FILENAME"
+>data/webdot/.htaccess</TT
+> to the ip
+ address of the webdot server that you are using.
+ </P
></TD
></TR
></TABLE
+></DIV
+>
+
+ </P
+><P
+> If you are using Internet Information Server or other web
+ server which does not observe <TT
+CLASS="FILENAME"
+>.htaccess</TT
+>
+ conventions, you can disable their creation by editing
+ <TT
+CLASS="FILENAME"
+>localconfig</TT
+> and setting the
+ <TT
+CLASS="VARNAME"
+>$create_htaccess</TT
+> variable to
+ <TT
+CLASS="PARAMETER"
+><I
+>0</I
+></TT
+>.
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H2
+CLASS="SECTION"
+><A
+NAME="MOD_THROTTLE"
+>3.5.4. <TT
+CLASS="FILENAME"
+>mod_throttle</TT
+> and Security</A
+></H2
+><P
+> 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 <TT
+CLASS="FILENAME"
+>mod_throttle</TT
+> which can limit
+ connections by ip-address. You may download this module at
+ <A
+HREF="http://www.snert.com/Software/Throttle/"
+TARGET="_top"
+>http://www.snert.com/Software/Throttle/</A
+>. Follow the instructions to install into your Apache install. <EM
+>This module only functions with the Apache web server!</EM
+>. You may use the <B
+CLASS="COMMAND"
+>ThrottleClientIP</B
+> command provided by this module to accomplish this goal. See the <A
+HREF="http://www.snert.com/Software/Throttle/"
+TARGET="_top"
+>Module Instructions</A
+> for more information. </P
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H2
+CLASS="SECTION"
+><A
+NAME="CONTENT_TYPE"
+>3.5.5. Preventing untrusted Bugzilla content from executing malicious Javascript code</A
+></H2
+><P
+>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 <A
+HREF="http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3"
+TARGET="_top"
+>http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3</A
+>. 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. </P
><P
->to</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
+><FONT
+COLOR="#000000"
><PRE
CLASS="PROGRAMLISTING"
->my $webservergid = 'Administrators'
- </PRE
+>bash# cd $BUGZILLA_HOME; for i in `ls *.cgi`; \
+ do cat $i | sed 's/Content-type\: text\/html/Content-Type: text\/html\; charset=ISO-8859-1/' >$i.tmp; \
+ mv $i.tmp $i; done
+ </PRE
+></FONT
></TD
></TR
></TABLE
-></LI
-><LI
+></P
><P
-> I then ran checksetup.pl
- </P
-></LI
-><LI
+> All this one-liner command does is search for all instances of
+ <SPAN
+CLASS="QUOTE"
+>"Content-type: text/html"</SPAN
+> and replaces it with
+ <SPAN
+CLASS="QUOTE"
+>"Content-Type: text/html; charset=ISO-8859-1"</SPAN
+>.
+ 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
+ <SPAN
+CLASS="QUOTE"
+>"ISO-8859-1"</SPAN
+>, above, to <SPAN
+CLASS="QUOTE"
+>"UTF-8"</SPAN
+>.
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H2
+CLASS="SECTION"
+><A
+NAME="UNIXHISTORY"
+>3.5.6. UNIX Installation Instructions History</A
+></H2
><P
-> I removed all the encrypt()
- <DIV
-CLASS="EXAMPLE"
+> This document was originally adapted from the Bonsai
+ installation instructions by Terry Weissman
+ <terry@mozilla.org>.
+ </P
+><P
+> The February 25, 1999 re-write of this page was done by Ry4an
+ Brase <ry4an@ry4an.org>, with some edits by Terry
+ Weissman, Bryce Nesbitt, Martin Pool, & Dan Mosedale (But
+ don't send bug reports to them; report them using bugzilla, at <A
+HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla"
+TARGET="_top"
+>http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla</A
+> ).
+ </P
+><P
+> This document was heavily modified again Wednesday, March 07
+ 2001 to reflect changes for Bugzilla 2.12 release by Matthew
+ P. Barnson. The securing MySQL section should be changed to
+ become standard procedure for Bugzilla installations.
+ </P
+><P
+> Finally, the README in its entirety was marked up in SGML and
+ included into the Guide on April 24, 2001 by Matt Barnson.
+ Since that time, it's undergone extensive modification as
+ Bugzilla grew.
+ </P
+><P
+> Comments from people using this Guide for the first time are
+ particularly welcome.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H1
+CLASS="SECTION"
><A
-NAME="AEN646"
-></A
+NAME="WIN32"
+>3.6. Win32 Installation Notes</A
+></H1
><P
-><B
->Example 2-1. Removing encrypt() for Windows NT installations</B
-></P
+>This section covers installation on Microsoft Windows 95,
+ 98, ME, NT, and 2000. Bugzilla works fine on Win32 platforms,
+ but please remember that the Bugzilla team and the author of the
+ Guide neither endorse nor support installation on Microsoft
+ Windows. Bugzilla installs and runs <EM
+>best</EM
+>
+ and <EM
+>easiest</EM
+> on UNIX-like operating systems,
+ and that is the way it will stay for the foreseeable future. The
+ Bugzilla team is considering supporting Win32 for the 2.16
+ release and later.</P
+><P
+>The easiest way to install Bugzilla on Intel-archiecture
+ machines is to install some variant of GNU/Linux, then follow
+ the UNIX installation instructions in this Guide. If you have
+ any influence in the platform choice for running this system,
+ please choose GNU/Linux instead of Microsoft Windows.</P
+><DIV
+CLASS="SECTION"
+><HR><H2
+CLASS="SECTION"
+><A
+NAME="WININSTALL"
+>3.6.1. Win32 Installation: Step-by-step</A
+></H2
+><DIV
+CLASS="NOTE"
><P
-> Replace this:
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
+></P
+><TABLE
+CLASS="NOTE"
WIDTH="100%"
+BORDER="0"
><TR
><TD
-><PRE
-CLASS="PROGRAMLISTING"
->SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " .
- SqlQuote(substr($realcryptpwd, 0, 2)) . ")");
-my $enteredcryptpwd = FetchOneColumn();
- </PRE
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> You should be familiar with, and cross-reference, the rest
+ of the
+ <A
+HREF="#INSTALLATION"
+>Bugzilla Installation</A
+> section while performing your
+ Win32 installation.
+ </P
+><P
+> Making Bugzilla work on Microsoft Windows is no
+ picnic. Support for Win32 has improved dramatically in the
+ last few releases, but, if you choose to proceed, you should
+ be a <EM
+>very</EM
+> skilled Windows Systems
+ Administrator with strong troubleshooting abilities, a high
+ tolerance for pain, and moderate perl skills. Bugzilla on NT
+ requires hacking source code and implementing some advanced
+ utilities. What follows is the recommended installation
+ procedure for Win32; additional suggestions are provided in
+ <A
+HREF="#FAQ"
+>Appendix A</A
+>.
+ </P
></TD
></TR
></TABLE
+></DIV
+><DIV
+CLASS="PROCEDURE"
+><OL
+TYPE="1"
+><LI
+><P
+> Install <A
+HREF="http://www.apache.org/"
+TARGET="_top"
+>Apache Web
+ Server</A
+> for Windows, and copy the Bugzilla files
+ somewhere Apache can serve them. Please follow all the
+ instructions referenced in <A
+HREF="#INSTALLATION"
+>Bugzilla Installation</A
>
- with this:
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
+ regarding your Apache configuration, particularly
+ instructions regarding the <SPAN
+CLASS="QUOTE"
+>"AddHandler"</SPAN
+>
+ parameter and <SPAN
+CLASS="QUOTE"
+>"ExecCGI"</SPAN
+>.
+ </P
+><DIV
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
WIDTH="100%"
+BORDER="0"
><TR
><TD
-><PRE
-CLASS="PROGRAMLISTING"
->my $enteredcryptpwd = $enteredpwd
- </PRE
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> You may also use Internet Information Server or Personal
+ Web Server for this purpose. However, setup is quite
+ different. If ActivePerl doesn't seem to handle your
+ file associations correctly (for .cgi and .pl files),
+ please consult <A
+HREF="#FAQ"
+>Appendix A</A
+>.
+ </P
+><P
+> If you are going to use IIS, if on Windows NT you must
+ be updated to at least Service Pack 4. Windows 2000
+ ships with a sufficient version of IIS.
+ </P
></TD
></TR
></TABLE
->
- in cgi.pl.
- </P
></DIV
+></LI
+><LI
+><P
+> Install <A
+HREF="http://www.activestate.com/"
+TARGET="_top"
+>ActivePerl</A
+> for Windows. Check <A
+HREF="http://aspn.activestate.com/ASPN/Downloads/ActivePerl/"
+TARGET="_top"
+>http://aspn.activestate.com/ASPN/Downloads/ActivePerl</A
+> for a current compiled binary.
+ </P
+><P
+> Please also check the following links to fully understand the status
+ of ActivePerl on Win32:
+ <A
+HREF="http://language.perl.com/newdocs/pod/perlport.html"
+TARGET="_top"
+> Perl Porting</A
+>, and
+ <A
+HREF="http://ftp.univie.ac.at/packages/perl/ports/nt/FAQ/perlwin32faq5.html"
+TARGET="_top"
+> Perl on Win32 FAQ</A
>
- </P
+ </P
></LI
><LI
><P
-> I renamed processmail to processmail.pl
- </P
-></LI
-><LI
+> Use ppm from your perl\bin directory to install the following packs: DBI,
+ DBD-Mysql, TimeDate, Chart, Date-Calc, Date-Manip, and GD. You may need
+ to extract them from .zip format using Winzip or other unzip program first.
+ These additional ppm modules can be downloaded from ActiveState.
+ </P
+><DIV
+CLASS="NOTE"
><P
-> I altered the sendmail statements to windmail:
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
+></P
+><TABLE
+CLASS="NOTE"
WIDTH="100%"
+BORDER="0"
><TR
><TD
-><PRE
-CLASS="PROGRAMLISTING"
->
-open SENDMAIL, "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t > mail.log";
- </PRE
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> You can find a list of modules at
+ <A
+HREF="http://www.activestate.com/PPMPackages/zips/5xx-builds-only"
+TARGET="_top"
+> http://www.activestate.com/PPMPackages/zips/5xx-builds-only/</A
+>
+ </P
></TD
></TR
></TABLE
->
- </P
-><P
-> The quotes around the dir is for the spaces. mail.log is for the output
- </P
-></LI
-></OL
></DIV
-></BLOCKQUOTE
-></BLOCKQUOTE
-></DIV
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="CHAPTER"
-><HR><H1
-><A
-NAME="ADMINISTRATION"
->Chapter 3. Administering Bugzilla</A
-></H1
-><FONT
-COLOR="RED"
->Or, I just got this cool thing installed. Now what the heck do I do with it?</FONT
><P
->So you followed the README isntructions to the letter, and
-just logged into bugzilla with your super-duper god account and you are sitting at the query
-screen. Yet, you have nothing to query. Your first act of business needs to be to setup the
-operating parameters for bugzilla.</P
+> The syntax for ppm is:
+ <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>C:> </TT
+><B
+CLASS="COMMAND"
+>ppm <modulename></B
+>
+ </TT
+>
+ </P
><DIV
-CLASS="SECTION"
-><HR><H1
-CLASS="SECTION"
+CLASS="EXAMPLE"
><A
-NAME="POSTINSTALL-CHECK"
->3.1. Post-Installation Checklist</A
-></H1
-><P
-> After installation, follow the checklist below to ensure that
- you have a successful installation.
- If you do not see a recommended setting for a parameter,
- consider leaving it at the default
- while you perform your initial tests on your Bugzilla setup.
- </P
-><DIV
-CLASS="PROCEDURE"
-><OL
-TYPE="1"
-><LI
+NAME="AEN1038"
+></A
><P
-> Bring up "editparams.cgi" in your web browser. For instance, to edit parameters
- at mozilla.org, the URL would be <A
-HREF="http://bugzilla.mozilla.org/editparams.cgi"
-TARGET="_top"
-> http://bugzilla.mozilla.org/editparams.cgi</A
->, also available under the "edit parameters"
- link on your query page.
- </P
-></LI
-><LI
+><B
+>Example 3-3. Installing ActivePerl ppd Modules on Microsoft Windows</B
+></P
><P
-> Set "maintainer" to <EM
->your</EM
-> email address.
- This allows Bugzilla's error messages
- to display your email
- address and allow people to contact you for help.
- </P
-></LI
-><LI
+><TT
+CLASS="PROMPT"
+>C:></TT
+><B
+CLASS="COMMAND"
+>ppm
+ <TT
+CLASS="OPTION"
+>DBD-Mysql</TT
+></B
+></P
><P
-> Set "urlbase" to the URL reference for your Bugzilla installation.
- If your bugzilla query page is at http://www.foo.com/bugzilla/query.cgi,
- your url base is http://www.foo.com/bugzilla/
- </P
-></LI
-><LI
+>Watch your capitalization!</P
+></DIV
><P
-> Set "usebuggroups" to "1" <EM
->only</EM
->
- if you need to restrict access to products.
- I suggest leaving this parameter <EM
->off</EM
+> You can find ActiveState ppm modules at
+ <A
+HREF="http://www.activestate.com/PPMPackages/5.6plus/"
+TARGET="_top"
+> http://www.activestate.com/PPMPackages/5.6plus</A
>
- while initially testing your Bugzilla.
- </P
-></LI
-><LI
-><P
-> Set "usebuggroupsentry" to "1" if you want to restrict access to products.
- Once again, if you are simply testing your installation, I suggest against
- turning this parameter on; the strict security checking may stop you from
- being able to modify your new entries.
- </P
+ </P
></LI
><LI
><P
-> Set "shadowdb" to "bug_shadowdb" if you will be
- running a *very* large installation of Bugzilla.
- The shadow database enables many simultaneous users
- to read and write to the database
- without interfering with one another.
- <DIV
-CLASS="NOTE"
-><BLOCKQUOTE
+> Install MySQL for NT.
+ <DIV
CLASS="NOTE"
><P
-><B
->Note: </B
-> Enabling "shadowdb" can adversely affect the stability
- of your installation of Bugzilla.
- You may frequently need to manually synchronize your databases,
- or schedule nightly syncs
- via "cron"
- </P
-></BLOCKQUOTE
-></DIV
->
- Once again, in testing you should
- avoid this option -- use it if or when you <EM
->need</EM
-> to use it, and have
- repeatedly run into the problem it was designed to solve -- very long wait times while
- attempting to commit a change to the database.
- </P
-><P
-> If you use the "shadowdb" option,
- it is only natural that you should turn the "queryagainstshadowdb"
- option "On" as well. Otherwise you are replicating data into a shadow database for no reason!
- </P
-></LI
-><LI
-><P
-> If you have custom logos or HTML you must put in place to fit within your site design guidelines,
- place the code in the "headerhtml", "footerhtml", "errorhtml",
- "bannerhtml", or "blurbhtml" text boxes.
- <DIV
-CLASS="NOTE"
-><BLOCKQUOTE
+></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
-><B
->Note: </B
-> The "headerhtml" text box is the HTML printed out
- <EM
->before</EM
-> any other code on the page.
- If you have a special banner, put the code for it in "bannerhtml".
- You may want to leave these
- settings at the defaults initially.
- </P
-></BLOCKQUOTE
+> You can download MySQL for Windows NT from <A
+HREF="http://www.mysql.com/"
+TARGET="_top"
+>MySQL.com</A
+>. Some find it helpful to use the WinMySqlAdmin utility, included with the download, to set up the database.
+ </P
+></TD
+></TR
+></TABLE
></DIV
>
- </P
-></LI
-><LI
-><P
-> Add any text you wish to the "passwordmail" parameter box. For instance,
- many people choose to use this box to give a quick training blurb about how to
- use Bugzilla at your site.
- </P
+ </P
></LI
><LI
><P
-> Ensure "newemailtech" is "on".
- Your users will thank you. This is the default in the post-2.12 world, and is
- only an issue if you are upgrading.
- </P
-></LI
+> Setup MySQL
+ </P
+><OL
+CLASS="SUBSTEPS"
+TYPE="a"
><LI
><P
-> Do you want to use the qa contact ("useqacontact")
- and status whiteboard ("usestatuswhiteboard") fields?
- These fields are useful because they allow for more flexibility,
- particularly when you have an existing
- Quality Assurance and/or Release Engineering team,
- but they may not be needed for smaller installations.
- </P
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>C:> </TT
+>
+ <B
+CLASS="COMMAND"
+>C:\mysql\bin\mysql -u root mysql</B
+>
+ </TT
+>
+ </P
></LI
><LI
><P
-> Set "whinedays" to the amount of days you want to let bugs go
- in the "New" or "Reopened" state before
- notifying people they have untouched new bugs. If you do not plan to use this feature, simply do
- not set up the whining cron job described in the README, or set this value to "0".
- </P
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>mysql></TT
+>
+ <B
+CLASS="COMMAND"
+>DELETE FROM user WHERE Host='localhost' AND User='';</B
+>
+ </TT
+>
+ </P
></LI
><LI
><P
-> Set the "commenton" options according to your site policy.
- It is a wise idea to require comments when users
- resolve, reassign, or reopen bugs.
- <DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
-><P
-><B
->Note: </B
-> It is generally far better to require a developer comment when resolving bugs than not.
- Few things are more annoying to bug database users than having a developer
- mark a bug "fixed" without any comment as to what the fix was (or even that it was truly fixed!)
- </P
-></BLOCKQUOTE
-></DIV
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>mysql></TT
>
- </P
-></LI
-><LI
+ <B
+CLASS="COMMAND"
+>UPDATE user SET Password=PASSWORD ('new_password')
+ WHERE user='root';</B
+>
+ </TT
+>
+ </P
><P
-> Set "supportwatchers" to "On". This feature is helpful for team leads to monitor progress in their
- respective areas, and can offer many other benefits, such as allowing a developer to pick up a
- former engineer's bugs without requiring her to change all the information in the bug.
- </P
+><SPAN
+CLASS="QUOTE"
+>"new_password"</SPAN
+>, above, indicates
+ whatever password you wish to use for your
+ <SPAN
+CLASS="QUOTE"
+>"root"</SPAN
+> user.</P
></LI
-></OL
-></DIV
-></DIV
-><DIV
-CLASS="SECTION"
-><HR><H1
-CLASS="SECTION"
-><A
-NAME="USERADMIN"
->3.2. User Administration</A
-></H1
-><P
-> User administration is one of the easiest parts of Bugzilla.
- Keeping it from getting out of hand, however, can become a challenge.
- </P
-><DIV
-CLASS="SECTION"
-><HR><H2
-CLASS="SECTION"
-><A
-NAME="DEFAULTUSER"
->3.2.1. Creating the Default User</A
-></H2
-><P
-> 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 were to delete the "super user" account, re-running
- checksetup.pl will again prompt you for this username and password.
- </P
-><DIV
-CLASS="TIP"
-><BLOCKQUOTE
-CLASS="TIP"
+><LI
+><A
+NAME="NTBUGS-PASSWORD"
+></A
><P
-><B
->Tip: </B
-> If you wish to add more administrative users, you must use the MySQL interface.
- Run "mysql" from the command line, and use these commands ("mysql>" denotes the
- mysql prompt, not something you should type in):
- <B
-CLASS="COMMAND"
-><TT
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
CLASS="PROMPT"
>mysql></TT
-> use bugs;</B
>
- <B
+ <B
CLASS="COMMAND"
-><TT
-CLASS="PROMPT"
->mysql></TT
-> update profiles set groupset=0x7ffffffffffffff
- where login_name = "(user's login name)"; </B
+>GRANT SELECT, INSERT, UPDATE, DELETE,
+ INDEX, ALTER, CREATE, DROP, REFERENCES
+ ON bugs.* to bugs@localhost
+ IDENTIFIED BY 'bugs_password';</B
>
- </P
-></BLOCKQUOTE
-></DIV
-></DIV
-><DIV
-CLASS="SECTION"
-><HR><H2
-CLASS="SECTION"
-><A
-NAME="MANAGEUSERS"
->3.2.2. Managing Other Users</A
-></H2
-><DIV
-CLASS="SECTION"
-><H3
-CLASS="SECTION"
-><A
-NAME="LOGIN"
->3.2.2.1. Logging In</A
-></H3
+ </TT
+>
+ </P
><P
-></P
-><OL
-TYPE="1"
+><SPAN
+CLASS="QUOTE"
+>"bugs_password"</SPAN
+>, above, indicates
+ whatever password you wish to use for your
+ <SPAN
+CLASS="QUOTE"
+>"bugs"</SPAN
+> user.</P
+></LI
><LI
><P
-> Open the index.html page for your Bugzilla installation in your browser window.
- </P
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>mysql></TT
+>
+ <B
+CLASS="COMMAND"
+>FLUSH PRIVILEGES;</B
+>
+ </TT
+>
+ </P
></LI
><LI
><P
-> Click the "Query Existing Bug Reports" link.
- </P
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>mysql></TT
+>
+ <B
+CLASS="COMMAND"
+>create database bugs;</B
+>
+ </TT
+>
+ </P
></LI
><LI
><P
-> Click the "Log In" link at the foot of the page.
- </P
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>mysql></TT
+>
+ <B
+CLASS="COMMAND"
+>exit;</B
+>
+ </TT
+>
+ </P
></LI
><LI
><P
-> Type your email address, and the password which was emailed to you when you
- created your Bugzilla account, into the spaces provided.
- </P
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>C:></TT
+>
+ <B
+CLASS="COMMAND"
+>C:\mysql\bin\mysqladmin -u root -p reload</B
+>
+ </TT
+>
+ </P
></LI
></OL
+></LI
+><LI
><P
->Congratulations, you are logged in!</P
-></DIV
-><DIV
-CLASS="SECTION"
-><HR><H3
-CLASS="SECTION"
-><A
-NAME="CREATENEWUSERS"
->3.2.2.2. Creating new users</A
-></H3
+> Edit <TT
+CLASS="FILENAME"
+>checksetup.pl</TT
+> in your Bugzilla directory. Change
+ this line:
+ </P
><P
-> Your users can create their own user accounts by clicking the "New Account"
- link at the bottom of each page.
- However, should you desire to create user accounts ahead of time, here is how you do it.
- </P
+> <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>my $webservergid = getgrnam($my_webservergroup);
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+ </P
><P
-></P
-><OL
-TYPE="1"
+> to
+ </P
+><P
+> <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>my $webservergid = $my_webservergroup;
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+or the name of the group you wish to own the files explicitly:
+ <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>my $webservergid = 'Administrators'
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+ </P
+></LI
><LI
><P
-> After logging in, click the "Users" link at the footer of the query page.
- </P
+> Run <TT
+CLASS="FILENAME"
+>checksetup.pl</TT
+> from the Bugzilla directory.
+ </P
></LI
><LI
><P
-> To see a specific user, type a portion of their login name
- in the box provided and click "submit".
- To see all users, simply click the "submit" button.
- You must click "submit" here to be able to add a new user.
- </P
+>Edit <TT
+CLASS="FILENAME"
+>localconfig</TT
+> to suit your
+ requirements. Set <TT
+CLASS="VARNAME"
+>$db_pass</TT
+> to your
+ <SPAN
+CLASS="QUOTE"
+>"bugs_password"</SPAN
+> from <A
+HREF="#NTBUGS-PASSWORD"
+>step 5.d</A
+>, and <TT
+CLASS="VARNAME"
+>$webservergroup</TT
+> to <SPAN
+CLASS="QUOTE"
+>"8"</SPAN
+>.</P
><DIV
-CLASS="TIP"
-><BLOCKQUOTE
-CLASS="TIP"
+CLASS="NOTE"
><P
-><B
->Tip: </B
-> More functionality is available via the list on the right-hand side
- of the text entry box.
- You can match what you type as a case-insensitive substring (the default)
- of all users on your system, a case-sensitive regular expression
- (please see the "man regexp" manual page for details on regular expression syntax),
- or a <EM
->reverse</EM
-> regular expression match,
- where every user name which does NOT match the regular expression
- is selected.
- </P
-></BLOCKQUOTE
-></DIV
-></LI
-><LI
+></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
-> Click the "Add New User" link at the bottom of the user list
- </P
+>Not sure on the <SPAN
+CLASS="QUOTE"
+>"8"</SPAN
+> for
+ <TT
+CLASS="VARNAME"
+>$webservergroup</TT
+> above. If it's
+ wrong, please send corrections.</P
+></TD
+></TR
+></TABLE
+></DIV
></LI
><LI
><P
-> Fill out the form presented. This page is self-explanatory. When done, click "submit".
- </P
+> Edit <TT
+CLASS="FILENAME"
+>defparams.pl</TT
+> to suit your
+ requirements. Particularly, set
+ <TT
+CLASS="VARNAME"
+>DefParam("maintainer")</TT
+> and
+ <TT
+CLASS="VARNAME"
+>DefParam("urlbase") to match your
+ install.</TT
+>
+ </P
><DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><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
-><B
->Note: </B
-> Adding a user this way will <EM
->not</EM
-> send an email
- informing them of their username and password.
- In general, it is preferable to log out and use the "New Account"
- button to create users, as it will pre-populate all the required fields and also notify
- the user of her account name and password.
- </P
-></BLOCKQUOTE
+>This is yet another step I'm not sure of, since the
+ maintainer of this documentation does not maintain
+ Bugzilla on NT. If you can confirm or deny that this
+ step is required, please let me know.</P
+></TD
+></TR
+></TABLE
></DIV
></LI
-></OL
-></DIV
+><LI
><DIV
-CLASS="SECTION"
-><HR><H3
-CLASS="SECTION"
-><A
-NAME="DISABLEUSERS"
->3.2.2.3. Disabling Users</A
-></H3
-><P
-> I bet you noticed that big "Disabled Text" entry box available from the "Add New User" screen,
- when you edit an account?
- By entering any text in this box and selecting "submit",
- you have prevented the user from using Bugzilla via the web interface.
- Your explanation, written in this text box, will be presented to the user
- the next time she attempts to use the system.
- <DIV
-CLASS="WARNING"
+CLASS="NOTE"
><P
></P
><TABLE
-CLASS="WARNING"
-BORDER="1"
+CLASS="NOTE"
WIDTH="100%"
+BORDER="0"
><TR
><TD
+WIDTH="25"
ALIGN="CENTER"
-><B
->Warning</B
-></TD
-></TR
-><TR
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
><TD
ALIGN="LEFT"
+VALIGN="TOP"
><P
-> Don't disable your own administrative account, or you will hate life!
+> There are several alternatives to Sendmail that will work on Win32.
+ The one mentioned here is a <EM
+>suggestion</EM
+>, not
+ a requirement. Some other mail packages that can work include
+ <A
+HREF="http://www.blat.net/"
+TARGET="_top"
+>BLAT</A
+>,
+ <A
+HREF="http://www.geocel.com/windmail/"
+TARGET="_top"
+>Windmail</A
+>,
+ <A
+HREF="http://www.dynamicstate.com/"
+TARGET="_top"
+>Mercury Sendmail</A
+>,
+ and the CPAN Net::SMTP Perl module (available in .ppm).
+ Every option requires some hacking of the Perl scripts for Bugzilla
+ to make it work. The option here simply requires the least.
</P
></TD
></TR
></TABLE
></DIV
->
- </P
-></DIV
><DIV
-CLASS="SECTION"
-><HR><H3
-CLASS="SECTION"
-><A
-NAME="MODIFYUSERS"
->3.2.2.4. Modifying Users</A
-></H3
-><P
-> Here I will attempt to describe the function of each option on the user edit screen.
- </P
-><P
-></P
-><UL
+CLASS="PROCEDURE"
+><OL
+TYPE="1"
><LI
><P
-> <EM
->Login Name</EM
->: This is generally the user's email address.
- However, if you have edited your system parameters,
- this may just be the user's login name or some other identifier.
- <DIV
-CLASS="TIP"
-><BLOCKQUOTE
-CLASS="TIP"
-><P
-><B
->Tip: </B
-> For compatability reasons, you should probably
- stick with email addresses as user login names. It will make your life easier.
- </P
-></BLOCKQUOTE
-></DIV
->
- </P
+> Download NTsendmail, available from<A
+HREF="http://www.ntsendmail.com/"
+TARGET="_top"
+> www.ntsendmail.com</A
+>. You must have a "real" mail server which allows you to relay off it in your $ENV{"NTsendmail"} (which you should probably place in globals.pl)
+ </P
></LI
><LI
><P
-> <EM
->Real Name</EM
->: Duh!
- </P
+>Put ntsendmail.pm into your .\perl\lib directory.</P
></LI
><LI
><P
-> <EM
->Password</EM
->: You will only see asterisks in versions
- of Bugzilla newer than 2.10 or early 2.11. You can change the user password here.
- </P
-></LI
-><LI
+>Add to globals.pl:</P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+># these settings configure the NTsendmail process
+use NTsendmail;
+$ENV{"NTsendmail"}="your.smtpserver.box";
+$ENV{"NTsendmail_debug"}=1;
+$ENV{"NTsendmail_max_tries"}=5;
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+><DIV
+CLASS="NOTE"
><P
-> <EM
->Email Notification</EM
->: You may choose from one of three options:
- <P
></P
-><OL
-TYPE="1"
-><LI
-><P
-> All qualifying bugs except those which I change:
- The user will be notified of any change to any bug
- for which she is the reporter, assignee, Q/A contact, CC recipient, or "watcher".
- </P
-></LI
-><LI
-><P
-> Only those bugs which I am listed on the CC line:
- The user will not be notified of changes to bugs where she is the assignee,
- reporter, or Q/A contact, but will receive them if she is on the CC list.
- <DIV
-CLASS="NOTE"
-><BLOCKQUOTE
+><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
-><B
->Note: </B
-> She will still receive whining cron emails if you set up the "whinemail" feature.
- </P
-></BLOCKQUOTE
+> Some mention to also edit
+ <TT
+CLASS="VARNAME"
+>$db_pass</TT
+> in
+ <TT
+CLASS="FILENAME"
+>globals.pl</TT
+> to be your
+ <SPAN
+CLASS="QUOTE"
+>"bugs_password"</SPAN
+>. Although this may get
+ you around some problem authenticating to your
+ database, since globals.pl is not normally
+ restricted by <TT
+CLASS="FILENAME"
+>.htaccess</TT
+>, your
+ database password is exposed to whoever uses your
+ web server.
+ </P
+></TD
+></TR
+></TABLE
></DIV
->
- </P
></LI
><LI
><P
-> <EM
->All Qualifying Bugs</EM
->: This user is a glutton for punishment.
- If her name is in the reporter, Q/A contact, CC, assignee, or is a "watcher",
- she will get email updates regarding the bug.
- </P
-></LI
-></OL
-></P
-><P
-> <EM
->Disable Text</EM
->: If you type anything in this box,
- including just a space, the user account is disabled from making any changes
- to bugs via the web interface, and what you type in this box is presented as the reason.
- <DIV
-CLASS="WARNING"
+> Find and comment out all occurences of
+ <SPAN
+CLASS="QUOTE"
+>"<B
+CLASS="COMMAND"
+>open(SENDMAIL</B
+>"</SPAN
+> in
+ your Bugzilla directory. Then replace them with:
+ <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+># new sendmail functionality
+my $mail=new NTsendmail;
+my $from="bugzilla\@your.machine.name.tld";
+my $to=$login;
+my $subject=$urlbase;
+$mail->send($from,$to,$subject,$msg);
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+ </P
+><DIV
+CLASS="NOTE"
><P
></P
><TABLE
-CLASS="WARNING"
-BORDER="1"
-WIDTH="90%"
+CLASS="NOTE"
+WIDTH="100%"
+BORDER="0"
><TR
><TD
+WIDTH="25"
ALIGN="CENTER"
-><B
->Warning</B
-></TD
-></TR
-><TR
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
><TD
ALIGN="LEFT"
+VALIGN="TOP"
><P
->Don't disable the administrator account!</P
+> Some have found success using the commercial product,
+ <SPAN
+CLASS="PRODUCTNAME"
+>Windmail</SPAN
+>.
+ You could try replacing your sendmail calls with:
+ <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>open SENDMAIL, "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t > mail.log";
+ </PRE
+></FONT
></TD
></TR
></TABLE
-></DIV
>
- <DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
-><P
-><B
->Note: </B
-> As of this writing, the user can still submit bugs via the e-mail gateway,
- if you set it up, despite the disabled text field. The e-mail gateway should
- <EM
->not</EM
-> be enabled for secure installations of Bugzilla.
+ or something to that effect.
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
->
- </P
></LI
-><LI
-><P
-> <EM
->CanConfirm</EM
->: This field is only used if you have enabled
- "unconfirmed" status in your parameters screen. If you enable this for a user,
- that user can then move bugs from "Unconfirmed" to "Confirmed" status (ergo: "New" status).
- Be judicious about allowing users to turn this bit on for other users.
- </P
-></LI
-><LI
-><P
-> <EM
->Creategroups</EM
->: This option will allow a user to create and
- destroy groups in Bugzilla. Unless you are using the Bugzilla GroupSentry security
- option "usebuggroupsentry" in your parameters, this setting has no effect.
- </P
-></LI
-><LI
-><P
-> <EM
->Editbugs</EM
->: Unless a user has this bit set, they can only edit
- those bugs for which they are the assignee or the reporter.
- <DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
-><P
-><B
->Note: </B
-> Leaving this option unchecked does not prevent users from adding
- comments to a bug! They simply cannot change a bug priority, severity,
- etc. unless they are the assignee or reporter.
- </P
-></BLOCKQUOTE
+></OL
></DIV
->
- </P
-></LI
-><LI
-><P
-> <EM
->Editcomponents</EM
->: This flag allows a user to create new
- products and components, as well as modify and destroy those that have no bugs
- associated with them. If a product or component has bugs associated with it,
- those bugs must be moved to a different product or component before Bugzilla
- will allow them to be destroyed. The name of a product or component can be
- changed without affecting the associated bugs, but it tends to annoy
- the hell out of your users when these change a lot.
- </P
></LI
><LI
><P
-> <EM
->Editkeywords</EM
->: If you use Bugzilla's keyword functionality,
- enabling this feature allows a user can create and destroy keywords.
- As always, the keywords for existing bugs containing the keyword
- the user wishes to destroy must be changed before Bugzilla will allow it to die.
- You must be very careful about creating too many new keywords
- if you run a very large Bugzilla installation; keywords are global variables
- across products, and you can often run into a phenomenon called "keyword bloat".
- This confuses users, and then the feature goes unused.
- </P
-></LI
-><LI
+> Change all references in all files from
+ <TT
+CLASS="FILENAME"
+>processmail</TT
+> to
+ <TT
+CLASS="FILENAME"
+>processmail.pl</TT
+>, and
+ rename <TT
+CLASS="FILENAME"
+>processmail</TT
+> to
+ <TT
+CLASS="FILENAME"
+>processmail.pl</TT
+>.
+ </P
+><DIV
+CLASS="NOTE"
><P
-> <EM
->Editusers</EM
->: This flag allows a user do what you're doing
- right now: edit other users.
- This will allow those with the right to do so to remove administrator
- priveleges from other users or grant them to themselves. Enable with care.
- </P
-></LI
-><LI
+></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
-> <EM
->PRODUCT</EM
->: PRODUCT bugs access. This allows an administrator,
- with product-level granularity, to specify in which products a user can edit bugs.
- The user must still have the "editbugs" privelege to edit bugs in this area;
- this simply restricts them from even seeing bugs outside these boundaries if the administrator
- has enabled the group sentry parameter "usebuggroupsentry". Unless you are using bug groups,
- this option has no effect.
+> Many think this may be a change we want to make for
+ main-tree Bugzilla. It's painless for the UNIX folks,
+ and will make the Win32 people happier.
</P
-></LI
-></UL
-></DIV
-></DIV
+></TD
+></TR
+></TABLE
></DIV
><DIV
-CLASS="SECTION"
-><HR><H1
-CLASS="SECTION"
-><A
-NAME="PROGRAMADMIN"
->3.3. Product, Component, Milestone, and Version Administration</A
-></H1
+CLASS="NOTE"
+><P
+></P
><TABLE
-BORDER="0"
+CLASS="NOTE"
WIDTH="100%"
-CELLSPACING="0"
-CELLPADDING="0"
-CLASS="EPIGRAPH"
+BORDER="0"
><TR
><TD
-WIDTH="45%"
-> </TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
><TD
-WIDTH="45%"
ALIGN="LEFT"
VALIGN="TOP"
-><I
><P
-><I
->Dear Lord, we have to get our users to do WHAT?</I
-></P
-></I
+> Some people have suggested using the Net::SMTP Perl module instead of NTsendmail or the other options listed here. You can change processmail.pl to make this work.
+ <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+> my $smtp = Net::SMTP->new('<Name of your SMTP server>'); #connect to SMTP server
+$smtp->mail('<your name>@<you smpt server>');# use the sender's adress here
+$smtp->to($tolist); # recipient's address
+$smtp->data(); # Start the mail
+$smtp->datasend($msg);
+$smtp->dataend(); # Finish sending the mail
+$smtp->quit; # Close the SMTP connection
+$logstr = "$logstr; mail sent to $tolist $cclist";
+} </PRE
+></FONT
></TD
></TR
></TABLE
-><DIV
-CLASS="SECTION"
-><HR><H2
-CLASS="SECTION"
-><A
-NAME="PRODUCTS"
->3.3.1. Products</A
-></H2
+>
+here is a test mail program for Net::SMTP:
+<TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
><FONT
-COLOR="RED"
->Formerly, and in some spots still, called "Programs"</FONT
-><P
-> <A
-HREF="#GLOSS_PRODUCT"
-><I
-CLASS="GLOSSTERM"
->Products</I
-></A
-> are the
- broadest category in Bugzilla, and you should have the least of these.
- If your company makes computer games, you should have one product per game,
- and possibly a few special products
- (website, meetings...)
- </P
-><P
-> A Product (formerly called "Program", and still referred to that way
- in some portions of the source code) controls some very important functions.
- The number of "votes" available for users to vote for the most important bugs
- is set per-product, as is the number of votes required to move a bug automatically
- from the UNCONFIRMED status to the NEW status. One can close a Product for further
- bug entry and define various Versions available from the Edit Product screen.
- </P
-><P
->To create a new product:</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
-> Select "components" from the yellow footer
- </P
-><DIV
-CLASS="TIP"
-><BLOCKQUOTE
-CLASS="TIP"
-><P
-><B
->Tip: </B
-> It may seem counterintuitive to click "components" when you want
- to edit the properties associated with Products. This is one of a long
- list of things we want in Bugzilla 3.0...
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+> use Net::SMTP;
+ my $smtp = Net::SMTP->new('<Name of your SMTP server', Timeout => 30, Debug
+=> 1, ); # connect to SMTP server
+ $smtp->auth;
+ $smtp->mail('you@yourcompany.com');# use the sender's adress
+here
+ $smtp->to('someotherAddress@someotherdomain.com'); #
+recipient's address
+ $smtp->data(); # Start the mail
+ $smtp->datasend('test');
+ $smtp->dataend(); # Finish sending the mail
+ $smtp->quit; # Close the SMTP connection
+exit; </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
></LI
><LI
-><P
-> Select the "Add" link to the right of "Add a new product".
- </P
-></LI
-><LI
-><P
-> Enter the name of the product and a description.
- The Description field is free-form.
- </P
-></LI
-></OL
-><DIV
-CLASS="TIP"
-><BLOCKQUOTE
-CLASS="TIP"
-><P
-><B
->Tip: </B
-> Don't worry about the "Closed for bug entry", "Maximum Votes per person",
- "Maximum votes a person can put on a single bug", "Number of votes a bug in
- this Product needs to automatically get out of the UNCOMFIRMED state",
- and "Version" options yet.
- We'll cover those in a few moments.
- </P
-></BLOCKQUOTE
-></DIV
-></DIV
-><DIV
-CLASS="SECTION"
-><HR><H2
-CLASS="SECTION"
-><A
-NAME="COMPONENTS"
->3.3.2. Components</A
-></H2
-><P
-> Components are subsections of a Product.
-
- <DIV
-CLASS="EXAMPLE"
-><A
-NAME="AEN838"
-></A
-><P
-><B
->Example 3-1. Creating some Components</B
-></P
><DIV
-CLASS="INFORMALEXAMPLE"
-><A
-NAME="AEN840"
-></A
+CLASS="NOTE"
><P
></P
+><TABLE
+CLASS="NOTE"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
><P
-> The computer game you are designing may 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.
+> This step is optional if you are using IIS or another
+ web server which only decides on an interpreter based
+ upon the file extension (.pl), rather than the
+ <SPAN
+CLASS="QUOTE"
+>"shebang"</SPAN
+> line (#/usr/bonsaitools/bin/perl)
</P
-><P
-></P
-></DIV
+></TD
+></TR
+></TABLE
></DIV
->
-
- 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
- <EM
->default assignments</EM
->; the Owner and Q/A Contact fields in a bug
- are otherwise unrelated to the Component.
- </P
-><P
-> To create a new Component:
- </P
-><P
-></P
-><OL
-TYPE="1"
-><LI
><P
-> Select the "Edit components" link from the "Edit Product" page
+> Modify the path to perl on the first line (#!) of all
+ files to point to your Perl installation, and add
+ <SPAN
+CLASS="QUOTE"
+>"perl"</SPAN
+> to the beginning of all Perl system
+ calls that use a perl script as an argument. This may
+ take you a while. There is a <SPAN
+CLASS="QUOTE"
+>"setperl.csh"</SPAN
+>
+ utility to speed part of this procedure, available in the
+ <A
+HREF="#PATCHES"
+>Useful Patches and Utilities for Bugzilla</A
+> section of The Bugzilla Guide.
+ However, it requires the Cygwin GNU-compatible environment
+ for Win32 be set up in order to work. See <A
+HREF="http://www.cygwin.com/"
+TARGET="_top"
+>http://www.cygwin.com/</A
+> for details on obtaining Cygwin.
</P
></LI
><LI
><P
-> Select the "Add" link to the right of the "Add a new component" text
- on the "Select Component" page.
+> Modify the invocation of all system() calls in all perl
+ scripts in your Bugzilla directory. For instance, change
+ this line in processmail:
+ <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>
+system ("./processmail.pl",@ARGLIST);
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+> to
+ <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>
+system ("perl processmail.pl",@ARGLIST);
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
</P
></LI
><LI
><P
-> Fill out the "Component" field, a short "Description", and the "Initial Owner".
- The "Component" field should not contain a space. The "Description" field is
- free-form. The "Initial Owner" field must be that of a valid user already
- existing in the database. If the initial owner does not exist, Bugzilla
- will refuse to create the component.
- <DIV
-CLASS="TIP"
-><BLOCKQUOTE
-CLASS="TIP"
+> Add <TT
+CLASS="FUNCTION"
+>binmode()</TT
+> calls so attachments
+ will work (<A
+HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=62000"
+TARGET="_top"
+>bug 62000</A
+>).
+ </P
+><P
+> Because Microsoft Windows based systems handle binary
+ files different than Unix based systems, you need to add
+ the following lines to
+ <TT
+CLASS="FILENAME"
+>createattachment.cgi</TT
+> and
+ <TT
+CLASS="FILENAME"
+>showattachment.cgi</TT
+> before the
+ <TT
+CLASS="FUNCTION"
+>require 'CGI.pl';</TT
+> line.</P
+><P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>binmode(STDIN);
+binmode(STDOUT);</PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+ </P
+><DIV
+CLASS="NOTE"
><P
-><B
->Tip: </B
-> Is your "Default Owner" a user who is not yet in the database?
- No problem.
- <P
></P
-><OL
-TYPE="a"
-><LI
+><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
-> Select the "Log out" link on the footer of the page.
- </P
+> According to <A
+HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=62000"
+TARGET="_top"
+>bug 62000</A
+>, the perl documentation says that you should always use <TT
+CLASS="FUNCTION"
+>binmode()</TT
+> when dealing with binary files, but never when dealing with text files. That seems to suggest that rather than aribtrarily putting <TT
+CLASS="FUNCTION"
+>binmode()</TT
+> at the begining of the attachment files, there should be logic to determine if <TT
+CLASS="FUNCTION"
+>binmode()</TT
+> is needed or not.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
></LI
-><LI
+></OL
+></DIV
+><DIV
+CLASS="TIP"
><P
-> Select the "New Account" link on the footer of the "Relogin" page
- </P
-></LI
-><LI
+></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
-> Type in the email address of the default owner you want to create
- in the "E-mail address" field, and her full name in the "Real name"
- field, then select the "Submit Query" button.
- </P
-></LI
-><LI
+> 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:
+ </P
><P
-> Now select "Log in" again, type in your login information, and you
- can modify the product to use the Default Owner information
- you require.
- </P
-></LI
-></OL
->
- </P
-></BLOCKQUOTE
+> <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>
+.cgi to: <perl install directory>\perl.exe %s %s
+.pl to: <perl install directory>\perl.exe %s %s
+GET,HEAD,POST
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+ Change the path to Perl to match your
+ install, of course.
+ </P
+></TD
+></TR
+></TABLE
></DIV
->
- </P
-></LI
-><LI
-><P
-> Either "edit" more components or return to the "query" page on the ensuing
- "Addming new component" page. To return to the Product you were editing, you
- must select the "components" link as before.
- </P
-></LI
-></OL
></DIV
><DIV
CLASS="SECTION"
><HR><H2
CLASS="SECTION"
><A
-NAME="VERSIONS"
->3.3.3. Versions</A
+NAME="ADDLWINTIPS"
+>3.6.2. Additional Windows Tips</A
></H2
+><DIV
+CLASS="TIP"
><P
-> Versions are the revisions of the product, such as "Flinders 3.1", "Flinders 95",
- and "Flinders 2000". Using Versions helps you isolate code changes and are an aid
- in reporting.
-
- <DIV
-CLASS="EXAMPLE"
-><A
-NAME="AEN867"
-></A
-><P
-><B
->Example 3-2. Common Use of Versions</B
></P
-><DIV
-CLASS="INFORMALEXAMPLE"
-><A
-NAME="AEN869"
+><TABLE
+CLASS="TIP"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/tip.gif"
+HSPACE="5"
+ALT="Tip"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> From Andrew Pearson:
+ <A
+NAME="AEN1212"
></A
+><BLOCKQUOTE
+CLASS="BLOCKQUOTE"
><P
-></P
+> You can make Bugzilla work with Personal Web Server for
+ Windows 98 and higher, as well as for IIS 4.0.
+ Microsoft has information available at <A
+HREF=" http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP"
+TARGET="_top"
+> http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP</A
+>
+ </P
><P
-> A user reports a bug
- against Version "Beta 2.0" of your product. The current Version of your software
- is "Release Candidate 1", and no longer has the bug. This will
- help you triage and classify bugs according to their relevance. It is also
- possible people may report bugs against bleeding-edge beta versions that are
- not evident in older versions of the software. This can help isolate code
- changes that caused the bug
+> Basically you need to add two String Keys in the
+ registry at the following location:
</P
><P
-></P
-></DIV
-></DIV
+> <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\ScriptMap
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
>
- <DIV
-CLASS="EXAMPLE"
-><A
-NAME="AEN871"
-></A
+ </P
><P
-><B
->Example 3-3. A Different Use of Versions</B
-></P
+> The keys should be called ".pl" and ".cgi", and both
+ should have a value something like:
+ <B
+CLASS="COMMAND"
+>c:/perl/bin/perl.exe "%s" "%s"</B
+>
+ </P
+><P
+> The KB article only talks about .pl, but it goes into
+ more detail and provides a perl test script.
+ </P
+></BLOCKQUOTE
+>
+ </P
+></TD
+></TR
+></TABLE
+></DIV
><DIV
-CLASS="INFORMALEXAMPLE"
+CLASS="TIP"
+><P
+></P
+><TABLE
+CLASS="TIP"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/tip.gif"
+HSPACE="5"
+ALT="Tip"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> If attempting to run Bugzilla 2.12 or older, you will need
+ to remove encrypt() calls from the Perl source. This is
+ <EM
+>not necessary</EM
+> for Bugzilla 2.13 and
+ later, which includes the current release, Bugzilla
+ 2.14.
+ <DIV
+CLASS="EXAMPLE"
><A
-NAME="AEN873"
+NAME="AEN1224"
></A
><P
+><B
+>Example 3-4. Removing encrypt() for Windows NT Bugzilla version
+ 2.12 or earlier</B
></P
><P
-> This field has been used to good effect by an online service provider in a slightly
- different way. They had three versions of the product: "Production", "QA",
- and "Dev". Although it may be the same product, a bug in the development
- environment is not normally as critical as a Production bug, nor does it
- need to be reported publicly. When used in conjunction with Target Milestones,
- one can easily specify the environment where a bug can be reproduced, and
- the Milestone by which it will be fixed.
+> Replace this:
+ <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>
+SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " . SQLQuote(substr($realcryptpwd, 0, 2)) . ")");
+my $enteredcryptpwd = FetchOneColumn();
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+with this:
+ <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>
+my $enteredcryptpwd = $enteredpwd
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+ in cgi.pl.
</P
-><P
-></P
-></DIV
></DIV
>
- </P
-><P
-> To create and edit Versions:
- </P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
-> From the "Edit Product" screen, select "Edit Versions"
- </P
-></LI
-><LI
-><P
-> You will notice that the product already has the default version "undefined".
- If your product doesn't use version numbers, you may want to leave this as it is
- or edit it so that it is "---". You can then go back to the edit versions page
- and add new versions to your product.
- </P
-><P
-> Otherwise, click the "Add" button to the right of the "Add a new version" text.
- </P
-></LI
-><LI
-><P
-> Enter the name of the Version. This can be free-form characters up to the limit of the
- text box. Then select the "Add" button.
- </P
-></LI
-><LI
-><P
-> At this point you can select "Edit" to edit more Versions, or return to the "Query"
- page, from which you can navigate back to the product through the "components" link
- at the foot of the Query page.
- </P
-></LI
-></OL
+ </P
+></TD
+></TR
+></TABLE
+></DIV
></DIV
><DIV
CLASS="SECTION"
><HR><H2
CLASS="SECTION"
><A
-NAME="MILESTONES"
->3.3.4. Milestones</A
+NAME="BZLDAP"
+>3.6.3. Bugzilla LDAP Integration</A
></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 would be assigned the milestone of 3.0. Or, you have a
- bug that you plan to fix for 2.8, this would have a milestone of 2.8.
+> What follows is some late-breaking information on using the
+ LDAP authentication options with Bugzilla. The author has not
+ tested these (nor even formatted this section!) so please
+ contribute feedback to the newsgroup.
</P
+><P
+CLASS="LITERALLAYOUT"
+>Mozilla::LDAP module<br>
+<br>
+The Mozilla::LDAP module allows you to use LDAP for authentication to<br>
+the Bugzilla system. This module is not required if you are not using<br>
+LDAP.<br>
+<br>
+Mozilla::LDAP (aka PerLDAP) is available for download from<br>
+http://www.mozilla.org/directory.<br>
+<br>
+NOTE: The Mozilla::LDAP module requires Netscape's Directory SDK.<br>
+Follow the link for "Directory SDK for C" on that same page to<br>
+download the SDK first. After you have installed this SDK, then<br>
+install the PerLDAP module.<br>
+----------------------------------------------------------------------<br>
+<br>
+Post-Installation Checklist<br>
+----------------------------------------------------------------------<br>
+Set useLDAP to "On" **only** if you will be using an LDAP directory<br>
+for authentication. Be very careful when setting up this parameter;<br>
+if you set LDAP authentication, but do not have a valid LDAP directory<br>
+set up, you will not be able to log back in to Bugzilla once you log<br>
+out. (If this happens, you can get back in by manually editing the<br>
+data/params file, and setting useLDAP back to 0.)<br>
+<br>
+If using LDAP, you must set the three additional parameters:<br>
+<br>
+Set LDAPserver to the name (and optionally port) of your LDAP server.<br>
+If no port is specified, it defaults to the default port of 389. (e.g<br>
+"ldap.mycompany.com" or "ldap.mycompany.com:1234")<br>
+<br>
+Set LDAPBaseDN to the base DN for searching for users in your LDAP<br>
+directory. (e.g. "ou=People,o=MyCompany") uids must be unique under<br>
+the DN specified here.<br>
+<br>
+Set LDAPmailattribute to the name of the attribute in your LDAP<br>
+directory which contains the primary email address. On most directory<br>
+servers available, this is "mail", but you may need to change this.<br>
+----------------------------------------------------------------------<br>
+<br>
+(Not sure where this bit should go, but it's important that it be in<br>
+there somewhere...)<br>
+----------------------------------------------------------------------<br>
+Using LDAP authentication for Bugzilla:<br>
+<br>
+The existing authentication scheme for Bugzilla uses email addresses<br>
+as the primary user ID, and a password to authenticate that user. All<br>
+places within Bugzilla where you need to deal with user ID (e.g<br>
+assigning a bug) use the email address.<br>
+<br>
+The LDAP authentication builds on top of this scheme, rather than<br>
+replacing it. The initial log in is done with a username and password<br>
+for the LDAP directory. This then fetches the email address from LDAP<br>
+and authenticates seamlessly in the standard Bugzilla authentication<br>
+scheme using this email address. If an account for this address<br>
+already exists in your Bugzilla system, it will log in to that<br>
+account. If no account for that email address exists, one is created<br>
+at the time of login. (In this case, Bugzilla will attempt to use the<br>
+"displayName" or "cn" attribute to determine the user's full name.)<br>
+<br>
+After authentication, all other user-related tasks are still handled<br>
+by email address, not LDAP username. You still assign bugs by email<br>
+address, query on users by email address, etc.<br>
+----------------------------------------------------------------------<br>
+ </P
+></DIV
+></DIV
+></DIV
><DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="ADMINISTRATION"
+>Chapter 4. Administering Bugzilla</A
+></H1
+><FONT
+COLOR="RED"
+> Or, I just got this cool thing installed. Now what the heck do I
+ do with it?
+ </FONT
><P
-><B
->Note: </B
-> Milestone options will only appear for a Product if you turned the "usetargetmilestone" field
- in the "Edit Parameters" screen "On".
+> So you followed <SPAN
+CLASS="QUOTE"
+>"<A
+HREF="#INSTALLATION"
+>Bugzilla Installation</A
+>"</SPAN
+> to the
+ letter, and logged into Bugzilla for the very first time with your
+ super-duper god account. You sit, contentedly staring at the
+ Bugzilla Query Screen, the worst of the whole mad business of
+ installing this terrific program behind you. It seems, though, you
+ have nothing yet to query! Your first act of business should be to
+ setup the operating parameters for Bugzilla so you can get busy
+ getting data into your bug tracker.
+ </P
+><DIV
+CLASS="SECTION"
+><HR><H1
+CLASS="SECTION"
+><A
+NAME="POSTINSTALL-CHECK"
+>4.1. Post-Installation Checklist</A
+></H1
+><P
+> After installation, follow the checklist below to help ensure
+ that you have a successful installation. If you do not see a
+ recommended setting for a parameter, consider leaving it at the
+ default while you perform your initial tests on your Bugzilla
+ setup.
+ </P
+><DIV
+CLASS="PROCEDURE"
+><OL
+TYPE="1"
+><LI
+><P
+> Bring up <TT
+CLASS="FILENAME"
+>editparams.cgi</TT
+> in your web
+ browser. This should be available as the <SPAN
+CLASS="QUOTE"
+>"edit
+ parameters"</SPAN
+> link from any Bugzilla screen once you
+ have logged in.
</P
-></BLOCKQUOTE
-></DIV
+></LI
+><LI
+><P
+>The <SPAN
+CLASS="QUOTE"
+>"maintainer"</SPAN
+> is the email address of
+ the person responsible for maintaining this Bugzilla
+ installation. The maintainer need not be a valid Bugzilla
+ user. Error pages, error emails, and administrative mail
+ will be sent with the maintainer as the return email
+ address.</P
+><P
+> Set <SPAN
+CLASS="QUOTE"
+>"maintainer"</SPAN
+> to <EM
+>your</EM
+> email address.
+ This allows Bugzilla's error messages to display your email
+ address and allow people to contact you for help.
+ </P
+></LI
+><LI
><P
-> To create new Milestones, set Default Milestones, and set Milestone URL:
- </P
+>The <SPAN
+CLASS="QUOTE"
+>"urlbase"</SPAN
+> parameter defines the fully
+ qualified domain name and web server path to your Bugzilla
+ installation.</P
><P
-></P
-><OL
-TYPE="1"
+> For example, if your bugzilla query page is
+ http://www.foo.com/bugzilla/query.cgi, set your
+ <SPAN
+CLASS="QUOTE"
+>"urlbase"</SPAN
+> is http://www.foo.com/bugzilla/.
+ </P
+></LI
><LI
><P
-> Select "edit milestones"
- </P
+><SPAN
+CLASS="QUOTE"
+>"usebuggroups"</SPAN
+> dictates whether or not to
+ implement group-based security for Bugzilla. If set,
+ Bugzilla bugs can have an associated groupmask defining
+ which groups of users are allowed to see and edit the
+ bug.</P
+><P
+> Set "usebuggroups" to "on" <EM
+>only</EM
+> if you
+ may wish to restrict access to products. I suggest leaving
+ this parameter <EM
+>off</EM
+> while initially
+ testing your Bugzilla.
+ </P
></LI
><LI
><P
-> Select "Add" to the right of the "Add a new milestone" text
- </P
+> <SPAN
+CLASS="QUOTE"
+>"usebuggroupsentry"</SPAN
+>, when set to
+ <SPAN
+CLASS="QUOTE"
+>"on"</SPAN
+>, requires that all bugs have an associated
+ groupmask when submitted. This parameter is made for those
+ installations where product isolation is a necessity.
+ </P
+><P
+> Set "usebuggroupsentry" to "on" if you absolutely need to
+ restrict access to bugs from the moment they are submitted
+ through resolution. Once again, if you are simply testing
+ your installation, I suggest against turning this parameter
+ on; the strict security checking may stop you from being
+ able to modify your new entries.
+ </P
></LI
><LI
><P
-> 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.
- Select "Add".
- </P
-><DIV
-CLASS="EXAMPLE"
-><A
-NAME="AEN899"
-></A
+> You run into an interesting problem when Bugzilla reaches a
+ high level of continuous activity. MySQL supports only
+ table-level write locking. What this means is that if
+ someone needs to make a change to a bug, they will lock the
+ entire table until the operation is complete. Locking for
+ write also blocks reads until the write is complete. The
+ <SPAN
+CLASS="QUOTE"
+>"shadowdb"</SPAN
+> parameter was designed to get around
+ this limitation. While only a single user is allowed to
+ write to a table at a time, reads can continue unimpeded on
+ a read-only shadow copy of the database. Although your
+ database size will double, a shadow database can cause an
+ enormous performance improvement when implemented on
+ extremely high-traffic Bugzilla databases.
+ </P
><P
-><B
->Example 3-4. Using SortKey with Target Milestone</B
-></P
-><DIV
-CLASS="INFORMALEXAMPLE"
-><A
-NAME="AEN901"
-></A
+> Set "shadowdb" to "bug_shadowdb" if you will be running a
+ *very* large installation of Bugzilla. The shadow database
+ enables many simultaneous users to read and write to the
+ database without interfering with one another.
+ <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
-> Let's say you create a target milestone called "Release 1.0", with Sortkey set to "0".
- Later, you realize that you will have a public beta, called "Beta1".
- You can create a Milestone called "Beta1", with a Sortkey of "-1" in order to ensure
- people will see the Target Milestone of "Beta1" earlier on the list than "Release 1.0"
- </P
-><P
-></P
-></DIV
+> Enabling "shadowdb" can adversely affect the stability
+ of your installation of Bugzilla. You should regularly
+ check that your database is in sync. It is often
+ advisable to force a shadow database sync nightly via
+ <SPAN
+CLASS="QUOTE"
+>"cron"</SPAN
+>.
+ </P
+></TD
+></TR
+></TABLE
></DIV
+> Once again, in testing you should avoid this option
+ -- use it if or when you <EM
+>need</EM
+> to use
+ it, and have repeatedly run into the problem it was designed
+ to solve -- very long wait times while attempting to commit
+ a change to the database. Mozilla.org began needing
+ <SPAN
+CLASS="QUOTE"
+>"shadowdb"</SPAN
+> when they reached around 40,000
+ Bugzilla users with several hundred Bugzilla bug changes and
+ comments per day.
+ </P
+><P
+> If you use the "shadowdb" option, it is only natural that
+ you should turn the "queryagainstshadowdb" option "On" as
+ well. Otherwise you are replicating data into a shadow
+ database for no reason!
+ </P
></LI
><LI
><P
-> If you want to add more milestones, select the "Edit" link.
- If you don't, well shoot, you have to go back to the "query" page and select "components"
- again, and make your way back to the Product you were editing.
- <DIV
+><SPAN
+CLASS="QUOTE"
+>"headerhtml"</SPAN
+>, <SPAN
+CLASS="QUOTE"
+>"footerhtml"</SPAN
+>,
+ <SPAN
+CLASS="QUOTE"
+>"errorhtml"</SPAN
+>, <SPAN
+CLASS="QUOTE"
+>"bannerhtml"</SPAN
+>, and
+ <SPAN
+CLASS="QUOTE"
+>"blurbhtml"</SPAN
+> are all templates which control
+ display of headers, footers, errors, banners, and additional
+ data. We could go into some detail regarding the usage of
+ these, but it is really best just to monkey around with them
+ a bit to see what they do. I strongly recommend you copy
+ your <TT
+CLASS="FILENAME"
+>data/params</TT
+> file somewhere safe
+ before playing with these values, though. If they are
+ changed dramatically, it may make it impossible for you to
+ display Bugzilla pages to fix the problem until you have
+ restored your <TT
+CLASS="FILENAME"
+>data/params</TT
+> file.</P
+><P
+> If you have custom logos or HTML you must put in place to
+ fit within your site design guidelines, place the code in
+ the "headerhtml", "footerhtml", "errorhtml", "bannerhtml",
+ or "blurbhtml" text boxes.
+ <DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><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
-><B
->Note: </B
-> This is another in the list of unusual user interface decisions that
- we'd like to get cleaned up. Shouldn't there be a link to the effect of
- "edit the Product I was editing when I ended up here"? In any case,
- clicking "components" in the footer takes you back to the "Select product"
- screen, from which you can begin editing your product again.
- </P
-></BLOCKQUOTE
+> The "headerhtml" text box is the HTML printed out
+ <EM
+>before</EM
+> any other code on the page,
+ except the CONTENT-TYPE header sent by the Bugzilla
+ engine. If you have a special banner, put the code for
+ it in "bannerhtml". You may want to leave these settings
+ at the defaults initially.
+ </P
+></TD
+></TR
+></TABLE
></DIV
>
- </P
+ </P
></LI
><LI
><P
-> From the Edit Product screen again (once you've made your way back), enter the URL
- for a description of what your milestones are for this product in the "Milestone URL" field.
- It should be of the format "http://www.foo.com/bugzilla/product_milestones.html"
- </P
-><P
-> Some common uses of this field include product descriptions, product roadmaps,
- and of course a simple description of the meaning of each milestone.
- </P
+><SPAN
+CLASS="QUOTE"
+>"passwordmail"</SPAN
+> is rather simple. Every
+ time a user creates an account, the text of this parameter
+ is read as the text to send to the new user along with their
+ password message.</P
+><P
+> Add any text you wish to the "passwordmail" parameter box.
+ For instance, many people choose to use this box to give a
+ quick training blurb about how to use Bugzilla at your site.
+ </P
></LI
><LI
><P
-> If you're using Target Milestones, the "Default Milestone" field must have some
- kind of entry. If you really don't care if people set coherent Target Milestones,
- simply leave this at the default, "---". However, controlling and regularly updating the Default
- Milestone field is a powerful tool when reporting the status of projects.
- </P
-><P
->Select the "Update" button when you are done.</P
-></LI
-><LI
+><SPAN
+CLASS="QUOTE"
+>"useqacontact"</SPAN
+> allows you to define an
+ email address for each component, in addition to that of the
+ default owner, who will be sent carbon copies of incoming
+ bugs. The critical difference between a QA Contact and an
+ Owner is that the QA Contact follows the component. If you
+ reassign a bug from component A to component B, the QA
+ Contact for that bug will change with the reassignment,
+ regardless of owner.</P
><P
->
- </P
+><SPAN
+CLASS="QUOTE"
+>"usestatuswhiteboard"</SPAN
+> defines whether you
+ wish to have a free-form, overwritable field associated with
+ each bug. The advantage of the Status Whiteboard is that it
+ can be deleted or modified with ease, and provides an
+ easily-searchable field for indexing some bugs that have
+ some trait in common. Many people will put <SPAN
+CLASS="QUOTE"
+>"help
+ wanted"</SPAN
+>, <SPAN
+CLASS="QUOTE"
+>"stalled"</SPAN
+>, or <SPAN
+CLASS="QUOTE"
+>"waiting
+ on reply from somebody"</SPAN
+> messages into the Status
+ Whiteboard field so those who peruse the bugs are aware of
+ their status even more than that which can be indicated by
+ the Resolution fields.</P
+><P
+> Do you want to use the QA Contact ("useqacontact") and
+ status whiteboard ("usestatuswhiteboard") fields? These
+ fields are useful because they allow for more flexibility,
+ particularly when you have an existing Quality Assurance
+ and/or Release Engineering team, but they may not be needed
+ for many smaller installations.
+ </P
></LI
-></OL
-></DIV
-><DIV
-CLASS="SECTION"
-><HR><H2
-CLASS="SECTION"
-><A
-NAME="VOTING"
->3.3.5. Voting</A
-></H2
-><P
-> The concept of "voting" is a poorly understood, yet powerful feature for the management
- of open-source projects. Each user is assigned so many Votes per product, which they can
- freely reassign (or assign multiple votes to a single bug).
- 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.
- </P
-><P
-> The daunting challenge of Votes is deciding where you draw the line for a "vocal majority". If you
- only have a user base of 100 users, setting a low threshold for bugs to move from UNCONFIRMED
- to NEW makes sense. As the Bugzilla user base expands, however, these thresholds must be
- re-evaluated. You should gauge whether this feature is worth the time and close monitoring involved,
- and perhaps forego implementation until you have a critical mass of users who demand it.
- </P
-><P
->To modify Voting settings:</P
-><P
-></P
-><OL
-TYPE="1"
><LI
><P
-> Navigate to the "Edit Product" screen for the Product you wish to modify
- </P
+> Set "whinedays" to the amount of days you want to let bugs
+ go in the "New" or "Reopened" state before notifying people
+ they have untouched new bugs. If you do not plan to use
+ this feature, simply do not set up the whining cron job
+ described in the installation instructions, or set this
+ value to "0" (never whine).
+ </P
></LI
><LI
><P
-> Set "Maximum Votes per person" to your calculated value. Setting this field
- to "0" disables voting.
- </P
-></LI
-><LI
+><SPAN
+CLASS="QUOTE"
+>"commenton"</SPAN
+> fields allow you to dictate
+ what changes can pass without comment, and which must have a
+ comment from the person who changed them. Often,
+ administrators will allow users to add themselves to the CC
+ list, accept bugs, or change the Status Whiteboard without
+ adding a comment as to their reasons for the change, yet
+ require that most other changes come with an
+ explanation.</P
><P
-> Set "Maximum Votes a person can put on a single bug" to your calculated value. It
- should probably be some number lower than the "Maximum votes per person".
- Setting this field to "0" disables voting, but leaves the voting options open
- to the user. This is confusing.
- </P
-></LI
-><LI
+> Set the "commenton" options according to your site policy.
+ It is a wise idea to require comments when users resolve,
+ reassign, or reopen bugs at the very least.
+ <DIV
+CLASS="NOTE"
><P
-> Set "Number of votes a bug in this product needs to automatically get out of the
- UNCONFIRMED state" to your calculated number. Setting this field to "0"
- disables the automatic move of bugs from UNCONFIRMED to NEW. Some people
- advocate leaving this at "0", but of what use are Votes if your Bugzilla
- user base is unable to affect which bugs appear on Development radar?
- <DIV
-CLASS="TIP"
-><BLOCKQUOTE
-CLASS="TIP"
+></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
-><B
->Tip: </B
-> You should probably set this number to higher than a small coalition of
- Bugzilla users can influence it. Most sites use this as a "referendum"
- mechanism -- if users are able to vote a bug out of UNCONFIRMED, it
- is a <EM
->really</EM
-> bad bug!
- </P
-></BLOCKQUOTE
+> It is generally far better to require a developer
+ comment when resolving bugs than not. Few things are
+ more annoying to bug database users than having a
+ developer mark a bug "fixed" without any comment as to
+ what the fix was (or even that it was truly fixed!)
+ </P
+></TD
+></TR
+></TABLE
></DIV
>
- </P
+ </P
></LI
><LI
><P
-> Once you have adjusted the values to your preference, select the "Update" button.
- </P
+>The <SPAN
+CLASS="QUOTE"
+>"supportwatchers"</SPAN
+> option can be an
+ exceptionally powerful tool in the hands of a power Bugzilla
+ user. By enabling this option, you allow users to receive
+ email updates whenever other users receive email updates.
+ This is, of course, subject to the groupset restrictions on
+ the bug; if the <SPAN
+CLASS="QUOTE"
+>"watcher"</SPAN
+> would not normally be
+ allowed to view a bug, the watcher cannot get around the
+ system by setting herself up to watch the bugs of someone
+ with bugs outside her priveleges. She would still only
+ receive email updates for those bugs she could normally
+ view.</P
+><P
+>For Bugzilla sites which require strong inter-Product
+ security to prevent snooping, watchers are not a good
+ idea.</P
+><P
+> However, for most sites you should set
+ <SPAN
+CLASS="QUOTE"
+>"supportwatchers"</SPAN
+> to "On". This feature is
+ helpful for team leads to monitor progress in their
+ respective areas, and can offer many other benefits, such as
+ allowing a developer to pick up a former engineer's bugs
+ without requiring her to change all the information in the
+ bug.
+ </P
></LI
></OL
></DIV
+></DIV
><DIV
CLASS="SECTION"
-><HR><H2
+><HR><H1
CLASS="SECTION"
><A
-NAME="GROUPS"
->3.3.6. Groups and Group Security</A
-></H2
+NAME="USERADMIN"
+>4.2. User Administration</A
+></H1
><P
-> Groups can be very useful in bugzilla, because they allow users to isolate
- bugs or products that should only be seen by certain people. Groups can also
- be a complicated minefield of interdependencies and weirdness if mismanaged.
-
- <DIV
-CLASS="EXAMPLE"
+> User administration is one of the easiest parts of Bugzilla.
+ Keeping it from getting out of hand, however, can become a
+ challenge.
+ </P
+><DIV
+CLASS="SECTION"
+><HR><H2
+CLASS="SECTION"
><A
-NAME="AEN937"
-></A
+NAME="DEFAULTUSER"
+>4.2.1. Creating the Default User</A
+></H2
><P
-><B
->Example 3-5. When to Use Group Security</B
-></P
+> 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 were to delete the "super user" account, re-running
+ checksetup.pl will again prompt you for this username and
+ password.
+ </P
><DIV
-CLASS="INFORMALEXAMPLE"
-><A
-NAME="AEN939"
-></A
+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
-> Many Bugzilla sites isolate "Security-related" bugs from all other bugs.
- This way, they can have a fix ready before the security vulnerability
- is announced to the world. You can create a "Security" product which, by
- default, has no members, and only add members to the group (in their individual
- User page, as described under User Administration) who should have
- priveleged access to "Security" bugs. Alternately, you may create a Group
- independently of any Product, and change the Group mask on individual bugs
- to restrict access to members only of certain Groups.
- </P
-><P
-></P
-></DIV
-></DIV
+> If you wish to add more administrative users, you must use the
+ MySQL interface. Run "mysql" from the command line, and use
+ these commands ("mysql>" denotes the mysql prompt, not
+ something you should type in):
+ <B
+CLASS="COMMAND"
+><TT
+CLASS="PROMPT"
+>mysql></TT
+> use bugs;</B
+>
+ <B
+CLASS="COMMAND"
+><TT
+CLASS="PROMPT"
+>mysql></TT
+> update profiles set
+ groupset=0x7ffffffffffffff where login_name = "(user's
+ login name)"; </B
>
-
- Groups only work if you enable the "usebuggroups" paramater.
- In addition, if the "usebuggroupsentry" parameter is "On", one can restrict access
- to products by groups, so that only members of a product group are able to view
- bugs within that product.
- Group security in Bugzilla can be divided into two categories:
- Generic and Product-Based.
- </P
-><DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
-><P
-><B
->Note: </B
-> Groups in Bugzilla are a complicated beast that evolved out of very simple user
- permission bitmasks, apparently itself derived from common concepts in UNIX access
- controls. A "bitmask" is a fixed-length number whose value can describe one, and
- only one, set of states. For instance, UNIX file permissions are assigned bitmask
- values: "execute" has a value of 1, "write" has a value of 2,
- and "read" has a value of 4. Add them together,
- and a file can be read, written to, and executed if it has a bitmask of "7". (This
- is a simplified example -- anybody who knows UNIX security knows there is much
- more to it than this. Please bear with me for the purpose of this note.) The only
- way a bitmask scheme can work is by doubling the bit count for each value. Thus
- if UNIX wanted to offer another file permission, the next would have to be a value of
- 8, then the next 16, the next 32, etc.
</P
><P
-> Similarly, Bugzilla offers a bitmask to define group permissions, with an internal
- limit of 64. Several are already occupied
- by built-in permissions. The way around this limitation is
- to avoid assigning groups to products if you have many products, avoid bloating
- of group lists, and religiously prune irrelevant groups. In reality, most installations
- of Bugzilla support far fewer than 64 groups, so this limitation has not hit
- for most sites, but it is on the table to be revised for Bugzilla 3.0
- because it interferes with the security schemes of some administrators.
- </P
-></BLOCKQUOTE
+>Yes, that is <EM
+>fourteen</EM
+>
+ <SPAN
+CLASS="QUOTE"
+>"f"</SPAN
+>'s. A whole lot of f-ing going on if you
+ want to create a new administator.</P
+></TD
+></TR
+></TABLE
></DIV
-><P
-> To enable Generic Group Security ("usebuggroups"):
- </P
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H2
+CLASS="SECTION"
+><A
+NAME="MANAGEUSERS"
+>4.2.2. Managing Other Users</A
+></H2
+><DIV
+CLASS="SECTION"
+><H3
+CLASS="SECTION"
+><A
+NAME="LOGIN"
+>4.2.2.1. Logging In</A
+></H3
><P
></P
><OL
TYPE="1"
><LI
><P
-> Turn "On" "usebuggroups" in the "Edit Parameters" screen.
- </P
+> Open the index.html page for your Bugzilla installation
+ in your browser window.
+ </P
></LI
><LI
><P
-> You will generally have no groups set up. Select the "groups" link
- in the footer.
- </P
+> Click the "Query Existing Bug Reports" link.
+ </P
></LI
><LI
><P
-> Take a moment to understand the instructions on the "Edit Groups" screen.
- Once you feel confident you understand what is expected of you, select the
- "Add Group" link.
- </P
+> Click the "Log In" link at the foot of the page.
+ </P
></LI
><LI
><P
-> Fill out the "New Name" (remember, no spaces!), "New Description", and "New
- User RegExp" fields. "New User RegExp" allows you to automatically place
- all users who fulfill the Regular Expression into the new group.
-
- <DIV
-CLASS="EXAMPLE"
-><A
-NAME="AEN954"
-></A
+> Type your email address, and the password which was
+ emailed to you when you created your Bugzilla account,
+ into the spaces provided.
+ </P
+></LI
+></OL
><P
-><B
->Example 3-6. Creating a New Group</B
-></P
+>Congratulations, you are logged in!</P
+></DIV
><DIV
-CLASS="INFORMALEXAMPLE"
+CLASS="SECTION"
+><HR><H3
+CLASS="SECTION"
><A
-NAME="AEN956"
-></A
-><P
-></P
+NAME="CREATENEWUSERS"
+>4.2.2.2. Creating new users</A
+></H3
><P
-> I created a group called "DefaultGroup" with a description of "This is simply
- a group to play with", and a "New User RegExp" of "*@velio.com". This
- new group automatically includes all Bugzilla users with "@velio.com" at the
- end of their user id. When I finished, my new group was assigned bit #128.
- </P
+> Your users can create their own user accounts by clicking
+ the "New Account" link at the bottom of each page. However,
+ should you desire to create user accounts ahead of time,
+ here is how you do it.
+ </P
><P
></P
-></DIV
-></DIV
->
-
- When you have finished, select the "Add" button.
- </P
+><OL
+TYPE="1"
+><LI
+><P
+> After logging in, click the "Users" link at the footer
+ of the query page.
+ </P
></LI
-></OL
+><LI
><P
-> To enable Product-Based Group Security ("usebuggroupsentry"):
- </P
+> To see a specific user, type a portion of their login
+ name in the box provided and click "submit". To see all
+ users, simply click the "submit" button. You must click
+ "submit" here to be able to add a new user.
+ </P
><DIV
-CLASS="WARNING"
+CLASS="TIP"
><P
></P
><TABLE
-CLASS="WARNING"
-BORDER="1"
-WIDTH="100%"
+CLASS="TIP"
+WIDTH="90%"
+BORDER="0"
><TR
><TD
+WIDTH="25"
ALIGN="CENTER"
-><B
->Warning</B
-></TD
-></TR
-><TR
+VALIGN="TOP"
+><IMG
+SRC="../images/tip.gif"
+HSPACE="5"
+ALT="Tip"></TD
><TD
ALIGN="LEFT"
+VALIGN="TOP"
><P
-> Don't forget that you only have 64 groups masks available, total, for
- your installation of Bugzilla! If you plan on having more than 50
- products in your individual Bugzilla installation, and require group
- security for your products, you should
- consider either running multiple Bugzillas or using Generic Group Security
- instead of Product-Based ("usebuggroupsentry") Group Security.
- </P
+> More functionality is available via the list on the
+ right-hand side of the text entry box. You can match
+ what you type as a case-insensitive substring (the
+ default) of all users on your system, a case-sensitive
+ regular expression (please see the <B
+CLASS="COMMAND"
+>man
+ regexp</B
+> manual page for details on regular
+ expression syntax), or a <EM
+>reverse</EM
+>
+ regular expression match, where every user name which
+ does NOT match the regular expression is selected.
+ </P
></TD
></TR
></TABLE
></DIV
+></LI
+><LI
><P
-></P
-><OL
-TYPE="1"
+> Click the "Add New User" link at the bottom of the user
+ list
+ </P
+></LI
><LI
><P
-> Turn "On" "usebuggroups" and "usebuggroupsentry" in the "Edit Parameters" screen.
- </P
+> Fill out the form presented. This page is
+ self-explanatory. When done, click "submit".
+ </P
><DIV
-CLASS="WARNING"
+CLASS="NOTE"
><P
></P
><TABLE
-CLASS="WARNING"
-BORDER="1"
+CLASS="NOTE"
WIDTH="90%"
+BORDER="0"
><TR
><TD
+WIDTH="25"
ALIGN="CENTER"
-><B
->Warning</B
-></TD
-></TR
-><TR
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
><TD
ALIGN="LEFT"
+VALIGN="TOP"
><P
-> "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, Products, etc. with the administrative account.
- </P
+> Adding a user this way will <EM
+>not</EM
+>
+ send an email informing them of their username and
+ password. While useful for creating dummy accounts
+ (watchers which shuttle mail to another system, for
+ instance, or email addresses which are a mailing
+ list), in general it is preferable to log out and use
+ the <SPAN
+CLASS="QUOTE"
+>"New Account"</SPAN
+> button to create users,
+ as it will pre-populate all the required fields and
+ also notify the user of her account name and
+ password.
+ </P
></TD
></TR
></TABLE
></DIV
></LI
-><LI
-><P
-> You will generally have no Groups set up, unless you enabled "usebuggroupsentry"
- prior to creating any Products. To create "Generic Group Security" groups,
- follow the instructions given above. To create Product-Based Group security,
- simply follow the instructions for creating a new Product. If you need to
- add users to these new groups as you create them, you will find the option
- to add them to the group available under the "Edit User" screens.
- </P
-></LI
></OL
></DIV
-></DIV
><DIV
CLASS="SECTION"
-><HR><H1
+><HR><H3
CLASS="SECTION"
><A
-NAME="SECURITY"
->3.4. Bugzilla Security</A
-></H1
+NAME="DISABLEUSERS"
+>4.2.2.3. Disabling Users</A
+></H3
+><P
+> I bet you noticed that big "Disabled Text" entry box
+ available from the "Add New User" screen, when you edit an
+ account? By entering any text in this box and selecting
+ "submit", you have prevented the user from using Bugzilla
+ via the web interface. Your explanation, written in this
+ text box, will be presented to the user the next time she
+ attempts to use the system.
+ <DIV
+CLASS="WARNING"
+><P
+></P
><TABLE
-BORDER="0"
+CLASS="WARNING"
WIDTH="100%"
-CELLSPACING="0"
-CELLPADDING="0"
-CLASS="EPIGRAPH"
+BORDER="0"
><TR
><TD
-WIDTH="45%"
-> </TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/warning.gif"
+HSPACE="5"
+ALT="Warning"></TD
><TD
-WIDTH="45%"
ALIGN="LEFT"
VALIGN="TOP"
-><I
><P
-><I
->Putting your money in a wall safe is better protection than depending on the fact that
- no one knows that you hide your money in a mayonnaise jar in your fridge.</I
-></P
-></I
+> Don't disable your own administrative account, or you
+ will hate life!
+ </P
+><P
+>At this time, <SPAN
+CLASS="QUOTE"
+>"Disabled Text"</SPAN
+> does not
+ prevent a user from using the email interface. If you
+ have the email interface enabled, they can still
+ continue to submit bugs and comments that way. We need
+ a patch to fix this.</P
></TD
></TR
></TABLE
-><DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
-><P
-><B
->Note: </B
-> Poorly-configured MySQL, Bugzilla, and FTP installations have given attackers full
- access to systems in the past. Please take these guidelines seriously, even
- for Bugzilla machines hidden away behind your firewall. 80% of all computer
- trespassers are insiders, not anonymous crackers.
- </P
-></BLOCKQUOTE
></DIV
-><P
-> First thing's first: Secure your installation.
- <DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
-><P
-><B
->Note: </B
-> 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"
-TARGET="_top"
->mozilla-webtools@mozilla.org</A
>
</P
-></BLOCKQUOTE
></DIV
->
- <P
+><DIV
+CLASS="SECTION"
+><HR><H3
+CLASS="SECTION"
+><A
+NAME="MODIFYUSERS"
+>4.2.2.4. Modifying Users</A
+></H3
+><P
+> Here I will attempt to describe the function of each option
+ on the Edit User screen.
+ </P
+><P
></P
-><OL
-TYPE="1"
+><UL
><LI
><P
-> Ensure you are running at least MysQL version 3.22.32 or newer. Earlier versions had
- notable security holes and poorly secured default configuration choices.
- </P
-></LI
-><LI
+> <EM
+>Login Name</EM
+>: This is generally the
+ user's email address. However, if you have edited your
+ system parameters, this may just be the user's login
+ name or some other identifier.
+ <DIV
+CLASS="TIP"
><P
-><EM
->There is no substitute for understanding the tools on your system!</EM
->
- Read <A
-HREF="http://www.mysql.com/documentation/mysql/bychapter/manual_Privilege_system.html"
-TARGET="_top"
-> The MySQL Privelege System</A
-> until you can recite it from memory!</P
+></P
+><TABLE
+CLASS="TIP"
+WIDTH="90%"
+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
-> At the very least, ensure you password the "mysql -u root" account and the "bugs" account, establish grant
- table rights (consult the Keystone guide in Appendix C: The Bugzilla Database for some easy-to-use details)
- that do not allow CREATE, DROP, RELOAD, SHUTDOWN, and PROCESS for user "bugs". I wrote up the Keystone
- advice back when I knew far less about security than I do now : )
- </P
+> For compatability reasons, you should probably stick
+ with email addresses as user login names. It will
+ make your life easier.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+>
+ </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
+> <EM
+>Real Name</EM
+>: Duh!
+ </P
></LI
><LI
><P
->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.</P
+> <EM
+>Password</EM
+>: You can change the user
+ password here. It is normal to only see asterisks.
+ </P
></LI
><LI
><P
-> Ensure you have adequate access controls for the $BUGZILLA_HOME/data/ and
- $BUGZILLA_HOME/shadow/ directories, as well as the $BUGZILLA_HOME/localconfig file.
- The localconfig file stores your "bugs" user password,
- which would be terrible to have in the hands
- of a criminal. Also some files under $BUGZILLA_HOME/data/ store sensitive information, and
- $BUGZILLA_HOME/shadow/ stores bug information for faster retrieval. If you fail to secure
- these directories and this file, you will expose bug information to those who may not
- be allowed to see it.
- </P
+> <EM
+>Email Notification</EM
+>: You may choose
+ from one of three options:
+ <P
+></P
+><OL
+TYPE="1"
+><LI
><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"
-TARGET="_top"
-> Bug 65572</A
-> for adequate protection in your data/ and shadow/ directories.
- </P
+> All qualifying bugs except those which I change:
+ The user will be notified of any change to any bug
+ for which she is the reporter, assignee, QA
+ Contact, CC recipient, or "watcher".
+ </P
+></LI
+><LI
><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
+> Only those bugs which I am listed on the CC line:
+ The user will not be notified of changes to bugs
+ where she is the assignee, reporter, or QA
+ Contact, but will receive them if she is on the CC
+ list.
+ <DIV
+CLASS="NOTE"
><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><br>
- allow from all<br>
- </Files><br>
- deny from all<br>
- </P
->
- </P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="90%"
+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
-> Place the following text into a file named ".htaccess", readable by your web server,
- in your $BUGZILLA_HOME/ directory.
- <P
-CLASS="LITERALLAYOUT"
-> <Files localconfig><br>
- deny from all<br>
- </Files><br>
- allow from all<br>
- </P
+> She will still receive whining cron emails if
+ you set up the "whinemail" feature.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
>
- </P
+ </P
+></LI
+><LI
><P
-> Place the following text into a file named ".htaccess", readable by your web server,
- in your $BUGZILLA_HOME/shadow directory.
- <P
-CLASS="LITERALLAYOUT"
-> deny from all<br>
- </P
->
- </P
+> <EM
+>All Qualifying Bugs</EM
+>: This
+ user is a glutton for punishment. If her name is
+ in the reporter, QA Contact, CC, assignee, or is a
+ "watcher", she will get email updates regarding
+ the bug.
+ </P
></LI
></OL
->
- </P
-></DIV
-></DIV
-><DIV
-CLASS="CHAPTER"
-><HR><H1
-><A
-NAME="USING"
->Chapter 4. Using Bugzilla</A
-></H1
+></P
+><P
+> <EM
+>Disable Text</EM
+>: If you type anything
+ in this box, including just a space, the user account is
+ disabled from making any changes to bugs via the web
+ interface, and what you type in this box is presented as
+ the reason.
+ <DIV
+CLASS="WARNING"
+><P
+></P
><TABLE
+CLASS="WARNING"
+WIDTH="90%"
BORDER="0"
-WIDTH="100%"
-CELLSPACING="0"
-CELLPADDING="0"
-CLASS="EPIGRAPH"
><TR
><TD
-WIDTH="45%"
-> </TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/warning.gif"
+HSPACE="5"
+ALT="Warning"></TD
><TD
-WIDTH="45%"
ALIGN="LEFT"
VALIGN="TOP"
-><I
><P
-><I
->What, Why, How, & What's in it for me?</I
-></P
-></I
+>Don't disable the administrator account!</P
></TD
></TR
></TABLE
-><DIV
-CLASS="SECTION"
-><HR><H1
-CLASS="SECTION"
-><A
-NAME="WHATIS"
->4.1. What is Bugzilla?</A
-></H1
-><P
-> Bugzilla is one example of a class of programs called "Defect Tracking Systems",
- or, more commonly, "Bug-Tracking Systems". Defect Tracking Systems allow individual or
- groups of developers to keep track of outstanding bugs in their product effectively.
- Bugzilla was originally written by Terry Weissman in a programming language called
- "TCL", to replace a crappy
- bug-tracking database used internally for Netscape Communications. Terry later ported
- Bugzilla to
- Perl from TCL, and in Perl it remains to this day.
- Most commercial defect-tracking software vendors at the
- time charged enormous licensing fees, and Bugzilla quickly became a favorite of the
- open-source crowd (with its genesis in the open-source browser project, Mozilla). It
- is now the de-facto standard defect-tracking system against which all others are
- measured.
- </P
+></DIV
+>
+ <DIV
+CLASS="NOTE"
><P
-> Bugzilla has matured immensely, and now boasts many advanced features. These include:
- <P
></P
-><UL
-><LI
+><TABLE
+CLASS="NOTE"
+WIDTH="90%"
+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
-> integrated, product-based granular security schema
- </P
+> As of this writing, the user can still submit bugs
+ via the e-mail gateway, if you set it up, despite
+ the disabled text field. The e-mail gateway should
+ <EM
+>not</EM
+> be enabled for secure
+ installations of Bugzilla.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+>
+ </P
></LI
><LI
><P
-> inter-bug dependencies and dependency graphing
- </P
+> <EM
+>CanConfirm</EM
+>: This field is only used
+ if you have enabled "unconfirmed" status in your
+ parameters screen. If you enable this for a user, that
+ user can then move bugs from "Unconfirmed" to
+ "Confirmed" status (e.g.: "New" status). Be judicious
+ about allowing users to turn this bit on for other
+ users.
+ </P
></LI
><LI
><P
-> advanced reporting capabilities
- </P
+> <EM
+>Creategroups</EM
+>: This option will
+ allow a user to create and destroy groups in Bugzilla.
+ Unless you are using the Bugzilla GroupSentry security
+ option "usebuggroupsentry" in your parameters, this
+ setting has no effect.
+ </P
></LI
><LI
><P
-> a robust, stable RDBMS back-end
- </P
-></LI
-><LI
+> <EM
+>Editbugs</EM
+>: Unless a user has this
+ bit set, they can only edit those bugs for which they
+ are the assignee or the reporter.
+ <DIV
+CLASS="NOTE"
><P
-> extensive configurability
- </P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="90%"
+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
+> Leaving this option unchecked does not prevent users
+ from adding comments to a bug! They simply cannot
+ change a bug priority, severity, etc. unless they
+ are the assignee or reporter.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+>
+ </P
></LI
><LI
><P
-> a very well-understood and well-thought-out natural bug resolution protocol
- </P
+> <EM
+>Editcomponents</EM
+>: This flag allows a
+ user to create new products and components, as well as
+ modify and destroy those that have no bugs associated
+ with them. If a product or component has bugs
+ associated with it, those bugs must be moved to a
+ different product or component before Bugzilla will
+ allow them to be destroyed. The name of a product or
+ component can be changed without affecting the
+ associated bugs, but it tends to annoy the hell out of
+ your users when these change a lot.
+ </P
></LI
><LI
><P
-> email, XML, and HTTP APIs
- </P
+> <EM
+>Editkeywords</EM
+>: If you use Bugzilla's
+ keyword functionality, enabling this feature allows a
+ user can create and destroy keywords. As always, the
+ keywords for existing bugs containing the keyword the
+ user wishes to destroy must be changed before Bugzilla
+ will allow it to die. You must be very careful about
+ creating too many new keywords if you run a very large
+ Bugzilla installation; keywords are global variables
+ across products, and you can often run into a phenomenon
+ called "keyword bloat". This confuses users, and then
+ the feature goes unused.
+ </P
></LI
><LI
><P
-> available integration with automated software configuration management systems, including
- Perforce and CVS.
- </P
+> <EM
+>Editusers</EM
+>: This flag allows a user
+ do what you're doing right now: edit other users. This
+ will allow those with the right to do so to remove
+ administrator priveleges from other users or grant them
+ to themselves. Enable with care.
+ </P
></LI
><LI
><P
-> too many more features to list
- </P
+> <EM
+>PRODUCT</EM
+>: PRODUCT bugs access. This
+ allows an administrator, with product-level granularity,
+ to specify in which products a user can edit bugs. The
+ user must still have the "editbugs" privelege to edit
+ bugs in this area; this simply restricts them from even
+ seeing bugs outside these boundaries if the
+ administrator has enabled the group sentry parameter
+ "usebuggroupsentry". Unless you are using bug groups,
+ this option has no effect.
+ </P
></LI
></UL
->
- </P
-><P
-> Despite its current robustness and popularity, however, Bugzilla
- faces some near-term challenges, such as reliance on a single database, a lack of
- abstraction of the user interface and program logic, verbose email bug
- notifications, a powerful but daunting query interface, little reporting configurability,
- problems with extremely large queries, some unsupportable bug resolution options,
- no internationalization, and dependence on some nonstandard libraries.
- </P
-><P
-> Some recent headway has been made on the query front, however. If you are using the latest
- version of Bugzilla, you should see a "simple search" form on the default front page of
- your Bugzilla install. Type in two or three search terms and you should pull up some
- relevant information. This is also available as "queryhelp.cgi".
- </P
-><P
-> Despite these small problems, Bugzilla is very hard to beat. It is under <EM
->very</EM
->
- active development to address the current issues, and a long-awaited overhaul in the form
- of Bugzilla 3.0 is expected sometime later this year.
- </P
+></DIV
+></DIV
></DIV
><DIV
CLASS="SECTION"
><HR><H1
CLASS="SECTION"
><A
-NAME="WHY"
->4.2. Why Should We Use Bugzilla?</A
+NAME="PROGRAMADMIN"
+>4.3. Product, Component, Milestone, and Version
+ Administration</A
></H1
><TABLE
BORDER="0"
@@ -5556,158 +8806,187 @@ VALIGN="TOP"
><I
><P
><I
->No, Who's on first...</I
+>Dear Lord, we have to get our users to do WHAT?</I
></P
></I
></TD
></TR
></TABLE
+><DIV
+CLASS="SECTION"
+><HR><H2
+CLASS="SECTION"
+><A
+NAME="PRODUCTS"
+>4.3.1. Products</A
+></H2
+><FONT
+COLOR="RED"
+>Formerly, and in some spots still, called
+ "Programs"</FONT
><P
-> 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
- </P
-><P
-> 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.
- </P
+> <A
+HREF="#GLOSS_PRODUCT"
+><I
+CLASS="GLOSSTERM"
+>Products</I
+></A
+> are
+ the broadest category in Bugzilla, and you should have the
+ least of these. If your company makes computer games, you
+ should have one product per game, and possibly a few special
+ products (website, meetings...)
+ </P
><P
-> But why should <EM
->you</EM
-> use Bugzilla?
- </P
+> A Product (formerly called "Program", and still referred to
+ that way in some portions of the source code) controls some
+ very important functions. The number of "votes" available for
+ users to vote for the most important bugs is set per-product,
+ as is the number of votes required to move a bug automatically
+ from the UNCONFIRMED status to the NEW status. One can close
+ a Product for further bug entry and define various Versions
+ available from the Edit product screen.
+ </P
><P
-> 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, Loki software,
- Linux-Mandrake, and VA Systems. Combined with systems such as CVS, Bonsai,
- or Perforce SCM, Bugzilla provides a powerful, easy-to-use solution to
- configuration management and replication problems
- </P
+>To create a new product:</P
><P
-> 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 by using Bugzilla's e-mail integration features
- be able to follow the discussion trail that led to critical decisions.
- </P
+></P
+><OL
+TYPE="1"
+><LI
><P
-> 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.
- </P
-></DIV
+> Select "components" from the yellow footer
+ </P
><DIV
-CLASS="SECTION"
-><HR><H1
-CLASS="SECTION"
-><A
-NAME="HOW"
->4.3. How do I use Bugzilla?</A
-></H1
+CLASS="TIP"
+><P
+></P
><TABLE
+CLASS="TIP"
+WIDTH="90%"
BORDER="0"
-WIDTH="100%"
-CELLSPACING="0"
-CELLPADDING="0"
-CLASS="EPIGRAPH"
><TR
><TD
-WIDTH="45%"
-> </TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/tip.gif"
+HSPACE="5"
+ALT="Tip"></TD
><TD
-WIDTH="45%"
ALIGN="LEFT"
VALIGN="TOP"
-><I
><P
-><I
->Hey! I'm Woody! Howdy, Howdy, Howdy!</I
+> It may seem counterintuitive to click "components" when
+ you want to edit the properties associated with
+ Products. This is one of a long list of things we want
+ in Bugzilla 3.0...
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+></LI
+><LI
+><P
+> Select the "Add" link to the right of "Add a new product".
+ </P
+></LI
+><LI
+><P
+> Enter the name of the product and a description. The
+ Description field is free-form.
+ </P
+></LI
+></OL
+><DIV
+CLASS="TIP"
+><P
></P
-></I
+><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
+> Don't worry about the "Closed for bug entry", "Maximum Votes
+ per person", "Maximum votes a person can put on a single
+ bug", "Number of votes a bug in this Product needs to
+ automatically get out of the UNCOMFIRMED state", and
+ "Version" options yet. We'll cover those in a few moments.
+ </P
></TD
></TR
></TABLE
-><P
-> Bugzilla is a large, complex system. Describing how to use it
- requires some time. If you are only interested in installing or administering
- a Bugzilla installation, please consult the Installing and Administering
- Bugzilla portions of this Guide. This section is principally aimed towards
- developing end-user mastery of Bugzilla, so you may fully enjoy the benefits
- afforded by using this reliable open-source bug-tracking software.
- </P
-><P
-> Throughout this portion of the Guide, we will refer to user account
- options available at the Bugzilla test installation,
- <A
-HREF="http://landfill.tequilarista.org/"
-TARGET="_top"
-> landfill.tequilarista.org</A
->.
- <DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
-><P
-><B
->Note: </B
-> Some people have run into difficulties completing this tutorial. If
- you run into problems, please check the updated, online documentation available
- at <A
-HREF="http://www.trilobyte.net/barnsons/"
-TARGET="_top"
->http://www.trilobyte.net/barnsons</A
->.
- If you're still stumped, please subscribe to the newsgroup and provide details of exactly
- what's stumping you! If enough people complain, I'll have to fix it in the next
- version of this Guide. You can subscribe to the newsgroup at
- <A
-HREF="news://news.mozilla.org/netscape.public.mozilla.webtools"
-TARGET="_top"
-> news://news.mozilla.org/netscape.public.mozilla.webtools</A
->
- </P
-></BLOCKQUOTE
></DIV
->
- Although Landfill serves as a great introduction to Bugzilla, it does not offer
- all the options you would have as a user on your own installation of Bugzilla,
- nor can it do more than serve as a general introduction to Bugzilla. Additionally,
- Landfill often runs cutting-edge versions of Bugzilla for testing, so some things
- may work slightly differently than mentioned here.
- </P
+></DIV
><DIV
CLASS="SECTION"
><HR><H2
CLASS="SECTION"
><A
-NAME="MYACCOUNT"
->4.3.1. Create a Bugzilla Account</A
+NAME="COMPONENTS"
+>4.3.2. Components</A
></H2
><P
-> First thing's first! 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 the end-user Bugzilla experience, use this URL:
- <A
-HREF="http://landfill.tequilarista.org/mozilla/bugzilla/"
-TARGET="_top"
-> http://landfill.tequilarista.org/mozilla/bugzilla/</A
->
+> Components are subsections of a Product.
+
+ <DIV
+CLASS="EXAMPLE"
+><A
+NAME="AEN1461"
+></A
+><P
+><B
+>Example 4-1. Creating some Components</B
+></P
+><DIV
+CLASS="INFORMALEXAMPLE"
+><A
+NAME="AEN1463"
+></A
+><P
+></P
+><P
+> 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.
+ </P
+><P
+></P
+></DIV
+></DIV
+> 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 <EM
+>default assignments</EM
+>; the
+ Owner and QA Contact fields in a bug are otherwise unrelated
+ to the Component.
+ </P
+><P
+> To create a new Component:
</P
><P
></P
@@ -5715,66 +8994,80 @@ TARGET="_top"
TYPE="1"
><LI
><P
-> Click the "Open a new Bugzilla account" link.
- </P
-></LI
-><LI
-><P
-> Enter your "E-mail address" and "Real Name" (or whatever name you want to call yourself)
- in the spaces provided, then select the "Create Account" button.
+> Select the "Edit components" link from the "Edit product"
+ page
</P
></LI
><LI
><P
-> Within 5-10 minutes, you should receive an email to the address you provided above,
- which contains your login name (generally the same as the email address), and
- a password you can use to access your account. This password is randomly generated,
- and should be changed at your nearest opportunity (we'll go into how to do it later).
+> Select the "Add" link to the right of the "Add a new
+ component" text on the "Select Component" page.
</P
></LI
><LI
><P
-> Click the "Log In" link in the yellow area at the bottom of the page in your browser,
- then enter your "E-mail address" and "Password" you just received into the spaces provided,
- and select "Login".
- <DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
-><P
-><B
->Note: </B
-> If you ever forget your password, you can come back to this page, enter your
- "E-mail address", then select the "E-mail me a password" button to have your password
- mailed to you again so that you can login.
- </P
-></BLOCKQUOTE
-></DIV
->
+> Fill out the "Component" field, a short "Description", and
+ the "Initial Owner". The Component and Description fields
+ are free-form; the "Initial Owner" field must be that of a
+ user ID already existing in the database. If the initial
+ owner does not exist, Bugzilla will refuse to create the
+ component.
<DIV
-CLASS="CAUTION"
+CLASS="TIP"
><P
></P
><TABLE
-CLASS="CAUTION"
-BORDER="1"
+CLASS="TIP"
WIDTH="90%"
+BORDER="0"
><TR
><TD
+WIDTH="25"
ALIGN="CENTER"
-><B
->Caution</B
-></TD
-></TR
-><TR
+VALIGN="TOP"
+><IMG
+SRC="../images/tip.gif"
+HSPACE="5"
+ALT="Tip"></TD
><TD
ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> Is your "Default Owner" a user who is not yet in the
+ database? No problem.
+ <P
+></P
+><OL
+TYPE="a"
+><LI
+><P
+> Select the "Log out" link on the footer of the
+ page.
+ </P
+></LI
+><LI
+><P
+> Select the "New Account" link on the footer of
+ the "Relogin" page
+ </P
+></LI
+><LI
+><P
+> Type in the email address of the default owner
+ you want to create in the "E-mail address"
+ field, and her full name in the "Real name"
+ field, then select the "Submit Query" button.
+ </P
+></LI
+><LI
><P
-> Many modern browsers include an "Auto-Complete" or "Form Fill" feature to
- remember the user names and passwords you type in at many sites. Unfortunately,
- sometimes they attempt to "guess" what you will put in as your password, and guess
- wrong. If you notice a text box is already filled out, please overwrite the contents
- of the text box so you can be sure to input the correct information.
+> Now select "Log in" again, type in your login
+ information, and you can modify the product to
+ use the Default Owner information you require.
+ </P
+></LI
+></OL
+>
</P
></TD
></TR
@@ -5783,61 +9076,95 @@ ALIGN="LEFT"
>
</P
></LI
-></OL
+><LI
><P
-> Congratulations! If you followed these directions, you now are the
- proud owner of a user account on landfill.tequilarista.org (Landfill) or
- your local Bugzilla install. You should now see in your browser a
- page called the "Bugzilla Query Page". It may look daunting, but
- with this Guide to walk you through it, you will master it in no time.
- </P
+> Either Edit more components or return to the Bugzilla
+ Query Page. To return to the Product you were editing, you
+ must select the Components link as before.
+ </P
+></LI
+></OL
></DIV
><DIV
CLASS="SECTION"
><HR><H2
CLASS="SECTION"
><A
-NAME="QUERY"
->4.3.2. The Bugzilla Query Page</A
+NAME="VERSIONS"
+>4.3.3. Versions</A
></H2
><P
-> The Bugzilla Query Page is the heart and soul of Bugzilla. It is the master
- interface where you can find any bug report, comment, or patch currently in the Bugzilla
- system. We'll go into how to create your own bug report later on.
- </P
+> Versions are the revisions of the product, such as "Flinders
+ 3.1", "Flinders 95", and "Flinders 2000". Using Versions
+ helps you isolate code changes and are an aid in reporting.
+
+ <DIV
+CLASS="EXAMPLE"
+><A
+NAME="AEN1490"
+></A
><P
-> There are efforts underway to simplify query usage. If you have a local installation
- of Bugzilla 2.12 or higher, you should have "quicksearch.html" available
- to use and simplify your searches. There is also, or shortly will be, a helper
- for the query interface, called "queryhelp.cgi". Landfill tends to run the latest code,
- so these two utilities should be available there for your perusal.
- </P
+><B
+>Example 4-2. Common Use of Versions</B
+></P
+><DIV
+CLASS="INFORMALEXAMPLE"
+><A
+NAME="AEN1492"
+></A
><P
-> At this point, please visit the main Bugzilla site,
- <A
-HREF="http://bugzilla.mozilla.org/query.cgi"
-TARGET="_top"
-> bugzilla.mozilla.org</A
->, to see a more fleshed-out query page.
- </P
+></P
><P
-> The first thing you need to notice about the Bugzilla Query Page is that
- nearly every box you see on your screen has a hyperlink nearby, explaining what
- it is or what it does. Near the upper-left-hand corner of your browser window
- you should see the word "Status" underlined. Select it.
- </P
+> A user reports a bug against Version "Beta 2.0" of your
+ product. The current Version of your software is
+ "Release Candidate 1", and no longer has the bug. This
+ will help you triage and classify bugs according to
+ their relevance. It is also possible people may report
+ bugs against bleeding-edge beta versions that are not
+ evident in older versions of the software. This can
+ help isolate code changes that caused the bug
+ </P
><P
-> Notice the page that popped up? Every underlined word you see on your screen
- is a hyperlink that will take you to context-sensitive help.
- Click around for a while, and learn what everything here does. To return
- to the query interface after pulling up a help page, use the "Back" button in
- your browser.
- </P
+></P
+></DIV
+></DIV
+>
+ <DIV
+CLASS="EXAMPLE"
+><A
+NAME="AEN1494"
+></A
+><P
+><B
+>Example 4-3. A Different Use of Versions</B
+></P
+><DIV
+CLASS="INFORMALEXAMPLE"
+><A
+NAME="AEN1496"
+></A
+><P
+></P
+><P
+> This field has been used to good effect by an online
+ service provider in a slightly different way. They had
+ three versions of the product: "Production", "QA", and
+ "Dev". Although it may be the same product, a bug in
+ the development environment is not normally as critical
+ as a Production bug, nor does it need to be reported
+ publicly. When used in conjunction with Target
+ Milestones, one can easily specify the environment where
+ a bug can be reproduced, and the Milestone by which it
+ will be fixed.
+ </P
+><P
+></P
+></DIV
+></DIV
+>
+ </P
><P
-> I'm sure that after checking out the online help, you are now an Expert
- on the Bugzilla Query Page. If, however, you feel you haven't mastered it yet,
- let me walk you through making a few successful queries to find out what there
- are in the Bugzilla bug-tracking system itself.
+> To create and edit Versions:
</P
><P
></P
@@ -5845,574 +9172,697 @@ TARGET="_top"
TYPE="1"
><LI
><P
-> Ensure you are back on the "Bugzilla Query Page"
- Do nothing in the boxes marked "Status", "Resolution", "Platform", "OpSys",
- "Priority", or "Severity". The default query for "Status" is to find all bugs that
- are NEW, ASSIGNED, or REOPENED, which is what we want. If you don't select anything
- in the other 5 scrollboxes there, then you are saying that "any of these are OK";
- we're not locking ourselves into only finding bugs on the "DEC" Platform, or "Windows 95"
- OpSys (Operating System). You're smart, I think you have it figured out.
- </P
-><P
-> Basically, selecting <EM
->anything</EM
-> on the query page narrows your search
- down. Leaving stuff unselected, or text boxes unfilled, broadens your search!
+> From the "Edit product" screen, select "Edit Versions"
</P
></LI
><LI
><P
-> You see the box immediately below the top six boxes that contains an "Email" text box,
- with the words "matching as", a drop-down selection box, then some checkboxes with
- "Assigned To" checked by default? This allows you to filter your search down based upon
- email address. Let's put my email address in there, and see what happens.
+> You will notice that the product already has the default
+ version "undefined". If your product doesn't use version
+ numbers, you may want to leave this as it is or edit it so
+ that it is "---". You can then go back to the edit
+ versions page and add new versions to your product.
</P
><P
-> Type "barnboy@trilobyte.net" in the top Email text box.
+> Otherwise, click the "Add" button to the right of the "Add
+ a new version" text.
</P
></LI
><LI
><P
-> Let's narrow the search some more. Scroll down until you find the box with the word
- "Program" over the top of it. This is where we can narrow our search down to only
- specific products (software programs or product lines) in our Bugzilla database.
- Please notice the box is a <EM
->scrollbox</EM
->. Using the down arrow on the
- scrollbox, scroll down until you can see an entry called "Webtools". Select this entry.
+> Enter the name of the Version. This can be free-form
+ characters up to the limit of the text box. Then select
+ the "Add" button.
</P
></LI
><LI
><P
-> Did you notice that some of the boxes to the right changed when you selected "Webtools"?
- Every Program (or Product) has different Versions, Components, and Target Milestones associated
- with it. A "Version" is the number of a software program.
- <DIV
-CLASS="EXAMPLE"
+> At this point you can select "Edit" to edit more Versions,
+ or return to the "Query" page, from which you can navigate
+ back to the product through the "components" link at the
+ foot of the Query page.
+ </P
+></LI
+></OL
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H2
+CLASS="SECTION"
><A
-NAME="AEN1095"
-></A
+NAME="MILESTONES"
+>4.3.4. Milestones</A
+></H2
><P
-><B
->Example 4-1. Some Famous Software Versions</B
-></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 would be assigned the milestone of 3.0. Or, you
+ have a bug that you plan to fix for 2.8, this would have a
+ milestone of 2.8.
+ </P
><DIV
-CLASS="INFORMALEXAMPLE"
-><A
-NAME="AEN1097"
-></A
+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
-> Do you remember the hype in 1995 when Microsoft Windows 95(r) was released?
- It may have been several years
- ago, but Microsoft(tm) spent over $300 Million advertising this new Version of their
- software. Three years later, they released Microsoft Windows 98(r),
- another new version, to great fanfare, and then in 2000 quietly
- released Microsoft Windows ME(Millenium Edition)(r).
- </P
-><P
-> Software "Versions" help a manufacturer differentiate
- their current product from their
- previous products. Most do not identify their products
- by the year they were released.
- Instead, the "original" version of their software will
- often be numbered "1.0", with
- small bug-fix releases on subsequent tenths of a digit. In most cases, it's not
- a decimal number; for instance, often 1.9 is an <EM
->older</EM
-> version
- of the software than 1.11,
- but is a <EM
->newer</EM
-> version than 1.1.1.
- </P
+> Milestone options will only appear for a Product if you
+ turned the "usetargetmilestone" field in the "Edit
+ Parameters" screen "On".
+ </P
+></TD
+></TR
+></TABLE
+></DIV
><P
-> In general, a "Version" in Bugzilla should refer to
- <EM
->released</EM
->
- products, not products that have not yet been released
- to the public. Forthcoming products
- are what the Target Milestone field is for.
- </P
+> To create new Milestones, set Default Milestones, and set
+ Milestone URL:
+ </P
><P
></P
-></DIV
-></DIV
->
+><OL
+TYPE="1"
+><LI
+><P
+> Select "edit milestones"
</P
+></LI
+><LI
><P
-> A "Component" is a piece of a Product.
- It may be a standalone program, or some other logical
- division of a Product or Program.
- Normally, a Component has a single Owner, who is responsible
- for overseeing efforts to improve that Component.
- <DIV
+> Select "Add" to the right of the "Add a new milestone"
+ text
+ </P
+></LI
+><LI
+><P
+> 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. Select "Add".
+ </P
+><DIV
CLASS="EXAMPLE"
><A
-NAME="AEN1105"
+NAME="AEN1522"
></A
><P
><B
->Example 4-2. Mozilla Webtools Components</B
+>Example 4-4. Using SortKey with Target Milestone</B
></P
><DIV
CLASS="INFORMALEXAMPLE"
><A
-NAME="AEN1107"
+NAME="AEN1524"
></A
><P
-></P
+></P
+><P
+> Let's say you create a target milestone called
+ "Release 1.0", with Sortkey set to "0". Later, you
+ realize that you will have a public beta, called
+ "Beta1". You can create a Milestone called "Beta1",
+ with a Sortkey of "-1" in order to ensure people will
+ see the Target Milestone of "Beta1" earlier on the
+ list than "Release 1.0"
+ </P
+><P
+></P
+></DIV
+></DIV
+></LI
+><LI
+><P
+> If you want to add more milestones, select the "Edit"
+ link. If you don't, well shoot, you have to go back to the
+ "query" page and select "components" again, and make your
+ way back to the Product you were editing.
+ <DIV
+CLASS="NOTE"
><P
-> Mozilla's "Webtools" Product is composed of several pieces (Components):
- <P
></P
><TABLE
+CLASS="NOTE"
+WIDTH="90%"
BORDER="0"
-><TBODY
-><TR
-><TD
-><EM
->Bonsai</EM
->,
- a tool to show recent changes to Mozilla</TD
-></TR
-><TR
-><TD
-><EM
->Bugzilla</EM
->,
- a defect-tracking tool</TD
-></TR
-><TR
-><TD
-><EM
->Build</EM
->,
- a tool to automatically compile source code
- into machine-readable form</TD
-></TR
-><TR
-><TD
-><EM
->Despot</EM
->,
- a program that controls access to the other Webtools</TD
-></TR
-><TR
-><TD
-><EM
->LXR</EM
->,
- a utility that automatically marks up text files
- to make them more readable</TD
-></TR
><TR
><TD
-><EM
->MozBot</EM
->,
- a "robot" that announces changes to Mozilla in Chat</TD
-></TR
-><TR
-><TD
-><EM
->TestManager</EM
->,
- a tool to help find bugs in Mozilla</TD
-></TR
-><TR
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
><TD
-><EM
->Tinderbox</EM
->,
- which displays reports from Build</TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> This is another in the list of unusual user interface
+ decisions that we'd like to get cleaned up. Shouldn't
+ there be a link to the effect of "edit the Product I
+ was editing when I ended up here"? In any case,
+ clicking "components" in the footer takes you back to
+ the "Select product" screen, from which you can begin
+ editing your product again.
+ </P
+></TD
></TR
-></TBODY
></TABLE
-><P
-></P
->
- </P
-><P
-> A different person is responsible for each of these Components.
- Tara Hernandez keeps
- the "Bugzilla" component up-to-date.
- </P
-><P
-></P
-></DIV
></DIV
>
</P
+></LI
+><LI
><P
-> A "Milestone", or "Target Milestone" is a often a planned future "Version" of a
- product. In many cases, though, Milestones simply represent significant dates for
- a developer. Having certain features in your Product is frequently
- tied to revenue (money)
- the developer will receive if the features work by the time she
- reaches the Target Milestone.
- Target Milestones are a great tool to organize your time.
- If someone will pay you $100,000 for
- incorporating certain features by a certain date,
- those features by that Milestone date become
- a very high priority. Milestones tend to be highly malleable creatures,
- though, that appear
- to be in reach but are out of reach by the time the important day arrives.
+> From the Edit product screen again (once you've made your
+ way back), enter the URL for a description of what your
+ milestones are for this product in the "Milestone URL"
+ field. It should be of the format
+ "http://www.foo.com/bugzilla/product_milestones.html"
</P
><P
-> The Bugzilla Project has set up Milestones for future
- Bugzilla versions 2.14, 2.16, 2.18, 3.0, etc. However,
- a Target Milestone can just as easily be a specific date,
- code name, or weird alphanumeric
- combination, like "M19".
+> Some common uses of this field include product
+ descriptions, product roadmaps, and of course a simple
+ description of the meaning of each milestone.
</P
></LI
><LI
><P
-> OK, now let's select the "Bugzilla" component from its scrollbox.
+> If you're using Target Milestones, the "Default Milestone"
+ field must have some kind of entry. If you really don't
+ care if people set coherent Target Milestones, simply
+ leave this at the default, "---". However, controlling
+ and regularly updating the Default Milestone field is a
+ powerful tool when reporting the status of projects.
</P
+><P
+>Select the "Update" button when you are done.</P
></LI
+></OL
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H2
+CLASS="SECTION"
+><A
+NAME="VOTING"
+>4.3.5. Voting</A
+></H2
+><P
+> The concept of "voting" is a poorly understood, yet powerful
+ feature for the management of open-source projects. Each user
+ is assigned so many Votes per product, which they can freely
+ reassign (or assign multiple votes to a single bug). 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.
+ </P
+><P
+> The daunting challenge of Votes is deciding where you draw the
+ line for a "vocal majority". If you only have a user base of
+ 100 users, setting a low threshold for bugs to move from
+ UNCONFIRMED to NEW makes sense. As the Bugzilla user base
+ expands, however, these thresholds must be re-evaluated. You
+ should gauge whether this feature is worth the time and close
+ monitoring involved, and perhaps forego implementation until
+ you have a critical mass of users who demand it.
+ </P
+><P
+>To modify Voting settings:</P
+><P
+></P
+><OL
+TYPE="1"
><LI
><P
-> Skip down the page a bit -- do you see the "submit query" button?
- Select it, and let's run
- this query!
+> Navigate to the "Edit product" screen for the Product you
+ wish to modify
</P
></LI
><LI
><P
-> Congratulations! You've completed your first Query, and have before you the Bug List
- of the author of this Guide, Matthew P. Barnson (barnboy@trilobyte.net). If I'm
- doing well,
- you'll have a cryptic "Zarro Boogs Found" message on your screen. It is just
- a happy hacker's way of saying "Zero Bugs Found". However, I am fairly certain I will
- always have some bugs assigned to me that aren't done yet,
- so you won't often see that message!
+> Set "Maximum Votes per person" to your calculated value.
+ Setting this field to "0" disables voting.
</P
></LI
-></OL
+><LI
><P
-> I encourage you to click the bug numbers in the left-hand column and examine
- my bugs. Also notice that if you click the underlined
- links near the top of this page, they do
- not take you to context-sensitive help here,
- but instead sort the columns of bugs on the screen!
- When you need to sort your bugs by priority, severity,
- or the people they are assigned to, this
- is a tremendous timesaver.
- </P
+> Set "Maximum Votes a person can put on a single bug" to
+ your calculated value. It should probably be some number
+ lower than the "Maximum votes per person". Setting this
+ field to "0" disables voting, but leaves the voting
+ options open to the user. This is confusing.
+ </P
+></LI
+><LI
+><P
+> Set "Number of votes a bug in this product needs to
+ automatically get out of the UNCONFIRMED state" to your
+ calculated number. Setting this field to "0" disables
+ the automatic move of bugs from UNCONFIRMED to NEW. Some
+ people advocate leaving this at "0", but of what use are
+ Votes if your Bugzilla user base is unable to affect which
+ bugs appear on Development radar?
+ <DIV
+CLASS="TIP"
><P
-> A couple more interesting things about the Bug List page:
- <P
></P
><TABLE
+CLASS="TIP"
+WIDTH="90%"
BORDER="0"
-><TBODY
-><TR
-><TD
-><EM
->Change Columns</EM
->:
- by selecting this link, you can show all kinds
- of information in the Bug List</TD
-></TR
-><TR
-><TD
-><EM
->Change several bugs at once</EM
->:
- If you have sufficient rights to change all
- the bugs shown in the Bug List, you can mass-modify them.
- This is a big time-saver.</TD
-></TR
><TR
><TD
-><EM
->Send mail to bug owners</EM
->:
- If you have many related bugs, you can request
- an update from every person who owns the bugs in
- the Bug List asking them the status.</TD
-></TR
-><TR
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/tip.gif"
+HSPACE="5"
+ALT="Tip"></TD
><TD
-><EM
->Edit this query</EM
->:
- If you didn't get exactly the results you were looking for,
- you can return to the Query page through this link and make
- small revisions to the query you just made so
- you get more accurate results.</TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> You should probably set this number to higher than a
+ small coalition of Bugzilla users can influence it.
+ Most sites use this as a "referendum" mechanism -- if
+ users are able to vote a bug out of UNCONFIRMED, it is
+ a <EM
+>really</EM
+> bad bug!
+ </P
+></TD
></TR
-></TBODY
></TABLE
-><P
-></P
+></DIV
>
- </P
-><DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
+ </P
+></LI
+><LI
><P
-><B
->Note: </B
-> There are many more options to the Bugzilla Query Page
- and the Bug List than I have shown you.
- But this should be enough for you to learn to get around.
- I encourage you to check out the
- <A
-HREF="http://www.mozilla.org/bugs/"
-TARGET="_top"
->Bugzilla Home Page</A
->
- to learn about the Anatomy
- and Life Cycle of a Bug before continuing.
- </P
-></BLOCKQUOTE
-></DIV
+> Once you have adjusted the values to your preference,
+ select the "Update" button.
+ </P
+></LI
+></OL
></DIV
><DIV
CLASS="SECTION"
><HR><H2
CLASS="SECTION"
><A
-NAME="BUGREPORTS"
->4.3.3. Creating and Managing Bug Reports</A
+NAME="GROUPS"
+>4.3.6. Groups and Group Security</A
></H2
+><P
+> Groups can be very useful in bugzilla, because they allow
+ users to isolate bugs or products that should only be seen by
+ certain people. Groups can also be a complicated minefield of
+ interdependencies and weirdness if mismanaged.
+
+ <DIV
+CLASS="EXAMPLE"
+><A
+NAME="AEN1558"
+></A
+><P
+><B
+>Example 4-5. When to Use Group Security</B
+></P
+><DIV
+CLASS="INFORMALEXAMPLE"
+><A
+NAME="AEN1560"
+></A
+><P
+></P
+><P
+> Many Bugzilla sites isolate "Security-related" bugs from
+ all other bugs. This way, they can have a fix ready
+ before the security vulnerability is announced to the
+ world. You can create a "Security" product which, by
+ default, has no members, and only add members to the
+ group (in their individual User page, as described under
+ User Administration) who should have priveleged access
+ to "Security" bugs. Alternately, you may create a Group
+ independently of any Product, and change the Group mask
+ on individual bugs to restrict access to members only of
+ certain Groups.
+ </P
+><P
+></P
+></DIV
+></DIV
+> Groups only work if you enable the "usebuggroups"
+ paramater. In addition, if the "usebuggroupsentry" parameter
+ is "On", one can restrict access to products by groups, so
+ that only members of a product group are able to view bugs
+ within that product. Group security in Bugzilla can be divided
+ into two categories: Generic and Product-Based.
+ </P
+><DIV
+CLASS="NOTE"
+><P
+></P
><TABLE
-BORDER="0"
+CLASS="NOTE"
WIDTH="100%"
-CELLSPACING="0"
-CELLPADDING="0"
-CLASS="EPIGRAPH"
+BORDER="0"
><TR
><TD
-WIDTH="45%"
-> </TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
><TD
-WIDTH="45%"
ALIGN="LEFT"
VALIGN="TOP"
-><I
-><P
-><I
->And all this time, I thought we were taking bugs <EM
->out</EM
->...</I
-></P
-></I
-></TD
-></TR
-></TABLE
-><DIV
-CLASS="SECTION"
-><HR><H3
-CLASS="SECTION"
-><A
-NAME="BUG_WRITING"
->4.3.3.1. Writing a Great Bug Report</A
-></H3
><P
-> Before we plunge into writing your first bug report, I encourage you to read
- <A
-HREF="http://www.mozilla.org/quality/bug-writing-guidelines.html"
-TARGET="_top"
->Mozilla.org's Bug
- Writing Guidelines</A
->. 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.
+> Groups in Bugzilla are a complicated beast that evolved out
+ of very simple user permission bitmasks, apparently itself
+ derived from common concepts in UNIX access controls. A
+ "bitmask" is a fixed-length number whose value can describe
+ one, and only one, set of states. For instance, UNIX file
+ permissions are assigned bitmask values: "execute" has a
+ value of 1, "write" has a value of 2, and "read" has a
+ value of 4. Add them together, and a file can be read,
+ written to, and executed if it has a bitmask of "7". (This
+ is a simplified example -- anybody who knows UNIX security
+ knows there is much more to it than this. Please bear with
+ me for the purpose of this note.) The only way a bitmask
+ scheme can work is by doubling the bit count for each value.
+ Thus if UNIX wanted to offer another file permission, the
+ next would have to be a value of 8, then the next 16, the
+ next 32, etc.
</P
><P
-> While you are at it, why not learn how to find previously reported bugs? Mozilla.org
- has published a great tutorial on finding duplicate bugs, available at
- <A
-HREF="http://www.mozilla.org/quality/help/beginning-duplicate-finding.html"
-TARGET="_top"
-> http://www.mozilla.org/quality/help/beginning-duplicate-finding.html</A
->.
+> Similarly, Bugzilla offers a bitmask to define group
+ permissions, with an internal limit of 64. Several are
+ already occupied by built-in permissions. The way around
+ this limitation is to avoid assigning groups to products if
+ you have many products, avoid bloating of group lists, and
+ religiously prune irrelevant groups. In reality, most
+ installations of Bugzilla support far fewer than 64 groups,
+ so this limitation has not hit for most sites, but it is on
+ the table to be revised for Bugzilla 3.0 because it
+ interferes with the security schemes of some administrators.
</P
+></TD
+></TR
+></TABLE
+></DIV
><P
-> I realize this was a lot to read. However, understanding the mentality of writing
- great bug reports will help us on the next part!
- </P
+> To enable Generic Group Security ("usebuggroups"):
+ </P
><P
></P
><OL
-TYPE="1"
-><LI
-><P
-> Go back to <A
-HREF="http://landfill.tequilarista.org/mozilla/bugzilla/"
-TARGET="_top"
-> http://landfill.tequilarista.org/mozilla/bugzilla/</A
->
- in your browser.
- </P
-></LI
-><LI
-><P
-> Select the
- <A
-HREF="http://landfill.tequilarista.org/mozilla/bugzilla/enter_bug.cgi"
-TARGET="_top"
-> Enter a new bug report</A
-> link.
- </P
-></LI
-><LI
-><P
-> Select a product.
- </P
-></LI
-><LI
-><P
-> Now you should be at the "Enter Bug" form.
- The "reporter" should have been automatically filled out
- for you (or else Bugzilla prompted you to Log In again
- -- you did keep the email with your username
- and password, didn't you?).
- </P
-></LI
+TYPE="1"
><LI
><P
-> Select a Component in the scrollbox.
- </P
+> Turn "On" "usebuggroups" in the "Edit Parameters" screen.
+ </P
></LI
><LI
><P
-> Bugzilla should have made reasonable guesses, based upon your browser,
- for the "Platform" and "OS" drop-down
- boxes. If those are wrong, change them -- if you're on an SGI box
- running IRIX, we want to know!
- </P
+> You will generally have no groups set up. Select the
+ "groups" link in the footer.
+ </P
></LI
><LI
><P
-> Fill in the "Assigned To" box with the email address you provided earlier.
- This way you don't end up sending copies of your bug to lots of other people,
- since it's just a test bug.
- </P
+> Take a moment to understand the instructions on the "Edit
+ Groups" screen. Once you feel confident you understand
+ what is expected of you, select the "Add Group" link.
+ </P
></LI
><LI
><P
-> Leave the "CC" text box blank.
- Fill in the "URL" box with "http://www.mozilla.org".
- </P
-></LI
-><LI
+> Fill out the "New Name" (remember, no spaces!), "New
+ Description", and "New User RegExp" fields. "New User
+ RegExp" allows you to automatically place all users who
+ fulfill the Regular Expression into the new group.
+
+ <DIV
+CLASS="EXAMPLE"
+><A
+NAME="AEN1575"
+></A
><P
-> Enter "The Bugzilla Guide" in the Summary text box,
- and place any comments you have on this
- tutorial, or the Guide in general, into the Description box.
- </P
+><B
+>Example 4-6. Creating a New Group</B
+></P
+><DIV
+CLASS="INFORMALEXAMPLE"
+><A
+NAME="AEN1577"
+></A
+><P
+></P
+><P
+> I created a group called DefaultGroup with a
+ description of <SPAN
+CLASS="QUOTE"
+>"This is simply a group to play
+ with"</SPAN
+>, and a New User RegExp of <SPAN
+CLASS="QUOTE"
+>".*@mydomain.tld"</SPAN
+>.
+ This new group automatically includes all Bugzilla
+ users with "@mydomain.tld" at the end of their user id.
+ When I finished, my new group was assigned bit #128.
+ </P
+><P
+></P
+></DIV
+></DIV
+> When you have finished, select the Add
+ button.
+ </P
></LI
></OL
><P
-> Voila! Select "Commit" and send in your bug report!
- Next we'll look at resolving bugs.
- </P
-></DIV
+> To enable Product-Based Group Security (usebuggroupsentry):
+ </P
><DIV
-CLASS="SECTION"
-><HR><H3
-CLASS="SECTION"
-><A
-NAME="BUG_MANAGE"
->4.3.3.2. Managing your Bug Reports</A
-></H3
+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
-> OK, you should have a link to the bug you just created near the top of your page.
- It should say
- "Bug XXXX posted", with a link to the right saying "Back to BUG# XXXX".
- Select this link.
+> Don't forget that you only have 64 groups masks available,
+ total, for your installation of Bugzilla! If you plan on
+ having more than 50 products in your individual Bugzilla
+ installation, and require group security for your products,
+ you should consider either running multiple Bugzillas or
+ using Generic Group Security instead of Product-Based
+ ("usebuggroupsentry") Group Security.
</P
+></TD
+></TR
+></TABLE
+></DIV
><P
></P
><OL
TYPE="1"
><LI
><P
-> Scroll down a bit on the subsequent page,
- until you see the "Resolve bug, changing resolution to (dropdown box).
- Normally, you would
- "Accept bug (change status to ASSIGNED)", fix it, and then resolve.
- But in this case, we're
- going to short-circuit the process because this wasn't a real bug.
- Change the dropdown next to
- "Resolve Bug" to "INVALID", make sure the radio button is
- marked next to "Resolve Bug", then
- click "Commit".
+> Turn "On" "usebuggroups" and "usebuggroupsentry" in the
+ "Edit Parameters" screen.
+ </P
+><DIV
+CLASS="WARNING"
+><P
+></P
+><TABLE
+CLASS="WARNING"
+WIDTH="90%"
+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
+> "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, Products, etc.
+ with the administrative account.
</P
+></TD
+></TR
+></TABLE
+></DIV
></LI
><LI
><P
-> Hey! It said it couldn't take the change in a big red box!
- That's right, you must specify
- a Comment in order to make this change. Select the "Back"
- button in your browser, add a
- Comment, then try Resolving the bug with INVALID status again.
- This time it should work.
- </P
+> You will generally have no Groups set up, unless you
+ enabled "usebuggroupsentry" prior to creating any
+ Products. To create "Generic Group Security" groups,
+ follow the instructions given above. To create
+ Product-Based Group security, simply follow the
+ instructions for creating a new Product. If you need to
+ add users to these new groups as you create them, you will
+ find the option to add them to the group available under
+ the "Edit User" screens.
+ </P
></LI
></OL
><P
-> You have now learned the basics of Bugzilla navigation,
- entering a bug, and bug maintenance.
- I encourage you to explore these features, and see what you can do with them!
- We'll spend no more time on individual Bugs or Queries from this point on, so you are
- on your own there.
- </P
-><P
-> But I'll give a few last hints!
- </P
-><P
-> There is a <A
-HREF="http://bugzilla.mozilla.org/help.html"
-TARGET="_top"
->CLUE</A
->
- on the Query page
- that will teach you more how to use the form.
- </P
-><P
-> If you click the hyperlink on the
- <A
-HREF="http://bugzilla.mozilla.org/describecomponents.cgi"
-TARGET="_top"
->Component</A
->
- box of the Query page, you will be presented a form that will describe what all
- the components are.
- </P
+> You may find this example illustrative for how bug groups work.
+ <DIV
+CLASS="EXAMPLE"
+><A
+NAME="AEN1592"
+></A
><P
-> Possibly the most powerful feature of the Query page is the
- <A
-HREF="http://bugzilla.mozilla.org/booleanchart.html"
-TARGET="_top"
->Boolean Chart</A
-> section.
- It's a bit confusing to use the first time, but can provide unparalleled
- flexibility in your queries,
- allowing you to build extremely powerful requests.
- </P
+><B
+>Example 4-7. Bugzilla Groups</B
+></P
><P
-> Finally, you can build some nifty
- <A
-HREF="http://bugzilla.mozilla.org/reports.cgi"
-TARGET="_top"
->Reports</A
->
- using the "Bug Reports" link near the bottom of the query page, and also
- available via the "Reports" link
- at the footer of each page.
- </P
+CLASS="LITERALLAYOUT"
+>Bugzilla Groups example<br>
+-----------------------<br>
+<br>
+For this example, let us suppose we have four groups, call them<br>
+Group1, Group2, Group3, and Group4.<br>
+<br>
+We have 5 users, User1, User2, User3, User4, User5.<br>
+<br>
+We have 8 bugs, Bug1, ..., Bug8.<br>
+<br>
+Group membership is defined by this chart:<br>
+(X denotes that user is in that group.)<br>
+(I apologize for the nasty formatting of this table. Try viewing<br>
+it in a text-based browser or something for now. -MPB)<br>
+<br>
+ G G G G<br>
+ r r r r<br>
+ o o o o<br>
+ u u u u<br>
+ p p p p<br>
+ 1 2 3 4<br>
+ +-+-+-+-+<br>
+User1|X| | | |<br>
+ +-+-+-+-+<br>
+User2| |X| | |<br>
+ +-+-+-+-+<br>
+User3|X| |X| |<br>
+ +-+-+-+-+<br>
+User4|X|X|X| |<br>
+ +-+-+-+-+<br>
+User5| | | | |<br>
+ +-+-+-+-+<br>
+<br>
+Bug restrictions are defined by this chart:<br>
+(X denotes that bug is restricted to that group.)<br>
+<br>
+ G G G G<br>
+ r r r r<br>
+ o o o o<br>
+ u u u u<br>
+ p p p p<br>
+ 1 2 3 4<br>
+ +-+-+-+-+<br>
+Bug1| | | | |<br>
+ +-+-+-+-+<br>
+Bug2| |X| | |<br>
+ +-+-+-+-+<br>
+Bug3| | |X| |<br>
+ +-+-+-+-+<br>
+Bug4| | | |X|<br>
+ +-+-+-+-+<br>
+Bug5|X|X| | |<br>
+ +-+-+-+-+<br>
+Bug6|X| |X| |<br>
+ +-+-+-+-+<br>
+Bug7|X|X|X| |<br>
+ +-+-+-+-+<br>
+Bug8|X|X|X|X|<br>
+ +-+-+-+-+<br>
+<br>
+Who can see each bug?<br>
+<br>
+Bug1 has no group restrictions. Therefore, Bug1 can be seen by any<br>
+user, whatever their group membership. This is going to be the only<br>
+bug that User5 can see, because User5 isn't in any groups.<br>
+<br>
+Bug2 can be seen by anyone in Group2, that is User2 and User4.<br>
+<br>
+Bug3 can be seen by anyone in Group3, that is User3 and User4.<br>
+<br>
+Bug4 can be seen by anyone in Group4. Nobody is in Group4, so none of<br>
+these users can see Bug4.<br>
+<br>
+Bug5 can be seen by anyone who is in _both_ Group1 and Group2. This<br>
+is only User4. User1 cannot see it because he is not in Group2, and<br>
+User2 cannot see it because she is not in Group1.<br>
+<br>
+Bug6 can be seen by anyone who is in both Group1 and Group3. This<br>
+would include User3 and User4. Similar to Bug5, User1 cannot see Bug6<br>
+because he is not in Group3.<br>
+<br>
+Bug7 can be seen by anyone who is in Group1, Group2, and Group3. This<br>
+is only User4. All of the others are missing at least one of those<br>
+group priveleges, and thus cannot see the bug.<br>
+<br>
+Bug8 can be seen by anyone who is in Group1, Group2, Group3, and<br>
+Group4. There is nobody in all four of these groups, so nobody can<br>
+see Bug8. It doesn't matter that User4 is in Group1, Group2, and<br>
+Group3, since he isn't in Group4.<br>
+ </P
></DIV
+>
+ </P
></DIV
></DIV
><DIV
@@ -6420,8 +9870,8 @@ CLASS="SECTION"
><HR><H1
CLASS="SECTION"
><A
-NAME="INIT4ME"
->4.4. What's in it for me?</A
+NAME="SECURITY"
+>4.4. Bugzilla Security</A
></H1
><TABLE
BORDER="0"
@@ -6440,271 +9890,283 @@ VALIGN="TOP"
><I
><P
><I
->Indiana, it feels like we walking on fortune cookies!</I
-></P
-><P
-><I
->These ain't fortune cookies, kid...</I
+>Putting your money in a wall safe is better protection than
+ depending on the fact that no one knows that you hide your
+ money in a mayonnaise jar in your fridge.</I
></P
></I
></TD
></TR
></TABLE
-><P
-> Customized User Preferences offer tremendous versatility to
- your individual Bugzilla experience.
- Let's plunge into what you can do! The first step is to click
- the "Edit prefs" link at the footer of each page once you
- have logged in to
- <A
-HREF="http://landfill.tequilarista.org/mozilla/bugzilla/query.cgi?GoAheadAndLogIn=1"
-TARGET="_top"
-> Landfill</A
->.
- </P
-><DIV
-CLASS="SECTION"
-><HR><H2
-CLASS="SECTION"
-><A
-NAME="ACCOUNTSETTINGS"
->4.4.1. Account Settings</A
-></H2
-><P
-> On this page, you can change your basic Account Settings,
- including your password and full name.
- For security reasons, in order to change anything on this page you
- must type your <EM
->current</EM
->
- password into the "Old Password" field.
- If you wish to change your password, type the new password you
- want into the "New Password" field and again into the "Re-enter
- new password" field to ensure
- you typed your new password correctly. Select the "Submit" button and you're done!
- </P
-></DIV
-><DIV
-CLASS="SECTION"
-><HR><H2
-CLASS="SECTION"
-><A
-NAME="EMAILSETTINGS"
->4.4.2. Email Settings</A
-></H2
-><DIV
-CLASS="SECTION"
-><H3
-CLASS="SECTION"
-><A
-NAME="NOTIFICATION"
->4.4.2.1. Email Notification</A
-></H3
><DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><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
-><B
->Note: </B
-> The email notification settings described below have been obsoleted in Bugzilla 2.12, and
- this section will be replaced with a comprehensive description of the amazing array of
- new options at your disposal. However, in the meantime, throw this chunk out the window
- and go crazy with goofing around with different notification options.
- </P
-></BLOCKQUOTE
+> Poorly-configured MySQL, Bugzilla, and FTP installations have
+ given attackers full access to systems in the past. Please
+ take these guidelines seriously, even for Bugzilla machines
+ hidden away behind your firewall. 80% of all computer
+ trespassers are insiders, not anonymous crackers.
+ </P
+></TD
+></TR
+></TABLE
></DIV
><P
-> Ahh, here you can reduce or increase the amount of email sent you from Bugzilla!
- In the drop-down "Notify me of changes to", select one of
- <P
+> Secure your installation.
+ <DIV
+CLASS="NOTE"
+><P
></P
><TABLE
+CLASS="NOTE"
+WIDTH="100%"
BORDER="0"
-><TBODY
><TR
><TD
-><EM
->All qualifying bugs</EM
->: sends you every change to every bug
- where your name is somewhere on it, regardless of who changed it.</TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+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"
+TARGET="_top"
+>mozilla-webtools@mozilla.org</A
+>
+ </P
+></TD
></TR
+></TABLE
+></DIV
+>
+ <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
+ poorly secured default configuration choices.
+ </P
+></LI
+><LI
+><P
+><EM
+>There is no substitute for understanding the
+ tools on your system!</EM
+> Read <A
+HREF="http://www.mysql.com/documentation/mysql/bychapter/manual_Privilege_system.html"
+TARGET="_top"
+> The MySQL Privilege System</A
+> until you can recite it from memory!</P
+><P
+> At the very least, ensure you password the "mysql -u root"
+ account and the "bugs" account, establish grant table
+ rights (consult the Keystone guide in Appendix C: The
+ Bugzilla Database for some easy-to-use details) that do
+ not allow CREATE, DROP, RELOAD, SHUTDOWN, and PROCESS for
+ user "bugs". I wrote up the Keystone advice back when I
+ knew far less about security than I do now : )
+ </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
+></LI
+><LI
+><P
+> Do not run Apache as <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
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="90%"
+BORDER="0"
><TR
><TD
-><EM
->Only those bugs which I am listed in the CC line</EM
->: prevents
- you from receiving mail for which you are the reporter,'
- owner, or QA contact. If you are on the CC
- list, presumably someone had a <EM
->good</EM
->
- reason for you to get the email.</TD
-></TR
-><TR
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
><TD
-><EM
->All qulifying bugs except those which I change</EM
->:
- This is the default, and
- a sensible setting. If someone else changes your bugs, you will get emailed,
- but if you change bugs
- yourself you will receive no notification of the change.</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
+></TD
></TR
-></TBODY
></TABLE
-><P
-></P
->
- </P
></DIV
-><DIV
-CLASS="SECTION"
-><HR><H3
-CLASS="SECTION"
-><A
-NAME="NEWEMAILTECH"
->4.4.2.2. New Email Technology</A
-></H3
-><DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
-><P
-><B
->Note: </B
-> This option may not be available in all Bugzilla installations, depending upon
- the preferences of the systems administrator responsible for the setup of your Bugzilla.
- However, if you really want this functionality, ask her to "enable newemailtech
- in Params"
- and "make it the default for all new users", referring her to the Administration section
- of this Guide.
+>
</P
-></BLOCKQUOTE
-></DIV
-><P
-> Disregard the warnings about "experimental and bleeding edge"; the code to handle email
- in a cleaner manner than that historically used for Bugzilla is
- quite robust and well-tested now.
- </P
+></LI
+><LI
><P
-> I recommend you enable the option, "Click here to sign up (and risk any bugs)".
- Your email-box
- will thank you for it. The fundamental shift in "newemailtech" is away from standard UNIX
- "diff" output, which is quite ugly, to a prettier, better laid-out email.
- </P
-></DIV
-><DIV
-CLASS="SECTION"
-><HR><H3
-CLASS="SECTION"
-><A
-NAME="WATCHSETTINGS"
->4.4.2.3. "Watching" Users</A
-></H3
+> Ensure you have adequate access controls for the
+ $BUGZILLA_HOME/data/ and $BUGZILLA_HOME/shadow/
+ directories, as well as the $BUGZILLA_HOME/localconfig and
+ $BUGZILLA_HOME/globals.pl files. The localconfig file
+ stores your "bugs" user password, which would be terrible
+ to have in the hands of a criminal, while the "globals.pl"
+ stores some default information regarding your
+ installation which could aid a system cracker. In
+ addition, some files under $BUGZILLA_HOME/data/ store
+ sensitive information, and $BUGZILLA_HOME/shadow/ stores
+ bug information for faster retrieval. If you fail to
+ secure these directories and this file, you will expose
+ bug information to those who may not be allowed to see it.
+ </P
><DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><P
+></P
+><TABLE
CLASS="NOTE"
+WIDTH="90%"
+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
-><B
->Note: </B
-> This option may not be available in all Bugzilla installations, depending upon
- the preferences of the systems administrator responsible for the setup of your Bugzilla.
- However, if you really want this functionality, ask her to "enable watchers in Params".
- </P
-></BLOCKQUOTE
-></DIV
+> 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
-> By entering user email names into the "Users to watch" text entry box, delineated by commas,
- you can watch bugs of other users. This powerful functionality enables seamless transitions
- as developers change projects, managers wish to get in touch with the issues faced by their
- direct reports, or users go on vacation. If any of these three situations apply
- to you, you will undoubtedly find this feature quite convenient.
- </P
-></DIV
+> 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"
+TARGET="_top"
+> http://bugzilla.mozilla.org/localconfig</A
+>). 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
+></TD
+></TR
+></TABLE
></DIV
-><DIV
-CLASS="SECTION"
-><HR><H2
-CLASS="SECTION"
-><A
-NAME="FOOTERSETTINGS"
->4.4.3. Page Footer</A
-></H2
-><DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
><P
-><B
->Note: </B
-> By default, this page is quite barren. However, go explore the Query Page some more; you will
- find that you can store numerous queries on the server, so if you regularly run a particular query
- it is just a drop-down menu away. On this page of Preferences, if you have many stored
- queries you can elect to have them always one-click away!
- </P
-></BLOCKQUOTE
-></DIV
+> 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"
+TARGET="_top"
+> Bug 65572</A
+> for adequate protection in your data/ and shadow/ directories.
+ </P
><P
-> If you have many stored queries on the server, here you will find individual drop-downs for each
- stored query. Each drop-down gives you the option of that query appearing on the footer of every
- page in Bugzilla! This gives you powerful one-click access to any complex searches you may set up,
- and is an excellent way to impress your boss...
- </P
-><DIV
-CLASS="TIP"
-><BLOCKQUOTE
-CLASS="TIP"
+> 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
-><B
->Tip: </B
->By default, the "My Bugs" link appears at the bottom of each page. However, this query
- gives you both the bugs you have reported, as well as those you are assigned. One of the most
- common uses for this page is to remove the "My Bugs" link, replacing it with two other queries,
- commonly called "My Bug Reports" and "My Bugs" (but only referencing bugs assigned to you). This
- allows you to distinguish those bugs you have reported from those you are assigned. I commonly
- set up complex Boolean queries in the Query page and link them to my footer in this page. When
- they are significantly complex, a one-click reference can save hours of work.</P
-></BLOCKQUOTE
-></DIV
-></DIV
-><DIV
-CLASS="SECTION"
-><HR><H2
-CLASS="SECTION"
-><A
-NAME="PERMISSIONSETTINGS"
->4.4.4. Permissions</A
-></H2
+> 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<br>
+ from all </Files> deny from all </P
+>
+ </P
><P
-> This is a purely informative page which outlines your current permissions on
- this installation of Bugzilla. If you have permissions to grant certain permissions to
- other users, the "other users" link appears on this page as well as the footer.
- For more information regarding user administration, please consult the Administration
- section of this Guide.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="SECTION"
-><HR><H1
-CLASS="SECTION"
-><A
-NAME="USINGBZ-CONC"
->4.5. Using Bugzilla-Conclusion</A
-></H1
+> 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<br>
+ from all </Files> allow from all </P
+>
+ </P
><P
-> Thank you for reading through this portion of the Bugzilla Guide. I anticipate
- it may not yet meet the needs of all readers. If you have additional comments or
- corrections to make, please submit your contributions to the
- <A
-HREF="mailto://mozilla-webtools@mozilla.org"
-TARGET="_top"
->mozilla-webtools</A
+> Place the following text into a file named ".htaccess",
+ readable by your web server, in your $BUGZILLA_HOME/shadow
+ directory. <P
+CLASS="LITERALLAYOUT"
+> deny from all </P
+>
+ </P
+></LI
+></OL
>
- mailing list/newsgroup. The mailing list is mirrored to the netscape.public.mozilla.webtools
- newsgroup, and the newsgroup is mirrored to mozilla-webtools@mozilla.org
</P
></DIV
></DIV
@@ -6724,7 +10186,23 @@ NAME="BONSAI"
>5.1. Bonsai</A
></H1
><P
->We need Bonsai integration information.</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. These kinds of changes cause the
+ engineer responsible to be <SPAN
+CLASS="QUOTE"
+>"on the hook"</SPAN
+> (include
+ cool URL link here for Hook policies at mozilla.org). Bonsai
+ also includes gateways to <A
+HREF="#TINDERBOX"
+>Tinderbox, the Mozilla automated build management system</A
+> and Bugzilla </P
></DIV
><DIV
CLASS="SECTION"
@@ -6735,7 +10213,37 @@ NAME="CVS"
>5.2. CVS</A
></H1
><P
->We need CVS integration information</P
+>CVS integration is best accomplished, at this point, using
+ the Bugzilla Email Gateway. There have been some files
+ submitted to allow greater CVS integration, but we need to make
+ certain that Bugzilla is not tied into one particular software
+ management package.</P
+><P
+> Follow the instructions in the FAQ 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
+> There is also a 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
+>, under the
+ <SPAN
+CLASS="QUOTE"
+>"cvszilla"</SPAN
+> link.
+ </P
></DIV
><DIV
CLASS="SECTION"
@@ -6746,37 +10254,28 @@ NAME="SCM"
>5.3. Perforce SCM</A
></H1
><P
-> Richard Brooksby created a Perforce integration tool for Bugzilla and TeamTrack.
- You can find the main project page at
- <A
+> 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
->. "p4dti" is now an officially
- supported product from Perforce, and you can find the "Perforce Public Depot"
- p4dti page at <A
+> 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
+> http://public.perforce.com/public/perforce/p4dti/index.html</A
>.
</P
><P
-> Integration of Perforce with Bugzilla, once patches are applied, is fairly seamless. However,
- p4dti is a patch against the Bugzilla 2.10 release, not the current 2.12 release. I anticipate
- patches for 2.12 will be out shortly. Check the project page regularly for updates, or
- take the given patches and patch it manually. p4dti is designed to support multiple defect
- trackers, and maintains its own documentation for it. Please consult the pages linked
- above for further information.
- </P
-><P
-> Right now, there is no way to synchronize the Bug ID and the Perforce Transaction Number, or
- to change the Bug ID to read (PRODUCT).bugID unless you hack it in. Additionally, if you
- have synchronization problems, the easiest way to avoid them is to only put the bug
- information, comments, etc. into Bugzilla, and not into the Perforce change records.
- They will link anyway; merely reference the bug ID fixed in your change description,
- and put a comment into Bugzilla
- giving the change ID that fixed the Bugzilla bug. It's a process issue, not a technology
- question.
+> 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
@@ -6785,10 +10284,10 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="TINDERBOX"
->5.4. Tinderbox</A
+>5.4. Tinderbox/Tinderbox2</A
></H1
><P
->We need Tinderbox integration information</P
+>We need Tinderbox integration information.</P
></DIV
></DIV
><DIV
@@ -6800,212 +10299,654 @@ NAME="FUTURE"
></H1
><TABLE
BORDER="0"
-BGCOLOR="#E0E0E0"
+BGCOLOR="#6495ED"
WIDTH="100%"
><TR
><TD
+><FONT
+COLOR="#000000"
><PRE
CLASS="SYNOPSIS"
>Bugzilla's Future. Much of this is the present, now.</PRE
+></FONT
></TD
></TR
></TABLE
-><DIV
-CLASS="SECTION"
-><HR><H1
-CLASS="SECTION"
-><A
-NAME="SPAMLITE"
->6.1. Reducing Spam</A
-></H1
><P
+> Bugzilla's future is a constantly-changing thing, as various developers
+ <SPAN
+CLASS="QUOTE"
+>"scratch an itch"</SPAN
+> when it comes to functionality.
+ Thus this section is very malleable, subject to change without notice, etc.
+ You'll probably also notice the lack of formatting. I apologize that it's
+ not quite as readable as the rest of the Guide.
+ </P
><P
+> <P
CLASS="LITERALLAYOUT"
->Those who use Bugzilla frequently are probably used to notification spam<br>
-- unwanted or unnecessary notifications. A number of proposals have<br>
-been put forward to attempt to reduce this.<br>
+> Bugzilla Blue Sky<br>
+<br>
+Customisability<br>
+<br>
+ One of the major stumbling blocks of Bugzilla has been that it is too<br>
+ rigid and does not adapt itself well enough to the needs of an<br>
+ organisation. This has led to organisations making changes to the<br>
+ Bugzilla code that need to be redone each new version of Bugzilla.<br>
+ Bugzilla should attempt to move away from this to a world where this<br>
+ doesn't need to occur.<br>
+<br>
+ Most of the subsections in this section are currently explicit design<br>
+ goals for the "Bugzilla 3" rewrite. This does not necessarily mean<br>
+ that they will not occur before them in Bugzilla 2, but most are<br>
+ significant undertakings.<br>
+<br>
+ Field Customisation<br>
+<br>
+ Many installations wish to customise the fields that appear on bug<br>
+ reports. Current versions of Bugzilla offer limited<br>
+ customisability. In particular, some fields can be turned off.<br>
+<br>
+ However, many administrators wish to add their own fields, and rename<br>
+ or otherwise modify existing fields. An architecture that supports<br>
+ this would be extraordinarily useful.<br>
+<br>
+ Indeed, many fields work similarly and could be abstracted into "field<br>
+ types", so that an administrator need write little or no code to<br>
+ support the new fields they desire.<br>
+<br>
+ Possible field types include text (eg status whiteboard), numbers,<br>
+ dates (eg report time), accounts (eg reporter, qa, cc), inter-bug<br>
+ relationships (dependencies, duplicates), option groups (platform, os,<br>
+ severity, priority, target milestone, version) etc.<br>
+<br>
+ Ideally an administrator could configure their fields through a<br>
+ Bugzilla interface that requires no code to be added. However, it is<br>
+ highly unlikely this ideal will never be met, and in a similar way<br>
+ that office applications have scripting languages, Bugzilla should<br>
+ allow new field types to be written.<br>
+<br>
+ Similarly, a common desire is for resolutions to be added or removed.<br>
+<br>
+ Allocations<br>
+<br>
+ ?<br>
+<br>
+ Option Groups<br>
+<br>
+ ?<br>
+<br>
+ Relations<br>
+<br>
+ ?<br>
+<br>
+ Database Integrity<br>
+<br>
+ Furthermore, it is desirable for administrators to be able to specify<br>
+ rules that must or should apply between the fields on a bug report.<br>
+<br>
+ For example, you might wish to specify that a bug with status ASSIGNED<br>
+ must have a target milestone field that that is not untargetted. Or<br>
+ that a bug with a certain number of votes should get ASSIGNED. Or<br>
+ that the QA contact must be different from the assignee.<br>
+<br>
+ "Must" relationships could be implemented by refusing to make changes<br>
+ that violate the relationships, or alternatively, automatically<br>
+ updating certain fields in order to satisfy the criteria. Which<br>
+ occurs should be up to the administrator.<br>
+<br>
+ "Should" relationships could be implemented by a combination of<br>
+ emitting warnings on the process bug page, the same on notification<br>
+ mails, or emitting periodic whine mails about the situation. Again,<br>
+ which occurs should be up to the administrator.<br>
+<br>
+ It should also be possible for whine mails to be emitted for "must"<br>
+ relationships, as they might become violated through direct database<br>
+ access, Bugzilla bugs, or because they were there before the<br>
+ relationship was enforced.<br>
+<br>
+ As well as implementing intra-bug constraints, it would be useful to<br>
+ create inter-bug constraints. For example, a bug that is dependent on<br>
+ another bug should not have an earlier milestone or greater priority<br>
+ than that bug.<br>
+<br>
+ Database Adaptability<br>
+<br>
+ Often an administrator desires that fields adapt to the values of<br>
+ other fields. For example, the value of a field might determine the<br>
+ possible values of another field or even whether it appears (whether<br>
+ it is "applicable").<br>
+<br>
+ Limited adaptability is present in Bugzilla 2, and only on the<br>
+ "Product" field:<br>
+ * The possible values of the target milestone, version and component<br>
+ fields depend on the product.<br>
+ * UNCONFIRMED can be turned off for specific products.<br>
+ * Voting can be configured differently or turned off for different<br>
+ products, and there is a separate user vote limits for each<br>
+ product.<br>
+<br>
+ It would be good if more adaptability was present, both in terms of<br>
+ all fields relying on the product, as well as the ability to adapt<br>
+ based on the value of all fields.<br>
+<br>
+ Example ???<br>
+<br>
+ General adaptability raises the issue of circular references between<br>
+ fields causing problems. One possible solution to this is to place<br>
+ the fields in a total ordering and require a field refer only to the<br>
+ previous fields.<br>
+<br>
+ In Bugzilla 2, changing the product of a bug meant a second page would<br>
+ appear that allowed you to choose a new milestone, component and<br>
+ version, as those fields adapted themselves to the new product. This<br>
+ page could be generalised to support all instances where:<br>
+ * a field value must or might be changed because the possible values<br>
+ have changed<br>
+ * is going to drop off because it it is no longer applicable, and<br>
+ this should be confirmed<br>
+ * must be specified because it is suddenly applicable, and the<br>
+ default value, if one exists, might not be acceptable<br>
+<br>
+ Database Independence<br>
+<br>
+ Currently Bugzilla only runs on the MySQL database. It would be<br>
+ desirable for Bugzilla to run on other databases, because:<br>
+ * Organisations may have existing database products they use and<br>
+ would prefer to run a homogenous environment.<br>
+ * Databases each have their own shortcomings, including MySQL. An<br>
+ administrator might choose a database that would work better with<br>
+ their Bugzilla.<br>
+<br>
+ This raises the possibility that we could use features that are only<br>
+ present in some databases, by appropriately falling back. For<br>
+ example, in the MySQL world, we live without:<br>
+ * record-level locking, instead we use table-level locking<br>
+ * referential and record constraints, instead we checking code<br>
+ * subselects, instead we use multiple queries and redundant "caches"<br>
+<br>
+ Multiple Front Ends<br>
+<br>
+ Currently Bugzilla is manipulated via the Web, and notifies via<br>
+ E-Mail. It would be desirable for Bugzilla to easily support various<br>
+ front ends.<br>
+<br>
+ There is no reason that Bugzilla could not be controlled via a whole<br>
+ range of front ends, including Web, E-Mail, IRC, ICQ, etc, and<br>
+ similarly for how it notifies. It's also possible that we could<br>
+ introduce a special Bugzilla client that uses its own protocol, for<br>
+ maximum user productivity.<br>
+<br>
+ Indeed a request reply might be returned via a totally different<br>
+ transport method than was use to submit the request.<br>
+<br>
+Internationalisation<br>
+<br>
+ Bugzilla currently supports only English. All of the field names,<br>
+ user instructions, etc are written in English. It would be desirable<br>
+ to allow "language packs" so Bugzilla can be easily used in<br>
+ non-English speaking locales.<br>
+<br>
+ To a degree field customisation supports this, because administrators<br>
+ could specify their own fields names anyway. However, there will<br>
+ always be some basic facilities not covered by this, and it is<br>
+ desirable that the administrator's interface also is<br>
+ internationalisable.<br>
+<br>
+Better Searching<br>
+<br>
+ General Summary Reports<br>
+<br>
+ Sometimes, the normal querying page leaves a lot to be desired. There<br>
+ are other facilities already in place or which people have asked for:<br>
+<br>
+ Most Doomed Reports - All Bugs or All Bugs In A Product, Categorised<br>
+ On Assignee, Shows and Counts Number of Bugs For Each Assignee<br>
+ Most Voted For Bugs - All Bugs, Categorised On Product, Shows Top Ten<br>
+ Bugs Voters Most Want Fixed<br>
+ Number of Open Bugs For An Assignee - Bug List, Categorised On<br>
+ Developers, Counts Number of Bugs In Category<br>
+<br>
+ The important thing to realise is that people want categorised reports<br>
+ on all sorts of things - a general summary report.<br>
+<br>
+ In a categorised report, you choose the subset of bugs you wish to<br>
+ operate on (similar to how you would specify a query), and then<br>
+ categorise them on one or more fields.<br>
+<br>
+ For each category you display the count of the number of things in<br>
+ that category. You can optionally display the bugs themselves, or<br>
+ leave them out, just showing the counts. And you can optionally limit<br>
+ the number of things (bugs or subcategories) that display in each<br>
+ category.<br>
+<br>
+ Such a mechanism would let you do all of the above and more.<br>
+ Applications of this mechanism would only be recognised once it was<br>
+ implemented.<br>
+<br>
+ Related Bugs<br>
+<br>
+ It would be nice to have a field where you could enter other bugs<br>
+ related to the current bug. It would be handy for navigation and<br>
+ possibly even finding duplicates.<br>
+<br>
+ Column Specification Support<br>
+<br>
+ Currently bug lists use the columns that you last used. This doesn't<br>
+ work well for "prepackaged queries", where you followed a link. You<br>
+ can probably add a column by specifying a sort column, but this is<br>
+ difficult and suboptimal.<br>
+<br>
+ Furthermore, I find that when I want to add a column to a bug list,<br>
+ it's usually a one off and I would prefer it to go away for the next<br>
+ query. Hence, it would be nice to specify the columns that appear on<br>
+ the bug list (and general summary report) pages. The default query<br>
+ mechanism should be able to let you specify your default columns.<br>
+<br>
+ Advanced Querying Redesign<br>
+<br>
+ ?<br>
+<br>
+Keywords<br>
+<br>
+ People have a need to apply tags to bugs. In the beginning, people<br>
+ placed designators in the summary and status whiteboard. However,<br>
+ these fields were not designed for that, and so there were many flaws<br>
+ with this system:<br>
+ * They pollute the field with information that was never intended to<br>
+ be present.<br>
+ * Removing them with a bulk change is a difficult problem that has<br>
+ too many pitfalls to implement.<br>
+ * You can easily get the capitalisation wrong.<br>
+<br>
+ Then dependencies were introduced (when?), and people realised that<br>
+ they could use them for "tracking bugs". Again, dependencies were not<br>
+ designed for that, and so there were more flaws, albeit different<br>
+ ones, including:<br>
+ * They aren't really bugs, so it's difficult to distinguish issues<br>
+ from bugs.<br>
+ * They can pollute bugs counts, and you must somehow exclude them<br>
+ from queries.<br>
+ * There is a whole lot of useless information on them. They have an<br>
+ assignee but there is nothing to fix, and that person can get<br>
+ whined at by Bugzilla. They have target milestones which must be<br>
+ manually maintained. And so on.<br>
+<br>
+ Finally, keywords were introduced (when?) for this purpose to remove<br>
+ the need for these two systems. Unfortunately, the simple keywords<br>
+ implementation was itself lacking in certain features provided by the<br>
+ two previous systems, and has remained almost unchanged since its<br>
+ inception. Furthermore, it could not be forseen that in large<br>
+ installations, the sheer number of keywords could become unwieldly and<br>
+ could lead to a movement back to the other systems.<br>
+<br>
+ The keywords system was the right idea, however, and it remains so.<br>
+ Fixing the keywords system is one of the most important Bugzilla<br>
+ issues.<br>
+<br>
+ Bringing Keywords Up To Par<br>
+<br>
+ For the most part, keywords are very good at what they do. It is easy<br>
+ to add and remove them (unlike summary/whiteboard designators), we can<br>
+ simply see what issues are present on a bug (unlike tracking bugs),<br>
+ and we do not confuse bugs with issues (unlike tracking bugs).<br>
+<br>
+ However, there are still some "regressions" in the keyword system over<br>
+ previous systems:<br>
+ * Users wish to view the "dependency forest" of a keyword. While a<br>
+ dependency tree is of one bug, a dependency forest is of a bug<br>
+ list, and consists of a dependency tree for each member of the bug<br>
+ list. Users can work around this with tracking bugs by creating a<br>
+ tracking bug and viewing the dependency tree of that tracking bug.<br>
+ * Users wish to specify the keywords that initially apply to a bug,<br>
+ but instead they must edit the bug once it has already been<br>
+ submitted. They can work around this with summary designators,<br>
+ since they specify the summary at reporting time.<br>
+ * Users wish to store or share a bug list that contains a keywords<br>
+ column. Hence they wish to be able to specify what columns appear<br>
+ in the bug list URL, as mentioned earlier. They can work around<br>
+ this using summary designators, since almost all bug lists have a<br>
+ summary column.<br>
+ * Users wish to be able to view keywords on a bug list. However<br>
+ often they are only interested in a small number of keywords.<br>
+ Having a bug list with a keywords column means that all keywords<br>
+ will appear on a bug list. This can take a substantial amount of<br>
+ space where a bug has a lot of keywords, since the table columns<br>
+ in Bugzilla adjust to the largest cell in that column. Hence<br>
+ users wish to be able to specify which keywords should appear in<br>
+ the bug list. In a very real sense, each keyword is a field unto<br>
+ itself. Users can work around this by using summary designators,<br>
+ since they keywords will share the space in the summary column.<br>
+ * Users wish to know when bugs with a specific issue are resolved.<br>
+ Hence they wish to be able to receive notifications on all the<br>
+ bugs with a specific keyword. The introduction a generic watching<br>
+ facility (also for things like watching all bugs in a component)<br>
+ would achieve this. Users can work around this by using tracking<br>
+ bugs, as dependencies have an existing way of detecting fixes to<br>
+ bug a bug was blocked by.<br>
+<br>
+ Dealing With The Keyword Overload<br>
+<br>
+ At the time of writing, the mozilla.org installation has approximately<br>
+ 100 keywords, and many more would be in use if the keywords system<br>
+ didn't have the problems it does.<br>
+<br>
+ Such a large number of keywords introduces logistical problems:<br>
+ * It must be easy for someone to learn what a keyword means. If a<br>
+ keyword is buried within a lot of other keywords, it can be<br>
+ difficult to find.<br>
+ * It must be easy to see what keywords are on a bug. If the number<br>
+ of keywords is large, then this can be difficult.<br>
+<br>
+ These lead some people to feel that there are "too many keywords".<br>
+<br>
+ These problems are not without solutions however. It is harder to<br>
+ find a list of designators or tracking bugs than it is a list of<br>
+ keywords.<br>
+<br>
+ The essential problem is it needs to be easy to find the keywords<br>
+ we're interested in through the mass of keywords.<br>
+<br>
+ Keyword Applicability<br>
+<br>
+ As has been previously mentioned, it is desirable for fields to be<br>
+ able to adapt to the values of other fields. This is certainly true<br>
+ for keywords. Many keywords are simply not relevant because of the<br>
+ bugs product, component, etc.<br>
+<br>
+ Hence, by introducing keyword applicability, and not displaying<br>
+ keywords that are not relevant to the current bug, or clearly<br>
+ separating them, we can make the keyword overload problem less<br>
+ significant.<br>
+<br>
+ Currently when you click on "keywords" on a bug, you get a list of all<br>
+ bugs. It would be desirable to introduce a list of keywords tailored<br>
+ to a specific bug, that reports, in order:<br>
+ * the keywords currently on the bug<br>
+ * the keywords not currently on the bug, but applicable to the bug<br>
+ * optionally, the keywords not applicable to the bug<br>
+<br>
+ This essentially orders the keywords into three groups, where each<br>
+ group is more important than the previous, and therefore appears<br>
+ closer to the top.<br>
+<br>
+ Keyword Grouping & Ordering<br>
+<br>
+ We could further enhance both the global and bug specific keyword list<br>
+ by grouping keywords. We should always have a "flat" view of<br>
+ keywords, but other ways of viewing the keywords would be useful too.<br>
+<br>
+ If keyword applicability was implemented, we could group keywords<br>
+ based on their "applicability condition". Keywords that apply to all<br>
+ bugs could be separated from keywords that apply to a specific<br>
+ product, both on the global keyword list and the keyword list of a bug<br>
+ that is in that product.<br>
+<br>
+ We could specify groups of our own. For example, many keywords are in<br>
+ a mutually exclusive group, essentially like radio buttons in a user<br>
+ interface. This creates a natural grouping, although other groupings<br>
+ occur (which depends on your keywords).<br>
+<br>
+ It is possible that we could use collapsing/expanding operations on<br>
+ "twisties" to only should the groups we are interested in.<br>
+<br>
+ And instead of grouping keywords, we could order them on some metric<br>
+ of usefulness, such as:<br>
+ * when the keyword was last added to a bug<br>
+ * how many bugs the keyword is on<br>
+ * how many open bugs the keyword is on<br>
+<br>
+ Opting Out Of Keywords<br>
+<br>
+ Not all people are going to care about all keywords. Therefore it<br>
+ makes sense that you may wish to specify which keywords you are<br>
+ interested in, either on the bug page, or on notifications.<br>
+<br>
+ Other keywords will therefore not bother users who are not interested<br>
+ in them.<br>
+<br>
+ Keyword Security<br>
+<br>
+ Currently all keywords are available and editable to all people with<br>
+ edit bugs access. This situation is clearly suboptimal.<br>
+<br>
+ Although relying on good behaviour for people to not do what they<br>
+ shouldn't works reasonably well on the mozilla.org, it is better to<br>
+ enforce that behaviour - it can be breached through malice, accident<br>
+ or ignorance.<br>
+<br>
+ And in the situation where it is desirable for the presence or absence<br>
+ of a keyword not to be revealed, organisations either need to be<br>
+ content with the divulgence, or not use keywords at all.<br>
+<br>
+ In the situation where they choose to divulge, introducing the ability<br>
+ to restrict who can see the keyword would also reduce keyword<br>
+ overload.<br>
+<br>
+ Personal Keywords<br>
+<br>
+ Keywords join together a set of bugs which would otherwise be<br>
+ unrelated in the bug system.<br>
+<br>
+ We allow users to store their own queries. However we don't allow<br>
+ them to store their own keywords on a bug. This reduces the<br>
+ usefulness of personal queries, since you cannot join a set of<br>
+ unrelated bugs together in a way that you wish. Lists of bug numbers<br>
+ can work, by they can only be used for small lists, and it is<br>
+ impossible to share a list between multiple queries.<br>
+<br>
+ Personal keywords are necessary to replace personal tracking bugs, as<br>
+ they would not pollute the keyword space. Indeed, on many<br>
+ installations this could remove some keywords out of the global<br>
+ keyword space.<br>
+<br>
+ In a similar vein and with similar effects, group keywords could be<br>
+ introduced that are only available to members of a specific group.<br>
+<br>
+ Keyword Restrictions<br>
<br>
-1. Reduce CC Spam<br>
+ Keywords are not islands unto themselves. Along with their potential<br>
+ to be involved in the inter-field relationships mentioned earlier,<br>
+ keywords can also be related to other keywords.<br>
<br>
-Some of you probably know me as that guy who CCs on heaps and heaps of<br>
-bugs. Just as you get a lot of CC changes from me, so do I get a lot<br>
-from others. Why should CC changes send out email notifications?<br>
+ Essentially, there are two possibilities:<br>
+ * a set of keywords are mutually exclusive<br>
+ * the presence of a keyword implies another keyword must be present<br>
<br>
-It's not necessarily the best idea to just remove the CC spam, there are<br>
-other issues too, like the difficulty of adding to large CC fields.<br>
+ Introduction of the ability to specify these restrictions would have<br>
+ benefits.<br>
<br>
-For these reasons and more, an RFE for a per user "BCC" facility exists<br>
-that people could use to silently and privately track bugs, in a similar<br>
-way to voting today, but applying to an unlimited number of bugs. See<br>
-"http://bugzilla.mozilla.org/show_bug.cgi?id=7345".<br>
+ If mutually exclusive keywords were present on a bug, their removal<br>
+ would fix up the database, as well as reducing the number of keywords<br>
+ on that bug.<br>
<br>
-2. Bulk Changes<br>
+ In the situation where a keyword implies another keyword, there are<br>
+ two possiblities as to how to handle the situation.<br>
<br>
-You know the drill - a large milestone change, a component movement,<br>
-whatever, and lots of notifications are generated. If there's enough<br>
-maybe you'll just go delete, delete, delete, whoops, there goes another<br>
-notification that wasn't from the bulk change you missed.<br>
+ The first is automatically add the keyword. This would fix up the<br>
+ database, but it would increase the number of keywords on a bug.<br>
<br>
-Shouldn't bulk changes send out one notification? A proposal for this<br>
-is at "http://bugzilla.mozilla.org/show_bug.cgi?id=26943".<br>
+ The second is to automatically remove the keyword, and alter queries<br>
+ so they pick up the first keyword as well as the removed keyword.<br>
+ This would fix up the database and reduce the number of keywords on a<br>
+ bug, but it might confuse users who don't see the keyword.<br>
+ Alternatively, the implied keywords could be listed separately.<br>
<br>
-3. Configurable Notification Criteria<br>
+Notifications<br>
<br>
-It would be good if you could choose what you want to receive. There<br>
-are two parts to this.<br>
+ Every time a bug gets changed notifications get sent out to people<br>
+ letting them know about what changes have been made. This is a<br>
+ significant feature, and all sorts of questions can be raised, but<br>
+ they mainly boil down to when they should be sent and what they should<br>
+ look like.<br>
<br>
-(a) Choose a selection of bugs you're interested in. This would be<br>
-similar to CC except you let the set be computed from selection criteria<br>
-rather than limited to the bugs your name is on. There is currently a<br>
-limited version of this in the bugzilla preferences, ie "all qualifying<br>
-bugs"/"all qualifying bugs except the ones I change"/"only those bugs<br>
-which I am listed on the cc line".<br>
-(b) Choose what changes will trigger a notification for the bugs you are<br>
-watching. With this, you could choose whether you want to receive cc,<br>
-dependency and keyword changes, for example.<br>
+ Changes You're Interested In<br>
<br>
-Both of these proposals live at<br>
-"http://bugzilla.mozilla.org/show_bug.cgi?id=14137".<br>
-Note that they also live at<br>
-"http://bugzilla.mozilla.org/show_bug.cgi?id=17464", and the change <br>
-has been checked in. This is fixed with Bugzilla 2.12 and is no longer<br>
-an issue. Woo-Hoo!</P
-></P
-></DIV
-><DIV
-CLASS="SECTION"
-><HR><H1
-CLASS="SECTION"
-><A
-NAME="SEARCHING"
->6.2. Better Searching</A
-></H1
-><P
-><P
-CLASS="LITERALLAYOUT"
->Current searching tools in Bugzilla include the querying mechanism,<br>
-special summary reports and dependency trees. This message is about new<br>
-facilities.<br>
+ As of version 2.12 users can specify what sort of changes they are<br>
+ interested in receiving notifications for. However, this is still<br>
+ limited. As yet there is no facility to specify which keywords you<br>
+ care about, and whether you care about changes to fields such as the<br>
+ QA contact changes.<br>
+ Furthermore, often an unnecessary comment will go along with a change,<br>
+ either because it is required, or the commenter is ignorant of how the<br>
+ new system works. While explaining why you did something is useful,<br>
+ merely commenting on what you did is not because that information is<br>
+ already accessible view "Bug Activity".<br>
<br>
-1. General Summary Reports<br>
+ Because of this unnecessary comment, a lot of changes that would<br>
+ otherwise not generate notifications for certain people do so, because<br>
+ few people are willing to turn off comments. One way to deal with<br>
+ this problem is to allow people to specify that their comments are<br>
+ purely explanatory, and that anyone who is not interested in the<br>
+ change will not be interested in the comment.<br>
<br>
-For some time now it has been apparent to me that the query bug list<br>
-leaves a little to be desired in its linear nature. There is a need to<br>
-have categorised subsets, and counts of each category. If you don't<br>
-believe me, how about these facilities already in place or which people<br>
-have asked for:<br>
+ Furthermore, one possible rationale for unnecessary comments is that<br>
+ the bug activity does not display on the normal page and hence it is<br>
+ difficult to cross reference comments and actions. Hence, it would be<br>
+ beneficial to be able to do this.<br>
<br>
-Most Doomed Reports - Categorised On Assignee, Shows and Counts Number<br>
-of Bugs For Each Assignee<br>
-Bug #15806 (Most Voted For Bugs) - Categorised On Product, Shows Bugs<br>
-Voters Most Want Fixed<br>
-Bug #9789 (BugAThon Tracking Page) - Categorised On Developer (Subset),<br>
-Counts Number of Bugs<br>
-Bug #9409 and #9411 - The desire to be able to report on more subsets.<br>
+ Bugs You're Watching<br>
<br>
-Hopefully you can see the gist of what is desired here. It's a general<br>
-reporting mechanism.<br>
+ Currently to receive a notification about a bug you need to have your<br>
+ name on it. This is suboptimal because you need to know about a bug<br>
+ before you can receive notifications on it. Often you are interested<br>
+ in any bug with a field set to a specific value. For example, you<br>
+ might be interested in all bugs with a specific product, component or<br>
+ keyword.<br>
<br>
-This mechanism lets you choose the subset of bugs to operate on (like<br>
-query), let's you categorise them, possibly along with subcategories and<br>
-counts the number of bugs within each category. It might or might not<br>
-show the actual bugs themselves, and it might limit the number of bugs<br>
-within a category, or categories to report on.<br>
+ If someone could automatically receive notifications about these bugs,<br>
+ it would make everyone's lives easier. Currently the default assignee<br>
+ and QA contact for a component will automatically receive<br>
+ notifications for<br>
<br>
-I'm further sure that many applications of this mechanism would only be<br>
-recognised once it was implemented.<br>
+ Question: This moves half way to a BCC.<br>
<br>
-The general summary reports bug is at<br>
-"http://bugzilla.mozilla.org/show_bug.cgi?id=12282".<br>
+ Bulk Changes<br>
<br>
-2. Related Bugs<br>
+ A very useful feature of Bugzilla is the ability to perform an action<br>
+ on multiple bugs at once. However, this means that similar<br>
+ notifications are currently generated for each bug modified.<br>
<br>
-It would be nice to have a field where you could enter other bugs<br>
-related to the current bug - it would be handy for navigation and<br>
-possibly even finding duplicates. See<br>
-"http://bugzilla.mozilla.org/show_bug.cgi?id=12286".<br>
+ This can result in a torrent of notifications that can annoy.<br>
<br>
-3. Column Specification Support<br>
+ Furthermore, since the bugs are all changed close to each other in<br>
+ time, it is easy for someone to mass delete all the notifications<br>
+ generated by a bulk change and miss an unrelated notification in the<br>
+ middle.<br>
<br>
-Currently query seems to get what columns to report on from whatever the<br>
-user last used. This doesn't work well for "prepackaged queries", where<br>
-you followed a link. You can probably add a column by specifying a sort<br>
-column, but this is difficult and suboptimal.<br>
+ These factors can lead to a tendency for people to delay bulk changes,<br>
+ or avoid them entirely. This is suboptimal.<br>
<br>
-Furthermore, I find that when I want to add a column to a query, it's<br>
-usually a one off and I would prefer it to go away for the next query. <br>
-Hence, it would be nice to specify the columns that appear on the query<br>
-(and general summary report) pages. The default query mechanism should<br>
-be able to let you specify your default columns.<br>
+ It would be better if a bulk change generated only one notification<br>
+ mail. This would vastly reduce the annoyance factor, and prevent<br>
+ accidental deletion of notifications.<br>
<br>
-This proposal lives at<br>
-"http://bugzilla.mozilla.org/show_bug.cgi?id=12284".</P
-></P
+ One problem with this change is that some people separate out<br>
+ notifications using filtering. This means that they would no longer<br>
+ be match parts of a bulk change under different filtering rules.<br>
+<br>
+ One possibility to resolve this is to allow people to specify groups<br>
+ of bugs. All bugs within a group would go into the same<br>
+ notification. The filters could then distinguish the different bug<br>
+ groups.<br>
+<br>
+ In any case, it is likely there would need to be a transition period<br>
+ to allow people to alter their filters.<br>
+<br>
+Nominations<br>
+<br>
+ ?<br>
+<br>
+Linking Bugzilla Installations<br>
+<br>
+ The first example of linking Bugzilla installations together has is<br>
+ the introduction of bug moving in version 2.12. However, it would be<br>
+ useful to be able to link installations in more ways.<br>
+ * Dependencies and other relationships between bugs in other<br>
+ installations. This is difficult because dependencies are<br>
+ synchronised on both bugs, so the installation that changes<br>
+ dependencies would need to communicate the new state to the other<br>
+ installation. It would also mean that relationships and<br>
+ notifications that refer to other bugs would need to communicate<br>
+ with the other installation.<br>
+ * References to bugs in other installations. Currently if you type<br>
+ "bug XXX" or "bug #XXX" where XXX is a number, you get an<br>
+ automatic hyperlink to that bug. It would be useful if you could<br>
+ say "YYY bug #XXX" where YYY is the name of another installation.<br>
+<br>
+Retirement<br>
+<br>
+ ?<br>
+<br>
+Whiny Reports<br>
+<br>
+ ?<br>
+<br>
+ Group Redesign<br>
+<br>
+ ?<br>
+<br>
+ Hard Wrapping Comments<br>
+<br>
+ Currently Bugzilla "hard wraps" its comments to a specific line size,<br>
+ similar to E-Mail. This has various problems:<br>
+ * The way it currently works, wrapping is done in the browser at<br>
+ submission time using a non-standard HTML extension not supported<br>
+ by some (uncommon) browsers. These browsers generate comments<br>
+ that scroll off the right side of the screen.<br>
+ * Because comments are of fixed width, when you expand your browser<br>
+ window, the comments do not expand to fit available space.<br>
+<br>
+ It would be much better to move to a world of soft wrapping, where the<br>
+ browser wraps the text at display time, similar to a world processor.<br>
+ And as in a word processor, soft wrapping does not preclude the<br>
+ insertion of newlines.<br>
+<br>
+ Hard wrapping is too entrenched into text E-Mail to fix, but we can<br>
+ fix Bugzilla without causing any problems. The old content will still<br>
+ be wrapped too early, but at least new content will work.<br>
+ </P
+>
+ </P
></DIV
><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="VARIANTS"
+>Chapter 7. Bugzilla Variants and Competitors</A
+></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
+><DIV
CLASS="SECTION"
><HR><H1
CLASS="SECTION"
><A
-NAME="TRACKINGBUGS"
->6.3. Description Flags and Tracking Bugs</A
+NAME="RHBUGZILLA"
+>7.1. Red Hat Bugzilla</A
></H1
><P
+> Red Hat Bugzilla is probably the most popular Bugzilla variant
+ on the planet. One of the major benefits of Red Hat Bugzilla is
+ the ability to work with Oracle, MySQL, and PostGreSQL databases
+ serving as the back-end, instead of just MySQL. Dave Lawrence
+ has worked very hard to keep Red Hat Bugzilla up-to-date, and
+ many people prefer the snappier-looking page layout of Red Hat
+ Bugzilla to the default Mozilla-standard formatting.
+ </P
><P
-CLASS="LITERALLAYOUT"
->Since I last posted on this issue, we now have "keywords" that solve<br>
-many of the issues of description and status whiteboard keywords. We<br>
-have seen a migration towards keywords, but there is still further to<br>
-go.<br>
-<br>
-Description ( + Status Whiteboard ) Keywords<br>
---------------------------------------------<br>
-<br>
-Some description keywords remain. I'd like to hear what reasons, other<br>
-than time, there are for these staying as they are. I'm suspecting many<br>
-are not really being used. Hopefully we can totally remove these<br>
-eventually.<br>
-<br>
-Tracking Bugs<br>
--------------<br>
-<br>
-When I suggested keywords, I did so to get rid of tracking bugs too,<br>
-though we've had less success on that front.<br>
-<br>
-There are many disadvantages to tracking bugs.<br>
-<br>
-- They can pollute bugs counts, and you must make sure you exclude<br>
-them. I believe the meta keyword might be used for this purpose.<br>
-- They have an assignee but there is nothing to fix, and that person can<br>
-get whined at by Bugzilla.<br>
-- It would be better to craft your own "dependency tree" rather than<br>
-rely on a fixed hierachy in the bug system.<br>
-- In creating a nice little hierachy, many bugs duplicate information<br>
-that should be available in other ways, eg<br>
-"http://bugzilla.mozilla.org/show_bug.cgi?id=12833" which is<br>
-about beta 1 networking issues. These could fall behind the actual<br>
-data. What tracking bugs are good for, ad hoc lists, is what keywords<br>
-are better for.<br>
-- An automatically generated dependency structure between one "tracking<br>
-bug" and another would be better than a manual one, since it gives exact<br>
-rather than manually set up classifications.<br>
-<br>
-Probably the only feature preventing tracking bugs being replaced is the<br>
-dependency tree. The quintessential tracking bug seems to be bug #7229<br>
-"chofmann's watch list", which probably has about a couple of hundred<br>
-bugs at various levels, which allows a nice visualisation.<br>
-<br>
-Before keywords can replace tracking bugs better visualisation is going<br>
-to be required. General summary reports and dependency forests of a bug<br>
-list ("http://bugzilla.mozilla.org/show_bug.cgi?id=12992") could both<br>
-help, but neither solves the problem totally. Perhaps keywords within<br>
-keywords would help here. In any case, I'm still thinking about this<br>
-one.<br>
-<br>
-Some tracking bugs could definitely be turned into keywords immediately<br>
-though, and I'll point the finger at<br>
-"http://bugzilla.mozilla.org/show_bug.cgi?id=7954" here since that's<br>
-what came to mind first.</P
+>URL: <A
+HREF="http://bugzilla.redhat.com/bugzilla/"
+TARGET="_top"
+>http://bugzilla.redhat.com/bugzilla/</A
></P
></DIV
><DIV
@@ -7013,83 +10954,40 @@ CLASS="SECTION"
><HR><H1
CLASS="SECTION"
><A
-NAME="BUGPROBS"
->6.4. Bug Issues</A
+NAME="VARIANT_FENRIS"
+>7.2. Loki Bugzilla (Fenris)</A
></H1
><P
+>Fenris can be found at <A
+HREF="http://fenris.lokigames.com/"
+TARGET="_top"
+>http://fenris.lokigames.com</A
+>. It is a fork from Bugzilla.</P
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H1
+CLASS="SECTION"
+><A
+NAME="VARIANT_ISSUEZILLA"
+>7.3. Issuezilla</A
+></H1
><P
-CLASS="LITERALLAYOUT"
->1. Inline Bug Changes<br>
-<br>
-Why do I see so many "moving to M5" and "reassigning to blahblah"<br>
-messages, and in other circumstances none are entered? Why aren't these<br>
-automatically generated? A comment should be only necessary when there<br>
-is something to add, and if I'm not interested in this sort of<br>
-information, I should be able to hide it.<br>
-<br>
-At the moment we're in a hybrid world where we don't get everything, but<br>
-we can't get rid of the bug change "messages" either. Furthermore,<br>
-"View Bug Activity" requires me to manually cross reference events on<br>
-another page, rather than being able to visually see the chronological<br>
-order. Shouldn't I be able to see all the information on one page?<br>
-<br>
-A proposal to allow bugs to be shown either way is at<br>
-"http://bugzilla.mozilla.org/show_bug.cgi?id=11368".<br>
-<br>
-2. Hard Wrapping Comments<br>
-<br>
-One thing that annoys me is the fact that comments are "hard wrapped" to<br>
-a certain column width. This is a mistake Internet Mail and News has<br>
-made, unlike every word processor in existence, and as a consequence,<br>
-Usenet suffers to this day from bad software. Why has Bugzilla repeated<br>
-the problem?<br>
-<br>
-Hard wrapping to a certain column width is open to abuse (see old<br>
-Mozilla browsers that didn't wrap properly, resulting in many ugly bug<br>
-reports we have to read to this day), and furthermore doesn't expand to<br>
-fill greater screen sizes. I'm also under the impression the current<br>
-hard wrap uses a non-standard HTML facility. See<br>
-"http://bugzilla.mozilla.org/show_bug.cgi?id=11901".<br>
-<br>
-3. REMIND and LATER Are Evil<br>
-<br>
-I really hate REMIND and LATER. Not because they mean something<br>
-won't be implemented, but because they aren't the best solutions.<br>
-<br>
-Why are they bad? Well, basically because they are not resolved, yet<br>
-they are marked as such. Hence queries have to be well crafted to<br>
-include them.<br>
-<br>
-LATER, according to Bugzilla, means it won't be done this release. <br>
-There is a better mechanism of doing this, that is assigning to<br>
-nobody@mozilla.org and making the milestone blank. It's more likely to<br>
-appear in a casual query, and it doesn't resolve the bug.<br>
-<br>
-REMIND, according to Bugzilla, means it might still be implemented this<br>
-release. Well, why not just move it to a later milestone then? You're<br>
-a lot less likely to forget it. If it's really needed, a keyword would<br>
-be better.<br>
-<br>
-Some people can't use blank milestones to mean an untargetted milestone,<br>
-since they use this to assess new bugs that have no target. Hence, it<br>
-would be nice to distinguish between bugs that have not yet been<br>
-considered, and those that really are not assigned to any milestone in<br>
-the future (assumedly beyond).<br>
-<br>
-All this is covered at<br>
-"http://bugzilla.mozilla.org/show_bug.cgi?id=13534".<br>
-<br>
-4. Create An Enhancement Field<br>
-<br>
-Currently enhancement is an option in severity. This means that<br>
-important enhancements (like for example, POP3 support) are not properly<br>
-distinguished as such, because they need a proper severity. This<br>
-dilutes the meaning of enhancement.<br>
-<br>
-If enhancement was separated, we could properly see what was an<br>
-enhancement. See "http://bugzilla.mozilla.org/show_bug.cgi?id=9412". I<br>
-see keywords like [RFE] and [FEATURE] that seem to be compensating for<br>
-this problem.</P
+>Issuezilla is another fork from Bugzilla, and seems nearly
+ as popular as the Red Hat Bugzilla fork. Some Issuezilla team
+ members are regular contributors to the Bugzilla mailing
+ list/newsgroup. Issuezilla is not the primary focus of
+ bug-tracking at tigris.org, however. Their Java-based
+ bug-tracker, <A
+HREF="#VARIANT_SCARAB"
+>Scarab, a newfangled Java-based issue tracker</A
+>, is under heavy development
+ and looks promising!</P
+><P
+>URL: <A
+HREF="http://issuezilla.tigris.org/servlets/ProjectHome"
+TARGET="_top"
+>http://issuezilla.tigris.org/servlets/ProjectHome</A
></P
></DIV
><DIV
@@ -7097,51 +10995,20 @@ CLASS="SECTION"
><HR><H1
CLASS="SECTION"
><A
-NAME="DBASEINTEGRITY"
->6.5. Database Integrity</A
+NAME="VARIANT_SCARAB"
+>7.4. Scarab</A
></H1
><P
+>Scarab is a promising new bug-tracking system built using
+ Java Serlet technology. As of this writing, no source code has
+ been released as a package, but you can obtain the code from
+ CVS.
+ </P
><P
-CLASS="LITERALLAYOUT"
->Bugzilla could be more proactive in detecting suboptimal situations and<br>
-prevent them or whine about them.<br>
-<br>
-1. Bugzilla Crime #1: Marking A Bug Fixed With Unresolved Dependencies<br>
-<br>
-It can't be marked fixed with unresolved dependencies. Either mark it<br>
-INVALID (tracking bugs), fix the dependencies at the same time, or<br>
-resolve the blockers.<br>
-<br>
-See "http://bugzilla.mozilla.org/show_bug.cgi?id=24496".<br>
-<br>
-2. Keyword Restrictions<br>
-<br>
-Some keywords should only apply in certain circumstances, eg beta1 =><br>
-Milestone <<br>
-M14, css1 => Component = Style System are possibilities. See<br>
-"http://bugzilla.mozilla.org/show_bug.cgi?id=26940".<br>
-<br>
-3. Whine About Old Votes<br>
-<br>
-Old votes can just sit on resolved bugs. This is problematic with<br>
-duplicates especially. Automatic transferral/removal is not<br>
-appropriate since bugs can be reopened, but a whining solution might<br>
-work. See "http://bugzilla.mozilla.org/show_bug.cgi?id=27553".<br>
-<br>
-4. Whine And Warn About Milestone Mismatches<br>
-<br>
-Here's a fun one. Bug X (M17) depends on Bug Y (M15). Bug Y gets moved<br>
-out to M19. The notification to the assignee of Bug X gets ignored (of<br>
-course) and Bug X is now due to be fixed before one of its blockers.<br>
-<br>
-Warnings about this when it is detected as well as whining about it in<br>
-email would help bring these issues to the attention of people sooner.<br>
-<br>
-Note that this would be less of a problem if we didn't have so many<br>
-tracking bugs since they aren't updated that often and often have this<br>
-problem.<br>
-<br>
-See "http://bugzilla.mozilla.org/show_bug.cgi?id=16743".</P
+>URL: <A
+HREF="http://scarab.tigris.org/"
+TARGET="_top"
+>http://scarab.tigris.org</A
></P
></DIV
><DIV
@@ -7149,11 +11016,42 @@ CLASS="SECTION"
><HR><H1
CLASS="SECTION"
><A
-NAME="BZ30"
->6.6. Bugzilla 3.0</A
+NAME="VARIANT_PERFORCE"
+>7.5. Perforce SCM</A
+></H1
+><P
+>Although Perforce isn't really a bug tracker, it can be used
+ as such through the <SPAN
+CLASS="QUOTE"
+>"jobs"</SPAN
+> functionality.</P
+><P
+><A
+HREF="http://www.perforce.com/perforce/technotes/note052.html"
+TARGET="_top"
+>http://www.perforce.com/perforce/technotes/note052.html</A
+>http://www.perforce.com/perforce/technotes/note052.html</P
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H1
+CLASS="SECTION"
+><A
+NAME="VARIANT_SOURCEFORGE"
+>7.6. SourceForge</A
></H1
><P
->One day, Bugzilla 3.0 will have lots of cool stuff.</P
+>SourceForge is more of a way of coordinating geographically
+ distributed free software and open source projects over the
+ Internet than strictly a bug tracker, but if you're hunting for
+ bug-tracking for your open project, it may be just what the
+ software engineer ordered!</P
+><P
+>URL: <A
+HREF="http://www.sourceforge.net"
+TARGET="_top"
+>http://www.sourceforge.net</A
+></P
></DIV
></DIV
><DIV
@@ -7175,63 +11073,63 @@ HREF="#FAQ_GENERAL"
><DL
><DT
>A.1.1. <A
-HREF="#AEN1302"
+HREF="#AEN1713"
> Where can I find information about Bugzilla?</A
></DT
><DT
>A.1.2. <A
-HREF="#AEN1308"
+HREF="#AEN1719"
> What license is Bugzilla distributed under?
</A
></DT
><DT
>A.1.3. <A
-HREF="#AEN1314"
+HREF="#AEN1725"
> How do I get commercial support for Bugzilla?
</A
></DT
><DT
>A.1.4. <A
-HREF="#AEN1321"
+HREF="#AEN1732"
> What major companies or projects are currently using Bugzilla
for bug-tracking?
</A
></DT
><DT
>A.1.5. <A
-HREF="#AEN1346"
+HREF="#AEN1757"
> Who maintains Bugzilla?
</A
></DT
><DT
>A.1.6. <A
-HREF="#AEN1351"
+HREF="#AEN1763"
> How does Bugzilla stack up against other bug-tracking databases?
</A
></DT
><DT
>A.1.7. <A
-HREF="#AEN1358"
+HREF="#AEN1770"
> How do I change my user name in Bugzilla?
</A
></DT
><DT
>A.1.8. <A
-HREF="#AEN1363"
+HREF="#AEN1775"
> Why doesn't Bugzilla offer this or that feature or compatability
with this other tracking software?
</A
></DT
><DT
>A.1.9. <A
-HREF="#AEN1370"
+HREF="#AEN1782"
> Why MySQL? I'm interested in seeing Bugzilla run on
Oracle/Sybase/Msql/PostgreSQL/MSSQL?
</A
></DT
><DT
>A.1.10. <A
-HREF="#AEN1388"
+HREF="#AEN1800"
> Why do the scripts say "/usr/bonsaitools/bin/perl" instead of
"/usr/bin/perl" or something else?
</A
@@ -7247,19 +11145,19 @@ HREF="#FAQ_REDHAT"
><DL
><DT
>A.2.1. <A
-HREF="#AEN1405"
+HREF="#AEN1817"
> What about Red Hat Bugzilla?
</A
></DT
><DT
>A.2.2. <A
-HREF="#AEN1413"
+HREF="#AEN1825"
> What are the primary benefits of Red Hat Bugzilla?
</A
></DT
><DT
>A.2.3. <A
-HREF="#AEN1441"
+HREF="#AEN1853"
> What's the current status of Red Hat Bugzilla?
</A
></DT
@@ -7274,20 +11172,8 @@ HREF="#FAQ_LOKI"
><DL
><DT
>A.3.1. <A
-HREF="#AEN1457"
-> What about Loki Bugzilla?
- </A
-></DT
-><DT
->A.3.2. <A
-HREF="#AEN1464"
-> Who maintains Fenris (Loki Bugzilla) now?
- </A
-></DT
-><DT
->A.3.3. <A
-HREF="#AEN1469"
->
+HREF="#AEN1866"
+> What is Loki Bugzilla (Fenris)?
</A
></DT
></DL
@@ -7301,41 +11187,41 @@ HREF="#FAQ_PHB"
><DL
><DT
>A.4.1. <A
-HREF="#AEN1477"
+HREF="#AEN1877"
> Is Bugzilla web-based or do you have to have specific software or
specific operating system on your machine?
</A
></DT
><DT
>A.4.2. <A
-HREF="#AEN1482"
+HREF="#AEN1882"
> Has anyone you know of already done any Bugzilla integration with
Perforce (SCM software)?
</A
></DT
><DT
>A.4.3. <A
-HREF="#AEN1487"
+HREF="#AEN1887"
> Does Bugzilla allow the user to track multiple projects?
</A
></DT
><DT
>A.4.4. <A
-HREF="#AEN1492"
+HREF="#AEN1892"
> If I am on many projects, and search for all bugs assigned to me, will
Bugzilla list them for me and allow me to sort by project, severity etc?
</A
></DT
><DT
>A.4.5. <A
-HREF="#AEN1497"
+HREF="#AEN1897"
> Does Bugzilla allow attachments (text, screenshots, urls etc)? If yes,
are there any that are NOT allowed?
</A
></DT
><DT
>A.4.6. <A
-HREF="#AEN1502"
+HREF="#AEN1902"
> 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?
@@ -7343,43 +11229,51 @@ HREF="#AEN1502"
></DT
><DT
>A.4.7. <A
-HREF="#AEN1507"
+HREF="#AEN1909"
+> The index.html page doesn't show the footer. It's really annoying to have
+ to go to the querypage just to check my "my bugs" link. How do I get a footer
+ on static HTML pages?
+ </A
+></DT
+><DT
+>A.4.8. <A
+HREF="#AEN1931"
> Does Bugzilla provide any reporting features, metrics, graphs, etc? You
know, the type of stuff that management likes to see. :)
</A
></DT
><DT
->A.4.8. <A
-HREF="#AEN1515"
+>A.4.9. <A
+HREF="#AEN1939"
> Is there email notification and if so, what do you see when you get an
email? Do you see bug number and title or is it only the number?
</A
></DT
><DT
->A.4.9. <A
-HREF="#AEN1520"
+>A.4.10. <A
+HREF="#AEN1944"
> Can email notification be set up to send to multiple
people, some on the To List, CC List, BCC List etc?
</A
></DT
><DT
->A.4.10. <A
-HREF="#AEN1525"
+>A.4.11. <A
+HREF="#AEN1949"
> If there is email notification, do users have to have any particular
type of email application?
</A
></DT
><DT
->A.4.11. <A
-HREF="#AEN1532"
+>A.4.12. <A
+HREF="#AEN1956"
> If I just wanted to track certain bugs, as they go through life, can I
set it up to alert me via email whenever that bug changes, whether it be
owner, status or description etc.?
</A
></DT
><DT
->A.4.12. <A
-HREF="#AEN1537"
+>A.4.13. <A
+HREF="#AEN1961"
> 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
@@ -7387,56 +11281,48 @@ HREF="#AEN1537"
</A
></DT
><DT
->A.4.13. <A
-HREF="#AEN1545"
-> Does Bugzilla allow fields to be added, changed or deleted? If I want to
- customize the bug submission form to meet our needs, can I do that using our
- terminology?
- </A
-></DT
-><DT
>A.4.14. <A
-HREF="#AEN1550"
+HREF="#AEN1969"
> Has anyone converted Bugzilla to another language to be used in other
countries? Is it localizable?
</A
></DT
><DT
>A.4.15. <A
-HREF="#AEN1555"
+HREF="#AEN1974"
> Can a user create and save reports? Can they do this in Word format?
Excel format?
</A
></DT
><DT
>A.4.16. <A
-HREF="#AEN1560"
+HREF="#AEN1979"
> Can a user re-run a report with a new project, same query?
</A
></DT
><DT
>A.4.17. <A
-HREF="#AEN1565"
+HREF="#AEN1984"
> Can a user modify an existing report and then save it into another name?
</A
></DT
><DT
>A.4.18. <A
-HREF="#AEN1570"
+HREF="#AEN1989"
> Does Bugzilla have the ability to search by word, phrase, compound
search?
</A
></DT
><DT
>A.4.19. <A
-HREF="#AEN1575"
+HREF="#AEN1994"
> Can the admin person establish separate group and individual user
privileges?
</A
></DT
><DT
>A.4.20. <A
-HREF="#AEN1580"
+HREF="#AEN1999"
> 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?
@@ -7444,19 +11330,19 @@ HREF="#AEN1580"
></DT
><DT
>A.4.21. <A
-HREF="#AEN1585"
+HREF="#AEN2004"
> Are there any backup features provided?
</A
></DT
><DT
>A.4.22. <A
-HREF="#AEN1591"
+HREF="#AEN2010"
> Can users be on the system while a backup is in progress?
</A
></DT
><DT
>A.4.23. <A
-HREF="#AEN1596"
+HREF="#AEN2015"
> 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
@@ -7466,7 +11352,7 @@ HREF="#AEN1596"
></DT
><DT
>A.4.24. <A
-HREF="#AEN1603"
+HREF="#AEN2022"
> 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
@@ -7476,7 +11362,7 @@ HREF="#AEN1603"
></DT
><DT
>A.4.25. <A
-HREF="#AEN1608"
+HREF="#AEN2027"
> 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
@@ -7492,19 +11378,19 @@ HREF="#FAQ_INSTALL"
><DL
><DT
>A.5.1. <A
-HREF="#AEN1615"
+HREF="#AEN2034"
> How do I download and install Bugzilla?
</A
></DT
><DT
>A.5.2. <A
-HREF="#AEN1621"
+HREF="#AEN2040"
> How do I install Bugzilla on Windows NT?
</A
></DT
><DT
>A.5.3. <A
-HREF="#AEN1626"
+HREF="#AEN2045"
> Is there an easy way to change the Bugzilla cookie name?
</A
></DT
@@ -7519,20 +11405,20 @@ HREF="#FAQ_SECURITY"
><DL
><DT
>A.6.1. <A
-HREF="#AEN1633"
+HREF="#AEN2052"
> How do I completely disable MySQL security if it's giving me problems
- (I've followed the instructions in the README!)?
+ (I've followed the instructions in the installation section of this guide!)?
</A
></DT
><DT
>A.6.2. <A
-HREF="#AEN1639"
+HREF="#AEN2058"
> Are there any security problems with Bugzilla?
</A
></DT
><DT
>A.6.3. <A
-HREF="#AEN1644"
+HREF="#AEN2063"
> 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.
@@ -7549,48 +11435,48 @@ HREF="#FAQ_EMAIL"
><DL
><DT
>A.7.1. <A
-HREF="#AEN1651"
+HREF="#AEN2070"
> I have a user who doesn't want to receive any more email from Bugzilla.
How do I stop it entirely for this user?
</A
></DT
><DT
>A.7.2. <A
-HREF="#AEN1656"
+HREF="#AEN2075"
> I'm evaluating/testing Bugzilla, and don't want it to send email to
anyone but me. How do I do it?
</A
></DT
><DT
>A.7.3. <A
-HREF="#AEN1661"
+HREF="#AEN2080"
> I want whineatnews.pl to whine at something more, or other than, only new
bugs. How do I do it?
</A
></DT
><DT
>A.7.4. <A
-HREF="#AEN1667"
+HREF="#AEN2086"
> I don't like/want to use Procmail to hand mail off to bug_email.pl.
What alternatives do I have?
</A
></DT
><DT
>A.7.5. <A
-HREF="#AEN1674"
+HREF="#AEN2093"
> How do I set up the email interface to submit/change bugs via email?
</A
></DT
><DT
>A.7.6. <A
-HREF="#AEN1679"
+HREF="#AEN2098"
> Email takes FOREVER to reach me from bugzilla -- it's extremely slow.
What gives?
</A
></DT
><DT
>A.7.7. <A
-HREF="#AEN1686"
+HREF="#AEN2105"
> How come email never reaches me from bugzilla changes?
</A
></DT
@@ -7605,60 +11491,60 @@ HREF="#FAQ_DB"
><DL
><DT
>A.8.1. <A
-HREF="#AEN1694"
+HREF="#AEN2113"
> I've heard Bugzilla can be used with Oracle?
</A
></DT
><DT
>A.8.2. <A
-HREF="#AEN1699"
+HREF="#AEN2118"
> Bugs are missing from queries, but exist in the database (and I can pull
them up by specifying the bug ID). What's wrong?
</A
></DT
><DT
>A.8.3. <A
-HREF="#AEN1704"
+HREF="#AEN2123"
> I think my database might be corrupted, or contain invalid entries. What
do I do?
</A
></DT
><DT
>A.8.4. <A
-HREF="#AEN1709"
+HREF="#AEN2131"
> I want to manually edit some entries in my database. How?
</A
></DT
><DT
>A.8.5. <A
-HREF="#AEN1714"
+HREF="#AEN2136"
> I try to add myself as a user, but Bugzilla always tells me my password is wrong.
</A
></DT
><DT
>A.8.6. <A
-HREF="#AEN1719"
+HREF="#AEN2141"
> I think I've set up MySQL permissions correctly, but bugzilla still can't
connect.
</A
></DT
><DT
>A.8.7. <A
-HREF="#AEN1724"
+HREF="#AEN2146"
> How do I synchronize bug information among multiple different Bugzilla
databases?
</A
></DT
><DT
>A.8.8. <A
-HREF="#AEN1731"
+HREF="#AEN2153"
> Why do I get bizarre errors when trying to submit data, particularly problems
with "groupset"?
</A
></DT
><DT
>A.8.9. <A
-HREF="#AEN1736"
+HREF="#AEN2158"
> How come even after I delete bugs, the long descriptions show up?
</A
></DT
@@ -7673,32 +11559,32 @@ HREF="#FAQ_NT"
><DL
><DT
>A.9.1. <A
-HREF="#AEN1743"
+HREF="#AEN2168"
> What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
</A
></DT
><DT
>A.9.2. <A
-HREF="#AEN1748"
+HREF="#AEN2173"
> Is there a "Bundle::Bugzilla" equivalent for Win32?
</A
></DT
><DT
>A.9.3. <A
-HREF="#AEN1753"
+HREF="#AEN2178"
> CGI's are failing with a "something.cgi is not a valid Windows NT
application" error. Why?
</A
></DT
><DT
>A.9.4. <A
-HREF="#AEN1761"
+HREF="#AEN2186"
> Can I have some general instructions on how to make Bugzilla on Win32 work?
</A
></DT
><DT
>A.9.5. <A
-HREF="#AEN1767"
+HREF="#AEN2192"
> I'm having trouble with the perl modules for NT not being able to talk to
to the database.
</A
@@ -7714,34 +11600,34 @@ HREF="#FAQ_USE"
><DL
><DT
>A.10.1. <A
-HREF="#AEN1788"
+HREF="#AEN2213"
> The query page is very confusing. Isn't there a simpler way to query?
</A
></DT
><DT
>A.10.2. <A
-HREF="#AEN1794"
+HREF="#AEN2219"
> I'm confused by the behavior of the "accept" button in the Show Bug form.
Why doesn't it assign the bug to me when I accept it?
</A
></DT
><DT
>A.10.3. <A
-HREF="#AEN1804"
+HREF="#AEN2229"
> I can't upload anything into the database via the "Create Attachment"
link. What am I doing wrong?
</A
></DT
><DT
>A.10.4. <A
-HREF="#AEN1809"
+HREF="#AEN2234"
> Email submissions to Bugzilla that have attachments end up asking me to
save it as a "cgi" file.
</A
></DT
><DT
>A.10.5. <A
-HREF="#AEN1814"
+HREF="#AEN2239"
> How do I change a keyword in Bugzilla, once some bugs are using it?
</A
></DT
@@ -7756,20 +11642,20 @@ HREF="#FAQ_HACKING"
><DL
><DT
>A.11.1. <A
-HREF="#AEN1821"
+HREF="#AEN2246"
> What bugs are in Bugzilla right now?
</A
></DT
><DT
>A.11.2. <A
-HREF="#AEN1830"
+HREF="#AEN2255"
> How can I change the default priority to a null value? For instance, have the default
priority be "---" instead of "P2"?
</A
></DT
><DT
>A.11.3. <A
-HREF="#AEN1836"
+HREF="#AEN2261"
> What's the best way to submit patches? What guidelines should I follow?
</A
></DT
@@ -7789,7 +11675,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1302"
+NAME="AEN1713"
></A
><B
>A.1.1. </B
@@ -7815,7 +11701,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1308"
+NAME="AEN1719"
></A
><B
>A.1.2. </B
@@ -7842,7 +11728,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1314"
+NAME="AEN1725"
></A
><B
>A.1.3. </B
@@ -7877,7 +11763,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1321"
+NAME="AEN1732"
></A
><B
>A.1.4. </B
@@ -7985,7 +11871,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1346"
+NAME="AEN1757"
></A
><B
>A.1.5. </B
@@ -7997,13 +11883,12 @@ CLASS="ANSWER"
><P
><B
> </B
-> There are many, many contributors from around the world maintaining Bugzilla.
- The designated "Maintainer" is Tara Hernandez, with QA support by Matthew Tuck.
- Dan Mosedale and Dawn Endico are employees of Mozilla.org responsible for the
- installation of Bugzilla there, and are very frequent code contributors.
- Terry Weissman originally ported Bugzilla, but "these days, Terry just hangs around
- and heckles." The rest of us are mostly transient developers; Bugzilla suits
- our needs, and we contribute code as we have needs for updates.
+> Bugzilla maintenance has been in a state of flux recently.
+ Please check <A
+HREF="http://www.mozilla.org/projects/bugzilla/"
+TARGET="_top"
+>the Bugzilla Project Page for the latest details. </A
+>
</P
></DIV
></DIV
@@ -8013,7 +11898,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1351"
+NAME="AEN1763"
></A
><B
>A.1.6. </B
@@ -8027,18 +11912,22 @@ CLASS="ANSWER"
> </B
> A year has gone by, and I <EM
>still</EM
-> can't find any head-to-head
- comparisons of Bugzilla against other defect-tracking software. However, from my
- 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.
+> can't
+ find any head-to-head comparisons of Bugzilla against
+ other defect-tracking software. However, from my 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 Bugzilla vendor, please step forward with a rebuttal
- so I can include it in the FAQ. We're not in pursuit of Bugzilla ueber alles;
- we simply love having a powerful, open-source tool to get our jobs done.
+> If you happen to be a commercial bug-tracker vendor, please
+ step forward with a rebuttal so I can include it in the
+ FAQ. We're not in pursuit of Bugzilla ueber alles; we
+ simply love having a powerful, open-source tool to get our
+ jobs done.
</P
></DIV
></DIV
@@ -8048,7 +11937,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1358"
+NAME="AEN1770"
></A
><B
>A.1.7. </B
@@ -8071,7 +11960,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1363"
+NAME="AEN1775"
></A
><B
>A.1.8. </B
@@ -8109,7 +11998,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1370"
+NAME="AEN1782"
></A
><B
>A.1.9. </B
@@ -8124,7 +12013,7 @@ CLASS="ANSWER"
> </B
>Terry Weissman answers,
<A
-NAME="AEN1374"
+NAME="AEN1786"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
@@ -8200,7 +12089,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1388"
+NAME="AEN1800"
></A
><B
>A.1.10. </B
@@ -8220,7 +12109,7 @@ CLASS="ANSWER"
><P
> Here's Terry Weissman's comment, for some historical context:
<A
-NAME="AEN1393"
+NAME="AEN1805"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
@@ -8232,11 +12121,25 @@ CLASS="BLOCKQUOTE"
</P
><DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><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
-><B
->Note: </B
> We always recommend that, if possible, you keep the path
as /usr/bonsaitools/bin/perl, and simply add a /usr/bonsaitools
and /usr/bonsaitools/bin directory, then symlink your version
@@ -8247,7 +12150,9 @@ CLASS="NOTE"
> Obviously, if you do not have root access to your Bugzilla
box, our suggestion is irrelevant.
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
></BLOCKQUOTE
>
@@ -8265,17 +12170,33 @@ NAME="FAQ_REDHAT"
><P
> <DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><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
-><B
->Note: </B
> <EM
>This section is no longer up-to-date.</EM
>
Please see the section on "Red Hat Bugzilla" under "Variants" in The Bugzilla Guide.
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
>
</P
@@ -8285,7 +12206,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1405"
+NAME="AEN1817"
></A
><B
>A.2.1. </B
@@ -8309,7 +12230,7 @@ CLASS="ANSWER"
><P
> Dave Lawrence, the original Red Hat Bugzilla maintainer, mentions:
<A
-NAME="AEN1410"
+NAME="AEN1822"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
@@ -8332,7 +12253,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1413"
+NAME="AEN1825"
></A
><B
>A.2.2. </B
@@ -8348,7 +12269,7 @@ CLASS="ANSWER"
>Dave Lawrence</EM
>:
<A
-NAME="AEN1418"
+NAME="AEN1830"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
@@ -8464,7 +12385,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1441"
+NAME="AEN1853"
></A
><B
>A.2.3. </B
@@ -8478,23 +12399,39 @@ CLASS="ANSWER"
> </B
> <DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><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
-><B
->Note: </B
> This information is somewhat dated; I last updated it
7 June 2000. Please see the "Variants" section of "The Bugzilla Guide"
for more up-to-date information regarding Red Hat Bugzilla.
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
>
<EM
>Dave Lawrence</EM
>:
<A
-NAME="AEN1448"
+NAME="AEN1860"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
@@ -8557,39 +12494,17 @@ CLASS="QANDADIV"
NAME="FAQ_LOKI"
></A
>3. Loki Bugzilla (AKA Fenris)</H3
-><P
-> <DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
-><P
-><B
->Note: </B
-> Loki's "Fenris" Bugzilla is based upon the (now ancient) Bugzilla 2.8
- tree, and is no longer actively maintained.
- It works well enough for Loki. Additionally, the major
- differences in Fenris have now been integrated into
- the main source tree of Bugzilla, so there's not much
- reason to go grab the source. I leave this section of the
- FAQ principally for historical interest, but unless Loki has further
- input into Bugzilla's future, it will be deprecated in future versions
- of the Guide.
- </P
-></BLOCKQUOTE
-></DIV
->
- </P
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
-NAME="AEN1457"
+NAME="AEN1866"
></A
><B
>A.3.1. </B
-> What about Loki Bugzilla?
+> What is Loki Bugzilla (Fenris)?
</P
></DIV
><DIV
@@ -8598,67 +12513,11 @@ CLASS="ANSWER"
><B
> </B
> Loki Games has a customized version of Bugzilla available at
- http://fenris.lokigames.com. From that page,
<A
-NAME="AEN1461"
-></A
-><BLOCKQUOTE
-CLASS="BLOCKQUOTE"
-><P
-> You may have noticed that Fenris is a fork from Bugzilla-- our
- patches weren't suitable for integration --and a few people have
- expressed interest in the code. Fenris has one major improvement
- over Bugzilla, and that is individual comments are not appended
- onto a string blob, they are stored as a record in a separate
- table. This allows you to, for instance, separate comments out
- according to privilege levels in case your bug database could
- contain sensitive information not for public eyes. We also provide
- things like email hiding to protect user's privacy, additional
- fields such as 'user_affected' in case someone enters someone
- else's bug, comment editing and deletion, and more conditional
- system variables than Bugzilla does (turn off attachments,
- qacontact, etc.).
- </P
-></BLOCKQUOTE
->
- </P
-></DIV
-></DIV
-><DIV
-CLASS="QANDAENTRY"
-><DIV
-CLASS="QUESTION"
-><P
-><A
-NAME="AEN1464"
-></A
-><B
->A.3.2. </B
-> Who maintains Fenris (Loki Bugzilla) now?
- </P
-></DIV
-><DIV
-CLASS="ANSWER"
-><P
-><B
-> </B
-> Raphael Barrerro <raistlin@lokigames.com>.
- Michael Vance created the initial fork, but no longer
- maintains the project.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="QANDAENTRY"
-><DIV
-CLASS="QUESTION"
-><P
-><A
-NAME="AEN1469"
-></A
-><B
->A.3.3. </B
->
+HREF="http://fenris.lokigames.com/"
+TARGET="_top"
+>http://fenris.lokigames.com</A
+>. There are some advantages to using Fenris, chief being separation of comments based upon user privacy level, data hiding, forced login for any data retrieval, and some additional fields. Loki has mainted their code, originally a fork from the Bugzilla 2.8 code base, and it is quite a bit different than stock Bugzilla at this point. I recommend you stick with official Bugzilla version 2.14 rather than using a fork, but it's up to you.
</P
></DIV
></DIV
@@ -8673,15 +12532,31 @@ NAME="FAQ_PHB"
><P
> <DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><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
-><B
->Note: </B
> The title of this section doesn't mean you're a PHB -- it just means
you probably HAVE a PHB who wants to know this :)
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
>
</P
@@ -8691,7 +12566,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1477"
+NAME="AEN1877"
></A
><B
>A.4.1. </B
@@ -8715,7 +12590,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1482"
+NAME="AEN1882"
></A
><B
>A.4.2. </B
@@ -8730,9 +12605,6 @@ CLASS="ANSWER"
> </B
> Yes! You can find more information elsewhere in "The Bugzilla
Guide" in the "Integration with Third-Party Products" section.
- The section on Perforce isn't very large, but as the maintainer
- of the Guide is charged with Perforce/Bugzilla integration by
- his company, you can expect this section to grow.
</P
></DIV
></DIV
@@ -8742,7 +12614,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1487"
+NAME="AEN1887"
></A
><B
>A.4.3. </B
@@ -8768,7 +12640,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1492"
+NAME="AEN1892"
></A
><B
>A.4.4. </B
@@ -8791,7 +12663,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1497"
+NAME="AEN1897"
></A
><B
>A.4.5. </B
@@ -8819,7 +12691,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1502"
+NAME="AEN1902"
></A
><B
>A.4.6. </B
@@ -8837,6 +12709,15 @@ CLASS="ANSWER"
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"
+TARGET="_top"
+>http://bugzilla.mozilla.org/show_bug.cgi?id=91037</A
+>
+ </P
></DIV
></DIV
><DIV
@@ -8845,10 +12726,186 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1507"
+NAME="AEN1909"
></A
><B
>A.4.7. </B
+> The index.html page doesn't show the footer. It's really annoying to have
+ to go to the querypage just to check my "my bugs" link. How do I get a footer
+ on static HTML pages?
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><B
+> </B
+> It's possible to get the footer on the static index page using
+ Server Side Includes (SSI). The trick to doing this is making
+ sure that your web server is set up to allow SSI and specifically,
+ the #exec directive. You should also rename <TT
+CLASS="FILENAME"
+>index.html</TT
+>
+ to <TT
+CLASS="FILENAME"
+>index.shtml</TT
+>.
+ </P
+><P
+> After you've done all that, you can add the following line to
+ <TT
+CLASS="FILENAME"
+>index.shtml</TT
+>:
+<TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+><!--#exec cmd="/usr/bin/perl -e &quot;require 'CGI.pl'; PutFooter();&quot;" --></PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+ </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
+> This line will be replaced with the actual HTML for the footer
+ when the page is requested, so you should put this line where you
+ want the footer to appear.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+></P
+><P
+> Because this method depends on being able to use a #exec directive,
+ and most ISP's will not allow that, there is an alternative method.
+ You could have a small script (such as <TT
+CLASS="FILENAME"
+>api.cgi</TT
+>)
+ that basically looks like:
+<TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>#!/usr/bonsaitools/bin/perl -w
+
+require 'globals.pl';
+
+if ($::FORM{sub} eq 'PutFooter') {
+ PutFooter();
+} else {
+ die 'api.cgi was incorrectly called';
+}</PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+ and then put this line in <TT
+CLASS="FILENAME"
+>index.shtml</TT
+>.
+<TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+><!--#include virtual="api.cgi?sub=PutFooter"--></PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+ </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
+> This still requires being able to use Server Side Includes, if
+ this simply will not work for you, see <A
+HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=80183"
+TARGET="_top"
+>bug 80183</A
+>
+ for a third option.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+></P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1931"
+></A
+><B
+>A.4.8. </B
> Does Bugzilla provide any reporting features, metrics, graphs, etc? You
know, the type of stuff that management likes to see. :)
</P
@@ -8884,10 +12941,10 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1515"
+NAME="AEN1939"
></A
><B
->A.4.8. </B
+>A.4.9. </B
> Is there email notification and if so, what do you see when you get an
email? Do you see bug number and title or is it only the number?
</P
@@ -8909,10 +12966,10 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1520"
+NAME="AEN1944"
></A
><B
->A.4.9. </B
+>A.4.10. </B
> Can email notification be set up to send to multiple
people, some on the To List, CC List, BCC List etc?
</P
@@ -8932,10 +12989,10 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1525"
+NAME="AEN1949"
></A
><B
->A.4.10. </B
+>A.4.11. </B
> If there is email notification, do users have to have any particular
type of email application?
</P
@@ -8949,11 +13006,25 @@ CLASS="ANSWER"
on the planet.
<DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><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
-><B
->Note: </B
> 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
@@ -8961,7 +13032,9 @@ CLASS="NOTE"
Bugzilla ignores HTML tags in comments, and if a user sends HTML-based
email into Bugzilla the resulting comment looks downright awful.
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
>
</P
@@ -8973,10 +13046,10 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1532"
+NAME="AEN1956"
></A
><B
->A.4.11. </B
+>A.4.12. </B
> If I just wanted to track certain bugs, as they go through life, can I
set it up to alert me via email whenever that bug changes, whether it be
owner, status or description etc.?
@@ -9000,10 +13073,10 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1537"
+NAME="AEN1961"
></A
><B
->A.4.12. </B
+>A.4.13. </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
@@ -9045,31 +13118,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1545"
-></A
-><B
->A.4.13. </B
-> Does Bugzilla allow fields to be added, changed or deleted? If I want to
- customize the bug submission form to meet our needs, can I do that using our
- terminology?
- </P
-></DIV
-><DIV
-CLASS="ANSWER"
-><P
-><B
-> </B
-> Yes.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="QANDAENTRY"
-><DIV
-CLASS="QUESTION"
-><P
-><A
-NAME="AEN1550"
+NAME="AEN1969"
></A
><B
>A.4.14. </B
@@ -9095,7 +13144,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1555"
+NAME="AEN1974"
></A
><B
>A.4.15. </B
@@ -9118,7 +13167,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1560"
+NAME="AEN1979"
></A
><B
>A.4.16. </B
@@ -9140,7 +13189,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1565"
+NAME="AEN1984"
></A
><B
>A.4.17. </B
@@ -9163,7 +13212,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1570"
+NAME="AEN1989"
></A
><B
>A.4.18. </B
@@ -9187,7 +13236,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1575"
+NAME="AEN1994"
></A
><B
>A.4.19. </B
@@ -9210,7 +13259,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1580"
+NAME="AEN1999"
></A
><B
>A.4.20. </B
@@ -9235,7 +13284,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1585"
+NAME="AEN2004"
></A
><B
>A.4.21. </B
@@ -9263,7 +13312,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1591"
+NAME="AEN2010"
></A
><B
>A.4.22. </B
@@ -9287,7 +13336,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1596"
+NAME="AEN2015"
></A
><B
>A.4.23. </B
@@ -9326,7 +13375,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1603"
+NAME="AEN2022"
></A
><B
>A.4.24. </B
@@ -9357,7 +13406,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1608"
+NAME="AEN2027"
></A
><B
>A.4.25. </B
@@ -9389,7 +13438,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1615"
+NAME="AEN2034"
></A
><B
>A.5.1. </B
@@ -9406,8 +13455,7 @@ HREF="http://www.mozilla.org/projects/bugzilla/"
TARGET="_top"
> http://www.mozilla.org/projects/bugzilla/</A
> for details.
- Once you download it, untar it, read the README and
- the Bugzilla Guide.
+ Once you download it, untar it, read the Bugzilla Guide.
</P
></DIV
></DIV
@@ -9417,7 +13465,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1621"
+NAME="AEN2040"
></A
><B
>A.5.2. </B
@@ -9440,7 +13488,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1626"
+NAME="AEN2045"
></A
><B
>A.5.3. </B
@@ -9470,12 +13518,12 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1633"
+NAME="AEN2052"
></A
><B
>A.6.1. </B
> How do I completely disable MySQL security if it's giving me problems
- (I've followed the instructions in the README!)?
+ (I've followed the instructions in the installation section of this guide!)?
</P
></DIV
><DIV
@@ -9498,7 +13546,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1639"
+NAME="AEN2058"
></A
><B
>A.6.2. </B
@@ -9513,7 +13561,7 @@ CLASS="ANSWER"
> The Bugzilla code has not undergone a complete security audit.
It is recommended that you closely examine permissions on your Bugzilla
installation, and follow the recommended security guidelines found
- in the README and in The Bugzilla Guide.
+ in The Bugzilla Guide.
</P
></DIV
></DIV
@@ -9523,7 +13571,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1644"
+NAME="AEN2063"
></A
><B
>A.6.3. </B
@@ -9557,7 +13605,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1651"
+NAME="AEN2070"
></A
><B
>A.7.1. </B
@@ -9581,7 +13629,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1656"
+NAME="AEN2075"
></A
><B
>A.7.2. </B
@@ -9605,7 +13653,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1661"
+NAME="AEN2080"
></A
><B
>A.7.3. </B
@@ -9635,7 +13683,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1667"
+NAME="AEN2086"
></A
><B
>A.7.4. </B
@@ -9651,7 +13699,7 @@ CLASS="ANSWER"
> You can call bug_email.pl directly from your aliases file, with
an entry like this:
<A
-NAME="AEN1671"
+NAME="AEN2090"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
@@ -9672,7 +13720,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1674"
+NAME="AEN2093"
></A
><B
>A.7.5. </B
@@ -9695,7 +13743,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1679"
+NAME="AEN2098"
></A
><B
>A.7.6. </B
@@ -9710,20 +13758,14 @@ CLASS="ANSWER"
> </B
> If you are using an alternate Mail Transport Agent (MTA other than
sendmail), make sure the options given in the "processmail" script for all
- instances of "sendmail" are correct for your MTA. If you are using Sendmail,
- you may wish to delete the "-ODeliveryMode=deferred" option in the
- "processmail" script for every invocation of "sendmail". (Be sure and leave
- the "-t" option, though!)
- </P
-><P
-> A better alternative is to change the "-O" option to
- "-ODeliveryMode=background". This prevents Sendmail from hanging your
- Bugzilla Perl processes if the domain to which it must send mail
- is unavailable.
+ instances of "sendmail" are correct for your MTA.
</P
><P
-> This is now a configurable parameter called "sendmailnow", available
- from editparams.cgi.
+> 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
@@ -9733,7 +13775,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1686"
+NAME="AEN2105"
></A
><B
>A.7.7. </B
@@ -9771,7 +13813,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1694"
+NAME="AEN2113"
></A
><B
>A.8.1. </B
@@ -9796,7 +13838,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1699"
+NAME="AEN2118"
></A
><B
>A.8.2. </B
@@ -9831,7 +13873,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1704"
+NAME="AEN2123"
></A
><B
>A.8.3. </B
@@ -9844,12 +13886,29 @@ CLASS="ANSWER"
><P
><B
> </B
-> Run the "sanity check" utility (./sanitycheck.cgi in the bugzilla_home
- directory) to see! If it all comes back, you're 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...
+> 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
@@ -9859,7 +13918,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1709"
+NAME="AEN2131"
></A
><B
>A.8.4. </B
@@ -9886,7 +13945,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1714"
+NAME="AEN2136"
></A
><B
>A.8.5. </B
@@ -9910,7 +13969,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1719"
+NAME="AEN2141"
></A
><B
>A.8.6. </B
@@ -9937,7 +13996,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1724"
+NAME="AEN2146"
></A
><B
>A.8.7. </B
@@ -9973,7 +14032,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1731"
+NAME="AEN2153"
></A
><B
>A.8.8. </B
@@ -9999,7 +14058,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1736"
+NAME="AEN2158"
></A
><B
>A.8.9. </B
@@ -10011,10 +14070,21 @@ CLASS="ANSWER"
><P
><B
> </B
-> Delete everything from $BUZILLA_HOME/shadow. Bugzilla creates shadow
- files there, with each filename corresponding to a
- bug number. Also be sure to run syncshadowdb to make sure, if you are using
- a shadow database, that the shadow database is current.
+> This should only happen with Bugzilla 2.14 if you are
+ using the <SPAN
+CLASS="QUOTE"
+>"shadow database"</SPAN
+> feature, and your
+ shadow database is out of sync. Try running
+ <TT
+CLASS="FILENAME"
+>syncshadowdb</TT
+>
+ <TT
+CLASS="OPTION"
+>-syncall</TT
+> to make sure your shadow
+ database is in synch with your primary database.
</P
></DIV
></DIV
@@ -10032,7 +14102,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1743"
+NAME="AEN2168"
></A
><B
>A.9.1. </B
@@ -10055,7 +14125,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1748"
+NAME="AEN2173"
></A
><B
>A.9.2. </B
@@ -10079,7 +14149,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1753"
+NAME="AEN2178"
></A
><B
>A.9.3. </B
@@ -10100,7 +14170,7 @@ CLASS="ANSWER"
><P
> Microsoft has some advice on this matter, as well:
<A
-NAME="AEN1758"
+NAME="AEN2183"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
@@ -10125,7 +14195,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1761"
+NAME="AEN2186"
></A
><B
>A.9.4. </B
@@ -10236,7 +14306,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1767"
+NAME="AEN2192"
></A
><B
>A.9.5. </B
@@ -10311,7 +14381,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1788"
+NAME="AEN2213"
></A
><B
>A.10.1. </B
@@ -10339,7 +14409,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1794"
+NAME="AEN2219"
></A
><B
>A.10.2. </B
@@ -10392,7 +14462,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1804"
+NAME="AEN2229"
></A
><B
>A.10.3. </B
@@ -10417,7 +14487,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1809"
+NAME="AEN2234"
></A
><B
>A.10.4. </B
@@ -10442,7 +14512,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1814"
+NAME="AEN2239"
></A
><B
>A.10.5. </B
@@ -10474,7 +14544,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1821"
+NAME="AEN2246"
></A
><B
>A.11.1. </B
@@ -10487,20 +14557,20 @@ CLASS="ANSWER"
><B
> </B
> Try <A
-HREF="http://bugzilla.mozilla.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Webtools&component=Bugzilla"
+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.14 release
+> You can view bugs marked for 2.16 release
<A
-HREF="http://bugzilla.mozilla.org/buglist.cgi?product=Webtools&component=Bugzilla&target_milestone=Bugzilla+2.14"
+HREF="http://bugzilla.mozilla.org/buglist.cgi?product=Bugzilla&target_milestone=Bugzilla+2.16"
TARGET="_top"
>here</A
>.
- This list includes bugs for the 2.14 release that have already
+ This list includes bugs for the 2.16 release that have already
been fixed and checked into CVS. Please consult the
<A
HREF="http://www.mozilla.org/projects/bugzilla/"
@@ -10518,7 +14588,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1830"
+NAME="AEN2255"
></A
><B
>A.11.2. </B
@@ -10550,7 +14620,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1836"
+NAME="AEN2261"
></A
><B
>A.11.3. </B
@@ -10568,8 +14638,15 @@ CLASS="ANSWER"
TYPE="1"
><LI
><P
-> Enter a bug into bugzilla.mozilla.org for the "Webtools" product,
- "Bugzilla" component.
+> 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
@@ -10643,9 +14720,9 @@ TARGET="_top"
</P
><P
> MySQL: <A
-HREF="http://www.mysql.org/"
+HREF="http://www.mysql.com/"
TARGET="_top"
->http://www.mysql.org/</A
+>http://www.mysql.com/</A
>
</P
><P
@@ -10735,244 +14812,323 @@ NAME="DATABASE"
></H1
><DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><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
-><B
->Note: </B
->This document really needs to be updated with more fleshed out information about primary keys, interrelationships, and maybe some nifty tables to document dependencies. Any takers?</P
-></BLOCKQUOTE
+> 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
+><DIV
+CLASS="SECTION"
+><HR><H1
+CLASS="SECTION"
+><A
+NAME="DBSCHEMA"
+>C.1. Database Schema Chart</A
+></H1
+><P
+> <DIV
+CLASS="MEDIAOBJECT"
+><P
+><IMG
+SRC="../images/dbschema.jpg"
+ALT="Database Relationships"
+></IMG
+><DIV
+CLASS="CAPTION"
+><P
+>Bugzilla database relationships chart</P
+></DIV
+></P
+></DIV
+>
+ </P
></DIV
><DIV
CLASS="SECTION"
-><HR><H1
+><HR><H1
+CLASS="SECTION"
+><A
+NAME="DBDOC"
+>C.2. MySQL Bugzilla Database Introduction</A
+></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="DBSCHEMA"
->C.1. Database Schema Chart</A
-></H1
+NAME="AEN2331"
+>C.2.1. Bugzilla Database Basics</A
+></H2
><P
-> <DIV
-CLASS="MEDIAOBJECT"
+> 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"
+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
-><IMG
-SRC="dbschema.jpg"
-ALT="Database Relationships"
-></IMG
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+> To connect to your database:
+ </P
+><P
+> <TT
+CLASS="PROMPT"
+>bash#</TT
+><B
+CLASS="COMMAND"
+>mysql</B
+><TT
+CLASS="PARAMETER"
+><I
+>-u root</I
+></TT
+>
+ </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 MySQL searchable documentation at
+ http://www.mysql.com/php/manual.php3?section=Privilege_system .
+ </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
+> file
+ for your Bugzilla database, type:</P
+><P
+><TT
+CLASS="PROMPT"
+>mysql</TT
+><B
+CLASS="COMMAND"
+>use bugs;</B
+></P
><DIV
-CLASS="CAPTION"
+CLASS="NOTE"
><P
->Bugzilla database relationships chart</P
-></DIV
></P
+><TABLE
+CLASS="NOTE"
+WIDTH="90%"
+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
+>Don't forget the <SPAN
+CLASS="QUOTE"
+>";"</SPAN
+> at the end of
+ each line, or you'll be kicking yourself later.</P
+></TD
+></TR
+></TABLE
></DIV
+></LI
+></OL
>
- </P
-></DIV
+ </P
><DIV
CLASS="SECTION"
-><HR><H1
+><HR><H3
CLASS="SECTION"
><A
-NAME="DBDOC"
->C.2. MySQL Bugzilla Database Introduction</A
-></H1
+NAME="AEN2360"
+>C.2.1.1. Bugzilla Database Tables</A
+></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
+><B
+CLASS="COMMAND"
+>show tables from bugs;</B
+></P
+><P
+>you'll be able to see all the
+ <SPAN
+CLASS="QUOTE"
+>"spreadsheets"</SPAN
+> (tables) in your database. It
+ is similar to a file system, only faster and more robust for
+ certain types of operations.</P
+><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
><P
CLASS="LITERALLAYOUT"
><br>
-Contributor(s): Matthew P. Barnson (mbarnson@excitehome.net)<br>
-<br>
-Last update: May 16, 2000<br>
-<br>
-Changes:<br>
-Version 1.0: Initial public release (May 16, 2000)<br>
-<br>
-Maintainer: Matthew P. Barnson (mbarnson@excitehome.net)<br>
-<br>
-<br>
-===<br>
-Table Of Contents<br>
-===<br>
-<br>
-FOREWORD<br>
-INTRODUCTION<br>
-THE BASICS<br>
-THE TABLES<br>
-THE DETAILS<br>
-<br>
-<br>
-<br>
-===<br>
-FOREWORD<br>
-===<br>
-<br>
- This information comes straight from my life. I was forced to learn how<br>
-Bugzilla organizes database because of nitpicky requests from users for tiny<br>
-changes in wording, rather than having people re-educate themselves or<br>
-figure out how to work our procedures around the tool. It sucks, but it can<br>
-and will happen to you, so learn how the schema works and deal with it when it<br>
-comes.<br>
-<br>
- I'm sorry this version is plain text. I can whip this info out a lot faster<br>
-if I'm not concerned about complex formatting. I'll get it into sgml for easy<br>
-portability as time permits.<br>
-<br>
- The Bugzilla Database Schema has a home! In addition to availability via CVS<br>
-and released versions 2.12 and higher of Bugzilla, you can find the latest &<br>
-greatest version of the Bugzilla Database Schema at<br>
-http://www.trilobyte.net/barnsons/. This is a living document; please be sure<br>
-you are up-to-date with the latest version before mirroring.<br>
-<br>
- The Bugzilla Database Schema is designed to provide vital information<br>
-regarding the structure of the MySQL database. Where appropriate, this<br>
-document will refer to URLs rather than including documents in their entirety<br>
-to ensure completeness even should this paper become out of date.<br>
-<br>
- This document is not maintained by Netscape or Netscape employees, so please<br>
-do not contact them regarding errors or omissions contained herein. Please<br>
-direct all questions, comments, updates, flames, etc. to Matthew P. Barnson<br>
-mbarnson@excitehome.net) (barnboy or barnhome on irc.mozilla.org in<br>
-#mozwebtools).<br>
-<br>
- I'm sure I've made some glaring errors or omissions in this paper -- please<br>
-email me corrections or post corrections to the<br>
-netscape.public.mozilla.webtools newsgroup.<br>
-<br>
-<br>
-<br>
-===<br>
-INTRODUCTION<br>
-===<br>
-<br>
-<br>
-<br>
- So, here you are with your brand-new installation of Bugzilla. You've got<br>
-MySQL set up, Apache working right, Perl DBI and DBD talking to the database<br>
-flawlessly. Maybe you've even entered a few test bugs to make sure email's<br>
-working; people seem to be notified of new bugs and changes, and you can<br>
-enter and edit bugs to your heart's content. Perhaps you've gone through the<br>
-trouble of setting up a gateway for people to submit bugs to your database via<br>
-email, have had a few people test it, and received rave reviews from your beta<br>
-testers.<br>
-<br>
- What's the next thing you do? Outline a training strategy for your<br>
-development team, of course, and bring them up to speed on the new tool you've<br>
-labored over for hours.<br>
-<br>
- Your first training session starts off very well! You have a captive<br>
-audience which seems enraptured by the efficiency embodied in this thing called<br>
-"Bugzilla". You are caught up describing the nifty features, how people can<br>
-save favorite queries in the database, set them up as headers and footers on<br>
-their pages, customize their layouts, generate reports, track status with<br>
-greater efficiency than ever before, leap tall buildings with a single bound<br>
-and rescue Jane from the clutches of Certain Death!<br>
-<br>
- But Certain Death speaks up -- a tiny voice, from the dark corners of the<br>
-conference room. "I have a concern," the voice hisses from the darkness,<br>
-"about the use of the word 'verified'.<br>
-<br>
- The room, previously filled with happy chatter, lapses into reverential<br>
-silence as Certain Death (better known as the Vice President of Software<br>
-Engineering) continues. "You see, for two years we've used the word 'verified'<br>
-to indicate that a developer or quality assurance engineer has confirmed that,<br>
-in fact, a bug is valid. I don't want to lose two years of training to a<br>
-new software product. You need to change the bug status of 'verified' to<br>
-'approved' as soon as possible. To avoid confusion, of course."<br>
-<br>
- Oh no! Terror strikes your heart, as you find yourself mumbling "yes, yes, I<br>
-don't think that would be a problem," You review the changes with Certain<br>
-Death, and continue to jabber on, "no, it's not too big a change. I mean, we<br>
-have the source code, right? You know, 'Use the Source, Luke' and all that...<br>
-no problem," All the while you quiver inside like a beached jellyfish bubbling,<br>
-burbling, and boiling on a hot Jamaican sand dune...<br>
-<br>
- Thus begins your adventure into the heart of Bugzilla. You've been forced<br>
-to learn about non-portable enum() fields, varchar columns, and tinyint<br>
-definitions. The Adventure Awaits You!<br>
-<br>
-<br>
-<br>
-===<br>
-The Basics<br>
-===<br>
-<br>
- If you were like me, at this point you're totally clueless about the<br>
-internals of MySQL, and if it weren't for this executive order from the Vice<br>
-President you couldn't care less about the difference between a "bigint" and a<br>
-"tinyint" entry in MySQL. I'd refer you first to the MySQL documentation,<br>
-available at http://www.mysql.com/doc.html, but that's mostly a confusing<br>
-morass of high-level database jargon. Here are the basics you need to know<br>
-about the database to proceed:<br>
-<br>
-1. To connect to your database, type "mysql -u root" at the command prompt as<br>
-any user. If this works without asking you for a password, SHAME ON YOU! You<br>
-should have locked your security down like the README told you to. You can<br>
-find details on locking down your database in the Bugzilla FAQ in this<br>
-directory (under "Security"), or more robust security generalities in the<br>
-MySQL searchable documentation at<br>
-http://www.mysql.com/php/manual.php3?section=Privilege_system .<br>
-<br>
-2. You should now be at a prompt that looks like this:<br>
-<br>
-mysql><br>
- <br>
- At the prompt, if "bugs" is the name of your Bugzilla database, type:<br>
- <br>
-mysql> use bugs;<br>
- <br>
- (don't forget the ";" at the end of each line, or you'll be kicking yourself<br>
-all the way through this documentation)<br>
- Young Grasshopper, you are now ready for the unveiling of the Bugzilla<br>
-database, in the next section...<br>
-<br>
-<br>
-<br>
-===<br>
-THE TABLES<br>
-===<br>
-<br>
- Imagine your MySQL database as a series of spreadsheets, and you won't be too<br>
-far off. If you use this command:<br>
-<br>
-mysql> show tables from bugs;<br>
- <br>
- you'll be able to see all the "spreadsheets" (tables) in your database. Cool,<br>
-huh? It's kinda' like a filesystem, only much faster and more robust. Come<br>
-on, I'll show you more!<br>
-<br>
- From the command issued above, you should now have some output that looks<br>
-like this:<br>
-<br>
-+-------------------+<br>
-| Tables in bugs |<br>
-+-------------------+<br>
-| attachments |<br>
-| bugs |<br>
-| bugs_activity |<br>
-| cc |<br>
-| components |<br>
-| dependencies |<br>
-| fielddefs |<br>
-| groups |<br>
-| keyworddefs |<br>
-| keywords |<br>
-| logincookies |<br>
-| longdescs |<br>
-| milestones |<br>
-| namedqueries |<br>
-| products |<br>
-| profiles |<br>
-| profiles_activity |<br>
-| shadowlog |<br>
-| versions |<br>
-| votes |<br>
-| watch |<br>
-+-------------------+<br>
-<br>
-<br>
- If it doesn't look quite the same, that probably means it's time to<br>
-update this documentation :)<br>
-<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>
@@ -11149,7 +15305,9 @@ LINKS<br>
Great MySQL tutorial site:<br>
http://www.devshed.com/Server_Side/MySQL/<br>
<br>
- </P
+ </P
+></DIV
+></DIV
></DIV
><DIV
CLASS="SECTION"
@@ -11161,19 +15319,46 @@ NAME="GRANTTABLES"
></H1
><DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><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
-><B
->Note: </B
->The following portion of documentation comes from my answer to an old discussion of Keystone,
- a cool product that does trouble-ticket tracking for IT departments. I wrote this post to the
- Keystone support group regarding MySQL grant table permissions, and how to use them effectively.
- It is badly in need of updating, as I believe MySQL has added a field or two to the grant tables
- since this time, but it serves as a decent introduction and troubleshooting document for grant
- table issues. I used Keynote to track my troubles until I discovered Bugzilla,
- which gave me a whole new set of troubles to work on : )</P
-></BLOCKQUOTE
+>The following portion of documentation comes from my
+ answer to an old discussion of Keystone, a cool product that
+ does trouble-ticket tracking for IT departments. I wrote this
+ post to the Keystone support group regarding MySQL grant
+ table permissions, and how to use them effectively. It is
+ badly in need of updating, as I believe MySQL has added a
+ field or two to the grant tables since this time, but it
+ serves as a decent introduction and troubleshooting document
+ for grant table issues. I used Keynote to track my troubles
+ until I discovered Bugzilla, which gave me a whole new set of
+ troubles to work on : ) Although it is of limited use, it
+ still has SOME use, thus it's still included.</P
+><P
+> Please note, however, that I was a relatively new user to
+ MySQL at the time. Some of my suggestions, particularly in
+ how to set up security, showed a terrible lack of
+ security-related database experience.
+ </P
+></TD
+></TR
+></TABLE
></DIV
><P
CLASS="LITERALLAYOUT"
@@ -11339,163 +15524,95 @@ Once again, you can't go wrong by reading&nbs
is more detailed than I!<br>
http://www.mysql.com/Manual/manual.html.<br>
<br>
-----------------------------------------------------------------------------<br>
-10/12/2000<br>
-Matthew sent in some mail with updated contact information:<br>
-NEW CONTACT INFORMATION: <br>
-<br>
- ------------------------ <br>
- Matthew P. Barnson <br>
- Manager, Systems Administration <br>
- Excite@Home Business Applications <br>
- mbarnson@excitehome.net <br>
- (801)234-8300 <br>
-<br>
-<br>
- </P
-></DIV
-><DIV
-CLASS="SECTION"
-><HR><H1
-CLASS="SECTION"
-><A
-NAME="CLEANUPWORK"
->C.4. Cleaning up after mucking with Bugzilla</A
-></H1
-><P
-CLASS="LITERALLAYOUT"
->Contributed by Eric Hanson:<br>
-There are several things, and one trick. There is a small tiny piece of<br>
-documentation I saw once that said something very important.<br>
-1) After pretty much any manual working of the Mysql db, you must<br>
-delete a file in the bugzilla directory: data/versioncache<br>
-Versioncache basically is a way to speed up bugzilla (from what I<br>
-understand). It stores a lot of commonly used information. However,<br>
-this file is refreshed every so often (I can't remember the time<br>
-interval though). So eventually all changes do propogate out, so you<br>
-may see stuff suddenly working.<br>
-2) Assuming that failed, you will also have to check something with the<br>
-checksetup.pl file. It actually is run twice. The first time it<br>
-creates the file: localconfig. You can modify localconfig, (or not if<br>
-you are doing bug_status stuff) or you should delete localconfig and<br>
-rerun your modified checksetup.pl. Since I don't actually see anything<br>
-in localconfig pertaining to bug_status, this point is mainly a FYI.<br>
</P
></DIV
></DIV
><DIV
-CLASS="CHAPTER"
+CLASS="APPENDIX"
><HR><H1
><A
-NAME="VARIANTS"
->Chapter 7. Bugzilla Variants</A
+NAME="PATCHES"
+>Appendix D. Useful Patches and Utilities for Bugzilla</A
></H1
-><DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
><P
-><B
->Note: </B
-> I <EM
->know</EM
-> there are more variants than just RedHat Bugzilla out there.
- Please help me get information about them, their project status, and benefits there
- might be in using them or in using their code in main-tree Bugzilla.
- </P
-></BLOCKQUOTE
-></DIV
+>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="SECTION"
><HR><H1
CLASS="SECTION"
><A
-NAME="RHBUGZILLA"
->7.1. Red Hat Bugzilla</A
+NAME="REWRITE"
+>D.1. Apache <TT
+CLASS="FILENAME"
+>mod_rewrite</TT
+> magic</A
></H1
><P
-> Red Hat Bugzilla is probably the most popular Bugzilla variant, aside from Mozilla Bugzilla,
- on the planet.
- One of the major benefits of Red Hat Bugzilla is the ability to work with Oracle as a
- database, as well as MySQL.
- Here's what Dave Lawrence had to say about the status of Red Hat Bugzilla,
- <A
-NAME="AEN1913"
-></A
-><BLOCKQUOTE
-CLASS="BLOCKQUOTE"
+>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
-CLASS="LITERALLAYOUT"
-> Hello. I apologize that I am getting back to you so late. It has been difficult to keep<br>
-up with email this past week. I have checked out your updated documentation and I will<br>
-have to say very good work. A few notes and additions as follows.<br>
-<br>
-(ed: from the FAQ)<br>
->For the record, we are not using any template type implementation for the cosmetic changes <br>
->maded to Bugzilla. It is just alot of html changes in the code itself. I admit I may have <br>
->gotten a little carried away with it but the corporate types asked for a more standardized <br>
->interface to match up with other projects relating to Red Hat web sites. A lot of other web <br>
->based internal tools I am working on also look like Bugzilla. <br>
-<br>
-<br>
-This should probably be changed since we are now in fact using Text::Template for most<br>
-of the html rendering. You actually state this later in your numbered list.<br>
-<br>
-Also number 6 contradicts number 8 where number 6 would be the most up to date status<br>
-on the Oracle port.<br>
-<br>
-Additional Information:<br>
------------------------------<br>
-1. Comments are now stored in varchar fields of 4k in size each. If the comment is more<br>
-than 4k it is broken up into chunks and given a sort number so each comment can be re<br>
-assembled in the correct order. This was done because originally I was storing the comments<br>
-in a long datatype which unfortunately cannot be indexed or joined with another table. This<br>
-cause the search of text within the long description to be disabled for a long time. That<br>
-is now working and is nto showing any noticeble performance hit that I can tell. <br>
-<br>
-2. Work is being started on internationalizing the Bugzilla source we have to allow our<br>
-Japanese customers to enter bug reports into a single bugzilla system. This will probably<br>
-be done by using the nvarchar data types supported by Oracle which allows storage of<br>
-double byte characters and also the use of the Accept-Language in the http header for <br>
-detection by Bugilla of which language to render.<br>
-<br>
-3. Of course even more cosmetic changes. It is difficult to keep up with the ever <br>
-changing faces of www.redhat.com.<br>
-<br>
-4. Some convenience enhancements in the administration utilities. And more integration<br>
-with other internal/external Red Hat web sites.<br>
-<br>
-I hope this information may prove helpful for your documentation. Please contact<br>
-me if you have any more question or I can do anything else.<br>
-<br>
-Regards<br>
- </P
-></BLOCKQUOTE
->
- </P
-></DIV
-></DIV
-><DIV
-CLASS="APPENDIX"
-><HR><H1
-><A
-NAME="PATCHES"
->Appendix D. Useful Patches and Utilities for Bugzilla</A
-></H1
+></P
+><OL
+TYPE="1"
+><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="90%"
+><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
+>There are many, many more things you can do with
+ mod_rewrite. As time goes on, I will include many more in
+ the Guide. For now, though, please refer to the mod_rewrite
+ documentation at <A
+HREF="http://www.apache.org"
+TARGET="_top"
+>http://www.apache.org</A
+></P
+></LI
+></OL
+></DIV
><DIV
CLASS="SECTION"
-><H1
+><HR><H1
CLASS="SECTION"
><A
NAME="SETPERL"
->D.1. The setperl.csh Utility</A
+>D.2. The setperl.csh Utility</A
></H1
><P
->
- You can use the "setperl.csh" utility to quickly and easily
- change the path to perl on all your Bugzilla files.
- This is a C-shell script; if you do not have "csh" or "tcsh" in the search
- path on your system, it will not work!
+> You can use the "setperl.csh" utility to quickly and
+ easily change the path to perl on all your Bugzilla files. This
+ is a C-shell script; if you do not have "csh" or "tcsh" in the
+ search path on your system, it will not work!
</P
><DIV
CLASS="PROCEDURE"
@@ -11529,15 +15646,15 @@ CLASS="COMMAND"
><P
> <TT
CLASS="COMPUTEROUTPUT"
-> <TT
+> <TT
CLASS="PROMPT"
>bash#</TT
->
- <B
+> <B
CLASS="COMMAND"
->wget -O setperl.csh 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'</B
->
- </TT
+>wget -O
+ setperl.csh
+ 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'</B
+> </TT
>
</P
></LI
@@ -11545,15 +15662,14 @@ CLASS="COMMAND"
><P
> <TT
CLASS="COMPUTEROUTPUT"
-> <TT
+> <TT
CLASS="PROMPT"
>bash#</TT
->
- <B
+> <B
CLASS="COMMAND"
->chmod u+x setperl.csh</B
->
- </TT
+>chmod
+ u+x setperl.csh</B
+> </TT
>
</P
></LI
@@ -11586,15 +15702,14 @@ CLASS="COMMAND"
><P
> <TT
CLASS="COMPUTEROUTPUT"
-> <TT
+> <TT
CLASS="PROMPT"
>bash#</TT
->
- <B
+> <B
CLASS="COMMAND"
->chmod u+x duplicates.cgi</B
->
- </TT
+>chmod
+ u+x duplicates.cgi</B
+> </TT
>
</P
></LI
@@ -11623,7 +15738,7 @@ CLASS="COMMAND"
><P
> <TT
CLASS="COMPUTEROUTPUT"
-> <TT
+> <TT
CLASS="PROMPT"
>bash#</TT
>
@@ -11636,7 +15751,7 @@ CLASS="COMMAND"
<DIV
CLASS="EXAMPLE"
><A
-NAME="AEN1963"
+NAME="AEN2439"
></A
><P
><B
@@ -11645,11 +15760,11 @@ NAME="AEN1963"
><P
> <TT
CLASS="COMPUTEROUTPUT"
-> <TT
+> <TT
CLASS="PROMPT"
>bash#</TT
>
- <B
+ <B
CLASS="COMMAND"
>./setperl.csh /usr/bin/perl</B
>
@@ -11669,25 +15784,26 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="CMDLINE"
->D.2. Command-line Bugzilla Queries</A
+>D.3. Command-line Bugzilla Queries</A
></H1
><P
-> Users can query Bugzilla from the command line using
- this suite of utilities.
+> Users can query Bugzilla from the command line using this suite
+ of utilities.
</P
><P
> The query.conf file 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"
+ 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
-> 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=".
+> 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=".
</P
><P
> The columlist is taken from the COLUMNLIST environment variable.
@@ -11702,12 +15818,12 @@ CLASS="COMMAND"
><P
> 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
- <B
+ "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
+>sed -e 's/,/ /g' | wc |
+ awk '{printf $2 "\n"}'</B
>
</P
><P
@@ -11732,15 +15848,15 @@ TYPE="a"
><P
> <TT
CLASS="COMPUTEROUTPUT"
-> <TT
+> <TT
CLASS="PROMPT"
>bash$</TT
->
- <B
+> <B
CLASS="COMMAND"
->wget -O query.conf 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26157'</B
->
- </TT
+>wget -O
+ query.conf
+ 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26157'</B
+> </TT
>
</P
></LI
@@ -11748,15 +15864,15 @@ CLASS="COMMAND"
><P
> <TT
CLASS="COMPUTEROUTPUT"
-> <TT
+> <TT
CLASS="PROMPT"
>bash$</TT
->
- <B
+> <B
CLASS="COMMAND"
->wget -O buglist 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26944'</B
->
- </TT
+>wget -O
+ buglist
+ 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26944'</B
+> </TT
>
</P
></LI
@@ -11764,15 +15880,15 @@ CLASS="COMMAND"
><P
> <TT
CLASS="COMPUTEROUTPUT"
-> <TT
+> <TT
CLASS="PROMPT"
>bash#</TT
->
- <B
+> <B
CLASS="COMMAND"
->wget -O bugs 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26215'</B
->
- </TT
+>wget -O
+ bugs
+ 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26215'</B
+> </TT
>
</P
></LI
@@ -11804,26 +15920,30 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="QUICKSEARCH"
->D.3. The Quicksearch Utility</A
+>D.4. The Quicksearch Utility</A
></H1
><P
> Quicksearch is a new, experimental feature of the 2.12 release.
- It consist of two Javascript files, "quicksearch.js" and "localconfig.js",
- and two documentation files, "quicksearch.html" and "quicksearchhack.html"
+ It consist of two Javascript files, "quicksearch.js" and
+ "localconfig.js", and two documentation files,
+ "quicksearch.html" and "quicksearchhack.html"
</P
><P
-> The index.html page has been updated to include the QuickSearch text box.
+> The index.html page has been updated to include the QuickSearch
+ text box.
</P
><P
-> To take full advantage of the query power, the Bugzilla maintainer must
- edit "localconfig.js" according to the value sets used in the local installation.
+> To take full advantage of the query power, the Bugzilla
+ maintainer must edit "localconfig.js" according to the value
+ sets used in the local installation.
</P
><P
-> Currently, keywords must be hard-coded in localconfig.js. If they are not,
- keywords are not automatically recognized. This means, if localconfig.js
- is left unconfigured, that searching for a bug with the "foo" keyword
- will only find bugs with "foo" in the summary, status whiteboard, product or
- component name, but not those with the keyword "foo".
+> Currently, keywords must be hard-coded in localconfig.js. If
+ they are not, keywords are not automatically recognized. This
+ means, if localconfig.js is left unconfigured, that searching
+ for a bug with the "foo" keyword will only find bugs with "foo"
+ in the summary, status whiteboard, product or component name,
+ but not those with the keyword "foo".
</P
><P
> Workarounds for Bugzilla users:
@@ -11834,11 +15954,13 @@ BORDER="0"
><TBODY
><TR
><TD
->search for '!foo' (this will find only bugs with the keyword "foo"</TD
+>search for '!foo' (this will find only bugs with the
+ keyword "foo"</TD
></TR
><TR
><TD
->search 'foo,!foo' (equivalent to 'foo OR keyword:foo')</TD
+>search 'foo,!foo' (equivalent to 'foo OR
+ keyword:foo')</TD
></TR
></TBODY
></TABLE
@@ -11847,15 +15969,118 @@ BORDER="0"
>
</P
><P
-> When this tool is ported from client-side JavaScript to server-side Perl,
- the requirement for hard-coding keywords can be fixed.
- <A
+> When this tool is ported from client-side JavaScript to
+ server-side Perl, the requirement for hard-coding keywords can
+ be fixed. <A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=70907"
TARGET="_top"
>This bug</A
->
- has details.
+> has details.
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H1
+CLASS="SECTION"
+><A
+NAME="BZHACKING"
+>D.5. Hacking Bugzilla</A
+></H1
+><P
+> What follows are some general guidelines for changing Bugzilla, and adhering to good coding practice while doing so. We've had some checkins in the past which ruined Bugzilla installations because of disregard for these conventions. Sorry for the lack of formatting; I got this info into the Guide on the day of 2.14 release and haven't formatted it yet.
</P
+><P
+CLASS="LITERALLAYOUT"
+><br>
+The following is a guide for reviewers when checking code into Bugzilla's<br>
+CVS repostory at mozilla.org. If you wish to submit patches to Bugzilla,<br>
+you should follow the rules and style conventions below. Any code that<br>
+does not adhere to these basic rules will not be added to Bugzilla's<br>
+codebase.<br>
+<br>
+ 1. Usage of variables in Regular Expressions<br>
+<br>
+ It is very important that you don't use a variable in a regular<br>
+ expression unless that variable is supposed to contain an expression.<br>
+ This especially applies when using grep. You should use:<br>
+<br>
+ grep ($_ eq $value, @array);<br>
+<br>
+ - NOT -<br>
+<br>
+ grep (/$value/, @array);<br>
+<br>
+ If you need to use a non-expression variable inside of an expression, be<br>
+ sure to quote it properly (using \Q..\E).<br>
+<br>
+Coding Style for Bugzilla<br>
+-------------------------<br>
+<br>
+While it's true that not all of the code currently in Bugzilla adheres to<br>
+this styleguide, it is something that is being worked toward. Therefore,<br>
+we ask that all new code (submitted patches and new files) follow this guide<br>
+as closely as possible (if you're only changing 1 or 2 lines, you don't have<br>
+to reformat the entire file :).<br>
+<br>
+ 1. Whitespace<br>
+<br>
+ Bugzilla's prefered indentation is 4 spaces (no tabs, please).<br>
+<br>
+ 2. Curly braces.<br>
+<br>
+ The opening brace of a block should be on the same line as the statement<br>
+ that is causing the block and the closing brace should be at the same<br>
+ indentation level as that statement, for example:<br>
+<br>
+ if ($var) {<br>
+ print "The variable is true";<br>
+ } else {<br>
+ print "Try again";<br>
+ }<br>
+<br>
+ - NOT -<br>
+<br>
+ if ($var)<br>
+ {<br>
+ print "The variable is true";<br>
+ }<br>
+ else<br>
+ {<br>
+ print "Try again";<br>
+ }<br>
+<br>
+ 3. File Names<br>
+<br>
+ File names for bugzilla code and support documention should be legal across<br>
+ multiple platforms. \ / : * ? " < > and | are all illegal characters for<br>
+ filenames on various platforms. Also, file names should not have spaces in<br>
+ them as they can cause confusion in CVS and other mozilla.org utilities.<br>
+<br>
+ 4. Variable Names<br>
+<br>
+ If a variable is scoped globally ($::variable) its name should be descriptive<br>
+ of what it contains. Local variables can be named a bit looser, provided the<br>
+ context makes their content obvious. For example, $ret could be used as a<br>
+ staging variable for a routine's return value as the line |return $ret;| will<br>
+ make it blatently obvious what the variable holds and most likely be shown<br>
+ on the same screen as |my $ret = "";|.<br>
+<br>
+ 5. Cross Database Compatability<br>
+<br>
+ Bugzilla was originally written to work with MySQL and therefore took advantage<br>
+ of some of its features that aren't contained in other RDBMS software. These<br>
+ should be avoided in all new code. Examples of these features are enums and<br>
+ encrypt().<br>
+<br>
+ 6. Cross Platform Compatability<br>
+<br>
+ While Bugzilla was written to be used on Unix based systems (and Unix/Linux is<br>
+ still the only officially supported platform) there are many who desire/need to<br>
+ run Bugzilla on Microsoft Windows boxes. Whenever possible, we should strive<br>
+ not to make the lives of these people any more complicated and avoid doing things<br>
+ that break Bugzilla's ability to run on multiple operating systems.<br>
+<br>
+ </P
></DIV
></DIV
><DIV
@@ -11868,7 +16093,7 @@ NAME="GFDL"
><P
>Version 1.1, March 2000</P
><A
-NAME="AEN2019"
+NAME="AEN2499"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
@@ -12367,7 +16592,7 @@ NAME="GFDL_HOWTO"
a copy of the License in the document and put the following
copyright and license notices just after the title page:</P
><A
-NAME="AEN2109"
+NAME="AEN2589"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
@@ -12406,17 +16631,69 @@ CLASS="GLOSSDIV"
><H1
CLASS="GLOSSDIV"
><A
+NAME="AEN2594"
+>0-9, high ascii</A
+></H1
+><DL
+><DT
+><B
+>.htaccess</B
+></DT
+><DD
+><P
+> Apache web server, and other NCSA-compliant web servers,
+ observe the convention of using files in directories
+ called <TT
+CLASS="FILENAME"
+>.htaccess</TT
+> files. These
+ restrict parameters of the web server. In Bugzilla, they
+ are used to restrict access to certain files which would
+ otherwise compromise your installation. For instance, the
+ <TT
+CLASS="FILENAME"
+>localconfig</TT
+> file contains the
+ password to your database. If this information were
+ generally available, and remote access to your database
+ turned on, you risk corruption of your database by
+ computer criminals or the curious.
+ </P
+></DD
+></DL
+></DIV
+><DIV
+CLASS="GLOSSDIV"
+><H1
+CLASS="GLOSSDIV"
+><A
NAME="GLOSS_A"
>A</A
></H1
><DL
><DT
><B
->There are no entries for A</B
+>Apache</B
></DT
><DD
><P
-></P
+>In this context, Apache is the web server most
+ commonly used for serving up
+ <I
+CLASS="GLOSSTERM"
+>Bugzilla</I
+> pages. Contrary to
+ popular belief, the apache web server has nothing to do
+ with the ancient and noble Native American tribe, but
+ instead derived its name from the fact that it was
+ <SPAN
+CLASS="QUOTE"
+>"a patchy"</SPAN
+> version of the original
+ <SPAN
+CLASS="ACRONYM"
+>NCSA</SPAN
+> world-wide-web server.</P
></DD
></DL
></DIV
@@ -12435,7 +16712,21 @@ NAME="GLOSS_B"
></DT
><DD
><P
->A "Bug" in Bugzilla refers to an issue entered into the database which has an associated number, assignments, comments, etc. Many also refer to a "Ticket" or "Issue"; in this context, they are synonymous.</P
+> A <SPAN
+CLASS="QUOTE"
+>"Bug"</SPAN
+> in Bugzilla refers to an issue
+ entered into the database which has an associated number,
+ assignments, comments, etc. Some also refer to a
+ <SPAN
+CLASS="QUOTE"
+>"tickets"</SPAN
+> or <SPAN
+CLASS="QUOTE"
+>"issues"</SPAN
+>; in the
+ context of Bugzilla, they are synonymous.
+ </P
></DD
><DT
><B
@@ -12443,7 +16734,11 @@ NAME="GLOSS_B"
></DT
><DD
><P
->Each Bugzilla Bug is assigned a number that uniquely identifies that Bug. The Bug associated with a Bug Number can be pulled up via a query, or easily from the very front page by typing the number in the "Find" box.</P
+> Each Bugzilla Bug is assigned a number that uniquely
+ identifies that Bug. The Bug associated with a Bug Number
+ can be pulled up via a query, or easily from the very
+ front page by typing the number in the "Find" box.
+ </P
></DD
><DT
><B
@@ -12451,7 +16746,150 @@ NAME="GLOSS_B"
></DT
><DD
><P
->A Bug has stages through which it must pass before becoming a "closed bug", including acceptance, resolution, and verification. The "Bug Life Cycle" is moderately flexible according to the needs of the organization using it, though.</P
+>A Bug has stages through which it must pass before
+ becoming a <SPAN
+CLASS="QUOTE"
+>"closed bug"</SPAN
+>, including
+ acceptance, resolution, and verification. The <SPAN
+CLASS="QUOTE"
+>"Bug
+ Life Cycle"</SPAN
+> is moderately flexible according to
+ the needs of the organization using it, though.</P
+></DD
+><DT
+><B
+>Bugzilla</B
+></DT
+><DD
+><P
+> Bugzilla is the industry-standard bug tracking system. It
+ is quite popular among Open Source enthusiasts.
+ </P
+></DD
+></DL
+></DIV
+><DIV
+CLASS="GLOSSDIV"
+><H1
+CLASS="GLOSSDIV"
+><A
+NAME="GLOSS_C"
+></A
+></H1
+><DL
+><DT
+><A
+NAME="GLOSS_COMPONENT"
+><B
+>Component</B
+></A
+></DT
+><DD
+><P
+> A Component is a subsection of a Product. It should be a
+ narrow category, tailored to your organization. All
+ Products must contain at least one Component (and, as a
+ matter of fact, creating a Product with no Components will
+ create an error in Bugzilla).
+ </P
+></DD
+><DT
+><A
+NAME="GLOSS_CPAN"
+><B
+><SPAN
+CLASS="ACRONYM"
+>CPAN</SPAN
+></B
+></A
+></DT
+><DD
+><P
+><SPAN
+CLASS="ACRONYM"
+>CPAN</SPAN
+> stands for the
+ <SPAN
+CLASS="QUOTE"
+>"Comprehensive Perl Archive Network"</SPAN
+>. CPAN
+ maintains a large number of extremely useful
+ <I
+CLASS="GLOSSTERM"
+>Perl</I
+> modules. By themselves, Perl
+ modules generally do nothing, but when used as part of a
+ larger program, they provide much-needed algorithms and
+ functionality.</P
+></DD
+></DL
+></DIV
+><DIV
+CLASS="GLOSSDIV"
+><H1
+CLASS="GLOSSDIV"
+><A
+NAME="GLOSS_D"
+>D</A
+></H1
+><DL
+><DT
+><B
+>daemon</B
+></DT
+><DD
+><P
+>A daemon is a computer program which runs in the
+ background. In general, most daemons are started at boot
+ time via System V init scripts, or through RC scripts on
+ BSD-based systems. <I
+CLASS="GLOSSTERM"
+>mysqld</I
+>, the
+ MySQL server, and <I
+CLASS="GLOSSTERM"
+>apache</I
+>, a web
+ server, are generally run as daemons.</P
+></DD
+></DL
+></DIV
+><DIV
+CLASS="GLOSSDIV"
+><H1
+CLASS="GLOSSDIV"
+><A
+NAME="GLOSS_G"
+></A
+></H1
+><DL
+><DT
+><B
+>Groups</B
+></DT
+><DD
+><P
+>The word <SPAN
+CLASS="QUOTE"
+>"Groups"</SPAN
+> has a very special
+ meaning to Bugzilla. Bugzilla's main security mechanism
+ comes by lumping users into groups, and assigning those
+ groups certain privileges to
+ <I
+CLASS="GLOSSTERM"
+>Products</I
+> and
+ <I
+CLASS="GLOSSTERM"
+>Components</I
+> in the
+ <I
+CLASS="GLOSSTERM"
+>Bugzilla</I
+> database.</P
></DD
></DL
></DIV
@@ -12473,12 +16911,34 @@ NAME="GLOSS_INFINITELOOP"
></DT
><DD
><P
-><EM
->See: </EM
+>A loop of information that never ends; see recursion.</P
+></DD
+></DL
+></DIV
+><DIV
+CLASS="GLOSSDIV"
+><H1
+CLASS="GLOSSDIV"
><A
-HREF="#GLOSS_RECURSION"
->Recursion</A
-></P
+NAME="GLOSS_M"
+>M</A
+></H1
+><DL
+><DT
+><B
+>mysqld</B
+></DT
+><DD
+><P
+>mysqld is the name of the
+ <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
></DD
></DL
></DIV
@@ -12497,20 +16957,74 @@ NAME="GLOSS_P"
></DT
><DD
><P
->A Product is a broad category of types of bugs. In general, there are several Components to a Product. A Product also defines a default Group (used for Bug Security) for all bugs entered into components beneath it.</P
+>A Product is a broad category of types of bugs. In
+ general, there are several Components to a Product. A
+ Product also defines a default Group (used for Bug
+ Security) for all bugs entered into components beneath
+ it.</P
><DIV
CLASS="EXAMPLE"
><A
-NAME="AEN2145"
+NAME="AEN2685"
></A
><P
><B
>Example 1. A Sample Product</B
></P
><P
->A company sells a software product called "X". They also maintain some older software called "Y", and have a secret project "Z". An effective use of Products might be to create Products "X", "Y", and "Z", each with Components "User Interface", "Database", and "Business Logic". They might also change group permissions so that only those people who are members of Group "Z" can see components and bugs under Product "Z".</P
+>A company sells a software product called
+ <SPAN
+CLASS="QUOTE"
+>"X"</SPAN
+>. They also maintain some older
+ software called <SPAN
+CLASS="QUOTE"
+>"Y"</SPAN
+>, and have a secret
+ project <SPAN
+CLASS="QUOTE"
+>"Z"</SPAN
+>. An effective use of Products
+ might be to create Products <SPAN
+CLASS="QUOTE"
+>"X"</SPAN
+>,
+ <SPAN
+CLASS="QUOTE"
+>"Y"</SPAN
+>, <SPAN
+CLASS="QUOTE"
+>"Z"</SPAN
+>, each with Components
+ of User Interface, Database, and Business Logic. They
+ might also change group permissions so that only those
+ people who are members of Group <SPAN
+CLASS="QUOTE"
+>"Z"</SPAN
+> can see
+ components and bugs under Product
+ <SPAN
+CLASS="QUOTE"
+>"Z"</SPAN
+>.</P
></DIV
></DD
+><DT
+><B
+>Perl</B
+></DT
+><DD
+><P
+>First written by Larry Wall, Perl is a remarkable
+ program language. It has the benefits of the flexibility
+ of an interpreted scripting language (such as shell
+ script), combined with the speed and power of a compiled
+ language, such as C. <I
+CLASS="GLOSSTERM"
+>Bugzilla</I
+> is
+ maintained in Perl.</P
+></DD
></DL
></DIV
><DIV
@@ -12524,11 +17038,33 @@ NAME="GLOSS_Q"
><DL
><DT
><B
->Q/A</B
+>QA</B
></DT
><DD
><P
->"Q/A" is short for "Quality Assurance". In most large software development organizations, there is a team devoted to ensuring the product meets minimum standards before shipping. This team will also generally want to track the progress of bugs over their life cycle, thus the need for the "Q/A Contact" field in a Bug.</P
+><SPAN
+CLASS="QUOTE"
+>"QA"</SPAN
+>, <SPAN
+CLASS="QUOTE"
+>"Q/A"</SPAN
+>, and
+ <SPAN
+CLASS="QUOTE"
+>"Q.A."</SPAN
+> are short for <SPAN
+CLASS="QUOTE"
+>"Quality
+ Assurance"</SPAN
+>. In most large software development
+ organizations, there is a team devoted to ensuring the
+ product meets minimum standards before shipping. This
+ team will also generally want to track the progress of
+ bugs over their life cycle, thus the need for the
+ <SPAN
+CLASS="QUOTE"
+>"QA Contact"</SPAN
+> field in a Bug.</P
></DD
></DL
></DIV
@@ -12542,17 +17078,123 @@ NAME="GLOSS_R"
></H1
><DL
><DT
+><A
+NAME="GLOSS_RECURSION"
><B
>Recursion</B
+></A
></DT
><DD
><P
-><EM
->See: </EM
+>The property of a function looking back at itself for
+ something. <SPAN
+CLASS="QUOTE"
+>"GNU"</SPAN
+>, for instance, stands for
+ <SPAN
+CLASS="QUOTE"
+>"GNU's Not UNIX"</SPAN
+>, thus recursing upon itself
+ for definition. For further clarity, see Infinite
+ Loop.</P
+></DD
+></DL
+></DIV
+><DIV
+CLASS="GLOSSDIV"
+><H1
+CLASS="GLOSSDIV"
><A
-HREF="#GLOSS_INFINITELOOP"
->Infinite Loop</A
-></P
+NAME="GLOSS_S"
+>S</A
+></H1
+><DL
+><DT
+><B
+><SPAN
+CLASS="ACRONYM"
+>SGML</SPAN
+></B
+></DT
+><DD
+><P
+><SPAN
+CLASS="ACRONYM"
+>SGML</SPAN
+> stands for <SPAN
+CLASS="QUOTE"
+>"Standard
+ Generalized Markup Language"</SPAN
+>. Created in the
+ 1980's to provide an extensible means to maintain
+ documentation based upon content instead of presentation,
+ <SPAN
+CLASS="ACRONYM"
+>SGML</SPAN
+> has withstood the test of time as
+ a robust, powerful language.
+ <I
+CLASS="GLOSSTERM"
+><SPAN
+CLASS="ACRONYM"
+>XML</SPAN
+></I
+> is the
+ <SPAN
+CLASS="QUOTE"
+>"baby brother"</SPAN
+> of SGML; any valid
+ <SPAN
+CLASS="ACRONYM"
+>XML</SPAN
+> document it, by definition, a valid
+ <SPAN
+CLASS="ACRONYM"
+>SGML</SPAN
+> document. The document you are
+ reading is written and maintained in
+ <SPAN
+CLASS="ACRONYM"
+>SGML</SPAN
+>, and is also valid
+ <SPAN
+CLASS="ACRONYM"
+>XML</SPAN
+> if you modify the Document Type
+ Definition.</P
+></DD
+></DL
+></DIV
+><DIV
+CLASS="GLOSSDIV"
+><H1
+CLASS="GLOSSDIV"
+><A
+NAME="GLOSS_T"
+>T</A
+></H1
+><DL
+><DT
+><A
+NAME="GLOSS_TARGET_MILESTONE"
+><B
+>Target Milestone</B
+></A
+></DT
+><DD
+><P
+> Target Milestones are Product goals. They are
+ configurable on a per-Product basis. Most software
+ development houses have a concept of
+ <SPAN
+CLASS="QUOTE"
+>"milestones"</SPAN
+> where the people funding a
+ project expect certain functionality on certain dates.
+ Bugzilla facilitates meeting these milestones by giving
+ you the ability to declare by which milestone a bug will be
+ fixed, or an enhancement will be implemented.
+ </P
></DD
></DL
></DIV
@@ -12566,12 +17208,17 @@ NAME="GLOSS_Z"
></H1
><DL
><DT
+><A
+NAME="ZARRO-BOOGS-FOUND"
><B
>Zarro Boogs Found</B
+></A
></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 the cryptic response sent by Bugzilla when a
+ query returned no results. It is just a goofy way of
+ saying "Zero Bugs Found".</P
></DD
></DL
></DIV
@@ -12579,4 +17226,4 @@ NAME="GLOSS_Z"
></DIV
></BODY
></HTML
->
\ No newline at end of file
+>
diff --git a/docs/html/CVS/Entries b/docs/html/CVS/Entries
index a46848e7d..13c860283 100644
--- a/docs/html/CVS/Entries
+++ b/docs/html/CVS/Entries
@@ -1,67 +1,70 @@
-/Bugzilla-Guide.html/1.3/Wed Apr 25 07:38:17 2001//
-/about.html/1.2/Wed Apr 25 07:11:48 2001//
-/aboutthisguide.html/1.2/Wed Apr 25 07:11:48 2001//
-/administration.html/1.2/Wed Apr 25 07:11:48 2001//
-/bonsai.html/1.2/Wed Apr 25 07:11:49 2001//
-/bugprobs.html/1.2/Wed Apr 25 07:11:49 2001//
-/bz30.html/1.2/Wed Apr 25 07:11:49 2001//
-/cleanupwork.html/1.2/Wed Apr 25 07:11:50 2001//
-/cmdline.html/1.2/Wed Apr 25 07:11:50 2001//
-/contributors.html/1.2/Wed Apr 25 07:11:50 2001//
-/conventions.html/1.2/Wed Apr 25 07:11:50 2001//
-/copyright.html/1.2/Wed Apr 25 07:11:51 2001//
-/credits.html/1.2/Wed Apr 25 07:11:51 2001//
-/cvs.html/1.2/Wed Apr 25 07:11:51 2001//
-/database.html/1.2/Wed Apr 25 07:11:51 2001//
-/dbaseintegrity.html/1.2/Wed Apr 25 07:11:51 2001//
-/dbdoc.html/1.2/Wed Apr 25 07:11:52 2001//
-/dbschema.html/1.2/Wed Apr 25 07:11:52 2001//
-/dbschema.jpg/1.3/Wed Apr 25 07:11:52 2001//
-/disclaimer.html/1.2/Wed Apr 25 07:11:53 2001//
-/downloadlinks.html/1.1/Wed Apr 25 07:11:54 2001//
-/faq.html/1.2/Wed Apr 25 07:11:54 2001//
-/feedback.html/1.2/Wed Apr 25 07:11:55 2001//
-/future.html/1.2/Wed Apr 25 07:11:55 2001//
-/gfdl.html/1.2/Wed Apr 25 07:11:55 2001//
-/gfdl_0.html/1.2/Wed Apr 25 07:11:56 2001//
-/gfdl_1.html/1.2/Wed Apr 25 07:11:56 2001//
-/gfdl_10.html/1.2/Wed Apr 25 07:11:56 2001//
-/gfdl_2.html/1.2/Wed Apr 25 07:11:56 2001//
-/gfdl_3.html/1.2/Wed Apr 25 07:11:57 2001//
-/gfdl_4.html/1.2/Wed Apr 25 07:11:57 2001//
-/gfdl_5.html/1.2/Wed Apr 25 07:11:57 2001//
-/gfdl_6.html/1.2/Wed Apr 25 07:11:57 2001//
-/gfdl_7.html/1.2/Wed Apr 25 07:11:58 2001//
-/gfdl_8.html/1.2/Wed Apr 25 07:11:58 2001//
-/gfdl_9.html/1.2/Wed Apr 25 07:11:58 2001//
-/gfdl_howto.html/1.2/Wed Apr 25 07:11:58 2001//
-/glossary.html/1.2/Wed Apr 25 07:11:59 2001//
-/granttables.html/1.2/Wed Apr 25 07:11:59 2001//
-/how.html/1.2/Wed Apr 25 07:11:59 2001//
-/index.html/1.2/Wed Apr 25 07:12:00 2001//
-/init4me.html/1.2/Wed Apr 25 07:12:00 2001//
-/installation.html/1.2/Wed Apr 25 07:12:00 2001//
-/integration.html/1.2/Wed Apr 25 07:12:01 2001//
-/newversions.html/1.2/Wed Apr 25 07:12:01 2001//
-/patches.html/1.2/Wed Apr 25 07:12:01 2001//
-/postinstall-check.html/1.2/Wed Apr 25 07:12:01 2001//
-/programadmin.html/1.2/Wed Apr 25 07:12:02 2001//
-/quicksearch.html/1.2/Wed Apr 25 07:12:02 2001//
-/readme.unix.html/1.2/Wed Apr 25 07:12:02 2001//
-/readme.windows.html/1.2/Wed Apr 25 07:12:02 2001//
-/rhbugzilla.html/1.1/Wed Apr 25 07:12:03 2001//
-/scm.html/1.2/Wed Apr 25 07:12:03 2001//
-/searching.html/1.2/Wed Apr 25 07:12:04 2001//
-/security.html/1.3/Wed Apr 25 07:38:19 2001//
-/setperl.html/1.2/Wed Apr 25 07:12:04 2001//
-/spamlite.html/1.2/Wed Apr 25 07:12:04 2001//
-/tinderbox.html/1.2/Wed Apr 25 07:12:05 2001//
-/trackingbugs.html/1.2/Wed Apr 25 07:12:05 2001//
-/translations.html/1.2/Wed Apr 25 07:12:05 2001//
-/useradmin.html/1.2/Wed Apr 25 07:12:06 2001//
-/using.html/1.2/Wed Apr 25 07:12:06 2001//
-/usingbz-conc.html/1.2/Wed Apr 25 07:12:06 2001//
-/variants.html/1.1/Wed Apr 25 07:12:06 2001//
-/whatis.html/1.2/Wed Apr 25 07:12:07 2001//
-/why.html/1.2/Wed Apr 25 07:12:07 2001//
+/Bugzilla-Guide.html/1.9/Wed Aug 29 18:13:38 2001//TBUGZILLA-2_14
+/about.html/1.4/Fri Aug 10 22:26:40 2001//TBUGZILLA-2_14
+/aboutthisguide.html/1.6/Wed Aug 29 17:25:25 2001//TBUGZILLA-2_14
+/administration.html/1.5/Wed Aug 22 03:44:17 2001//TBUGZILLA-2_14
+/bonsai.html/1.5/Wed Aug 22 03:44:17 2001//TBUGZILLA-2_14
+/bsdinstall.html/1.1/Fri Aug 10 22:26:42 2001//TBUGZILLA-2_14
+/bzhacking.html/1.1/Wed Aug 29 17:25:25 2001//TBUGZILLA-2_14
+/cmdline.html/1.5/Wed Aug 22 03:44:18 2001//TBUGZILLA-2_14
+/contributors.html/1.5/Wed Aug 29 17:25:25 2001//TBUGZILLA-2_14
+/conventions.html/1.5/Wed Aug 22 03:44:18 2001//TBUGZILLA-2_14
+/copyright.html/1.6/Wed Aug 29 17:25:26 2001//TBUGZILLA-2_14
+/credits.html/1.5/Wed Aug 29 17:25:26 2001//TBUGZILLA-2_14
+/cvs.html/1.6/Wed Aug 29 17:25:26 2001//TBUGZILLA-2_14
+/database.html/1.4/Fri Aug 10 22:26:44 2001//TBUGZILLA-2_14
+/dbdoc.html/1.6/Wed Aug 29 17:25:26 2001//TBUGZILLA-2_14
+/dbschema.html/1.5/Wed Aug 29 17:25:26 2001//TBUGZILLA-2_14
+/disclaimer.html/1.4/Fri Aug 10 22:26:46 2001//TBUGZILLA-2_14
+/downloadlinks.html/1.3/Fri Aug 10 22:26:46 2001//TBUGZILLA-2_14
+/errata.html/1.1/Fri Aug 10 22:26:47 2001//TBUGZILLA-2_14
+/faq.html/1.7/Wed Aug 29 17:25:27 2001//TBUGZILLA-2_14
+/feedback.html/1.4/Fri Aug 10 22:26:48 2001//TBUGZILLA-2_14
+/future.html/1.6/Wed Aug 29 17:25:28 2001//TBUGZILLA-2_14
+/geninstall.html/1.3/Wed Aug 29 17:25:28 2001//TBUGZILLA-2_14
+/gfdl.html/1.7/Wed Aug 29 17:25:28 2001//TBUGZILLA-2_14
+/gfdl_0.html/1.4/Fri Aug 10 22:26:49 2001//TBUGZILLA-2_14
+/gfdl_1.html/1.4/Fri Aug 10 22:26:49 2001//TBUGZILLA-2_14
+/gfdl_10.html/1.4/Fri Aug 10 22:26:50 2001//TBUGZILLA-2_14
+/gfdl_2.html/1.4/Fri Aug 10 22:26:50 2001//TBUGZILLA-2_14
+/gfdl_3.html/1.4/Fri Aug 10 22:26:51 2001//TBUGZILLA-2_14
+/gfdl_4.html/1.4/Fri Aug 10 22:26:51 2001//TBUGZILLA-2_14
+/gfdl_5.html/1.4/Fri Aug 10 22:26:52 2001//TBUGZILLA-2_14
+/gfdl_6.html/1.4/Fri Aug 10 22:26:52 2001//TBUGZILLA-2_14
+/gfdl_7.html/1.4/Fri Aug 10 22:26:52 2001//TBUGZILLA-2_14
+/gfdl_8.html/1.4/Fri Aug 10 22:26:53 2001//TBUGZILLA-2_14
+/gfdl_9.html/1.4/Fri Aug 10 22:26:53 2001//TBUGZILLA-2_14
+/gfdl_howto.html/1.7/Wed Aug 29 17:25:28 2001//TBUGZILLA-2_14
+/glossary.html/1.7/Wed Aug 29 17:25:28 2001//TBUGZILLA-2_14
+/granttables.html/1.6/Wed Aug 29 17:25:28 2001//TBUGZILLA-2_14
+/how.html/1.7/Wed Aug 29 17:25:29 2001//TBUGZILLA-2_14
+/index.html/1.7/Wed Aug 29 17:25:29 2001//TBUGZILLA-2_14
+/init4me.html/1.5/Wed Aug 22 03:44:20 2001//TBUGZILLA-2_14
+/installation.html/1.7/Wed Aug 29 17:25:29 2001//TBUGZILLA-2_14
+/integration.html/1.5/Wed Aug 22 03:44:20 2001//TBUGZILLA-2_14
+/newversions.html/1.5/Wed Aug 22 03:44:20 2001//TBUGZILLA-2_14
+/osx.html/1.1/Fri Aug 10 22:26:58 2001//TBUGZILLA-2_14
+/patches.html/1.6/Wed Aug 29 17:25:29 2001//TBUGZILLA-2_14
+/postinstall-check.html/1.5/Wed Aug 22 03:44:21 2001//TBUGZILLA-2_14
+/programadmin.html/1.7/Wed Aug 29 17:25:29 2001//TBUGZILLA-2_14
+/quicksearch.html/1.6/Wed Aug 29 17:25:29 2001//TBUGZILLA-2_14
+/rewrite.html/1.1/Wed Aug 22 03:44:21 2001//TBUGZILLA-2_14
+/rhbugzilla.html/1.5/Wed Aug 22 03:44:22 2001//TBUGZILLA-2_14
+/scm.html/1.5/Wed Aug 22 03:44:22 2001//TBUGZILLA-2_14
+/security.html/1.6/Fri Aug 10 22:27:01 2001//TBUGZILLA-2_14
+/setperl.html/1.7/Wed Aug 29 17:25:30 2001//TBUGZILLA-2_14
+/stepbystep.html/1.4/Wed Aug 29 18:13:39 2001//TBUGZILLA-2_14
+/tinderbox.html/1.5/Wed Aug 22 03:44:23 2001//TBUGZILLA-2_14
+/translations.html/1.4/Fri Aug 10 22:27:03 2001//TBUGZILLA-2_14
+/useradmin.html/1.5/Wed Aug 22 03:44:23 2001//TBUGZILLA-2_14
+/using.html/1.5/Wed Aug 22 03:44:23 2001//TBUGZILLA-2_14
+/usingbz-conc.html/1.5/Wed Aug 22 03:44:23 2001//TBUGZILLA-2_14
+/variant_fenris.html/1.1/Wed Aug 22 03:44:23 2001//TBUGZILLA-2_14
+/variant_issuezilla.html/1.1/Wed Aug 22 03:44:24 2001//TBUGZILLA-2_14
+/variant_perforce.html/1.1/Wed Aug 22 03:44:24 2001//TBUGZILLA-2_14
+/variant_scarab.html/1.1/Wed Aug 22 03:44:24 2001//TBUGZILLA-2_14
+/variant_sourceforge.html/1.2/Wed Aug 29 17:25:30 2001//TBUGZILLA-2_14
+/variants.html/1.5/Wed Aug 29 17:25:30 2001//TBUGZILLA-2_14
+/whatis.html/1.5/Wed Aug 22 03:44:25 2001//TBUGZILLA-2_14
+/why.html/1.5/Wed Aug 22 03:44:26 2001//TBUGZILLA-2_14
+/win32.html/1.3/Wed Aug 29 17:25:30 2001//TBUGZILLA-2_14
D
diff --git a/docs/html/CVS/Tag b/docs/html/CVS/Tag
new file mode 100644
index 000000000..c10f87310
--- /dev/null
+++ b/docs/html/CVS/Tag
@@ -0,0 +1 @@
+NBUGZILLA-2_14
diff --git a/docs/html/about.html b/docs/html/about.html
index 7133e3cca..affb6046f 100644
--- a/docs/html/about.html
+++ b/docs/html/about.html
@@ -4,7 +4,7 @@
>About This Guide</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
diff --git a/docs/html/aboutthisguide.html b/docs/html/aboutthisguide.html
index 7a8de6691..0ed58bd19 100644
--- a/docs/html/aboutthisguide.html
+++ b/docs/html/aboutthisguide.html
@@ -4,7 +4,7 @@
>Purpose and Scope of this Guide</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
@@ -74,53 +74,60 @@ NAME="ABOUTTHISGUIDE"
>1.1. Purpose and Scope of this Guide</A
></H1
><P
-> This document was started on September 17, 2000
- by Matthew P. Barnson after a great deal of procrastination updating the Bugzilla FAQ,
- which I left untouched for nearly half a year.
- After numerous complete rewrites and reformatting, it is the document you see today.
+> This document was started on September 17, 2000 by Matthew P.
+ Barnson after a great deal of procrastination updating the
+ Bugzilla FAQ, which I left untouched for nearly half a year.
+ After numerous complete rewrites and reformatting, it is the
+ document you see today.
</P
><P
-> Despite the lack of updates, Bugzilla is simply the best piece of bug-tracking software
- the world has ever seen. This document is intended to be the comprehensive guide to
- the installation, administration, maintenance, and use of the Bugzilla bug-tracking system.
+> Bugzilla is simply the best piece of bug-tracking software the
+ world has ever seen. This document is intended to be the
+ comprehensive guide to the installation, administration,
+ maintenance, and use of the Bugzilla bug-tracking system.
</P
><P
-> This release of the Bugzilla Guide is the <EM
->2.11</EM
-> release.
- It is so named that it may match the current version of Bugzilla.
- The numbering tradition stems from that used for many free software projects,
+> This release of the Bugzilla Guide is the
+ <EM
+>2.14</EM
+> release. It is so named that it
+ may match the current version of Bugzilla. The numbering
+ tradition stems from that used for many free software projects,
in which <EM
>even-numbered</EM
-> point releases (1.2, 1.14, etc.)
- are considered "stable releases", intended for public consumption; on the other
- hand, <EM
+> point releases (1.2,
+ 1.14, etc.) are considered "stable releases", intended for
+ public consumption; on the other hand,
+ <EM
>odd-numbered</EM
-> point releases (1.3, 2.09, etc.)
- are considered unstable <EM
+> point releases (1.3, 2.09,
+ etc.) are considered unstable <EM
>development</EM
-> releases intended
- for advanced users, systems administrators, developers, and those who enjoy
- a lot of pain.
+>
+ releases intended for advanced users, systems administrators,
+ developers, and those who enjoy a lot of pain.
</P
><P
-> Newer revisions of the Bugzilla Guide will follow the numbering conventions of
- the main-tree Bugzilla releases, available at
+> Newer revisions of the Bugzilla Guide follow the numbering
+ conventions of the main-tree Bugzilla releases, available at
<A
-HREF="http://www.mozilla.org/bugs/source.html"
+HREF="http://www.mozilla.org/projects/bugzilla"
TARGET="_top"
->Mozilla.org</A
->, with
- the exception that intermediate releases will have a minor revision number
- following a period. For instance, if the current version of Bugzilla is 4.2,
- the current "stable" version of the Bugzilla guide, in, say, it's fifth revision,
- would be numbered "4.2.5". Got it? Good.
+>http://www.mozilla.org/projects/bugzilla</A
+>. Intermediate releases will have
+ a minor revision number following a period. The current version
+ of Bugzilla, as of this writing (August 10, 2001) is 2.14; if
+ something were seriously wrong with that edition of the Guide,
+ subsequent releases would receive an additional dotted-decimal
+ digit to indicate the update (2.14.1, 2.14.2, etc.).
+ Got it? Good.
</P
><P
-> I wrote this in response to the enormous demand for decent Bugzilla documentation.
- I have incorporated instructions from the Bugzilla README, Frequently Asked Questions,
- Database Schema Document, and various mailing lists to create it.
- Chances are, there are glaring errors in this documentation; please contact
+> I wrote this in response to the enormous demand for decent
+ Bugzilla documentation. I have incorporated instructions from
+ the Bugzilla README, Frequently Asked Questions, Database Schema
+ Document, and various mailing lists to create it. Chances are,
+ there are glaring errors in this documentation; please contact
<TT
CLASS="EMAIL"
><<A
diff --git a/docs/html/administration.html b/docs/html/administration.html
index feef30d12..6a107f712 100644
--- a/docs/html/administration.html
+++ b/docs/html/administration.html
@@ -4,14 +4,14 @@
>Administering Bugzilla</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="PREVIOUS"
-TITLE="Win32 (Win98+/NT/2K) Installation"
-HREF="readme.windows.html"><LINK
+TITLE="Win32 Installation Notes"
+HREF="win32.html"><LINK
REL="NEXT"
TITLE="Post-Installation Checklist"
HREF="postinstall-check.html"></HEAD
@@ -41,7 +41,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
-HREF="readme.windows.html"
+HREF="win32.html"
>Prev</A
></TD
><TD
@@ -67,7 +67,7 @@ CLASS="CHAPTER"
><H1
><A
NAME="ADMINISTRATION"
->Chapter 3. Administering Bugzilla</A
+>Chapter 4. Administering Bugzilla</A
></H1
><DIV
CLASS="TOC"
@@ -77,46 +77,46 @@ CLASS="TOC"
>Table of Contents</B
></DT
><DT
->3.1. <A
+>4.1. <A
HREF="postinstall-check.html"
>Post-Installation Checklist</A
></DT
><DT
->3.2. <A
+>4.2. <A
HREF="useradmin.html"
>User Administration</A
></DT
><DD
><DL
><DT
->3.2.1. <A
+>4.2.1. <A
HREF="useradmin.html#DEFAULTUSER"
>Creating the Default User</A
></DT
><DT
->3.2.2. <A
+>4.2.2. <A
HREF="useradmin.html#MANAGEUSERS"
>Managing Other Users</A
></DT
><DD
><DL
><DT
->3.2.2.1. <A
+>4.2.2.1. <A
HREF="useradmin.html#LOGIN"
>Logging In</A
></DT
><DT
->3.2.2.2. <A
+>4.2.2.2. <A
HREF="useradmin.html#CREATENEWUSERS"
>Creating new users</A
></DT
><DT
->3.2.2.3. <A
+>4.2.2.3. <A
HREF="useradmin.html#DISABLEUSERS"
>Disabling Users</A
></DT
><DT
->3.2.2.4. <A
+>4.2.2.4. <A
HREF="useradmin.html#MODIFYUSERS"
>Modifying Users</A
></DT
@@ -125,46 +125,47 @@ HREF="useradmin.html#MODIFYUSERS"
></DL
></DD
><DT
->3.3. <A
+>4.3. <A
HREF="programadmin.html"
->Product, Component, Milestone, and Version Administration</A
+>Product, Component, Milestone, and Version
+ Administration</A
></DT
><DD
><DL
><DT
->3.3.1. <A
+>4.3.1. <A
HREF="programadmin.html#PRODUCTS"
>Products</A
></DT
><DT
->3.3.2. <A
+>4.3.2. <A
HREF="programadmin.html#COMPONENTS"
>Components</A
></DT
><DT
->3.3.3. <A
+>4.3.3. <A
HREF="programadmin.html#VERSIONS"
>Versions</A
></DT
><DT
->3.3.4. <A
+>4.3.4. <A
HREF="programadmin.html#MILESTONES"
>Milestones</A
></DT
><DT
->3.3.5. <A
+>4.3.5. <A
HREF="programadmin.html#VOTING"
>Voting</A
></DT
><DT
->3.3.6. <A
+>4.3.6. <A
HREF="programadmin.html#GROUPS"
>Groups and Group Security</A
></DT
></DL
></DD
><DT
->3.4. <A
+>4.4. <A
HREF="security.html"
>Bugzilla Security</A
></DT
@@ -172,12 +173,25 @@ HREF="security.html"
></DIV
><FONT
COLOR="RED"
->Or, I just got this cool thing installed. Now what the heck do I do with it?</FONT
+> Or, I just got this cool thing installed. Now what the heck do I
+ do with it?
+ </FONT
><P
->So you followed the README isntructions to the letter, and
-just logged into bugzilla with your super-duper god account and you are sitting at the query
-screen. Yet, you have nothing to query. Your first act of business needs to be to setup the
-operating parameters for bugzilla.</P
+> So you followed <SPAN
+CLASS="QUOTE"
+>"<A
+HREF="installation.html"
+>Bugzilla Installation</A
+>"</SPAN
+> to the
+ letter, and logged into Bugzilla for the very first time with your
+ super-duper god account. You sit, contentedly staring at the
+ Bugzilla Query Screen, the worst of the whole mad business of
+ installing this terrific program behind you. It seems, though, you
+ have nothing yet to query! Your first act of business should be to
+ setup the operating parameters for Bugzilla so you can get busy
+ getting data into your bug tracker.
+ </P
></DIV
><DIV
CLASS="NAVFOOTER"
@@ -194,7 +208,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
-HREF="readme.windows.html"
+HREF="win32.html"
>Prev</A
></TD
><TD
@@ -219,7 +233,7 @@ HREF="postinstall-check.html"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
->Win32 (Win98+/NT/2K) Installation</TD
+>Win32 Installation Notes</TD
><TD
WIDTH="34%"
ALIGN="center"
diff --git a/docs/html/bonsai.html b/docs/html/bonsai.html
index ec2fb924a..5be34aff5 100644
--- a/docs/html/bonsai.html
+++ b/docs/html/bonsai.html
@@ -4,7 +4,7 @@
>Bonsai</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
@@ -74,7 +74,23 @@ NAME="BONSAI"
>5.1. Bonsai</A
></H1
><P
->We need Bonsai integration information.</P
+>Bonsai is a web-based tool for managing <A
+HREF="cvs.html"
+>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. These kinds of changes cause the
+ engineer responsible to be <SPAN
+CLASS="QUOTE"
+>"on the hook"</SPAN
+> (include
+ cool URL link here for Hook policies at mozilla.org). Bonsai
+ also includes gateways to <A
+HREF="tinderbox.html"
+>Tinderbox, the Mozilla automated build management system</A
+> and Bugzilla </P
></DIV
><DIV
CLASS="NAVFOOTER"
diff --git a/docs/html/bz30.html b/docs/html/bsdinstall.html
similarity index 65%
rename from docs/html/bz30.html
rename to docs/html/bsdinstall.html
index b133205be..56f68a3b1 100644
--- a/docs/html/bz30.html
+++ b/docs/html/bsdinstall.html
@@ -1,23 +1,23 @@
<HTML
><HEAD
><TITLE
->Bugzilla 3.0</TITLE
+>BSD Installation Notes</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
-TITLE="The Future of Bugzilla"
-HREF="future.html"><LINK
+TITLE="Installation"
+HREF="installation.html"><LINK
REL="PREVIOUS"
-TITLE="Database Integrity"
-HREF="dbaseintegrity.html"><LINK
+TITLE="Mac OS X Installation Notes"
+HREF="osx.html"><LINK
REL="NEXT"
-TITLE="The Bugzilla FAQ"
-HREF="faq.html"></HEAD
+TITLE="Installation General Notes"
+HREF="geninstall.html"></HEAD
><BODY
CLASS="SECTION"
BGCOLOR="#FFFFFF"
@@ -44,20 +44,20 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
-HREF="dbaseintegrity.html"
+HREF="osx.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
->Chapter 6. The Future of Bugzilla</TD
+>Chapter 3. Installation</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
-HREF="faq.html"
+HREF="geninstall.html"
>Next</A
></TD
></TR
@@ -70,11 +70,16 @@ CLASS="SECTION"
><H1
CLASS="SECTION"
><A
-NAME="BZ30"
->6.6. Bugzilla 3.0</A
+NAME="BSDINSTALL"
+>3.4. BSD Installation Notes</A
></H1
><P
->One day, Bugzilla 3.0 will have lots of cool stuff.</P
+> For instructions on how to set up Bugzilla on FreeBSD, NetBSD, OpenBSD, BSDi, etc. please
+ consult <A
+HREF="osx.html"
+>Section 3.3</A
+>.
+ </P
></DIV
><DIV
CLASS="NAVFOOTER"
@@ -91,7 +96,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
-HREF="dbaseintegrity.html"
+HREF="osx.html"
>Prev</A
></TD
><TD
@@ -107,7 +112,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
-HREF="faq.html"
+HREF="geninstall.html"
>Next</A
></TD
></TR
@@ -116,20 +121,20 @@ HREF="faq.html"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
->Database Integrity</TD
+>Mac OS X Installation Notes</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
-HREF="future.html"
+HREF="installation.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
->The Bugzilla FAQ</TD
+>Installation General Notes</TD
></TR
></TABLE
></DIV
diff --git a/docs/html/bugprobs.html b/docs/html/bugprobs.html
deleted file mode 100644
index 24805ea35..000000000
--- a/docs/html/bugprobs.html
+++ /dev/null
@@ -1,211 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Bug Issues</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="The Future of Bugzilla"
-HREF="future.html"><LINK
-REL="PREVIOUS"
-TITLE="Description Flags and Tracking Bugs"
-HREF="trackingbugs.html"><LINK
-REL="NEXT"
-TITLE="Database Integrity"
-HREF="dbaseintegrity.html"></HEAD
-><BODY
-CLASS="SECTION"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="trackingbugs.html"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 6. The Future of Bugzilla</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="dbaseintegrity.html"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="SECTION"
-><H1
-CLASS="SECTION"
-><A
-NAME="BUGPROBS"
->6.4. Bug Issues</A
-></H1
-><P
-><P
-CLASS="LITERALLAYOUT"
->1. Inline Bug Changes<br>
-<br>
-Why do I see so many "moving to M5" and "reassigning to blahblah"<br>
-messages, and in other circumstances none are entered? Why aren't these<br>
-automatically generated? A comment should be only necessary when there<br>
-is something to add, and if I'm not interested in this sort of<br>
-information, I should be able to hide it.<br>
-<br>
-At the moment we're in a hybrid world where we don't get everything, but<br>
-we can't get rid of the bug change "messages" either. Furthermore,<br>
-"View Bug Activity" requires me to manually cross reference events on<br>
-another page, rather than being able to visually see the chronological<br>
-order. Shouldn't I be able to see all the information on one page?<br>
-<br>
-A proposal to allow bugs to be shown either way is at<br>
-"http://bugzilla.mozilla.org/show_bug.cgi?id=11368".<br>
-<br>
-2. Hard Wrapping Comments<br>
-<br>
-One thing that annoys me is the fact that comments are "hard wrapped" to<br>
-a certain column width. This is a mistake Internet Mail and News has<br>
-made, unlike every word processor in existence, and as a consequence,<br>
-Usenet suffers to this day from bad software. Why has Bugzilla repeated<br>
-the problem?<br>
-<br>
-Hard wrapping to a certain column width is open to abuse (see old<br>
-Mozilla browsers that didn't wrap properly, resulting in many ugly bug<br>
-reports we have to read to this day), and furthermore doesn't expand to<br>
-fill greater screen sizes. I'm also under the impression the current<br>
-hard wrap uses a non-standard HTML facility. See<br>
-"http://bugzilla.mozilla.org/show_bug.cgi?id=11901".<br>
-<br>
-3. REMIND and LATER Are Evil<br>
-<br>
-I really hate REMIND and LATER. Not because they mean something<br>
-won't be implemented, but because they aren't the best solutions.<br>
-<br>
-Why are they bad? Well, basically because they are not resolved, yet<br>
-they are marked as such. Hence queries have to be well crafted to<br>
-include them.<br>
-<br>
-LATER, according to Bugzilla, means it won't be done this release. <br>
-There is a better mechanism of doing this, that is assigning to<br>
-nobody@mozilla.org and making the milestone blank. It's more likely to<br>
-appear in a casual query, and it doesn't resolve the bug.<br>
-<br>
-REMIND, according to Bugzilla, means it might still be implemented this<br>
-release. Well, why not just move it to a later milestone then? You're<br>
-a lot less likely to forget it. If it's really needed, a keyword would<br>
-be better.<br>
-<br>
-Some people can't use blank milestones to mean an untargetted milestone,<br>
-since they use this to assess new bugs that have no target. Hence, it<br>
-would be nice to distinguish between bugs that have not yet been<br>
-considered, and those that really are not assigned to any milestone in<br>
-the future (assumedly beyond).<br>
-<br>
-All this is covered at<br>
-"http://bugzilla.mozilla.org/show_bug.cgi?id=13534".<br>
-<br>
-4. Create An Enhancement Field<br>
-<br>
-Currently enhancement is an option in severity. This means that<br>
-important enhancements (like for example, POP3 support) are not properly<br>
-distinguished as such, because they need a proper severity. This<br>
-dilutes the meaning of enhancement.<br>
-<br>
-If enhancement was separated, we could properly see what was an<br>
-enhancement. See "http://bugzilla.mozilla.org/show_bug.cgi?id=9412". I<br>
-see keywords like [RFE] and [FEATURE] that seem to be compensating for<br>
-this problem.</P
-></P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="trackingbugs.html"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="dbaseintegrity.html"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Description Flags and Tracking Bugs</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="future.html"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Database Integrity</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
diff --git a/docs/html/bzhacking.html b/docs/html/bzhacking.html
new file mode 100644
index 000000000..5bb15b44f
--- /dev/null
+++ b/docs/html/bzhacking.html
@@ -0,0 +1,231 @@
+<HTML
+><HEAD
+><TITLE
+>Hacking Bugzilla</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide"
+HREF="index.html"><LINK
+REL="UP"
+TITLE="Useful Patches and Utilities for Bugzilla"
+HREF="patches.html"><LINK
+REL="PREVIOUS"
+TITLE="The Quicksearch Utility"
+HREF="quicksearch.html"><LINK
+REL="NEXT"
+TITLE="GNU Free Documentation License"
+HREF="gfdl.html"></HEAD
+><BODY
+CLASS="SECTION"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>The Bugzilla Guide</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="quicksearch.html"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Appendix D. Useful Patches and Utilities for Bugzilla</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="gfdl.html"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="SECTION"
+><H1
+CLASS="SECTION"
+><A
+NAME="BZHACKING"
+>D.5. Hacking Bugzilla</A
+></H1
+><P
+> What follows are some general guidelines for changing Bugzilla, and adhering to good coding practice while doing so. We've had some checkins in the past which ruined Bugzilla installations because of disregard for these conventions. Sorry for the lack of formatting; I got this info into the Guide on the day of 2.14 release and haven't formatted it yet.
+ </P
+><P
+CLASS="LITERALLAYOUT"
+><br>
+The following is a guide for reviewers when checking code into Bugzilla's<br>
+CVS repostory at mozilla.org. If you wish to submit patches to Bugzilla,<br>
+you should follow the rules and style conventions below. Any code that<br>
+does not adhere to these basic rules will not be added to Bugzilla's<br>
+codebase.<br>
+<br>
+ 1. Usage of variables in Regular Expressions<br>
+<br>
+ It is very important that you don't use a variable in a regular<br>
+ expression unless that variable is supposed to contain an expression.<br>
+ This especially applies when using grep. You should use:<br>
+<br>
+ grep ($_ eq $value, @array);<br>
+<br>
+ - NOT -<br>
+<br>
+ grep (/$value/, @array);<br>
+<br>
+ If you need to use a non-expression variable inside of an expression, be<br>
+ sure to quote it properly (using \Q..\E).<br>
+<br>
+Coding Style for Bugzilla<br>
+-------------------------<br>
+<br>
+While it's true that not all of the code currently in Bugzilla adheres to<br>
+this styleguide, it is something that is being worked toward. Therefore,<br>
+we ask that all new code (submitted patches and new files) follow this guide<br>
+as closely as possible (if you're only changing 1 or 2 lines, you don't have<br>
+to reformat the entire file :).<br>
+<br>
+ 1. Whitespace<br>
+<br>
+ Bugzilla's prefered indentation is 4 spaces (no tabs, please).<br>
+<br>
+ 2. Curly braces.<br>
+<br>
+ The opening brace of a block should be on the same line as the statement<br>
+ that is causing the block and the closing brace should be at the same<br>
+ indentation level as that statement, for example:<br>
+<br>
+ if ($var) {<br>
+ print "The variable is true";<br>
+ } else {<br>
+ print "Try again";<br>
+ }<br>
+<br>
+ - NOT -<br>
+<br>
+ if ($var)<br>
+ {<br>
+ print "The variable is true";<br>
+ }<br>
+ else<br>
+ {<br>
+ print "Try again";<br>
+ }<br>
+<br>
+ 3. File Names<br>
+<br>
+ File names for bugzilla code and support documention should be legal across<br>
+ multiple platforms. \ / : * ? " < > and | are all illegal characters for<br>
+ filenames on various platforms. Also, file names should not have spaces in<br>
+ them as they can cause confusion in CVS and other mozilla.org utilities.<br>
+<br>
+ 4. Variable Names<br>
+<br>
+ If a variable is scoped globally ($::variable) its name should be descriptive<br>
+ of what it contains. Local variables can be named a bit looser, provided the<br>
+ context makes their content obvious. For example, $ret could be used as a<br>
+ staging variable for a routine's return value as the line |return $ret;| will<br>
+ make it blatently obvious what the variable holds and most likely be shown<br>
+ on the same screen as |my $ret = "";|.<br>
+<br>
+ 5. Cross Database Compatability<br>
+<br>
+ Bugzilla was originally written to work with MySQL and therefore took advantage<br>
+ of some of its features that aren't contained in other RDBMS software. These<br>
+ should be avoided in all new code. Examples of these features are enums and<br>
+ encrypt().<br>
+<br>
+ 6. Cross Platform Compatability<br>
+<br>
+ While Bugzilla was written to be used on Unix based systems (and Unix/Linux is<br>
+ still the only officially supported platform) there are many who desire/need to<br>
+ run Bugzilla on Microsoft Windows boxes. Whenever possible, we should strive<br>
+ not to make the lives of these people any more complicated and avoid doing things<br>
+ that break Bugzilla's ability to run on multiple operating systems.<br>
+<br>
+ </P
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="quicksearch.html"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="gfdl.html"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>The Quicksearch Utility</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="patches.html"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>GNU Free Documentation License</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file
diff --git a/docs/html/cleanupwork.html b/docs/html/cleanupwork.html
deleted file mode 100644
index d81c9ff58..000000000
--- a/docs/html/cleanupwork.html
+++ /dev/null
@@ -1,155 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Cleaning up after mucking with Bugzilla</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="The Bugzilla Database"
-HREF="database.html"><LINK
-REL="PREVIOUS"
-TITLE="MySQL Permissions & Grant Tables"
-HREF="granttables.html"><LINK
-REL="NEXT"
-TITLE="Bugzilla Variants"
-HREF="variants.html"></HEAD
-><BODY
-CLASS="SECTION"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="granttables.html"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix C. The Bugzilla Database</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="variants.html"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="SECTION"
-><H1
-CLASS="SECTION"
-><A
-NAME="CLEANUPWORK"
->C.4. Cleaning up after mucking with Bugzilla</A
-></H1
-><P
-CLASS="LITERALLAYOUT"
->Contributed by Eric Hanson:<br>
-There are several things, and one trick. There is a small tiny piece of<br>
-documentation I saw once that said something very important.<br>
-1) After pretty much any manual working of the Mysql db, you must<br>
-delete a file in the bugzilla directory: data/versioncache<br>
-Versioncache basically is a way to speed up bugzilla (from what I<br>
-understand). It stores a lot of commonly used information. However,<br>
-this file is refreshed every so often (I can't remember the time<br>
-interval though). So eventually all changes do propogate out, so you<br>
-may see stuff suddenly working.<br>
-2) Assuming that failed, you will also have to check something with the<br>
-checksetup.pl file. It actually is run twice. The first time it<br>
-creates the file: localconfig. You can modify localconfig, (or not if<br>
-you are doing bug_status stuff) or you should delete localconfig and<br>
-rerun your modified checksetup.pl. Since I don't actually see anything<br>
-in localconfig pertaining to bug_status, this point is mainly a FYI.<br>
- </P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="granttables.html"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="variants.html"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->MySQL Permissions & Grant Tables</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="database.html"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Bugzilla Variants</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
diff --git a/docs/html/cmdline.html b/docs/html/cmdline.html
index a7dcdf0da..7a1e1ba44 100644
--- a/docs/html/cmdline.html
+++ b/docs/html/cmdline.html
@@ -4,7 +4,7 @@
>Command-line Bugzilla Queries</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
@@ -71,25 +71,26 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="CMDLINE"
->D.2. Command-line Bugzilla Queries</A
+>D.3. Command-line Bugzilla Queries</A
></H1
><P
-> Users can query Bugzilla from the command line using
- this suite of utilities.
+> Users can query Bugzilla from the command line using this suite
+ of utilities.
</P
><P
> The query.conf file 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"
+ 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
-> 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=".
+> 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=".
</P
><P
> The columlist is taken from the COLUMNLIST environment variable.
@@ -104,12 +105,12 @@ CLASS="COMMAND"
><P
> 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
- <B
+ "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
+>sed -e 's/,/ /g' | wc |
+ awk '{printf $2 "\n"}'</B
>
</P
><P
@@ -134,15 +135,15 @@ TYPE="a"
><P
> <TT
CLASS="COMPUTEROUTPUT"
-> <TT
+> <TT
CLASS="PROMPT"
>bash$</TT
->
- <B
+> <B
CLASS="COMMAND"
->wget -O query.conf 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26157'</B
->
- </TT
+>wget -O
+ query.conf
+ 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26157'</B
+> </TT
>
</P
></LI
@@ -150,15 +151,15 @@ CLASS="COMMAND"
><P
> <TT
CLASS="COMPUTEROUTPUT"
-> <TT
+> <TT
CLASS="PROMPT"
>bash$</TT
->
- <B
+> <B
CLASS="COMMAND"
->wget -O buglist 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26944'</B
->
- </TT
+>wget -O
+ buglist
+ 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26944'</B
+> </TT
>
</P
></LI
@@ -166,15 +167,15 @@ CLASS="COMMAND"
><P
> <TT
CLASS="COMPUTEROUTPUT"
-> <TT
+> <TT
CLASS="PROMPT"
>bash#</TT
->
- <B
+> <B
CLASS="COMMAND"
->wget -O bugs 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26215'</B
->
- </TT
+>wget -O
+ bugs
+ 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26215'</B
+> </TT
>
</P
></LI
diff --git a/docs/html/contributors.html b/docs/html/contributors.html
index bcc6b29b2..6b87af19c 100644
--- a/docs/html/contributors.html
+++ b/docs/html/contributors.html
@@ -4,7 +4,7 @@
>Contributors</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
@@ -74,15 +74,12 @@ NAME="CONTRIBUTORS"
>1.6. Contributors</A
></H1
><P
-> Thanks go to these people for significant contributions
- to this documentation (in no particular order):
+> Thanks go to these people for significant contributions to this
+ documentation (in no particular order):
</P
><P
-> Zach Lipton (significant textual contributions),
- Andrew Pearson,
- Spencer Smith,
- Eric Hanson,
- Kevin Brannen,
+> Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen, Ron
+ Teitelbaum, Jacob Steenhagen, Joe Robins
</P
></DIV
><DIV
diff --git a/docs/html/conventions.html b/docs/html/conventions.html
index cd598f8f2..c5bf9dcbc 100644
--- a/docs/html/conventions.html
+++ b/docs/html/conventions.html
@@ -4,7 +4,7 @@
>Document Conventions</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
@@ -16,8 +16,8 @@ REL="PREVIOUS"
TITLE="Translations"
HREF="translations.html"><LINK
REL="NEXT"
-TITLE="Installing Bugzilla"
-HREF="installation.html"></HEAD
+TITLE="Using Bugzilla"
+HREF="using.html"></HEAD
><BODY
CLASS="SECTION"
BGCOLOR="#FFFFFF"
@@ -57,7 +57,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
-HREF="installation.html"
+HREF="using.html"
>Next</A
></TD
></TR
@@ -79,7 +79,7 @@ NAME="CONVENTIONS"
><DIV
CLASS="INFORMALTABLE"
><A
-NAME="AEN117"
+NAME="AEN129"
></A
><P
></P
@@ -113,18 +113,20 @@ CLASS="CAUTION"
></P
><TABLE
CLASS="CAUTION"
-BORDER="1"
WIDTH="100%"
+BORDER="0"
><TR
><TD
+WIDTH="25"
ALIGN="CENTER"
-><B
->Caution</B
-></TD
-></TR
-><TR
+VALIGN="TOP"
+><IMG
+SRC="../images/caution.gif"
+HSPACE="5"
+ALT="Caution"></TD
><TD
ALIGN="LEFT"
+VALIGN="TOP"
><P
>Warnings.</P
></TD
@@ -143,13 +145,29 @@ ALIGN="LEFT"
VALIGN="TOP"
><DIV
CLASS="TIP"
-><BLOCKQUOTE
+><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
-><B
->Tip: </B
>Hint.</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
></TD
></TR
@@ -163,13 +181,29 @@ ALIGN="LEFT"
VALIGN="TOP"
><DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><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
-><B
->Note: </B
>Note.</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
></TD
></TR
@@ -187,18 +221,20 @@ CLASS="WARNING"
></P
><TABLE
CLASS="WARNING"
-BORDER="1"
WIDTH="100%"
+BORDER="0"
><TR
><TD
+WIDTH="25"
ALIGN="CENTER"
-><B
->Warning</B
-></TD
-></TR
-><TR
+VALIGN="TOP"
+><IMG
+SRC="../images/warning.gif"
+HSPACE="5"
+ALT="Warning"></TD
><TD
ALIGN="LEFT"
+VALIGN="TOP"
><P
>Warning.</P
></TD
@@ -337,6 +373,8 @@ BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
+><FONT
+COLOR="#000000"
><PRE
CLASS="PROGRAMLISTING"
><TT
@@ -346,6 +384,7 @@ CLASS="SGMLTAG"
CLASS="SGMLTAG"
></para></TT
></PRE
+></FONT
></TD
></TR
></TABLE
@@ -388,7 +427,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
-HREF="installation.html"
+HREF="using.html"
>Next</A
></TD
></TR
@@ -410,7 +449,7 @@ HREF="about.html"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
->Installing Bugzilla</TD
+>Using Bugzilla</TD
></TR
></TABLE
></DIV
diff --git a/docs/html/copyright.html b/docs/html/copyright.html
index dfae5da01..f480206d2 100644
--- a/docs/html/copyright.html
+++ b/docs/html/copyright.html
@@ -4,7 +4,7 @@
>Copyright Information</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
@@ -74,7 +74,7 @@ NAME="COPYRIGHT"
>1.2. Copyright Information</A
></H1
><A
-NAME="AEN57"
+NAME="AEN70"
></A
><TABLE
BORDER="0"
@@ -91,11 +91,13 @@ VALIGN="TOP"
WIDTH="80%"
VALIGN="TOP"
><P
-> Permission is granted to copy, distribute and/or modify this document under thei
- terms of the GNU Free Documentation License, Version 1.1 or any later version published
- by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and
- with no Back-Cover Texts. A copy of the license is included in the section entitled
- "GNU Free Documentation LIcense".
+> Permission is granted to copy, distribute and/or modify this
+ document under the terms of the GNU Free Documentation
+ License, Version 1.1 or any later version published by the
+ Free Software Foundation; with no Invariant Sections, no
+ Front-Cover Texts, and with no Back-Cover Texts. A copy of
+ the license is included in the section entitled "GNU Free
+ Documentation LIcense".
</P
></TD
><TD
@@ -118,14 +120,9 @@ WIDTH="10%"
></TR
></TABLE
><P
-> If you have any questions regarding this document, its' copyright, or publishing this
- document in non-electronic form, please contact <TT
-CLASS="EMAIL"
-><<A
-HREF="mailto:barnboy@trilobyte.net"
->barnboy@trilobyte.net</A
->></TT
->
+> If you have any questions regarding this document, its
+ copyright, or publishing this document in non-electronic form,
+ please contact Matthew P. Barnson.
</P
></DIV
><DIV
diff --git a/docs/html/credits.html b/docs/html/credits.html
index 41cd51cfc..1c177276b 100644
--- a/docs/html/credits.html
+++ b/docs/html/credits.html
@@ -4,7 +4,7 @@
>Credits</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
@@ -74,10 +74,10 @@ NAME="CREDITS"
>1.5. Credits</A
></H1
><P
-> The people listed below have made enormous contributions to the creation
- of this Guide, through their dedicated hacking efforts,
- numerous e-mail and IRC support sessions,
- and overall excellent contribution to the Bugzilla community:
+> The people listed below have made enormous contributions to the
+ creation of this Guide, through their dedicated hacking efforts,
+ numerous e-mail and IRC support sessions, and overall excellent
+ contribution to the Bugzilla community:
</P
><P
> <A
@@ -85,44 +85,43 @@ HREF="mailto://terry@mozilla.org"
TARGET="_top"
>Terry Weissman</A
>
- for initially converting Bugzilla from BugSplat!
- and writing the README upon which this documentation is largely based.
+ 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
+>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
+> 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
+> 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
+> 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.
+> netscape.public.mozilla.webtools</A
+> newsgroup. Without your discussions, insight, suggestions, and patches, this could never have happened.
</P
></DIV
><DIV
diff --git a/docs/html/cvs.html b/docs/html/cvs.html
index fc4a7cacf..47dbc8940 100644
--- a/docs/html/cvs.html
+++ b/docs/html/cvs.html
@@ -4,7 +4,7 @@
>CVS</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
@@ -74,7 +74,37 @@ NAME="CVS"
>5.2. CVS</A
></H1
><P
->We need CVS integration information</P
+>CVS integration is best accomplished, at this point, using
+ the Bugzilla Email Gateway. There have been some files
+ submitted to allow greater CVS integration, but we need to make
+ certain that Bugzilla is not tied into one particular software
+ management package.</P
+><P
+> Follow the instructions in the FAQ 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
+> There is also a 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
+>, under the
+ <SPAN
+CLASS="QUOTE"
+>"cvszilla"</SPAN
+> link.
+ </P
></DIV
><DIV
CLASS="NAVFOOTER"
diff --git a/docs/html/database.html b/docs/html/database.html
index 008c3ec65..25054e2e8 100644
--- a/docs/html/database.html
+++ b/docs/html/database.html
@@ -4,7 +4,7 @@
>The Bugzilla Database</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
@@ -91,22 +91,34 @@ HREF="dbdoc.html"
HREF="granttables.html"
>MySQL Permissions & Grant Tables</A
></DT
-><DT
->C.4. <A
-HREF="cleanupwork.html"
->Cleaning up after mucking with Bugzilla</A
-></DT
></DL
></DIV
><DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><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
-><B
->Note: </B
->This document really needs to be updated with more fleshed out information about primary keys, interrelationships, and maybe some nifty tables to document dependencies. Any takers?</P
-></BLOCKQUOTE
+> 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
></DIV
><DIV
diff --git a/docs/html/dbaseintegrity.html b/docs/html/dbaseintegrity.html
deleted file mode 100644
index 4ddcd0bed..000000000
--- a/docs/html/dbaseintegrity.html
+++ /dev/null
@@ -1,179 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Database Integrity</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="The Future of Bugzilla"
-HREF="future.html"><LINK
-REL="PREVIOUS"
-TITLE="Bug Issues"
-HREF="bugprobs.html"><LINK
-REL="NEXT"
-TITLE="Bugzilla 3.0"
-HREF="bz30.html"></HEAD
-><BODY
-CLASS="SECTION"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="bugprobs.html"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 6. The Future of Bugzilla</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="bz30.html"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="SECTION"
-><H1
-CLASS="SECTION"
-><A
-NAME="DBASEINTEGRITY"
->6.5. Database Integrity</A
-></H1
-><P
-><P
-CLASS="LITERALLAYOUT"
->Bugzilla could be more proactive in detecting suboptimal situations and<br>
-prevent them or whine about them.<br>
-<br>
-1. Bugzilla Crime #1: Marking A Bug Fixed With Unresolved Dependencies<br>
-<br>
-It can't be marked fixed with unresolved dependencies. Either mark it<br>
-INVALID (tracking bugs), fix the dependencies at the same time, or<br>
-resolve the blockers.<br>
-<br>
-See "http://bugzilla.mozilla.org/show_bug.cgi?id=24496".<br>
-<br>
-2. Keyword Restrictions<br>
-<br>
-Some keywords should only apply in certain circumstances, eg beta1 =><br>
-Milestone <<br>
-M14, css1 => Component = Style System are possibilities. See<br>
-"http://bugzilla.mozilla.org/show_bug.cgi?id=26940".<br>
-<br>
-3. Whine About Old Votes<br>
-<br>
-Old votes can just sit on resolved bugs. This is problematic with<br>
-duplicates especially. Automatic transferral/removal is not<br>
-appropriate since bugs can be reopened, but a whining solution might<br>
-work. See "http://bugzilla.mozilla.org/show_bug.cgi?id=27553".<br>
-<br>
-4. Whine And Warn About Milestone Mismatches<br>
-<br>
-Here's a fun one. Bug X (M17) depends on Bug Y (M15). Bug Y gets moved<br>
-out to M19. The notification to the assignee of Bug X gets ignored (of<br>
-course) and Bug X is now due to be fixed before one of its blockers.<br>
-<br>
-Warnings about this when it is detected as well as whining about it in<br>
-email would help bring these issues to the attention of people sooner.<br>
-<br>
-Note that this would be less of a problem if we didn't have so many<br>
-tracking bugs since they aren't updated that often and often have this<br>
-problem.<br>
-<br>
-See "http://bugzilla.mozilla.org/show_bug.cgi?id=16743".</P
-></P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="bugprobs.html"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="bz30.html"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Bug Issues</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="future.html"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Bugzilla 3.0</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
diff --git a/docs/html/dbdoc.html b/docs/html/dbdoc.html
index d3f4ec024..44ea6aa60 100644
--- a/docs/html/dbdoc.html
+++ b/docs/html/dbdoc.html
@@ -4,7 +4,7 @@
>MySQL Bugzilla Database Introduction</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
@@ -74,201 +74,263 @@ NAME="DBDOC"
>C.2. MySQL Bugzilla Database Introduction</A
></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"
+><H2
+CLASS="SECTION"
+><A
+NAME="AEN2331"
+>C.2.1. Bugzilla Database Basics</A
+></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
+> 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
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+> To connect to your database:
+ </P
+><P
+> <TT
+CLASS="PROMPT"
+>bash#</TT
+><B
+CLASS="COMMAND"
+>mysql</B
+><TT
+CLASS="PARAMETER"
+><I
+>-u root</I
+></TT
+>
+ </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 MySQL searchable documentation at
+ http://www.mysql.com/php/manual.php3?section=Privilege_system .
+ </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
+> file
+ for your Bugzilla database, type:</P
+><P
+><TT
+CLASS="PROMPT"
+>mysql</TT
+><B
+CLASS="COMMAND"
+>use bugs;</B
+></P
+><DIV
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="90%"
+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
+>Don't forget the <SPAN
+CLASS="QUOTE"
+>";"</SPAN
+> at the end of
+ each line, or you'll be kicking yourself later.</P
+></TD
+></TR
+></TABLE
+></DIV
+></LI
+></OL
+>
+ </P
+><DIV
+CLASS="SECTION"
+><H3
+CLASS="SECTION"
+><A
+NAME="AEN2360"
+>C.2.1.1. Bugzilla Database Tables</A
+></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
+><B
+CLASS="COMMAND"
+>show tables from bugs;</B
+></P
+><P
+>you'll be able to see all the
+ <SPAN
+CLASS="QUOTE"
+>"spreadsheets"</SPAN
+> (tables) in your database. It
+ is similar to a file system, only faster and more robust for
+ certain types of operations.</P
+><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
+><P
CLASS="LITERALLAYOUT"
><br>
-Contributor(s): Matthew P. Barnson (mbarnson@excitehome.net)<br>
-<br>
-Last update: May 16, 2000<br>
-<br>
-Changes:<br>
-Version 1.0: Initial public release (May 16, 2000)<br>
-<br>
-Maintainer: Matthew P. Barnson (mbarnson@excitehome.net)<br>
-<br>
-<br>
-===<br>
-Table Of Contents<br>
-===<br>
-<br>
-FOREWORD<br>
-INTRODUCTION<br>
-THE BASICS<br>
-THE TABLES<br>
-THE DETAILS<br>
-<br>
-<br>
-<br>
-===<br>
-FOREWORD<br>
-===<br>
-<br>
- This information comes straight from my life. I was forced to learn how<br>
-Bugzilla organizes database because of nitpicky requests from users for tiny<br>
-changes in wording, rather than having people re-educate themselves or<br>
-figure out how to work our procedures around the tool. It sucks, but it can<br>
-and will happen to you, so learn how the schema works and deal with it when it<br>
-comes.<br>
-<br>
- I'm sorry this version is plain text. I can whip this info out a lot faster<br>
-if I'm not concerned about complex formatting. I'll get it into sgml for easy<br>
-portability as time permits.<br>
-<br>
- The Bugzilla Database Schema has a home! In addition to availability via CVS<br>
-and released versions 2.12 and higher of Bugzilla, you can find the latest &<br>
-greatest version of the Bugzilla Database Schema at<br>
-http://www.trilobyte.net/barnsons/. This is a living document; please be sure<br>
-you are up-to-date with the latest version before mirroring.<br>
-<br>
- The Bugzilla Database Schema is designed to provide vital information<br>
-regarding the structure of the MySQL database. Where appropriate, this<br>
-document will refer to URLs rather than including documents in their entirety<br>
-to ensure completeness even should this paper become out of date.<br>
-<br>
- This document is not maintained by Netscape or Netscape employees, so please<br>
-do not contact them regarding errors or omissions contained herein. Please<br>
-direct all questions, comments, updates, flames, etc. to Matthew P. Barnson<br>
-mbarnson@excitehome.net) (barnboy or barnhome on irc.mozilla.org in<br>
-#mozwebtools).<br>
-<br>
- I'm sure I've made some glaring errors or omissions in this paper -- please<br>
-email me corrections or post corrections to the<br>
-netscape.public.mozilla.webtools newsgroup.<br>
-<br>
-<br>
-<br>
-===<br>
-INTRODUCTION<br>
-===<br>
-<br>
-<br>
-<br>
- So, here you are with your brand-new installation of Bugzilla. You've got<br>
-MySQL set up, Apache working right, Perl DBI and DBD talking to the database<br>
-flawlessly. Maybe you've even entered a few test bugs to make sure email's<br>
-working; people seem to be notified of new bugs and changes, and you can<br>
-enter and edit bugs to your heart's content. Perhaps you've gone through the<br>
-trouble of setting up a gateway for people to submit bugs to your database via<br>
-email, have had a few people test it, and received rave reviews from your beta<br>
-testers.<br>
-<br>
- What's the next thing you do? Outline a training strategy for your<br>
-development team, of course, and bring them up to speed on the new tool you've<br>
-labored over for hours.<br>
-<br>
- Your first training session starts off very well! You have a captive<br>
-audience which seems enraptured by the efficiency embodied in this thing called<br>
-"Bugzilla". You are caught up describing the nifty features, how people can<br>
-save favorite queries in the database, set them up as headers and footers on<br>
-their pages, customize their layouts, generate reports, track status with<br>
-greater efficiency than ever before, leap tall buildings with a single bound<br>
-and rescue Jane from the clutches of Certain Death!<br>
-<br>
- But Certain Death speaks up -- a tiny voice, from the dark corners of the<br>
-conference room. "I have a concern," the voice hisses from the darkness,<br>
-"about the use of the word 'verified'.<br>
-<br>
- The room, previously filled with happy chatter, lapses into reverential<br>
-silence as Certain Death (better known as the Vice President of Software<br>
-Engineering) continues. "You see, for two years we've used the word 'verified'<br>
-to indicate that a developer or quality assurance engineer has confirmed that,<br>
-in fact, a bug is valid. I don't want to lose two years of training to a<br>
-new software product. You need to change the bug status of 'verified' to<br>
-'approved' as soon as possible. To avoid confusion, of course."<br>
-<br>
- Oh no! Terror strikes your heart, as you find yourself mumbling "yes, yes, I<br>
-don't think that would be a problem," You review the changes with Certain<br>
-Death, and continue to jabber on, "no, it's not too big a change. I mean, we<br>
-have the source code, right? You know, 'Use the Source, Luke' and all that...<br>
-no problem," All the while you quiver inside like a beached jellyfish bubbling,<br>
-burbling, and boiling on a hot Jamaican sand dune...<br>
-<br>
- Thus begins your adventure into the heart of Bugzilla. You've been forced<br>
-to learn about non-portable enum() fields, varchar columns, and tinyint<br>
-definitions. The Adventure Awaits You!<br>
-<br>
-<br>
-<br>
-===<br>
-The Basics<br>
-===<br>
-<br>
- If you were like me, at this point you're totally clueless about the<br>
-internals of MySQL, and if it weren't for this executive order from the Vice<br>
-President you couldn't care less about the difference between a "bigint" and a<br>
-"tinyint" entry in MySQL. I'd refer you first to the MySQL documentation,<br>
-available at http://www.mysql.com/doc.html, but that's mostly a confusing<br>
-morass of high-level database jargon. Here are the basics you need to know<br>
-about the database to proceed:<br>
-<br>
-1. To connect to your database, type "mysql -u root" at the command prompt as<br>
-any user. If this works without asking you for a password, SHAME ON YOU! You<br>
-should have locked your security down like the README told you to. You can<br>
-find details on locking down your database in the Bugzilla FAQ in this<br>
-directory (under "Security"), or more robust security generalities in the<br>
-MySQL searchable documentation at<br>
-http://www.mysql.com/php/manual.php3?section=Privilege_system .<br>
-<br>
-2. You should now be at a prompt that looks like this:<br>
-<br>
-mysql><br>
- <br>
- At the prompt, if "bugs" is the name of your Bugzilla database, type:<br>
- <br>
-mysql> use bugs;<br>
- <br>
- (don't forget the ";" at the end of each line, or you'll be kicking yourself<br>
-all the way through this documentation)<br>
- Young Grasshopper, you are now ready for the unveiling of the Bugzilla<br>
-database, in the next section...<br>
-<br>
-<br>
-<br>
-===<br>
-THE TABLES<br>
-===<br>
-<br>
- Imagine your MySQL database as a series of spreadsheets, and you won't be too<br>
-far off. If you use this command:<br>
-<br>
-mysql> show tables from bugs;<br>
- <br>
- you'll be able to see all the "spreadsheets" (tables) in your database. Cool,<br>
-huh? It's kinda' like a filesystem, only much faster and more robust. Come<br>
-on, I'll show you more!<br>
-<br>
- From the command issued above, you should now have some output that looks<br>
-like this:<br>
-<br>
-+-------------------+<br>
-| Tables in bugs |<br>
-+-------------------+<br>
-| attachments |<br>
-| bugs |<br>
-| bugs_activity |<br>
-| cc |<br>
-| components |<br>
-| dependencies |<br>
-| fielddefs |<br>
-| groups |<br>
-| keyworddefs |<br>
-| keywords |<br>
-| logincookies |<br>
-| longdescs |<br>
-| milestones |<br>
-| namedqueries |<br>
-| products |<br>
-| profiles |<br>
-| profiles_activity |<br>
-| shadowlog |<br>
-| versions |<br>
-| votes |<br>
-| watch |<br>
-+-------------------+<br>
-<br>
-<br>
- If it doesn't look quite the same, that probably means it's time to<br>
-update this documentation :)<br>
-<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>
@@ -445,7 +507,9 @@ LINKS<br>
Great MySQL tutorial site:<br>
http://www.devshed.com/Server_Side/MySQL/<br>
<br>
- </P
+ </P
+></DIV
+></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
diff --git a/docs/html/dbschema.html b/docs/html/dbschema.html
index 0f069365c..36f51014d 100644
--- a/docs/html/dbschema.html
+++ b/docs/html/dbschema.html
@@ -4,7 +4,7 @@
>Database Schema Chart</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
@@ -78,7 +78,7 @@ NAME="DBSCHEMA"
CLASS="MEDIAOBJECT"
><P
><IMG
-SRC="dbschema.jpg"
+SRC="../images/dbschema.jpg"
ALT="Database Relationships"
></IMG
><DIV
diff --git a/docs/html/disclaimer.html b/docs/html/disclaimer.html
index fb8e1bbaa..e9874f9f4 100644
--- a/docs/html/disclaimer.html
+++ b/docs/html/disclaimer.html
@@ -4,7 +4,7 @@
>Disclaimer</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
@@ -77,34 +77,44 @@ NAME="DISCLAIMER"
> No liability for the contents of this document can be accepted.
Use the concepts, examples, and other content at your own risk.
As this is a new edition of this document, there may be errors
- and inaccuracies that may damage your system. Use of this document
- may cause your girlfriend to leave you, your cats to pee on your
- furniture and clothing, your computer to cease functioning, your
- boss to fire you, and global thermonuclear war. Proceed with caution.
+ and inaccuracies that may damage your system. Use of this
+ document may cause your girlfriend to leave you, your cats to
+ pee on your furniture and clothing, your computer to cease
+ functioning, your boss to fire you, and global thermonuclear
+ war. Proceed with caution.
</P
><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.
- In particular, I like to put down Microsoft(tm). Live with it.
+> 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".
- Use GNU/Linux. Love it. Bathe with it. It is life and happiness.
- I endorse it wholeheartedly and encourage you to do the same.
+> Naming of particular products or brands should not be seen as
+ endorsements, with the exception of the term "GNU/Linux". I
+ 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. Heaven knows
- it's saved my bacon time after time; if you implement any suggestion in
- this Guide, implement this one!
+> You are strongly recommended to make a backup of your system
+ before installing Bugzilla and at regular intervals thereafter.
+ Heaven knows it's saved my bacon time after time; if you
+ implement any suggestion in this Guide, implement this one!
</P
><P
-> Bugzilla has not undergone a complete security review.
- Security holes probably exist in the code.
- Great care should be taken both in the installation and usage of this software.
- Carefully consider the implications of installing other network services with Bugzilla.
+> 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 insure
+ your security needs are met.
</P
></DIV
><DIV
diff --git a/docs/html/downloadlinks.html b/docs/html/downloadlinks.html
index 897c66157..a6f289a75 100644
--- a/docs/html/downloadlinks.html
+++ b/docs/html/downloadlinks.html
@@ -4,7 +4,7 @@
>Software Download Links</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
@@ -90,9 +90,9 @@ TARGET="_top"
</P
><P
> MySQL: <A
-HREF="http://www.mysql.org/"
+HREF="http://www.mysql.com/"
TARGET="_top"
->http://www.mysql.org/</A
+>http://www.mysql.com/</A
>
</P
><P
diff --git a/docs/html/errata.html b/docs/html/errata.html
new file mode 100644
index 000000000..4782c9758
--- /dev/null
+++ b/docs/html/errata.html
@@ -0,0 +1,273 @@
+<HTML
+><HEAD
+><TITLE
+>ERRATA</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide"
+HREF="index.html"><LINK
+REL="UP"
+TITLE="Installation"
+HREF="installation.html"><LINK
+REL="PREVIOUS"
+TITLE="Installation"
+HREF="installation.html"><LINK
+REL="NEXT"
+TITLE="Step-by-step Install"
+HREF="stepbystep.html"></HEAD
+><BODY
+CLASS="SECTION"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>The Bugzilla Guide</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="installation.html"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Chapter 3. Installation</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="stepbystep.html"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="SECTION"
+><H1
+CLASS="SECTION"
+><A
+NAME="ERRATA"
+>3.1. ERRATA</A
+></H1
+><P
+>Here are some miscellaneous notes about possible issues you
+ main run into when you begin your Bugzilla installation.
+ Reference platforms for Bugzilla installation are Redhat Linux
+ 7.2, Linux-Mandrake 8.0, and Solaris 8.</P
+><P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+> If you are installing Bugzilla on S.u.S.e. Linux, or some
+ other distributions with <SPAN
+CLASS="QUOTE"
+>"paranoid"</SPAN
+> security
+ options, it is possible that the checksetup.pl script may fail
+ with the error: <SPAN
+CLASS="ERRORNAME"
+>cannot chdir(/var/spool/mqueue):
+ Permission denied</SPAN
+> This is because your
+ <TT
+CLASS="FILENAME"
+>/var/spool/mqueue</TT
+> directory has a mode of
+ <SPAN
+CLASS="QUOTE"
+>"drwx------"</SPAN
+>. Type <B
+CLASS="COMMAND"
+>chmod 755
+ <TT
+CLASS="FILENAME"
+>/var/spool/mqueue</TT
+></B
+> as root to
+ fix this problem.
+ </TD
+></TR
+><TR
+><TD
+> Bugzilla may be installed on Macintosh OS X (10), which is a
+ unix-based (BSD) operating system. Everything required for
+ Bugzilla on OS X will install cleanly, but the optional GD
+ perl module which is used for bug charting requires some
+ additional setup for installation. Please see the Mac OS X
+ installation section below for details
+ </TD
+></TR
+><TR
+><TD
+> Release Notes for Bugzilla 2.14 are available at
+ <TT
+CLASS="FILENAME"
+>docs/rel_notes.txt</TT
+> in your Bugzilla
+ source distribution.
+ </TD
+></TR
+><TR
+><TD
+> The preferred documentation for Bugzilla is available in
+ docs/, with a variety of document types available. Please
+ refer to these documents when installing, configuring, and
+ maintaining your Bugzilla installation.
+ </TD
+></TR
+></TBODY
+></TABLE
+><P
+></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
+> Bugzilla is not a package where you can just plop it in a directory,
+ twiddle a few things, and you're off. Installing Bugzilla assumes you
+ know your variant of UNIX or Microsoft Windows well, are familiar with the
+ command line, and are comfortable compiling and installing a plethora
+ of third-party utilities. To install Bugzilla on Win32 requires
+ fair Perl proficiency, and if you use a webserver other than Apache you
+ should be intimately familiar with the security mechanisms and CGI
+ environment thereof.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+><DIV
+CLASS="WARNING"
+><P
+></P
+><TABLE
+CLASS="WARNING"
+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
+> Bugzilla has not undergone a complete security review. Security holes
+ may exist in the code. Great care should be taken both in the installation
+ and usage of this software. Carefully consider the implications of
+ installing other network services with Bugzilla.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="installation.html"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="stepbystep.html"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Installation</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="installation.html"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Step-by-step Install</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file
diff --git a/docs/html/faq.html b/docs/html/faq.html
index 4a2bb7505..eea2d6b3d 100644
--- a/docs/html/faq.html
+++ b/docs/html/faq.html
@@ -4,14 +4,14 @@
>The Bugzilla FAQ</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="PREVIOUS"
-TITLE="Bugzilla 3.0"
-HREF="bz30.html"><LINK
+TITLE="SourceForge"
+HREF="variant_sourceforge.html"><LINK
REL="NEXT"
TITLE="Software Download Links"
HREF="downloadlinks.html"></HEAD
@@ -41,7 +41,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
-HREF="bz30.html"
+HREF="variant_sourceforge.html"
>Prev</A
></TD
><TD
@@ -81,63 +81,63 @@ HREF="faq.html#FAQ_GENERAL"
><DL
><DT
>A.1.1. <A
-HREF="faq.html#AEN1302"
+HREF="faq.html#AEN1713"
> Where can I find information about Bugzilla?</A
></DT
><DT
>A.1.2. <A
-HREF="faq.html#AEN1308"
+HREF="faq.html#AEN1719"
> What license is Bugzilla distributed under?
</A
></DT
><DT
>A.1.3. <A
-HREF="faq.html#AEN1314"
+HREF="faq.html#AEN1725"
> How do I get commercial support for Bugzilla?
</A
></DT
><DT
>A.1.4. <A
-HREF="faq.html#AEN1321"
+HREF="faq.html#AEN1732"
> What major companies or projects are currently using Bugzilla
for bug-tracking?
</A
></DT
><DT
>A.1.5. <A
-HREF="faq.html#AEN1346"
+HREF="faq.html#AEN1757"
> Who maintains Bugzilla?
</A
></DT
><DT
>A.1.6. <A
-HREF="faq.html#AEN1351"
+HREF="faq.html#AEN1763"
> How does Bugzilla stack up against other bug-tracking databases?
</A
></DT
><DT
>A.1.7. <A
-HREF="faq.html#AEN1358"
+HREF="faq.html#AEN1770"
> How do I change my user name in Bugzilla?
</A
></DT
><DT
>A.1.8. <A
-HREF="faq.html#AEN1363"
+HREF="faq.html#AEN1775"
> Why doesn't Bugzilla offer this or that feature or compatability
with this other tracking software?
</A
></DT
><DT
>A.1.9. <A
-HREF="faq.html#AEN1370"
+HREF="faq.html#AEN1782"
> Why MySQL? I'm interested in seeing Bugzilla run on
Oracle/Sybase/Msql/PostgreSQL/MSSQL?
</A
></DT
><DT
>A.1.10. <A
-HREF="faq.html#AEN1388"
+HREF="faq.html#AEN1800"
> Why do the scripts say "/usr/bonsaitools/bin/perl" instead of
"/usr/bin/perl" or something else?
</A
@@ -153,19 +153,19 @@ HREF="faq.html#FAQ_REDHAT"
><DL
><DT
>A.2.1. <A
-HREF="faq.html#AEN1405"
+HREF="faq.html#AEN1817"
> What about Red Hat Bugzilla?
</A
></DT
><DT
>A.2.2. <A
-HREF="faq.html#AEN1413"
+HREF="faq.html#AEN1825"
> What are the primary benefits of Red Hat Bugzilla?
</A
></DT
><DT
>A.2.3. <A
-HREF="faq.html#AEN1441"
+HREF="faq.html#AEN1853"
> What's the current status of Red Hat Bugzilla?
</A
></DT
@@ -180,20 +180,8 @@ HREF="faq.html#FAQ_LOKI"
><DL
><DT
>A.3.1. <A
-HREF="faq.html#AEN1457"
-> What about Loki Bugzilla?
- </A
-></DT
-><DT
->A.3.2. <A
-HREF="faq.html#AEN1464"
-> Who maintains Fenris (Loki Bugzilla) now?
- </A
-></DT
-><DT
->A.3.3. <A
-HREF="faq.html#AEN1469"
->
+HREF="faq.html#AEN1866"
+> What is Loki Bugzilla (Fenris)?
</A
></DT
></DL
@@ -207,41 +195,41 @@ HREF="faq.html#FAQ_PHB"
><DL
><DT
>A.4.1. <A
-HREF="faq.html#AEN1477"
+HREF="faq.html#AEN1877"
> Is Bugzilla web-based or do you have to have specific software or
specific operating system on your machine?
</A
></DT
><DT
>A.4.2. <A
-HREF="faq.html#AEN1482"
+HREF="faq.html#AEN1882"
> Has anyone you know of already done any Bugzilla integration with
Perforce (SCM software)?
</A
></DT
><DT
>A.4.3. <A
-HREF="faq.html#AEN1487"
+HREF="faq.html#AEN1887"
> Does Bugzilla allow the user to track multiple projects?
</A
></DT
><DT
>A.4.4. <A
-HREF="faq.html#AEN1492"
+HREF="faq.html#AEN1892"
> If I am on many projects, and search for all bugs assigned to me, will
Bugzilla list them for me and allow me to sort by project, severity etc?
</A
></DT
><DT
>A.4.5. <A
-HREF="faq.html#AEN1497"
+HREF="faq.html#AEN1897"
> Does Bugzilla allow attachments (text, screenshots, urls etc)? If yes,
are there any that are NOT allowed?
</A
></DT
><DT
>A.4.6. <A
-HREF="faq.html#AEN1502"
+HREF="faq.html#AEN1902"
> Does Bugzilla allow us to define our own priorities and levels? Do we
have complete freedom to change the labels of fields and format of them, and
the choice of acceptable values?
@@ -249,43 +237,51 @@ HREF="faq.html#AEN1502"
></DT
><DT
>A.4.7. <A
-HREF="faq.html#AEN1507"
+HREF="faq.html#AEN1909"
+> The index.html page doesn't show the footer. It's really annoying to have
+ to go to the querypage just to check my "my bugs" link. How do I get a footer
+ on static HTML pages?
+ </A
+></DT
+><DT
+>A.4.8. <A
+HREF="faq.html#AEN1931"
> Does Bugzilla provide any reporting features, metrics, graphs, etc? You
know, the type of stuff that management likes to see. :)
</A
></DT
><DT
->A.4.8. <A
-HREF="faq.html#AEN1515"
+>A.4.9. <A
+HREF="faq.html#AEN1939"
> Is there email notification and if so, what do you see when you get an
email? Do you see bug number and title or is it only the number?
</A
></DT
><DT
->A.4.9. <A
-HREF="faq.html#AEN1520"
+>A.4.10. <A
+HREF="faq.html#AEN1944"
> Can email notification be set up to send to multiple
people, some on the To List, CC List, BCC List etc?
</A
></DT
><DT
->A.4.10. <A
-HREF="faq.html#AEN1525"
+>A.4.11. <A
+HREF="faq.html#AEN1949"
> If there is email notification, do users have to have any particular
type of email application?
</A
></DT
><DT
->A.4.11. <A
-HREF="faq.html#AEN1532"
+>A.4.12. <A
+HREF="faq.html#AEN1956"
> If I just wanted to track certain bugs, as they go through life, can I
set it up to alert me via email whenever that bug changes, whether it be
owner, status or description etc.?
</A
></DT
><DT
->A.4.12. <A
-HREF="faq.html#AEN1537"
+>A.4.13. <A
+HREF="faq.html#AEN1961"
> 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
@@ -293,56 +289,48 @@ HREF="faq.html#AEN1537"
</A
></DT
><DT
->A.4.13. <A
-HREF="faq.html#AEN1545"
-> Does Bugzilla allow fields to be added, changed or deleted? If I want to
- customize the bug submission form to meet our needs, can I do that using our
- terminology?
- </A
-></DT
-><DT
>A.4.14. <A
-HREF="faq.html#AEN1550"
+HREF="faq.html#AEN1969"
> Has anyone converted Bugzilla to another language to be used in other
countries? Is it localizable?
</A
></DT
><DT
>A.4.15. <A
-HREF="faq.html#AEN1555"
+HREF="faq.html#AEN1974"
> Can a user create and save reports? Can they do this in Word format?
Excel format?
</A
></DT
><DT
>A.4.16. <A
-HREF="faq.html#AEN1560"
+HREF="faq.html#AEN1979"
> Can a user re-run a report with a new project, same query?
</A
></DT
><DT
>A.4.17. <A
-HREF="faq.html#AEN1565"
+HREF="faq.html#AEN1984"
> Can a user modify an existing report and then save it into another name?
</A
></DT
><DT
>A.4.18. <A
-HREF="faq.html#AEN1570"
+HREF="faq.html#AEN1989"
> Does Bugzilla have the ability to search by word, phrase, compound
search?
</A
></DT
><DT
>A.4.19. <A
-HREF="faq.html#AEN1575"
+HREF="faq.html#AEN1994"
> Can the admin person establish separate group and individual user
privileges?
</A
></DT
><DT
>A.4.20. <A
-HREF="faq.html#AEN1580"
+HREF="faq.html#AEN1999"
> Does Bugzilla provide record locking when there is simultaneous access
to the same bug? Does the second person get a notice that the bug is in use
or how are they notified?
@@ -350,19 +338,19 @@ HREF="faq.html#AEN1580"
></DT
><DT
>A.4.21. <A
-HREF="faq.html#AEN1585"
+HREF="faq.html#AEN2004"
> Are there any backup features provided?
</A
></DT
><DT
>A.4.22. <A
-HREF="faq.html#AEN1591"
+HREF="faq.html#AEN2010"
> Can users be on the system while a backup is in progress?
</A
></DT
><DT
>A.4.23. <A
-HREF="faq.html#AEN1596"
+HREF="faq.html#AEN2015"
> What type of human resources are needed to be on staff to install and
maintain Bugzilla? Specifically, what type of skills does the person need to
have? I need to find out if we were to go with Bugzilla, what types of
@@ -372,7 +360,7 @@ HREF="faq.html#AEN1596"
></DT
><DT
>A.4.24. <A
-HREF="faq.html#AEN1603"
+HREF="faq.html#AEN2022"
> What time frame are we looking at if we decide to hire people to install
and maintain the Bugzilla? Is this something that takes hours or weeks to
install and a couple of hours per week to maintain and customize or is this
@@ -382,7 +370,7 @@ HREF="faq.html#AEN1603"
></DT
><DT
>A.4.25. <A
-HREF="faq.html#AEN1608"
+HREF="faq.html#AEN2027"
> Is there any licensing fee or other fees for using Bugzilla? Any
out-of-pocket cost other than the bodies needed as identified above?
</A
@@ -398,19 +386,19 @@ HREF="faq.html#FAQ_INSTALL"
><DL
><DT
>A.5.1. <A
-HREF="faq.html#AEN1615"
+HREF="faq.html#AEN2034"
> How do I download and install Bugzilla?
</A
></DT
><DT
>A.5.2. <A
-HREF="faq.html#AEN1621"
+HREF="faq.html#AEN2040"
> How do I install Bugzilla on Windows NT?
</A
></DT
><DT
>A.5.3. <A
-HREF="faq.html#AEN1626"
+HREF="faq.html#AEN2045"
> Is there an easy way to change the Bugzilla cookie name?
</A
></DT
@@ -425,20 +413,20 @@ HREF="faq.html#FAQ_SECURITY"
><DL
><DT
>A.6.1. <A
-HREF="faq.html#AEN1633"
+HREF="faq.html#AEN2052"
> How do I completely disable MySQL security if it's giving me problems
- (I've followed the instructions in the README!)?
+ (I've followed the instructions in the installation section of this guide!)?
</A
></DT
><DT
>A.6.2. <A
-HREF="faq.html#AEN1639"
+HREF="faq.html#AEN2058"
> Are there any security problems with Bugzilla?
</A
></DT
><DT
>A.6.3. <A
-HREF="faq.html#AEN1644"
+HREF="faq.html#AEN2063"
> I've implemented the security fixes mentioned in Chris Yeh's security
advisory of 5/10/2000 advising not to run MySQL as root, and am running into
problems with MySQL no longer working correctly.
@@ -455,48 +443,48 @@ HREF="faq.html#FAQ_EMAIL"
><DL
><DT
>A.7.1. <A
-HREF="faq.html#AEN1651"
+HREF="faq.html#AEN2070"
> I have a user who doesn't want to receive any more email from Bugzilla.
How do I stop it entirely for this user?
</A
></DT
><DT
>A.7.2. <A
-HREF="faq.html#AEN1656"
+HREF="faq.html#AEN2075"
> I'm evaluating/testing Bugzilla, and don't want it to send email to
anyone but me. How do I do it?
</A
></DT
><DT
>A.7.3. <A
-HREF="faq.html#AEN1661"
+HREF="faq.html#AEN2080"
> I want whineatnews.pl to whine at something more, or other than, only new
bugs. How do I do it?
</A
></DT
><DT
>A.7.4. <A
-HREF="faq.html#AEN1667"
+HREF="faq.html#AEN2086"
> I don't like/want to use Procmail to hand mail off to bug_email.pl.
What alternatives do I have?
</A
></DT
><DT
>A.7.5. <A
-HREF="faq.html#AEN1674"
+HREF="faq.html#AEN2093"
> How do I set up the email interface to submit/change bugs via email?
</A
></DT
><DT
>A.7.6. <A
-HREF="faq.html#AEN1679"
+HREF="faq.html#AEN2098"
> Email takes FOREVER to reach me from bugzilla -- it's extremely slow.
What gives?
</A
></DT
><DT
>A.7.7. <A
-HREF="faq.html#AEN1686"
+HREF="faq.html#AEN2105"
> How come email never reaches me from bugzilla changes?
</A
></DT
@@ -511,60 +499,60 @@ HREF="faq.html#FAQ_DB"
><DL
><DT
>A.8.1. <A
-HREF="faq.html#AEN1694"
+HREF="faq.html#AEN2113"
> I've heard Bugzilla can be used with Oracle?
</A
></DT
><DT
>A.8.2. <A
-HREF="faq.html#AEN1699"
+HREF="faq.html#AEN2118"
> Bugs are missing from queries, but exist in the database (and I can pull
them up by specifying the bug ID). What's wrong?
</A
></DT
><DT
>A.8.3. <A
-HREF="faq.html#AEN1704"
+HREF="faq.html#AEN2123"
> I think my database might be corrupted, or contain invalid entries. What
do I do?
</A
></DT
><DT
>A.8.4. <A
-HREF="faq.html#AEN1709"
+HREF="faq.html#AEN2131"
> I want to manually edit some entries in my database. How?
</A
></DT
><DT
>A.8.5. <A
-HREF="faq.html#AEN1714"
+HREF="faq.html#AEN2136"
> I try to add myself as a user, but Bugzilla always tells me my password is wrong.
</A
></DT
><DT
>A.8.6. <A
-HREF="faq.html#AEN1719"
+HREF="faq.html#AEN2141"
> I think I've set up MySQL permissions correctly, but bugzilla still can't
connect.
</A
></DT
><DT
>A.8.7. <A
-HREF="faq.html#AEN1724"
+HREF="faq.html#AEN2146"
> How do I synchronize bug information among multiple different Bugzilla
databases?
</A
></DT
><DT
>A.8.8. <A
-HREF="faq.html#AEN1731"
+HREF="faq.html#AEN2153"
> Why do I get bizarre errors when trying to submit data, particularly problems
with "groupset"?
</A
></DT
><DT
>A.8.9. <A
-HREF="faq.html#AEN1736"
+HREF="faq.html#AEN2158"
> How come even after I delete bugs, the long descriptions show up?
</A
></DT
@@ -579,32 +567,32 @@ HREF="faq.html#FAQ_NT"
><DL
><DT
>A.9.1. <A
-HREF="faq.html#AEN1743"
+HREF="faq.html#AEN2168"
> What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
</A
></DT
><DT
>A.9.2. <A
-HREF="faq.html#AEN1748"
+HREF="faq.html#AEN2173"
> Is there a "Bundle::Bugzilla" equivalent for Win32?
</A
></DT
><DT
>A.9.3. <A
-HREF="faq.html#AEN1753"
+HREF="faq.html#AEN2178"
> CGI's are failing with a "something.cgi is not a valid Windows NT
application" error. Why?
</A
></DT
><DT
>A.9.4. <A
-HREF="faq.html#AEN1761"
+HREF="faq.html#AEN2186"
> Can I have some general instructions on how to make Bugzilla on Win32 work?
</A
></DT
><DT
>A.9.5. <A
-HREF="faq.html#AEN1767"
+HREF="faq.html#AEN2192"
> I'm having trouble with the perl modules for NT not being able to talk to
to the database.
</A
@@ -620,34 +608,34 @@ HREF="faq.html#FAQ_USE"
><DL
><DT
>A.10.1. <A
-HREF="faq.html#AEN1788"
+HREF="faq.html#AEN2213"
> The query page is very confusing. Isn't there a simpler way to query?
</A
></DT
><DT
>A.10.2. <A
-HREF="faq.html#AEN1794"
+HREF="faq.html#AEN2219"
> I'm confused by the behavior of the "accept" button in the Show Bug form.
Why doesn't it assign the bug to me when I accept it?
</A
></DT
><DT
>A.10.3. <A
-HREF="faq.html#AEN1804"
+HREF="faq.html#AEN2229"
> I can't upload anything into the database via the "Create Attachment"
link. What am I doing wrong?
</A
></DT
><DT
>A.10.4. <A
-HREF="faq.html#AEN1809"
+HREF="faq.html#AEN2234"
> Email submissions to Bugzilla that have attachments end up asking me to
save it as a "cgi" file.
</A
></DT
><DT
>A.10.5. <A
-HREF="faq.html#AEN1814"
+HREF="faq.html#AEN2239"
> How do I change a keyword in Bugzilla, once some bugs are using it?
</A
></DT
@@ -662,20 +650,20 @@ HREF="faq.html#FAQ_HACKING"
><DL
><DT
>A.11.1. <A
-HREF="faq.html#AEN1821"
+HREF="faq.html#AEN2246"
> What bugs are in Bugzilla right now?
</A
></DT
><DT
>A.11.2. <A
-HREF="faq.html#AEN1830"
+HREF="faq.html#AEN2255"
> How can I change the default priority to a null value? For instance, have the default
priority be "---" instead of "P2"?
</A
></DT
><DT
>A.11.3. <A
-HREF="faq.html#AEN1836"
+HREF="faq.html#AEN2261"
> What's the best way to submit patches? What guidelines should I follow?
</A
></DT
@@ -695,7 +683,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1302"
+NAME="AEN1713"
></A
><B
>A.1.1. </B
@@ -721,7 +709,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1308"
+NAME="AEN1719"
></A
><B
>A.1.2. </B
@@ -748,7 +736,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1314"
+NAME="AEN1725"
></A
><B
>A.1.3. </B
@@ -783,7 +771,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1321"
+NAME="AEN1732"
></A
><B
>A.1.4. </B
@@ -891,7 +879,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1346"
+NAME="AEN1757"
></A
><B
>A.1.5. </B
@@ -903,13 +891,12 @@ CLASS="ANSWER"
><P
><B
> </B
-> There are many, many contributors from around the world maintaining Bugzilla.
- The designated "Maintainer" is Tara Hernandez, with QA support by Matthew Tuck.
- Dan Mosedale and Dawn Endico are employees of Mozilla.org responsible for the
- installation of Bugzilla there, and are very frequent code contributors.
- Terry Weissman originally ported Bugzilla, but "these days, Terry just hangs around
- and heckles." The rest of us are mostly transient developers; Bugzilla suits
- our needs, and we contribute code as we have needs for updates.
+> Bugzilla maintenance has been in a state of flux recently.
+ Please check <A
+HREF="http://www.mozilla.org/projects/bugzilla/"
+TARGET="_top"
+>the Bugzilla Project Page for the latest details. </A
+>
</P
></DIV
></DIV
@@ -919,7 +906,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1351"
+NAME="AEN1763"
></A
><B
>A.1.6. </B
@@ -933,18 +920,22 @@ CLASS="ANSWER"
> </B
> A year has gone by, and I <EM
>still</EM
-> can't find any head-to-head
- comparisons of Bugzilla against other defect-tracking software. However, from my
- 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.
+> can't
+ find any head-to-head comparisons of Bugzilla against
+ other defect-tracking software. However, from my 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 Bugzilla vendor, please step forward with a rebuttal
- so I can include it in the FAQ. We're not in pursuit of Bugzilla ueber alles;
- we simply love having a powerful, open-source tool to get our jobs done.
+> If you happen to be a commercial bug-tracker vendor, please
+ step forward with a rebuttal so I can include it in the
+ FAQ. We're not in pursuit of Bugzilla ueber alles; we
+ simply love having a powerful, open-source tool to get our
+ jobs done.
</P
></DIV
></DIV
@@ -954,7 +945,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1358"
+NAME="AEN1770"
></A
><B
>A.1.7. </B
@@ -977,7 +968,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1363"
+NAME="AEN1775"
></A
><B
>A.1.8. </B
@@ -1015,7 +1006,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1370"
+NAME="AEN1782"
></A
><B
>A.1.9. </B
@@ -1030,7 +1021,7 @@ CLASS="ANSWER"
> </B
>Terry Weissman answers,
<A
-NAME="AEN1374"
+NAME="AEN1786"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
@@ -1106,7 +1097,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1388"
+NAME="AEN1800"
></A
><B
>A.1.10. </B
@@ -1126,7 +1117,7 @@ CLASS="ANSWER"
><P
> Here's Terry Weissman's comment, for some historical context:
<A
-NAME="AEN1393"
+NAME="AEN1805"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
@@ -1138,11 +1129,25 @@ CLASS="BLOCKQUOTE"
</P
><DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><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
-><B
->Note: </B
> We always recommend that, if possible, you keep the path
as /usr/bonsaitools/bin/perl, and simply add a /usr/bonsaitools
and /usr/bonsaitools/bin directory, then symlink your version
@@ -1153,7 +1158,9 @@ CLASS="NOTE"
> Obviously, if you do not have root access to your Bugzilla
box, our suggestion is irrelevant.
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
></BLOCKQUOTE
>
@@ -1171,17 +1178,33 @@ NAME="FAQ_REDHAT"
><P
> <DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><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
-><B
->Note: </B
> <EM
>This section is no longer up-to-date.</EM
>
Please see the section on "Red Hat Bugzilla" under "Variants" in The Bugzilla Guide.
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
>
</P
@@ -1191,7 +1214,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1405"
+NAME="AEN1817"
></A
><B
>A.2.1. </B
@@ -1215,7 +1238,7 @@ CLASS="ANSWER"
><P
> Dave Lawrence, the original Red Hat Bugzilla maintainer, mentions:
<A
-NAME="AEN1410"
+NAME="AEN1822"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
@@ -1238,7 +1261,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1413"
+NAME="AEN1825"
></A
><B
>A.2.2. </B
@@ -1254,7 +1277,7 @@ CLASS="ANSWER"
>Dave Lawrence</EM
>:
<A
-NAME="AEN1418"
+NAME="AEN1830"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
@@ -1370,7 +1393,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1441"
+NAME="AEN1853"
></A
><B
>A.2.3. </B
@@ -1384,23 +1407,39 @@ CLASS="ANSWER"
> </B
> <DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><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
-><B
->Note: </B
> This information is somewhat dated; I last updated it
7 June 2000. Please see the "Variants" section of "The Bugzilla Guide"
for more up-to-date information regarding Red Hat Bugzilla.
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
>
<EM
>Dave Lawrence</EM
>:
<A
-NAME="AEN1448"
+NAME="AEN1860"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
@@ -1463,39 +1502,17 @@ CLASS="QANDADIV"
NAME="FAQ_LOKI"
></A
>3. Loki Bugzilla (AKA Fenris)</H3
-><P
-> <DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
-><P
-><B
->Note: </B
-> Loki's "Fenris" Bugzilla is based upon the (now ancient) Bugzilla 2.8
- tree, and is no longer actively maintained.
- It works well enough for Loki. Additionally, the major
- differences in Fenris have now been integrated into
- the main source tree of Bugzilla, so there's not much
- reason to go grab the source. I leave this section of the
- FAQ principally for historical interest, but unless Loki has further
- input into Bugzilla's future, it will be deprecated in future versions
- of the Guide.
- </P
-></BLOCKQUOTE
-></DIV
->
- </P
><DIV
CLASS="QANDAENTRY"
><DIV
CLASS="QUESTION"
><P
><A
-NAME="AEN1457"
+NAME="AEN1866"
></A
><B
>A.3.1. </B
-> What about Loki Bugzilla?
+> What is Loki Bugzilla (Fenris)?
</P
></DIV
><DIV
@@ -1504,67 +1521,11 @@ CLASS="ANSWER"
><B
> </B
> Loki Games has a customized version of Bugzilla available at
- http://fenris.lokigames.com. From that page,
<A
-NAME="AEN1461"
-></A
-><BLOCKQUOTE
-CLASS="BLOCKQUOTE"
-><P
-> You may have noticed that Fenris is a fork from Bugzilla-- our
- patches weren't suitable for integration --and a few people have
- expressed interest in the code. Fenris has one major improvement
- over Bugzilla, and that is individual comments are not appended
- onto a string blob, they are stored as a record in a separate
- table. This allows you to, for instance, separate comments out
- according to privilege levels in case your bug database could
- contain sensitive information not for public eyes. We also provide
- things like email hiding to protect user's privacy, additional
- fields such as 'user_affected' in case someone enters someone
- else's bug, comment editing and deletion, and more conditional
- system variables than Bugzilla does (turn off attachments,
- qacontact, etc.).
- </P
-></BLOCKQUOTE
->
- </P
-></DIV
-></DIV
-><DIV
-CLASS="QANDAENTRY"
-><DIV
-CLASS="QUESTION"
-><P
-><A
-NAME="AEN1464"
-></A
-><B
->A.3.2. </B
-> Who maintains Fenris (Loki Bugzilla) now?
- </P
-></DIV
-><DIV
-CLASS="ANSWER"
-><P
-><B
-> </B
-> Raphael Barrerro <raistlin@lokigames.com>.
- Michael Vance created the initial fork, but no longer
- maintains the project.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="QANDAENTRY"
-><DIV
-CLASS="QUESTION"
-><P
-><A
-NAME="AEN1469"
-></A
-><B
->A.3.3. </B
->
+HREF="http://fenris.lokigames.com/"
+TARGET="_top"
+>http://fenris.lokigames.com</A
+>. There are some advantages to using Fenris, chief being separation of comments based upon user privacy level, data hiding, forced login for any data retrieval, and some additional fields. Loki has mainted their code, originally a fork from the Bugzilla 2.8 code base, and it is quite a bit different than stock Bugzilla at this point. I recommend you stick with official Bugzilla version 2.14 rather than using a fork, but it's up to you.
</P
></DIV
></DIV
@@ -1579,15 +1540,31 @@ NAME="FAQ_PHB"
><P
> <DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><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
-><B
->Note: </B
> The title of this section doesn't mean you're a PHB -- it just means
you probably HAVE a PHB who wants to know this :)
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
>
</P
@@ -1597,7 +1574,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1477"
+NAME="AEN1877"
></A
><B
>A.4.1. </B
@@ -1621,7 +1598,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1482"
+NAME="AEN1882"
></A
><B
>A.4.2. </B
@@ -1636,9 +1613,6 @@ CLASS="ANSWER"
> </B
> Yes! You can find more information elsewhere in "The Bugzilla
Guide" in the "Integration with Third-Party Products" section.
- The section on Perforce isn't very large, but as the maintainer
- of the Guide is charged with Perforce/Bugzilla integration by
- his company, you can expect this section to grow.
</P
></DIV
></DIV
@@ -1648,7 +1622,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1487"
+NAME="AEN1887"
></A
><B
>A.4.3. </B
@@ -1674,7 +1648,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1492"
+NAME="AEN1892"
></A
><B
>A.4.4. </B
@@ -1697,7 +1671,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1497"
+NAME="AEN1897"
></A
><B
>A.4.5. </B
@@ -1725,7 +1699,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1502"
+NAME="AEN1902"
></A
><B
>A.4.6. </B
@@ -1743,6 +1717,15 @@ CLASS="ANSWER"
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"
+TARGET="_top"
+>http://bugzilla.mozilla.org/show_bug.cgi?id=91037</A
+>
+ </P
></DIV
></DIV
><DIV
@@ -1751,10 +1734,186 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1507"
+NAME="AEN1909"
></A
><B
>A.4.7. </B
+> The index.html page doesn't show the footer. It's really annoying to have
+ to go to the querypage just to check my "my bugs" link. How do I get a footer
+ on static HTML pages?
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><B
+> </B
+> It's possible to get the footer on the static index page using
+ Server Side Includes (SSI). The trick to doing this is making
+ sure that your web server is set up to allow SSI and specifically,
+ the #exec directive. You should also rename <TT
+CLASS="FILENAME"
+>index.html</TT
+>
+ to <TT
+CLASS="FILENAME"
+>index.shtml</TT
+>.
+ </P
+><P
+> After you've done all that, you can add the following line to
+ <TT
+CLASS="FILENAME"
+>index.shtml</TT
+>:
+<TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+><!--#exec cmd="/usr/bin/perl -e &quot;require 'CGI.pl'; PutFooter();&quot;" --></PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+ </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
+> This line will be replaced with the actual HTML for the footer
+ when the page is requested, so you should put this line where you
+ want the footer to appear.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+></P
+><P
+> Because this method depends on being able to use a #exec directive,
+ and most ISP's will not allow that, there is an alternative method.
+ You could have a small script (such as <TT
+CLASS="FILENAME"
+>api.cgi</TT
+>)
+ that basically looks like:
+<TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>#!/usr/bonsaitools/bin/perl -w
+
+require 'globals.pl';
+
+if ($::FORM{sub} eq 'PutFooter') {
+ PutFooter();
+} else {
+ die 'api.cgi was incorrectly called';
+}</PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+ and then put this line in <TT
+CLASS="FILENAME"
+>index.shtml</TT
+>.
+<TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+><!--#include virtual="api.cgi?sub=PutFooter"--></PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+ </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
+> This still requires being able to use Server Side Includes, if
+ this simply will not work for you, see <A
+HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=80183"
+TARGET="_top"
+>bug 80183</A
+>
+ for a third option.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+></P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1931"
+></A
+><B
+>A.4.8. </B
> Does Bugzilla provide any reporting features, metrics, graphs, etc? You
know, the type of stuff that management likes to see. :)
</P
@@ -1790,10 +1949,10 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1515"
+NAME="AEN1939"
></A
><B
->A.4.8. </B
+>A.4.9. </B
> Is there email notification and if so, what do you see when you get an
email? Do you see bug number and title or is it only the number?
</P
@@ -1815,10 +1974,10 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1520"
+NAME="AEN1944"
></A
><B
->A.4.9. </B
+>A.4.10. </B
> Can email notification be set up to send to multiple
people, some on the To List, CC List, BCC List etc?
</P
@@ -1838,10 +1997,10 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1525"
+NAME="AEN1949"
></A
><B
->A.4.10. </B
+>A.4.11. </B
> If there is email notification, do users have to have any particular
type of email application?
</P
@@ -1855,11 +2014,25 @@ CLASS="ANSWER"
on the planet.
<DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><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
-><B
->Note: </B
> 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
@@ -1867,7 +2040,9 @@ CLASS="NOTE"
Bugzilla ignores HTML tags in comments, and if a user sends HTML-based
email into Bugzilla the resulting comment looks downright awful.
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
>
</P
@@ -1879,10 +2054,10 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1532"
+NAME="AEN1956"
></A
><B
->A.4.11. </B
+>A.4.12. </B
> If I just wanted to track certain bugs, as they go through life, can I
set it up to alert me via email whenever that bug changes, whether it be
owner, status or description etc.?
@@ -1906,10 +2081,10 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1537"
+NAME="AEN1961"
></A
><B
->A.4.12. </B
+>A.4.13. </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
@@ -1951,31 +2126,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1545"
-></A
-><B
->A.4.13. </B
-> Does Bugzilla allow fields to be added, changed or deleted? If I want to
- customize the bug submission form to meet our needs, can I do that using our
- terminology?
- </P
-></DIV
-><DIV
-CLASS="ANSWER"
-><P
-><B
-> </B
-> Yes.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="QANDAENTRY"
-><DIV
-CLASS="QUESTION"
-><P
-><A
-NAME="AEN1550"
+NAME="AEN1969"
></A
><B
>A.4.14. </B
@@ -2001,7 +2152,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1555"
+NAME="AEN1974"
></A
><B
>A.4.15. </B
@@ -2024,7 +2175,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1560"
+NAME="AEN1979"
></A
><B
>A.4.16. </B
@@ -2046,7 +2197,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1565"
+NAME="AEN1984"
></A
><B
>A.4.17. </B
@@ -2069,7 +2220,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1570"
+NAME="AEN1989"
></A
><B
>A.4.18. </B
@@ -2093,7 +2244,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1575"
+NAME="AEN1994"
></A
><B
>A.4.19. </B
@@ -2116,7 +2267,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1580"
+NAME="AEN1999"
></A
><B
>A.4.20. </B
@@ -2141,7 +2292,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1585"
+NAME="AEN2004"
></A
><B
>A.4.21. </B
@@ -2169,7 +2320,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1591"
+NAME="AEN2010"
></A
><B
>A.4.22. </B
@@ -2193,7 +2344,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1596"
+NAME="AEN2015"
></A
><B
>A.4.23. </B
@@ -2232,7 +2383,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1603"
+NAME="AEN2022"
></A
><B
>A.4.24. </B
@@ -2263,7 +2414,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1608"
+NAME="AEN2027"
></A
><B
>A.4.25. </B
@@ -2295,7 +2446,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1615"
+NAME="AEN2034"
></A
><B
>A.5.1. </B
@@ -2312,8 +2463,7 @@ HREF="http://www.mozilla.org/projects/bugzilla/"
TARGET="_top"
> http://www.mozilla.org/projects/bugzilla/</A
> for details.
- Once you download it, untar it, read the README and
- the Bugzilla Guide.
+ Once you download it, untar it, read the Bugzilla Guide.
</P
></DIV
></DIV
@@ -2323,7 +2473,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1621"
+NAME="AEN2040"
></A
><B
>A.5.2. </B
@@ -2346,7 +2496,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1626"
+NAME="AEN2045"
></A
><B
>A.5.3. </B
@@ -2376,12 +2526,12 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1633"
+NAME="AEN2052"
></A
><B
>A.6.1. </B
> How do I completely disable MySQL security if it's giving me problems
- (I've followed the instructions in the README!)?
+ (I've followed the instructions in the installation section of this guide!)?
</P
></DIV
><DIV
@@ -2404,7 +2554,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1639"
+NAME="AEN2058"
></A
><B
>A.6.2. </B
@@ -2419,7 +2569,7 @@ CLASS="ANSWER"
> The Bugzilla code has not undergone a complete security audit.
It is recommended that you closely examine permissions on your Bugzilla
installation, and follow the recommended security guidelines found
- in the README and in The Bugzilla Guide.
+ in The Bugzilla Guide.
</P
></DIV
></DIV
@@ -2429,7 +2579,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1644"
+NAME="AEN2063"
></A
><B
>A.6.3. </B
@@ -2463,7 +2613,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1651"
+NAME="AEN2070"
></A
><B
>A.7.1. </B
@@ -2487,7 +2637,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1656"
+NAME="AEN2075"
></A
><B
>A.7.2. </B
@@ -2511,7 +2661,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1661"
+NAME="AEN2080"
></A
><B
>A.7.3. </B
@@ -2541,7 +2691,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1667"
+NAME="AEN2086"
></A
><B
>A.7.4. </B
@@ -2557,7 +2707,7 @@ CLASS="ANSWER"
> You can call bug_email.pl directly from your aliases file, with
an entry like this:
<A
-NAME="AEN1671"
+NAME="AEN2090"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
@@ -2578,7 +2728,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1674"
+NAME="AEN2093"
></A
><B
>A.7.5. </B
@@ -2601,7 +2751,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1679"
+NAME="AEN2098"
></A
><B
>A.7.6. </B
@@ -2616,20 +2766,14 @@ CLASS="ANSWER"
> </B
> If you are using an alternate Mail Transport Agent (MTA other than
sendmail), make sure the options given in the "processmail" script for all
- instances of "sendmail" are correct for your MTA. If you are using Sendmail,
- you may wish to delete the "-ODeliveryMode=deferred" option in the
- "processmail" script for every invocation of "sendmail". (Be sure and leave
- the "-t" option, though!)
+ instances of "sendmail" are correct for your MTA.
</P
><P
-> A better alternative is to change the "-O" option to
- "-ODeliveryMode=background". This prevents Sendmail from hanging your
- Bugzilla Perl processes if the domain to which it must send mail
- is unavailable.
- </P
-><P
-> This is now a configurable parameter called "sendmailnow", available
- from editparams.cgi.
+> 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
@@ -2639,7 +2783,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1686"
+NAME="AEN2105"
></A
><B
>A.7.7. </B
@@ -2677,7 +2821,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1694"
+NAME="AEN2113"
></A
><B
>A.8.1. </B
@@ -2702,7 +2846,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1699"
+NAME="AEN2118"
></A
><B
>A.8.2. </B
@@ -2737,7 +2881,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1704"
+NAME="AEN2123"
></A
><B
>A.8.3. </B
@@ -2750,12 +2894,29 @@ CLASS="ANSWER"
><P
><B
> </B
-> Run the "sanity check" utility (./sanitycheck.cgi in the bugzilla_home
- directory) to see! If it all comes back, you're 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...
+> 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
@@ -2765,7 +2926,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1709"
+NAME="AEN2131"
></A
><B
>A.8.4. </B
@@ -2792,7 +2953,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1714"
+NAME="AEN2136"
></A
><B
>A.8.5. </B
@@ -2816,7 +2977,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1719"
+NAME="AEN2141"
></A
><B
>A.8.6. </B
@@ -2843,7 +3004,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1724"
+NAME="AEN2146"
></A
><B
>A.8.7. </B
@@ -2879,7 +3040,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1731"
+NAME="AEN2153"
></A
><B
>A.8.8. </B
@@ -2905,7 +3066,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1736"
+NAME="AEN2158"
></A
><B
>A.8.9. </B
@@ -2917,10 +3078,21 @@ CLASS="ANSWER"
><P
><B
> </B
-> Delete everything from $BUZILLA_HOME/shadow. Bugzilla creates shadow
- files there, with each filename corresponding to a
- bug number. Also be sure to run syncshadowdb to make sure, if you are using
- a shadow database, that the shadow database is current.
+> This should only happen with Bugzilla 2.14 if you are
+ using the <SPAN
+CLASS="QUOTE"
+>"shadow database"</SPAN
+> feature, and your
+ shadow database is out of sync. Try running
+ <TT
+CLASS="FILENAME"
+>syncshadowdb</TT
+>
+ <TT
+CLASS="OPTION"
+>-syncall</TT
+> to make sure your shadow
+ database is in synch with your primary database.
</P
></DIV
></DIV
@@ -2938,7 +3110,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1743"
+NAME="AEN2168"
></A
><B
>A.9.1. </B
@@ -2961,7 +3133,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1748"
+NAME="AEN2173"
></A
><B
>A.9.2. </B
@@ -2985,7 +3157,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1753"
+NAME="AEN2178"
></A
><B
>A.9.3. </B
@@ -3006,7 +3178,7 @@ CLASS="ANSWER"
><P
> Microsoft has some advice on this matter, as well:
<A
-NAME="AEN1758"
+NAME="AEN2183"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
@@ -3031,7 +3203,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1761"
+NAME="AEN2186"
></A
><B
>A.9.4. </B
@@ -3142,7 +3314,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1767"
+NAME="AEN2192"
></A
><B
>A.9.5. </B
@@ -3217,7 +3389,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1788"
+NAME="AEN2213"
></A
><B
>A.10.1. </B
@@ -3245,7 +3417,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1794"
+NAME="AEN2219"
></A
><B
>A.10.2. </B
@@ -3298,7 +3470,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1804"
+NAME="AEN2229"
></A
><B
>A.10.3. </B
@@ -3323,7 +3495,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1809"
+NAME="AEN2234"
></A
><B
>A.10.4. </B
@@ -3348,7 +3520,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1814"
+NAME="AEN2239"
></A
><B
>A.10.5. </B
@@ -3380,7 +3552,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1821"
+NAME="AEN2246"
></A
><B
>A.11.1. </B
@@ -3393,20 +3565,20 @@ CLASS="ANSWER"
><B
> </B
> Try <A
-HREF="http://bugzilla.mozilla.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Webtools&component=Bugzilla"
+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.14 release
+> You can view bugs marked for 2.16 release
<A
-HREF="http://bugzilla.mozilla.org/buglist.cgi?product=Webtools&component=Bugzilla&target_milestone=Bugzilla+2.14"
+HREF="http://bugzilla.mozilla.org/buglist.cgi?product=Bugzilla&target_milestone=Bugzilla+2.16"
TARGET="_top"
>here</A
>.
- This list includes bugs for the 2.14 release that have already
+ This list includes bugs for the 2.16 release that have already
been fixed and checked into CVS. Please consult the
<A
HREF="http://www.mozilla.org/projects/bugzilla/"
@@ -3424,7 +3596,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1830"
+NAME="AEN2255"
></A
><B
>A.11.2. </B
@@ -3456,7 +3628,7 @@ CLASS="QANDAENTRY"
CLASS="QUESTION"
><P
><A
-NAME="AEN1836"
+NAME="AEN2261"
></A
><B
>A.11.3. </B
@@ -3474,8 +3646,15 @@ CLASS="ANSWER"
TYPE="1"
><LI
><P
-> Enter a bug into bugzilla.mozilla.org for the "Webtools" product,
- "Bugzilla" component.
+> 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
@@ -3536,7 +3715,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
-HREF="bz30.html"
+HREF="variant_sourceforge.html"
>Prev</A
></TD
><TD
@@ -3561,7 +3740,7 @@ HREF="downloadlinks.html"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
->Bugzilla 3.0</TD
+>SourceForge</TD
><TD
WIDTH="34%"
ALIGN="center"
diff --git a/docs/html/feedback.html b/docs/html/feedback.html
index e5c347d2e..9ef62e718 100644
--- a/docs/html/feedback.html
+++ b/docs/html/feedback.html
@@ -4,7 +4,7 @@
>Feedback</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
@@ -74,15 +74,16 @@ NAME="FEEDBACK"
>1.7. Feedback</A
></H1
><P
-> I welcome feedback on this document. Without your submissions and input,
- this Guide cannot continue to exist. Please mail additions, comments, criticisms, etc.
- to <TT
+> I welcome feedback on this document. Without your submissions
+ and input, this Guide cannot continue to exist. Please mail
+ additions, comments, criticisms, etc. to
+ <TT
CLASS="EMAIL"
><<A
HREF="mailto:barnboy@trilobyte.net"
>barnboy@trilobyte.net</A
>></TT
->. Please send flames to
+>. Please send flames to
<TT
CLASS="EMAIL"
><<A
diff --git a/docs/html/future.html b/docs/html/future.html
index 60553e411..99a577ff8 100644
--- a/docs/html/future.html
+++ b/docs/html/future.html
@@ -4,17 +4,17 @@
>The Future of Bugzilla</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="PREVIOUS"
-TITLE="Tinderbox"
+TITLE="Tinderbox/Tinderbox2"
HREF="tinderbox.html"><LINK
REL="NEXT"
-TITLE="Reducing Spam"
-HREF="spamlite.html"></HEAD
+TITLE="Bugzilla Variants and Competitors"
+HREF="variants.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@@ -54,7 +54,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
-HREF="spamlite.html"
+HREF="variants.html"
>Next</A
></TD
></TR
@@ -69,57 +69,617 @@ CLASS="CHAPTER"
NAME="FUTURE"
>Chapter 6. The Future of Bugzilla</A
></H1
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->6.1. <A
-HREF="spamlite.html"
->Reducing Spam</A
-></DT
-><DT
->6.2. <A
-HREF="searching.html"
->Better Searching</A
-></DT
-><DT
->6.3. <A
-HREF="trackingbugs.html"
->Description Flags and Tracking Bugs</A
-></DT
-><DT
->6.4. <A
-HREF="bugprobs.html"
->Bug Issues</A
-></DT
-><DT
->6.5. <A
-HREF="dbaseintegrity.html"
->Database Integrity</A
-></DT
-><DT
->6.6. <A
-HREF="bz30.html"
->Bugzilla 3.0</A
-></DT
-></DL
-></DIV
><TABLE
BORDER="0"
-BGCOLOR="#E0E0E0"
+BGCOLOR="#6495ED"
WIDTH="100%"
><TR
><TD
+><FONT
+COLOR="#000000"
><PRE
CLASS="SYNOPSIS"
>Bugzilla's Future. Much of this is the present, now.</PRE
+></FONT
></TD
></TR
></TABLE
+><P
+> Bugzilla's future is a constantly-changing thing, as various developers
+ <SPAN
+CLASS="QUOTE"
+>"scratch an itch"</SPAN
+> when it comes to functionality.
+ Thus this section is very malleable, subject to change without notice, etc.
+ You'll probably also notice the lack of formatting. I apologize that it's
+ not quite as readable as the rest of the Guide.
+ </P
+><P
+> <P
+CLASS="LITERALLAYOUT"
+> Bugzilla Blue Sky<br>
+<br>
+Customisability<br>
+<br>
+ One of the major stumbling blocks of Bugzilla has been that it is too<br>
+ rigid and does not adapt itself well enough to the needs of an<br>
+ organisation. This has led to organisations making changes to the<br>
+ Bugzilla code that need to be redone each new version of Bugzilla.<br>
+ Bugzilla should attempt to move away from this to a world where this<br>
+ doesn't need to occur.<br>
+<br>
+ Most of the subsections in this section are currently explicit design<br>
+ goals for the "Bugzilla 3" rewrite. This does not necessarily mean<br>
+ that they will not occur before them in Bugzilla 2, but most are<br>
+ significant undertakings.<br>
+<br>
+ Field Customisation<br>
+<br>
+ Many installations wish to customise the fields that appear on bug<br>
+ reports. Current versions of Bugzilla offer limited<br>
+ customisability. In particular, some fields can be turned off.<br>
+<br>
+ However, many administrators wish to add their own fields, and rename<br>
+ or otherwise modify existing fields. An architecture that supports<br>
+ this would be extraordinarily useful.<br>
+<br>
+ Indeed, many fields work similarly and could be abstracted into "field<br>
+ types", so that an administrator need write little or no code to<br>
+ support the new fields they desire.<br>
+<br>
+ Possible field types include text (eg status whiteboard), numbers,<br>
+ dates (eg report time), accounts (eg reporter, qa, cc), inter-bug<br>
+ relationships (dependencies, duplicates), option groups (platform, os,<br>
+ severity, priority, target milestone, version) etc.<br>
+<br>
+ Ideally an administrator could configure their fields through a<br>
+ Bugzilla interface that requires no code to be added. However, it is<br>
+ highly unlikely this ideal will never be met, and in a similar way<br>
+ that office applications have scripting languages, Bugzilla should<br>
+ allow new field types to be written.<br>
+<br>
+ Similarly, a common desire is for resolutions to be added or removed.<br>
+<br>
+ Allocations<br>
+<br>
+ ?<br>
+<br>
+ Option Groups<br>
+<br>
+ ?<br>
+<br>
+ Relations<br>
+<br>
+ ?<br>
+<br>
+ Database Integrity<br>
+<br>
+ Furthermore, it is desirable for administrators to be able to specify<br>
+ rules that must or should apply between the fields on a bug report.<br>
+<br>
+ For example, you might wish to specify that a bug with status ASSIGNED<br>
+ must have a target milestone field that that is not untargetted. Or<br>
+ that a bug with a certain number of votes should get ASSIGNED. Or<br>
+ that the QA contact must be different from the assignee.<br>
+<br>
+ "Must" relationships could be implemented by refusing to make changes<br>
+ that violate the relationships, or alternatively, automatically<br>
+ updating certain fields in order to satisfy the criteria. Which<br>
+ occurs should be up to the administrator.<br>
+<br>
+ "Should" relationships could be implemented by a combination of<br>
+ emitting warnings on the process bug page, the same on notification<br>
+ mails, or emitting periodic whine mails about the situation. Again,<br>
+ which occurs should be up to the administrator.<br>
+<br>
+ It should also be possible for whine mails to be emitted for "must"<br>
+ relationships, as they might become violated through direct database<br>
+ access, Bugzilla bugs, or because they were there before the<br>
+ relationship was enforced.<br>
+<br>
+ As well as implementing intra-bug constraints, it would be useful to<br>
+ create inter-bug constraints. For example, a bug that is dependent on<br>
+ another bug should not have an earlier milestone or greater priority<br>
+ than that bug.<br>
+<br>
+ Database Adaptability<br>
+<br>
+ Often an administrator desires that fields adapt to the values of<br>
+ other fields. For example, the value of a field might determine the<br>
+ possible values of another field or even whether it appears (whether<br>
+ it is "applicable").<br>
+<br>
+ Limited adaptability is present in Bugzilla 2, and only on the<br>
+ "Product" field:<br>
+ * The possible values of the target milestone, version and component<br>
+ fields depend on the product.<br>
+ * UNCONFIRMED can be turned off for specific products.<br>
+ * Voting can be configured differently or turned off for different<br>
+ products, and there is a separate user vote limits for each<br>
+ product.<br>
+<br>
+ It would be good if more adaptability was present, both in terms of<br>
+ all fields relying on the product, as well as the ability to adapt<br>
+ based on the value of all fields.<br>
+<br>
+ Example ???<br>
+<br>
+ General adaptability raises the issue of circular references between<br>
+ fields causing problems. One possible solution to this is to place<br>
+ the fields in a total ordering and require a field refer only to the<br>
+ previous fields.<br>
+<br>
+ In Bugzilla 2, changing the product of a bug meant a second page would<br>
+ appear that allowed you to choose a new milestone, component and<br>
+ version, as those fields adapted themselves to the new product. This<br>
+ page could be generalised to support all instances where:<br>
+ * a field value must or might be changed because the possible values<br>
+ have changed<br>
+ * is going to drop off because it it is no longer applicable, and<br>
+ this should be confirmed<br>
+ * must be specified because it is suddenly applicable, and the<br>
+ default value, if one exists, might not be acceptable<br>
+<br>
+ Database Independence<br>
+<br>
+ Currently Bugzilla only runs on the MySQL database. It would be<br>
+ desirable for Bugzilla to run on other databases, because:<br>
+ * Organisations may have existing database products they use and<br>
+ would prefer to run a homogenous environment.<br>
+ * Databases each have their own shortcomings, including MySQL. An<br>
+ administrator might choose a database that would work better with<br>
+ their Bugzilla.<br>
+<br>
+ This raises the possibility that we could use features that are only<br>
+ present in some databases, by appropriately falling back. For<br>
+ example, in the MySQL world, we live without:<br>
+ * record-level locking, instead we use table-level locking<br>
+ * referential and record constraints, instead we checking code<br>
+ * subselects, instead we use multiple queries and redundant "caches"<br>
+<br>
+ Multiple Front Ends<br>
+<br>
+ Currently Bugzilla is manipulated via the Web, and notifies via<br>
+ E-Mail. It would be desirable for Bugzilla to easily support various<br>
+ front ends.<br>
+<br>
+ There is no reason that Bugzilla could not be controlled via a whole<br>
+ range of front ends, including Web, E-Mail, IRC, ICQ, etc, and<br>
+ similarly for how it notifies. It's also possible that we could<br>
+ introduce a special Bugzilla client that uses its own protocol, for<br>
+ maximum user productivity.<br>
+<br>
+ Indeed a request reply might be returned via a totally different<br>
+ transport method than was use to submit the request.<br>
+<br>
+Internationalisation<br>
+<br>
+ Bugzilla currently supports only English. All of the field names,<br>
+ user instructions, etc are written in English. It would be desirable<br>
+ to allow "language packs" so Bugzilla can be easily used in<br>
+ non-English speaking locales.<br>
+<br>
+ To a degree field customisation supports this, because administrators<br>
+ could specify their own fields names anyway. However, there will<br>
+ always be some basic facilities not covered by this, and it is<br>
+ desirable that the administrator's interface also is<br>
+ internationalisable.<br>
+<br>
+Better Searching<br>
+<br>
+ General Summary Reports<br>
+<br>
+ Sometimes, the normal querying page leaves a lot to be desired. There<br>
+ are other facilities already in place or which people have asked for:<br>
+<br>
+ Most Doomed Reports - All Bugs or All Bugs In A Product, Categorised<br>
+ On Assignee, Shows and Counts Number of Bugs For Each Assignee<br>
+ Most Voted For Bugs - All Bugs, Categorised On Product, Shows Top Ten<br>
+ Bugs Voters Most Want Fixed<br>
+ Number of Open Bugs For An Assignee - Bug List, Categorised On<br>
+ Developers, Counts Number of Bugs In Category<br>
+<br>
+ The important thing to realise is that people want categorised reports<br>
+ on all sorts of things - a general summary report.<br>
+<br>
+ In a categorised report, you choose the subset of bugs you wish to<br>
+ operate on (similar to how you would specify a query), and then<br>
+ categorise them on one or more fields.<br>
+<br>
+ For each category you display the count of the number of things in<br>
+ that category. You can optionally display the bugs themselves, or<br>
+ leave them out, just showing the counts. And you can optionally limit<br>
+ the number of things (bugs or subcategories) that display in each<br>
+ category.<br>
+<br>
+ Such a mechanism would let you do all of the above and more.<br>
+ Applications of this mechanism would only be recognised once it was<br>
+ implemented.<br>
+<br>
+ Related Bugs<br>
+<br>
+ It would be nice to have a field where you could enter other bugs<br>
+ related to the current bug. It would be handy for navigation and<br>
+ possibly even finding duplicates.<br>
+<br>
+ Column Specification Support<br>
+<br>
+ Currently bug lists use the columns that you last used. This doesn't<br>
+ work well for "prepackaged queries", where you followed a link. You<br>
+ can probably add a column by specifying a sort column, but this is<br>
+ difficult and suboptimal.<br>
+<br>
+ Furthermore, I find that when I want to add a column to a bug list,<br>
+ it's usually a one off and I would prefer it to go away for the next<br>
+ query. Hence, it would be nice to specify the columns that appear on<br>
+ the bug list (and general summary report) pages. The default query<br>
+ mechanism should be able to let you specify your default columns.<br>
+<br>
+ Advanced Querying Redesign<br>
+<br>
+ ?<br>
+<br>
+Keywords<br>
+<br>
+ People have a need to apply tags to bugs. In the beginning, people<br>
+ placed designators in the summary and status whiteboard. However,<br>
+ these fields were not designed for that, and so there were many flaws<br>
+ with this system:<br>
+ * They pollute the field with information that was never intended to<br>
+ be present.<br>
+ * Removing them with a bulk change is a difficult problem that has<br>
+ too many pitfalls to implement.<br>
+ * You can easily get the capitalisation wrong.<br>
+<br>
+ Then dependencies were introduced (when?), and people realised that<br>
+ they could use them for "tracking bugs". Again, dependencies were not<br>
+ designed for that, and so there were more flaws, albeit different<br>
+ ones, including:<br>
+ * They aren't really bugs, so it's difficult to distinguish issues<br>
+ from bugs.<br>
+ * They can pollute bugs counts, and you must somehow exclude them<br>
+ from queries.<br>
+ * There is a whole lot of useless information on them. They have an<br>
+ assignee but there is nothing to fix, and that person can get<br>
+ whined at by Bugzilla. They have target milestones which must be<br>
+ manually maintained. And so on.<br>
+<br>
+ Finally, keywords were introduced (when?) for this purpose to remove<br>
+ the need for these two systems. Unfortunately, the simple keywords<br>
+ implementation was itself lacking in certain features provided by the<br>
+ two previous systems, and has remained almost unchanged since its<br>
+ inception. Furthermore, it could not be forseen that in large<br>
+ installations, the sheer number of keywords could become unwieldly and<br>
+ could lead to a movement back to the other systems.<br>
+<br>
+ The keywords system was the right idea, however, and it remains so.<br>
+ Fixing the keywords system is one of the most important Bugzilla<br>
+ issues.<br>
+<br>
+ Bringing Keywords Up To Par<br>
+<br>
+ For the most part, keywords are very good at what they do. It is easy<br>
+ to add and remove them (unlike summary/whiteboard designators), we can<br>
+ simply see what issues are present on a bug (unlike tracking bugs),<br>
+ and we do not confuse bugs with issues (unlike tracking bugs).<br>
+<br>
+ However, there are still some "regressions" in the keyword system over<br>
+ previous systems:<br>
+ * Users wish to view the "dependency forest" of a keyword. While a<br>
+ dependency tree is of one bug, a dependency forest is of a bug<br>
+ list, and consists of a dependency tree for each member of the bug<br>
+ list. Users can work around this with tracking bugs by creating a<br>
+ tracking bug and viewing the dependency tree of that tracking bug.<br>
+ * Users wish to specify the keywords that initially apply to a bug,<br>
+ but instead they must edit the bug once it has already been<br>
+ submitted. They can work around this with summary designators,<br>
+ since they specify the summary at reporting time.<br>
+ * Users wish to store or share a bug list that contains a keywords<br>
+ column. Hence they wish to be able to specify what columns appear<br>
+ in the bug list URL, as mentioned earlier. They can work around<br>
+ this using summary designators, since almost all bug lists have a<br>
+ summary column.<br>
+ * Users wish to be able to view keywords on a bug list. However<br>
+ often they are only interested in a small number of keywords.<br>
+ Having a bug list with a keywords column means that all keywords<br>
+ will appear on a bug list. This can take a substantial amount of<br>
+ space where a bug has a lot of keywords, since the table columns<br>
+ in Bugzilla adjust to the largest cell in that column. Hence<br>
+ users wish to be able to specify which keywords should appear in<br>
+ the bug list. In a very real sense, each keyword is a field unto<br>
+ itself. Users can work around this by using summary designators,<br>
+ since they keywords will share the space in the summary column.<br>
+ * Users wish to know when bugs with a specific issue are resolved.<br>
+ Hence they wish to be able to receive notifications on all the<br>
+ bugs with a specific keyword. The introduction a generic watching<br>
+ facility (also for things like watching all bugs in a component)<br>
+ would achieve this. Users can work around this by using tracking<br>
+ bugs, as dependencies have an existing way of detecting fixes to<br>
+ bug a bug was blocked by.<br>
+<br>
+ Dealing With The Keyword Overload<br>
+<br>
+ At the time of writing, the mozilla.org installation has approximately<br>
+ 100 keywords, and many more would be in use if the keywords system<br>
+ didn't have the problems it does.<br>
+<br>
+ Such a large number of keywords introduces logistical problems:<br>
+ * It must be easy for someone to learn what a keyword means. If a<br>
+ keyword is buried within a lot of other keywords, it can be<br>
+ difficult to find.<br>
+ * It must be easy to see what keywords are on a bug. If the number<br>
+ of keywords is large, then this can be difficult.<br>
+<br>
+ These lead some people to feel that there are "too many keywords".<br>
+<br>
+ These problems are not without solutions however. It is harder to<br>
+ find a list of designators or tracking bugs than it is a list of<br>
+ keywords.<br>
+<br>
+ The essential problem is it needs to be easy to find the keywords<br>
+ we're interested in through the mass of keywords.<br>
+<br>
+ Keyword Applicability<br>
+<br>
+ As has been previously mentioned, it is desirable for fields to be<br>
+ able to adapt to the values of other fields. This is certainly true<br>
+ for keywords. Many keywords are simply not relevant because of the<br>
+ bugs product, component, etc.<br>
+<br>
+ Hence, by introducing keyword applicability, and not displaying<br>
+ keywords that are not relevant to the current bug, or clearly<br>
+ separating them, we can make the keyword overload problem less<br>
+ significant.<br>
+<br>
+ Currently when you click on "keywords" on a bug, you get a list of all<br>
+ bugs. It would be desirable to introduce a list of keywords tailored<br>
+ to a specific bug, that reports, in order:<br>
+ * the keywords currently on the bug<br>
+ * the keywords not currently on the bug, but applicable to the bug<br>
+ * optionally, the keywords not applicable to the bug<br>
+<br>
+ This essentially orders the keywords into three groups, where each<br>
+ group is more important than the previous, and therefore appears<br>
+ closer to the top.<br>
+<br>
+ Keyword Grouping & Ordering<br>
+<br>
+ We could further enhance both the global and bug specific keyword list<br>
+ by grouping keywords. We should always have a "flat" view of<br>
+ keywords, but other ways of viewing the keywords would be useful too.<br>
+<br>
+ If keyword applicability was implemented, we could group keywords<br>
+ based on their "applicability condition". Keywords that apply to all<br>
+ bugs could be separated from keywords that apply to a specific<br>
+ product, both on the global keyword list and the keyword list of a bug<br>
+ that is in that product.<br>
+<br>
+ We could specify groups of our own. For example, many keywords are in<br>
+ a mutually exclusive group, essentially like radio buttons in a user<br>
+ interface. This creates a natural grouping, although other groupings<br>
+ occur (which depends on your keywords).<br>
+<br>
+ It is possible that we could use collapsing/expanding operations on<br>
+ "twisties" to only should the groups we are interested in.<br>
+<br>
+ And instead of grouping keywords, we could order them on some metric<br>
+ of usefulness, such as:<br>
+ * when the keyword was last added to a bug<br>
+ * how many bugs the keyword is on<br>
+ * how many open bugs the keyword is on<br>
+<br>
+ Opting Out Of Keywords<br>
+<br>
+ Not all people are going to care about all keywords. Therefore it<br>
+ makes sense that you may wish to specify which keywords you are<br>
+ interested in, either on the bug page, or on notifications.<br>
+<br>
+ Other keywords will therefore not bother users who are not interested<br>
+ in them.<br>
+<br>
+ Keyword Security<br>
+<br>
+ Currently all keywords are available and editable to all people with<br>
+ edit bugs access. This situation is clearly suboptimal.<br>
+<br>
+ Although relying on good behaviour for people to not do what they<br>
+ shouldn't works reasonably well on the mozilla.org, it is better to<br>
+ enforce that behaviour - it can be breached through malice, accident<br>
+ or ignorance.<br>
+<br>
+ And in the situation where it is desirable for the presence or absence<br>
+ of a keyword not to be revealed, organisations either need to be<br>
+ content with the divulgence, or not use keywords at all.<br>
+<br>
+ In the situation where they choose to divulge, introducing the ability<br>
+ to restrict who can see the keyword would also reduce keyword<br>
+ overload.<br>
+<br>
+ Personal Keywords<br>
+<br>
+ Keywords join together a set of bugs which would otherwise be<br>
+ unrelated in the bug system.<br>
+<br>
+ We allow users to store their own queries. However we don't allow<br>
+ them to store their own keywords on a bug. This reduces the<br>
+ usefulness of personal queries, since you cannot join a set of<br>
+ unrelated bugs together in a way that you wish. Lists of bug numbers<br>
+ can work, by they can only be used for small lists, and it is<br>
+ impossible to share a list between multiple queries.<br>
+<br>
+ Personal keywords are necessary to replace personal tracking bugs, as<br>
+ they would not pollute the keyword space. Indeed, on many<br>
+ installations this could remove some keywords out of the global<br>
+ keyword space.<br>
+<br>
+ In a similar vein and with similar effects, group keywords could be<br>
+ introduced that are only available to members of a specific group.<br>
+<br>
+ Keyword Restrictions<br>
+<br>
+ Keywords are not islands unto themselves. Along with their potential<br>
+ to be involved in the inter-field relationships mentioned earlier,<br>
+ keywords can also be related to other keywords.<br>
+<br>
+ Essentially, there are two possibilities:<br>
+ * a set of keywords are mutually exclusive<br>
+ * the presence of a keyword implies another keyword must be present<br>
+<br>
+ Introduction of the ability to specify these restrictions would have<br>
+ benefits.<br>
+<br>
+ If mutually exclusive keywords were present on a bug, their removal<br>
+ would fix up the database, as well as reducing the number of keywords<br>
+ on that bug.<br>
+<br>
+ In the situation where a keyword implies another keyword, there are<br>
+ two possiblities as to how to handle the situation.<br>
+<br>
+ The first is automatically add the keyword. This would fix up the<br>
+ database, but it would increase the number of keywords on a bug.<br>
+<br>
+ The second is to automatically remove the keyword, and alter queries<br>
+ so they pick up the first keyword as well as the removed keyword.<br>
+ This would fix up the database and reduce the number of keywords on a<br>
+ bug, but it might confuse users who don't see the keyword.<br>
+ Alternatively, the implied keywords could be listed separately.<br>
+<br>
+Notifications<br>
+<br>
+ Every time a bug gets changed notifications get sent out to people<br>
+ letting them know about what changes have been made. This is a<br>
+ significant feature, and all sorts of questions can be raised, but<br>
+ they mainly boil down to when they should be sent and what they should<br>
+ look like.<br>
+<br>
+ Changes You're Interested In<br>
+<br>
+ As of version 2.12 users can specify what sort of changes they are<br>
+ interested in receiving notifications for. However, this is still<br>
+ limited. As yet there is no facility to specify which keywords you<br>
+ care about, and whether you care about changes to fields such as the<br>
+ QA contact changes.<br>
+ Furthermore, often an unnecessary comment will go along with a change,<br>
+ either because it is required, or the commenter is ignorant of how the<br>
+ new system works. While explaining why you did something is useful,<br>
+ merely commenting on what you did is not because that information is<br>
+ already accessible view "Bug Activity".<br>
+<br>
+ Because of this unnecessary comment, a lot of changes that would<br>
+ otherwise not generate notifications for certain people do so, because<br>
+ few people are willing to turn off comments. One way to deal with<br>
+ this problem is to allow people to specify that their comments are<br>
+ purely explanatory, and that anyone who is not interested in the<br>
+ change will not be interested in the comment.<br>
+<br>
+ Furthermore, one possible rationale for unnecessary comments is that<br>
+ the bug activity does not display on the normal page and hence it is<br>
+ difficult to cross reference comments and actions. Hence, it would be<br>
+ beneficial to be able to do this.<br>
+<br>
+ Bugs You're Watching<br>
+<br>
+ Currently to receive a notification about a bug you need to have your<br>
+ name on it. This is suboptimal because you need to know about a bug<br>
+ before you can receive notifications on it. Often you are interested<br>
+ in any bug with a field set to a specific value. For example, you<br>
+ might be interested in all bugs with a specific product, component or<br>
+ keyword.<br>
+<br>
+ If someone could automatically receive notifications about these bugs,<br>
+ it would make everyone's lives easier. Currently the default assignee<br>
+ and QA contact for a component will automatically receive<br>
+ notifications for<br>
+<br>
+ Question: This moves half way to a BCC.<br>
+<br>
+ Bulk Changes<br>
+<br>
+ A very useful feature of Bugzilla is the ability to perform an action<br>
+ on multiple bugs at once. However, this means that similar<br>
+ notifications are currently generated for each bug modified.<br>
+<br>
+ This can result in a torrent of notifications that can annoy.<br>
+<br>
+ Furthermore, since the bugs are all changed close to each other in<br>
+ time, it is easy for someone to mass delete all the notifications<br>
+ generated by a bulk change and miss an unrelated notification in the<br>
+ middle.<br>
+<br>
+ These factors can lead to a tendency for people to delay bulk changes,<br>
+ or avoid them entirely. This is suboptimal.<br>
+<br>
+ It would be better if a bulk change generated only one notification<br>
+ mail. This would vastly reduce the annoyance factor, and prevent<br>
+ accidental deletion of notifications.<br>
+<br>
+ One problem with this change is that some people separate out<br>
+ notifications using filtering. This means that they would no longer<br>
+ be match parts of a bulk change under different filtering rules.<br>
+<br>
+ One possibility to resolve this is to allow people to specify groups<br>
+ of bugs. All bugs within a group would go into the same<br>
+ notification. The filters could then distinguish the different bug<br>
+ groups.<br>
+<br>
+ In any case, it is likely there would need to be a transition period<br>
+ to allow people to alter their filters.<br>
+<br>
+Nominations<br>
+<br>
+ ?<br>
+<br>
+Linking Bugzilla Installations<br>
+<br>
+ The first example of linking Bugzilla installations together has is<br>
+ the introduction of bug moving in version 2.12. However, it would be<br>
+ useful to be able to link installations in more ways.<br>
+ * Dependencies and other relationships between bugs in other<br>
+ installations. This is difficult because dependencies are<br>
+ synchronised on both bugs, so the installation that changes<br>
+ dependencies would need to communicate the new state to the other<br>
+ installation. It would also mean that relationships and<br>
+ notifications that refer to other bugs would need to communicate<br>
+ with the other installation.<br>
+ * References to bugs in other installations. Currently if you type<br>
+ "bug XXX" or "bug #XXX" where XXX is a number, you get an<br>
+ automatic hyperlink to that bug. It would be useful if you could<br>
+ say "YYY bug #XXX" where YYY is the name of another installation.<br>
+<br>
+Retirement<br>
+<br>
+ ?<br>
+<br>
+Whiny Reports<br>
+<br>
+ ?<br>
+<br>
+ Group Redesign<br>
+<br>
+ ?<br>
+<br>
+ Hard Wrapping Comments<br>
+<br>
+ Currently Bugzilla "hard wraps" its comments to a specific line size,<br>
+ similar to E-Mail. This has various problems:<br>
+ * The way it currently works, wrapping is done in the browser at<br>
+ submission time using a non-standard HTML extension not supported<br>
+ by some (uncommon) browsers. These browsers generate comments<br>
+ that scroll off the right side of the screen.<br>
+ * Because comments are of fixed width, when you expand your browser<br>
+ window, the comments do not expand to fit available space.<br>
+<br>
+ It would be much better to move to a world of soft wrapping, where the<br>
+ browser wraps the text at display time, similar to a world processor.<br>
+ And as in a word processor, soft wrapping does not preclude the<br>
+ insertion of newlines.<br>
+<br>
+ Hard wrapping is too entrenched into text E-Mail to fix, but we can<br>
+ fix Bugzilla without causing any problems. The old content will still<br>
+ be wrapped too early, but at least new content will work.<br>
+ </P
+>
+ </P
></DIV
><DIV
CLASS="NAVFOOTER"
@@ -152,7 +712,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
-HREF="spamlite.html"
+HREF="variants.html"
>Next</A
></TD
></TR
@@ -161,7 +721,7 @@ HREF="spamlite.html"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
->Tinderbox</TD
+>Tinderbox/Tinderbox2</TD
><TD
WIDTH="34%"
ALIGN="center"
@@ -171,7 +731,7 @@ VALIGN="top"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
->Reducing Spam</TD
+>Bugzilla Variants and Competitors</TD
></TR
></TABLE
></DIV
diff --git a/docs/html/geninstall.html b/docs/html/geninstall.html
new file mode 100644
index 000000000..18217ef48
--- /dev/null
+++ b/docs/html/geninstall.html
@@ -0,0 +1,421 @@
+<HTML
+><HEAD
+><TITLE
+>Installation General Notes</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide"
+HREF="index.html"><LINK
+REL="UP"
+TITLE="Installation"
+HREF="installation.html"><LINK
+REL="PREVIOUS"
+TITLE="BSD Installation Notes"
+HREF="bsdinstall.html"><LINK
+REL="NEXT"
+TITLE="Win32 Installation Notes"
+HREF="win32.html"></HEAD
+><BODY
+CLASS="SECTION"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>The Bugzilla Guide</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="bsdinstall.html"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Chapter 3. Installation</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="win32.html"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="SECTION"
+><H1
+CLASS="SECTION"
+><A
+NAME="GENINSTALL"
+>3.5. Installation General Notes</A
+></H1
+><DIV
+CLASS="SECTION"
+><H2
+CLASS="SECTION"
+><A
+NAME="AEN941"
+>3.5.1. Modifying Your Running System</A
+></H2
+><P
+> Bugzilla optimizes database lookups by storing all relatively static
+ information in the versioncache file, located in the data/ subdirectory
+ under your installation directory.
+ </P
+><P
+> If you make a change to the structural data in your database
+ (the versions table for example), or to the
+ <SPAN
+CLASS="QUOTE"
+>"constants"</SPAN
+> encoded in defparams.pl, you will
+ need to remove the cached content from the data directory
+ (by doing a <SPAN
+CLASS="QUOTE"
+>"rm data/versioncache"</SPAN
+>), or your
+ changes won't show up.
+ </P
+><P
+> That file gets automatically regenerated whenever it's more than an
+ hour old, so Bugzilla will eventually notice your changes by itself, but
+ generally you want it to notice right away, so that you can test things.
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><H2
+CLASS="SECTION"
+><A
+NAME="AEN948"
+>3.5.2. Upgrading From Previous Versions</A
+></H2
+><P
+> The developers of Bugzilla are constantly adding new tables, columns and
+ fields. You'll get SQL errors if you just update the code. The strategy
+ to update is to simply always run the checksetup.pl script whenever
+ you upgrade your installation of Bugzilla. If you want to see what has
+ changed, you can read the comments in that file, starting from the end.
+ </P
+><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"
+><H2
+CLASS="SECTION"
+><A
+NAME="HTACCESS"
+>3.5.3. <TT
+CLASS="FILENAME"
+>.htaccess</TT
+> files and security</A
+></H2
+><P
+> To enhance the security of your Bugzilla installation,
+ Bugzilla will generate
+ <I
+CLASS="GLOSSTERM"
+><TT
+CLASS="FILENAME"
+>.htaccess</TT
+></I
+> files
+ which the Apache webserver can use to restrict access to
+ the bugzilla data files. The checksetup script will
+ generate the <TT
+CLASS="FILENAME"
+>.htaccess</TT
+> files.
+
+ <DIV
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> If you are using an alternate provider of
+ <SPAN
+CLASS="PRODUCTNAME"
+>webdot</SPAN
+> services for graphing
+ (as described when viewing
+ <TT
+CLASS="FILENAME"
+>editparams.cgi</TT
+> in your web
+ browser), you will need to change the ip address in
+ <TT
+CLASS="FILENAME"
+>data/webdot/.htaccess</TT
+> to the ip
+ address of the webdot server that you are using.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+>
+
+ </P
+><P
+> If you are using Internet Information Server or other web
+ server which does not observe <TT
+CLASS="FILENAME"
+>.htaccess</TT
+>
+ conventions, you can disable their creation by editing
+ <TT
+CLASS="FILENAME"
+>localconfig</TT
+> and setting the
+ <TT
+CLASS="VARNAME"
+>$create_htaccess</TT
+> variable to
+ <TT
+CLASS="PARAMETER"
+><I
+>0</I
+></TT
+>.
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><H2
+CLASS="SECTION"
+><A
+NAME="MOD_THROTTLE"
+>3.5.4. <TT
+CLASS="FILENAME"
+>mod_throttle</TT
+> and Security</A
+></H2
+><P
+> 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 <TT
+CLASS="FILENAME"
+>mod_throttle</TT
+> which can limit
+ connections by ip-address. You may download this module at
+ <A
+HREF="http://www.snert.com/Software/Throttle/"
+TARGET="_top"
+>http://www.snert.com/Software/Throttle/</A
+>. Follow the instructions to install into your Apache install. <EM
+>This module only functions with the Apache web server!</EM
+>. You may use the <B
+CLASS="COMMAND"
+>ThrottleClientIP</B
+> command provided by this module to accomplish this goal. See the <A
+HREF="http://www.snert.com/Software/Throttle/"
+TARGET="_top"
+>Module Instructions</A
+> for more information. </P
+></DIV
+><DIV
+CLASS="SECTION"
+><H2
+CLASS="SECTION"
+><A
+NAME="CONTENT_TYPE"
+>3.5.5. Preventing untrusted Bugzilla content from executing malicious Javascript code</A
+></H2
+><P
+>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 <A
+HREF="http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3"
+TARGET="_top"
+>http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3</A
+>. 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. </P
+><P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>bash# cd $BUGZILLA_HOME; for i in `ls *.cgi`; \
+ do cat $i | sed 's/Content-type\: text\/html/Content-Type: text\/html\; charset=ISO-8859-1/' >$i.tmp; \
+ mv $i.tmp $i; done
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+></P
+><P
+> All this one-liner command does is search for all instances of
+ <SPAN
+CLASS="QUOTE"
+>"Content-type: text/html"</SPAN
+> and replaces it with
+ <SPAN
+CLASS="QUOTE"
+>"Content-Type: text/html; charset=ISO-8859-1"</SPAN
+>.
+ 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
+ <SPAN
+CLASS="QUOTE"
+>"ISO-8859-1"</SPAN
+>, above, to <SPAN
+CLASS="QUOTE"
+>"UTF-8"</SPAN
+>.
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><H2
+CLASS="SECTION"
+><A
+NAME="UNIXHISTORY"
+>3.5.6. UNIX Installation Instructions History</A
+></H2
+><P
+> This document was originally adapted from the Bonsai
+ installation instructions by Terry Weissman
+ <terry@mozilla.org>.
+ </P
+><P
+> The February 25, 1999 re-write of this page was done by Ry4an
+ Brase <ry4an@ry4an.org>, with some edits by Terry
+ Weissman, Bryce Nesbitt, Martin Pool, & Dan Mosedale (But
+ don't send bug reports to them; report them using bugzilla, at <A
+HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla"
+TARGET="_top"
+>http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla</A
+> ).
+ </P
+><P
+> This document was heavily modified again Wednesday, March 07
+ 2001 to reflect changes for Bugzilla 2.12 release by Matthew
+ P. Barnson. The securing MySQL section should be changed to
+ become standard procedure for Bugzilla installations.
+ </P
+><P
+> Finally, the README in its entirety was marked up in SGML and
+ included into the Guide on April 24, 2001 by Matt Barnson.
+ Since that time, it's undergone extensive modification as
+ Bugzilla grew.
+ </P
+><P
+> Comments from people using this Guide for the first time are
+ particularly welcome.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="bsdinstall.html"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="win32.html"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>BSD Installation Notes</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="installation.html"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Win32 Installation Notes</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file
diff --git a/docs/html/gfdl.html b/docs/html/gfdl.html
index 5cd6b47cc..dfb5c69da 100644
--- a/docs/html/gfdl.html
+++ b/docs/html/gfdl.html
@@ -4,14 +4,14 @@
>GNU Free Documentation License</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="PREVIOUS"
-TITLE="The Quicksearch Utility"
-HREF="quicksearch.html"><LINK
+TITLE="Hacking Bugzilla"
+HREF="bzhacking.html"><LINK
REL="NEXT"
TITLE="PREAMBLE"
HREF="gfdl_0.html"></HEAD
@@ -41,7 +41,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
-HREF="quicksearch.html"
+HREF="bzhacking.html"
>Prev</A
></TD
><TD
@@ -141,7 +141,7 @@ HREF="gfdl_howto.html"
><P
>Version 1.1, March 2000</P
><A
-NAME="AEN2019"
+NAME="AEN2499"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
@@ -167,7 +167,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
-HREF="quicksearch.html"
+HREF="bzhacking.html"
>Prev</A
></TD
><TD
@@ -192,7 +192,7 @@ HREF="gfdl_0.html"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
->The Quicksearch Utility</TD
+>Hacking Bugzilla</TD
><TD
WIDTH="34%"
ALIGN="center"
diff --git a/docs/html/gfdl_0.html b/docs/html/gfdl_0.html
index 376adafcd..899b444c1 100644
--- a/docs/html/gfdl_0.html
+++ b/docs/html/gfdl_0.html
@@ -4,7 +4,7 @@
>PREAMBLE</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
diff --git a/docs/html/gfdl_1.html b/docs/html/gfdl_1.html
index e54e987bb..0b4fb7dd8 100644
--- a/docs/html/gfdl_1.html
+++ b/docs/html/gfdl_1.html
@@ -4,7 +4,7 @@
>APPLICABILITY AND DEFINITIONS</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
diff --git a/docs/html/gfdl_10.html b/docs/html/gfdl_10.html
index 19469b513..7d0af2295 100644
--- a/docs/html/gfdl_10.html
+++ b/docs/html/gfdl_10.html
@@ -4,7 +4,7 @@
>FUTURE REVISIONS OF THIS LICENSE</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
diff --git a/docs/html/gfdl_2.html b/docs/html/gfdl_2.html
index c259dca1b..db838d948 100644
--- a/docs/html/gfdl_2.html
+++ b/docs/html/gfdl_2.html
@@ -4,7 +4,7 @@
>VERBATIM COPYING</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
diff --git a/docs/html/gfdl_3.html b/docs/html/gfdl_3.html
index e0d278085..35bf01eec 100644
--- a/docs/html/gfdl_3.html
+++ b/docs/html/gfdl_3.html
@@ -4,7 +4,7 @@
>COPYING IN QUANTITY</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
diff --git a/docs/html/gfdl_4.html b/docs/html/gfdl_4.html
index 6738204d0..ec3dbfc4e 100644
--- a/docs/html/gfdl_4.html
+++ b/docs/html/gfdl_4.html
@@ -4,7 +4,7 @@
>MODIFICATIONS</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
diff --git a/docs/html/gfdl_5.html b/docs/html/gfdl_5.html
index 9835eb4ca..c89a77a98 100644
--- a/docs/html/gfdl_5.html
+++ b/docs/html/gfdl_5.html
@@ -4,7 +4,7 @@
>COMBINING DOCUMENTS</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
diff --git a/docs/html/gfdl_6.html b/docs/html/gfdl_6.html
index fa3f2aa82..abb433e33 100644
--- a/docs/html/gfdl_6.html
+++ b/docs/html/gfdl_6.html
@@ -4,7 +4,7 @@
>COLLECTIONS OF DOCUMENTS</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
diff --git a/docs/html/gfdl_7.html b/docs/html/gfdl_7.html
index 94fad4c3c..b2aabea60 100644
--- a/docs/html/gfdl_7.html
+++ b/docs/html/gfdl_7.html
@@ -4,7 +4,7 @@
>AGGREGATION WITH INDEPENDENT WORKS</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
diff --git a/docs/html/gfdl_8.html b/docs/html/gfdl_8.html
index 8224c0c2c..6db660d9b 100644
--- a/docs/html/gfdl_8.html
+++ b/docs/html/gfdl_8.html
@@ -4,7 +4,7 @@
>TRANSLATION</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
diff --git a/docs/html/gfdl_9.html b/docs/html/gfdl_9.html
index b115424d4..2c59ccfb1 100644
--- a/docs/html/gfdl_9.html
+++ b/docs/html/gfdl_9.html
@@ -4,7 +4,7 @@
>TERMINATION</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
diff --git a/docs/html/gfdl_howto.html b/docs/html/gfdl_howto.html
index 8a7f15f58..775fca0c8 100644
--- a/docs/html/gfdl_howto.html
+++ b/docs/html/gfdl_howto.html
@@ -4,7 +4,7 @@
>How to use this License for your documents</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
@@ -78,7 +78,7 @@ NAME="GFDL_HOWTO"
a copy of the License in the document and put the following
copyright and license notices just after the title page:</P
><A
-NAME="AEN2109"
+NAME="AEN2589"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
diff --git a/docs/html/glossary.html b/docs/html/glossary.html
index 35c6df076..7f821c83b 100644
--- a/docs/html/glossary.html
+++ b/docs/html/glossary.html
@@ -4,7 +4,7 @@
>Glossary</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
@@ -68,17 +68,69 @@ CLASS="GLOSSDIV"
><H1
CLASS="GLOSSDIV"
><A
+NAME="AEN2594"
+>0-9, high ascii</A
+></H1
+><DL
+><DT
+><B
+>.htaccess</B
+></DT
+><DD
+><P
+> Apache web server, and other NCSA-compliant web servers,
+ observe the convention of using files in directories
+ called <TT
+CLASS="FILENAME"
+>.htaccess</TT
+> files. These
+ restrict parameters of the web server. In Bugzilla, they
+ are used to restrict access to certain files which would
+ otherwise compromise your installation. For instance, the
+ <TT
+CLASS="FILENAME"
+>localconfig</TT
+> file contains the
+ password to your database. If this information were
+ generally available, and remote access to your database
+ turned on, you risk corruption of your database by
+ computer criminals or the curious.
+ </P
+></DD
+></DL
+></DIV
+><DIV
+CLASS="GLOSSDIV"
+><H1
+CLASS="GLOSSDIV"
+><A
NAME="GLOSS_A"
>A</A
></H1
><DL
><DT
><B
->There are no entries for A</B
+>Apache</B
></DT
><DD
><P
-></P
+>In this context, Apache is the web server most
+ commonly used for serving up
+ <I
+CLASS="GLOSSTERM"
+>Bugzilla</I
+> pages. Contrary to
+ popular belief, the apache web server has nothing to do
+ with the ancient and noble Native American tribe, but
+ instead derived its name from the fact that it was
+ <SPAN
+CLASS="QUOTE"
+>"a patchy"</SPAN
+> version of the original
+ <SPAN
+CLASS="ACRONYM"
+>NCSA</SPAN
+> world-wide-web server.</P
></DD
></DL
></DIV
@@ -97,7 +149,21 @@ NAME="GLOSS_B"
></DT
><DD
><P
->A "Bug" in Bugzilla refers to an issue entered into the database which has an associated number, assignments, comments, etc. Many also refer to a "Ticket" or "Issue"; in this context, they are synonymous.</P
+> A <SPAN
+CLASS="QUOTE"
+>"Bug"</SPAN
+> in Bugzilla refers to an issue
+ entered into the database which has an associated number,
+ assignments, comments, etc. Some also refer to a
+ <SPAN
+CLASS="QUOTE"
+>"tickets"</SPAN
+> or <SPAN
+CLASS="QUOTE"
+>"issues"</SPAN
+>; in the
+ context of Bugzilla, they are synonymous.
+ </P
></DD
><DT
><B
@@ -105,7 +171,11 @@ NAME="GLOSS_B"
></DT
><DD
><P
->Each Bugzilla Bug is assigned a number that uniquely identifies that Bug. The Bug associated with a Bug Number can be pulled up via a query, or easily from the very front page by typing the number in the "Find" box.</P
+> Each Bugzilla Bug is assigned a number that uniquely
+ identifies that Bug. The Bug associated with a Bug Number
+ can be pulled up via a query, or easily from the very
+ front page by typing the number in the "Find" box.
+ </P
></DD
><DT
><B
@@ -113,7 +183,150 @@ NAME="GLOSS_B"
></DT
><DD
><P
->A Bug has stages through which it must pass before becoming a "closed bug", including acceptance, resolution, and verification. The "Bug Life Cycle" is moderately flexible according to the needs of the organization using it, though.</P
+>A Bug has stages through which it must pass before
+ becoming a <SPAN
+CLASS="QUOTE"
+>"closed bug"</SPAN
+>, including
+ acceptance, resolution, and verification. The <SPAN
+CLASS="QUOTE"
+>"Bug
+ Life Cycle"</SPAN
+> is moderately flexible according to
+ the needs of the organization using it, though.</P
+></DD
+><DT
+><B
+>Bugzilla</B
+></DT
+><DD
+><P
+> Bugzilla is the industry-standard bug tracking system. It
+ is quite popular among Open Source enthusiasts.
+ </P
+></DD
+></DL
+></DIV
+><DIV
+CLASS="GLOSSDIV"
+><H1
+CLASS="GLOSSDIV"
+><A
+NAME="GLOSS_C"
+></A
+></H1
+><DL
+><DT
+><A
+NAME="GLOSS_COMPONENT"
+><B
+>Component</B
+></A
+></DT
+><DD
+><P
+> A Component is a subsection of a Product. It should be a
+ narrow category, tailored to your organization. All
+ Products must contain at least one Component (and, as a
+ matter of fact, creating a Product with no Components will
+ create an error in Bugzilla).
+ </P
+></DD
+><DT
+><A
+NAME="GLOSS_CPAN"
+><B
+><SPAN
+CLASS="ACRONYM"
+>CPAN</SPAN
+></B
+></A
+></DT
+><DD
+><P
+><SPAN
+CLASS="ACRONYM"
+>CPAN</SPAN
+> stands for the
+ <SPAN
+CLASS="QUOTE"
+>"Comprehensive Perl Archive Network"</SPAN
+>. CPAN
+ maintains a large number of extremely useful
+ <I
+CLASS="GLOSSTERM"
+>Perl</I
+> modules. By themselves, Perl
+ modules generally do nothing, but when used as part of a
+ larger program, they provide much-needed algorithms and
+ functionality.</P
+></DD
+></DL
+></DIV
+><DIV
+CLASS="GLOSSDIV"
+><H1
+CLASS="GLOSSDIV"
+><A
+NAME="GLOSS_D"
+>D</A
+></H1
+><DL
+><DT
+><B
+>daemon</B
+></DT
+><DD
+><P
+>A daemon is a computer program which runs in the
+ background. In general, most daemons are started at boot
+ time via System V init scripts, or through RC scripts on
+ BSD-based systems. <I
+CLASS="GLOSSTERM"
+>mysqld</I
+>, the
+ MySQL server, and <I
+CLASS="GLOSSTERM"
+>apache</I
+>, a web
+ server, are generally run as daemons.</P
+></DD
+></DL
+></DIV
+><DIV
+CLASS="GLOSSDIV"
+><H1
+CLASS="GLOSSDIV"
+><A
+NAME="GLOSS_G"
+></A
+></H1
+><DL
+><DT
+><B
+>Groups</B
+></DT
+><DD
+><P
+>The word <SPAN
+CLASS="QUOTE"
+>"Groups"</SPAN
+> has a very special
+ meaning to Bugzilla. Bugzilla's main security mechanism
+ comes by lumping users into groups, and assigning those
+ groups certain privileges to
+ <I
+CLASS="GLOSSTERM"
+>Products</I
+> and
+ <I
+CLASS="GLOSSTERM"
+>Components</I
+> in the
+ <I
+CLASS="GLOSSTERM"
+>Bugzilla</I
+> database.</P
></DD
></DL
></DIV
@@ -135,12 +348,34 @@ NAME="GLOSS_INFINITELOOP"
></DT
><DD
><P
-><EM
->See: </EM
+>A loop of information that never ends; see recursion.</P
+></DD
+></DL
+></DIV
+><DIV
+CLASS="GLOSSDIV"
+><H1
+CLASS="GLOSSDIV"
><A
-HREF="glossary.html#GLOSS_RECURSION"
->Recursion</A
-></P
+NAME="GLOSS_M"
+>M</A
+></H1
+><DL
+><DT
+><B
+>mysqld</B
+></DT
+><DD
+><P
+>mysqld is the name of the
+ <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
></DD
></DL
></DIV
@@ -159,20 +394,74 @@ NAME="GLOSS_P"
></DT
><DD
><P
->A Product is a broad category of types of bugs. In general, there are several Components to a Product. A Product also defines a default Group (used for Bug Security) for all bugs entered into components beneath it.</P
+>A Product is a broad category of types of bugs. In
+ general, there are several Components to a Product. A
+ Product also defines a default Group (used for Bug
+ Security) for all bugs entered into components beneath
+ it.</P
><DIV
CLASS="EXAMPLE"
><A
-NAME="AEN2145"
+NAME="AEN2685"
></A
><P
><B
>Example 1. A Sample Product</B
></P
><P
->A company sells a software product called "X". They also maintain some older software called "Y", and have a secret project "Z". An effective use of Products might be to create Products "X", "Y", and "Z", each with Components "User Interface", "Database", and "Business Logic". They might also change group permissions so that only those people who are members of Group "Z" can see components and bugs under Product "Z".</P
+>A company sells a software product called
+ <SPAN
+CLASS="QUOTE"
+>"X"</SPAN
+>. They also maintain some older
+ software called <SPAN
+CLASS="QUOTE"
+>"Y"</SPAN
+>, and have a secret
+ project <SPAN
+CLASS="QUOTE"
+>"Z"</SPAN
+>. An effective use of Products
+ might be to create Products <SPAN
+CLASS="QUOTE"
+>"X"</SPAN
+>,
+ <SPAN
+CLASS="QUOTE"
+>"Y"</SPAN
+>, <SPAN
+CLASS="QUOTE"
+>"Z"</SPAN
+>, each with Components
+ of User Interface, Database, and Business Logic. They
+ might also change group permissions so that only those
+ people who are members of Group <SPAN
+CLASS="QUOTE"
+>"Z"</SPAN
+> can see
+ components and bugs under Product
+ <SPAN
+CLASS="QUOTE"
+>"Z"</SPAN
+>.</P
></DIV
></DD
+><DT
+><B
+>Perl</B
+></DT
+><DD
+><P
+>First written by Larry Wall, Perl is a remarkable
+ program language. It has the benefits of the flexibility
+ of an interpreted scripting language (such as shell
+ script), combined with the speed and power of a compiled
+ language, such as C. <I
+CLASS="GLOSSTERM"
+>Bugzilla</I
+> is
+ maintained in Perl.</P
+></DD
></DL
></DIV
><DIV
@@ -186,11 +475,33 @@ NAME="GLOSS_Q"
><DL
><DT
><B
->Q/A</B
+>QA</B
></DT
><DD
><P
->"Q/A" is short for "Quality Assurance". In most large software development organizations, there is a team devoted to ensuring the product meets minimum standards before shipping. This team will also generally want to track the progress of bugs over their life cycle, thus the need for the "Q/A Contact" field in a Bug.</P
+><SPAN
+CLASS="QUOTE"
+>"QA"</SPAN
+>, <SPAN
+CLASS="QUOTE"
+>"Q/A"</SPAN
+>, and
+ <SPAN
+CLASS="QUOTE"
+>"Q.A."</SPAN
+> are short for <SPAN
+CLASS="QUOTE"
+>"Quality
+ Assurance"</SPAN
+>. In most large software development
+ organizations, there is a team devoted to ensuring the
+ product meets minimum standards before shipping. This
+ team will also generally want to track the progress of
+ bugs over their life cycle, thus the need for the
+ <SPAN
+CLASS="QUOTE"
+>"QA Contact"</SPAN
+> field in a Bug.</P
></DD
></DL
></DIV
@@ -204,17 +515,123 @@ NAME="GLOSS_R"
></H1
><DL
><DT
+><A
+NAME="GLOSS_RECURSION"
><B
>Recursion</B
+></A
></DT
><DD
><P
-><EM
->See: </EM
+>The property of a function looking back at itself for
+ something. <SPAN
+CLASS="QUOTE"
+>"GNU"</SPAN
+>, for instance, stands for
+ <SPAN
+CLASS="QUOTE"
+>"GNU's Not UNIX"</SPAN
+>, thus recursing upon itself
+ for definition. For further clarity, see Infinite
+ Loop.</P
+></DD
+></DL
+></DIV
+><DIV
+CLASS="GLOSSDIV"
+><H1
+CLASS="GLOSSDIV"
><A
-HREF="glossary.html#GLOSS_INFINITELOOP"
->Infinite Loop</A
-></P
+NAME="GLOSS_S"
+>S</A
+></H1
+><DL
+><DT
+><B
+><SPAN
+CLASS="ACRONYM"
+>SGML</SPAN
+></B
+></DT
+><DD
+><P
+><SPAN
+CLASS="ACRONYM"
+>SGML</SPAN
+> stands for <SPAN
+CLASS="QUOTE"
+>"Standard
+ Generalized Markup Language"</SPAN
+>. Created in the
+ 1980's to provide an extensible means to maintain
+ documentation based upon content instead of presentation,
+ <SPAN
+CLASS="ACRONYM"
+>SGML</SPAN
+> has withstood the test of time as
+ a robust, powerful language.
+ <I
+CLASS="GLOSSTERM"
+><SPAN
+CLASS="ACRONYM"
+>XML</SPAN
+></I
+> is the
+ <SPAN
+CLASS="QUOTE"
+>"baby brother"</SPAN
+> of SGML; any valid
+ <SPAN
+CLASS="ACRONYM"
+>XML</SPAN
+> document it, by definition, a valid
+ <SPAN
+CLASS="ACRONYM"
+>SGML</SPAN
+> document. The document you are
+ reading is written and maintained in
+ <SPAN
+CLASS="ACRONYM"
+>SGML</SPAN
+>, and is also valid
+ <SPAN
+CLASS="ACRONYM"
+>XML</SPAN
+> if you modify the Document Type
+ Definition.</P
+></DD
+></DL
+></DIV
+><DIV
+CLASS="GLOSSDIV"
+><H1
+CLASS="GLOSSDIV"
+><A
+NAME="GLOSS_T"
+>T</A
+></H1
+><DL
+><DT
+><A
+NAME="GLOSS_TARGET_MILESTONE"
+><B
+>Target Milestone</B
+></A
+></DT
+><DD
+><P
+> Target Milestones are Product goals. They are
+ configurable on a per-Product basis. Most software
+ development houses have a concept of
+ <SPAN
+CLASS="QUOTE"
+>"milestones"</SPAN
+> where the people funding a
+ project expect certain functionality on certain dates.
+ Bugzilla facilitates meeting these milestones by giving
+ you the ability to declare by which milestone a bug will be
+ fixed, or an enhancement will be implemented.
+ </P
></DD
></DL
></DIV
@@ -228,12 +645,17 @@ NAME="GLOSS_Z"
></H1
><DL
><DT
+><A
+NAME="ZARRO-BOOGS-FOUND"
><B
>Zarro Boogs Found</B
+></A
></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 the cryptic response sent by Bugzilla when a
+ query returned no results. It is just a goofy way of
+ saying "Zero Bugs Found".</P
></DD
></DL
></DIV
diff --git a/docs/html/granttables.html b/docs/html/granttables.html
index 779e9d311..2c5147270 100644
--- a/docs/html/granttables.html
+++ b/docs/html/granttables.html
@@ -4,7 +4,7 @@
>MySQL Permissions & Grant Tables</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
@@ -16,8 +16,8 @@ REL="PREVIOUS"
TITLE="MySQL Bugzilla Database Introduction"
HREF="dbdoc.html"><LINK
REL="NEXT"
-TITLE="Cleaning up after mucking with Bugzilla"
-HREF="cleanupwork.html"></HEAD
+TITLE="Useful Patches and Utilities for Bugzilla"
+HREF="patches.html"></HEAD
><BODY
CLASS="SECTION"
BGCOLOR="#FFFFFF"
@@ -57,7 +57,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
-HREF="cleanupwork.html"
+HREF="patches.html"
>Next</A
></TD
></TR
@@ -75,19 +75,46 @@ NAME="GRANTTABLES"
></H1
><DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><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
-><B
->Note: </B
->The following portion of documentation comes from my answer to an old discussion of Keystone,
- a cool product that does trouble-ticket tracking for IT departments. I wrote this post to the
- Keystone support group regarding MySQL grant table permissions, and how to use them effectively.
- It is badly in need of updating, as I believe MySQL has added a field or two to the grant tables
- since this time, but it serves as a decent introduction and troubleshooting document for grant
- table issues. I used Keynote to track my troubles until I discovered Bugzilla,
- which gave me a whole new set of troubles to work on : )</P
-></BLOCKQUOTE
+>The following portion of documentation comes from my
+ answer to an old discussion of Keystone, a cool product that
+ does trouble-ticket tracking for IT departments. I wrote this
+ post to the Keystone support group regarding MySQL grant
+ table permissions, and how to use them effectively. It is
+ badly in need of updating, as I believe MySQL has added a
+ field or two to the grant tables since this time, but it
+ serves as a decent introduction and troubleshooting document
+ for grant table issues. I used Keynote to track my troubles
+ until I discovered Bugzilla, which gave me a whole new set of
+ troubles to work on : ) Although it is of limited use, it
+ still has SOME use, thus it's still included.</P
+><P
+> Please note, however, that I was a relatively new user to
+ MySQL at the time. Some of my suggestions, particularly in
+ how to set up security, showed a terrible lack of
+ security-related database experience.
+ </P
+></TD
+></TR
+></TABLE
></DIV
><P
CLASS="LITERALLAYOUT"
@@ -253,19 +280,6 @@ Once again, you can't go wrong by reading&nbs
is more detailed than I!<br>
http://www.mysql.com/Manual/manual.html.<br>
<br>
-----------------------------------------------------------------------------<br>
-10/12/2000<br>
-Matthew sent in some mail with updated contact information:<br>
-NEW CONTACT INFORMATION: <br>
-<br>
- ------------------------ <br>
- Matthew P. Barnson <br>
- Manager, Systems Administration <br>
- Excite@Home Business Applications <br>
- mbarnson@excitehome.net <br>
- (801)234-8300 <br>
-<br>
-<br>
</P
></DIV
><DIV
@@ -299,7 +313,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
-HREF="cleanupwork.html"
+HREF="patches.html"
>Next</A
></TD
></TR
@@ -321,7 +335,7 @@ HREF="database.html"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
->Cleaning up after mucking with Bugzilla</TD
+>Useful Patches and Utilities for Bugzilla</TD
></TR
></TABLE
></DIV
diff --git a/docs/html/how.html b/docs/html/how.html
index 60ad56e55..cad748643 100644
--- a/docs/html/how.html
+++ b/docs/html/how.html
@@ -4,7 +4,7 @@
>How do I use Bugzilla?</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
@@ -16,7 +16,7 @@ REL="PREVIOUS"
TITLE="Why Should We Use Bugzilla?"
HREF="why.html"><LINK
REL="NEXT"
-TITLE="What's in it for me?"
+TITLE="Where can I find my user preferences?"
HREF="init4me.html"></HEAD
><BODY
CLASS="SECTION"
@@ -51,7 +51,7 @@ HREF="why.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
->Chapter 4. Using Bugzilla</TD
+>Chapter 2. Using Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
@@ -71,7 +71,7 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="HOW"
->4.3. How do I use Bugzilla?</A
+>2.3. How do I use Bugzilla?</A
></H1
><TABLE
BORDER="0"
@@ -98,51 +98,66 @@ VALIGN="TOP"
></TABLE
><P
> Bugzilla is a large, complex system. Describing how to use it
- requires some time. If you are only interested in installing or administering
- a Bugzilla installation, please consult the Installing and Administering
- Bugzilla portions of this Guide. This section is principally aimed towards
- developing end-user mastery of Bugzilla, so you may fully enjoy the benefits
- afforded by using this reliable open-source bug-tracking software.
+ requires some time. If you are only interested in installing or
+ administering a Bugzilla installation, please consult the
+ Installing and Administering Bugzilla portions of this Guide.
+ This section is principally aimed towards developing end-user
+ mastery of Bugzilla, so you may fully enjoy the benefits
+ afforded by using this reliable open-source bug-tracking
+ software.
</P
><P
-> Throughout this portion of the Guide, we will refer to user account
- options available at the Bugzilla test installation,
+> Throughout this portion of the Guide, we will refer to user
+ account options available at the Bugzilla test installation,
<A
HREF="http://landfill.tequilarista.org/"
TARGET="_top"
-> landfill.tequilarista.org</A
+> landfill.tequilarista.org</A
>.
<DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><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
-><B
->Note: </B
-> Some people have run into difficulties completing this tutorial. If
- you run into problems, please check the updated, online documentation available
- at <A
+> Some people have run into difficulties completing this
+ tutorial. If you run into problems, please check the
+ updated online documentation available at <A
HREF="http://www.trilobyte.net/barnsons/"
TARGET="_top"
>http://www.trilobyte.net/barnsons</A
->.
- If you're still stumped, please subscribe to the newsgroup and provide details of exactly
- what's stumping you! If enough people complain, I'll have to fix it in the next
- version of this Guide. You can subscribe to the newsgroup at
- <A
+>. If you're still stumped, please subscribe to the newsgroup and provide details of exactly what's stumping you! If enough people complain, I'll have to fix it in the next version of this Guide. You can subscribe to the newsgroup at <A
HREF="news://news.mozilla.org/netscape.public.mozilla.webtools"
TARGET="_top"
-> news://news.mozilla.org/netscape.public.mozilla.webtools</A
+> news://news.mozilla.org/netscape.public.mozilla.webtools</A
>
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
->
- Although Landfill serves as a great introduction to Bugzilla, it does not offer
- all the options you would have as a user on your own installation of Bugzilla,
- nor can it do more than serve as a general introduction to Bugzilla. Additionally,
- Landfill often runs cutting-edge versions of Bugzilla for testing, so some things
- may work slightly differently than mentioned here.
+> Although Landfill serves as a great introduction to
+ Bugzilla, it does not offer all the options you would have as a
+ user on your own installation of Bugzilla, nor can it do more
+ than serve as a general introduction to Bugzilla. Additionally,
+ Landfill often runs cutting-edge versions of Bugzilla for
+ testing, so some things may work slightly differently than
+ mentioned here.
</P
><DIV
CLASS="SECTION"
@@ -150,17 +165,17 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="MYACCOUNT"
->4.3.1. Create a Bugzilla Account</A
+>2.3.1. Create a Bugzilla Account</A
></H2
><P
-> First thing's first! 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 the end-user Bugzilla experience, use this URL:
- <A
-HREF="http://landfill.tequilarista.org/mozilla/bugzilla/"
+> First things first! 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 the end-user
+ Bugzilla experience, use this URL: <A
+HREF="http://landfill.tequilarista.org/bugzilla-tip/"
TARGET="_top"
-> http://landfill.tequilarista.org/mozilla/bugzilla/</A
+> http://landfill.tequilarista.org/bugzilla-tip/</A
>
</P
><P
@@ -174,35 +189,76 @@ TYPE="1"
></LI
><LI
><P
-> Enter your "E-mail address" and "Real Name" (or whatever name you want to call yourself)
- in the spaces provided, then select the "Create Account" button.
+> Enter your "E-mail address" and "Real Name" (or whatever
+ name you want to call yourself) in the spaces provided,
+ then select the "Create Account" button.
</P
></LI
><LI
><P
-> Within 5-10 minutes, you should receive an email to the address you provided above,
- which contains your login name (generally the same as the email address), and
- a password you can use to access your account. This password is randomly generated,
- and should be changed at your nearest opportunity (we'll go into how to do it later).
+> Within moments, you should receive an email to the address
+ you provided above, which contains your login name
+ (generally the same as the email address), and a password
+ you can use to access your account. This password is
+ randomly generated, and should be changed at your nearest
+ opportunity (we'll go into how to do it later).
</P
></LI
><LI
><P
-> Click the "Log In" link in the yellow area at the bottom of the page in your browser,
- then enter your "E-mail address" and "Password" you just received into the spaces provided,
- and select "Login".
+> Click the <SPAN
+CLASS="QUOTE"
+>"Log In"</SPAN
+> link in the yellow area at
+ the bottom of the page in your browser, then enter your
+ <SPAN
+CLASS="QUOTE"
+>"E-mail address"</SPAN
+> and <SPAN
+CLASS="QUOTE"
+>"Password"</SPAN
+>
+ you just received into the spaces provided, and select
+ <SPAN
+CLASS="QUOTE"
+>"Login"</SPAN
+>.
<DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><P
+></P
+><TABLE
CLASS="NOTE"
+WIDTH="90%"
+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
-><B
->Note: </B
-> If you ever forget your password, you can come back to this page, enter your
- "E-mail address", then select the "E-mail me a password" button to have your password
- mailed to you again so that you can login.
+> If you ever forget your password, you can come back to
+ this page, enter your <SPAN
+CLASS="QUOTE"
+>"E-mail address"</SPAN
+>,
+ then select the <SPAN
+CLASS="QUOTE"
+>"E-mail me a password"</SPAN
+>
+ button to have your password mailed to you again so
+ that you can login.
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
>
<DIV
@@ -211,24 +267,36 @@ CLASS="CAUTION"
></P
><TABLE
CLASS="CAUTION"
-BORDER="1"
WIDTH="90%"
+BORDER="0"
><TR
><TD
+WIDTH="25"
ALIGN="CENTER"
-><B
->Caution</B
-></TD
-></TR
-><TR
+VALIGN="TOP"
+><IMG
+SRC="../images/caution.gif"
+HSPACE="5"
+ALT="Caution"></TD
><TD
ALIGN="LEFT"
+VALIGN="TOP"
><P
-> Many modern browsers include an "Auto-Complete" or "Form Fill" feature to
- remember the user names and passwords you type in at many sites. Unfortunately,
- sometimes they attempt to "guess" what you will put in as your password, and guess
- wrong. If you notice a text box is already filled out, please overwrite the contents
- of the text box so you can be sure to input the correct information.
+> Many modern browsers include an
+ <SPAN
+CLASS="QUOTE"
+>"Auto-Complete"</SPAN
+> or <SPAN
+CLASS="QUOTE"
+>"Form
+ Fill"</SPAN
+> feature to remember the user names and
+ passwords you type in at many sites. Unfortunately,
+ sometimes they attempt to guess what you will put in
+ as your password, and guess wrong. If you notice a
+ text box is already filled out, please overwrite the
+ contents of the text box so you can be sure to input
+ the correct information.
</P
></TD
></TR
@@ -239,11 +307,15 @@ ALIGN="LEFT"
></LI
></OL
><P
-> Congratulations! If you followed these directions, you now are the
- proud owner of a user account on landfill.tequilarista.org (Landfill) or
- your local Bugzilla install. You should now see in your browser a
- page called the "Bugzilla Query Page". It may look daunting, but
- with this Guide to walk you through it, you will master it in no time.
+> Congratulations! If you followed these directions, you now
+ are the proud owner of a user account on
+ landfill.tequilarista.org (Landfill) or your local Bugzilla
+ install. You should now see in your browser a page called the
+ <SPAN
+CLASS="QUOTE"
+>"Bugzilla Query Page"</SPAN
+>. It may look daunting, but with this
+ Guide to walk you through it, you will master it in no time.
</P
></DIV
><DIV
@@ -252,19 +324,30 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="QUERY"
->4.3.2. The Bugzilla Query Page</A
+>2.3.2. The Bugzilla Query Page</A
></H2
><P
-> The Bugzilla Query Page is the heart and soul of Bugzilla. It is the master
- interface where you can find any bug report, comment, or patch currently in the Bugzilla
- system. We'll go into how to create your own bug report later on.
+> The Bugzilla Query Page is the heart and soul of the Bugzilla
+ user experience. It is the master interface where you can
+ find any bug report, comment, or patch currently in the
+ Bugzilla system. We'll go into how to create your own bug
+ report later on.
</P
><P
-> There are efforts underway to simplify query usage. If you have a local installation
- of Bugzilla 2.12 or higher, you should have "quicksearch.html" available
- to use and simplify your searches. There is also, or shortly will be, a helper
- for the query interface, called "queryhelp.cgi". Landfill tends to run the latest code,
- so these two utilities should be available there for your perusal.
+> There are efforts underway to simplify query usage. If you
+ have a local installation of Bugzilla 2.12 or higher, you
+ should have <TT
+CLASS="FILENAME"
+>quicksearch.html</TT
+> available to
+ use and simplify your searches. There is also a helper for
+ the query interface, called
+ <TT
+CLASS="FILENAME"
+>queryhelp.cgi</TT
+>. Landfill tends to run the
+ latest code, so these two utilities should be available there
+ for your perusal.
</P
><P
> At this point, please visit the main Bugzilla site,
@@ -275,23 +358,32 @@ TARGET="_top"
>, to see a more fleshed-out query page.
</P
><P
-> The first thing you need to notice about the Bugzilla Query Page is that
- nearly every box you see on your screen has a hyperlink nearby, explaining what
- it is or what it does. Near the upper-left-hand corner of your browser window
- you should see the word "Status" underlined. Select it.
+> The first thing you need to notice about the Bugzilla Query
+ Page is that nearly every box you see on your screen has a
+ hyperlink nearby, explaining what it is or what it does. Near
+ the upper-left-hand corner of your browser window you should
+ see the word <SPAN
+CLASS="QUOTE"
+>"Status"</SPAN
+> underlined. Select it.
</P
><P
-> Notice the page that popped up? Every underlined word you see on your screen
- is a hyperlink that will take you to context-sensitive help.
- Click around for a while, and learn what everything here does. To return
- to the query interface after pulling up a help page, use the "Back" button in
- your browser.
+> Notice the page that popped up? Every underlined word you see
+ on your screen is a hyperlink that will take you to
+ context-sensitive help. Click around for a while, and learn
+ what everything here does. To return to the query interface
+ after pulling up a help page, use the <SPAN
+CLASS="QUOTE"
+>"Back"</SPAN
+>
+ button in your browser.
</P
><P
-> I'm sure that after checking out the online help, you are now an Expert
- on the Bugzilla Query Page. If, however, you feel you haven't mastered it yet,
- let me walk you through making a few successful queries to find out what there
- are in the Bugzilla bug-tracking system itself.
+> I'm sure that after checking out the online help, you are now
+ an expert on the Bugzilla Query Page. If, however, you feel
+ you haven't mastered it yet, let me walk you through making a
+ few successful queries to find out what there are in the
+ Bugzilla bug-tracking system itself.
</P
><P
></P
@@ -299,27 +391,37 @@ TARGET="_top"
TYPE="1"
><LI
><P
-> Ensure you are back on the "Bugzilla Query Page"
- Do nothing in the boxes marked "Status", "Resolution", "Platform", "OpSys",
- "Priority", or "Severity". The default query for "Status" is to find all bugs that
- are NEW, ASSIGNED, or REOPENED, which is what we want. If you don't select anything
- in the other 5 scrollboxes there, then you are saying that "any of these are OK";
- we're not locking ourselves into only finding bugs on the "DEC" Platform, or "Windows 95"
- OpSys (Operating System). You're smart, I think you have it figured out.
+> Ensure you are back on the <SPAN
+CLASS="QUOTE"
+>"Bugzilla Query
+ Page"</SPAN
+>. Do nothing in the boxes marked "Status",
+ "Resolution", "Platform", "OpSys", "Priority", or
+ "Severity". The default query for "Status" is to find all
+ bugs that are NEW, ASSIGNED, or REOPENED, which is what we
+ want. If you don't select anything in the other 5
+ scrollboxes there, then you are saying that "any of these
+ are OK"; we're not locking ourselves into only finding
+ bugs on the "DEC" Platform, or "Windows 95" OpSys
+ (Operating System). You're smart, I think you have it
+ figured out.
</P
><P
> Basically, selecting <EM
>anything</EM
-> on the query page narrows your search
- down. Leaving stuff unselected, or text boxes unfilled, broadens your search!
+> on the
+ query page narrows your search down. Leaving stuff
+ unselected, or text boxes unfilled, broadens your search.
</P
></LI
><LI
><P
-> You see the box immediately below the top six boxes that contains an "Email" text box,
- with the words "matching as", a drop-down selection box, then some checkboxes with
- "Assigned To" checked by default? This allows you to filter your search down based upon
- email address. Let's put my email address in there, and see what happens.
+> You see the box immediately below the top six boxes that
+ contains an "Email" text box, with the words "matching
+ as", a drop-down selection box, then some checkboxes with
+ "Assigned To" checked by default? This allows you to
+ filter your search down based upon email address. Let's
+ put my email address in there, and see what happens.
</P
><P
> Type "barnboy@trilobyte.net" in the top Email text box.
@@ -327,68 +429,76 @@ TYPE="1"
></LI
><LI
><P
-> Let's narrow the search some more. Scroll down until you find the box with the word
- "Program" over the top of it. This is where we can narrow our search down to only
- specific products (software programs or product lines) in our Bugzilla database.
- Please notice the box is a <EM
+> Let's narrow the search some more. Scroll down until you
+ find the box with the word "Program" over the top of it.
+ This is where we can narrow our search down to only
+ specific products (software programs or product lines) in
+ our Bugzilla database. Please notice the box is a
+ <EM
>scrollbox</EM
->. Using the down arrow on the
- scrollbox, scroll down until you can see an entry called "Webtools". Select this entry.
+>. Using the down arrow on
+ the scrollbox, scroll down until you can see an entry
+ called "Bugzilla". Select this entry.
</P
></LI
><LI
><P
-> Did you notice that some of the boxes to the right changed when you selected "Webtools"?
- Every Program (or Product) has different Versions, Components, and Target Milestones associated
- with it. A "Version" is the number of a software program.
+> Did you notice that some of the boxes to the right changed
+ when you selected "Bugzilla"? Every Program (or Product)
+ has different Versions, Components, and Target Milestones
+ associated with it. A "Version" is the number of a
+ software program.
<DIV
CLASS="EXAMPLE"
><A
-NAME="AEN1095"
+NAME="AEN307"
></A
><P
><B
->Example 4-1. Some Famous Software Versions</B
+>Example 2-1. Some Famous Software Versions</B
></P
><DIV
CLASS="INFORMALEXAMPLE"
><A
-NAME="AEN1097"
+NAME="AEN309"
></A
><P
></P
><P
-> Do you remember the hype in 1995 when Microsoft Windows 95(r) was released?
- It may have been several years
- ago, but Microsoft(tm) spent over $300 Million advertising this new Version of their
- software. Three years later, they released Microsoft Windows 98(r),
- another new version, to great fanfare, and then in 2000 quietly
- released Microsoft Windows ME(Millenium Edition)(r).
+> Do you remember the hype in 1995 when Microsoft
+ Windows 95(r) was released? It may have been several
+ years ago, but Microsoft(tm) spent over $300 Million
+ advertising this new Version of their software.
+ Three years later, they released Microsoft Windows
+ 98(r), another new version, to great fanfare, and
+ then in 2000 quietly released Microsoft Windows
+ ME(Millenium Edition)(r).
</P
><P
-> Software "Versions" help a manufacturer differentiate
- their current product from their
- previous products. Most do not identify their products
- by the year they were released.
- Instead, the "original" version of their software will
- often be numbered "1.0", with
- small bug-fix releases on subsequent tenths of a digit. In most cases, it's not
- a decimal number; for instance, often 1.9 is an <EM
+> Software "Versions" help a manufacturer
+ differentiate their current product from their
+ previous products. Most do not identify their
+ products by the year they were released. Instead,
+ the "original" version of their software will often
+ be numbered "1.0", with small bug-fix releases on
+ subsequent tenths of a digit. In most cases, it's
+ not a decimal number; for instance, often 1.9 is an
+ <EM
>older</EM
-> version
- of the software than 1.11,
- but is a <EM
+> version of the software
+ than 1.11, but is a <EM
>newer</EM
-> version than 1.1.1.
+>
+ version than 1.1.1.
</P
><P
-> In general, a "Version" in Bugzilla should refer to
+> In general, a "Version" in Bugzilla should refer to
<EM
>released</EM
->
- products, not products that have not yet been released
- to the public. Forthcoming products
- are what the Target Milestone field is for.
+> products, not products
+ that have not yet been released to the public.
+ Forthcoming products are what the Target Milestone
+ field is for.
</P
><P
></P
@@ -405,21 +515,21 @@ NAME="AEN1097"
<DIV
CLASS="EXAMPLE"
><A
-NAME="AEN1105"
+NAME="AEN317"
></A
><P
><B
->Example 4-2. Mozilla Webtools Components</B
+>Example 2-2. Mozilla's Bugzilla Components</B
></P
><DIV
CLASS="INFORMALEXAMPLE"
><A
-NAME="AEN1107"
+NAME="AEN319"
></A
><P
></P
><P
-> Mozilla's "Webtools" Product is composed of several pieces (Components):
+> Mozilla's "Bugzilla" Product is composed of several pieces (Components):
<P
></P
><TABLE
@@ -428,60 +538,166 @@ BORDER="0"
><TR
><TD
><EM
->Bonsai</EM
+>Administration</EM
>,
- a tool to show recent changes to Mozilla</TD
+ Administration of a bugzilla installation, including
+ <TT
+CLASS="FILENAME"
+>editcomponents.cgi</TT
+>,
+ <TT
+CLASS="FILENAME"
+>editgroups.cgi</TT
+>,
+ <TT
+CLASS="FILENAME"
+>editkeywords.cgi</TT
+>,
+ <TT
+CLASS="FILENAME"
+>editparams.cgi</TT
+>,
+ <TT
+CLASS="FILENAME"
+>editproducts.cgi</TT
+>,
+ <TT
+CLASS="FILENAME"
+>editusers.cgi</TT
+>,
+ <TT
+CLASS="FILENAME"
+>editversions.cgi,</TT
+> and
+ <TT
+CLASS="FILENAME"
+>sanitycheck.cgi</TT
+>.
+ </TD
></TR
><TR
><TD
><EM
->Bugzilla</EM
+>Bugzilla-General</EM
>,
- a defect-tracking tool</TD
+ Anything that doesn't fit in the other components, or spans
+ multiple components.
+ </TD
></TR
><TR
><TD
><EM
->Build</EM
+>Creating/Changing Bugs</EM
+>,
+ Creating, changing, and viewing bugs.
+ <TT
+CLASS="FILENAME"
+>enter_bug.cgi</TT
+>,
+ <TT
+CLASS="FILENAME"
+>post_bug.cgi</TT
>,
- a tool to automatically compile source code
- into machine-readable form</TD
+ <TT
+CLASS="FILENAME"
+>show_bug.cgi</TT
+> and
+ <TT
+CLASS="FILENAME"
+>process_bug.cgi</TT
+>.
+ </TD
></TR
><TR
><TD
><EM
->Despot</EM
+>Documentation</EM
>,
- a program that controls access to the other Webtools</TD
+ The bugzilla documentation, including anything in the
+ <TT
+CLASS="FILENAME"
+>docs/</TT
+> directory and The Bugzilla Guide
+ (This document :)
+ </TD
></TR
><TR
><TD
><EM
->LXR</EM
+>Email</EM
>,
- a utility that automatically marks up text files
- to make them more readable</TD
+ Anything to do with email sent by Bugzilla.
+ <TT
+CLASS="FILENAME"
+>processmail</TT
+>
+ </TD
></TR
><TR
><TD
><EM
->MozBot</EM
+>Installation</EM
>,
- a "robot" that announces changes to Mozilla in Chat</TD
+ The installation process of Bugzilla. This includes
+ <TT
+CLASS="FILENAME"
+>checksetup.pl</TT
+> and whatever else it evolves into.
+ </TD
></TR
><TR
><TD
><EM
->TestManager</EM
+>Query/Buglist</EM
>,
- a tool to help find bugs in Mozilla</TD
+ Anything to do with searching for bugs and viewing the buglists.
+ <TT
+CLASS="FILENAME"
+>query.cgi</TT
+> and
+ <TT
+CLASS="FILENAME"
+>buglist.cgi</TT
+>
+ </TD
></TR
><TR
><TD
><EM
->Tinderbox</EM
+>Reporting/Charting</EM
>,
- which displays reports from Build</TD
+ Getting reports from Bugzilla.
+ <TT
+CLASS="FILENAME"
+>reports.cgi</TT
+> and
+ <TT
+CLASS="FILENAME"
+>duplicates.cgi</TT
+>
+ </TD
+></TR
+><TR
+><TD
+><EM
+>User Accounts</EM
+>,
+ Anything about managing a user account from the user's perspective.
+ <TT
+CLASS="FILENAME"
+>userprefs.cgi</TT
+>, saved queries, creating accounts,
+ changing passwords, logging in, etc.
+ </TD
+></TR
+><TR
+><TD
+><EM
+>User Interface</EM
+>,
+ General issues having to do with the user interface cosmetics (not
+ functionality) including cosmetic issues, HTML templates, etc.
+ </TD
></TR
></TBODY
></TABLE
@@ -490,37 +706,31 @@ BORDER="0"
>
</P
><P
-> A different person is responsible for each of these Components.
- Tara Hernandez keeps
- the "Bugzilla" component up-to-date.
- </P
-><P
></P
></DIV
></DIV
>
</P
><P
-> A "Milestone", or "Target Milestone" is a often a planned future "Version" of a
- product. In many cases, though, Milestones simply represent significant dates for
- a developer. Having certain features in your Product is frequently
- tied to revenue (money)
- the developer will receive if the features work by the time she
- reaches the Target Milestone.
- Target Milestones are a great tool to organize your time.
- If someone will pay you $100,000 for
- incorporating certain features by a certain date,
- those features by that Milestone date become
- a very high priority. Milestones tend to be highly malleable creatures,
- though, that appear
- to be in reach but are out of reach by the time the important day arrives.
+> A "Milestone", or "Target Milestone" is a often a planned
+ future "Version" of a product. In many cases, though,
+ Milestones simply represent significant dates for a
+ developer. Having certain features in your Product is
+ frequently tied to revenue (money) the developer will
+ receive if the features work by the time she reaches the
+ Target Milestone. Target Milestones are a great tool to
+ organize your time. If someone will pay you $100,000 for
+ incorporating certain features by a certain date, those
+ features by that Milestone date become a very high
+ priority. Milestones tend to be highly malleable
+ creatures, though, that appear to be in reach but are out
+ of reach by the time the important day arrives.
</P
><P
-> The Bugzilla Project has set up Milestones for future
- Bugzilla versions 2.14, 2.16, 2.18, 3.0, etc. However,
- a Target Milestone can just as easily be a specific date,
- code name, or weird alphanumeric
- combination, like "M19".
+> The Bugzilla Project has set up Milestones for future
+ Bugzilla versions 2.14, 2.16, 2.18, 3.0, etc. However, a
+ Target Milestone can just as easily be a specific date,
+ code name, or weird alphanumeric combination, like "M19".
</P
></LI
><LI
@@ -537,25 +747,25 @@ BORDER="0"
></LI
><LI
><P
-> Congratulations! You've completed your first Query, and have before you the Bug List
- of the author of this Guide, Matthew P. Barnson (barnboy@trilobyte.net). If I'm
- doing well,
- you'll have a cryptic "Zarro Boogs Found" message on your screen. It is just
- a happy hacker's way of saying "Zero Bugs Found". However, I am fairly certain I will
+> Congratulations! You've completed your first Query, and
+ have before you the Bug List of the author of this Guide,
+ Matthew P. Barnson (barnboy@trilobyte.net). If I'm doing
+ well, you'll have a cryptic "Zarro Boogs Found" message on
+ your screen. It is just a happy hacker's way of saying
+ "Zero Bugs Found". However, I am fairly certain I will
always have some bugs assigned to me that aren't done yet,
so you won't often see that message!
</P
></LI
></OL
><P
-> I encourage you to click the bug numbers in the left-hand column and examine
- my bugs. Also notice that if you click the underlined
- links near the top of this page, they do
- not take you to context-sensitive help here,
- but instead sort the columns of bugs on the screen!
- When you need to sort your bugs by priority, severity,
- or the people they are assigned to, this
- is a tremendous timesaver.
+> I encourage you to click the bug numbers in the left-hand
+ column and examine my bugs. Also notice that if you click the
+ underlined links near the top of this page, they do not take
+ you to context-sensitive help here, but instead sort the
+ columns of bugs on the screen! When you need to sort your bugs
+ by priority, severity, or the people they are assigned to,
+ this is a tremendous timesaver.
</P
><P
> A couple more interesting things about the Bug List page:
@@ -568,37 +778,37 @@ BORDER="0"
><TD
><EM
>Change Columns</EM
->:
- by selecting this link, you can show all kinds
- of information in the Bug List</TD
+>: by selecting
+ this link, you can show all kinds of information in the
+ Bug List</TD
></TR
><TR
><TD
><EM
>Change several bugs at once</EM
->:
- If you have sufficient rights to change all
- the bugs shown in the Bug List, you can mass-modify them.
- This is a big time-saver.</TD
+>: If
+ you have sufficient rights to change all the bugs shown in
+ the Bug List, you can mass-modify them. This is a big
+ time-saver.</TD
></TR
><TR
><TD
><EM
>Send mail to bug owners</EM
->:
- If you have many related bugs, you can request
- an update from every person who owns the bugs in
- the Bug List asking them the status.</TD
+>: If you
+ have many related bugs, you can request an update from
+ every person who owns the bugs in the Bug List asking them
+ the status.</TD
></TR
><TR
><TD
><EM
>Edit this query</EM
->:
- If you didn't get exactly the results you were looking for,
- you can return to the Query page through this link and make
- small revisions to the query you just made so
- you get more accurate results.</TD
+>: If you didn't
+ get exactly the results you were looking for, you can
+ return to the Query page through this link and make small
+ revisions to the query you just made so you get more
+ accurate results.</TD
></TR
></TBODY
></TABLE
@@ -608,24 +818,37 @@ BORDER="0"
</P
><DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><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
-><B
->Note: </B
-> There are many more options to the Bugzilla Query Page
- and the Bug List than I have shown you.
- But this should be enough for you to learn to get around.
- I encourage you to check out the
- <A
+> There are many more options to the Bugzilla Query Page and
+ the Bug List than I have shown you. But this should be
+ enough for you to learn to get around. I encourage you to
+ check out the <A
HREF="http://www.mozilla.org/bugs/"
TARGET="_top"
>Bugzilla Home Page</A
->
- to learn about the Anatomy
- and Life Cycle of a Bug before continuing.
+> to learn about the Anatomy and Life Cycle of a Bug before continuing.
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
></DIV
><DIV
@@ -634,7 +857,7 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="BUGREPORTS"
->4.3.3. Creating and Managing Bug Reports</A
+>2.3.3. Creating and Managing Bug Reports</A
></H2
><TABLE
BORDER="0"
@@ -667,33 +890,36 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="BUG_WRITING"
->4.3.3.1. Writing a Great Bug Report</A
+>2.3.3.1. Writing a Great Bug Report</A
></H3
><P
-> Before we plunge into writing your first bug report, I encourage you to read
- <A
+> Before we plunge into writing your first bug report, I
+ encourage you to read some bug-writing guidelines. If you
+ are reading this document as part of a Bugzilla CVS checkout
+ or un-tarred Bugzilla distribution, you should be able to
+ read them by clicking <A
+HREF="../../bugwritinghelp.html"
+TARGET="_top"
+>here</A
+>. If you are reading this online, check out the Mozilla.org bug-writing guidelines at <A
HREF="http://www.mozilla.org/quality/bug-writing-guidelines.html"
TARGET="_top"
->Mozilla.org's Bug
- Writing Guidelines</A
->. 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.
+>http://www.mozilla.org/quality/bug-writing-guidelines.html</A
+>. While some of the advice is Mozilla-specific, the basic principles of reporting Reproducible, Specific bugs, isolating the Product you are using, the Version of the Product, the Component which failed, the Hardware Platform, and Operating System you were using at the time of the failure go a long way toward ensuring accurate, responsible fixes for the bug that bit you.
</P
><P
-> While you are at it, why not learn how to find previously reported bugs? Mozilla.org
- has published a great tutorial on finding duplicate bugs, available at
- <A
+> While you are at it, why not learn how to find previously
+ reported bugs? Mozilla.org has published a great tutorial
+ on finding duplicate bugs, available at <A
HREF="http://www.mozilla.org/quality/help/beginning-duplicate-finding.html"
TARGET="_top"
-> http://www.mozilla.org/quality/help/beginning-duplicate-finding.html</A
+> http://www.mozilla.org/quality/help/beginning-duplicate-finding.html</A
>.
</P
><P
-> I realize this was a lot to read. However, understanding the mentality of writing
- great bug reports will help us on the next part!
+> I realize this was a lot to read. However, understanding
+ the mentality of writing great bug reports will help us on
+ the next part!
</P
><P
></P
@@ -702,20 +928,18 @@ TYPE="1"
><LI
><P
> Go back to <A
-HREF="http://landfill.tequilarista.org/mozilla/bugzilla/"
+HREF="http://landfill.tequilarista.org/bugzilla-tip/"
TARGET="_top"
-> http://landfill.tequilarista.org/mozilla/bugzilla/</A
->
- in your browser.
+> http://landfill.tequilarista.org/bugzilla-tip/</A
+> in your browser.
</P
></LI
><LI
><P
-> Select the
- <A
-HREF="http://landfill.tequilarista.org/mozilla/bugzilla/enter_bug.cgi"
+> Select the <A
+HREF="http://landfill.tequilarista.org/bugzilla-tip/enter_bug.cgi"
TARGET="_top"
-> Enter a new bug report</A
+> Enter a new bug report</A
> link.
</P
></LI
@@ -726,11 +950,11 @@ TARGET="_top"
></LI
><LI
><P
-> Now you should be at the "Enter Bug" form.
- The "reporter" should have been automatically filled out
- for you (or else Bugzilla prompted you to Log In again
- -- you did keep the email with your username
- and password, didn't you?).
+> Now you should be at the "Enter Bug" form. The
+ "reporter" should have been automatically filled out for
+ you (or else Bugzilla prompted you to Log In again --
+ you did keep the email with your username and password,
+ didn't you?).
</P
></LI
><LI
@@ -740,36 +964,37 @@ TARGET="_top"
></LI
><LI
><P
-> Bugzilla should have made reasonable guesses, based upon your browser,
- for the "Platform" and "OS" drop-down
- boxes. If those are wrong, change them -- if you're on an SGI box
- running IRIX, we want to know!
+> Bugzilla should have made reasonable guesses, based upon
+ your browser, for the "Platform" and "OS" drop-down
+ boxes. If those are wrong, change them -- if you're on
+ an SGI box running IRIX, we want to know!
</P
></LI
><LI
><P
-> Fill in the "Assigned To" box with the email address you provided earlier.
- This way you don't end up sending copies of your bug to lots of other people,
- since it's just a test bug.
+> Fill in the "Assigned To" box with the email address you
+ provided earlier. This way you don't end up sending
+ copies of your bug to lots of other people, since it's
+ just a test bug.
</P
></LI
><LI
><P
-> Leave the "CC" text box blank.
- Fill in the "URL" box with "http://www.mozilla.org".
+> Leave the "CC" text box blank. Fill in the "URL" box
+ with "http://www.mozilla.org".
</P
></LI
><LI
><P
-> Enter "The Bugzilla Guide" in the Summary text box,
- and place any comments you have on this
- tutorial, or the Guide in general, into the Description box.
+> Enter "The Bugzilla Guide" in the Summary text box, and
+ place any comments you have on this tutorial, or the
+ Guide in general, into the Description box.
</P
></LI
></OL
><P
-> Voila! Select "Commit" and send in your bug report!
- Next we'll look at resolving bugs.
+> Voila! Select "Commit" and send in your bug report! Next
+ we'll look at resolving bugs.
</P
></DIV
><DIV
@@ -778,13 +1003,13 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="BUG_MANAGE"
->4.3.3.2. Managing your Bug Reports</A
+>2.3.3.2. Managing your Bug Reports</A
></H3
><P
-> OK, you should have a link to the bug you just created near the top of your page.
- It should say
- "Bug XXXX posted", with a link to the right saying "Back to BUG# XXXX".
- Select this link.
+> OK, you should have a link to the bug you just created near
+ the top of your page. It should say "Bug XXXX posted", with
+ a link to the right saying "Back to BUG# XXXX". Select this
+ link.
</P
><P
></P
@@ -792,35 +1017,32 @@ NAME="BUG_MANAGE"
TYPE="1"
><LI
><P
-> Scroll down a bit on the subsequent page,
- until you see the "Resolve bug, changing resolution to (dropdown box).
- Normally, you would
- "Accept bug (change status to ASSIGNED)", fix it, and then resolve.
- But in this case, we're
- going to short-circuit the process because this wasn't a real bug.
- Change the dropdown next to
- "Resolve Bug" to "INVALID", make sure the radio button is
- marked next to "Resolve Bug", then
- click "Commit".
+> Scroll down a bit on the subsequent page, until you see
+ the "Resolve bug, changing resolution to (dropdown box).
+ Normally, you would "Accept bug (change status to
+ ASSIGNED)", fix it, and then resolve. But in this case,
+ we're going to short-circuit the process because this
+ wasn't a real bug. Change the dropdown next to "Resolve
+ Bug" to "INVALID", make sure the radio button is marked
+ next to "Resolve Bug", then click "Commit".
</P
></LI
><LI
><P
-> Hey! It said it couldn't take the change in a big red box!
- That's right, you must specify
- a Comment in order to make this change. Select the "Back"
- button in your browser, add a
- Comment, then try Resolving the bug with INVALID status again.
- This time it should work.
+> Hey! It said it couldn't take the change in a big red
+ box! That's right, you must specify a Comment in order
+ to make this change. Select the "Back" button in your
+ browser, add a Comment, then try Resolving the bug with
+ INVALID status again. This time it should work.
</P
></LI
></OL
><P
> You have now learned the basics of Bugzilla navigation,
- entering a bug, and bug maintenance.
- I encourage you to explore these features, and see what you can do with them!
- We'll spend no more time on individual Bugs or Queries from this point on, so you are
- on your own there.
+ entering a bug, and bug maintenance. I encourage you to
+ explore these features, and see what you can do with them!
+ We'll spend no more time on individual Bugs or Queries from
+ this point on, so you are on your own there.
</P
><P
> But I'll give a few last hints!
@@ -830,41 +1052,29 @@ TYPE="1"
HREF="http://bugzilla.mozilla.org/help.html"
TARGET="_top"
>CLUE</A
->
- on the Query page
- that will teach you more how to use the form.
+> on the Query page that will teach you more how to use the form.
</P
><P
-> If you click the hyperlink on the
- <A
+> If you click the hyperlink on the <A
HREF="http://bugzilla.mozilla.org/describecomponents.cgi"
TARGET="_top"
>Component</A
->
- box of the Query page, you will be presented a form that will describe what all
- the components are.
+> box of the Query page, you will be presented a form that will describe what all the components are.
</P
><P
-> Possibly the most powerful feature of the Query page is the
+> Possibly the most powerful feature of the Query page is the
<A
HREF="http://bugzilla.mozilla.org/booleanchart.html"
TARGET="_top"
>Boolean Chart</A
-> section.
- It's a bit confusing to use the first time, but can provide unparalleled
- flexibility in your queries,
- allowing you to build extremely powerful requests.
+> section. It's a bit confusing to use the first time, but can provide unparalleled flexibility in your queries, allowing you to build extremely powerful requests.
</P
><P
-> Finally, you can build some nifty
- <A
+> Finally, you can build some nifty <A
HREF="http://bugzilla.mozilla.org/reports.cgi"
TARGET="_top"
>Reports</A
->
- using the "Bug Reports" link near the bottom of the query page, and also
- available via the "Reports" link
- at the footer of each page.
+> using the "Bug Reports" link near the bottom of the query page, and also available via the "Reports" link at the footer of each page.
</P
></DIV
></DIV
@@ -922,7 +1132,7 @@ HREF="using.html"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
->What's in it for me?</TD
+>Where can I find my user preferences?</TD
></TR
></TABLE
></DIV
diff --git a/docs/html/index.html b/docs/html/index.html
index 815c0e1c2..2e51ca844 100644
--- a/docs/html/index.html
+++ b/docs/html/index.html
@@ -4,7 +4,7 @@
>The Bugzilla Guide</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="NEXT"
TITLE="About This Guide"
@@ -50,7 +50,7 @@ NAME="AEN2"
><H3
CLASS="AUTHOR"
><A
-NAME="AEN5"
+NAME="AEN27"
>Matthew P. Barnson</A
></H3
><DIV
@@ -62,6 +62,21 @@ CLASS="ADDRESS"
>barnboy@trilobyte.net</P
></DIV
></DIV
+><SPAN
+CLASS="COLLAB"
+><SPAN
+CLASS="COLLABNAME"
+>Zach Lipton</SPAN
+><DIV
+CLASS="AFFILIATION"
+><DIV
+CLASS="ADDRESS"
+><P
+CLASS="ADDRESS"
+>zach AT zachlipton DOT com</P
+></DIV
+></DIV
+><BR></SPAN
><DIV
CLASS="REVHISTORY"
><TABLE
@@ -91,8 +106,8 @@ ALIGN="LEFT"
><TD
ALIGN="LEFT"
COLSPAN="3"
->Converted the README, FAQ, and DATABASE information into SGML
- docbook format.</TD
+>Converted the README, FAQ, and DATABASE information into
+ SGML docbook format.</TD
></TR
><TR
><TD
@@ -109,12 +124,13 @@ ALIGN="LEFT"
><TD
ALIGN="LEFT"
COLSPAN="3"
->Took way too long to revise this for 2.12 release.
- Updated FAQ to use qandaset tags instead of literallayout,
- cleaned up administration section, added User Guide section,
- miscellaneous FAQ updates and third-party integration information.
- From this point on all new tags are lowercase in preparation for the
- 2.13 release of the Guide in XML format instead of SGML.</TD
+>Took way too long to revise this for 2.12 release. Updated
+ FAQ to use qandaset tags instead of literallayout, cleaned
+ up administration section, added User Guide section,
+ miscellaneous FAQ updates and third-party integration
+ information. From this point on all new tags are lowercase
+ in preparation for the 2.13 release of the Guide in XML
+ format instead of SGML.</TD
></TR
><TR
><TD
@@ -131,12 +147,38 @@ ALIGN="LEFT"
><TD
ALIGN="LEFT"
COLSPAN="3"
->Things fixed this release: Elaborated on queryhelp interface, added FAQ regarding
- moving bugs from one keyword to another, clarified possible problems with the Landfill
- tutorial, fixed a boatload of typos and unclear sentence structures. Incorporated the
- README into the UNIX installation section, and changed the README to indicate the deprecated
- status. Things I know need work: Used "simplelist" a lot, where I should have used
- "procedure" to tag things. Need to lowercase all tags to be XML compliant.</TD
+>Things fixed this release: Elaborated on queryhelp
+ interface, added FAQ regarding moving bugs from one keyword
+ to another, clarified possible problems with the Landfill
+ tutorial, fixed a boatload of typos and unclear sentence
+ structures. Incorporated the README into the UNIX
+ installation section, and changed the README to indicate the
+ deprecated status. Things I know need work: Used
+ "simplelist" a lot, where I should have used "procedure" to
+ tag things. Need to lowercase all tags to be XML compliant.</TD
+></TR
+><TR
+><TD
+ALIGN="LEFT"
+>Revision 2.14.0</TD
+><TD
+ALIGN="LEFT"
+>07 August 2001</TD
+><TD
+ALIGN="LEFT"
+>Revised by: MPB</TD
+></TR
+><TR
+><TD
+ALIGN="LEFT"
+COLSPAN="3"
+>Attempted to integrate relevant portions of the UNIX and
+ Windows installation instructions, moved some data from FAQ
+ to Install, removed references to README from text, added
+ Mac OS X install instructions, fixed a bunch
+ of tpyos (Mark Harig), linked text that referenced other
+ parts of the Guide, and nuked the old MySQL permissions
+ section.</TD
></TR
></TABLE
></DIV
@@ -144,12 +186,32 @@ COLSPAN="3"
><DIV
CLASS="ABSTRACT"
><A
-NAME="AEN12"
+NAME="AEN39"
></A
><P
></P
><P
->This is the documentation for Bugzilla, the Mozilla bug-tracking system.</P
+> This is the documentation for Bugzilla, the Mozilla
+ bug-tracking system.
+ </P
+><P
+> Bugzilla is an enterprise-class set of software utilities
+ that, when used together, power issue-tracking for hundreds of
+ organizations around the world, tracking millions of bugs.
+ While it is easy to use and quite flexible, it is very
+ difficult for a novice to install and maintain. Although we
+ have provided step-by-step directions, Bugzilla is not always
+ easy to get working. Please be sure the person responsible
+ for installing and maintaining this software is a qualified
+ professional on operating system upon which you install
+ Bugzilla.
+ </P
+><P
+> THIS DOCUMENTATION IS MAINTAINED IN DOCBOOK 4.1 SGML FORMAT.
+ IF YOU WISH TO MAKE CORRECTIONS, PLEASE MAKE THEM IN PLAIN
+ TEXT OR SGML DIFFS AGAINST THE SOURCE. I CANNOT ACCEPT
+ ADDITIONS TO THE GUIDE WRITTEN IN HTML!
+ </P
><P
></P
></DIV
@@ -218,203 +280,362 @@ HREF="conventions.html"
></DD
><DT
>2. <A
-HREF="installation.html"
->Installing Bugzilla</A
+HREF="using.html"
+>Using Bugzilla</A
></DT
><DD
><DL
><DT
>2.1. <A
-HREF="readme.unix.html"
->UNIX Installation</A
+HREF="whatis.html"
+>What is Bugzilla?</A
+></DT
+><DT
+>2.2. <A
+HREF="why.html"
+>Why Should We Use Bugzilla?</A
+></DT
+><DT
+>2.3. <A
+HREF="how.html"
+>How do I use Bugzilla?</A
+></DT
+><DD
+><DL
+><DT
+>2.3.1. <A
+HREF="how.html#MYACCOUNT"
+>Create a Bugzilla Account</A
+></DT
+><DT
+>2.3.2. <A
+HREF="how.html#QUERY"
+>The Bugzilla Query Page</A
+></DT
+><DT
+>2.3.3. <A
+HREF="how.html#BUGREPORTS"
+>Creating and Managing Bug Reports</A
+></DT
+><DD
+><DL
+><DT
+>2.3.3.1. <A
+HREF="how.html#BUG_WRITING"
+>Writing a Great Bug Report</A
+></DT
+><DT
+>2.3.3.2. <A
+HREF="how.html#BUG_MANAGE"
+>Managing your Bug Reports</A
+></DT
+></DL
+></DD
+></DL
+></DD
+><DT
+>2.4. <A
+HREF="init4me.html"
+>Where can I find my user preferences?</A
+></DT
+><DD
+><DL
+><DT
+>2.4.1. <A
+HREF="init4me.html#ACCOUNTSETTINGS"
+>Account Settings</A
+></DT
+><DT
+>2.4.2. <A
+HREF="init4me.html#EMAILSETTINGS"
+>Email Settings</A
+></DT
+><DD
+><DL
+><DT
+>2.4.2.1. <A
+HREF="init4me.html#NOTIFICATION"
+>Email Notification</A
+></DT
+><DT
+>2.4.2.2. <A
+HREF="init4me.html#NEWEMAILTECH"
+>New Email Technology</A
+></DT
+><DT
+>2.4.2.3. <A
+HREF="init4me.html#WATCHSETTINGS"
+>"Watching" Users</A
+></DT
+></DL
+></DD
+><DT
+>2.4.3. <A
+HREF="init4me.html#FOOTERSETTINGS"
+>Page Footer</A
+></DT
+><DT
+>2.4.4. <A
+HREF="init4me.html#PERMISSIONSETTINGS"
+>Permissions</A
+></DT
+></DL
+></DD
+><DT
+>2.5. <A
+HREF="usingbz-conc.html"
+>Using Bugzilla-Conclusion</A
+></DT
+></DL
+></DD
+><DT
+>3. <A
+HREF="installation.html"
+>Installation</A
></DT
><DD
><DL
><DT
->2.1.1. <A
-HREF="readme.unix.html#AEN190"
+>3.1. <A
+HREF="errata.html"
>ERRATA</A
></DT
><DT
->2.1.2. <A
-HREF="readme.unix.html#AEN204"
+>3.2. <A
+HREF="stepbystep.html"
>Step-by-step Install</A
></DT
><DD
><DL
><DT
->2.1.2.1. <A
-HREF="readme.unix.html#AEN206"
+>3.2.1. <A
+HREF="stepbystep.html#AEN509"
>Introduction</A
></DT
><DT
->2.1.2.2. <A
-HREF="readme.unix.html#AEN211"
+>3.2.2. <A
+HREF="stepbystep.html#AEN515"
>Installing the Prerequisites</A
></DT
><DT
->2.1.2.3. <A
-HREF="readme.unix.html#AEN242"
+>3.2.3. <A
+HREF="stepbystep.html#INSTALL-MYSQL"
>Installing MySQL Database</A
></DT
><DT
->2.1.2.4. <A
-HREF="readme.unix.html#AEN248"
+>3.2.4. <A
+HREF="stepbystep.html#INSTALL-PERL"
>Perl (5.004 or greater)</A
></DT
><DT
->2.1.2.5. <A
-HREF="readme.unix.html#AEN259"
+>3.2.5. <A
+HREF="stepbystep.html#AEN602"
>DBI Perl Module</A
></DT
><DT
->2.1.2.6. <A
-HREF="readme.unix.html#AEN296"
+>3.2.6. <A
+HREF="stepbystep.html#AEN640"
>Data::Dumper Perl Module</A
></DT
><DT
->2.1.2.7. <A
-HREF="readme.unix.html#AEN300"
+>3.2.7. <A
+HREF="stepbystep.html#AEN645"
>MySQL related Perl Module Collection</A
></DT
><DT
->2.1.2.8. <A
-HREF="readme.unix.html#AEN309"
+>3.2.8. <A
+HREF="stepbystep.html#AEN654"
>TimeDate Perl Module Collection</A
></DT
><DT
->2.1.2.9. <A
-HREF="readme.unix.html#AEN312"
+>3.2.9. <A
+HREF="stepbystep.html#AEN658"
>GD Perl Module (1.8.3)</A
></DT
><DT
->2.1.2.10. <A
-HREF="readme.unix.html#AEN318"
+>3.2.10. <A
+HREF="stepbystep.html#AEN667"
>Chart::Base Perl Module (0.99c)</A
></DT
><DT
->2.1.2.11. <A
-HREF="readme.unix.html#AEN321"
+>3.2.11. <A
+HREF="stepbystep.html#AEN671"
>DB_File Perl Module</A
></DT
><DT
->2.1.2.12. <A
-HREF="readme.unix.html#AEN324"
+>3.2.12. <A
+HREF="stepbystep.html#AEN674"
>HTTP Server</A
></DT
><DT
->2.1.2.13. <A
-HREF="readme.unix.html#AEN334"
+>3.2.13. <A
+HREF="stepbystep.html#AEN692"
>Installing the Bugzilla Files</A
></DT
><DT
->2.1.2.14. <A
-HREF="readme.unix.html#AEN343"
+>3.2.14. <A
+HREF="stepbystep.html#AEN721"
>Setting Up the MySQL Database</A
></DT
><DT
->2.1.2.15. <A
-HREF="readme.unix.html#AEN379"
->Tweaking "localconfig"</A
+>3.2.15. <A
+HREF="stepbystep.html#AEN768"
+>Tweaking <TT
+CLASS="FILENAME"
+>localconfig</TT
+></A
></DT
><DT
->2.1.2.16. <A
-HREF="readme.unix.html#AEN401"
->Setting Up Maintainers Manuall (Optional)</A
+>3.2.16. <A
+HREF="stepbystep.html#AEN806"
+>Setting Up Maintainers Manually (Optional)</A
></DT
><DT
->2.1.2.17. <A
-HREF="readme.unix.html#AEN410"
+>3.2.17. <A
+HREF="stepbystep.html#AEN817"
>The Whining Cron (Optional)</A
></DT
><DT
->2.1.2.18. <A
-HREF="readme.unix.html#AEN417"
+>3.2.18. <A
+HREF="stepbystep.html#AEN827"
>Bug Graphs (Optional)</A
></DT
><DT
->2.1.2.19. <A
-HREF="readme.unix.html#AEN429"
+>3.2.19. <A
+HREF="stepbystep.html#AEN839"
>Securing MySQL</A
></DT
+></DL
+></DD
><DT
->2.1.2.20. <A
-HREF="readme.unix.html#AEN495"
+>3.3. <A
+HREF="osx.html"
+>Mac OS X Installation Notes</A
+></DT
+><DT
+>3.4. <A
+HREF="bsdinstall.html"
+>BSD Installation Notes</A
+></DT
+><DT
+>3.5. <A
+HREF="geninstall.html"
>Installation General Notes</A
></DT
-></DL
-></DD
+><DD
+><DL
+><DT
+>3.5.1. <A
+HREF="geninstall.html#AEN941"
+>Modifying Your Running System</A
+></DT
+><DT
+>3.5.2. <A
+HREF="geninstall.html#AEN948"
+>Upgrading From Previous Versions</A
+></DT
+><DT
+>3.5.3. <A
+HREF="geninstall.html#HTACCESS"
+><TT
+CLASS="FILENAME"
+>.htaccess</TT
+> files and security</A
+></DT
+><DT
+>3.5.4. <A
+HREF="geninstall.html#MOD_THROTTLE"
+><TT
+CLASS="FILENAME"
+>mod_throttle</TT
+> and Security</A
+></DT
+><DT
+>3.5.5. <A
+HREF="geninstall.html#CONTENT_TYPE"
+>Preventing untrusted Bugzilla content from executing malicious Javascript code</A
+></DT
+><DT
+>3.5.6. <A
+HREF="geninstall.html#UNIXHISTORY"
+>UNIX Installation Instructions History</A
+></DT
></DL
></DD
><DT
->2.2. <A
-HREF="readme.windows.html"
->Win32 (Win98+/NT/2K) Installation</A
+>3.6. <A
+HREF="win32.html"
+>Win32 Installation Notes</A
></DT
><DD
><DL
><DT
->2.2.1. <A
-HREF="readme.windows.html#NTVERIFIED"
+>3.6.1. <A
+HREF="win32.html#WININSTALL"
>Win32 Installation: Step-by-step</A
></DT
><DT
->2.2.2. <A
-HREF="readme.windows.html#ADDLWINTIPS"
+>3.6.2. <A
+HREF="win32.html#ADDLWINTIPS"
>Additional Windows Tips</A
></DT
+><DT
+>3.6.3. <A
+HREF="win32.html#BZLDAP"
+>Bugzilla LDAP Integration</A
+></DT
></DL
></DD
></DL
></DD
><DT
->3. <A
+>4. <A
HREF="administration.html"
>Administering Bugzilla</A
></DT
><DD
><DL
><DT
->3.1. <A
+>4.1. <A
HREF="postinstall-check.html"
>Post-Installation Checklist</A
></DT
><DT
->3.2. <A
+>4.2. <A
HREF="useradmin.html"
>User Administration</A
></DT
><DD
><DL
><DT
->3.2.1. <A
+>4.2.1. <A
HREF="useradmin.html#DEFAULTUSER"
>Creating the Default User</A
></DT
><DT
->3.2.2. <A
+>4.2.2. <A
HREF="useradmin.html#MANAGEUSERS"
>Managing Other Users</A
></DT
><DD
><DL
><DT
->3.2.2.1. <A
+>4.2.2.1. <A
HREF="useradmin.html#LOGIN"
>Logging In</A
></DT
><DT
->3.2.2.2. <A
+>4.2.2.2. <A
HREF="useradmin.html#CREATENEWUSERS"
>Creating new users</A
></DT
><DT
->3.2.2.3. <A
+>4.2.2.3. <A
HREF="useradmin.html#DISABLEUSERS"
>Disabling Users</A
></DT
><DT
->3.2.2.4. <A
+>4.2.2.4. <A
HREF="useradmin.html#MODIFYUSERS"
>Modifying Users</A
></DT
@@ -423,162 +644,53 @@ HREF="useradmin.html#MODIFYUSERS"
></DL
></DD
><DT
->3.3. <A
+>4.3. <A
HREF="programadmin.html"
->Product, Component, Milestone, and Version Administration</A
+>Product, Component, Milestone, and Version
+ Administration</A
></DT
><DD
><DL
><DT
->3.3.1. <A
+>4.3.1. <A
HREF="programadmin.html#PRODUCTS"
>Products</A
></DT
><DT
->3.3.2. <A
+>4.3.2. <A
HREF="programadmin.html#COMPONENTS"
>Components</A
></DT
><DT
->3.3.3. <A
+>4.3.3. <A
HREF="programadmin.html#VERSIONS"
>Versions</A
></DT
><DT
->3.3.4. <A
+>4.3.4. <A
HREF="programadmin.html#MILESTONES"
>Milestones</A
></DT
><DT
->3.3.5. <A
+>4.3.5. <A
HREF="programadmin.html#VOTING"
>Voting</A
></DT
><DT
->3.3.6. <A
+>4.3.6. <A
HREF="programadmin.html#GROUPS"
>Groups and Group Security</A
></DT
></DL
></DD
><DT
->3.4. <A
+>4.4. <A
HREF="security.html"
>Bugzilla Security</A
></DT
></DL
></DD
><DT
->4. <A
-HREF="using.html"
->Using Bugzilla</A
-></DT
-><DD
-><DL
-><DT
->4.1. <A
-HREF="whatis.html"
->What is Bugzilla?</A
-></DT
-><DT
->4.2. <A
-HREF="why.html"
->Why Should We Use Bugzilla?</A
-></DT
-><DT
->4.3. <A
-HREF="how.html"
->How do I use Bugzilla?</A
-></DT
-><DD
-><DL
-><DT
->4.3.1. <A
-HREF="how.html#MYACCOUNT"
->Create a Bugzilla Account</A
-></DT
-><DT
->4.3.2. <A
-HREF="how.html#QUERY"
->The Bugzilla Query Page</A
-></DT
-><DT
->4.3.3. <A
-HREF="how.html#BUGREPORTS"
->Creating and Managing Bug Reports</A
-></DT
-><DD
-><DL
-><DT
->4.3.3.1. <A
-HREF="how.html#BUG_WRITING"
->Writing a Great Bug Report</A
-></DT
-><DT
->4.3.3.2. <A
-HREF="how.html#BUG_MANAGE"
->Managing your Bug Reports</A
-></DT
-></DL
-></DD
-></DL
-></DD
-><DT
->4.4. <A
-HREF="init4me.html"
->What's in it for me?</A
-></DT
-><DD
-><DL
-><DT
->4.4.1. <A
-HREF="init4me.html#ACCOUNTSETTINGS"
->Account Settings</A
-></DT
-><DT
->4.4.2. <A
-HREF="init4me.html#EMAILSETTINGS"
->Email Settings</A
-></DT
-><DD
-><DL
-><DT
->4.4.2.1. <A
-HREF="init4me.html#NOTIFICATION"
->Email Notification</A
-></DT
-><DT
->4.4.2.2. <A
-HREF="init4me.html#NEWEMAILTECH"
->New Email Technology</A
-></DT
-><DT
->4.4.2.3. <A
-HREF="init4me.html#WATCHSETTINGS"
->"Watching" Users</A
-></DT
-></DL
-></DD
-><DT
->4.4.3. <A
-HREF="init4me.html#FOOTERSETTINGS"
->Page Footer</A
-></DT
-><DT
->4.4.4. <A
-HREF="init4me.html#PERMISSIONSETTINGS"
->Permissions</A
-></DT
-></DL
-></DD
-><DT
->4.5. <A
-HREF="usingbz-conc.html"
->Using Bugzilla-Conclusion</A
-></DT
-></DL
-></DD
-><DT
>5. <A
HREF="integration.html"
>Integrating Bugzilla with Third-Party Tools</A
@@ -603,7 +715,7 @@ HREF="scm.html"
><DT
>5.4. <A
HREF="tinderbox.html"
->Tinderbox</A
+>Tinderbox/Tinderbox2</A
></DT
></DL
></DD
@@ -612,37 +724,42 @@ HREF="tinderbox.html"
HREF="future.html"
>The Future of Bugzilla</A
></DT
+><DT
+>7. <A
+HREF="variants.html"
+>Bugzilla Variants and Competitors</A
+></DT
><DD
><DL
><DT
->6.1. <A
-HREF="spamlite.html"
->Reducing Spam</A
+>7.1. <A
+HREF="rhbugzilla.html"
+>Red Hat Bugzilla</A
></DT
><DT
->6.2. <A
-HREF="searching.html"
->Better Searching</A
+>7.2. <A
+HREF="variant_fenris.html"
+>Loki Bugzilla (Fenris)</A
></DT
><DT
->6.3. <A
-HREF="trackingbugs.html"
->Description Flags and Tracking Bugs</A
+>7.3. <A
+HREF="variant_issuezilla.html"
+>Issuezilla</A
></DT
><DT
->6.4. <A
-HREF="bugprobs.html"
->Bug Issues</A
+>7.4. <A
+HREF="variant_scarab.html"
+>Scarab</A
></DT
><DT
->6.5. <A
-HREF="dbaseintegrity.html"
->Database Integrity</A
+>7.5. <A
+HREF="variant_perforce.html"
+>Perforce SCM</A
></DT
><DT
->6.6. <A
-HREF="bz30.html"
->Bugzilla 3.0</A
+>7.6. <A
+HREF="variant_sourceforge.html"
+>SourceForge</A
></DT
></DL
></DD
@@ -673,29 +790,28 @@ HREF="dbschema.html"
HREF="dbdoc.html"
>MySQL Bugzilla Database Introduction</A
></DT
+><DD
+><DL
><DT
->C.3. <A
-HREF="granttables.html"
->MySQL Permissions & Grant Tables</A
+>C.2.1. <A
+HREF="dbdoc.html#AEN2331"
+>Bugzilla Database Basics</A
></DT
+><DD
+><DL
><DT
->C.4. <A
-HREF="cleanupwork.html"
->Cleaning up after mucking with Bugzilla</A
+>C.2.1.1. <A
+HREF="dbdoc.html#AEN2360"
+>Bugzilla Database Tables</A
></DT
></DL
></DD
+></DL
+></DD
><DT
->7. <A
-HREF="variants.html"
->Bugzilla Variants</A
-></DT
-><DD
-><DL
-><DT
->7.1. <A
-HREF="rhbugzilla.html"
->Red Hat Bugzilla</A
+>C.3. <A
+HREF="granttables.html"
+>MySQL Permissions & Grant Tables</A
></DT
></DL
></DD
@@ -708,19 +824,32 @@ HREF="patches.html"
><DL
><DT
>D.1. <A
+HREF="rewrite.html"
+>Apache <TT
+CLASS="FILENAME"
+>mod_rewrite</TT
+> magic</A
+></DT
+><DT
+>D.2. <A
HREF="setperl.html"
>The setperl.csh Utility</A
></DT
><DT
->D.2. <A
+>D.3. <A
HREF="cmdline.html"
>Command-line Bugzilla Queries</A
></DT
><DT
->D.3. <A
+>D.4. <A
HREF="quicksearch.html"
>The Quicksearch Utility</A
></DT
+><DT
+>D.5. <A
+HREF="bzhacking.html"
+>Hacking Bugzilla</A
+></DT
></DL
></DD
><DT
@@ -809,64 +938,83 @@ CLASS="LOT"
></DT
><DT
>2-1. <A
-HREF="readme.windows.html#AEN646"
->Removing encrypt() for Windows NT installations</A
+HREF="how.html#AEN307"
+>Some Famous Software Versions</A
+></DT
+><DT
+>2-2. <A
+HREF="how.html#AEN317"
+>Mozilla's Bugzilla Components</A
></DT
><DT
>3-1. <A
-HREF="programadmin.html#AEN838"
->Creating some Components</A
+HREF="stepbystep.html#AEN708"
+>Setting up bonsaitools symlink</A
></DT
><DT
>3-2. <A
-HREF="programadmin.html#AEN867"
->Common Use of Versions</A
+HREF="stepbystep.html#AEN799"
+>Running checksetup.pl as the web user</A
></DT
><DT
>3-3. <A
-HREF="programadmin.html#AEN871"
->A Different Use of Versions</A
+HREF="win32.html#AEN1038"
+>Installing ActivePerl ppd Modules on Microsoft Windows</A
></DT
><DT
>3-4. <A
-HREF="programadmin.html#AEN899"
+HREF="win32.html#AEN1224"
+>Removing encrypt() for Windows NT Bugzilla version
+ 2.12 or earlier</A
+></DT
+><DT
+>4-1. <A
+HREF="programadmin.html#AEN1461"
+>Creating some Components</A
+></DT
+><DT
+>4-2. <A
+HREF="programadmin.html#AEN1490"
+>Common Use of Versions</A
+></DT
+><DT
+>4-3. <A
+HREF="programadmin.html#AEN1494"
+>A Different Use of Versions</A
+></DT
+><DT
+>4-4. <A
+HREF="programadmin.html#AEN1522"
>Using SortKey with Target Milestone</A
></DT
><DT
->3-5. <A
-HREF="programadmin.html#AEN937"
+>4-5. <A
+HREF="programadmin.html#AEN1558"
>When to Use Group Security</A
></DT
><DT
->3-6. <A
-HREF="programadmin.html#AEN954"
+>4-6. <A
+HREF="programadmin.html#AEN1575"
>Creating a New Group</A
></DT
><DT
->4-1. <A
-HREF="how.html#AEN1095"
->Some Famous Software Versions</A
-></DT
-><DT
->4-2. <A
-HREF="how.html#AEN1105"
->Mozilla Webtools Components</A
+>4-7. <A
+HREF="programadmin.html#AEN1592"
+>Bugzilla Groups</A
></DT
><DT
>D-1. <A
-HREF="setperl.html#AEN1963"
+HREF="setperl.html#AEN2439"
>Using Setperl to set your perl path</A
></DT
><DT
>1. <A
-HREF="glossary.html#AEN2145"
+HREF="glossary.html#AEN2685"
>A Sample Product</A
></DT
></DL
></DIV
->] >
-
-</DIV
+></DIV
><DIV
CLASS="NAVFOOTER"
><HR
diff --git a/docs/html/init4me.html b/docs/html/init4me.html
index d430ad21d..d400108b2 100644
--- a/docs/html/init4me.html
+++ b/docs/html/init4me.html
@@ -1,10 +1,10 @@
<HTML
><HEAD
><TITLE
->What's in it for me?</TITLE
+>Where can I find my user preferences?</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
@@ -51,7 +51,7 @@ HREF="how.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
->Chapter 4. Using Bugzilla</TD
+>Chapter 2. Using Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
@@ -71,7 +71,7 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="INIT4ME"
->4.4. What's in it for me?</A
+>2.4. Where can I find my user preferences?</A
></H1
><TABLE
BORDER="0"
@@ -101,15 +101,13 @@ VALIGN="TOP"
></TR
></TABLE
><P
-> Customized User Preferences offer tremendous versatility to
- your individual Bugzilla experience.
- Let's plunge into what you can do! The first step is to click
- the "Edit prefs" link at the footer of each page once you
- have logged in to
- <A
-HREF="http://landfill.tequilarista.org/mozilla/bugzilla/query.cgi?GoAheadAndLogIn=1"
+> Customized User Preferences offer tremendous versatility to your
+ individual Bugzilla experience. Let's plunge into what you can
+ do! The first step is to click the "Edit prefs" link at the
+ footer of each page once you have logged in to <A
+HREF="http://landfill.tequilarista.org/bugzilla-tip/query.cgi?GoAheadAndLogIn=1"
TARGET="_top"
-> Landfill</A
+> Landfill</A
>.
</P
><DIV
@@ -118,20 +116,33 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="ACCOUNTSETTINGS"
->4.4.1. Account Settings</A
+>2.4.1. Account Settings</A
></H2
><P
> On this page, you can change your basic Account Settings,
- including your password and full name.
- For security reasons, in order to change anything on this page you
- must type your <EM
+ including your password and full name. For security reasons,
+ in order to change anything on this page you must type your
+ <EM
>current</EM
->
- password into the "Old Password" field.
- If you wish to change your password, type the new password you
- want into the "New Password" field and again into the "Re-enter
- new password" field to ensure
- you typed your new password correctly. Select the "Submit" button and you're done!
+> password into the <SPAN
+CLASS="QUOTE"
+>"Old
+ Password"</SPAN
+> field. If you wish to change your
+ password, type the new password you want into the <SPAN
+CLASS="QUOTE"
+>"New
+ Password"</SPAN
+> field and again into the <SPAN
+CLASS="QUOTE"
+>"Re-enter
+ new password"</SPAN
+> field to ensure you typed your new
+ password correctly. Select the <SPAN
+CLASS="QUOTE"
+>"Submit"</SPAN
+> button
+ and you are done.
</P
></DIV
><DIV
@@ -140,7 +151,7 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="EMAILSETTINGS"
->4.4.2. Email Settings</A
+>2.4.2. Email Settings</A
></H2
><DIV
CLASS="SECTION"
@@ -148,64 +159,32 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="NOTIFICATION"
->4.4.2.1. Email Notification</A
+>2.4.2.1. Email Notification</A
></H3
-><DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
-><P
-><B
->Note: </B
-> The email notification settings described below have been obsoleted in Bugzilla 2.12, and
- this section will be replaced with a comprehensive description of the amazing array of
- new options at your disposal. However, in the meantime, throw this chunk out the window
- and go crazy with goofing around with different notification options.
- </P
-></BLOCKQUOTE
-></DIV
-><P
-> Ahh, here you can reduce or increase the amount of email sent you from Bugzilla!
- In the drop-down "Notify me of changes to", select one of
- <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
-><EM
->All qualifying bugs</EM
->: sends you every change to every bug
- where your name is somewhere on it, regardless of who changed it.</TD
-></TR
-><TR
-><TD
-><EM
->Only those bugs which I am listed in the CC line</EM
->: prevents
- you from receiving mail for which you are the reporter,'
- owner, or QA contact. If you are on the CC
- list, presumably someone had a <EM
->good</EM
->
- reason for you to get the email.</TD
-></TR
-><TR
-><TD
-><EM
->All qulifying bugs except those which I change</EM
->:
- This is the default, and
- a sensible setting. If someone else changes your bugs, you will get emailed,
- but if you change bugs
- yourself you will receive no notification of the change.</TD
-></TR
-></TBODY
-></TABLE
><P
-></P
->
+> Here you can reduce or increase the amount of email sent you
+ from Bugzilla. Although this is referred to as
+ <SPAN
+CLASS="QUOTE"
+>"Advanced Email Filtering Options"</SPAN
+>, they are,
+ in fact, the standard email filter set. All of them are
+ self-explanatory, but you can use the filters in interesting
+ ways. For instance, some people (notably Quality Assurance
+ personnel) often only care to receive updates regarding a
+ bug when the bug changes state, so they can track bugs on
+ their flow charts and know when it is time to pull the bug
+ onto a quality assurance platform for inspection. Other
+ people set up email gateways to
+ <A
+HREF="bonsai.html"
+>Bonsai, the Mozilla automated CVS management system</A
+> or <A
+HREF="tinderbox.html"
+>Tinderbox, the Mozilla automated build management system</A
+>, and
+ restrict which types of Bugzilla information are fed to
+ these systems..
</P
></DIV
><DIV
@@ -214,34 +193,53 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="NEWEMAILTECH"
->4.4.2.2. New Email Technology</A
+>2.4.2.2. New Email Technology</A
></H3
><DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><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
-><B
->Note: </B
-> This option may not be available in all Bugzilla installations, depending upon
- the preferences of the systems administrator responsible for the setup of your Bugzilla.
- However, if you really want this functionality, ask her to "enable newemailtech
- in Params"
- and "make it the default for all new users", referring her to the Administration section
- of this Guide.
+> This option may not be available in all Bugzilla
+ installations, depending upon the preferences of the
+ systems administrator responsible for the setup of your
+ Bugzilla. However, if you really want this functionality,
+ ask her to "enable newemailtech in Params" and "make it
+ the default for all new users", referring her to the
+ Administration section of this Guide.
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
><P
-> Disregard the warnings about "experimental and bleeding edge"; the code to handle email
- in a cleaner manner than that historically used for Bugzilla is
- quite robust and well-tested now.
+> Disregard the warnings about "experimental and bleeding
+ edge"; the code to handle email in a cleaner manner than
+ that historically used for Bugzilla is quite robust and
+ well-tested now.
</P
><P
-> I recommend you enable the option, "Click here to sign up (and risk any bugs)".
- Your email-box
- will thank you for it. The fundamental shift in "newemailtech" is away from standard UNIX
- "diff" output, which is quite ugly, to a prettier, better laid-out email.
+> I recommend you enable the option, "Click here to sign up
+ (and risk any bugs)". Your email-box will thank you for it.
+ The fundamental shift in "newemailtech" is away from
+ standard UNIX "diff" output, which is quite ugly, to a
+ prettier, better laid-out email.
</P
></DIV
><DIV
@@ -250,27 +248,48 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="WATCHSETTINGS"
->4.4.2.3. "Watching" Users</A
+>2.4.2.3. "Watching" Users</A
></H3
><DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><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
-><B
->Note: </B
-> This option may not be available in all Bugzilla installations, depending upon
- the preferences of the systems administrator responsible for the setup of your Bugzilla.
- However, if you really want this functionality, ask her to "enable watchers in Params".
+> This option may not be available in all Bugzilla
+ installations, depending upon the preferences of the
+ systems administrator responsible for the setup of your
+ Bugzilla. However, if you really want this functionality,
+ ask her to "enable watchers in Params".
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
><P
-> By entering user email names into the "Users to watch" text entry box, delineated by commas,
- you can watch bugs of other users. This powerful functionality enables seamless transitions
- as developers change projects, managers wish to get in touch with the issues faced by their
- direct reports, or users go on vacation. If any of these three situations apply
- to you, you will undoubtedly find this feature quite convenient.
+> By entering user email names into the "Users to watch" text
+ entry box, delineated by commas, you can watch bugs of other
+ users. This powerful functionality enables seamless
+ transitions as developers change projects, managers wish to
+ get in touch with the issues faced by their direct reports,
+ or users go on vacation. If any of these three situations
+ apply to you, you will undoubtedly find this feature quite
+ convenient.
</P
></DIV
></DIV
@@ -280,43 +299,84 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="FOOTERSETTINGS"
->4.4.3. Page Footer</A
+>2.4.3. Page Footer</A
></H2
><DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><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
-><B
->Note: </B
-> By default, this page is quite barren. However, go explore the Query Page some more; you will
- find that you can store numerous queries on the server, so if you regularly run a particular query
- it is just a drop-down menu away. On this page of Preferences, if you have many stored
- queries you can elect to have them always one-click away!
+> By default, this page is quite barren. However, go explore
+ the Query Page some more; you will find that you can store
+ numerous queries on the server, so if you regularly run a
+ particular query it is just a drop-down menu away. On this
+ page of Preferences, if you have many stored queries you can
+ elect to have them always one-click away!
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
><P
-> If you have many stored queries on the server, here you will find individual drop-downs for each
- stored query. Each drop-down gives you the option of that query appearing on the footer of every
- page in Bugzilla! This gives you powerful one-click access to any complex searches you may set up,
- and is an excellent way to impress your boss...
+> If you have many stored queries on the server, here you will
+ find individual drop-downs for each stored query. Each
+ drop-down gives you the option of that query appearing on the
+ footer of every page in Bugzilla! This gives you powerful
+ one-click access to any complex searches you may set up, and
+ is an excellent way to impress your boss...
</P
><DIV
CLASS="TIP"
-><BLOCKQUOTE
+><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
-><B
->Tip: </B
->By default, the "My Bugs" link appears at the bottom of each page. However, this query
- gives you both the bugs you have reported, as well as those you are assigned. One of the most
- common uses for this page is to remove the "My Bugs" link, replacing it with two other queries,
- commonly called "My Bug Reports" and "My Bugs" (but only referencing bugs assigned to you). This
- allows you to distinguish those bugs you have reported from those you are assigned. I commonly
- set up complex Boolean queries in the Query page and link them to my footer in this page. When
- they are significantly complex, a one-click reference can save hours of work.</P
-></BLOCKQUOTE
+>By default, the "My Bugs" link appears at the bottom of
+ each page. However, this query gives you both the bugs you
+ have reported, as well as those you are assigned. One of
+ the most common uses for this page is to remove the "My
+ Bugs" link, replacing it with two other queries, commonly
+ called "My Bug Reports" and "My Bugs" (but only referencing
+ bugs assigned to you). This allows you to distinguish those
+ bugs you have reported from those you are assigned. I
+ commonly set up complex Boolean queries in the Query page
+ and link them to my footer in this page. When they are
+ significantly complex, a one-click reference can save hours
+ of work.</P
+></TD
+></TR
+></TABLE
></DIV
></DIV
><DIV
@@ -325,14 +385,15 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="PERMISSIONSETTINGS"
->4.4.4. Permissions</A
+>2.4.4. Permissions</A
></H2
><P
-> This is a purely informative page which outlines your current permissions on
- this installation of Bugzilla. If you have permissions to grant certain permissions to
- other users, the "other users" link appears on this page as well as the footer.
- For more information regarding user administration, please consult the Administration
- section of this Guide.
+> This is a purely informative page which outlines your current
+ permissions on this installation of Bugzilla. If you have
+ permissions to grant certain permissions to other users, the
+ "other users" link appears on this page as well as the footer.
+ For more information regarding user administration, please
+ consult the Administration section of this Guide.
</P
></DIV
></DIV
diff --git a/docs/html/installation.html b/docs/html/installation.html
index f46abd61b..5725bb8b8 100644
--- a/docs/html/installation.html
+++ b/docs/html/installation.html
@@ -1,20 +1,20 @@
<HTML
><HEAD
><TITLE
->Installing Bugzilla</TITLE
+>Installation</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="PREVIOUS"
-TITLE="Document Conventions"
-HREF="conventions.html"><LINK
+TITLE="Using Bugzilla-Conclusion"
+HREF="usingbz-conc.html"><LINK
REL="NEXT"
-TITLE="UNIX Installation"
-HREF="readme.unix.html"></HEAD
+TITLE="ERRATA"
+HREF="errata.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@@ -41,7 +41,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
-HREF="conventions.html"
+HREF="usingbz-conc.html"
>Prev</A
></TD
><TD
@@ -54,7 +54,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
-HREF="readme.unix.html"
+HREF="errata.html"
>Next</A
></TD
></TR
@@ -67,7 +67,7 @@ CLASS="CHAPTER"
><H1
><A
NAME="INSTALLATION"
->Chapter 2. Installing Bugzilla</A
+>Chapter 3. Installation</A
></H1
><DIV
CLASS="TOC"
@@ -77,168 +77,205 @@ CLASS="TOC"
>Table of Contents</B
></DT
><DT
->2.1. <A
-HREF="readme.unix.html"
->UNIX Installation</A
-></DT
-><DD
-><DL
-><DT
->2.1.1. <A
-HREF="readme.unix.html#AEN190"
+>3.1. <A
+HREF="errata.html"
>ERRATA</A
></DT
><DT
->2.1.2. <A
-HREF="readme.unix.html#AEN204"
+>3.2. <A
+HREF="stepbystep.html"
>Step-by-step Install</A
></DT
><DD
><DL
><DT
->2.1.2.1. <A
-HREF="readme.unix.html#AEN206"
+>3.2.1. <A
+HREF="stepbystep.html#AEN509"
>Introduction</A
></DT
><DT
->2.1.2.2. <A
-HREF="readme.unix.html#AEN211"
+>3.2.2. <A
+HREF="stepbystep.html#AEN515"
>Installing the Prerequisites</A
></DT
><DT
->2.1.2.3. <A
-HREF="readme.unix.html#AEN242"
+>3.2.3. <A
+HREF="stepbystep.html#INSTALL-MYSQL"
>Installing MySQL Database</A
></DT
><DT
->2.1.2.4. <A
-HREF="readme.unix.html#AEN248"
+>3.2.4. <A
+HREF="stepbystep.html#INSTALL-PERL"
>Perl (5.004 or greater)</A
></DT
><DT
->2.1.2.5. <A
-HREF="readme.unix.html#AEN259"
+>3.2.5. <A
+HREF="stepbystep.html#AEN602"
>DBI Perl Module</A
></DT
><DT
->2.1.2.6. <A
-HREF="readme.unix.html#AEN296"
+>3.2.6. <A
+HREF="stepbystep.html#AEN640"
>Data::Dumper Perl Module</A
></DT
><DT
->2.1.2.7. <A
-HREF="readme.unix.html#AEN300"
+>3.2.7. <A
+HREF="stepbystep.html#AEN645"
>MySQL related Perl Module Collection</A
></DT
><DT
->2.1.2.8. <A
-HREF="readme.unix.html#AEN309"
+>3.2.8. <A
+HREF="stepbystep.html#AEN654"
>TimeDate Perl Module Collection</A
></DT
><DT
->2.1.2.9. <A
-HREF="readme.unix.html#AEN312"
+>3.2.9. <A
+HREF="stepbystep.html#AEN658"
>GD Perl Module (1.8.3)</A
></DT
><DT
->2.1.2.10. <A
-HREF="readme.unix.html#AEN318"
+>3.2.10. <A
+HREF="stepbystep.html#AEN667"
>Chart::Base Perl Module (0.99c)</A
></DT
><DT
->2.1.2.11. <A
-HREF="readme.unix.html#AEN321"
+>3.2.11. <A
+HREF="stepbystep.html#AEN671"
>DB_File Perl Module</A
></DT
><DT
->2.1.2.12. <A
-HREF="readme.unix.html#AEN324"
+>3.2.12. <A
+HREF="stepbystep.html#AEN674"
>HTTP Server</A
></DT
><DT
->2.1.2.13. <A
-HREF="readme.unix.html#AEN334"
+>3.2.13. <A
+HREF="stepbystep.html#AEN692"
>Installing the Bugzilla Files</A
></DT
><DT
->2.1.2.14. <A
-HREF="readme.unix.html#AEN343"
+>3.2.14. <A
+HREF="stepbystep.html#AEN721"
>Setting Up the MySQL Database</A
></DT
><DT
->2.1.2.15. <A
-HREF="readme.unix.html#AEN379"
->Tweaking "localconfig"</A
+>3.2.15. <A
+HREF="stepbystep.html#AEN768"
+>Tweaking <TT
+CLASS="FILENAME"
+>localconfig</TT
+></A
></DT
><DT
->2.1.2.16. <A
-HREF="readme.unix.html#AEN401"
->Setting Up Maintainers Manuall (Optional)</A
+>3.2.16. <A
+HREF="stepbystep.html#AEN806"
+>Setting Up Maintainers Manually (Optional)</A
></DT
><DT
->2.1.2.17. <A
-HREF="readme.unix.html#AEN410"
+>3.2.17. <A
+HREF="stepbystep.html#AEN817"
>The Whining Cron (Optional)</A
></DT
><DT
->2.1.2.18. <A
-HREF="readme.unix.html#AEN417"
+>3.2.18. <A
+HREF="stepbystep.html#AEN827"
>Bug Graphs (Optional)</A
></DT
><DT
->2.1.2.19. <A
-HREF="readme.unix.html#AEN429"
+>3.2.19. <A
+HREF="stepbystep.html#AEN839"
>Securing MySQL</A
></DT
+></DL
+></DD
><DT
->2.1.2.20. <A
-HREF="readme.unix.html#AEN495"
+>3.3. <A
+HREF="osx.html"
+>Mac OS X Installation Notes</A
+></DT
+><DT
+>3.4. <A
+HREF="bsdinstall.html"
+>BSD Installation Notes</A
+></DT
+><DT
+>3.5. <A
+HREF="geninstall.html"
>Installation General Notes</A
></DT
><DD
><DL
><DT
->2.1.2.20.1. <A
-HREF="readme.unix.html#AEN497"
+>3.5.1. <A
+HREF="geninstall.html#AEN941"
>Modifying Your Running System</A
></DT
><DT
->2.1.2.20.2. <A
-HREF="readme.unix.html#AEN502"
+>3.5.2. <A
+HREF="geninstall.html#AEN948"
>Upgrading From Previous Versions</A
></DT
><DT
->2.1.2.20.3. <A
-HREF="readme.unix.html#AEN505"
+>3.5.3. <A
+HREF="geninstall.html#HTACCESS"
+><TT
+CLASS="FILENAME"
+>.htaccess</TT
+> files and security</A
+></DT
+><DT
+>3.5.4. <A
+HREF="geninstall.html#MOD_THROTTLE"
+><TT
+CLASS="FILENAME"
+>mod_throttle</TT
+> and Security</A
+></DT
+><DT
+>3.5.5. <A
+HREF="geninstall.html#CONTENT_TYPE"
+>Preventing untrusted Bugzilla content from executing malicious Javascript code</A
+></DT
+><DT
+>3.5.6. <A
+HREF="geninstall.html#UNIXHISTORY"
>UNIX Installation Instructions History</A
></DT
></DL
></DD
-></DL
-></DD
-></DL
-></DD
><DT
->2.2. <A
-HREF="readme.windows.html"
->Win32 (Win98+/NT/2K) Installation</A
+>3.6. <A
+HREF="win32.html"
+>Win32 Installation Notes</A
></DT
><DD
><DL
><DT
->2.2.1. <A
-HREF="readme.windows.html#NTVERIFIED"
+>3.6.1. <A
+HREF="win32.html#WININSTALL"
>Win32 Installation: Step-by-step</A
></DT
><DT
->2.2.2. <A
-HREF="readme.windows.html#ADDLWINTIPS"
+>3.6.2. <A
+HREF="win32.html#ADDLWINTIPS"
>Additional Windows Tips</A
></DT
+><DT
+>3.6.3. <A
+HREF="win32.html#BZLDAP"
+>Bugzilla LDAP Integration</A
+></DT
></DL
></DD
></DL
></DIV
+><P
+> These installation instructions are presented assuming you are
+ installing on a UNIX or completely POSIX-compliant system. If
+ you are installing on Microsoft Windows or another oddball
+ operating system, please consult the appropriate sections in
+ this installation guide for notes on how to be successful.
+ </P
></DIV
><DIV
CLASS="NAVFOOTER"
@@ -255,7 +292,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
-HREF="conventions.html"
+HREF="usingbz-conc.html"
>Prev</A
></TD
><TD
@@ -271,7 +308,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
-HREF="readme.unix.html"
+HREF="errata.html"
>Next</A
></TD
></TR
@@ -280,7 +317,7 @@ HREF="readme.unix.html"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
->Document Conventions</TD
+>Using Bugzilla-Conclusion</TD
><TD
WIDTH="34%"
ALIGN="center"
@@ -290,7 +327,7 @@ VALIGN="top"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
->UNIX Installation</TD
+>ERRATA</TD
></TR
></TABLE
></DIV
diff --git a/docs/html/integration.html b/docs/html/integration.html
index 59970b107..69648fdf2 100644
--- a/docs/html/integration.html
+++ b/docs/html/integration.html
@@ -4,14 +4,14 @@
>Integrating Bugzilla with Third-Party Tools</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="PREVIOUS"
-TITLE="Using Bugzilla-Conclusion"
-HREF="usingbz-conc.html"><LINK
+TITLE="Bugzilla Security"
+HREF="security.html"><LINK
REL="NEXT"
TITLE="Bonsai"
HREF="bonsai.html"></HEAD
@@ -41,7 +41,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
-HREF="usingbz-conc.html"
+HREF="security.html"
>Prev</A
></TD
><TD
@@ -94,7 +94,7 @@ HREF="scm.html"
><DT
>5.4. <A
HREF="tinderbox.html"
->Tinderbox</A
+>Tinderbox/Tinderbox2</A
></DT
></DL
></DIV
@@ -114,7 +114,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
-HREF="usingbz-conc.html"
+HREF="security.html"
>Prev</A
></TD
><TD
@@ -139,7 +139,7 @@ HREF="bonsai.html"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
->Using Bugzilla-Conclusion</TD
+>Bugzilla Security</TD
><TD
WIDTH="34%"
ALIGN="center"
diff --git a/docs/html/newversions.html b/docs/html/newversions.html
index de3135bce..ab287d22e 100644
--- a/docs/html/newversions.html
+++ b/docs/html/newversions.html
@@ -4,7 +4,7 @@
>New Versions</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
@@ -74,7 +74,10 @@ NAME="NEWVERSIONS"
>1.4. New Versions</A
></H1
><P
-> This is the initial release of the Bugzilla Guide.
+> This is the 2.14 version of The Bugzilla Guide. 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:
@@ -106,7 +109,8 @@ TARGET="_top"
> <A
HREF="http://www.linuxdoc.org/"
TARGET="_top"
->The Linux Documentation Project</A
+>The Linux
+ Documentation Project</A
>
</P
></LI
@@ -115,13 +119,11 @@ TARGET="_top"
</P
><P
> The latest version of this document can be checked out via CVS.
- Please follow the instructions available at
- <A
+ Please follow the instructions available at <A
HREF="http://www.mozilla.org/cvs.html"
TARGET="_top"
>the Mozilla CVS page</A
->,
- and check out the mozilla/webtools/bugzilla/docs/ branch.
+>, and check out the mozilla/webtools/bugzilla/docs/ branch.
</P
></DIV
><DIV
diff --git a/docs/html/osx.html b/docs/html/osx.html
new file mode 100644
index 000000000..caa9efbdf
--- /dev/null
+++ b/docs/html/osx.html
@@ -0,0 +1,289 @@
+<HTML
+><HEAD
+><TITLE
+>Mac OS X Installation Notes</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide"
+HREF="index.html"><LINK
+REL="UP"
+TITLE="Installation"
+HREF="installation.html"><LINK
+REL="PREVIOUS"
+TITLE="Step-by-step Install"
+HREF="stepbystep.html"><LINK
+REL="NEXT"
+TITLE="BSD Installation Notes"
+HREF="bsdinstall.html"></HEAD
+><BODY
+CLASS="SECTION"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>The Bugzilla Guide</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="stepbystep.html"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Chapter 3. Installation</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="bsdinstall.html"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="SECTION"
+><H1
+CLASS="SECTION"
+><A
+NAME="OSX"
+>3.3. Mac OS X Installation Notes</A
+></H1
+><P
+> There are a lot of common libraries and utilities out there
+ that Apple did not include with Mac OS X, but which run
+ perfectly well on it. The GD library, which Bugzilla needs to
+ do bug graphs, is one of these.
+ </P
+><P
+> The easiest way to get a lot of these is with a program called
+ Fink, which is similar in nature to the CPAN installer, but
+ installs common GNU utilities. Fink is available from
+ <http://sourceforge.net/projects/fink/>.
+ </P
+><P
+> Follow the instructions for setting up Fink. Once it's
+ installed, you'll want to run the following as root:
+ <B
+CLASS="COMMAND"
+>fink install gd</B
+>
+ </P
+><P
+> It will prompt you for a number of dependencies, type 'y' and
+ hit enter to install all of the dependencies. Then watch it
+ work.
+ </P
+><P
+> To prevent creating conflicts with the software that Apple
+ installs by default, Fink creates its own directory tree at
+ /sw where it installs most of the software that it installs.
+ This means your libraries and headers for libgd will be at
+ /sw/lib and /sw/include instead of /usr/lib and
+ /usr/local/include. Because of these changed locations for
+ the libraries, the Perl GD module will not install directly
+ via CPAN (it looks for the specific paths instead of getting
+ them from your environment). But there's a way around that
+ :-)
+ </P
+><P
+> Instead of typing <SPAN
+CLASS="QUOTE"
+>"install GD"</SPAN
+> at the
+ <TT
+CLASS="PROMPT"
+>cpan></TT
+> prompt, type <B
+CLASS="COMMAND"
+>look
+ GD</B
+>. This should go through the motions of
+ downloading the latest version of the GD module, then it will
+ open a shell and drop you into the build directory. Apply the
+ following patch to the Makefile.PL file (save the patch into a
+ file and use the command <B
+CLASS="COMMAND"
+>patch <
+ patchfile</B
+>:
+ </P
+><P
+> <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>
+--- GD-1.33/Makefile.PL Fri Aug 4 16:59:22 2000
++++ GD-1.33-darwin/Makefile.PL Tue Jun 26 01:29:32 2001
+@@ -3,8 +3,8 @@
+ warn "NOTICE: This module requires libgd 1.8.3 or higher (shared library version 4.X).\n";
+
+ # =====> PATHS: CHECK AND ADJUST <=====
+-my @INC = qw(-I/usr/local/include -I/usr/local/include/gd);
+-my @LIBPATH = qw(-L/usr/lib/X11 -L/usr/X11R6/lib -L/usr/X11/lib -L/usr/local/lib );
++my @INC = qw(-I/sw/include -I/sw/include/gd -I/usr/local/include -I/usr/local/include/gd);
++my @LIBPATH = qw(-L/usr/lib/X11 -L/usr/X11R6/lib -L/usr/X11/lib -L/sw/lib -L/usr/local/lib);
+ my @LIBS = qw(-lgd -lpng -lz);
+
+ # FEATURE FLAGS
+@@ -23,7 +23,7 @@
+
+ push @LIBS,'-lttf' if $TTF;
+ push @LIBS,'-ljpeg' if $JPEG;
+-push @LIBS, '-lm' unless $^O eq 'MSWin32';
++push @LIBS, '-lm' unless ($^O =~ /^MSWin32|darwin$/);
+
+ # FreeBSD 3.3 with libgd built from ports croaks if -lXpm is specified
+ if ($^O ne 'freebsd' && $^O ne 'MSWin32') {
+
+
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+ </P
+><P
+> Then, run these commands to finish the installation of the perl module:
+ <P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+><B
+CLASS="COMMAND"
+>perl Makefile.PL</B
+></TD
+></TR
+><TR
+><TD
+><B
+CLASS="COMMAND"
+>make</B
+></TD
+></TR
+><TR
+><TD
+><B
+CLASS="COMMAND"
+>make test</B
+></TD
+></TR
+><TR
+><TD
+><B
+CLASS="COMMAND"
+>make install</B
+></TD
+></TR
+><TR
+><TD
+>And don't forget to run <B
+CLASS="COMMAND"
+>exit</B
+> to get back to cpan.</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+>
+ </P
+><P
+> Happy Hacking!
+ </P
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="stepbystep.html"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="bsdinstall.html"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Step-by-step Install</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="installation.html"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>BSD Installation Notes</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file
diff --git a/docs/html/patches.html b/docs/html/patches.html
index 9591e67ae..877cb9134 100644
--- a/docs/html/patches.html
+++ b/docs/html/patches.html
@@ -4,17 +4,17 @@
>Useful Patches and Utilities for Bugzilla</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="PREVIOUS"
-TITLE="Red Hat Bugzilla"
-HREF="rhbugzilla.html"><LINK
+TITLE="MySQL Permissions & Grant Tables"
+HREF="granttables.html"><LINK
REL="NEXT"
-TITLE="The setperl.csh Utility"
-HREF="setperl.html"></HEAD
+TITLE="Apache mod_rewrite magic"
+HREF="rewrite.html"></HEAD
><BODY
CLASS="APPENDIX"
BGCOLOR="#FFFFFF"
@@ -41,7 +41,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
-HREF="rhbugzilla.html"
+HREF="granttables.html"
>Prev</A
></TD
><TD
@@ -54,7 +54,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
-HREF="setperl.html"
+HREF="rewrite.html"
>Next</A
></TD
></TR
@@ -78,21 +78,36 @@ CLASS="TOC"
></DT
><DT
>D.1. <A
+HREF="rewrite.html"
+>Apache <TT
+CLASS="FILENAME"
+>mod_rewrite</TT
+> magic</A
+></DT
+><DT
+>D.2. <A
HREF="setperl.html"
>The setperl.csh Utility</A
></DT
><DT
->D.2. <A
+>D.3. <A
HREF="cmdline.html"
>Command-line Bugzilla Queries</A
></DT
><DT
->D.3. <A
+>D.4. <A
HREF="quicksearch.html"
>The Quicksearch Utility</A
></DT
+><DT
+>D.5. <A
+HREF="bzhacking.html"
+>Hacking Bugzilla</A
+></DT
></DL
></DIV
+><P
+>Are you looking for a way to put your Bugzilla into overdrive? Catch some of the niftiest tricks here in this section.</P
></DIV
><DIV
CLASS="NAVFOOTER"
@@ -109,7 +124,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
-HREF="rhbugzilla.html"
+HREF="granttables.html"
>Prev</A
></TD
><TD
@@ -125,7 +140,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
-HREF="setperl.html"
+HREF="rewrite.html"
>Next</A
></TD
></TR
@@ -134,7 +149,7 @@ HREF="setperl.html"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
->Red Hat Bugzilla</TD
+>MySQL Permissions & Grant Tables</TD
><TD
WIDTH="34%"
ALIGN="center"
@@ -144,7 +159,10 @@ VALIGN="top"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
->The setperl.csh Utility</TD
+>Apache <TT
+CLASS="FILENAME"
+>mod_rewrite</TT
+> magic</TD
></TR
></TABLE
></DIV
diff --git a/docs/html/postinstall-check.html b/docs/html/postinstall-check.html
index 2ab4a39ce..5b0cbbb7a 100644
--- a/docs/html/postinstall-check.html
+++ b/docs/html/postinstall-check.html
@@ -4,7 +4,7 @@
>Post-Installation Checklist</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
@@ -51,7 +51,7 @@ HREF="administration.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
->Chapter 3. Administering Bugzilla</TD
+>Chapter 4. Administering Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
@@ -71,14 +71,14 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="POSTINSTALL-CHECK"
->3.1. Post-Installation Checklist</A
+>4.1. Post-Installation Checklist</A
></H1
><P
-> After installation, follow the checklist below to ensure that
- you have a successful installation.
- If you do not see a recommended setting for a parameter,
- consider leaving it at the default
- while you perform your initial tests on your Bugzilla setup.
+> After installation, follow the checklist below to help ensure
+ that you have a successful installation. If you do not see a
+ recommended setting for a parameter, consider leaving it at the
+ default while you perform your initial tests on your Bugzilla
+ setup.
</P
><DIV
CLASS="PROCEDURE"
@@ -86,171 +86,412 @@ CLASS="PROCEDURE"
TYPE="1"
><LI
><P
-> Bring up "editparams.cgi" in your web browser. For instance, to edit parameters
- at mozilla.org, the URL would be <A
-HREF="http://bugzilla.mozilla.org/editparams.cgi"
-TARGET="_top"
-> http://bugzilla.mozilla.org/editparams.cgi</A
->, also available under the "edit parameters"
- link on your query page.
+> Bring up <TT
+CLASS="FILENAME"
+>editparams.cgi</TT
+> in your web
+ browser. This should be available as the <SPAN
+CLASS="QUOTE"
+>"edit
+ parameters"</SPAN
+> link from any Bugzilla screen once you
+ have logged in.
</P
></LI
><LI
><P
-> Set "maintainer" to <EM
+>The <SPAN
+CLASS="QUOTE"
+>"maintainer"</SPAN
+> is the email address of
+ the person responsible for maintaining this Bugzilla
+ installation. The maintainer need not be a valid Bugzilla
+ user. Error pages, error emails, and administrative mail
+ will be sent with the maintainer as the return email
+ address.</P
+><P
+> Set <SPAN
+CLASS="QUOTE"
+>"maintainer"</SPAN
+> to <EM
>your</EM
> email address.
- This allows Bugzilla's error messages
- to display your email
+ This allows Bugzilla's error messages to display your email
address and allow people to contact you for help.
</P
></LI
><LI
><P
-> Set "urlbase" to the URL reference for your Bugzilla installation.
- If your bugzilla query page is at http://www.foo.com/bugzilla/query.cgi,
- your url base is http://www.foo.com/bugzilla/
+>The <SPAN
+CLASS="QUOTE"
+>"urlbase"</SPAN
+> parameter defines the fully
+ qualified domain name and web server path to your Bugzilla
+ installation.</P
+><P
+> For example, if your bugzilla query page is
+ http://www.foo.com/bugzilla/query.cgi, set your
+ <SPAN
+CLASS="QUOTE"
+>"urlbase"</SPAN
+> is http://www.foo.com/bugzilla/.
</P
></LI
><LI
><P
-> Set "usebuggroups" to "1" <EM
+><SPAN
+CLASS="QUOTE"
+>"usebuggroups"</SPAN
+> dictates whether or not to
+ implement group-based security for Bugzilla. If set,
+ Bugzilla bugs can have an associated groupmask defining
+ which groups of users are allowed to see and edit the
+ bug.</P
+><P
+> Set "usebuggroups" to "on" <EM
>only</EM
->
- if you need to restrict access to products.
- I suggest leaving this parameter <EM
+> if you
+ may wish to restrict access to products. I suggest leaving
+ this parameter <EM
>off</EM
->
- while initially testing your Bugzilla.
+> while initially
+ testing your Bugzilla.
</P
></LI
><LI
><P
-> Set "usebuggroupsentry" to "1" if you want to restrict access to products.
- Once again, if you are simply testing your installation, I suggest against
- turning this parameter on; the strict security checking may stop you from
- being able to modify your new entries.
+> <SPAN
+CLASS="QUOTE"
+>"usebuggroupsentry"</SPAN
+>, when set to
+ <SPAN
+CLASS="QUOTE"
+>"on"</SPAN
+>, requires that all bugs have an associated
+ groupmask when submitted. This parameter is made for those
+ installations where product isolation is a necessity.
+ </P
+><P
+> Set "usebuggroupsentry" to "on" if you absolutely need to
+ restrict access to bugs from the moment they are submitted
+ through resolution. Once again, if you are simply testing
+ your installation, I suggest against turning this parameter
+ on; the strict security checking may stop you from being
+ able to modify your new entries.
</P
></LI
><LI
><P
-> Set "shadowdb" to "bug_shadowdb" if you will be
- running a *very* large installation of Bugzilla.
- The shadow database enables many simultaneous users
- to read and write to the database
- without interfering with one another.
+> You run into an interesting problem when Bugzilla reaches a
+ high level of continuous activity. MySQL supports only
+ table-level write locking. What this means is that if
+ someone needs to make a change to a bug, they will lock the
+ entire table until the operation is complete. Locking for
+ write also blocks reads until the write is complete. The
+ <SPAN
+CLASS="QUOTE"
+>"shadowdb"</SPAN
+> parameter was designed to get around
+ this limitation. While only a single user is allowed to
+ write to a table at a time, reads can continue unimpeded on
+ a read-only shadow copy of the database. Although your
+ database size will double, a shadow database can cause an
+ enormous performance improvement when implemented on
+ extremely high-traffic Bugzilla databases.
+ </P
+><P
+> Set "shadowdb" to "bug_shadowdb" if you will be running a
+ *very* large installation of Bugzilla. The shadow database
+ enables many simultaneous users to read and write to the
+ database without interfering with one another.
<DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><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
-><B
->Note: </B
> Enabling "shadowdb" can adversely affect the stability
- of your installation of Bugzilla.
- You may frequently need to manually synchronize your databases,
- or schedule nightly syncs
- via "cron"
+ of your installation of Bugzilla. You should regularly
+ check that your database is in sync. It is often
+ advisable to force a shadow database sync nightly via
+ <SPAN
+CLASS="QUOTE"
+>"cron"</SPAN
+>.
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
->
- Once again, in testing you should
- avoid this option -- use it if or when you <EM
+> Once again, in testing you should avoid this option
+ -- use it if or when you <EM
>need</EM
-> to use it, and have
- repeatedly run into the problem it was designed to solve -- very long wait times while
- attempting to commit a change to the database.
+> to use
+ it, and have repeatedly run into the problem it was designed
+ to solve -- very long wait times while attempting to commit
+ a change to the database. Mozilla.org began needing
+ <SPAN
+CLASS="QUOTE"
+>"shadowdb"</SPAN
+> when they reached around 40,000
+ Bugzilla users with several hundred Bugzilla bug changes and
+ comments per day.
</P
><P
-> If you use the "shadowdb" option,
- it is only natural that you should turn the "queryagainstshadowdb"
- option "On" as well. Otherwise you are replicating data into a shadow database for no reason!
+> If you use the "shadowdb" option, it is only natural that
+ you should turn the "queryagainstshadowdb" option "On" as
+ well. Otherwise you are replicating data into a shadow
+ database for no reason!
</P
></LI
><LI
><P
-> If you have custom logos or HTML you must put in place to fit within your site design guidelines,
- place the code in the "headerhtml", "footerhtml", "errorhtml",
- "bannerhtml", or "blurbhtml" text boxes.
+><SPAN
+CLASS="QUOTE"
+>"headerhtml"</SPAN
+>, <SPAN
+CLASS="QUOTE"
+>"footerhtml"</SPAN
+>,
+ <SPAN
+CLASS="QUOTE"
+>"errorhtml"</SPAN
+>, <SPAN
+CLASS="QUOTE"
+>"bannerhtml"</SPAN
+>, and
+ <SPAN
+CLASS="QUOTE"
+>"blurbhtml"</SPAN
+> are all templates which control
+ display of headers, footers, errors, banners, and additional
+ data. We could go into some detail regarding the usage of
+ these, but it is really best just to monkey around with them
+ a bit to see what they do. I strongly recommend you copy
+ your <TT
+CLASS="FILENAME"
+>data/params</TT
+> file somewhere safe
+ before playing with these values, though. If they are
+ changed dramatically, it may make it impossible for you to
+ display Bugzilla pages to fix the problem until you have
+ restored your <TT
+CLASS="FILENAME"
+>data/params</TT
+> file.</P
+><P
+> If you have custom logos or HTML you must put in place to
+ fit within your site design guidelines, place the code in
+ the "headerhtml", "footerhtml", "errorhtml", "bannerhtml",
+ or "blurbhtml" text boxes.
<DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><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
-><B
->Note: </B
> The "headerhtml" text box is the HTML printed out
<EM
>before</EM
-> any other code on the page.
- If you have a special banner, put the code for it in "bannerhtml".
- You may want to leave these
- settings at the defaults initially.
+> any other code on the page,
+ except the CONTENT-TYPE header sent by the Bugzilla
+ engine. If you have a special banner, put the code for
+ it in "bannerhtml". You may want to leave these settings
+ at the defaults initially.
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
>
</P
></LI
><LI
><P
-> Add any text you wish to the "passwordmail" parameter box. For instance,
- many people choose to use this box to give a quick training blurb about how to
- use Bugzilla at your site.
+><SPAN
+CLASS="QUOTE"
+>"passwordmail"</SPAN
+> is rather simple. Every
+ time a user creates an account, the text of this parameter
+ is read as the text to send to the new user along with their
+ password message.</P
+><P
+> Add any text you wish to the "passwordmail" parameter box.
+ For instance, many people choose to use this box to give a
+ quick training blurb about how to use Bugzilla at your site.
</P
></LI
><LI
><P
-> Ensure "newemailtech" is "on".
- Your users will thank you. This is the default in the post-2.12 world, and is
- only an issue if you are upgrading.
- </P
-></LI
-><LI
+><SPAN
+CLASS="QUOTE"
+>"useqacontact"</SPAN
+> allows you to define an
+ email address for each component, in addition to that of the
+ default owner, who will be sent carbon copies of incoming
+ bugs. The critical difference between a QA Contact and an
+ Owner is that the QA Contact follows the component. If you
+ reassign a bug from component A to component B, the QA
+ Contact for that bug will change with the reassignment,
+ regardless of owner.</P
+><P
+><SPAN
+CLASS="QUOTE"
+>"usestatuswhiteboard"</SPAN
+> defines whether you
+ wish to have a free-form, overwritable field associated with
+ each bug. The advantage of the Status Whiteboard is that it
+ can be deleted or modified with ease, and provides an
+ easily-searchable field for indexing some bugs that have
+ some trait in common. Many people will put <SPAN
+CLASS="QUOTE"
+>"help
+ wanted"</SPAN
+>, <SPAN
+CLASS="QUOTE"
+>"stalled"</SPAN
+>, or <SPAN
+CLASS="QUOTE"
+>"waiting
+ on reply from somebody"</SPAN
+> messages into the Status
+ Whiteboard field so those who peruse the bugs are aware of
+ their status even more than that which can be indicated by
+ the Resolution fields.</P
><P
-> Do you want to use the qa contact ("useqacontact")
- and status whiteboard ("usestatuswhiteboard") fields?
- These fields are useful because they allow for more flexibility,
- particularly when you have an existing
- Quality Assurance and/or Release Engineering team,
- but they may not be needed for smaller installations.
+> Do you want to use the QA Contact ("useqacontact") and
+ status whiteboard ("usestatuswhiteboard") fields? These
+ fields are useful because they allow for more flexibility,
+ particularly when you have an existing Quality Assurance
+ and/or Release Engineering team, but they may not be needed
+ for many smaller installations.
</P
></LI
><LI
><P
-> Set "whinedays" to the amount of days you want to let bugs go
- in the "New" or "Reopened" state before
- notifying people they have untouched new bugs. If you do not plan to use this feature, simply do
- not set up the whining cron job described in the README, or set this value to "0".
+> Set "whinedays" to the amount of days you want to let bugs
+ go in the "New" or "Reopened" state before notifying people
+ they have untouched new bugs. If you do not plan to use
+ this feature, simply do not set up the whining cron job
+ described in the installation instructions, or set this
+ value to "0" (never whine).
</P
></LI
><LI
><P
+><SPAN
+CLASS="QUOTE"
+>"commenton"</SPAN
+> fields allow you to dictate
+ what changes can pass without comment, and which must have a
+ comment from the person who changed them. Often,
+ administrators will allow users to add themselves to the CC
+ list, accept bugs, or change the Status Whiteboard without
+ adding a comment as to their reasons for the change, yet
+ require that most other changes come with an
+ explanation.</P
+><P
> Set the "commenton" options according to your site policy.
- It is a wise idea to require comments when users
- resolve, reassign, or reopen bugs.
+ It is a wise idea to require comments when users resolve,
+ reassign, or reopen bugs at the very least.
<DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><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
-><B
->Note: </B
-> It is generally far better to require a developer comment when resolving bugs than not.
- Few things are more annoying to bug database users than having a developer
- mark a bug "fixed" without any comment as to what the fix was (or even that it was truly fixed!)
+> It is generally far better to require a developer
+ comment when resolving bugs than not. Few things are
+ more annoying to bug database users than having a
+ developer mark a bug "fixed" without any comment as to
+ what the fix was (or even that it was truly fixed!)
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
>
</P
></LI
><LI
><P
-> Set "supportwatchers" to "On". This feature is helpful for team leads to monitor progress in their
- respective areas, and can offer many other benefits, such as allowing a developer to pick up a
- former engineer's bugs without requiring her to change all the information in the bug.
+>The <SPAN
+CLASS="QUOTE"
+>"supportwatchers"</SPAN
+> option can be an
+ exceptionally powerful tool in the hands of a power Bugzilla
+ user. By enabling this option, you allow users to receive
+ email updates whenever other users receive email updates.
+ This is, of course, subject to the groupset restrictions on
+ the bug; if the <SPAN
+CLASS="QUOTE"
+>"watcher"</SPAN
+> would not normally be
+ allowed to view a bug, the watcher cannot get around the
+ system by setting herself up to watch the bugs of someone
+ with bugs outside her priveleges. She would still only
+ receive email updates for those bugs she could normally
+ view.</P
+><P
+>For Bugzilla sites which require strong inter-Product
+ security to prevent snooping, watchers are not a good
+ idea.</P
+><P
+> However, for most sites you should set
+ <SPAN
+CLASS="QUOTE"
+>"supportwatchers"</SPAN
+> to "On". This feature is
+ helpful for team leads to monitor progress in their
+ respective areas, and can offer many other benefits, such as
+ allowing a developer to pick up a former engineer's bugs
+ without requiring her to change all the information in the
+ bug.
</P
></LI
></OL
diff --git a/docs/html/programadmin.html b/docs/html/programadmin.html
index 0098bf805..ea2bcbcfc 100644
--- a/docs/html/programadmin.html
+++ b/docs/html/programadmin.html
@@ -1,10 +1,11 @@
<HTML
><HEAD
><TITLE
->Product, Component, Milestone, and Version Administration</TITLE
+>Product, Component, Milestone, and Version
+ Administration</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
@@ -51,7 +52,7 @@ HREF="useradmin.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
->Chapter 3. Administering Bugzilla</TD
+>Chapter 4. Administering Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
@@ -71,7 +72,8 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="PROGRAMADMIN"
->3.3. Product, Component, Milestone, and Version Administration</A
+>4.3. Product, Component, Milestone, and Version
+ Administration</A
></H1
><TABLE
BORDER="0"
@@ -102,11 +104,12 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="PRODUCTS"
->3.3.1. Products</A
+>4.3.1. Products</A
></H2
><FONT
COLOR="RED"
->Formerly, and in some spots still, called "Programs"</FONT
+>Formerly, and in some spots still, called
+ "Programs"</FONT
><P
> <A
HREF="glossary.html#GLOSS_PRODUCT"
@@ -114,19 +117,21 @@ HREF="glossary.html#GLOSS_PRODUCT"
CLASS="GLOSSTERM"
>Products</I
></A
-> are the
- broadest category in Bugzilla, and you should have the least of these.
- If your company makes computer games, you should have one product per game,
- and possibly a few special products
- (website, meetings...)
+> are
+ the broadest category in Bugzilla, and you should have the
+ least of these. If your company makes computer games, you
+ should have one product per game, and possibly a few special
+ products (website, meetings...)
</P
><P
-> A Product (formerly called "Program", and still referred to that way
- in some portions of the source code) controls some very important functions.
- The number of "votes" available for users to vote for the most important bugs
- is set per-product, as is the number of votes required to move a bug automatically
- from the UNCONFIRMED status to the NEW status. One can close a Product for further
- bug entry and define various Versions available from the Edit Product screen.
+> A Product (formerly called "Program", and still referred to
+ that way in some portions of the source code) controls some
+ very important functions. The number of "votes" available for
+ users to vote for the most important bugs is set per-product,
+ as is the number of votes required to move a bug automatically
+ from the UNCONFIRMED status to the NEW status. One can close
+ a Product for further bug entry and define various Versions
+ available from the Edit product screen.
</P
><P
>To create a new product:</P
@@ -140,16 +145,33 @@ TYPE="1"
</P
><DIV
CLASS="TIP"
-><BLOCKQUOTE
+><P
+></P
+><TABLE
CLASS="TIP"
+WIDTH="90%"
+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
-><B
->Tip: </B
-> It may seem counterintuitive to click "components" when you want
- to edit the properties associated with Products. This is one of a long
- list of things we want in Bugzilla 3.0...
+> It may seem counterintuitive to click "components" when
+ you want to edit the properties associated with
+ Products. This is one of a long list of things we want
+ in Bugzilla 3.0...
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
></LI
><LI
@@ -159,25 +181,41 @@ CLASS="TIP"
></LI
><LI
><P
-> Enter the name of the product and a description.
- The Description field is free-form.
+> Enter the name of the product and a description. The
+ Description field is free-form.
</P
></LI
></OL
><DIV
CLASS="TIP"
-><BLOCKQUOTE
+><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
-><B
->Tip: </B
-> Don't worry about the "Closed for bug entry", "Maximum Votes per person",
- "Maximum votes a person can put on a single bug", "Number of votes a bug in
- this Product needs to automatically get out of the UNCOMFIRMED state",
- and "Version" options yet.
- We'll cover those in a few moments.
+> Don't worry about the "Closed for bug entry", "Maximum Votes
+ per person", "Maximum votes a person can put on a single
+ bug", "Number of votes a bug in this Product needs to
+ automatically get out of the UNCOMFIRMED state", and
+ "Version" options yet. We'll cover those in a few moments.
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
></DIV
><DIV
@@ -186,7 +224,7 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="COMPONENTS"
->3.3.2. Components</A
+>4.3.2. Components</A
></H2
><P
> Components are subsections of a Product.
@@ -194,40 +232,44 @@ NAME="COMPONENTS"
<DIV
CLASS="EXAMPLE"
><A
-NAME="AEN838"
+NAME="AEN1461"
></A
><P
><B
->Example 3-1. Creating some Components</B
+>Example 4-1. Creating some Components</B
></P
><DIV
CLASS="INFORMALEXAMPLE"
><A
-NAME="AEN840"
+NAME="AEN1463"
></A
><P
></P
><P
-> The computer game you are designing may 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.
+> 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.
</P
><P
></P
></DIV
></DIV
->
-
- 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
- <EM
+> 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 <EM
>default assignments</EM
->; the Owner and Q/A Contact fields in a bug
- are otherwise unrelated to the Component.
+>; the
+ Owner and QA Contact fields in a bug are otherwise unrelated
+ to the Component.
</P
><P
> To create a new Component:
@@ -238,72 +280,93 @@ NAME="AEN840"
TYPE="1"
><LI
><P
-> Select the "Edit components" link from the "Edit Product" page
+> Select the "Edit components" link from the "Edit product"
+ page
</P
></LI
><LI
><P
-> Select the "Add" link to the right of the "Add a new component" text
- on the "Select Component" page.
+> Select the "Add" link to the right of the "Add a new
+ component" text on the "Select Component" page.
</P
></LI
><LI
><P
-> Fill out the "Component" field, a short "Description", and the "Initial Owner".
- The "Component" field should not contain a space. The "Description" field is
- free-form. The "Initial Owner" field must be that of a valid user already
- existing in the database. If the initial owner does not exist, Bugzilla
- will refuse to create the component.
+> Fill out the "Component" field, a short "Description", and
+ the "Initial Owner". The Component and Description fields
+ are free-form; the "Initial Owner" field must be that of a
+ user ID already existing in the database. If the initial
+ owner does not exist, Bugzilla will refuse to create the
+ component.
<DIV
CLASS="TIP"
-><BLOCKQUOTE
+><P
+></P
+><TABLE
CLASS="TIP"
+WIDTH="90%"
+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
-><B
->Tip: </B
-> Is your "Default Owner" a user who is not yet in the database?
- No problem.
+> Is your "Default Owner" a user who is not yet in the
+ database? No problem.
<P
></P
><OL
TYPE="a"
><LI
><P
-> Select the "Log out" link on the footer of the page.
+> Select the "Log out" link on the footer of the
+ page.
</P
></LI
><LI
><P
-> Select the "New Account" link on the footer of the "Relogin" page
+> Select the "New Account" link on the footer of
+ the "Relogin" page
</P
></LI
><LI
><P
-> Type in the email address of the default owner you want to create
- in the "E-mail address" field, and her full name in the "Real name"
+> Type in the email address of the default owner
+ you want to create in the "E-mail address"
+ field, and her full name in the "Real name"
field, then select the "Submit Query" button.
</P
></LI
><LI
><P
-> Now select "Log in" again, type in your login information, and you
- can modify the product to use the Default Owner information
- you require.
+> Now select "Log in" again, type in your login
+ information, and you can modify the product to
+ use the Default Owner information you require.
</P
></LI
></OL
>
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
>
</P
></LI
><LI
><P
-> Either "edit" more components or return to the "query" page on the ensuing
- "Addming new component" page. To return to the Product you were editing, you
- must select the "components" link as before.
+> Either Edit more components or return to the Bugzilla
+ Query Page. To return to the Product you were editing, you
+ must select the Components link as before.
</P
></LI
></OL
@@ -314,37 +377,38 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="VERSIONS"
->3.3.3. Versions</A
+>4.3.3. Versions</A
></H2
><P
-> Versions are the revisions of the product, such as "Flinders 3.1", "Flinders 95",
- and "Flinders 2000". Using Versions helps you isolate code changes and are an aid
- in reporting.
+> Versions are the revisions of the product, such as "Flinders
+ 3.1", "Flinders 95", and "Flinders 2000". Using Versions
+ helps you isolate code changes and are an aid in reporting.
<DIV
CLASS="EXAMPLE"
><A
-NAME="AEN867"
+NAME="AEN1490"
></A
><P
><B
->Example 3-2. Common Use of Versions</B
+>Example 4-2. Common Use of Versions</B
></P
><DIV
CLASS="INFORMALEXAMPLE"
><A
-NAME="AEN869"
+NAME="AEN1492"
></A
><P
></P
><P
-> A user reports a bug
- against Version "Beta 2.0" of your product. The current Version of your software
- is "Release Candidate 1", and no longer has the bug. This will
- help you triage and classify bugs according to their relevance. It is also
- possible people may report bugs against bleeding-edge beta versions that are
- not evident in older versions of the software. This can help isolate code
- changes that caused the bug
+> A user reports a bug against Version "Beta 2.0" of your
+ product. The current Version of your software is
+ "Release Candidate 1", and no longer has the bug. This
+ will help you triage and classify bugs according to
+ their relevance. It is also possible people may report
+ bugs against bleeding-edge beta versions that are not
+ evident in older versions of the software. This can
+ help isolate code changes that caused the bug
</P
><P
></P
@@ -354,27 +418,30 @@ NAME="AEN869"
<DIV
CLASS="EXAMPLE"
><A
-NAME="AEN871"
+NAME="AEN1494"
></A
><P
><B
->Example 3-3. A Different Use of Versions</B
+>Example 4-3. A Different Use of Versions</B
></P
><DIV
CLASS="INFORMALEXAMPLE"
><A
-NAME="AEN873"
+NAME="AEN1496"
></A
><P
></P
><P
-> This field has been used to good effect by an online service provider in a slightly
- different way. They had three versions of the product: "Production", "QA",
- and "Dev". Although it may be the same product, a bug in the development
- environment is not normally as critical as a Production bug, nor does it
- need to be reported publicly. When used in conjunction with Target Milestones,
- one can easily specify the environment where a bug can be reproduced, and
- the Milestone by which it will be fixed.
+> This field has been used to good effect by an online
+ service provider in a slightly different way. They had
+ three versions of the product: "Production", "QA", and
+ "Dev". Although it may be the same product, a bug in
+ the development environment is not normally as critical
+ as a Production bug, nor does it need to be reported
+ publicly. When used in conjunction with Target
+ Milestones, one can easily specify the environment where
+ a bug can be reproduced, and the Milestone by which it
+ will be fixed.
</P
><P
></P
@@ -391,31 +458,35 @@ NAME="AEN873"
TYPE="1"
><LI
><P
-> From the "Edit Product" screen, select "Edit Versions"
+> From the "Edit product" screen, select "Edit Versions"
</P
></LI
><LI
><P
-> You will notice that the product already has the default version "undefined".
- If your product doesn't use version numbers, you may want to leave this as it is
- or edit it so that it is "---". You can then go back to the edit versions page
- and add new versions to your product.
+> You will notice that the product already has the default
+ version "undefined". If your product doesn't use version
+ numbers, you may want to leave this as it is or edit it so
+ that it is "---". You can then go back to the edit
+ versions page and add new versions to your product.
</P
><P
-> Otherwise, click the "Add" button to the right of the "Add a new version" text.
+> Otherwise, click the "Add" button to the right of the "Add
+ a new version" text.
</P
></LI
><LI
><P
-> Enter the name of the Version. This can be free-form characters up to the limit of the
- text box. Then select the "Add" button.
+> Enter the name of the Version. This can be free-form
+ characters up to the limit of the text box. Then select
+ the "Add" button.
</P
></LI
><LI
><P
-> At this point you can select "Edit" to edit more Versions, or return to the "Query"
- page, from which you can navigate back to the product through the "components" link
- at the foot of the Query page.
+> At this point you can select "Edit" to edit more Versions,
+ or return to the "Query" page, from which you can navigate
+ back to the product through the "components" link at the
+ foot of the Query page.
</P
></LI
></OL
@@ -426,27 +497,47 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="MILESTONES"
->3.3.4. Milestones</A
+>4.3.4. Milestones</A
></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 would be assigned the milestone of 3.0. Or, you have a
- bug that you plan to fix for 2.8, this would have a milestone of 2.8.
+> 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. Or, you
+ have a bug that you plan to fix for 2.8, this would have a
+ milestone of 2.8.
</P
><DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><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
-><B
->Note: </B
-> Milestone options will only appear for a Product if you turned the "usetargetmilestone" field
- in the "Edit Parameters" screen "On".
+> Milestone options will only appear for a Product if you
+ turned the "usetargetmilestone" field in the "Edit
+ Parameters" screen "On".
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
><P
-> To create new Milestones, set Default Milestones, and set Milestone URL:
+> To create new Milestones, set Default Milestones, and set
+ Milestone URL:
</P
><P
></P
@@ -459,37 +550,41 @@ TYPE="1"
></LI
><LI
><P
-> Select "Add" to the right of the "Add a new milestone" text
+> Select "Add" to the right of the "Add a new milestone"
+ text
</P
></LI
><LI
><P
> 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.
- Select "Add".
+ 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. Select "Add".
</P
><DIV
CLASS="EXAMPLE"
><A
-NAME="AEN899"
+NAME="AEN1522"
></A
><P
><B
->Example 3-4. Using SortKey with Target Milestone</B
+>Example 4-4. Using SortKey with Target Milestone</B
></P
><DIV
CLASS="INFORMALEXAMPLE"
><A
-NAME="AEN901"
+NAME="AEN1524"
></A
><P
></P
><P
-> Let's say you create a target milestone called "Release 1.0", with Sortkey set to "0".
- Later, you realize that you will have a public beta, called "Beta1".
- You can create a Milestone called "Beta1", with a Sortkey of "-1" in order to ensure
- people will see the Target Milestone of "Beta1" earlier on the list than "Release 1.0"
+> Let's say you create a target milestone called
+ "Release 1.0", with Sortkey set to "0". Later, you
+ realize that you will have a public beta, called
+ "Beta1". You can create a Milestone called "Beta1",
+ with a Sortkey of "-1" in order to ensure people will
+ see the Target Milestone of "Beta1" earlier on the
+ list than "Release 1.0"
</P
><P
></P
@@ -498,53 +593,72 @@ NAME="AEN901"
></LI
><LI
><P
-> If you want to add more milestones, select the "Edit" link.
- If you don't, well shoot, you have to go back to the "query" page and select "components"
- again, and make your way back to the Product you were editing.
+> If you want to add more milestones, select the "Edit"
+ link. If you don't, well shoot, you have to go back to the
+ "query" page and select "components" again, and make your
+ way back to the Product you were editing.
<DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><P
+></P
+><TABLE
CLASS="NOTE"
+WIDTH="90%"
+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
-><B
->Note: </B
-> This is another in the list of unusual user interface decisions that
- we'd like to get cleaned up. Shouldn't there be a link to the effect of
- "edit the Product I was editing when I ended up here"? In any case,
- clicking "components" in the footer takes you back to the "Select product"
- screen, from which you can begin editing your product again.
+> This is another in the list of unusual user interface
+ decisions that we'd like to get cleaned up. Shouldn't
+ there be a link to the effect of "edit the Product I
+ was editing when I ended up here"? In any case,
+ clicking "components" in the footer takes you back to
+ the "Select product" screen, from which you can begin
+ editing your product again.
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
>
</P
></LI
><LI
><P
-> From the Edit Product screen again (once you've made your way back), enter the URL
- for a description of what your milestones are for this product in the "Milestone URL" field.
- It should be of the format "http://www.foo.com/bugzilla/product_milestones.html"
+> From the Edit product screen again (once you've made your
+ way back), enter the URL for a description of what your
+ milestones are for this product in the "Milestone URL"
+ field. It should be of the format
+ "http://www.foo.com/bugzilla/product_milestones.html"
</P
><P
-> Some common uses of this field include product descriptions, product roadmaps,
- and of course a simple description of the meaning of each milestone.
+> Some common uses of this field include product
+ descriptions, product roadmaps, and of course a simple
+ description of the meaning of each milestone.
</P
></LI
><LI
><P
-> If you're using Target Milestones, the "Default Milestone" field must have some
- kind of entry. If you really don't care if people set coherent Target Milestones,
- simply leave this at the default, "---". However, controlling and regularly updating the Default
- Milestone field is a powerful tool when reporting the status of projects.
+> If you're using Target Milestones, the "Default Milestone"
+ field must have some kind of entry. If you really don't
+ care if people set coherent Target Milestones, simply
+ leave this at the default, "---". However, controlling
+ and regularly updating the Default Milestone field is a
+ powerful tool when reporting the status of projects.
</P
><P
>Select the "Update" button when you are done.</P
></LI
-><LI
-><P
->
- </P
-></LI
></OL
></DIV
><DIV
@@ -553,23 +667,28 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="VOTING"
->3.3.5. Voting</A
+>4.3.5. Voting</A
></H2
><P
-> The concept of "voting" is a poorly understood, yet powerful feature for the management
- of open-source projects. Each user is assigned so many Votes per product, which they can
- freely reassign (or assign multiple votes to a single bug).
- 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
+> The concept of "voting" is a poorly understood, yet powerful
+ feature for the management of open-source projects. Each user
+ is assigned so many Votes per product, which they can freely
+ reassign (or assign multiple votes to a single bug). 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.
</P
><P
-> The daunting challenge of Votes is deciding where you draw the line for a "vocal majority". If you
- only have a user base of 100 users, setting a low threshold for bugs to move from UNCONFIRMED
- to NEW makes sense. As the Bugzilla user base expands, however, these thresholds must be
- re-evaluated. You should gauge whether this feature is worth the time and close monitoring involved,
- and perhaps forego implementation until you have a critical mass of users who demand it.
+> The daunting challenge of Votes is deciding where you draw the
+ line for a "vocal majority". If you only have a user base of
+ 100 users, setting a low threshold for bugs to move from
+ UNCONFIRMED to NEW makes sense. As the Bugzilla user base
+ expands, however, these thresholds must be re-evaluated. You
+ should gauge whether this feature is worth the time and close
+ monitoring involved, and perhaps forego implementation until
+ you have a critical mass of users who demand it.
</P
><P
>To modify Voting settings:</P
@@ -579,52 +698,74 @@ NAME="VOTING"
TYPE="1"
><LI
><P
-> Navigate to the "Edit Product" screen for the Product you wish to modify
+> Navigate to the "Edit product" screen for the Product you
+ wish to modify
</P
></LI
><LI
><P
-> Set "Maximum Votes per person" to your calculated value. Setting this field
- to "0" disables voting.
+> Set "Maximum Votes per person" to your calculated value.
+ Setting this field to "0" disables voting.
</P
></LI
><LI
><P
-> Set "Maximum Votes a person can put on a single bug" to your calculated value. It
- should probably be some number lower than the "Maximum votes per person".
- Setting this field to "0" disables voting, but leaves the voting options open
- to the user. This is confusing.
+> Set "Maximum Votes a person can put on a single bug" to
+ your calculated value. It should probably be some number
+ lower than the "Maximum votes per person". Setting this
+ field to "0" disables voting, but leaves the voting
+ options open to the user. This is confusing.
</P
></LI
><LI
><P
-> Set "Number of votes a bug in this product needs to automatically get out of the
- UNCONFIRMED state" to your calculated number. Setting this field to "0"
- disables the automatic move of bugs from UNCONFIRMED to NEW. Some people
- advocate leaving this at "0", but of what use are Votes if your Bugzilla
- user base is unable to affect which bugs appear on Development radar?
+> Set "Number of votes a bug in this product needs to
+ automatically get out of the UNCONFIRMED state" to your
+ calculated number. Setting this field to "0" disables
+ the automatic move of bugs from UNCONFIRMED to NEW. Some
+ people advocate leaving this at "0", but of what use are
+ Votes if your Bugzilla user base is unable to affect which
+ bugs appear on Development radar?
<DIV
CLASS="TIP"
-><BLOCKQUOTE
+><P
+></P
+><TABLE
CLASS="TIP"
+WIDTH="90%"
+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
-><B
->Tip: </B
-> You should probably set this number to higher than a small coalition of
- Bugzilla users can influence it. Most sites use this as a "referendum"
- mechanism -- if users are able to vote a bug out of UNCONFIRMED, it
- is a <EM
+> You should probably set this number to higher than a
+ small coalition of Bugzilla users can influence it.
+ Most sites use this as a "referendum" mechanism -- if
+ users are able to vote a bug out of UNCONFIRMED, it is
+ a <EM
>really</EM
> bad bug!
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
>
</P
></LI
><LI
><P
-> Once you have adjusted the values to your preference, select the "Update" button.
+> Once you have adjusted the values to your preference,
+ select the "Update" button.
</P
></LI
></OL
@@ -635,83 +776,107 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="GROUPS"
->3.3.6. Groups and Group Security</A
+>4.3.6. Groups and Group Security</A
></H2
><P
-> Groups can be very useful in bugzilla, because they allow users to isolate
- bugs or products that should only be seen by certain people. Groups can also
- be a complicated minefield of interdependencies and weirdness if mismanaged.
+> Groups can be very useful in bugzilla, because they allow
+ users to isolate bugs or products that should only be seen by
+ certain people. Groups can also be a complicated minefield of
+ interdependencies and weirdness if mismanaged.
<DIV
CLASS="EXAMPLE"
><A
-NAME="AEN937"
+NAME="AEN1558"
></A
><P
><B
->Example 3-5. When to Use Group Security</B
+>Example 4-5. When to Use Group Security</B
></P
><DIV
CLASS="INFORMALEXAMPLE"
><A
-NAME="AEN939"
+NAME="AEN1560"
></A
><P
></P
><P
-> Many Bugzilla sites isolate "Security-related" bugs from all other bugs.
- This way, they can have a fix ready before the security vulnerability
- is announced to the world. You can create a "Security" product which, by
- default, has no members, and only add members to the group (in their individual
- User page, as described under User Administration) who should have
- priveleged access to "Security" bugs. Alternately, you may create a Group
- independently of any Product, and change the Group mask on individual bugs
- to restrict access to members only of certain Groups.
+> Many Bugzilla sites isolate "Security-related" bugs from
+ all other bugs. This way, they can have a fix ready
+ before the security vulnerability is announced to the
+ world. You can create a "Security" product which, by
+ default, has no members, and only add members to the
+ group (in their individual User page, as described under
+ User Administration) who should have priveleged access
+ to "Security" bugs. Alternately, you may create a Group
+ independently of any Product, and change the Group mask
+ on individual bugs to restrict access to members only of
+ certain Groups.
</P
><P
></P
></DIV
></DIV
->
-
- Groups only work if you enable the "usebuggroups" paramater.
- In addition, if the "usebuggroupsentry" parameter is "On", one can restrict access
- to products by groups, so that only members of a product group are able to view
- bugs within that product.
- Group security in Bugzilla can be divided into two categories:
- Generic and Product-Based.
+> Groups only work if you enable the "usebuggroups"
+ paramater. In addition, if the "usebuggroupsentry" parameter
+ is "On", one can restrict access to products by groups, so
+ that only members of a product group are able to view bugs
+ within that product. Group security in Bugzilla can be divided
+ into two categories: Generic and Product-Based.
</P
><DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><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
-><B
->Note: </B
-> Groups in Bugzilla are a complicated beast that evolved out of very simple user
- permission bitmasks, apparently itself derived from common concepts in UNIX access
- controls. A "bitmask" is a fixed-length number whose value can describe one, and
- only one, set of states. For instance, UNIX file permissions are assigned bitmask
- values: "execute" has a value of 1, "write" has a value of 2,
- and "read" has a value of 4. Add them together,
- and a file can be read, written to, and executed if it has a bitmask of "7". (This
- is a simplified example -- anybody who knows UNIX security knows there is much
- more to it than this. Please bear with me for the purpose of this note.) The only
- way a bitmask scheme can work is by doubling the bit count for each value. Thus
- if UNIX wanted to offer another file permission, the next would have to be a value of
- 8, then the next 16, the next 32, etc.
+> Groups in Bugzilla are a complicated beast that evolved out
+ of very simple user permission bitmasks, apparently itself
+ derived from common concepts in UNIX access controls. A
+ "bitmask" is a fixed-length number whose value can describe
+ one, and only one, set of states. For instance, UNIX file
+ permissions are assigned bitmask values: "execute" has a
+ value of 1, "write" has a value of 2, and "read" has a
+ value of 4. Add them together, and a file can be read,
+ written to, and executed if it has a bitmask of "7". (This
+ is a simplified example -- anybody who knows UNIX security
+ knows there is much more to it than this. Please bear with
+ me for the purpose of this note.) The only way a bitmask
+ scheme can work is by doubling the bit count for each value.
+ Thus if UNIX wanted to offer another file permission, the
+ next would have to be a value of 8, then the next 16, the
+ next 32, etc.
</P
><P
-> Similarly, Bugzilla offers a bitmask to define group permissions, with an internal
- limit of 64. Several are already occupied
- by built-in permissions. The way around this limitation is
- to avoid assigning groups to products if you have many products, avoid bloating
- of group lists, and religiously prune irrelevant groups. In reality, most installations
- of Bugzilla support far fewer than 64 groups, so this limitation has not hit
- for most sites, but it is on the table to be revised for Bugzilla 3.0
- because it interferes with the security schemes of some administrators.
+> Similarly, Bugzilla offers a bitmask to define group
+ permissions, with an internal limit of 64. Several are
+ already occupied by built-in permissions. The way around
+ this limitation is to avoid assigning groups to products if
+ you have many products, avoid bloating of group lists, and
+ religiously prune irrelevant groups. In reality, most
+ installations of Bugzilla support far fewer than 64 groups,
+ so this limitation has not hit for most sites, but it is on
+ the table to be revised for Bugzilla 3.0 because it
+ interferes with the security schemes of some administrators.
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
><P
> To enable Generic Group Security ("usebuggroups"):
@@ -727,57 +892,65 @@ TYPE="1"
></LI
><LI
><P
-> You will generally have no groups set up. Select the "groups" link
- in the footer.
+> You will generally have no groups set up. Select the
+ "groups" link in the footer.
</P
></LI
><LI
><P
-> Take a moment to understand the instructions on the "Edit Groups" screen.
- Once you feel confident you understand what is expected of you, select the
- "Add Group" link.
+> Take a moment to understand the instructions on the "Edit
+ Groups" screen. Once you feel confident you understand
+ what is expected of you, select the "Add Group" link.
</P
></LI
><LI
><P
-> Fill out the "New Name" (remember, no spaces!), "New Description", and "New
- User RegExp" fields. "New User RegExp" allows you to automatically place
- all users who fulfill the Regular Expression into the new group.
+> Fill out the "New Name" (remember, no spaces!), "New
+ Description", and "New User RegExp" fields. "New User
+ RegExp" allows you to automatically place all users who
+ fulfill the Regular Expression into the new group.
<DIV
CLASS="EXAMPLE"
><A
-NAME="AEN954"
+NAME="AEN1575"
></A
><P
><B
->Example 3-6. Creating a New Group</B
+>Example 4-6. Creating a New Group</B
></P
><DIV
CLASS="INFORMALEXAMPLE"
><A
-NAME="AEN956"
+NAME="AEN1577"
></A
><P
></P
><P
-> I created a group called "DefaultGroup" with a description of "This is simply
- a group to play with", and a "New User RegExp" of "*@velio.com". This
- new group automatically includes all Bugzilla users with "@velio.com" at the
- end of their user id. When I finished, my new group was assigned bit #128.
+> I created a group called DefaultGroup with a
+ description of <SPAN
+CLASS="QUOTE"
+>"This is simply a group to play
+ with"</SPAN
+>, and a New User RegExp of <SPAN
+CLASS="QUOTE"
+>".*@mydomain.tld"</SPAN
+>.
+ This new group automatically includes all Bugzilla
+ users with "@mydomain.tld" at the end of their user id.
+ When I finished, my new group was assigned bit #128.
</P
><P
></P
></DIV
></DIV
->
-
- When you have finished, select the "Add" button.
+> When you have finished, select the Add
+ button.
</P
></LI
></OL
><P
-> To enable Product-Based Group Security ("usebuggroupsentry"):
+> To enable Product-Based Group Security (usebuggroupsentry):
</P
><DIV
CLASS="WARNING"
@@ -785,25 +958,28 @@ CLASS="WARNING"
></P
><TABLE
CLASS="WARNING"
-BORDER="1"
WIDTH="100%"
+BORDER="0"
><TR
><TD
+WIDTH="25"
ALIGN="CENTER"
-><B
->Warning</B
-></TD
-></TR
-><TR
+VALIGN="TOP"
+><IMG
+SRC="../images/warning.gif"
+HSPACE="5"
+ALT="Warning"></TD
><TD
ALIGN="LEFT"
+VALIGN="TOP"
><P
-> Don't forget that you only have 64 groups masks available, total, for
- your installation of Bugzilla! If you plan on having more than 50
- products in your individual Bugzilla installation, and require group
- security for your products, you should
- consider either running multiple Bugzillas or using Generic Group Security
- instead of Product-Based ("usebuggroupsentry") Group Security.
+> Don't forget that you only have 64 groups masks available,
+ total, for your installation of Bugzilla! If you plan on
+ having more than 50 products in your individual Bugzilla
+ installation, and require group security for your products,
+ you should consider either running multiple Bugzillas or
+ using Generic Group Security instead of Product-Based
+ ("usebuggroupsentry") Group Security.
</P
></TD
></TR
@@ -815,7 +991,8 @@ ALIGN="LEFT"
TYPE="1"
><LI
><P
-> Turn "On" "usebuggroups" and "usebuggroupsentry" in the "Edit Parameters" screen.
+> Turn "On" "usebuggroups" and "usebuggroupsentry" in the
+ "Edit Parameters" screen.
</P
><DIV
CLASS="WARNING"
@@ -823,25 +1000,29 @@ CLASS="WARNING"
></P
><TABLE
CLASS="WARNING"
-BORDER="1"
WIDTH="90%"
+BORDER="0"
><TR
><TD
+WIDTH="25"
ALIGN="CENTER"
-><B
->Warning</B
-></TD
-></TR
-><TR
+VALIGN="TOP"
+><IMG
+SRC="../images/warning.gif"
+HSPACE="5"
+ALT="Warning"></TD
><TD
ALIGN="LEFT"
+VALIGN="TOP"
><P
-> "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, Products, etc. with the administrative account.
+> "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, Products, etc.
+ with the administrative account.
</P
></TD
></TR
@@ -850,15 +1031,124 @@ ALIGN="LEFT"
></LI
><LI
><P
-> You will generally have no Groups set up, unless you enabled "usebuggroupsentry"
- prior to creating any Products. To create "Generic Group Security" groups,
- follow the instructions given above. To create Product-Based Group security,
- simply follow the instructions for creating a new Product. If you need to
- add users to these new groups as you create them, you will find the option
- to add them to the group available under the "Edit User" screens.
+> You will generally have no Groups set up, unless you
+ enabled "usebuggroupsentry" prior to creating any
+ Products. To create "Generic Group Security" groups,
+ follow the instructions given above. To create
+ Product-Based Group security, simply follow the
+ instructions for creating a new Product. If you need to
+ add users to these new groups as you create them, you will
+ find the option to add them to the group available under
+ the "Edit User" screens.
</P
></LI
></OL
+><P
+> You may find this example illustrative for how bug groups work.
+ <DIV
+CLASS="EXAMPLE"
+><A
+NAME="AEN1592"
+></A
+><P
+><B
+>Example 4-7. Bugzilla Groups</B
+></P
+><P
+CLASS="LITERALLAYOUT"
+>Bugzilla Groups example<br>
+-----------------------<br>
+<br>
+For this example, let us suppose we have four groups, call them<br>
+Group1, Group2, Group3, and Group4.<br>
+<br>
+We have 5 users, User1, User2, User3, User4, User5.<br>
+<br>
+We have 8 bugs, Bug1, ..., Bug8.<br>
+<br>
+Group membership is defined by this chart:<br>
+(X denotes that user is in that group.)<br>
+(I apologize for the nasty formatting of this table. Try viewing<br>
+it in a text-based browser or something for now. -MPB)<br>
+<br>
+ G G G G<br>
+ r r r r<br>
+ o o o o<br>
+ u u u u<br>
+ p p p p<br>
+ 1 2 3 4<br>
+ +-+-+-+-+<br>
+User1|X| | | |<br>
+ +-+-+-+-+<br>
+User2| |X| | |<br>
+ +-+-+-+-+<br>
+User3|X| |X| |<br>
+ +-+-+-+-+<br>
+User4|X|X|X| |<br>
+ +-+-+-+-+<br>
+User5| | | | |<br>
+ +-+-+-+-+<br>
+<br>
+Bug restrictions are defined by this chart:<br>
+(X denotes that bug is restricted to that group.)<br>
+<br>
+ G G G G<br>
+ r r r r<br>
+ o o o o<br>
+ u u u u<br>
+ p p p p<br>
+ 1 2 3 4<br>
+ +-+-+-+-+<br>
+Bug1| | | | |<br>
+ +-+-+-+-+<br>
+Bug2| |X| | |<br>
+ +-+-+-+-+<br>
+Bug3| | |X| |<br>
+ +-+-+-+-+<br>
+Bug4| | | |X|<br>
+ +-+-+-+-+<br>
+Bug5|X|X| | |<br>
+ +-+-+-+-+<br>
+Bug6|X| |X| |<br>
+ +-+-+-+-+<br>
+Bug7|X|X|X| |<br>
+ +-+-+-+-+<br>
+Bug8|X|X|X|X|<br>
+ +-+-+-+-+<br>
+<br>
+Who can see each bug?<br>
+<br>
+Bug1 has no group restrictions. Therefore, Bug1 can be seen by any<br>
+user, whatever their group membership. This is going to be the only<br>
+bug that User5 can see, because User5 isn't in any groups.<br>
+<br>
+Bug2 can be seen by anyone in Group2, that is User2 and User4.<br>
+<br>
+Bug3 can be seen by anyone in Group3, that is User3 and User4.<br>
+<br>
+Bug4 can be seen by anyone in Group4. Nobody is in Group4, so none of<br>
+these users can see Bug4.<br>
+<br>
+Bug5 can be seen by anyone who is in _both_ Group1 and Group2. This<br>
+is only User4. User1 cannot see it because he is not in Group2, and<br>
+User2 cannot see it because she is not in Group1.<br>
+<br>
+Bug6 can be seen by anyone who is in both Group1 and Group3. This<br>
+would include User3 and User4. Similar to Bug5, User1 cannot see Bug6<br>
+because he is not in Group3.<br>
+<br>
+Bug7 can be seen by anyone who is in Group1, Group2, and Group3. This<br>
+is only User4. All of the others are missing at least one of those<br>
+group priveleges, and thus cannot see the bug.<br>
+<br>
+Bug8 can be seen by anyone who is in Group1, Group2, Group3, and<br>
+Group4. There is nobody in all four of these groups, so nobody can<br>
+see Bug8. It doesn't matter that User4 is in Group1, Group2, and<br>
+Group3, since he isn't in Group4.<br>
+ </P
+></DIV
+>
+ </P
></DIV
></DIV
><DIV
diff --git a/docs/html/quicksearch.html b/docs/html/quicksearch.html
index 14df20f49..43ae5c20b 100644
--- a/docs/html/quicksearch.html
+++ b/docs/html/quicksearch.html
@@ -4,7 +4,7 @@
>The Quicksearch Utility</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
@@ -16,8 +16,8 @@ REL="PREVIOUS"
TITLE="Command-line Bugzilla Queries"
HREF="cmdline.html"><LINK
REL="NEXT"
-TITLE="GNU Free Documentation License"
-HREF="gfdl.html"></HEAD
+TITLE="Hacking Bugzilla"
+HREF="bzhacking.html"></HEAD
><BODY
CLASS="SECTION"
BGCOLOR="#FFFFFF"
@@ -57,7 +57,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
-HREF="gfdl.html"
+HREF="bzhacking.html"
>Next</A
></TD
></TR
@@ -71,26 +71,30 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="QUICKSEARCH"
->D.3. The Quicksearch Utility</A
+>D.4. The Quicksearch Utility</A
></H1
><P
> Quicksearch is a new, experimental feature of the 2.12 release.
- It consist of two Javascript files, "quicksearch.js" and "localconfig.js",
- and two documentation files, "quicksearch.html" and "quicksearchhack.html"
+ It consist of two Javascript files, "quicksearch.js" and
+ "localconfig.js", and two documentation files,
+ "quicksearch.html" and "quicksearchhack.html"
</P
><P
-> The index.html page has been updated to include the QuickSearch text box.
+> The index.html page has been updated to include the QuickSearch
+ text box.
</P
><P
-> To take full advantage of the query power, the Bugzilla maintainer must
- edit "localconfig.js" according to the value sets used in the local installation.
+> To take full advantage of the query power, the Bugzilla
+ maintainer must edit "localconfig.js" according to the value
+ sets used in the local installation.
</P
><P
-> Currently, keywords must be hard-coded in localconfig.js. If they are not,
- keywords are not automatically recognized. This means, if localconfig.js
- is left unconfigured, that searching for a bug with the "foo" keyword
- will only find bugs with "foo" in the summary, status whiteboard, product or
- component name, but not those with the keyword "foo".
+> Currently, keywords must be hard-coded in localconfig.js. If
+ they are not, keywords are not automatically recognized. This
+ means, if localconfig.js is left unconfigured, that searching
+ for a bug with the "foo" keyword will only find bugs with "foo"
+ in the summary, status whiteboard, product or component name,
+ but not those with the keyword "foo".
</P
><P
> Workarounds for Bugzilla users:
@@ -101,11 +105,13 @@ BORDER="0"
><TBODY
><TR
><TD
->search for '!foo' (this will find only bugs with the keyword "foo"</TD
+>search for '!foo' (this will find only bugs with the
+ keyword "foo"</TD
></TR
><TR
><TD
->search 'foo,!foo' (equivalent to 'foo OR keyword:foo')</TD
+>search 'foo,!foo' (equivalent to 'foo OR
+ keyword:foo')</TD
></TR
></TBODY
></TABLE
@@ -114,14 +120,13 @@ BORDER="0"
>
</P
><P
-> When this tool is ported from client-side JavaScript to server-side Perl,
- the requirement for hard-coding keywords can be fixed.
- <A
+> When this tool is ported from client-side JavaScript to
+ server-side Perl, the requirement for hard-coding keywords can
+ be fixed. <A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=70907"
TARGET="_top"
>This bug</A
->
- has details.
+> has details.
</P
></DIV
><DIV
@@ -155,7 +160,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
-HREF="gfdl.html"
+HREF="bzhacking.html"
>Next</A
></TD
></TR
@@ -177,7 +182,7 @@ HREF="patches.html"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
->GNU Free Documentation License</TD
+>Hacking Bugzilla</TD
></TR
></TABLE
></DIV
diff --git a/docs/html/readme.unix.html b/docs/html/readme.unix.html
deleted file mode 100644
index faca430af..000000000
--- a/docs/html/readme.unix.html
+++ /dev/null
@@ -1,1735 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->UNIX Installation</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Installing Bugzilla"
-HREF="installation.html"><LINK
-REL="PREVIOUS"
-TITLE="Installing Bugzilla"
-HREF="installation.html"><LINK
-REL="NEXT"
-TITLE="Win32 (Win98+/NT/2K) Installation"
-HREF="readme.windows.html"></HEAD
-><BODY
-CLASS="SECTION"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="installation.html"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 2. Installing Bugzilla</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="readme.windows.html"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="SECTION"
-><H1
-CLASS="SECTION"
-><A
-NAME="README.UNIX"
->2.1. UNIX Installation</A
-></H1
-><DIV
-CLASS="SECTION"
-><H2
-CLASS="SECTION"
-><A
-NAME="AEN190"
->2.1.1. ERRATA</A
-></H2
-><DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
-><P
-><B
->Note: </B
-> If you are installing Bugzilla on S.u.S.e. Linux, or some other
- distributions with "paranoid" security options, it is possible
- that the checksetup.pl script may fail with the error:
- <SPAN
-CLASS="ERRORNAME"
->cannot chdir(/var/spool/mqueue): Permission denied</SPAN
->
- This is because your
- /var/spool/mqueue directory has a mode of "drwx------". Type
- <B
-CLASS="COMMAND"
->chmod 755 /var/spool/mqueue</B
-> as root to fix this problem.
- </P
-></BLOCKQUOTE
-></DIV
-><DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
-><P
-><B
->Note: </B
-> Release Notes for Bugzilla 2.12 are available at docs/rel_notes.txt
- </P
-></BLOCKQUOTE
-></DIV
-><DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
-><P
-><B
->Note: </B
-> The preferred documentation for Bugzilla is available in docs/, with
- a variety of document types available. Please refer to these documents when
- installing, configuring, and maintaining your Bugzilla installation.
- </P
-></BLOCKQUOTE
-></DIV
-><DIV
-CLASS="WARNING"
-><P
-></P
-><TABLE
-CLASS="WARNING"
-BORDER="1"
-WIDTH="100%"
-><TR
-><TD
-ALIGN="CENTER"
-><B
->Warning</B
-></TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-><P
-> Bugzilla is not a package where you can just plop it in a directory,
- twiddle a few things, and you're off. Installing Bugzilla assumes you
- know your variant of UNIX or Microsoft Windows well, are familiar with the
- command line, and are comfortable compiling and installing a plethora
- of third-party utilities. To install Bugzilla on Win32 requires
- fair Perl proficiency, and if you use a webserver other than Apache you
- should be intimately familiar with the security mechanisms and CGI
- environment thereof.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="WARNING"
-><P
-></P
-><TABLE
-CLASS="WARNING"
-BORDER="1"
-WIDTH="100%"
-><TR
-><TD
-ALIGN="CENTER"
-><B
->Warning</B
-></TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-><P
-> Bugzilla has not undergone a complete security review. Security holes
- may exist in the code. Great care should be taken both in the installation
- and usage of this software. Carefully consider the implications of
- installing other network services with Bugzilla.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="SECTION"
-><H2
-CLASS="SECTION"
-><A
-NAME="AEN204"
->2.1.2. Step-by-step Install</A
-></H2
-><DIV
-CLASS="SECTION"
-><H3
-CLASS="SECTION"
-><A
-NAME="AEN206"
->2.1.2.1. Introduction</A
-></H3
-><P
-> Installation of bugzilla is pretty straightforward, particularly if your
- machine already has MySQL and the MySQL-related perl packages installed.
- If those aren't installed yet, then that's the first order of business. The
- other necessary ingredient is a web server set up to run cgi scripts.
- While using Apache for your webserver is not required, it is recommended.
- </P
-><P
-> Bugzilla has been successfully installed under Solaris, Linux, and
- Win32. The peculiarities of installing on Win32 (Win98+/NT/2K) are not
- included in this section of the Guide; please check out the "Win32 Installation Instructions"
- for further advice on getting Bugzilla to work on Microsoft Windows.
- </P
-><P
-> The Bugzilla Guide is contained in the "docs/" folder. It is available
- in plain text (docs/txt), HTML (docs/html), or SGML source (docs/sgml).
- </P
-></DIV
-><DIV
-CLASS="SECTION"
-><H3
-CLASS="SECTION"
-><A
-NAME="AEN211"
->2.1.2.2. Installing the Prerequisites</A
-></H3
-><P
-> The software packages necessary for the proper running of bugzilla are:
- <P
-></P
-><OL
-TYPE="1"
-><LI
-><P
-> MySQL database server and the mysql client (3.22.5 or greater)
- </P
-></LI
-><LI
-><P
-> Perl (5.004 or greater)
- </P
-></LI
-><LI
-><P
-> DBI Perl module
- </P
-></LI
-><LI
-><P
-> Data::Dumper Perl module
- </P
-></LI
-><LI
-><P
-> DBD::mySQL
- </P
-></LI
-><LI
-><P
-> TimeDate Perl module collection
- </P
-></LI
-><LI
-><P
-> GD perl module (1.8.3) (optional, for bug charting)
- </P
-></LI
-><LI
-><P
-> Chart::Base Perl module (0.99c) (optional, for bug charting)
- </P
-></LI
-><LI
-><P
-> DB_File Perl module (optional, for bug charting)
- </P
-></LI
-><LI
-><P
-> The web server of your choice. Apache is recommended.
- </P
-></LI
-><LI
-><P
-> MIME::Parser Perl module (optional, for contrib/bug_email.pl interface)
- </P
-></LI
-></OL
->
- <DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
-><P
-><B
->Note: </B
-> You must run Bugzilla on a filesystem that supports file locking via
- flock(). This is necessary for Bugzilla to operate safely with multiple
- instances.
- </P
-></BLOCKQUOTE
-></DIV
->
- <DIV
-CLASS="WARNING"
-><P
-></P
-><TABLE
-CLASS="WARNING"
-BORDER="1"
-WIDTH="100%"
-><TR
-><TD
-ALIGN="CENTER"
-><B
->Warning</B
-></TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-><P
-> It is a good idea, while installing Bugzilla, to ensure it is not
- <EM
->accessible</EM
-> by other machines on the Internet.
- Your machine may be vulnerable to attacks
- while you are installing. In other words, ensure there is some kind of firewall between you
- and the rest of the Internet. Many installation steps require an active Internet connection
- to complete, but you must take care to ensure that at no point is your machine vulnerable
- to an attack.
- </P
-></TD
-></TR
-></TABLE
-></DIV
->
-
- </P
-></DIV
-><DIV
-CLASS="SECTION"
-><H3
-CLASS="SECTION"
-><A
-NAME="AEN242"
->2.1.2.3. Installing MySQL Database</A
-></H3
-><P
-> Visit MySQL homepage at http://www.mysql.org/ and grab the latest stable
- release of the server. Both binaries and source are available and which
- you get shouldn't matter. Be aware that many of the binary versions
- of MySQL store their data files in /var which on many installations
- (particularly common with linux installations) is part of a smaller
- root partition. If you decide to build from sources you can easily set
- the dataDir as an option to configure.
- </P
-><P
-> If you've installed from source or non-package (RPM, deb, etc.) binaries
- you'll want to make sure to add mysqld to your init scripts so the server
- daemon will come back up whenever your machine reboots.
- You also may want to edit those init scripts, to make sure that
- mysqld will accept large packets. By default, mysqld is set up to only
- accept packets up to 64K long. This limits the size of attachments you
- may put on bugs. If you add something like "-O max_allowed_packet=1M"
- to the command that starts mysqld (or safe_mysqld), then you will be
- able to have attachments up to about 1 megabyte.
- </P
-><DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
-><P
-><B
->Note: </B
-> If you plan on running Bugzilla and MySQL on the same machine,
- consider using the "--skip-networking" option in the init script.
- This enhances security by preventing network access to MySQL.
- </P
-></BLOCKQUOTE
-></DIV
-></DIV
-><DIV
-CLASS="SECTION"
-><H3
-CLASS="SECTION"
-><A
-NAME="AEN248"
->2.1.2.4. Perl (5.004 or greater)</A
-></H3
-><P
-> Any machine that doesn't have perl on it is a sad machine indeed. Perl
- for *nix systems can be gotten in source form from http://www.perl.com.
- </P
-><P
-> Perl is now a far cry from the the single compiler/interpreter binary it
- once was. It now includes a great many required modules and quite a
- few other support files. If you're not up to or not inclined to build
- perl from source, you'll want to install it on your machine using some
- sort of packaging system (be it RPM, deb, or what have you) to ensure
- a sane install. In the subsequent sections you'll be installing quite
- a few perl modules; this can be quite ornery if your perl installation
- isn't up to snuff.
- </P
-><DIV
-CLASS="TIP"
-><BLOCKQUOTE
-CLASS="TIP"
-><P
-><B
->Tip: </B
-> You can skip the following Perl module installation
- steps by installing "Bundle::Bugzilla" from CPAN, which includes them.
- All Perl module installation steps require you have an active Internet
- connection.
- </P
-><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->bash#</TT
->
- <B
-CLASS="COMMAND"
->perl -MCPAN -e 'install "Bundle::Bugzilla"'</B
->
- </TT
->
- </P
-><P
-> Bundle::Bugzilla doesn't include GD, Chart::Base, or MIME::Parser,
- which are not essential to a basic Bugzilla install. If installing
- this bundle fails, you should install each module individually to
- isolate the problem.
- </P
-></BLOCKQUOTE
-></DIV
-></DIV
-><DIV
-CLASS="SECTION"
-><H3
-CLASS="SECTION"
-><A
-NAME="AEN259"
->2.1.2.5. DBI Perl Module</A
-></H3
-><P
-> The DBI module is a generic Perl module used by other database related
- Perl modules. For our purposes it's required by the MySQL-related
- modules. As long as your Perl installation was done correctly the
- DBI module should be a breeze. It's a mixed Perl/C module, but Perl's
- MakeMaker system simplifies the C compilation greatly.
- </P
-><P
-> Like almost all Perl modules DBI can be found on the Comprehensive Perl
- Archive Network (CPAN) at http://www.cpan.org. The CPAN servers have a
- real tendency to bog down, so please use mirrors. The current location
- at the time of this writing (02/17/99) can be found in Appendix A.
- </P
-><P
-> Quality, general Perl module installation instructions can be found on
- the CPAN website, but the easy thing to do is to just use the CPAN shell
- which does all the hard work for you.
- </P
-><P
-> To use the CPAN shell to install DBI:
- <DIV
-CLASS="INFORMALEXAMPLE"
-><A
-NAME="AEN265"
-></A
-><P
-></P
-><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->bash#</TT
->
- <B
-CLASS="COMMAND"
->perl -MCPAN -e 'install "DBI"'</B
->
- </TT
->
- <DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
-><P
-><B
->Note: </B
->Replace "DBI" with the name of whichever module you wish
- to install, such as Data::Dumper, TimeDate, GD, etc.</P
-></BLOCKQUOTE
-></DIV
->
- </P
-><P
-></P
-></DIV
->
- To do it the hard way:
- <DIV
-CLASS="INFORMALEXAMPLE"
-><A
-NAME="AEN272"
-></A
-><P
-></P
-><P
-> Untar the module tarball -- it should create its own directory
- </P
-><P
-> CD to the directory just created, and enter the following commands:
- <P
-></P
-><OL
-TYPE="1"
-><LI
-><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->bash#</TT
->
- <B
-CLASS="COMMAND"
->perl Makefile.PL</B
->
- </TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->bash#</TT
->
- <B
-CLASS="COMMAND"
->make</B
->
- </TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->bash#</TT
->
- <B
-CLASS="COMMAND"
->make test</B
->
- </TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->bash#</TT
->
- <B
-CLASS="COMMAND"
->make install</B
->
- </TT
->
- </P
-></LI
-></OL
->
- If everything went ok that should be all it takes. For the vast
- majority of perl modules this is all that's required.
- </P
-><P
-></P
-></DIV
->
- </P
-></DIV
-><DIV
-CLASS="SECTION"
-><H3
-CLASS="SECTION"
-><A
-NAME="AEN296"
->2.1.2.6. Data::Dumper Perl Module</A
-></H3
-><P
-> The Data::Dumper module provides data structure persistence for Perl
- (similar to Java's serialization). It comes with later sub-releases of
- Perl 5.004, but a re-installation just to be sure it's available won't
- hurt anything.
- </P
-><P
-> Data::Dumper is used by the MySQL related Perl modules. It can be
- found on CPAN (link in Appendix A) and can be installed by following
- the same four step make sequence used for the DBI module.
- </P
-></DIV
-><DIV
-CLASS="SECTION"
-><H3
-CLASS="SECTION"
-><A
-NAME="AEN300"
->2.1.2.7. MySQL related Perl Module Collection</A
-></H3
-><P
-> The Perl/MySQL interface requires a few mutually-dependent perl
- modules. These modules are grouped together into the the
- Msql-Mysql-modules package. This package can be found at CPAN.
- After the archive file has been downloaded it should
- be untarred.
- </P
-><P
-> The MySQL modules are all built using one make file which is generated
- by running:
- <TT
-CLASS="PROMPT"
->bash#</TT
->
- <B
-CLASS="COMMAND"
->perl Makefile.pl</B
->
- </P
-><P
-> The MakeMaker process will ask you a few questions about the desired
- compilation target and your MySQL installation. For many of the questions
- the provided default will be adequate.
- </P
-><P
-> When asked if your desired target is the MySQL or mSQL packages
- selected the MySQL related ones. Later you will be asked if you wish
- to provide backwards compatibility with the older MySQL packages; you
- must answer YES to this question. The default will be no, and if you
- select it things won't work later.
- </P
-><P
-> A host of 'localhost' should be fine and a testing user of 'test' and
- a null password should find itself with sufficient access to run tests
- on the 'test' database which MySQL created upon installation. If 'make
- test' and 'make install' go through without errors you should be ready
- to go as far as database connectivity is concerned.
- </P
-></DIV
-><DIV
-CLASS="SECTION"
-><H3
-CLASS="SECTION"
-><A
-NAME="AEN309"
->2.1.2.8. TimeDate Perl Module Collection</A
-></H3
-><P
-> Many of the more common date/time/calendar related Perl modules have
- been grouped into a bundle similar to the MySQL modules bundle. This
- bundle is stored on the CPAN under the name TimeDate. A (hopefully
- current) link can be found in Appendix A. The component module we're
- most interested in is the Date::Format module, but installing all of them
- is probably a good idea anyway. The standard Perl module installation
- instructions should work perfectly for this simple package.
- </P
-></DIV
-><DIV
-CLASS="SECTION"
-><H3
-CLASS="SECTION"
-><A
-NAME="AEN312"
->2.1.2.9. GD Perl Module (1.8.3)</A
-></H3
-><P
-> The GD library was written by Thomas Boutell a long while ago to
- programatically generate images in C. Since then it's become almost a
- defacto standard for programatic image construction. The Perl bindings
- to it found in the GD library are used on a million web pages to generate
- graphs on the fly. That's what bugzilla will be using it for so you'd
- better install it if you want any of the graphing to work.
- </P
-><P
-> Actually bugzilla uses the Graph module which relies on GD itself,
- but isn't that always the way with OOP. At any rate, you can find the
- GD library on CPAN (link in Appendix "Required Software").
- </P
-><DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
-><P
-><B
->Note: </B
-> The Perl GD library requires some other libraries that may or may not be
- installed on your system, including "libpng" and "libgd". The full requirements
- are listed in the Perl GD library README. Just realize that if compiling GD fails,
- it's probably because you're missing a required library.
- </P
-></BLOCKQUOTE
-></DIV
-></DIV
-><DIV
-CLASS="SECTION"
-><H3
-CLASS="SECTION"
-><A
-NAME="AEN318"
->2.1.2.10. Chart::Base Perl Module (0.99c)</A
-></H3
-><P
-> The Chart module provides bugzilla with on-the-fly charting
- abilities. It can be installed in the usual fashion after it has been
- fetched from CPAN where it is found as the Chart-x.x... tarball in a
- directory to be listed in Appendix "Required Software". Note that as with the GD perl
- module, only the specific versions listed above (or newer) will work. Earlier
- versions used GIF's, which are no longer supported by the latest
- versions of GD.
- </P
-></DIV
-><DIV
-CLASS="SECTION"
-><H3
-CLASS="SECTION"
-><A
-NAME="AEN321"
->2.1.2.11. DB_File Perl Module</A
-></H3
-><P
-> DB_File is a module which allows Perl programs to make use of the facilities provided by
- Berkeley DB version 1.x. This module is required by collectstats.pl which is used for
- bug charting. If you plan to make use of bug charting, you must install this module.
- </P
-></DIV
-><DIV
-CLASS="SECTION"
-><H3
-CLASS="SECTION"
-><A
-NAME="AEN324"
->2.1.2.12. HTTP Server</A
-></H3
-><P
-> You have a freedom of choice here - Apache, Netscape or any other
- server on UNIX would do. You can easily run the web server on a different
- machine than MySQL, but need to adjust the MySQL "bugs" user permissions
- accordingly.
- </P
-><P
-> You'll want to make sure that your web server will run any file
- with the .cgi extension as a cgi and not just display it. If you're using
- apache that means uncommenting the following line in the srm.conf file:
- <TT
-CLASS="COMPUTEROUTPUT"
->AddHandler cgi-script .cgi</TT
->
- </P
-><P
-> With apache you'll also want to make sure that within the access.conf
- file the line:
- <TT
-CLASS="COMPUTEROUTPUT"
-> Options ExecCGI
- </TT
->
- is in the stanza that covers the directories you intend to put the bugzilla
- .html and .cgi files into.
- </P
-><P
-> If you are using a newer version of Apache, both of the above lines will be
- (or will need to be) in the httpd.conf file, rather than srm.conf or
- access.conf.
- </P
-><DIV
-CLASS="WARNING"
-><P
-></P
-><TABLE
-CLASS="WARNING"
-BORDER="1"
-WIDTH="100%"
-><TR
-><TD
-ALIGN="CENTER"
-><B
->Warning</B
-></TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-><P
-> There are two critical directories and a file that should not be a served by
- the HTTP server. These are the 'data' and 'shadow' directories and the
- 'localconfig' file. You should configure your HTTP server to not serve
- content from these files. Failure to do so will expose critical passwords
- and other data. Please see your HTTP server configuration manual on how
- to do this. If you use quips (at the top of the buglist pages) you will want
- the 'data/comments' file to still be served. This file contains those quips.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="SECTION"
-><H3
-CLASS="SECTION"
-><A
-NAME="AEN334"
->2.1.2.13. Installing the Bugzilla Files</A
-></H3
-><P
-> You should untar the Bugzilla files into a directory that you're
- willing to make writable by the default web server user (probably
- 'nobody'). You may decide to put the files off of the main web space
- for your web server or perhaps off of /usr/local with a symbolic link
- in the web space that points to the bugzilla directory. At any rate,
- just dump all the files in the same place (optionally omitting the CVS
- directories if they were accidentally tarred up with the rest of Bugzilla)
- and make sure you can access the files in that directory through your
- web server.
- </P
-><DIV
-CLASS="TIP"
-><BLOCKQUOTE
-CLASS="TIP"
-><P
-><B
->Tip: </B
-> HINT: If you symlink the bugzilla directory into your Apache's
- HTML heirarchy, you may receive "Forbidden" errors unless you
- add the "FollowSymLinks" directive to the <Directory> entry
- for the HTML root.
- </P
-></BLOCKQUOTE
-></DIV
-><P
-> Once all the files are in a web accessible directory, make that
- directory writable by your webserver's user (which may require just
- making it world writable). This is a temporary step until you run
- the post-install "checksetup.pl" script, which locks down your
- installation.
- </P
-><P
-> Lastly, you'll need to set up a symbolic link from /usr/bonsaitools/bin
- to the correct location of your perl executable (probably /usr/bin/perl).
- Otherwise you must hack all the .cgi files to change where they look
- for perl. To make future upgrades easier, you should use the symlink
- approach.
- <DIV
-CLASS="TIP"
-><BLOCKQUOTE
-CLASS="TIP"
-><P
-><B
->Tip: </B
-> If you don't have root access to set this symlink up, check out the
- "setperl.csh" utility, listed in the Patches section of this
- Guide. It will change the path to perl in all your Bugzilla files for
- you.
- </P
-></BLOCKQUOTE
-></DIV
->
- </P
-></DIV
-><DIV
-CLASS="SECTION"
-><H3
-CLASS="SECTION"
-><A
-NAME="AEN343"
->2.1.2.14. Setting Up the MySQL Database</A
-></H3
-><P
-> After you've gotten all the software installed and working you're ready
- to start preparing the database for its life as a the back end to a high
- quality bug tracker.
- </P
-><P
-> First, you'll want to fix MySQL permissions to allow access from
- Bugzilla. For the purpose of this Installation section, the Bugzilla username
- will be "bugs", and will have minimal permissions. Bugzilla has
- not undergone a thorough security audit. It may be possible for
- a system cracker to somehow trick Bugzilla into executing a command
- such as "; DROP DATABASE mysql".
- </P
-><P
-> That would be bad.
- </P
-><P
-> Give the MySQL root user a password. MySQL passwords are
- limited to 16 characters.
- <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->bash#</TT
->
- <B
-CLASS="COMMAND"
->mysql -u root mysql</B
->
- </TT
->
- </TD
-></TR
-><TR
-><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->mysql></TT
->
- <B
-CLASS="COMMAND"
-> UPDATE user SET Password=PASSWORD ('new_password')
- WHERE user='root';
- </B
->
- </TT
->
- </TD
-></TR
-><TR
-><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->mysql></TT
->
- <B
-CLASS="COMMAND"
->FLUSH PRIVILEGES;</B
->
- </TT
->
- </TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
- From this point on, if you need to access MySQL as the
- MySQL root user, you will need to use "mysql -u root -p" and
- enter your new_password. Remember that MySQL user names have
- nothing to do with Unix user names (login names).
- </P
-><P
-> Next, we create the "bugs" user, and grant sufficient
- permissions for checksetup.pl, which we'll use later, to work
- its magic. This also restricts the "bugs" user to operations
- within a database called "bugs", and only allows the account
- to connect from "localhost". Modify it to reflect your setup
- if you will be connecting from another machine or as a different
- user.
- </P
-><P
-> Remember to set bugs_password to some unique password.
- <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->mysql></TT
->
- <B
-CLASS="COMMAND"
->GRANT SELECT,INSERT,UPDATE,DELETE,INDEX,
- ALTER,CREATE,DROP,REFERENCES
- ON bugs.* TO bugs@localhost
- IDENTIFIED BY 'bugs_password';</B
->
- </TT
->
- </TD
-></TR
-><TR
-><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
-> mysql>
- </TT
->
- <B
-CLASS="COMMAND"
-> FLUSH PRIVILEGES;
- </B
->
- </TT
->
- </TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
- </P
-><P
-> Next, run the magic checksetup.pl script. (Many thanks to Holger
- Schurig <holgerschurig@nikocity.de> for writing this script!)
- It will make sure Bugzilla files and directories have reasonable
- permissions, set up the "data" directory, and create all the MySQL
- tables.
- <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->bash#</TT
->
- <B
-CLASS="COMMAND"
->./checksetup.pl</B
->
- </TT
->
- </TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
- The first time you run it, it will create a file called "localconfig".
- </P
-></DIV
-><DIV
-CLASS="SECTION"
-><H3
-CLASS="SECTION"
-><A
-NAME="AEN379"
->2.1.2.15. Tweaking "localconfig"</A
-></H3
-><P
-> This file contains a variety of settings you may need to tweak including
- how Bugzilla should connect to the MySQL database.
- </P
-><P
-> The connection settings include:
- <P
-></P
-><OL
-TYPE="1"
-><LI
-><P
-> server's host: just use "localhost" if the MySQL server is
- local
- </P
-></LI
-><LI
-><P
-> database name: "bugs" if you're following these directions
- </P
-></LI
-><LI
-><P
-> MySQL username: "bugs" if you're following these directions
- </P
-></LI
-><LI
-><P
-> Password for the "bugs" MySQL account above
- </P
-></LI
-></OL
->
- </P
-><P
-> Once you are happy with the settings, re-run checksetup.pl. On this
- second run, it will create the database and an administrator account
- for which you will be prompted to provide information.
- </P
-><P
-> When logged into an administrator account once Bugzilla is running,
- if you go to the query page (off of the bugzilla main menu), you'll
- find an 'edit parameters' option that is filled with editable treats.
- </P
-><P
-> Should everything work, you should have a nearly empty copy of the bug
- tracking setup.
- </P
-><P
-> The second time around, checksetup.pl will stall if it is on a
- filesystem that does not fully support file locking via flock(), such as
- NFS mounts. This support is required for Bugzilla to operate safely with
- multiple instances. If flock() is not fully supported, it will stall at:
- <SPAN
-CLASS="ERRORCODE"
->Now regenerating the shadow database for all bugs.</SPAN
->
- <DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
-><P
-><B
->Note: </B
-> The second time you run checksetup.pl, it is recommended you be the same
- user as your web server runs under, and that you be sure you have set the
- "webservergroup" parameter in localconfig to match the web server's group
- name, if any. Under some systems, otherwise, checksetup.pl will goof up
- your file permissions and make them unreadable to your web server.
- </P
-></BLOCKQUOTE
-></DIV
->
- </P
-><DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
-><P
-><B
->Note: </B
-> The checksetup.pl script is designed so that you can run it at any time
- without causing harm. You should run it after any upgrade to Bugzilla.
- </P
-></BLOCKQUOTE
-></DIV
-></DIV
-><DIV
-CLASS="SECTION"
-><H3
-CLASS="SECTION"
-><A
-NAME="AEN401"
->2.1.2.16. Setting Up Maintainers Manuall (Optional)</A
-></H3
-><P
-> If you want to add someone else to every group by hand, you can do it
- by typing the appropriate MySQL commands. Run '<TT
-CLASS="COMPUTEROUTPUT"
-> mysql -u root -p bugs</TT
->'
- (you may need different parameters, depending on your security settings
- according to section 3, above). Then:
- <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->mysql></TT
->
- <B
-CLASS="COMMAND"
->update profiles set groupset=0x7fffffffffffffff
- where login_name = 'XXX';</B
->
- </TT
->
- </TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
- replacing XXX with the Bugzilla email address.
- </P
-></DIV
-><DIV
-CLASS="SECTION"
-><H3
-CLASS="SECTION"
-><A
-NAME="AEN410"
->2.1.2.17. The Whining Cron (Optional)</A
-></H3
-><P
-> By now you've got a fully functional bugzilla, but what good are bugs
- if they're not annoying? To help make those bugs more annoying you can
- set up bugzilla's automatic whining system. This can be done by adding
- the following command as a daily crontab entry (for help on that see that
- crontab man page):
- <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <B
-CLASS="COMMAND"
->cd <your-bugzilla-directory> ; ./whineatnews.pl</B
->
- </TT
->
- </TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
- </P
-></DIV
-><DIV
-CLASS="SECTION"
-><H3
-CLASS="SECTION"
-><A
-NAME="AEN417"
->2.1.2.18. Bug Graphs (Optional)</A
-></H3
-><P
-> As long as you installed the GD and Graph::Base Perl modules you might
- as well turn on the nifty bugzilla bug reporting graphs.
- </P
-><P
-> Add a cron entry like this to run collectstats daily at 5 after midnight:
- <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->bash#</TT
->
- <B
-CLASS="COMMAND"
->crontab -e</B
->
- </TT
->
- </TD
-></TR
-><TR
-><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> 5 0 * * * cd <your-bugzilla-directory> ; ./collectstats.pl
- </TT
->
- </TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
- </P
-><P
-> After two days have passed you'll be able to view bug graphs from the
- Bug Reports page.
- </P
-></DIV
-><DIV
-CLASS="SECTION"
-><H3
-CLASS="SECTION"
-><A
-NAME="AEN429"
->2.1.2.19. Securing MySQL</A
-></H3
-><P
-> If you followed the README for setting up your "bugs" and "root" user in
- MySQL, much of this should not apply to you. If you are upgrading
- an existing installation of Bugzilla, you should pay close attention
- to this section.
- </P
-><P
-> Most MySQL installs have "interesting" default security parameters:
- <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->mysqld defaults to running as root</TD
-></TR
-><TR
-><TD
->it defaults to allowing external network connections</TD
-></TR
-><TR
-><TD
->it has a known port number, and is easy to detect</TD
-></TR
-><TR
-><TD
->it defaults to no passwords whatsoever</TD
-></TR
-><TR
-><TD
->it defaults to allowing "File_Priv"</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
- </P
-><P
-> This means anyone from anywhere on the internet can not only drop the
- database with one SQL command, and they can write as root to the system.
- </P
-><P
-> To see your permissions do:
- <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->bash#</TT
->
- <B
-CLASS="COMMAND"
->mysql -u root -p</B
->
- </TT
->
- </TD
-></TR
-><TR
-><TD
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->mysql></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
-> starting MySQL in a chroot jail
- </P
-></LI
-><LI
-><P
-> running the httpd in a "chrooted" jail
- </P
-></LI
-><LI
-><P
-> making sure the MySQL passwords are different from the OS
- passwords (MySQL "root" has nothing to do with system "root").
- </P
-></LI
-><LI
-><P
-> running MySQL on a separate untrusted machine
- </P
-></LI
-><LI
-><P
-> making backups ;-)
- </P
-></LI
-></OL
->
- </P
-></DIV
-><DIV
-CLASS="SECTION"
-><H3
-CLASS="SECTION"
-><A
-NAME="AEN495"
->2.1.2.20. Installation General Notes</A
-></H3
-><DIV
-CLASS="SECTION"
-><H4
-CLASS="SECTION"
-><A
-NAME="AEN497"
->2.1.2.20.1. Modifying Your Running System</A
-></H4
-><P
-> Bugzilla optimizes database lookups by storing all relatively static
- information in the versioncache file, located in the data/ subdirectory
- under your installation directory (we said before it needs to be writable,
- right?!)
- </P
-><P
-> If you make a change to the structural data in your database (the
- versions table for example), or to the "constants" encoded in
- defparams.pl, you will need to remove the cached content from the data
- directory (by doing a "rm data/versioncache"), or your changes won't show
- up!
- </P
-><P
-> That file gets automatically regenerated whenever it's more than an
- hour old, so Bugzilla will eventually notice your changes by itself, but
- generally you want it to notice right away, so that you can test things.
- </P
-></DIV
-><DIV
-CLASS="SECTION"
-><H4
-CLASS="SECTION"
-><A
-NAME="AEN502"
->2.1.2.20.2. Upgrading From Previous Versions</A
-></H4
-><P
-> The developers of Bugzilla are constantly adding new tables, columns and
- fields. You'll get SQL errors if you just update the code. The strategy
- to update is to simply always run the checksetup.pl script whenever
- you upgrade your installation of Bugzilla. If you want to see what has
- changed, you can read the comments in that file, starting from the end.
- </P
-></DIV
-><DIV
-CLASS="SECTION"
-><H4
-CLASS="SECTION"
-><A
-NAME="AEN505"
->2.1.2.20.3. UNIX Installation Instructions History</A
-></H4
-><P
-> This document was originally adapted from the Bonsai installation
- instructions by Terry Weissman <terry@mozilla.org>.
- </P
-><P
-> The February 25, 1999 re-write of this page was done by Ry4an Brase
- <ry4an@ry4an.org>, with some edits by Terry Weissman, Bryce Nesbitt,
- Martin Pool, & Dan Mosedale (But don't send bug reports to them!
- Report them using bugzilla, at http://bugzilla.mozilla.org/enter_bug.cgi ,
- project Webtools, component Bugzilla).
- </P
-><P
-> This document was heavily modified again Wednesday, March 07 2001 to
- reflect changes for Bugzilla 2.12 release by Matthew P. Barnson. The
- securing MySQL section should be changed to become standard procedure
- for Bugzilla installations.
- </P
-><P
-> Finally, the README in its entirety was marked up in SGML and included into
- the Guide on April 24, 2001.
- </P
-><P
-> Comments from people using this Guide for the first time are particularly welcome.
- </P
-></DIV
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="installation.html"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="readme.windows.html"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Installing Bugzilla</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="installation.html"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Win32 (Win98+/NT/2K) Installation</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
diff --git a/docs/html/readme.windows.html b/docs/html/readme.windows.html
deleted file mode 100644
index dc29a39ef..000000000
--- a/docs/html/readme.windows.html
+++ /dev/null
@@ -1,755 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Win32 (Win98+/NT/2K) Installation</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Installing Bugzilla"
-HREF="installation.html"><LINK
-REL="PREVIOUS"
-TITLE="UNIX Installation"
-HREF="readme.unix.html"><LINK
-REL="NEXT"
-TITLE="Administering Bugzilla"
-HREF="administration.html"></HEAD
-><BODY
-CLASS="SECTION"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="readme.unix.html"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 2. Installing Bugzilla</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="administration.html"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="SECTION"
-><H1
-CLASS="SECTION"
-><A
-NAME="README.WINDOWS"
->2.2. Win32 (Win98+/NT/2K) Installation</A
-></H1
-><P
-> These directions have <EM
->not</EM
-> been extensively tested.
- We need testers! Please try these out and post any changes to the
- newsgroup.
- </P
-><DIV
-CLASS="SECTION"
-><H2
-CLASS="SECTION"
-><A
-NAME="NTVERIFIED"
->2.2.1. Win32 Installation: Step-by-step</A
-></H2
-><DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
-><P
-><B
->Note: </B
-> You should be familiar with, and cross-reference, the UNIX README
- while performing your Win32 installation. Unfortunately, Win32
- directions are not yet as detailed as those for UNIX.
- </P
-><P
-> The <EM
->most critical</EM
-> difference for Win32 users is
- the lack of support for a crypt() function in MySQL for Windows. It does not
- have it! All ENCRYPT statements must be modified.
- </P
-></BLOCKQUOTE
-></DIV
-><DIV
-CLASS="PROCEDURE"
-><OL
-TYPE="1"
-><LI
-><P
-> Install <A
-HREF="http://www.apache.org/"
-TARGET="_top"
->Apache Web Server</A
->
- for Windows.
- </P
-><DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
-><P
-><B
->Note: </B
-> You may also use Internet Information Server or Personal Web
- Server for this purpose. However, setup is slightly more
- difficult. If ActivePerl doesn't seem to handle your file
- associations correctly (for .cgi and .pl files), please
- consult the FAQ, in the "Win32" section.
- </P
-><P
-> If you are going to use IIS, if on Windows NT you must be updated
- to at least Service Pack 4.
- </P
-></BLOCKQUOTE
-></DIV
-></LI
-><LI
-><P
-> Install <A
-HREF="http://www.activestate.com/"
-TARGET="_top"
->ActivePerl</A
->
- </P
-><P
-> Please also check the following links to fully understand the status
- of ActivePerl on Win32:
- <A
-HREF="http://language.perl.com/newdocs/pod/perlport.html"
-TARGET="_top"
-> Perl Porting</A
->, and
- <A
-HREF="http://ftp.univie.ac.at/packages/perl/ports/nt/FAQ/perlwin32faq5.html"
-TARGET="_top"
-> Hixie Click Here</A
->
- </P
-></LI
-><LI
-><P
-> Use ppm from your perl\bin directory to install the following packs: DBI,
- DBD-Mysql, TimeDate, Chart, Date-Calc, Date-Manip, and GD. You may need
- to extract them from .zip format using Winzip or other unzip program first.
- These additional ppm modules can be downloaded from ActiveState.
- </P
-><P
-> The syntax for ppm is:
- <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->C:> </TT
-><B
-CLASS="COMMAND"
->ppm install <module>.ppd</B
->
- </TT
->
- </P
-><P
-> You can find ActiveState ppm modules at
- <A
-HREF="http://www.activestate.com/PPMPackages/5.6plus/"
-TARGET="_top"
-> http://www.activestate.com/PPMPackages/5.6plus</A
->
- </P
-></LI
-><LI
-><P
-> Download and install the Windows GNU tools from
- <A
-HREF="http://www.cygwin.com/"
-TARGET="_top"
->www.cygwin.com</A
->.
- Make sure the GNU utilities are in your $PATH.
- </P
-></LI
-><LI
-><P
-> Install MySQL for NT.
- <DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
-><P
-><B
->Note: </B
-> Your configuration file for MySQL <EM
->must</EM
-> be named C:\MY.CNF.
- </P
-></BLOCKQUOTE
-></DIV
->
- </P
-></LI
-><LI
-><P
-> Setup MySQL
- </P
-><OL
-CLASS="SUBSTEPS"
-TYPE="a"
-><LI
-><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->C:> </TT
->
- <B
-CLASS="COMMAND"
->C:\mysql\bin\mysql -u root mysql</B
->
- </TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->mysql></TT
->
- <B
-CLASS="COMMAND"
->DELETE FROM user WHERE Host='localhost' AND User='';</B
->
- </TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->mysql></TT
->
- <B
-CLASS="COMMAND"
->UPDATE user SET Password=PASSWORD ('new_password')
- WHERE user='root';</B
->
- </TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->mysql></TT
->
- <B
-CLASS="COMMAND"
->GRANT SELECT, INSERT, UPDATE, DELETE,
- INDEX, ALTER, CREATE, DROP, REFERENCES
- ON bugs.* to bugs@localhost
- IDENTIFIED BY 'bugs_password';</B
->
- </TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->mysql></TT
->
- <B
-CLASS="COMMAND"
->FLUSH PRIVILEGES;</B
->
- </TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->mysql></TT
->
- <B
-CLASS="COMMAND"
->create database bugs;</B
->
- </TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->mysql></TT
->
- <B
-CLASS="COMMAND"
->exit</B
->
- </TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="COMPUTEROUTPUT"
-> <TT
-CLASS="PROMPT"
->C:></TT
->
- <B
-CLASS="COMMAND"
->C:\mysql\bin\mysqladmin -u root -p reload</B
->
- </TT
->
- </P
-></LI
-></OL
-></LI
-><LI
-><P
-> Configure Bugzilla. For Win32, this involves editing "defparams.pl"
- and "localconfig" to taste. Running "checksetup.pl" should create
- localconfig for you. Note that getgrnam() doesn't work, and should be
- deleted. Change this line:
- "my $webservergid = getgrnam($my_webservergroup); "
- to
- "my $webservergid = $my_webservergroup; "
- </P
-></LI
-><LI
-><DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
-><P
-><B
->Note: </B
-> There are several alternatives to Sendmail that will work on Win32.
- The one mentioned here is a <EM
->suggestion</EM
->, not
- a requirement. Some other mail packages that can work include
- <A
-HREF="http://www.blat.net/"
-TARGET="_top"
->BLAT</A
->,
- <A
-HREF="http://www.geocel.com/windmail/"
-TARGET="_top"
->Windmail</A
->,
- <A
-HREF="http://www.dynamicstate.com/"
-TARGET="_top"
->Mercury Sendmail</A
->,
- and the CPAN Net::SMTP Perl module (available in .ppm).
- Every option requires some hacking of the Perl scripts for Bugzilla
- to make it work. The option here simply requires the least.
- </P
-></BLOCKQUOTE
-></DIV
-><P
-> Download NTsendmail, available from<A
-HREF="http://www.ntsendmail.com/"
-TARGET="_top"
-> www.ntsendmail.com</A
->. In order for it to work, you must set up some
- new environment variables (detailed on the ntsendmail home page). Figuring
- out where to put those variables is left as an exercise for the reader.
- You must have a "real" mail server which allows you to relay off it
- in your $ENV{"NTsendmail"} (which you should probably place in globals.pl)
- </P
-><P
-> Once downloaded and installed, modify all open(SENDMAIL) calls to open
- "| c:\ntsendmail\ntsendmail -t" instead of "|/usr/lib/sendmail -t".
- </P
-><DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
-><P
-><B
->Note: </B
-> We need someone to test this and make sure this works as advertised.
- </P
-></BLOCKQUOTE
-></DIV
-></LI
-><LI
-><P
-> Modify globals.pl and CGI.pl to remove the word "encrypt".
- </P
-><DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
-><P
-><B
->Note: </B
-> I'm not sure this is all that is involved to remove crypt. Any
- NT Bugzilla hackers want to pipe up?
- </P
-></BLOCKQUOTE
-></DIV
-></LI
-><LI
-><P
-> Change all references to "processmail" to "processmail.pl" in
- all files, and rename "processmail" to "processmail.pl"
- </P
-><DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
-><P
-><B
->Note: </B
-> I really think this may be a change we want to make for
- main-tree Bugzilla. It's painless for the UNIX folks,
- and will make the Win32 people happier.
- </P
-></BLOCKQUOTE
-></DIV
-></LI
-><LI
-><P
-> 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.pl" utility to speed part of this procedure,
- available in the "Patches and Utilities" section of The Bugzilla Guide.
- </P
-></LI
-><LI
-><P
-> In processmail.pl, add "binmode(HANDLE)" before all read() calls.
- This may not be necessary, but in some cases the read() under
- Win32 doesn't count the EOL's without using a binary read().
- </P
-></LI
-></OL
-></DIV
-></DIV
-><DIV
-CLASS="SECTION"
-><H2
-CLASS="SECTION"
-><A
-NAME="ADDLWINTIPS"
->2.2.2. Additional Windows Tips</A
-></H2
-><DIV
-CLASS="TIP"
-><BLOCKQUOTE
-CLASS="TIP"
-><P
-><B
->Tip: </B
-> From Andrew Pearson:
- <A
-NAME="AEN624"
-></A
-><BLOCKQUOTE
-CLASS="BLOCKQUOTE"
-><P
-> "You can make Bugzilla work with Personal Web Server for
- Windows 98 and higher, as well as for IIS 4.0. Microsoft has
- information available at
- <A
-HREF=" http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP"
-TARGET="_top"
-> http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP</A
->
- </P
-><P
-> Basically you need to add two String Keys in the
- registry at the following location:
- </P
-><P
-> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\ScriptMap
- </P
-><P
-> The keys should be called ".pl" and ".cgi", and both
- should have a value something like:
- <B
-CLASS="COMMAND"
->c:/perl/bin/perl.exe "%s" "%s"</B
->
- </P
-><P
-> The KB article only talks about .pl, but it goes into
- more detail and provides a perl test script.
- </P
-></BLOCKQUOTE
->
- </P
-></BLOCKQUOTE
-></DIV
-><DIV
-CLASS="TIP"
-><BLOCKQUOTE
-CLASS="TIP"
-><P
-><B
->Tip: </B
->"Brian" had this to add, about upgrading to Bugzilla 2.12 from previous versions:</P
-><A
-NAME="AEN634"
-></A
-><BLOCKQUOTE
-CLASS="BLOCKQUOTE"
-><P
-> Hi - I am updating bugzilla to 2.12 so I can tell you what I did (after I
- deleted the current dir and copied the files in).
- </P
-><P
-> In checksetup.pl, I did the following...
- </P
-><DIV
-CLASS="PROCEDURE"
-><OL
-TYPE="1"
-><LI
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><PRE
-CLASS="PROGRAMLISTING"
->my $webservergid = getgrnam($my_webservergroup);
- </PRE
-></TD
-></TR
-></TABLE
-><P
->to</P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><PRE
-CLASS="PROGRAMLISTING"
->my $webservergid = 'Administrators'
- </PRE
-></TD
-></TR
-></TABLE
-></LI
-><LI
-><P
-> I then ran checksetup.pl
- </P
-></LI
-><LI
-><P
-> I removed all the encrypt()
- <DIV
-CLASS="EXAMPLE"
-><A
-NAME="AEN646"
-></A
-><P
-><B
->Example 2-1. Removing encrypt() for Windows NT installations</B
-></P
-><P
-> Replace this:
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><PRE
-CLASS="PROGRAMLISTING"
->SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " .
- SqlQuote(substr($realcryptpwd, 0, 2)) . ")");
-my $enteredcryptpwd = FetchOneColumn();
- </PRE
-></TD
-></TR
-></TABLE
->
- with this:
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><PRE
-CLASS="PROGRAMLISTING"
->my $enteredcryptpwd = $enteredpwd
- </PRE
-></TD
-></TR
-></TABLE
->
- in cgi.pl.
- </P
-></DIV
->
- </P
-></LI
-><LI
-><P
-> I renamed processmail to processmail.pl
- </P
-></LI
-><LI
-><P
-> I altered the sendmail statements to windmail:
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><PRE
-CLASS="PROGRAMLISTING"
->
-open SENDMAIL, "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t > mail.log";
- </PRE
-></TD
-></TR
-></TABLE
->
- </P
-><P
-> The quotes around the dir is for the spaces. mail.log is for the output
- </P
-></LI
-></OL
-></DIV
-></BLOCKQUOTE
-></BLOCKQUOTE
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="readme.unix.html"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="administration.html"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->UNIX Installation</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="installation.html"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Administering Bugzilla</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
diff --git a/docs/html/rewrite.html b/docs/html/rewrite.html
new file mode 100644
index 000000000..053474069
--- /dev/null
+++ b/docs/html/rewrite.html
@@ -0,0 +1,191 @@
+<HTML
+><HEAD
+><TITLE
+>Apache mod_rewrite magic</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide"
+HREF="index.html"><LINK
+REL="UP"
+TITLE="Useful Patches and Utilities for Bugzilla"
+HREF="patches.html"><LINK
+REL="PREVIOUS"
+TITLE="Useful Patches and Utilities for Bugzilla"
+HREF="patches.html"><LINK
+REL="NEXT"
+TITLE="The setperl.csh Utility"
+HREF="setperl.html"></HEAD
+><BODY
+CLASS="SECTION"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>The Bugzilla Guide</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="patches.html"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Appendix D. Useful Patches and Utilities for Bugzilla</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="setperl.html"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="SECTION"
+><H1
+CLASS="SECTION"
+><A
+NAME="REWRITE"
+>D.1. Apache <TT
+CLASS="FILENAME"
+>mod_rewrite</TT
+> magic</A
+></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
+><P
+></P
+><OL
+TYPE="1"
+><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="90%"
+><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
+>There are many, many more things you can do with
+ mod_rewrite. As time goes on, I will include many more in
+ the Guide. For now, though, please refer to the mod_rewrite
+ documentation at <A
+HREF="http://www.apache.org"
+TARGET="_top"
+>http://www.apache.org</A
+></P
+></LI
+></OL
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="patches.html"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="setperl.html"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Useful Patches and Utilities for Bugzilla</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="patches.html"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>The setperl.csh Utility</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file
diff --git a/docs/html/rhbugzilla.html b/docs/html/rhbugzilla.html
index 1d78c6473..c0412cced 100644
--- a/docs/html/rhbugzilla.html
+++ b/docs/html/rhbugzilla.html
@@ -4,20 +4,20 @@
>Red Hat Bugzilla</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
-TITLE="Bugzilla Variants"
+TITLE="Bugzilla Variants and Competitors"
HREF="variants.html"><LINK
REL="PREVIOUS"
-TITLE="Bugzilla Variants"
+TITLE="Bugzilla Variants and Competitors"
HREF="variants.html"><LINK
REL="NEXT"
-TITLE="Useful Patches and Utilities for Bugzilla"
-HREF="patches.html"></HEAD
+TITLE="Loki Bugzilla (Fenris)"
+HREF="variant_fenris.html"></HEAD
><BODY
CLASS="SECTION"
BGCOLOR="#FFFFFF"
@@ -51,13 +51,13 @@ HREF="variants.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
->Chapter 7. Bugzilla Variants</TD
+>Chapter 7. Bugzilla Variants and Competitors</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
-HREF="patches.html"
+HREF="variant_fenris.html"
>Next</A
></TD
></TR
@@ -74,65 +74,20 @@ NAME="RHBUGZILLA"
>7.1. Red Hat Bugzilla</A
></H1
><P
-> Red Hat Bugzilla is probably the most popular Bugzilla variant, aside from Mozilla Bugzilla,
- on the planet.
- One of the major benefits of Red Hat Bugzilla is the ability to work with Oracle as a
- database, as well as MySQL.
- Here's what Dave Lawrence had to say about the status of Red Hat Bugzilla,
- <A
-NAME="AEN1913"
-></A
-><BLOCKQUOTE
-CLASS="BLOCKQUOTE"
-><P
-CLASS="LITERALLAYOUT"
-> Hello. I apologize that I am getting back to you so late. It has been difficult to keep<br>
-up with email this past week. I have checked out your updated documentation and I will<br>
-have to say very good work. A few notes and additions as follows.<br>
-<br>
-(ed: from the FAQ)<br>
->For the record, we are not using any template type implementation for the cosmetic changes <br>
->maded to Bugzilla. It is just alot of html changes in the code itself. I admit I may have <br>
->gotten a little carried away with it but the corporate types asked for a more standardized <br>
->interface to match up with other projects relating to Red Hat web sites. A lot of other web <br>
->based internal tools I am working on also look like Bugzilla. <br>
-<br>
-<br>
-This should probably be changed since we are now in fact using Text::Template for most<br>
-of the html rendering. You actually state this later in your numbered list.<br>
-<br>
-Also number 6 contradicts number 8 where number 6 would be the most up to date status<br>
-on the Oracle port.<br>
-<br>
-Additional Information:<br>
------------------------------<br>
-1. Comments are now stored in varchar fields of 4k in size each. If the comment is more<br>
-than 4k it is broken up into chunks and given a sort number so each comment can be re<br>
-assembled in the correct order. This was done because originally I was storing the comments<br>
-in a long datatype which unfortunately cannot be indexed or joined with another table. This<br>
-cause the search of text within the long description to be disabled for a long time. That<br>
-is now working and is nto showing any noticeble performance hit that I can tell. <br>
-<br>
-2. Work is being started on internationalizing the Bugzilla source we have to allow our<br>
-Japanese customers to enter bug reports into a single bugzilla system. This will probably<br>
-be done by using the nvarchar data types supported by Oracle which allows storage of<br>
-double byte characters and also the use of the Accept-Language in the http header for <br>
-detection by Bugilla of which language to render.<br>
-<br>
-3. Of course even more cosmetic changes. It is difficult to keep up with the ever <br>
-changing faces of www.redhat.com.<br>
-<br>
-4. Some convenience enhancements in the administration utilities. And more integration<br>
-with other internal/external Red Hat web sites.<br>
-<br>
-I hope this information may prove helpful for your documentation. Please contact<br>
-me if you have any more question or I can do anything else.<br>
-<br>
-Regards<br>
- </P
-></BLOCKQUOTE
->
+> Red Hat Bugzilla is probably the most popular Bugzilla variant
+ on the planet. One of the major benefits of Red Hat Bugzilla is
+ the ability to work with Oracle, MySQL, and PostGreSQL databases
+ serving as the back-end, instead of just MySQL. Dave Lawrence
+ has worked very hard to keep Red Hat Bugzilla up-to-date, and
+ many people prefer the snappier-looking page layout of Red Hat
+ Bugzilla to the default Mozilla-standard formatting.
</P
+><P
+>URL: <A
+HREF="http://bugzilla.redhat.com/bugzilla/"
+TARGET="_top"
+>http://bugzilla.redhat.com/bugzilla/</A
+></P
></DIV
><DIV
CLASS="NAVFOOTER"
@@ -165,7 +120,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
-HREF="patches.html"
+HREF="variant_fenris.html"
>Next</A
></TD
></TR
@@ -174,7 +129,7 @@ HREF="patches.html"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
->Bugzilla Variants</TD
+>Bugzilla Variants and Competitors</TD
><TD
WIDTH="34%"
ALIGN="center"
@@ -187,7 +142,7 @@ HREF="variants.html"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
->Useful Patches and Utilities for Bugzilla</TD
+>Loki Bugzilla (Fenris)</TD
></TR
></TABLE
></DIV
diff --git a/docs/html/scm.html b/docs/html/scm.html
index 87dd195f1..c96598b81 100644
--- a/docs/html/scm.html
+++ b/docs/html/scm.html
@@ -4,7 +4,7 @@
>Perforce SCM</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
@@ -16,7 +16,7 @@ REL="PREVIOUS"
TITLE="CVS"
HREF="cvs.html"><LINK
REL="NEXT"
-TITLE="Tinderbox"
+TITLE="Tinderbox/Tinderbox2"
HREF="tinderbox.html"></HEAD
><BODY
CLASS="SECTION"
@@ -74,37 +74,28 @@ NAME="SCM"
>5.3. Perforce SCM</A
></H1
><P
-> Richard Brooksby created a Perforce integration tool for Bugzilla and TeamTrack.
- You can find the main project page at
- <A
+> 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
->. "p4dti" is now an officially
- supported product from Perforce, and you can find the "Perforce Public Depot"
- p4dti page at <A
+> 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
+> http://public.perforce.com/public/perforce/p4dti/index.html</A
>.
</P
><P
-> Integration of Perforce with Bugzilla, once patches are applied, is fairly seamless. However,
- p4dti is a patch against the Bugzilla 2.10 release, not the current 2.12 release. I anticipate
- patches for 2.12 will be out shortly. Check the project page regularly for updates, or
- take the given patches and patch it manually. p4dti is designed to support multiple defect
- trackers, and maintains its own documentation for it. Please consult the pages linked
- above for further information.
- </P
-><P
-> Right now, there is no way to synchronize the Bug ID and the Perforce Transaction Number, or
- to change the Bug ID to read (PRODUCT).bugID unless you hack it in. Additionally, if you
- have synchronization problems, the easiest way to avoid them is to only put the bug
- information, comments, etc. into Bugzilla, and not into the Perforce change records.
- They will link anyway; merely reference the bug ID fixed in your change description,
- and put a comment into Bugzilla
- giving the change ID that fixed the Bugzilla bug. It's a process issue, not a technology
- question.
+> 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
@@ -160,7 +151,7 @@ HREF="integration.html"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
->Tinderbox</TD
+>Tinderbox/Tinderbox2</TD
></TR
></TABLE
></DIV
diff --git a/docs/html/searching.html b/docs/html/searching.html
deleted file mode 100644
index 39cfe2793..000000000
--- a/docs/html/searching.html
+++ /dev/null
@@ -1,197 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Better Searching</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="The Future of Bugzilla"
-HREF="future.html"><LINK
-REL="PREVIOUS"
-TITLE="Reducing Spam"
-HREF="spamlite.html"><LINK
-REL="NEXT"
-TITLE="Description Flags and Tracking Bugs"
-HREF="trackingbugs.html"></HEAD
-><BODY
-CLASS="SECTION"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="spamlite.html"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 6. The Future of Bugzilla</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="trackingbugs.html"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="SECTION"
-><H1
-CLASS="SECTION"
-><A
-NAME="SEARCHING"
->6.2. Better Searching</A
-></H1
-><P
-><P
-CLASS="LITERALLAYOUT"
->Current searching tools in Bugzilla include the querying mechanism,<br>
-special summary reports and dependency trees. This message is about new<br>
-facilities.<br>
-<br>
-1. General Summary Reports<br>
-<br>
-For some time now it has been apparent to me that the query bug list<br>
-leaves a little to be desired in its linear nature. There is a need to<br>
-have categorised subsets, and counts of each category. If you don't<br>
-believe me, how about these facilities already in place or which people<br>
-have asked for:<br>
-<br>
-Most Doomed Reports - Categorised On Assignee, Shows and Counts Number<br>
-of Bugs For Each Assignee<br>
-Bug #15806 (Most Voted For Bugs) - Categorised On Product, Shows Bugs<br>
-Voters Most Want Fixed<br>
-Bug #9789 (BugAThon Tracking Page) - Categorised On Developer (Subset),<br>
-Counts Number of Bugs<br>
-Bug #9409 and #9411 - The desire to be able to report on more subsets.<br>
-<br>
-Hopefully you can see the gist of what is desired here. It's a general<br>
-reporting mechanism.<br>
-<br>
-This mechanism lets you choose the subset of bugs to operate on (like<br>
-query), let's you categorise them, possibly along with subcategories and<br>
-counts the number of bugs within each category. It might or might not<br>
-show the actual bugs themselves, and it might limit the number of bugs<br>
-within a category, or categories to report on.<br>
-<br>
-I'm further sure that many applications of this mechanism would only be<br>
-recognised once it was implemented.<br>
-<br>
-The general summary reports bug is at<br>
-"http://bugzilla.mozilla.org/show_bug.cgi?id=12282".<br>
-<br>
-2. Related Bugs<br>
-<br>
-It would be nice to have a field where you could enter other bugs<br>
-related to the current bug - it would be handy for navigation and<br>
-possibly even finding duplicates. See<br>
-"http://bugzilla.mozilla.org/show_bug.cgi?id=12286".<br>
-<br>
-3. Column Specification Support<br>
-<br>
-Currently query seems to get what columns to report on from whatever the<br>
-user last used. This doesn't work well for "prepackaged queries", where<br>
-you followed a link. You can probably add a column by specifying a sort<br>
-column, but this is difficult and suboptimal.<br>
-<br>
-Furthermore, I find that when I want to add a column to a query, it's<br>
-usually a one off and I would prefer it to go away for the next query. <br>
-Hence, it would be nice to specify the columns that appear on the query<br>
-(and general summary report) pages. The default query mechanism should<br>
-be able to let you specify your default columns.<br>
-<br>
-This proposal lives at<br>
-"http://bugzilla.mozilla.org/show_bug.cgi?id=12284".</P
-></P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="spamlite.html"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="trackingbugs.html"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Reducing Spam</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="future.html"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Description Flags and Tracking Bugs</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
diff --git a/docs/html/security.html b/docs/html/security.html
index 220559a72..45140609d 100644
--- a/docs/html/security.html
+++ b/docs/html/security.html
@@ -4,7 +4,7 @@
>Bugzilla Security</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
@@ -13,11 +13,12 @@ REL="UP"
TITLE="Administering Bugzilla"
HREF="administration.html"><LINK
REL="PREVIOUS"
-TITLE="Product, Component, Milestone, and Version Administration"
+TITLE="Product, Component, Milestone, and Version
+ Administration"
HREF="programadmin.html"><LINK
REL="NEXT"
-TITLE="Using Bugzilla"
-HREF="using.html"></HEAD
+TITLE="Integrating Bugzilla with Third-Party Tools"
+HREF="integration.html"></HEAD
><BODY
CLASS="SECTION"
BGCOLOR="#FFFFFF"
@@ -51,13 +52,13 @@ HREF="programadmin.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
->Chapter 3. Administering Bugzilla</TD
+>Chapter 4. Administering Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
-HREF="using.html"
+HREF="integration.html"
>Next</A
></TD
></TR
@@ -71,7 +72,7 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="SECURITY"
->3.4. Bugzilla Security</A
+>4.4. Bugzilla Security</A
></H1
><TABLE
BORDER="0"
@@ -90,8 +91,9 @@ VALIGN="TOP"
><I
><P
><I
->Putting your money in a wall safe is better protection than depending on the fact that
- no one knows that you hide your money in a mayonnaise jar in your fridge.</I
+>Putting your money in a wall safe is better protection than
+ depending on the fact that no one knows that you hide your
+ money in a mayonnaise jar in your fridge.</I
></P
></I
></TD
@@ -99,36 +101,70 @@ VALIGN="TOP"
></TABLE
><DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><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
-><B
->Note: </B
-> Poorly-configured MySQL, Bugzilla, and FTP installations have given attackers full
- access to systems in the past. Please take these guidelines seriously, even
- for Bugzilla machines hidden away behind your firewall. 80% of all computer
+> Poorly-configured MySQL, Bugzilla, and FTP installations have
+ given attackers full access to systems in the past. Please
+ take these guidelines seriously, even for Bugzilla machines
+ hidden away behind your firewall. 80% of all computer
trespassers are insiders, not anonymous crackers.
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
><P
-> First thing's first: Secure your installation.
+> Secure your installation.
<DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><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
-><B
->Note: </B
-> 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
+> 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"
TARGET="_top"
>mozilla-webtools@mozilla.org</A
>
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
>
<P
@@ -137,99 +173,196 @@ TARGET="_top"
TYPE="1"
><LI
><P
-> Ensure you are running at least MysQL version 3.22.32 or newer. Earlier versions had
- notable security holes and poorly secured default configuration choices.
+> Ensure you are running at least MysQL version 3.22.32 or
+ newer. Earlier versions had notable security holes and
+ poorly secured default configuration choices.
</P
></LI
><LI
><P
><EM
->There is no substitute for understanding the tools on your system!</EM
->
- Read <A
+>There is no substitute for understanding the
+ tools on your system!</EM
+> Read <A
HREF="http://www.mysql.com/documentation/mysql/bychapter/manual_Privilege_system.html"
TARGET="_top"
-> The MySQL Privelege System</A
+> The MySQL Privilege System</A
> until you can recite it from memory!</P
><P
-> At the very least, ensure you password the "mysql -u root" account and the "bugs" account, establish grant
- table rights (consult the Keystone guide in Appendix C: The Bugzilla Database for some easy-to-use details)
- that do not allow CREATE, DROP, RELOAD, SHUTDOWN, and PROCESS for user "bugs". I wrote up the Keystone
- advice back when I knew far less about security than I do now : )
+> At the very least, ensure you password the "mysql -u root"
+ account and the "bugs" account, establish grant table
+ rights (consult the Keystone guide in Appendix C: The
+ Bugzilla Database for some easy-to-use details) that do
+ not allow CREATE, DROP, RELOAD, SHUTDOWN, and PROCESS for
+ user "bugs". I wrote up the Keystone advice back when I
+ knew far less about security than I do now : )
</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
+> 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
></LI
><LI
><P
->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.</P
+> Do not run Apache as <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
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="90%"
+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
+> <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
+></TD
+></TR
+></TABLE
+></DIV
+>
+ </P
></LI
><LI
><P
-> Ensure you have adequate access controls for the $BUGZILLA_HOME/data/ and
- $BUGZILLA_HOME/shadow/ directories, as well as the $BUGZILLA_HOME/localconfig file.
- The localconfig file stores your "bugs" user password,
- which would be terrible to have in the hands
- of a criminal. Also some files under $BUGZILLA_HOME/data/ store sensitive information, and
- $BUGZILLA_HOME/shadow/ stores bug information for faster retrieval. If you fail to secure
- these directories and this file, you will expose bug information to those who may not
- be allowed to see it.
+> Ensure you have adequate access controls for the
+ $BUGZILLA_HOME/data/ and $BUGZILLA_HOME/shadow/
+ directories, as well as the $BUGZILLA_HOME/localconfig and
+ $BUGZILLA_HOME/globals.pl files. The localconfig file
+ stores your "bugs" user password, which would be terrible
+ to have in the hands of a criminal, while the "globals.pl"
+ stores some default information regarding your
+ installation which could aid a system cracker. In
+ addition, some files under $BUGZILLA_HOME/data/ store
+ sensitive information, and $BUGZILLA_HOME/shadow/ stores
+ bug information for faster retrieval. If you fail to
+ secure these directories and this file, you will expose
+ bug information to those who may not be allowed to see it.
</P
+><DIV
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="90%"
+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 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"
+TARGET="_top"
+> http://bugzilla.mozilla.org/localconfig</A
+>). 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
+></TD
+></TR
+></TABLE
+></DIV
><P
-> On Apache, you can use .htaccess files to protect access to these directories, as outlined
- in <A
+> 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
+> for the localconfig file, and <A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=65572"
TARGET="_top"
-> Bug 65572</A
+> Bug 65572</A
> for adequate protection in your data/ and shadow/ directories.
</P
><P
-> Note the instructions which follow are Apache-specific. If you use IIS, Netscape, or other
- non-Apache web servers, please consult your system documentation for how to secure these
- files from being transmitted to curious users.
+> 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
+> 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><br>
- allow from all<br>
- </Files><br>
- deny from all<br>
- </P
+> <Files comments> allow<br>
+ from all </Files> deny from all </P
>
</P
><P
-> Place the following text into a file named ".htaccess", readable by your web server,
- in your $BUGZILLA_HOME/ directory.
- <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><br>
- deny from all<br>
- </Files><br>
- allow from all<br>
- </P
+> <Files localconfig> deny<br>
+ from all </Files> allow from all </P
>
</P
><P
-> Place the following text into a file named ".htaccess", readable by your web server,
- in your $BUGZILLA_HOME/shadow directory.
- <P
+> Place the following text into a file named ".htaccess",
+ readable by your web server, in your $BUGZILLA_HOME/shadow
+ directory. <P
CLASS="LITERALLAYOUT"
-> deny from all<br>
- </P
+> deny from all </P
>
</P
></LI
@@ -268,7 +401,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
-HREF="using.html"
+HREF="integration.html"
>Next</A
></TD
></TR
@@ -277,7 +410,8 @@ HREF="using.html"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
->Product, Component, Milestone, and Version Administration</TD
+>Product, Component, Milestone, and Version
+ Administration</TD
><TD
WIDTH="34%"
ALIGN="center"
@@ -290,7 +424,7 @@ HREF="administration.html"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
->Using Bugzilla</TD
+>Integrating Bugzilla with Third-Party Tools</TD
></TR
></TABLE
></DIV
diff --git a/docs/html/setperl.html b/docs/html/setperl.html
index 376d87a1a..1d5384be2 100644
--- a/docs/html/setperl.html
+++ b/docs/html/setperl.html
@@ -4,7 +4,7 @@
>The setperl.csh Utility</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
@@ -13,8 +13,8 @@ REL="UP"
TITLE="Useful Patches and Utilities for Bugzilla"
HREF="patches.html"><LINK
REL="PREVIOUS"
-TITLE="Useful Patches and Utilities for Bugzilla"
-HREF="patches.html"><LINK
+TITLE="Apache mod_rewrite magic"
+HREF="rewrite.html"><LINK
REL="NEXT"
TITLE="Command-line Bugzilla Queries"
HREF="cmdline.html"></HEAD
@@ -44,7 +44,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
-HREF="patches.html"
+HREF="rewrite.html"
>Prev</A
></TD
><TD
@@ -71,14 +71,13 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="SETPERL"
->D.1. The setperl.csh Utility</A
+>D.2. The setperl.csh Utility</A
></H1
><P
->
- You can use the "setperl.csh" utility to quickly and easily
- change the path to perl on all your Bugzilla files.
- This is a C-shell script; if you do not have "csh" or "tcsh" in the search
- path on your system, it will not work!
+> You can use the "setperl.csh" utility to quickly and
+ easily change the path to perl on all your Bugzilla files. This
+ is a C-shell script; if you do not have "csh" or "tcsh" in the
+ search path on your system, it will not work!
</P
><DIV
CLASS="PROCEDURE"
@@ -112,15 +111,15 @@ CLASS="COMMAND"
><P
> <TT
CLASS="COMPUTEROUTPUT"
-> <TT
+> <TT
CLASS="PROMPT"
>bash#</TT
->
- <B
+> <B
CLASS="COMMAND"
->wget -O setperl.csh 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'</B
->
- </TT
+>wget -O
+ setperl.csh
+ 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'</B
+> </TT
>
</P
></LI
@@ -128,15 +127,14 @@ CLASS="COMMAND"
><P
> <TT
CLASS="COMPUTEROUTPUT"
-> <TT
+> <TT
CLASS="PROMPT"
>bash#</TT
->
- <B
+> <B
CLASS="COMMAND"
->chmod u+x setperl.csh</B
->
- </TT
+>chmod
+ u+x setperl.csh</B
+> </TT
>
</P
></LI
@@ -169,15 +167,14 @@ CLASS="COMMAND"
><P
> <TT
CLASS="COMPUTEROUTPUT"
-> <TT
+> <TT
CLASS="PROMPT"
>bash#</TT
->
- <B
+> <B
CLASS="COMMAND"
->chmod u+x duplicates.cgi</B
->
- </TT
+>chmod
+ u+x duplicates.cgi</B
+> </TT
>
</P
></LI
@@ -206,7 +203,7 @@ CLASS="COMMAND"
><P
> <TT
CLASS="COMPUTEROUTPUT"
-> <TT
+> <TT
CLASS="PROMPT"
>bash#</TT
>
@@ -219,7 +216,7 @@ CLASS="COMMAND"
<DIV
CLASS="EXAMPLE"
><A
-NAME="AEN1963"
+NAME="AEN2439"
></A
><P
><B
@@ -228,11 +225,11 @@ NAME="AEN1963"
><P
> <TT
CLASS="COMPUTEROUTPUT"
-> <TT
+> <TT
CLASS="PROMPT"
>bash#</TT
>
- <B
+ <B
CLASS="COMMAND"
>./setperl.csh /usr/bin/perl</B
>
@@ -261,7 +258,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
-HREF="patches.html"
+HREF="rewrite.html"
>Prev</A
></TD
><TD
@@ -286,7 +283,10 @@ HREF="cmdline.html"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
->Useful Patches and Utilities for Bugzilla</TD
+>Apache <TT
+CLASS="FILENAME"
+>mod_rewrite</TT
+> magic</TD
><TD
WIDTH="34%"
ALIGN="center"
diff --git a/docs/html/spamlite.html b/docs/html/spamlite.html
deleted file mode 100644
index b5701aa8f..000000000
--- a/docs/html/spamlite.html
+++ /dev/null
@@ -1,189 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Reducing Spam</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="The Future of Bugzilla"
-HREF="future.html"><LINK
-REL="PREVIOUS"
-TITLE="The Future of Bugzilla"
-HREF="future.html"><LINK
-REL="NEXT"
-TITLE="Better Searching"
-HREF="searching.html"></HEAD
-><BODY
-CLASS="SECTION"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="future.html"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 6. The Future of Bugzilla</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="searching.html"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="SECTION"
-><H1
-CLASS="SECTION"
-><A
-NAME="SPAMLITE"
->6.1. Reducing Spam</A
-></H1
-><P
-><P
-CLASS="LITERALLAYOUT"
->Those who use Bugzilla frequently are probably used to notification spam<br>
-- unwanted or unnecessary notifications. A number of proposals have<br>
-been put forward to attempt to reduce this.<br>
-<br>
-1. Reduce CC Spam<br>
-<br>
-Some of you probably know me as that guy who CCs on heaps and heaps of<br>
-bugs. Just as you get a lot of CC changes from me, so do I get a lot<br>
-from others. Why should CC changes send out email notifications?<br>
-<br>
-It's not necessarily the best idea to just remove the CC spam, there are<br>
-other issues too, like the difficulty of adding to large CC fields.<br>
-<br>
-For these reasons and more, an RFE for a per user "BCC" facility exists<br>
-that people could use to silently and privately track bugs, in a similar<br>
-way to voting today, but applying to an unlimited number of bugs. See<br>
-"http://bugzilla.mozilla.org/show_bug.cgi?id=7345".<br>
-<br>
-2. Bulk Changes<br>
-<br>
-You know the drill - a large milestone change, a component movement,<br>
-whatever, and lots of notifications are generated. If there's enough<br>
-maybe you'll just go delete, delete, delete, whoops, there goes another<br>
-notification that wasn't from the bulk change you missed.<br>
-<br>
-Shouldn't bulk changes send out one notification? A proposal for this<br>
-is at "http://bugzilla.mozilla.org/show_bug.cgi?id=26943".<br>
-<br>
-3. Configurable Notification Criteria<br>
-<br>
-It would be good if you could choose what you want to receive. There<br>
-are two parts to this.<br>
-<br>
-(a) Choose a selection of bugs you're interested in. This would be<br>
-similar to CC except you let the set be computed from selection criteria<br>
-rather than limited to the bugs your name is on. There is currently a<br>
-limited version of this in the bugzilla preferences, ie "all qualifying<br>
-bugs"/"all qualifying bugs except the ones I change"/"only those bugs<br>
-which I am listed on the cc line".<br>
-(b) Choose what changes will trigger a notification for the bugs you are<br>
-watching. With this, you could choose whether you want to receive cc,<br>
-dependency and keyword changes, for example.<br>
-<br>
-Both of these proposals live at<br>
-"http://bugzilla.mozilla.org/show_bug.cgi?id=14137".<br>
-Note that they also live at<br>
-"http://bugzilla.mozilla.org/show_bug.cgi?id=17464", and the change <br>
-has been checked in. This is fixed with Bugzilla 2.12 and is no longer<br>
-an issue. Woo-Hoo!</P
-></P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="future.html"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="searching.html"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->The Future of Bugzilla</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="future.html"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Better Searching</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
diff --git a/docs/html/stepbystep.html b/docs/html/stepbystep.html
new file mode 100644
index 000000000..b6e8e223a
--- /dev/null
+++ b/docs/html/stepbystep.html
@@ -0,0 +1,2339 @@
+<HTML
+><HEAD
+><TITLE
+>Step-by-step Install</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide"
+HREF="index.html"><LINK
+REL="UP"
+TITLE="Installation"
+HREF="installation.html"><LINK
+REL="PREVIOUS"
+TITLE="ERRATA"
+HREF="errata.html"><LINK
+REL="NEXT"
+TITLE="Mac OS X Installation Notes"
+HREF="osx.html"></HEAD
+><BODY
+CLASS="SECTION"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>The Bugzilla Guide</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="errata.html"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Chapter 3. Installation</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="osx.html"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="SECTION"
+><H1
+CLASS="SECTION"
+><A
+NAME="STEPBYSTEP"
+>3.2. Step-by-step Install</A
+></H1
+><DIV
+CLASS="SECTION"
+><H2
+CLASS="SECTION"
+><A
+NAME="AEN509"
+>3.2.1. Introduction</A
+></H2
+><P
+> Installation of bugzilla is pretty straightforward, particularly if your
+ machine already has MySQL and the MySQL-related perl packages installed.
+ If those aren't installed yet, then that's the first order of business. The
+ other necessary ingredient is a web server set up to run cgi scripts.
+ While using Apache for your webserver is not required, it is recommended.
+ </P
+><P
+> Bugzilla has been successfully installed under Solaris, Linux,
+ and Win32. The peculiarities of installing on Win32 (Microsoft
+ Windows) are not included in this section of the Guide; please
+ check out the <A
+HREF="win32.html"
+>Win32 Installation Notes</A
+> for further advice
+ on getting Bugzilla to work on Microsoft Windows.
+ </P
+><P
+> The Bugzilla Guide is contained in the "docs/" folder in your
+ Bugzilla distribution. It is available in plain text
+ (docs/txt), HTML (docs/html), or SGML source (docs/sgml).
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><H2
+CLASS="SECTION"
+><A
+NAME="AEN515"
+>3.2.2. Installing the Prerequisites</A
+></H2
+><DIV
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>If you want to skip these manual installation steps for
+ the CPAN dependencies listed below, and are running the very
+ most recent version of Perl and MySQL (both the executables
+ and development libraries) on your system, check out
+ Bundle::Bugzilla in <A
+HREF="stepbystep.html#BUNDLEBUGZILLA"
+>Using Bundle::Bugzilla instead of manually installing Perl modules</A
+></P
+></TD
+></TR
+></TABLE
+></DIV
+><P
+> The software packages necessary for the proper running of bugzilla are:
+ <P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+> MySQL database server and the mysql client (3.22.5 or greater)
+ </P
+></LI
+><LI
+><P
+> Perl (5.004 or greater, 5.6.1 is recommended if you wish
+ to use Bundle::Bugzilla)
+ </P
+></LI
+><LI
+><P
+> DBI Perl module
+ </P
+></LI
+><LI
+><P
+> Data::Dumper Perl module
+ </P
+></LI
+><LI
+><P
+> Bundle::Mysql Perl module collection
+ </P
+></LI
+><LI
+><P
+> TimeDate Perl module collection
+ </P
+></LI
+><LI
+><P
+> GD perl module (1.8.3) (optional, for bug charting)
+ </P
+></LI
+><LI
+><P
+> Chart::Base Perl module (0.99c) (optional, for bug charting)
+ </P
+></LI
+><LI
+><P
+> DB_File Perl module (optional, for bug charting)
+ </P
+></LI
+><LI
+><P
+> The web server of your choice. Apache is recommended.
+ </P
+></LI
+><LI
+><P
+> MIME::Parser Perl module (optional, for contrib/bug_email.pl interface)
+ </P
+></LI
+></OL
+>
+
+ <DIV
+CLASS="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
+> It is a good idea, while installing Bugzilla, to ensure it
+ is not <EM
+>accessible</EM
+> by other machines
+ on the Internet. Your machine may be vulnerable to attacks
+ while you are installing. In other words, ensure there is
+ some kind of firewall between you and the rest of the
+ Internet. Many installation steps require an active
+ Internet connection to complete, but you must take care to
+ ensure that at no point is your machine vulnerable to an
+ attack.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+>
+ <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
+>Linux-Mandrake 8.0, the author's test system, includes
+ every required and optional library for Bugzilla. The
+ easiest way to install them is by using the
+ <TT
+CLASS="FILENAME"
+>urpmi</TT
+> utility. If you follow these
+ commands, you should have everything you need for
+ Bugzilla, and <TT
+CLASS="FILENAME"
+>checksetup.pl</TT
+> should
+ not complain about any missing libraries. You may already
+ have some of these installed.</P
+><P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+><TT
+CLASS="PROMPT"
+>bash#</TT
+><B
+CLASS="COMMAND"
+> urpmi
+ perl-mysql</B
+></TD
+></TR
+><TR
+><TD
+><TT
+CLASS="PROMPT"
+>bash#</TT
+><B
+CLASS="COMMAND"
+> urpmi
+ perl-chart</B
+></TD
+></TR
+><TR
+><TD
+><TT
+CLASS="PROMPT"
+>bash#</TT
+><B
+CLASS="COMMAND"
+> urpmi
+ perl-gd</B
+></TD
+></TR
+><TR
+><TD
+><TT
+CLASS="PROMPT"
+>bash#</TT
+><B
+CLASS="COMMAND"
+> urpmi
+ perl-MailTools</B
+> (for Bugzilla email
+ integration)</TD
+></TR
+><TR
+><TD
+><TT
+CLASS="PROMPT"
+>bash#</TT
+><B
+CLASS="COMMAND"
+> urpmi
+ apache-modules</B
+></TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+></TD
+></TR
+></TABLE
+></DIV
+>
+
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><H2
+CLASS="SECTION"
+><A
+NAME="INSTALL-MYSQL"
+>3.2.3. Installing MySQL Database</A
+></H2
+><P
+> Visit MySQL homepage at <A
+HREF="http://www.mysql.com"
+TARGET="_top"
+>www.mysql.com</A
+> and grab the latest stable release of the server. Many of the binary versions of MySQL store their data files in <TT
+CLASS="FILENAME"
+>/var</TT
+> which is often part of a smaller root partition. If you decide to build from sources you can easily set the dataDir as an option to <TT
+CLASS="FILENAME"
+>configure</TT
+>.
+ </P
+><P
+> If you install from source or non-package (RPM, deb, etc.)
+ binaries you need to add
+ <I
+CLASS="FIRSTTERM"
+>mysqld</I
+> to your
+ init scripts so the server daemon will come back up whenever
+ your machine reboots. Further discussion of UNIX init
+ sequences are beyond the scope of this guide.
+ <DIV
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>You should have your init script start
+ <I
+CLASS="GLOSSTERM"
+>mysqld</I
+> with the ability to accept
+ large packets. By default, <TT
+CLASS="FILENAME"
+>mysqld</TT
+>
+ only accepts packets up to 64K long. This limits the size
+ of attachments you may put on bugs. If you add <TT
+CLASS="OPTION"
+>-O
+ max_allowed_packet=1M</TT
+> to the command that starts
+ <TT
+CLASS="FILENAME"
+>mysqld</TT
+> (or
+ <TT
+CLASS="FILENAME"
+>safe_mysqld</TT
+>), then you will be able
+ to have attachments up to about 1 megabyte.</P
+></TD
+></TR
+></TABLE
+></DIV
+>
+
+ </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 plan on running Bugzilla and MySQL on the same
+ machine, consider using the <TT
+CLASS="OPTION"
+>--skip-networking</TT
+>
+ option in the init script. This enhances security by
+ preventing network access to MySQL.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
+><DIV
+CLASS="SECTION"
+><H2
+CLASS="SECTION"
+><A
+NAME="INSTALL-PERL"
+>3.2.4. Perl (5.004 or greater)</A
+></H2
+><P
+> Any machine that doesn't have perl on it is a sad machine
+ indeed. Perl for *nix systems can be gotten in source form
+ from http://www.perl.com. Although Bugzilla runs with most
+ post-5.004 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.
+ </P
+><P
+> Perl is now a far cry from the the single compiler/interpreter
+ binary it once was. It includes a great many required modules
+ and quite a few other support files. If you're not up to or
+ not inclined to build perl from source, you'll want to install
+ it on your machine using some sort of packaging system (be it
+ RPM, deb, or what have you) to ensure a sane install. In the
+ subsequent sections you'll be installing quite a few perl
+ modules; this can be quite ornery if your perl installation
+ isn't up to snuff.
+ </P
+><DIV
+CLASS="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
+>Many people complain that Perl modules will not install
+ for them. Most times, the error messages complain that they
+ are missing a file in <SPAN
+CLASS="QUOTE"
+>"@INC"</SPAN
+>. Virtually every
+ time, this is due to permissions being set too restrictively
+ for you to compile Perl modules or not having the necessary
+ Perl development libraries installed on your system..
+ Consult your local UNIX systems administrator for help
+ solving these permissions issues; if you
+ <EM
+>are</EM
+> the local UNIX sysadmin, please
+ consult the newsgroup/mailing list for further assistance or
+ hire someone to help you out.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+><DIV
+CLASS="TIP"
+><A
+NAME="BUNDLEBUGZILLA"
+></A
+><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
+> You can skip the following Perl module installation steps by
+ installing <SPAN
+CLASS="PRODUCTNAME"
+>Bundle::Bugzilla</SPAN
+> from
+ <A
+HREF="glossary.html#GLOSS_CPAN"
+><I
+CLASS="GLOSSTERM"
+>CPAN</I
+></A
+>, which
+ includes them. All Perl module installation steps require
+ you have an active Internet connection. If you wish to use
+ Bundle::Bugzilla, however, you must be using the latest
+ version of Perl (at this writing, version 5.6.1)
+ </P
+><P
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>bash#</TT
+> <B
+CLASS="COMMAND"
+>perl -MCPAN
+ -e 'install "Bundle::Bugzilla"'</B
+>
+ </TT
+>
+ </P
+><P
+> Bundle::Bugzilla doesn't include GD, Chart::Base, or
+ MIME::Parser, which are not essential to a basic Bugzilla
+ install. If installing this bundle fails, you should
+ install each module individually to isolate the problem.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
+><DIV
+CLASS="SECTION"
+><H2
+CLASS="SECTION"
+><A
+NAME="AEN602"
+>3.2.5. DBI Perl Module</A
+></H2
+><P
+> The DBI module is a generic Perl module used by other database related
+ Perl modules. For our purposes it's required by the MySQL-related
+ modules. As long as your Perl installation was done correctly the
+ DBI module should be a breeze. It's a mixed Perl/C module, but Perl's
+ MakeMaker system simplifies the C compilation greatly.
+ </P
+><P
+> Like almost all Perl modules DBI can be found on the Comprehensive Perl
+ Archive Network (CPAN) at http://www.cpan.org. The CPAN servers have a
+ real tendency to bog down, so please use mirrors. The current location
+ at the time of this writing can be found in <A
+HREF="downloadlinks.html"
+>Appendix B</A
+>.
+ </P
+><P
+> Quality, general Perl module installation instructions can be found on
+ the CPAN website, but the easy thing to do is to just use the CPAN shell
+ which does all the hard work for you.
+ </P
+><P
+> To use the CPAN shell to install DBI:
+ <DIV
+CLASS="INFORMALEXAMPLE"
+><A
+NAME="AEN609"
+></A
+><P
+></P
+><P
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>bash#</TT
+>
+ <B
+CLASS="COMMAND"
+>perl -MCPAN -e 'install "DBI"'</B
+>
+ </TT
+>
+ <DIV
+CLASS="NOTE"
+><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
+>Replace "DBI" with the name of whichever module you wish
+ to install, such as Data::Dumper, TimeDate, GD, etc.</P
+></TD
+></TR
+></TABLE
+></DIV
+>
+ </P
+><P
+></P
+></DIV
+>
+ To do it the hard way:
+ <DIV
+CLASS="INFORMALEXAMPLE"
+><A
+NAME="AEN616"
+></A
+><P
+></P
+><P
+> Untar the module tarball -- it should create its own directory
+ </P
+><P
+> CD to the directory just created, and enter the following commands:
+ <P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>bash#</TT
+>
+ <B
+CLASS="COMMAND"
+>perl Makefile.PL</B
+>
+ </TT
+>
+ </P
+></LI
+><LI
+><P
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>bash#</TT
+>
+ <B
+CLASS="COMMAND"
+>make</B
+>
+ </TT
+>
+ </P
+></LI
+><LI
+><P
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>bash#</TT
+>
+ <B
+CLASS="COMMAND"
+>make test</B
+>
+ </TT
+>
+ </P
+></LI
+><LI
+><P
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>bash#</TT
+>
+ <B
+CLASS="COMMAND"
+>make install</B
+>
+ </TT
+>
+ </P
+></LI
+></OL
+>
+ If everything went ok that should be all it takes. For the vast
+ majority of perl modules this is all that's required.
+ </P
+><P
+></P
+></DIV
+>
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><H2
+CLASS="SECTION"
+><A
+NAME="AEN640"
+>3.2.6. Data::Dumper Perl Module</A
+></H2
+><P
+> The Data::Dumper module provides data structure persistence for Perl
+ (similar to Java's serialization). It comes with later sub-releases of
+ Perl 5.004, but a re-installation just to be sure it's available won't
+ hurt anything.
+ </P
+><P
+> Data::Dumper is used by the MySQL-related Perl modules. It
+ can be found on CPAN (see <A
+HREF="downloadlinks.html"
+>Appendix B</A
+>) and
+ can be
+ installed by following the same four step make sequence used
+ for the DBI module.
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><H2
+CLASS="SECTION"
+><A
+NAME="AEN645"
+>3.2.7. MySQL related Perl Module Collection</A
+></H2
+><P
+> The Perl/MySQL interface requires a few mutually-dependent perl
+ modules. These modules are grouped together into the the
+ Msql-Mysql-modules package. This package can be found at CPAN.
+ After the archive file has been downloaded it should
+ be untarred.
+ </P
+><P
+> The MySQL modules are all built using one make file which is generated
+ by running:
+ <TT
+CLASS="PROMPT"
+>bash#</TT
+>
+ <B
+CLASS="COMMAND"
+>perl Makefile.pl</B
+>
+ </P
+><P
+> The MakeMaker process will ask you a few questions about the desired
+ compilation target and your MySQL installation. For many of the questions
+ the provided default will be adequate.
+ </P
+><P
+> When asked if your desired target is the MySQL or mSQL packages,
+ 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.
+ </P
+><P
+> A host of 'localhost' should be fine and a testing user of 'test' and
+ a null password should find itself with sufficient access to run tests
+ on the 'test' database which MySQL created upon installation. If 'make
+ test' and 'make install' go through without errors you should be ready
+ to go as far as database connectivity is concerned.
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><H2
+CLASS="SECTION"
+><A
+NAME="AEN654"
+>3.2.8. TimeDate Perl Module Collection</A
+></H2
+><P
+> Many of the more common date/time/calendar related Perl
+ modules have been grouped into a bundle similar to the MySQL
+ modules bundle. This bundle is stored on the CPAN under the
+ name TimeDate (see link: <A
+HREF="downloadlinks.html"
+>Appendix B</A
+>). The
+ component module we're most interested in is the Date::Format
+ module, but installing all of them is probably a good idea
+ anyway. The standard Perl module installation instructions
+ should work perfectly for this simple package.
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><H2
+CLASS="SECTION"
+><A
+NAME="AEN658"
+>3.2.9. GD Perl Module (1.8.3)</A
+></H2
+><P
+> The GD library was written by Thomas Boutell a long while
+ ago to programatically generate images in C. Since then it's
+ become the defacto standard for programatic image
+ construction. The Perl bindings to it found in the GD library
+ are used on millions of web pages to generate graphs on the
+ fly. That's what bugzilla will be using it for so you must
+ install it if you want any of the graphing to work.
+ </P
+><P
+> Actually bugzilla uses the Graph module which relies on GD
+ itself. Isn't that always the way with object-oriented
+ programming? At any rate, you can find the GD library on CPAN
+ in <A
+HREF="downloadlinks.html"
+>Appendix B</A
+>.
+ </P
+><DIV
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> The Perl GD library requires some other libraries that may
+ or may not be installed on your system, including
+ <TT
+CLASS="CLASSNAME"
+>libpng</TT
+> and
+ <TT
+CLASS="CLASSNAME"
+>libgd</TT
+>. The full requirements are
+ listed in the Perl GD library README. Just realize that if
+ compiling GD fails, it's probably because you're missing a
+ required library.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
+><DIV
+CLASS="SECTION"
+><H2
+CLASS="SECTION"
+><A
+NAME="AEN667"
+>3.2.10. Chart::Base Perl Module (0.99c)</A
+></H2
+><P
+> The Chart module provides bugzilla with on-the-fly charting
+ abilities. It can be installed in the usual fashion after it
+ has been fetched from CPAN where it is found as the
+ Chart-x.x... tarball, linked in <A
+HREF="downloadlinks.html"
+>Appendix B</A
+>. Note that
+ as with the GD perl module, only the version listed above, or
+ newer, will work. Earlier versions used GIF's, which are no
+ longer supported by the latest versions of GD.
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><H2
+CLASS="SECTION"
+><A
+NAME="AEN671"
+>3.2.11. DB_File Perl Module</A
+></H2
+><P
+> DB_File is a module which allows Perl programs to make use
+ of the facilities provided by Berkeley DB version 1.x. This
+ module is required by collectstats.pl which is used for bug
+ charting. If you plan to make use of bug charting, you must
+ install this module.
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><H2
+CLASS="SECTION"
+><A
+NAME="AEN674"
+>3.2.12. HTTP Server</A
+></H2
+><P
+> You have a freedom of choice here - Apache, Netscape or any
+ other server on UNIX would do. You can easily run the web
+ server on a different machine than MySQL, but need to adjust
+ the MySQL <SPAN
+CLASS="QUOTE"
+>"bugs"</SPAN
+> user permissions accordingly.
+ <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
+>I strongly recommend Apache as the web server to use.
+ The Bugzilla Guide installation instructions, in general,
+ assume you are using Apache. As more users use different
+ webservers and send me information on the peculiarities of
+ installing using their favorite webserver, I will provide
+ notes for them.</P
+></TD
+></TR
+></TABLE
+></DIV
+>
+ </P
+><P
+> You'll want to make sure that your web server will run any
+ file with the .cgi extension as a cgi and not just display it.
+ If you're using apache that means uncommenting the following
+ line in the srm.conf file:
+ <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>AddHandler cgi-script .cgi
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+ </P
+><P
+> With apache you'll also want to make sure that within the
+ access.conf file the line:
+ <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>Options ExecCGI</PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+ is in the stanza that covers the directories into which
+ you intend to put the bugzilla .html and .cgi files.
+ </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
+> Users of newer versions of Apache will generally find both
+ of the above lines will be in the httpd.conf file, rather
+ than srm.conf or access.conf.
+ </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
+> There are important files and directories that should not
+ be a served by the HTTP server. These are most files in the
+ <SPAN
+CLASS="QUOTE"
+>"data"</SPAN
+> and <SPAN
+CLASS="QUOTE"
+>"shadow"</SPAN
+> directories
+ and the <SPAN
+CLASS="QUOTE"
+>"localconfig"</SPAN
+> file. You should
+ configure your HTTP server to not serve content from these
+ files. Failure to do so will expose critical passwords and
+ other data. Please see <A
+HREF="geninstall.html#HTACCESS"
+>.htaccess files and security</A
+> for details
+ on how to do this for Apache. I appreciate notes on how to
+ get this same functionality using other webservers.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
+><DIV
+CLASS="SECTION"
+><H2
+CLASS="SECTION"
+><A
+NAME="AEN692"
+>3.2.13. Installing the Bugzilla Files</A
+></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 <SPAN
+CLASS="QUOTE"
+>"nobody"</SPAN
+>). You may decide to put the
+ files off of the main web space for your web server or perhaps
+ off of <TT
+CLASS="FILENAME"
+>/usr/local</TT
+> with a symbolic link in
+ the web space that points to the Bugzilla directory. At any
+ rate, just dump all the files in the same place, and make sure
+ you can access the files in that directory through your web
+ server.
+ </P
+><DIV
+CLASS="TIP"
+><P
+></P
+><TABLE
+CLASS="TIP"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/tip.gif"
+HSPACE="5"
+ALT="Tip"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> If you symlink the bugzilla directory into your Apache's
+ HTML heirarchy, you may receive
+ <SPAN
+CLASS="ERRORNAME"
+>Forbidden</SPAN
+> errors unless you add the
+ <SPAN
+CLASS="QUOTE"
+>"FollowSymLinks"</SPAN
+> directive to the
+ <Directory> entry for the HTML root.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+><P
+> Once all the files are in a web accessible directory, make
+ that directory writable by your webserver's user. This is a
+ temporary step until you run the post-install
+ <TT
+CLASS="FILENAME"
+>checksetup.pl</TT
+> script, which locks down your
+ installation.
+ </P
+><P
+> Lastly, you'll need to set up a symbolic link to
+ <TT
+CLASS="FILENAME"
+>/usr/bonsaitools/bin/perl</TT
+> for the correct
+ location of your perl executable (probably
+ <TT
+CLASS="FILENAME"
+>/usr/bin/perl</TT
+>). Otherwise you must hack
+ all the .cgi files to change where they look for perl, or use
+ <A
+HREF="setperl.html"
+>The setperl.csh Utility</A
+>, found in
+ <A
+HREF="patches.html"
+>Useful Patches and Utilities for Bugzilla</A
+>. I suggest using the symlink
+ approach for future release compatability.
+ <DIV
+CLASS="EXAMPLE"
+><A
+NAME="AEN708"
+></A
+><P
+><B
+>Example 3-1. Setting up bonsaitools symlink</B
+></P
+><P
+> Here's how you set up the Perl symlink on Linux to make
+ Bugzilla work. Your mileage may vary. For some UNIX
+ operating systems, you probably need to subsitute
+ <SPAN
+CLASS="QUOTE"
+>"/usr/local/bin/perl"</SPAN
+> for
+ <SPAN
+CLASS="QUOTE"
+>"/usr/bin/perl"</SPAN
+> below; if on certain other
+ UNIX systems, Perl may live in weird places like
+ <SPAN
+CLASS="QUOTE"
+>"/opt/perl"</SPAN
+>. As root, run these commands:
+ <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>bash# mkdir /usr/bonsaitools
+bash# mkdir /usr/bonsaitools/bin
+bash# ln -s /usr/bin/perl /usr/bosaitools/bin/perl
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+ </P
+><P
+> Alternately, you can simply run this perl one-liner to
+ change your path to perl in all the files in your Bugzilla
+ installation:
+ <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>perl -pi -e 's@#!/usr/bonsaitools/bin/perl@#!/usr/bin/perl@' *cgi *pl Bug.pm
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+ Change the second path to perl to match your installation.
+ </P
+></DIV
+>
+ <DIV
+CLASS="TIP"
+><P
+></P
+><TABLE
+CLASS="TIP"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/tip.gif"
+HSPACE="5"
+ALT="Tip"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> If you don't have root access to set this symlink up,
+ check out the
+ <A
+HREF="setperl.html"
+>The setperl.csh Utility</A
+>, listed in <A
+HREF="patches.html"
+>Useful Patches and Utilities for Bugzilla</A
+>. It will change the path to perl in all your Bugzilla files for you.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+>
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><H2
+CLASS="SECTION"
+><A
+NAME="AEN721"
+>3.2.14. Setting Up the MySQL Database</A
+></H2
+><P
+> After you've gotten all the software installed and working you're ready
+ to start preparing the database for its life as a the back end to a high
+ quality bug tracker.
+ </P
+><P
+> First, you'll want to fix MySQL permissions to allow access
+ from Bugzilla. For the purpose of this Installation section,
+ the Bugzilla username will be <SPAN
+CLASS="QUOTE"
+>"bugs"</SPAN
+>, and will
+ have minimal permissions.
+
+ <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
+> Bugzilla has not undergone a thorough security audit. It
+ may be possible for a system cracker to somehow trick
+ Bugzilla into executing a command such as <B
+CLASS="COMMAND"
+>DROP
+ DATABASE mysql</B
+>.
+ </P
+><P
+>That would be bad.</P
+></TD
+></TR
+></TABLE
+></DIV
+>
+ </P
+><P
+> Give the MySQL root user a password. MySQL passwords are
+ limited to 16 characters.
+ <P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>bash#</TT
+> <B
+CLASS="COMMAND"
+>mysql
+ -u root mysql</B
+> </TT
+>
+ </TD
+></TR
+><TR
+><TD
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>mysql></TT
+> <B
+CLASS="COMMAND"
+> UPDATE user SET Password=PASSWORD ('new_password')
+ WHERE user='root'; </B
+> </TT
+>
+ </TD
+></TR
+><TR
+><TD
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>mysql></TT
+> <B
+CLASS="COMMAND"
+>FLUSH
+ PRIVILEGES;</B
+> </TT
+>
+ </TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+> From this point on, if you need to access
+ MySQL as the MySQL root user, you will need to use
+ <B
+CLASS="COMMAND"
+>mysql -u root -p</B
+> and enter your
+ new_password. Remember that MySQL user names have nothing to
+ do with Unix user names (login names).
+ </P
+><P
+> Next, we create the <SPAN
+CLASS="QUOTE"
+>"bugs"</SPAN
+> user, and grant
+ sufficient permissions for checksetup.pl, which we'll use
+ later, to work its magic. This also restricts the
+ <SPAN
+CLASS="QUOTE"
+>"bugs"</SPAN
+> user to operations within a database
+ called <SPAN
+CLASS="QUOTE"
+>"bugs"</SPAN
+>, and only allows the account to
+ connect from <SPAN
+CLASS="QUOTE"
+>"localhost"</SPAN
+>. Modify it to reflect
+ your setup if you will be connecting from another machine or
+ as a different user.
+ </P
+><P
+> Remember to set bugs_password to some unique password.
+ <P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>mysql></TT
+>
+ <B
+CLASS="COMMAND"
+>GRANT SELECT,INSERT,UPDATE,DELETE,INDEX,
+ ALTER,CREATE,DROP,REFERENCES
+ ON bugs.* TO bugs@localhost
+ IDENTIFIED BY 'bugs_password';</B
+>
+ </TT
+>
+ </TD
+></TR
+><TR
+><TD
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+> mysql>
+ </TT
+>
+ <B
+CLASS="COMMAND"
+> FLUSH PRIVILEGES;
+ </B
+>
+ </TT
+>
+ </TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+>
+ </P
+><P
+> Next, run the magic checksetup.pl script. (Many thanks to
+ Holger Schurig <holgerschurig@nikocity.de> for writing
+ this script!) It will make sure Bugzilla files and directories
+ have reasonable permissions, set up the
+ <TT
+CLASS="FILENAME"
+>data</TT
+> directory, and create all the MySQL
+ tables.
+ <P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>bash#</TT
+>
+ <B
+CLASS="COMMAND"
+>./checksetup.pl</B
+> </TT
+>
+ </TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+> The first time you run it, it will create a
+ file called <TT
+CLASS="FILENAME"
+>localconfig</TT
+>.
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><H2
+CLASS="SECTION"
+><A
+NAME="AEN768"
+>3.2.15. Tweaking <TT
+CLASS="FILENAME"
+>localconfig</TT
+></A
+></H2
+><P
+> This file contains a variety of settings you may need to tweak including
+ how Bugzilla should connect to the MySQL database.
+ </P
+><P
+> The connection settings include:
+ <P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+> server's host: just use <SPAN
+CLASS="QUOTE"
+>"localhost"</SPAN
+> if the
+ MySQL server is local
+ </P
+></LI
+><LI
+><P
+> database name: <SPAN
+CLASS="QUOTE"
+>"bugs"</SPAN
+> if you're following
+ these directions
+ </P
+></LI
+><LI
+><P
+> MySQL username: <SPAN
+CLASS="QUOTE"
+>"bugs"</SPAN
+> if you're following
+ these directions
+ </P
+></LI
+><LI
+><P
+> Password for the <SPAN
+CLASS="QUOTE"
+>"bugs"</SPAN
+> MySQL account above
+ </P
+></LI
+></OL
+>
+ </P
+><P
+> You should also install .htaccess files that the Apache
+ webserver will use to restrict access to Bugzilla data files.
+ See <A
+HREF="geninstall.html#HTACCESS"
+>.htaccess files and security</A
+>.
+ </P
+><P
+> Once you are happy with the settings, re-run
+ <TT
+CLASS="FILENAME"
+>checksetup.pl</TT
+>. On this second run, it will
+ create the database and an administrator account for which
+ you will be prompted to provide information.
+ </P
+><P
+> When logged into an administrator account once Bugzilla is
+ running, if you go to the query page (off of the Bugzilla main
+ menu), you'll find an <SPAN
+CLASS="QUOTE"
+>"edit parameters"</SPAN
+> option
+ that is filled with editable treats.
+ </P
+><P
+> Should everything work, you will have a nearly empty Bugzilla
+ database and a newly-created <TT
+CLASS="FILENAME"
+>localconfig</TT
+>
+ file in your Bugzilla root directory.
+ </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
+> The second time you run checksetup.pl, you should become
+ the user your web server runs as, and that you ensure that
+ you set the <SPAN
+CLASS="QUOTE"
+>"webservergroup"</SPAN
+> parameter in localconfig to
+ match the web server's group name, if any. I believe,
+ for the next release of Bugzilla, this will be fixed so
+ that Bugzilla supports a <SPAN
+CLASS="QUOTE"
+>"webserveruser"</SPAN
+> parameter in
+ localconfig as well.
+ <DIV
+CLASS="EXAMPLE"
+><A
+NAME="AEN799"
+></A
+><P
+><B
+>Example 3-2. Running checksetup.pl as the web user</B
+></P
+><P
+> Assuming your web server runs as user "apache", and
+ Bugzilla is installed in "/usr/local/bugzilla", here's
+ one way to run checksetup.pl as the web server user.
+ As root, for the <EM
+>second run</EM
+> of
+ checksetup.pl, do this:
+ <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>
+bash# chown -R apache:apache /usr/local/bugzilla
+bash# su - apache
+bash# cd /usr/local/bugzilla
+bash# ./checksetup.pl
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+ </P
+></DIV
+>
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+>
+ </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
+> The checksetup.pl script is designed so that you can run
+ it at any time without causing harm. You should run it
+ after any upgrade to Bugzilla.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
+><DIV
+CLASS="SECTION"
+><H2
+CLASS="SECTION"
+><A
+NAME="AEN806"
+>3.2.16. Setting Up Maintainers Manually (Optional)</A
+></H2
+><P
+> If you want to add someone else to every group by hand, you
+ can do it by typing the appropriate MySQL commands. Run
+ <B
+CLASS="COMMAND"
+> mysql -u root -p bugs</B
+> You
+ may need different parameters, depending on your security
+ settings. Then:
+ <P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>mysql></TT
+> <B
+CLASS="COMMAND"
+>update
+ profiles set groupset=0x7fffffffffffffff where
+ login_name = 'XXX';</B
+> </TT
+> (yes, that's <EM
+>fifteen</EM
+><SPAN
+CLASS="QUOTE"
+>"f"</SPAN
+>'s.
+ </TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+> replacing XXX with the Bugzilla email address.
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><H2
+CLASS="SECTION"
+><A
+NAME="AEN817"
+>3.2.17. The Whining Cron (Optional)</A
+></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 can set up bugzilla's automatic whining
+ system. This can be done by adding the following command as a
+ daily crontab entry (for help on that see that crontab man
+ page):
+ <P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <B
+CLASS="COMMAND"
+>cd
+ <your-bugzilla-directory> ;
+ ./whineatnews.pl</B
+> </TT
+>
+ </TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+>
+ </P
+><DIV
+CLASS="TIP"
+><P
+></P
+><TABLE
+CLASS="TIP"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/tip.gif"
+HSPACE="5"
+ALT="Tip"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> Depending on your system, crontab may have several manpages.
+ The following command should lead you to the most useful
+ page for this purpose:
+ <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+> man 5 crontab
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
+><DIV
+CLASS="SECTION"
+><H2
+CLASS="SECTION"
+><A
+NAME="AEN827"
+>3.2.18. Bug Graphs (Optional)</A
+></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
+><P
+> Add a cron entry like this to run collectstats daily at 5
+ after midnight:
+ <P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>bash#</TT
+> <B
+CLASS="COMMAND"
+>crontab
+ -e</B
+> </TT
+>
+ </TD
+></TR
+><TR
+><TD
+> <TT
+CLASS="COMPUTEROUTPUT"
+> 5 0 * * * cd
+ <your-bugzilla-directory> ; ./collectstats.pl
+ </TT
+>
+ </TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+>
+ </P
+><P
+> After two days have passed you'll be able to view bug graphs
+ from the Bug Reports page.
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><H2
+CLASS="SECTION"
+><A
+NAME="AEN839"
+>3.2.19. Securing MySQL</A
+></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
+> Use .htaccess files with the Apache webserver to secure your
+ bugzilla install. See <A
+HREF="geninstall.html#HTACCESS"
+>.htaccess files and security</A
+>
+ </P
+><P
+> Consider also:
+ <P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+> Turning off external networking with "--skip-networking",
+ unless you have "mit-pthreads", in which case you can't.
+ Without networking, MySQL connects with a Unix domain socket.
+ </P
+></LI
+><LI
+><P
+> using the --user= option to mysqld to run it as an unprivileged
+ user.
+ </P
+></LI
+><LI
+><P
+> starting MySQL in a chroot jail
+ </P
+></LI
+><LI
+><P
+> running the httpd in a "chrooted" jail
+ </P
+></LI
+><LI
+><P
+> making sure the MySQL passwords are different from the OS
+ passwords (MySQL "root" has nothing to do with system "root").
+ </P
+></LI
+><LI
+><P
+> running MySQL on a separate untrusted machine
+ </P
+></LI
+><LI
+><P
+> making backups ;-)
+ </P
+></LI
+></OL
+>
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="errata.html"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="osx.html"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>ERRATA</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="installation.html"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Mac OS X Installation Notes</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
diff --git a/docs/html/tinderbox.html b/docs/html/tinderbox.html
index 6ed10c5fb..239548421 100644
--- a/docs/html/tinderbox.html
+++ b/docs/html/tinderbox.html
@@ -1,10 +1,10 @@
<HTML
><HEAD
><TITLE
->Tinderbox</TITLE
+>Tinderbox/Tinderbox2</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
@@ -71,10 +71,10 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="TINDERBOX"
->5.4. Tinderbox</A
+>5.4. Tinderbox/Tinderbox2</A
></H1
><P
->We need Tinderbox integration information</P
+>We need Tinderbox integration information.</P
></DIV
><DIV
CLASS="NAVFOOTER"
diff --git a/docs/html/trackingbugs.html b/docs/html/trackingbugs.html
deleted file mode 100644
index 4083db800..000000000
--- a/docs/html/trackingbugs.html
+++ /dev/null
@@ -1,193 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Description Flags and Tracking Bugs</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="The Future of Bugzilla"
-HREF="future.html"><LINK
-REL="PREVIOUS"
-TITLE="Better Searching"
-HREF="searching.html"><LINK
-REL="NEXT"
-TITLE="Bug Issues"
-HREF="bugprobs.html"></HEAD
-><BODY
-CLASS="SECTION"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="searching.html"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 6. The Future of Bugzilla</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="bugprobs.html"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="SECTION"
-><H1
-CLASS="SECTION"
-><A
-NAME="TRACKINGBUGS"
->6.3. Description Flags and Tracking Bugs</A
-></H1
-><P
-><P
-CLASS="LITERALLAYOUT"
->Since I last posted on this issue, we now have "keywords" that solve<br>
-many of the issues of description and status whiteboard keywords. We<br>
-have seen a migration towards keywords, but there is still further to<br>
-go.<br>
-<br>
-Description ( + Status Whiteboard ) Keywords<br>
---------------------------------------------<br>
-<br>
-Some description keywords remain. I'd like to hear what reasons, other<br>
-than time, there are for these staying as they are. I'm suspecting many<br>
-are not really being used. Hopefully we can totally remove these<br>
-eventually.<br>
-<br>
-Tracking Bugs<br>
--------------<br>
-<br>
-When I suggested keywords, I did so to get rid of tracking bugs too,<br>
-though we've had less success on that front.<br>
-<br>
-There are many disadvantages to tracking bugs.<br>
-<br>
-- They can pollute bugs counts, and you must make sure you exclude<br>
-them. I believe the meta keyword might be used for this purpose.<br>
-- They have an assignee but there is nothing to fix, and that person can<br>
-get whined at by Bugzilla.<br>
-- It would be better to craft your own "dependency tree" rather than<br>
-rely on a fixed hierachy in the bug system.<br>
-- In creating a nice little hierachy, many bugs duplicate information<br>
-that should be available in other ways, eg<br>
-"http://bugzilla.mozilla.org/show_bug.cgi?id=12833" which is<br>
-about beta 1 networking issues. These could fall behind the actual<br>
-data. What tracking bugs are good for, ad hoc lists, is what keywords<br>
-are better for.<br>
-- An automatically generated dependency structure between one "tracking<br>
-bug" and another would be better than a manual one, since it gives exact<br>
-rather than manually set up classifications.<br>
-<br>
-Probably the only feature preventing tracking bugs being replaced is the<br>
-dependency tree. The quintessential tracking bug seems to be bug #7229<br>
-"chofmann's watch list", which probably has about a couple of hundred<br>
-bugs at various levels, which allows a nice visualisation.<br>
-<br>
-Before keywords can replace tracking bugs better visualisation is going<br>
-to be required. General summary reports and dependency forests of a bug<br>
-list ("http://bugzilla.mozilla.org/show_bug.cgi?id=12992") could both<br>
-help, but neither solves the problem totally. Perhaps keywords within<br>
-keywords would help here. In any case, I'm still thinking about this<br>
-one.<br>
-<br>
-Some tracking bugs could definitely be turned into keywords immediately<br>
-though, and I'll point the finger at<br>
-"http://bugzilla.mozilla.org/show_bug.cgi?id=7954" here since that's<br>
-what came to mind first.</P
-></P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="searching.html"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="bugprobs.html"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Better Searching</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="future.html"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Bug Issues</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
diff --git a/docs/html/translations.html b/docs/html/translations.html
index b3ca1cbd5..bc3fa8890 100644
--- a/docs/html/translations.html
+++ b/docs/html/translations.html
@@ -4,7 +4,7 @@
>Translations</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
@@ -74,17 +74,18 @@ NAME="TRANSLATIONS"
>1.8. Translations</A
></H1
><P
-> The Bugzilla Guide needs translators!
- Please volunteer your translation into the language of your choice.
- If you will translate this Guide, please notify the members of the mozilla-webtools mailing list at
+> The Bugzilla Guide needs translators! Please volunteer your
+ translation into the language of your choice. If you will
+ translate this Guide, please notify the members of the
+ mozilla-webtools mailing list at
<TT
CLASS="EMAIL"
><<A
HREF="mailto:mozilla-webtools@mozilla.org"
>mozilla-webtools@mozilla.org</A
>></TT
->. Since The Bugzilla Guide is also hosted on the
- Linux Documentation Project, you would also do well to notify
+>, and arrange with
+ Matt Barnson to check it into CVS.
</P
></DIV
><DIV
diff --git a/docs/html/useradmin.html b/docs/html/useradmin.html
index 644259a3d..a57ed8bbb 100644
--- a/docs/html/useradmin.html
+++ b/docs/html/useradmin.html
@@ -4,7 +4,7 @@
>User Administration</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
@@ -16,7 +16,8 @@ REL="PREVIOUS"
TITLE="Post-Installation Checklist"
HREF="postinstall-check.html"><LINK
REL="NEXT"
-TITLE="Product, Component, Milestone, and Version Administration"
+TITLE="Product, Component, Milestone, and Version
+ Administration"
HREF="programadmin.html"></HEAD
><BODY
CLASS="SECTION"
@@ -51,7 +52,7 @@ HREF="postinstall-check.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
->Chapter 3. Administering Bugzilla</TD
+>Chapter 4. Administering Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
@@ -71,11 +72,12 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="USERADMIN"
->3.2. User Administration</A
+>4.2. User Administration</A
></H1
><P
> User administration is one of the easiest parts of Bugzilla.
- Keeping it from getting out of hand, however, can become a challenge.
+ Keeping it from getting out of hand, however, can become a
+ challenge.
</P
><DIV
CLASS="SECTION"
@@ -83,41 +85,70 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="DEFAULTUSER"
->3.2.1. Creating the Default User</A
+>4.2.1. Creating the Default User</A
></H2
><P
-> 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 were to 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 were to delete the "super user" account, re-running
+ checksetup.pl will again prompt you for this username and
+ password.
</P
><DIV
CLASS="TIP"
-><BLOCKQUOTE
+><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
-><B
->Tip: </B
-> If you wish to add more administrative users, you must use the MySQL interface.
- Run "mysql" from the command line, and use these commands ("mysql>" denotes the
- mysql prompt, not something you should type in):
- <B
+> If you wish to add more administrative users, you must use the
+ MySQL interface. Run "mysql" from the command line, and use
+ these commands ("mysql>" denotes the mysql prompt, not
+ something you should type in):
+ <B
CLASS="COMMAND"
><TT
CLASS="PROMPT"
>mysql></TT
> use bugs;</B
>
- <B
+ <B
CLASS="COMMAND"
><TT
CLASS="PROMPT"
>mysql></TT
-> update profiles set groupset=0x7ffffffffffffff
- where login_name = "(user's login name)"; </B
+> update profiles set
+ groupset=0x7ffffffffffffff where login_name = "(user's
+ login name)"; </B
>
</P
-></BLOCKQUOTE
+><P
+>Yes, that is <EM
+>fourteen</EM
+>
+ <SPAN
+CLASS="QUOTE"
+>"f"</SPAN
+>'s. A whole lot of f-ing going on if you
+ want to create a new administator.</P
+></TD
+></TR
+></TABLE
></DIV
></DIV
><DIV
@@ -126,7 +157,7 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="MANAGEUSERS"
->3.2.2. Managing Other Users</A
+>4.2.2. Managing Other Users</A
></H2
><DIV
CLASS="SECTION"
@@ -134,7 +165,7 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="LOGIN"
->3.2.2.1. Logging In</A
+>4.2.2.1. Logging In</A
></H3
><P
></P
@@ -142,7 +173,8 @@ NAME="LOGIN"
TYPE="1"
><LI
><P
-> Open the index.html page for your Bugzilla installation in your browser window.
+> Open the index.html page for your Bugzilla installation
+ in your browser window.
</P
></LI
><LI
@@ -157,8 +189,9 @@ TYPE="1"
></LI
><LI
><P
-> Type your email address, and the password which was emailed to you when you
- created your Bugzilla account, into the spaces provided.
+> Type your email address, and the password which was
+ emailed to you when you created your Bugzilla account,
+ into the spaces provided.
</P
></LI
></OL
@@ -171,12 +204,13 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="CREATENEWUSERS"
->3.2.2.2. Creating new users</A
+>4.2.2.2. Creating new users</A
></H3
><P
-> Your users can create their own user accounts by clicking the "New Account"
- link at the bottom of each page.
- 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. However,
+ should you desire to create user accounts ahead of time,
+ here is how you do it.
</P
><P
></P
@@ -184,62 +218,109 @@ NAME="CREATENEWUSERS"
TYPE="1"
><LI
><P
-> After logging in, click the "Users" link at the footer of the query page.
+> After logging in, click the "Users" link at the footer
+ of the query page.
</P
></LI
><LI
><P
-> To see a specific user, type a portion of their login name
- in the box provided and click "submit".
- To see all users, simply click the "submit" button.
- You must click "submit" here to be able to add a new user.
+> To see a specific user, type a portion of their login
+ name in the box provided and click "submit". To see all
+ users, simply click the "submit" button. You must click
+ "submit" here to be able to add a new user.
</P
><DIV
CLASS="TIP"
-><BLOCKQUOTE
+><P
+></P
+><TABLE
CLASS="TIP"
+WIDTH="90%"
+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
-><B
->Tip: </B
-> More functionality is available via the list on the right-hand side
- of the text entry box.
- You can match what you type as a case-insensitive substring (the default)
- of all users on your system, a case-sensitive regular expression
- (please see the "man regexp" manual page for details on regular expression syntax),
- or a <EM
+> More functionality is available via the list on the
+ right-hand side of the text entry box. You can match
+ what you type as a case-insensitive substring (the
+ default) of all users on your system, a case-sensitive
+ regular expression (please see the <B
+CLASS="COMMAND"
+>man
+ regexp</B
+> manual page for details on regular
+ expression syntax), or a <EM
>reverse</EM
-> regular expression match,
- where every user name which does NOT match the regular expression
- is selected.
+>
+ regular expression match, where every user name which
+ does NOT match the regular expression is selected.
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
></LI
><LI
><P
-> Click the "Add New User" link at the bottom of the user list
+> Click the "Add New User" link at the bottom of the user
+ list
</P
></LI
><LI
><P
-> Fill out the form presented. This page is self-explanatory. When done, click "submit".
+> Fill out the form presented. This page is
+ self-explanatory. When done, click "submit".
</P
><DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><P
+></P
+><TABLE
CLASS="NOTE"
+WIDTH="90%"
+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
-><B
->Note: </B
> Adding a user this way will <EM
>not</EM
-> send an email
- informing them of their username and password.
- In general, it is preferable to log out and use the "New Account"
- button to create users, as it will pre-populate all the required fields and also notify
- the user of her account name and password.
+>
+ send an email informing them of their username and
+ password. While useful for creating dummy accounts
+ (watchers which shuttle mail to another system, for
+ instance, or email addresses which are a mailing
+ list), in general it is preferable to log out and use
+ the <SPAN
+CLASS="QUOTE"
+>"New Account"</SPAN
+> button to create users,
+ as it will pre-populate all the required fields and
+ also notify the user of her account name and
+ password.
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
></LI
></OL
@@ -250,36 +331,49 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="DISABLEUSERS"
->3.2.2.3. Disabling Users</A
+>4.2.2.3. Disabling Users</A
></H3
><P
-> I bet you noticed that big "Disabled Text" entry box available from the "Add New User" screen,
- when you edit an account?
- By entering any text in this box and selecting "submit",
- you have prevented the user from using Bugzilla via the web interface.
- Your explanation, written in this text box, will be presented to the user
- the next time she attempts to use the system.
+> I bet you noticed that big "Disabled Text" entry box
+ available from the "Add New User" screen, when you edit an
+ account? By entering any text in this box and selecting
+ "submit", you have prevented the user from using Bugzilla
+ via the web interface. Your explanation, written in this
+ text box, will be presented to the user the next time she
+ attempts to use the system.
<DIV
CLASS="WARNING"
><P
></P
><TABLE
CLASS="WARNING"
-BORDER="1"
WIDTH="100%"
+BORDER="0"
><TR
><TD
+WIDTH="25"
ALIGN="CENTER"
-><B
->Warning</B
-></TD
-></TR
-><TR
+VALIGN="TOP"
+><IMG
+SRC="../images/warning.gif"
+HSPACE="5"
+ALT="Warning"></TD
><TD
ALIGN="LEFT"
+VALIGN="TOP"
><P
-> Don't disable your own administrative account, or you will hate life!
+> Don't disable your own administrative account, or you
+ will hate life!
</P
+><P
+>At this time, <SPAN
+CLASS="QUOTE"
+>"Disabled Text"</SPAN
+> does not
+ prevent a user from using the email interface. If you
+ have the email interface enabled, they can still
+ continue to submit bugs and comments that way. We need
+ a patch to fix this.</P
></TD
></TR
></TABLE
@@ -293,10 +387,11 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="MODIFYUSERS"
->3.2.2.4. Modifying Users</A
+>4.2.2.4. Modifying Users</A
></H3
><P
-> Here I will attempt to describe the function of each option on the user edit screen.
+> Here I will attempt to describe the function of each option
+ on the Edit User screen.
</P
><P
></P
@@ -305,20 +400,38 @@ NAME="MODIFYUSERS"
><P
> <EM
>Login Name</EM
->: This is generally the user's email address.
- However, if you have edited your system parameters,
- this may just be the user's login name or some other identifier.
+>: This is generally the
+ user's email address. However, if you have edited your
+ system parameters, this may just be the user's login
+ name or some other identifier.
<DIV
CLASS="TIP"
-><BLOCKQUOTE
+><P
+></P
+><TABLE
CLASS="TIP"
+WIDTH="90%"
+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
-><B
->Tip: </B
-> For compatability reasons, you should probably
- stick with email addresses as user login names. It will make your life easier.
+> For compatability reasons, you should probably stick
+ with email addresses as user login names. It will
+ make your life easier.
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
>
</P
@@ -334,15 +447,16 @@ CLASS="TIP"
><P
> <EM
>Password</EM
->: You will only see asterisks in versions
- of Bugzilla newer than 2.10 or early 2.11. You can change the user password here.
+>: You can change the user
+ password here. It is normal to only see asterisks.
</P
></LI
><LI
><P
> <EM
>Email Notification</EM
->: You may choose from one of three options:
+>: You may choose
+ from one of three options:
<P
></P
><OL
@@ -351,24 +465,44 @@ TYPE="1"
><P
> All qualifying bugs except those which I change:
The user will be notified of any change to any bug
- for which she is the reporter, assignee, Q/A contact, CC recipient, or "watcher".
+ for which she is the reporter, assignee, QA
+ Contact, CC recipient, or "watcher".
</P
></LI
><LI
><P
> Only those bugs which I am listed on the CC line:
- The user will not be notified of changes to bugs where she is the assignee,
- reporter, or Q/A contact, but will receive them if she is on the CC list.
+ The user will not be notified of changes to bugs
+ where she is the assignee, reporter, or QA
+ Contact, but will receive them if she is on the CC
+ list.
<DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><P
+></P
+><TABLE
CLASS="NOTE"
+WIDTH="90%"
+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
-><B
->Note: </B
-> She will still receive whining cron emails if you set up the "whinemail" feature.
+> She will still receive whining cron emails if
+ you set up the "whinemail" feature.
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
>
</P
@@ -377,9 +511,11 @@ CLASS="NOTE"
><P
> <EM
>All Qualifying Bugs</EM
->: This user is a glutton for punishment.
- If her name is in the reporter, Q/A contact, CC, assignee, or is a "watcher",
- she will get email updates regarding the bug.
+>: This
+ user is a glutton for punishment. If her name is
+ in the reporter, QA Contact, CC, assignee, or is a
+ "watcher", she will get email updates regarding
+ the bug.
</P
></LI
></OL
@@ -387,27 +523,31 @@ CLASS="NOTE"
><P
> <EM
>Disable Text</EM
->: If you type anything in this box,
- including just a space, the user account is disabled from making any changes
- to bugs via the web interface, and what you type in this box is presented as the reason.
+>: If you type anything
+ in this box, including just a space, the user account is
+ disabled from making any changes to bugs via the web
+ interface, and what you type in this box is presented as
+ the reason.
<DIV
CLASS="WARNING"
><P
></P
><TABLE
CLASS="WARNING"
-BORDER="1"
WIDTH="90%"
+BORDER="0"
><TR
><TD
+WIDTH="25"
ALIGN="CENTER"
-><B
->Warning</B
-></TD
-></TR
-><TR
+VALIGN="TOP"
+><IMG
+SRC="../images/warning.gif"
+HSPACE="5"
+ALT="Warning"></TD
><TD
ALIGN="LEFT"
+VALIGN="TOP"
><P
>Don't disable the administrator account!</P
></TD
@@ -417,18 +557,36 @@ ALIGN="LEFT"
>
<DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><P
+></P
+><TABLE
CLASS="NOTE"
+WIDTH="90%"
+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
-><B
->Note: </B
-> As of this writing, the user can still submit bugs via the e-mail gateway,
- if you set it up, despite the disabled text field. The e-mail gateway should
+> As of this writing, the user can still submit bugs
+ via the e-mail gateway, if you set it up, despite
+ the disabled text field. The e-mail gateway should
<EM
>not</EM
-> be enabled for secure installations of Bugzilla.
+> be enabled for secure
+ installations of Bugzilla.
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
>
</P
@@ -437,39 +595,62 @@ CLASS="NOTE"
><P
> <EM
>CanConfirm</EM
->: This field is only used if you have enabled
- "unconfirmed" status in your parameters screen. If you enable this for a user,
- that user can then move bugs from "Unconfirmed" to "Confirmed" status (ergo: "New" status).
- Be judicious about allowing users to turn this bit on for other users.
+>: This field is only used
+ if you have enabled "unconfirmed" status in your
+ parameters screen. If you enable this for a user, that
+ user can then move bugs from "Unconfirmed" to
+ "Confirmed" status (e.g.: "New" status). Be judicious
+ about allowing users to turn this bit on for other
+ users.
</P
></LI
><LI
><P
> <EM
>Creategroups</EM
->: This option will allow a user to create and
- destroy groups in Bugzilla. Unless you are using the Bugzilla GroupSentry security
- option "usebuggroupsentry" in your parameters, this setting has no effect.
+>: This option will
+ allow a user to create and destroy groups in Bugzilla.
+ Unless you are using the Bugzilla GroupSentry security
+ option "usebuggroupsentry" in your parameters, this
+ setting has no effect.
</P
></LI
><LI
><P
> <EM
>Editbugs</EM
->: Unless a user has this bit set, they can only edit
- those bugs for which they are the assignee or the reporter.
+>: Unless a user has this
+ bit set, they can only edit those bugs for which they
+ are the assignee or the reporter.
<DIV
CLASS="NOTE"
-><BLOCKQUOTE
+><P
+></P
+><TABLE
CLASS="NOTE"
+WIDTH="90%"
+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
-><B
->Note: </B
-> Leaving this option unchecked does not prevent users from adding
- comments to a bug! They simply cannot change a bug priority, severity,
- etc. unless they are the assignee or reporter.
+> Leaving this option unchecked does not prevent users
+ from adding comments to a bug! They simply cannot
+ change a bug priority, severity, etc. unless they
+ are the assignee or reporter.
</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
>
</P
@@ -478,48 +659,58 @@ CLASS="NOTE"
><P
> <EM
>Editcomponents</EM
->: This flag allows a user to create new
- products and components, as well as modify and destroy those that have no bugs
- associated with them. If a product or component has bugs associated with it,
- those bugs must be moved to a different product or component before Bugzilla
- will allow them to be destroyed. The name of a product or component can be
- changed without affecting the associated bugs, but it tends to annoy
- the hell out of your users when these change a lot.
+>: This flag allows a
+ user to create new products and components, as well as
+ modify and destroy those that have no bugs associated
+ with them. If a product or component has bugs
+ associated with it, those bugs must be moved to a
+ different product or component before Bugzilla will
+ allow them to be destroyed. The name of a product or
+ component can be changed without affecting the
+ associated bugs, but it tends to annoy the hell out of
+ your users when these change a lot.
</P
></LI
><LI
><P
> <EM
>Editkeywords</EM
->: If you use Bugzilla's keyword functionality,
- enabling this feature allows a user can create and destroy keywords.
- As always, the keywords for existing bugs containing the keyword
- the user wishes to destroy must be changed before Bugzilla will allow it to die.
- You must be very careful about creating too many new keywords
- if you run a very large Bugzilla installation; keywords are global variables
- across products, and you can often run into a phenomenon called "keyword bloat".
- This confuses users, and then the feature goes unused.
+>: If you use Bugzilla's
+ keyword functionality, enabling this feature allows a
+ user can create and destroy keywords. As always, the
+ keywords for existing bugs containing the keyword the
+ user wishes to destroy must be changed before Bugzilla
+ will allow it to die. You must be very careful about
+ creating too many new keywords if you run a very large
+ Bugzilla installation; keywords are global variables
+ across products, and you can often run into a phenomenon
+ called "keyword bloat". This confuses users, and then
+ the feature goes unused.
</P
></LI
><LI
><P
> <EM
>Editusers</EM
->: This flag allows a user do what you're doing
- right now: edit other users.
- This will allow those with the right to do so to remove administrator
- priveleges from other users or grant them to themselves. Enable with care.
+>: This flag allows a user
+ do what you're doing right now: edit other users. This
+ will allow those with the right to do so to remove
+ administrator priveleges from other users or grant them
+ to themselves. Enable with care.
</P
></LI
><LI
><P
> <EM
>PRODUCT</EM
->: PRODUCT bugs access. This allows an administrator,
- with product-level granularity, to specify in which products a user can edit bugs.
- The user must still have the "editbugs" privelege to edit bugs in this area;
- this simply restricts them from even seeing bugs outside these boundaries if the administrator
- has enabled the group sentry parameter "usebuggroupsentry". Unless you are using bug groups,
+>: PRODUCT bugs access. This
+ allows an administrator, with product-level granularity,
+ to specify in which products a user can edit bugs. The
+ user must still have the "editbugs" privelege to edit
+ bugs in this area; this simply restricts them from even
+ seeing bugs outside these boundaries if the
+ administrator has enabled the group sentry parameter
+ "usebuggroupsentry". Unless you are using bug groups,
this option has no effect.
</P
></LI
@@ -580,7 +771,8 @@ HREF="administration.html"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
->Product, Component, Milestone, and Version Administration</TD
+>Product, Component, Milestone, and Version
+ Administration</TD
></TR
></TABLE
></DIV
diff --git a/docs/html/using.html b/docs/html/using.html
index 1d71a2219..51e333451 100644
--- a/docs/html/using.html
+++ b/docs/html/using.html
@@ -4,14 +4,14 @@
>Using Bugzilla</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="PREVIOUS"
-TITLE="Bugzilla Security"
-HREF="security.html"><LINK
+TITLE="Document Conventions"
+HREF="conventions.html"><LINK
REL="NEXT"
TITLE="What is Bugzilla?"
HREF="whatis.html"></HEAD
@@ -41,7 +41,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
-HREF="security.html"
+HREF="conventions.html"
>Prev</A
></TD
><TD
@@ -67,7 +67,7 @@ CLASS="CHAPTER"
><H1
><A
NAME="USING"
->Chapter 4. Using Bugzilla</A
+>Chapter 2. Using Bugzilla</A
></H1
><TABLE
BORDER="0"
@@ -86,7 +86,7 @@ VALIGN="TOP"
><I
><P
><I
->What, Why, How, & What's in it for me?</I
+>What, Why, How, & Where?</I
></P
></I
></TD
@@ -100,46 +100,46 @@ CLASS="TOC"
>Table of Contents</B
></DT
><DT
->4.1. <A
+>2.1. <A
HREF="whatis.html"
>What is Bugzilla?</A
></DT
><DT
->4.2. <A
+>2.2. <A
HREF="why.html"
>Why Should We Use Bugzilla?</A
></DT
><DT
->4.3. <A
+>2.3. <A
HREF="how.html"
>How do I use Bugzilla?</A
></DT
><DD
><DL
><DT
->4.3.1. <A
+>2.3.1. <A
HREF="how.html#MYACCOUNT"
>Create a Bugzilla Account</A
></DT
><DT
->4.3.2. <A
+>2.3.2. <A
HREF="how.html#QUERY"
>The Bugzilla Query Page</A
></DT
><DT
->4.3.3. <A
+>2.3.3. <A
HREF="how.html#BUGREPORTS"
>Creating and Managing Bug Reports</A
></DT
><DD
><DL
><DT
->4.3.3.1. <A
+>2.3.3.1. <A
HREF="how.html#BUG_WRITING"
>Writing a Great Bug Report</A
></DT
><DT
->4.3.3.2. <A
+>2.3.3.2. <A
HREF="how.html#BUG_MANAGE"
>Managing your Bug Reports</A
></DT
@@ -148,55 +148,55 @@ HREF="how.html#BUG_MANAGE"
></DL
></DD
><DT
->4.4. <A
+>2.4. <A
HREF="init4me.html"
->What's in it for me?</A
+>Where can I find my user preferences?</A
></DT
><DD
><DL
><DT
->4.4.1. <A
+>2.4.1. <A
HREF="init4me.html#ACCOUNTSETTINGS"
>Account Settings</A
></DT
><DT
->4.4.2. <A
+>2.4.2. <A
HREF="init4me.html#EMAILSETTINGS"
>Email Settings</A
></DT
><DD
><DL
><DT
->4.4.2.1. <A
+>2.4.2.1. <A
HREF="init4me.html#NOTIFICATION"
>Email Notification</A
></DT
><DT
->4.4.2.2. <A
+>2.4.2.2. <A
HREF="init4me.html#NEWEMAILTECH"
>New Email Technology</A
></DT
><DT
->4.4.2.3. <A
+>2.4.2.3. <A
HREF="init4me.html#WATCHSETTINGS"
>"Watching" Users</A
></DT
></DL
></DD
><DT
->4.4.3. <A
+>2.4.3. <A
HREF="init4me.html#FOOTERSETTINGS"
>Page Footer</A
></DT
><DT
->4.4.4. <A
+>2.4.4. <A
HREF="init4me.html#PERMISSIONSETTINGS"
>Permissions</A
></DT
></DL
></DD
><DT
->4.5. <A
+>2.5. <A
HREF="usingbz-conc.html"
>Using Bugzilla-Conclusion</A
></DT
@@ -218,7 +218,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
-HREF="security.html"
+HREF="conventions.html"
>Prev</A
></TD
><TD
@@ -243,7 +243,7 @@ HREF="whatis.html"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
->Bugzilla Security</TD
+>Document Conventions</TD
><TD
WIDTH="34%"
ALIGN="center"
diff --git a/docs/html/usingbz-conc.html b/docs/html/usingbz-conc.html
index 823b12694..ced0648ee 100644
--- a/docs/html/usingbz-conc.html
+++ b/docs/html/usingbz-conc.html
@@ -4,7 +4,7 @@
>Using Bugzilla-Conclusion</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
@@ -13,11 +13,11 @@ REL="UP"
TITLE="Using Bugzilla"
HREF="using.html"><LINK
REL="PREVIOUS"
-TITLE="What's in it for me?"
+TITLE="Where can I find my user preferences?"
HREF="init4me.html"><LINK
REL="NEXT"
-TITLE="Integrating Bugzilla with Third-Party Tools"
-HREF="integration.html"></HEAD
+TITLE="Installation"
+HREF="installation.html"></HEAD
><BODY
CLASS="SECTION"
BGCOLOR="#FFFFFF"
@@ -51,13 +51,13 @@ HREF="init4me.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
->Chapter 4. Using Bugzilla</TD
+>Chapter 2. Using Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
-HREF="integration.html"
+HREF="installation.html"
>Next</A
></TD
></TR
@@ -71,19 +71,17 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="USINGBZ-CONC"
->4.5. Using Bugzilla-Conclusion</A
+>2.5. Using Bugzilla-Conclusion</A
></H1
><P
-> Thank you for reading through this portion of the Bugzilla Guide. I anticipate
- it may not yet meet the needs of all readers. If you have additional comments or
- corrections to make, please submit your contributions to the
- <A
+> Thank you for reading through this portion of the Bugzilla
+ Guide. I anticipate it may not yet meet the needs of all
+ readers. If you have additional comments or corrections to
+ make, please submit your contributions to the <A
HREF="mailto://mozilla-webtools@mozilla.org"
TARGET="_top"
>mozilla-webtools</A
->
- mailing list/newsgroup. The mailing list is mirrored to the netscape.public.mozilla.webtools
- newsgroup, and the newsgroup is mirrored to mozilla-webtools@mozilla.org
+> mailing list/newsgroup. The mailing list is mirrored to the netscape.public.mozilla.webtools newsgroup, and the newsgroup is mirrored to mozilla-webtools@mozilla.org
</P
></DIV
><DIV
@@ -117,7 +115,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
-HREF="integration.html"
+HREF="installation.html"
>Next</A
></TD
></TR
@@ -126,7 +124,7 @@ HREF="integration.html"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
->What's in it for me?</TD
+>Where can I find my user preferences?</TD
><TD
WIDTH="34%"
ALIGN="center"
@@ -139,7 +137,7 @@ HREF="using.html"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
->Integrating Bugzilla with Third-Party Tools</TD
+>Installation</TD
></TR
></TABLE
></DIV
diff --git a/docs/html/variant_fenris.html b/docs/html/variant_fenris.html
new file mode 100644
index 000000000..3dd120fe0
--- /dev/null
+++ b/docs/html/variant_fenris.html
@@ -0,0 +1,142 @@
+<HTML
+><HEAD
+><TITLE
+>Loki Bugzilla (Fenris)</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide"
+HREF="index.html"><LINK
+REL="UP"
+TITLE="Bugzilla Variants and Competitors"
+HREF="variants.html"><LINK
+REL="PREVIOUS"
+TITLE="Red Hat Bugzilla"
+HREF="rhbugzilla.html"><LINK
+REL="NEXT"
+TITLE="Issuezilla"
+HREF="variant_issuezilla.html"></HEAD
+><BODY
+CLASS="SECTION"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>The Bugzilla Guide</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="rhbugzilla.html"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Chapter 7. Bugzilla Variants and Competitors</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="variant_issuezilla.html"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="SECTION"
+><H1
+CLASS="SECTION"
+><A
+NAME="VARIANT_FENRIS"
+>7.2. Loki Bugzilla (Fenris)</A
+></H1
+><P
+>Fenris can be found at <A
+HREF="http://fenris.lokigames.com/"
+TARGET="_top"
+>http://fenris.lokigames.com</A
+>. It is a fork from Bugzilla.</P
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="rhbugzilla.html"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="variant_issuezilla.html"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Red Hat Bugzilla</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="variants.html"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Issuezilla</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file
diff --git a/docs/html/variant_issuezilla.html b/docs/html/variant_issuezilla.html
new file mode 100644
index 000000000..83cf31704
--- /dev/null
+++ b/docs/html/variant_issuezilla.html
@@ -0,0 +1,153 @@
+<HTML
+><HEAD
+><TITLE
+>Issuezilla</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide"
+HREF="index.html"><LINK
+REL="UP"
+TITLE="Bugzilla Variants and Competitors"
+HREF="variants.html"><LINK
+REL="PREVIOUS"
+TITLE="Loki Bugzilla (Fenris)"
+HREF="variant_fenris.html"><LINK
+REL="NEXT"
+TITLE="Scarab"
+HREF="variant_scarab.html"></HEAD
+><BODY
+CLASS="SECTION"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>The Bugzilla Guide</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="variant_fenris.html"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Chapter 7. Bugzilla Variants and Competitors</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="variant_scarab.html"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="SECTION"
+><H1
+CLASS="SECTION"
+><A
+NAME="VARIANT_ISSUEZILLA"
+>7.3. Issuezilla</A
+></H1
+><P
+>Issuezilla is another fork from Bugzilla, and seems nearly
+ as popular as the Red Hat Bugzilla fork. Some Issuezilla team
+ members are regular contributors to the Bugzilla mailing
+ list/newsgroup. Issuezilla is not the primary focus of
+ bug-tracking at tigris.org, however. Their Java-based
+ bug-tracker, <A
+HREF="variant_scarab.html"
+>Scarab, a newfangled Java-based issue tracker</A
+>, is under heavy development
+ and looks promising!</P
+><P
+>URL: <A
+HREF="http://issuezilla.tigris.org/servlets/ProjectHome"
+TARGET="_top"
+>http://issuezilla.tigris.org/servlets/ProjectHome</A
+></P
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="variant_fenris.html"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="variant_scarab.html"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Loki Bugzilla (Fenris)</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="variants.html"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Scarab</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file
diff --git a/docs/html/variant_perforce.html b/docs/html/variant_perforce.html
new file mode 100644
index 000000000..13944a65b
--- /dev/null
+++ b/docs/html/variant_perforce.html
@@ -0,0 +1,148 @@
+<HTML
+><HEAD
+><TITLE
+>Perforce SCM</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide"
+HREF="index.html"><LINK
+REL="UP"
+TITLE="Bugzilla Variants and Competitors"
+HREF="variants.html"><LINK
+REL="PREVIOUS"
+TITLE="Scarab"
+HREF="variant_scarab.html"><LINK
+REL="NEXT"
+TITLE="SourceForge"
+HREF="variant_sourceforge.html"></HEAD
+><BODY
+CLASS="SECTION"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>The Bugzilla Guide</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="variant_scarab.html"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Chapter 7. Bugzilla Variants and Competitors</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="variant_sourceforge.html"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="SECTION"
+><H1
+CLASS="SECTION"
+><A
+NAME="VARIANT_PERFORCE"
+>7.5. Perforce SCM</A
+></H1
+><P
+>Although Perforce isn't really a bug tracker, it can be used
+ as such through the <SPAN
+CLASS="QUOTE"
+>"jobs"</SPAN
+> functionality.</P
+><P
+><A
+HREF="http://www.perforce.com/perforce/technotes/note052.html"
+TARGET="_top"
+>http://www.perforce.com/perforce/technotes/note052.html</A
+>http://www.perforce.com/perforce/technotes/note052.html</P
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="variant_scarab.html"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="variant_sourceforge.html"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Scarab</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="variants.html"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>SourceForge</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file
diff --git a/docs/html/variant_scarab.html b/docs/html/variant_scarab.html
new file mode 100644
index 000000000..57a085052
--- /dev/null
+++ b/docs/html/variant_scarab.html
@@ -0,0 +1,148 @@
+<HTML
+><HEAD
+><TITLE
+>Scarab</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide"
+HREF="index.html"><LINK
+REL="UP"
+TITLE="Bugzilla Variants and Competitors"
+HREF="variants.html"><LINK
+REL="PREVIOUS"
+TITLE="Issuezilla"
+HREF="variant_issuezilla.html"><LINK
+REL="NEXT"
+TITLE="Perforce SCM"
+HREF="variant_perforce.html"></HEAD
+><BODY
+CLASS="SECTION"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>The Bugzilla Guide</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="variant_issuezilla.html"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Chapter 7. Bugzilla Variants and Competitors</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="variant_perforce.html"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="SECTION"
+><H1
+CLASS="SECTION"
+><A
+NAME="VARIANT_SCARAB"
+>7.4. Scarab</A
+></H1
+><P
+>Scarab is a promising new bug-tracking system built using
+ Java Serlet technology. As of this writing, no source code has
+ been released as a package, but you can obtain the code from
+ CVS.
+ </P
+><P
+>URL: <A
+HREF="http://scarab.tigris.org/"
+TARGET="_top"
+>http://scarab.tigris.org</A
+></P
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="variant_issuezilla.html"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="variant_perforce.html"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Issuezilla</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="variants.html"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Perforce SCM</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file
diff --git a/docs/html/variant_sourceforge.html b/docs/html/variant_sourceforge.html
new file mode 100644
index 000000000..cfbaffb94
--- /dev/null
+++ b/docs/html/variant_sourceforge.html
@@ -0,0 +1,148 @@
+<HTML
+><HEAD
+><TITLE
+>SourceForge</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide"
+HREF="index.html"><LINK
+REL="UP"
+TITLE="Bugzilla Variants and Competitors"
+HREF="variants.html"><LINK
+REL="PREVIOUS"
+TITLE="Perforce SCM"
+HREF="variant_perforce.html"><LINK
+REL="NEXT"
+TITLE="The Bugzilla FAQ"
+HREF="faq.html"></HEAD
+><BODY
+CLASS="SECTION"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>The Bugzilla Guide</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="variant_perforce.html"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Chapter 7. Bugzilla Variants and Competitors</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="faq.html"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="SECTION"
+><H1
+CLASS="SECTION"
+><A
+NAME="VARIANT_SOURCEFORGE"
+>7.6. SourceForge</A
+></H1
+><P
+>SourceForge is more of a way of coordinating geographically
+ distributed free software and open source projects over the
+ Internet than strictly a bug tracker, but if you're hunting for
+ bug-tracking for your open project, it may be just what the
+ software engineer ordered!</P
+><P
+>URL: <A
+HREF="http://www.sourceforge.net"
+TARGET="_top"
+>http://www.sourceforge.net</A
+></P
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="variant_perforce.html"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="faq.html"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Perforce SCM</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="variants.html"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>The Bugzilla FAQ</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file
diff --git a/docs/html/variants.html b/docs/html/variants.html
index 997f00461..a2405d770 100644
--- a/docs/html/variants.html
+++ b/docs/html/variants.html
@@ -1,17 +1,17 @@
<HTML
><HEAD
><TITLE
->Bugzilla Variants</TITLE
+>Bugzilla Variants and Competitors</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="PREVIOUS"
-TITLE="Cleaning up after mucking with Bugzilla"
-HREF="cleanupwork.html"><LINK
+TITLE="The Future of Bugzilla"
+HREF="future.html"><LINK
REL="NEXT"
TITLE="Red Hat Bugzilla"
HREF="rhbugzilla.html"></HEAD
@@ -41,7 +41,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
-HREF="cleanupwork.html"
+HREF="future.html"
>Prev</A
></TD
><TD
@@ -67,23 +67,56 @@ CLASS="CHAPTER"
><H1
><A
NAME="VARIANTS"
->Chapter 7. Bugzilla Variants</A
+>Chapter 7. Bugzilla Variants and Competitors</A
></H1
><DIV
-CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
-><P
+CLASS="TOC"
+><DL
+><DT
><B
->Note: </B
-> I <EM
->know</EM
-> there are more variants than just RedHat Bugzilla out there.
- Please help me get information about them, their project status, and benefits there
- might be in using them or in using their code in main-tree Bugzilla.
- </P
-></BLOCKQUOTE
+>Table of Contents</B
+></DT
+><DT
+>7.1. <A
+HREF="rhbugzilla.html"
+>Red Hat Bugzilla</A
+></DT
+><DT
+>7.2. <A
+HREF="variant_fenris.html"
+>Loki Bugzilla (Fenris)</A
+></DT
+><DT
+>7.3. <A
+HREF="variant_issuezilla.html"
+>Issuezilla</A
+></DT
+><DT
+>7.4. <A
+HREF="variant_scarab.html"
+>Scarab</A
+></DT
+><DT
+>7.5. <A
+HREF="variant_perforce.html"
+>Perforce SCM</A
+></DT
+><DT
+>7.6. <A
+HREF="variant_sourceforge.html"
+>SourceForge</A
+></DT
+></DL
></DIV
+><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
></DIV
><DIV
CLASS="NAVFOOTER"
@@ -100,7 +133,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
-HREF="cleanupwork.html"
+HREF="future.html"
>Prev</A
></TD
><TD
@@ -125,7 +158,7 @@ HREF="rhbugzilla.html"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
->Cleaning up after mucking with Bugzilla</TD
+>The Future of Bugzilla</TD
><TD
WIDTH="34%"
ALIGN="center"
diff --git a/docs/html/whatis.html b/docs/html/whatis.html
index d53d68370..248467ef5 100644
--- a/docs/html/whatis.html
+++ b/docs/html/whatis.html
@@ -4,7 +4,7 @@
>What is Bugzilla?</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
@@ -51,7 +51,7 @@ HREF="using.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
->Chapter 4. Using Bugzilla</TD
+>Chapter 2. Using Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
@@ -71,22 +71,22 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="WHATIS"
->4.1. What is Bugzilla?</A
+>2.1. What is Bugzilla?</A
></H1
><P
-> Bugzilla is one example of a class of programs called "Defect Tracking Systems",
- or, more commonly, "Bug-Tracking Systems". Defect Tracking Systems allow individual or
- groups of developers to keep track of outstanding bugs in their product effectively.
- Bugzilla was originally written by Terry Weissman in a programming language called
- "TCL", to replace a crappy
- bug-tracking database used internally for Netscape Communications. Terry later ported
- Bugzilla to
- Perl from TCL, and in Perl it remains to this day.
- Most commercial defect-tracking software vendors at the
- time charged enormous licensing fees, and Bugzilla quickly became a favorite of the
- open-source crowd (with its genesis in the open-source browser project, Mozilla). It
- is now the de-facto standard defect-tracking system against which all others are
- measured.
+> Bugzilla is one example of a class of programs called "Defect
+Tracking Systems", or, more commonly, "Bug-Tracking Systems". Defect
+Tracking Systems allow individual or groups of developers to keep
+track of outstanding bugs in their product effectively. Bugzilla was
+originally written by Terry Weissman in a programming language called
+"TCL", to replace a crappy bug-tracking database used internally for
+Netscape Communications. Terry later ported Bugzilla to Perl from
+TCL, and in Perl it remains to this day. Most commercial
+defect-tracking software vendors at the time charged enormous
+licensing fees, and Bugzilla quickly became a favorite of the
+open-source crowd (with its genesis in the open-source browser
+project, Mozilla). It is now the de-facto standard defect-tracking
+system against which all others are measured.
</P
><P
> Bugzilla has matured immensely, and now boasts many advanced features. These include:
@@ -125,13 +125,15 @@ NAME="WHATIS"
></LI
><LI
><P
-> email, XML, and HTTP APIs
+> email, XML, console, and HTTP APIs
</P
></LI
><LI
><P
-> available integration with automated software configuration management systems, including
- Perforce and CVS.
+> available integration with automated software
+ configuration management systems, including Perforce and
+ CVS (through the Bugzilla email interface and
+ checkin/checkout scripts)
</P
></LI
><LI
@@ -143,25 +145,33 @@ NAME="WHATIS"
>
</P
><P
-> Despite its current robustness and popularity, however, Bugzilla
- faces some near-term challenges, such as reliance on a single database, a lack of
- abstraction of the user interface and program logic, verbose email bug
- notifications, a powerful but daunting query interface, little reporting configurability,
- problems with extremely large queries, some unsupportable bug resolution options,
- no internationalization, and dependence on some nonstandard libraries.
+> Despite its current robustness and popularity, Bugzilla faces
+ some near-term challenges, such as reliance on a single
+ database, a lack of abstraction of the user interface and
+ program logic, verbose email bug notifications, a powerful but
+ daunting query interface, little reporting configurability,
+ problems with extremely large queries, some unsupportable bug
+ resolution options, little internationalization (although non-US
+ character sets are accepted for comments), and dependence on
+ some nonstandard libraries.
</P
><P
-> Some recent headway has been made on the query front, however. If you are using the latest
- version of Bugzilla, you should see a "simple search" form on the default front page of
- your Bugzilla install. Type in two or three search terms and you should pull up some
- relevant information. This is also available as "queryhelp.cgi".
+> Some recent headway has been made on the query front, however.
+ If you are using the latest version of Bugzilla, you should see
+ a <SPAN
+CLASS="QUOTE"
+>"simple search"</SPAN
+> form on the default front page of
+ your Bugzilla install. Type in two or three search terms and
+ you should pull up some relevant information. This is also
+ available as "queryhelp.cgi".
</P
><P
-> Despite these small problems, Bugzilla is very hard to beat. It is under <EM
+> Despite these small problems, Bugzilla is very hard to beat. It
+ is under <EM
>very</EM
->
- active development to address the current issues, and a long-awaited overhaul in the form
- of Bugzilla 3.0 is expected sometime later this year.
+> active development to address
+ the current issues, and continually gains new features.
</P
></DIV
><DIV
diff --git a/docs/html/why.html b/docs/html/why.html
index b3110f1ec..dbbb4668b 100644
--- a/docs/html/why.html
+++ b/docs/html/why.html
@@ -4,7 +4,7 @@
>Why Should We Use Bugzilla?</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
@@ -51,7 +51,7 @@ HREF="whatis.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
->Chapter 4. Using Bugzilla</TD
+>Chapter 2. Using Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
@@ -71,7 +71,7 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="WHY"
->4.2. Why Should We Use Bugzilla?</A
+>2.2. Why Should We Use Bugzilla?</A
></H1
><TABLE
BORDER="0"
@@ -97,23 +97,25 @@ VALIGN="TOP"
></TR
></TABLE
><P
-> 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
+> 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.
</P
><P
-> 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.
+> 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.
</P
><P
> But why should <EM
@@ -121,28 +123,35 @@ VALIGN="TOP"
> use Bugzilla?
</P
><P
-> 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, Loki software,
- Linux-Mandrake, and VA Systems. Combined with systems such as CVS, Bonsai,
- or Perforce SCM, Bugzilla provides a powerful, easy-to-use solution to
- configuration management and replication problems
+> Bugzilla 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, Loki
+ software, Linux-Mandrake, and VA Systems. Combined with systems
+ such as CVS, Bonsai, or Perforce SCM, Bugzilla provides a
+ powerful, easy-to-use solution to configuration management and
+ replication problems
</P
><P
-> 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 by using Bugzilla's e-mail integration features
- be able to follow the discussion trail that led to critical decisions.
+> 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 <EM
+>something</EM
+> 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 by using Bugzilla's e-mail
+ integration features be able to follow the discussion trail that
+ led to critical decisions.
</P
><P
-> 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.
+> 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.
</P
></DIV
><DIV
diff --git a/docs/html/win32.html b/docs/html/win32.html
new file mode 100644
index 000000000..6b639622d
--- /dev/null
+++ b/docs/html/win32.html
@@ -0,0 +1,1634 @@
+<HTML
+><HEAD
+><TITLE
+>Win32 Installation Notes</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide"
+HREF="index.html"><LINK
+REL="UP"
+TITLE="Installation"
+HREF="installation.html"><LINK
+REL="PREVIOUS"
+TITLE="Installation General Notes"
+HREF="geninstall.html"><LINK
+REL="NEXT"
+TITLE="Administering Bugzilla"
+HREF="administration.html"></HEAD
+><BODY
+CLASS="SECTION"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>The Bugzilla Guide</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="geninstall.html"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Chapter 3. Installation</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="administration.html"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="SECTION"
+><H1
+CLASS="SECTION"
+><A
+NAME="WIN32"
+>3.6. Win32 Installation Notes</A
+></H1
+><P
+>This section covers installation on Microsoft Windows 95,
+ 98, ME, NT, and 2000. Bugzilla works fine on Win32 platforms,
+ but please remember that the Bugzilla team and the author of the
+ Guide neither endorse nor support installation on Microsoft
+ Windows. Bugzilla installs and runs <EM
+>best</EM
+>
+ and <EM
+>easiest</EM
+> on UNIX-like operating systems,
+ and that is the way it will stay for the foreseeable future. The
+ Bugzilla team is considering supporting Win32 for the 2.16
+ release and later.</P
+><P
+>The easiest way to install Bugzilla on Intel-archiecture
+ machines is to install some variant of GNU/Linux, then follow
+ the UNIX installation instructions in this Guide. If you have
+ any influence in the platform choice for running this system,
+ please choose GNU/Linux instead of Microsoft Windows.</P
+><DIV
+CLASS="SECTION"
+><H2
+CLASS="SECTION"
+><A
+NAME="WININSTALL"
+>3.6.1. Win32 Installation: Step-by-step</A
+></H2
+><DIV
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> You should be familiar with, and cross-reference, the rest
+ of the
+ <A
+HREF="installation.html"
+>Bugzilla Installation</A
+> section while performing your
+ Win32 installation.
+ </P
+><P
+> Making Bugzilla work on Microsoft Windows is no
+ picnic. Support for Win32 has improved dramatically in the
+ last few releases, but, if you choose to proceed, you should
+ be a <EM
+>very</EM
+> skilled Windows Systems
+ Administrator with strong troubleshooting abilities, a high
+ tolerance for pain, and moderate perl skills. Bugzilla on NT
+ requires hacking source code and implementing some advanced
+ utilities. What follows is the recommended installation
+ procedure for Win32; additional suggestions are provided in
+ <A
+HREF="faq.html"
+>Appendix A</A
+>.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+><DIV
+CLASS="PROCEDURE"
+><OL
+TYPE="1"
+><LI
+><P
+> Install <A
+HREF="http://www.apache.org/"
+TARGET="_top"
+>Apache Web
+ Server</A
+> for Windows, and copy the Bugzilla files
+ somewhere Apache can serve them. Please follow all the
+ instructions referenced in <A
+HREF="installation.html"
+>Bugzilla Installation</A
+>
+ regarding your Apache configuration, particularly
+ instructions regarding the <SPAN
+CLASS="QUOTE"
+>"AddHandler"</SPAN
+>
+ parameter and <SPAN
+CLASS="QUOTE"
+>"ExecCGI"</SPAN
+>.
+ </P
+><DIV
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> You may also use Internet Information Server or Personal
+ Web Server for this purpose. However, setup is quite
+ different. If ActivePerl doesn't seem to handle your
+ file associations correctly (for .cgi and .pl files),
+ please consult <A
+HREF="faq.html"
+>Appendix A</A
+>.
+ </P
+><P
+> If you are going to use IIS, if on Windows NT you must
+ be updated to at least Service Pack 4. Windows 2000
+ ships with a sufficient version of IIS.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+></LI
+><LI
+><P
+> Install <A
+HREF="http://www.activestate.com/"
+TARGET="_top"
+>ActivePerl</A
+> for Windows. Check <A
+HREF="http://aspn.activestate.com/ASPN/Downloads/ActivePerl/"
+TARGET="_top"
+>http://aspn.activestate.com/ASPN/Downloads/ActivePerl</A
+> for a current compiled binary.
+ </P
+><P
+> Please also check the following links to fully understand the status
+ of ActivePerl on Win32:
+ <A
+HREF="http://language.perl.com/newdocs/pod/perlport.html"
+TARGET="_top"
+> Perl Porting</A
+>, and
+ <A
+HREF="http://ftp.univie.ac.at/packages/perl/ports/nt/FAQ/perlwin32faq5.html"
+TARGET="_top"
+> Perl on Win32 FAQ</A
+>
+ </P
+></LI
+><LI
+><P
+> Use ppm from your perl\bin directory to install the following packs: DBI,
+ DBD-Mysql, TimeDate, Chart, Date-Calc, Date-Manip, and GD. You may need
+ to extract them from .zip format using Winzip or other unzip program first.
+ These additional ppm modules can be downloaded from ActiveState.
+ </P
+><DIV
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> You can find a list of modules at
+ <A
+HREF="http://www.activestate.com/PPMPackages/zips/5xx-builds-only"
+TARGET="_top"
+> http://www.activestate.com/PPMPackages/zips/5xx-builds-only/</A
+>
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+><P
+> The syntax for ppm is:
+ <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>C:> </TT
+><B
+CLASS="COMMAND"
+>ppm <modulename></B
+>
+ </TT
+>
+ </P
+><DIV
+CLASS="EXAMPLE"
+><A
+NAME="AEN1038"
+></A
+><P
+><B
+>Example 3-3. Installing ActivePerl ppd Modules on Microsoft Windows</B
+></P
+><P
+><TT
+CLASS="PROMPT"
+>C:></TT
+><B
+CLASS="COMMAND"
+>ppm
+ <TT
+CLASS="OPTION"
+>DBD-Mysql</TT
+></B
+></P
+><P
+>Watch your capitalization!</P
+></DIV
+><P
+> You can find ActiveState ppm modules at
+ <A
+HREF="http://www.activestate.com/PPMPackages/5.6plus/"
+TARGET="_top"
+> http://www.activestate.com/PPMPackages/5.6plus</A
+>
+ </P
+></LI
+><LI
+><P
+> Install MySQL for NT.
+ <DIV
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> You can download MySQL for Windows NT from <A
+HREF="http://www.mysql.com/"
+TARGET="_top"
+>MySQL.com</A
+>. Some find it helpful to use the WinMySqlAdmin utility, included with the download, to set up the database.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+>
+ </P
+></LI
+><LI
+><P
+> Setup MySQL
+ </P
+><OL
+CLASS="SUBSTEPS"
+TYPE="a"
+><LI
+><P
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>C:> </TT
+>
+ <B
+CLASS="COMMAND"
+>C:\mysql\bin\mysql -u root mysql</B
+>
+ </TT
+>
+ </P
+></LI
+><LI
+><P
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>mysql></TT
+>
+ <B
+CLASS="COMMAND"
+>DELETE FROM user WHERE Host='localhost' AND User='';</B
+>
+ </TT
+>
+ </P
+></LI
+><LI
+><P
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>mysql></TT
+>
+ <B
+CLASS="COMMAND"
+>UPDATE user SET Password=PASSWORD ('new_password')
+ WHERE user='root';</B
+>
+ </TT
+>
+ </P
+><P
+><SPAN
+CLASS="QUOTE"
+>"new_password"</SPAN
+>, above, indicates
+ whatever password you wish to use for your
+ <SPAN
+CLASS="QUOTE"
+>"root"</SPAN
+> user.</P
+></LI
+><LI
+><A
+NAME="NTBUGS-PASSWORD"
+></A
+><P
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>mysql></TT
+>
+ <B
+CLASS="COMMAND"
+>GRANT SELECT, INSERT, UPDATE, DELETE,
+ INDEX, ALTER, CREATE, DROP, REFERENCES
+ ON bugs.* to bugs@localhost
+ IDENTIFIED BY 'bugs_password';</B
+>
+ </TT
+>
+ </P
+><P
+><SPAN
+CLASS="QUOTE"
+>"bugs_password"</SPAN
+>, above, indicates
+ whatever password you wish to use for your
+ <SPAN
+CLASS="QUOTE"
+>"bugs"</SPAN
+> user.</P
+></LI
+><LI
+><P
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>mysql></TT
+>
+ <B
+CLASS="COMMAND"
+>FLUSH PRIVILEGES;</B
+>
+ </TT
+>
+ </P
+></LI
+><LI
+><P
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>mysql></TT
+>
+ <B
+CLASS="COMMAND"
+>create database bugs;</B
+>
+ </TT
+>
+ </P
+></LI
+><LI
+><P
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>mysql></TT
+>
+ <B
+CLASS="COMMAND"
+>exit;</B
+>
+ </TT
+>
+ </P
+></LI
+><LI
+><P
+> <TT
+CLASS="COMPUTEROUTPUT"
+> <TT
+CLASS="PROMPT"
+>C:></TT
+>
+ <B
+CLASS="COMMAND"
+>C:\mysql\bin\mysqladmin -u root -p reload</B
+>
+ </TT
+>
+ </P
+></LI
+></OL
+></LI
+><LI
+><P
+> Edit <TT
+CLASS="FILENAME"
+>checksetup.pl</TT
+> in your Bugzilla directory. Change
+ this line:
+ </P
+><P
+> <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>my $webservergid = getgrnam($my_webservergroup);
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+ </P
+><P
+> to
+ </P
+><P
+> <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>my $webservergid = $my_webservergroup;
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+or the name of the group you wish to own the files explicitly:
+ <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>my $webservergid = 'Administrators'
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+ </P
+></LI
+><LI
+><P
+> Run <TT
+CLASS="FILENAME"
+>checksetup.pl</TT
+> from the Bugzilla directory.
+ </P
+></LI
+><LI
+><P
+>Edit <TT
+CLASS="FILENAME"
+>localconfig</TT
+> to suit your
+ requirements. Set <TT
+CLASS="VARNAME"
+>$db_pass</TT
+> to your
+ <SPAN
+CLASS="QUOTE"
+>"bugs_password"</SPAN
+> from <A
+HREF="win32.html#NTBUGS-PASSWORD"
+>step 5.d</A
+>, and <TT
+CLASS="VARNAME"
+>$webservergroup</TT
+> to <SPAN
+CLASS="QUOTE"
+>"8"</SPAN
+>.</P
+><DIV
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>Not sure on the <SPAN
+CLASS="QUOTE"
+>"8"</SPAN
+> for
+ <TT
+CLASS="VARNAME"
+>$webservergroup</TT
+> above. If it's
+ wrong, please send corrections.</P
+></TD
+></TR
+></TABLE
+></DIV
+></LI
+><LI
+><P
+> Edit <TT
+CLASS="FILENAME"
+>defparams.pl</TT
+> to suit your
+ requirements. Particularly, set
+ <TT
+CLASS="VARNAME"
+>DefParam("maintainer")</TT
+> and
+ <TT
+CLASS="VARNAME"
+>DefParam("urlbase") to match your
+ install.</TT
+>
+ </P
+><DIV
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>This is yet another step I'm not sure of, since the
+ maintainer of this documentation does not maintain
+ Bugzilla on NT. If you can confirm or deny that this
+ step is required, please let me know.</P
+></TD
+></TR
+></TABLE
+></DIV
+></LI
+><LI
+><DIV
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> There are several alternatives to Sendmail that will work on Win32.
+ The one mentioned here is a <EM
+>suggestion</EM
+>, not
+ a requirement. Some other mail packages that can work include
+ <A
+HREF="http://www.blat.net/"
+TARGET="_top"
+>BLAT</A
+>,
+ <A
+HREF="http://www.geocel.com/windmail/"
+TARGET="_top"
+>Windmail</A
+>,
+ <A
+HREF="http://www.dynamicstate.com/"
+TARGET="_top"
+>Mercury Sendmail</A
+>,
+ and the CPAN Net::SMTP Perl module (available in .ppm).
+ Every option requires some hacking of the Perl scripts for Bugzilla
+ to make it work. The option here simply requires the least.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+><DIV
+CLASS="PROCEDURE"
+><OL
+TYPE="1"
+><LI
+><P
+> Download NTsendmail, available from<A
+HREF="http://www.ntsendmail.com/"
+TARGET="_top"
+> www.ntsendmail.com</A
+>. You must have a "real" mail server which allows you to relay off it in your $ENV{"NTsendmail"} (which you should probably place in globals.pl)
+ </P
+></LI
+><LI
+><P
+>Put ntsendmail.pm into your .\perl\lib directory.</P
+></LI
+><LI
+><P
+>Add to globals.pl:</P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+># these settings configure the NTsendmail process
+use NTsendmail;
+$ENV{"NTsendmail"}="your.smtpserver.box";
+$ENV{"NTsendmail_debug"}=1;
+$ENV{"NTsendmail_max_tries"}=5;
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+><DIV
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> Some mention to also edit
+ <TT
+CLASS="VARNAME"
+>$db_pass</TT
+> in
+ <TT
+CLASS="FILENAME"
+>globals.pl</TT
+> to be your
+ <SPAN
+CLASS="QUOTE"
+>"bugs_password"</SPAN
+>. Although this may get
+ you around some problem authenticating to your
+ database, since globals.pl is not normally
+ restricted by <TT
+CLASS="FILENAME"
+>.htaccess</TT
+>, your
+ database password is exposed to whoever uses your
+ web server.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+></LI
+><LI
+><P
+> Find and comment out all occurences of
+ <SPAN
+CLASS="QUOTE"
+>"<B
+CLASS="COMMAND"
+>open(SENDMAIL</B
+>"</SPAN
+> in
+ your Bugzilla directory. Then replace them with:
+ <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+># new sendmail functionality
+my $mail=new NTsendmail;
+my $from="bugzilla\@your.machine.name.tld";
+my $to=$login;
+my $subject=$urlbase;
+$mail->send($from,$to,$subject,$msg);
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+ </P
+><DIV
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> Some have found success using the commercial product,
+ <SPAN
+CLASS="PRODUCTNAME"
+>Windmail</SPAN
+>.
+ You could try replacing your sendmail calls with:
+ <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>open SENDMAIL, "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t > mail.log";
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+ or something to that effect.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+></LI
+></OL
+></DIV
+></LI
+><LI
+><P
+> Change all references in all files from
+ <TT
+CLASS="FILENAME"
+>processmail</TT
+> to
+ <TT
+CLASS="FILENAME"
+>processmail.pl</TT
+>, and
+ rename <TT
+CLASS="FILENAME"
+>processmail</TT
+> to
+ <TT
+CLASS="FILENAME"
+>processmail.pl</TT
+>.
+ </P
+><DIV
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> Many think this may be a change we want to make for
+ main-tree Bugzilla. It's painless for the UNIX folks,
+ and will make the Win32 people happier.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+><DIV
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> Some people have suggested using the Net::SMTP Perl module instead of NTsendmail or the other options listed here. You can change processmail.pl to make this work.
+ <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+> my $smtp = Net::SMTP->new('<Name of your SMTP server>'); #connect to SMTP server
+$smtp->mail('<your name>@<you smpt server>');# use the sender's adress here
+$smtp->to($tolist); # recipient's address
+$smtp->data(); # Start the mail
+$smtp->datasend($msg);
+$smtp->dataend(); # Finish sending the mail
+$smtp->quit; # Close the SMTP connection
+$logstr = "$logstr; mail sent to $tolist $cclist";
+} </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+here is a test mail program for Net::SMTP:
+<TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+> use Net::SMTP;
+ my $smtp = Net::SMTP->new('<Name of your SMTP server', Timeout => 30, Debug
+=> 1, ); # connect to SMTP server
+ $smtp->auth;
+ $smtp->mail('you@yourcompany.com');# use the sender's adress
+here
+ $smtp->to('someotherAddress@someotherdomain.com'); #
+recipient's address
+ $smtp->data(); # Start the mail
+ $smtp->datasend('test');
+ $smtp->dataend(); # Finish sending the mail
+ $smtp->quit; # Close the SMTP connection
+exit; </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+></LI
+><LI
+><DIV
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> This step is optional if you are using IIS or another
+ web server which only decides on an interpreter based
+ upon the file extension (.pl), rather than the
+ <SPAN
+CLASS="QUOTE"
+>"shebang"</SPAN
+> line (#/usr/bonsaitools/bin/perl)
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+><P
+> Modify the path to perl on the first line (#!) of all
+ files to point to your Perl installation, and add
+ <SPAN
+CLASS="QUOTE"
+>"perl"</SPAN
+> to the beginning of all Perl system
+ calls that use a perl script as an argument. This may
+ take you a while. There is a <SPAN
+CLASS="QUOTE"
+>"setperl.csh"</SPAN
+>
+ utility to speed part of this procedure, available in the
+ <A
+HREF="patches.html"
+>Useful Patches and Utilities for Bugzilla</A
+> section of The Bugzilla Guide.
+ However, it requires the Cygwin GNU-compatible environment
+ for Win32 be set up in order to work. See <A
+HREF="http://www.cygwin.com/"
+TARGET="_top"
+>http://www.cygwin.com/</A
+> for details on obtaining Cygwin.
+ </P
+></LI
+><LI
+><P
+> Modify the invocation of all system() calls in all perl
+ scripts in your Bugzilla directory. For instance, change
+ this line in processmail:
+ <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>
+system ("./processmail.pl",@ARGLIST);
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+> to
+ <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>
+system ("perl processmail.pl",@ARGLIST);
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+ </P
+></LI
+><LI
+><P
+> Add <TT
+CLASS="FUNCTION"
+>binmode()</TT
+> calls so attachments
+ will work (<A
+HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=62000"
+TARGET="_top"
+>bug 62000</A
+>).
+ </P
+><P
+> Because Microsoft Windows based systems handle binary
+ files different than Unix based systems, you need to add
+ the following lines to
+ <TT
+CLASS="FILENAME"
+>createattachment.cgi</TT
+> and
+ <TT
+CLASS="FILENAME"
+>showattachment.cgi</TT
+> before the
+ <TT
+CLASS="FUNCTION"
+>require 'CGI.pl';</TT
+> line.</P
+><P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>binmode(STDIN);
+binmode(STDOUT);</PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+ </P
+><DIV
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> According to <A
+HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=62000"
+TARGET="_top"
+>bug 62000</A
+>, the perl documentation says that you should always use <TT
+CLASS="FUNCTION"
+>binmode()</TT
+> when dealing with binary files, but never when dealing with text files. That seems to suggest that rather than aribtrarily putting <TT
+CLASS="FUNCTION"
+>binmode()</TT
+> at the begining of the attachment files, there should be logic to determine if <TT
+CLASS="FUNCTION"
+>binmode()</TT
+> is needed or not.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+></LI
+></OL
+></DIV
+><DIV
+CLASS="TIP"
+><P
+></P
+><TABLE
+CLASS="TIP"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/tip.gif"
+HSPACE="5"
+ALT="Tip"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> If you are using IIS or Personal Web Server, you must add cgi
+ relationships to Properties -> Home directory (tab) ->
+ Application Settings (section) -> Configuration (button),
+ such as:
+ </P
+><P
+> <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>
+.cgi to: <perl install directory>\perl.exe %s %s
+.pl to: <perl install directory>\perl.exe %s %s
+GET,HEAD,POST
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+ Change the path to Perl to match your
+ install, of course.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
+><DIV
+CLASS="SECTION"
+><H2
+CLASS="SECTION"
+><A
+NAME="ADDLWINTIPS"
+>3.6.2. Additional Windows Tips</A
+></H2
+><DIV
+CLASS="TIP"
+><P
+></P
+><TABLE
+CLASS="TIP"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/tip.gif"
+HSPACE="5"
+ALT="Tip"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> From Andrew Pearson:
+ <A
+NAME="AEN1212"
+></A
+><BLOCKQUOTE
+CLASS="BLOCKQUOTE"
+><P
+> You can make Bugzilla work with Personal Web Server for
+ Windows 98 and higher, as well as for IIS 4.0.
+ Microsoft has information available at <A
+HREF=" http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP"
+TARGET="_top"
+> http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP</A
+>
+ </P
+><P
+> Basically you need to add two String Keys in the
+ registry at the following location:
+ </P
+><P
+> <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\ScriptMap
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+ </P
+><P
+> The keys should be called ".pl" and ".cgi", and both
+ should have a value something like:
+ <B
+CLASS="COMMAND"
+>c:/perl/bin/perl.exe "%s" "%s"</B
+>
+ </P
+><P
+> The KB article only talks about .pl, but it goes into
+ more detail and provides a perl test script.
+ </P
+></BLOCKQUOTE
+>
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+><DIV
+CLASS="TIP"
+><P
+></P
+><TABLE
+CLASS="TIP"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/tip.gif"
+HSPACE="5"
+ALT="Tip"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> If attempting to run Bugzilla 2.12 or older, you will need
+ to remove encrypt() calls from the Perl source. This is
+ <EM
+>not necessary</EM
+> for Bugzilla 2.13 and
+ later, which includes the current release, Bugzilla
+ 2.14.
+ <DIV
+CLASS="EXAMPLE"
+><A
+NAME="AEN1224"
+></A
+><P
+><B
+>Example 3-4. Removing encrypt() for Windows NT Bugzilla version
+ 2.12 or earlier</B
+></P
+><P
+> Replace this:
+ <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>
+SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " . SQLQuote(substr($realcryptpwd, 0, 2)) . ")");
+my $enteredcryptpwd = FetchOneColumn();
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+with this:
+ <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+>
+my $enteredcryptpwd = $enteredpwd
+ </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+ in cgi.pl.
+ </P
+></DIV
+>
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
+><DIV
+CLASS="SECTION"
+><H2
+CLASS="SECTION"
+><A
+NAME="BZLDAP"
+>3.6.3. Bugzilla LDAP Integration</A
+></H2
+><P
+> What follows is some late-breaking information on using the
+ LDAP authentication options with Bugzilla. The author has not
+ tested these (nor even formatted this section!) so please
+ contribute feedback to the newsgroup.
+ </P
+><P
+CLASS="LITERALLAYOUT"
+>Mozilla::LDAP module<br>
+<br>
+The Mozilla::LDAP module allows you to use LDAP for authentication to<br>
+the Bugzilla system. This module is not required if you are not using<br>
+LDAP.<br>
+<br>
+Mozilla::LDAP (aka PerLDAP) is available for download from<br>
+http://www.mozilla.org/directory.<br>
+<br>
+NOTE: The Mozilla::LDAP module requires Netscape's Directory SDK.<br>
+Follow the link for "Directory SDK for C" on that same page to<br>
+download the SDK first. After you have installed this SDK, then<br>
+install the PerLDAP module.<br>
+----------------------------------------------------------------------<br>
+<br>
+Post-Installation Checklist<br>
+----------------------------------------------------------------------<br>
+Set useLDAP to "On" **only** if you will be using an LDAP directory<br>
+for authentication. Be very careful when setting up this parameter;<br>
+if you set LDAP authentication, but do not have a valid LDAP directory<br>
+set up, you will not be able to log back in to Bugzilla once you log<br>
+out. (If this happens, you can get back in by manually editing the<br>
+data/params file, and setting useLDAP back to 0.)<br>
+<br>
+If using LDAP, you must set the three additional parameters:<br>
+<br>
+Set LDAPserver to the name (and optionally port) of your LDAP server.<br>
+If no port is specified, it defaults to the default port of 389. (e.g<br>
+"ldap.mycompany.com" or "ldap.mycompany.com:1234")<br>
+<br>
+Set LDAPBaseDN to the base DN for searching for users in your LDAP<br>
+directory. (e.g. "ou=People,o=MyCompany") uids must be unique under<br>
+the DN specified here.<br>
+<br>
+Set LDAPmailattribute to the name of the attribute in your LDAP<br>
+directory which contains the primary email address. On most directory<br>
+servers available, this is "mail", but you may need to change this.<br>
+----------------------------------------------------------------------<br>
+<br>
+(Not sure where this bit should go, but it's important that it be in<br>
+there somewhere...)<br>
+----------------------------------------------------------------------<br>
+Using LDAP authentication for Bugzilla:<br>
+<br>
+The existing authentication scheme for Bugzilla uses email addresses<br>
+as the primary user ID, and a password to authenticate that user. All<br>
+places within Bugzilla where you need to deal with user ID (e.g<br>
+assigning a bug) use the email address.<br>
+<br>
+The LDAP authentication builds on top of this scheme, rather than<br>
+replacing it. The initial log in is done with a username and password<br>
+for the LDAP directory. This then fetches the email address from LDAP<br>
+and authenticates seamlessly in the standard Bugzilla authentication<br>
+scheme using this email address. If an account for this address<br>
+already exists in your Bugzilla system, it will log in to that<br>
+account. If no account for that email address exists, one is created<br>
+at the time of login. (In this case, Bugzilla will attempt to use the<br>
+"displayName" or "cn" attribute to determine the user's full name.)<br>
+<br>
+After authentication, all other user-related tasks are still handled<br>
+by email address, not LDAP username. You still assign bugs by email<br>
+address, query on users by email address, etc.<br>
+----------------------------------------------------------------------<br>
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="geninstall.html"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="administration.html"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Installation General Notes</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="installation.html"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Administering Bugzilla</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file
diff --git a/docs/images/CVS/Entries b/docs/images/CVS/Entries
new file mode 100644
index 000000000..06ab4731c
--- /dev/null
+++ b/docs/images/CVS/Entries
@@ -0,0 +1,7 @@
+/caution.gif/1.1/Thu Aug 23 14:30:18 2001/-kb/TBUGZILLA-2_14
+/dbschema.jpg/1.1/Wed Aug 29 17:25:34 2001/-kb/TBUGZILLA-2_14
+/dbschema.ps/1.1/Wed Aug 29 17:25:34 2001/-kb/TBUGZILLA-2_14
+/note.gif/1.1/Thu Aug 23 14:30:18 2001/-kb/TBUGZILLA-2_14
+/tip.gif/1.1/Thu Aug 23 14:30:19 2001/-kb/TBUGZILLA-2_14
+/warning.gif/1.1/Thu Aug 23 14:30:20 2001/-kb/TBUGZILLA-2_14
+D
diff --git a/docs/images/CVS/Repository b/docs/images/CVS/Repository
new file mode 100644
index 000000000..4a3e035b2
--- /dev/null
+++ b/docs/images/CVS/Repository
@@ -0,0 +1 @@
+mozilla/webtools/bugzilla/docs/images
diff --git a/oracle/CVS/Root b/docs/images/CVS/Root
similarity index 100%
rename from oracle/CVS/Root
rename to docs/images/CVS/Root
diff --git a/docs/images/CVS/Tag b/docs/images/CVS/Tag
new file mode 100644
index 000000000..c10f87310
--- /dev/null
+++ b/docs/images/CVS/Tag
@@ -0,0 +1 @@
+NBUGZILLA-2_14
diff --git a/docs/images/caution.gif b/docs/images/caution.gif
new file mode 100644
index 0000000000000000000000000000000000000000..c6bfd65bc004747cafb403ebde3845df0cbc9eb3
GIT binary patch
literal 260
zcmZ?wbhEHblxJ{YSjfP@@SoxTe};mF2@DJjia%Kx85kHCbU*}1o`LCVOaIE#Z}}I`
z5owLSdsk6kj$=l8!)y<xGzqSGnwy%U*KRUMS#9yyO8hl%nus+2_1SNtJZ7<o%;D|y
zipYM|6VZA_{llTRS=-O*uy9T5I-arh=N&!q{XTDO?ABg9T(#o&Ux&2v<3Zbxm3_Ki
zUNqH3;_8>rPt`cDRd9q$ut``*Mpl}vVAqT~>cLrc@@A#-_o9|rmmX_bCs@xeGU$HE
zdZe3U(xxq^c6~__F>=|_zU9ue>)Jn7Z&;EQHN$Oo<tmHg$uA;|tEJ-_le<lMH%9B-
Op2sb(|383%!5RR{hi<L_
literal 0
HcmV?d00001
diff --git a/docs/html/dbschema.jpg b/docs/images/dbschema.jpg
similarity index 100%
rename from docs/html/dbschema.jpg
rename to docs/images/dbschema.jpg
diff --git a/docs/images/dbschema.ps b/docs/images/dbschema.ps
new file mode 100644
index 000000000..8952a6834
--- /dev/null
+++ b/docs/images/dbschema.ps
@@ -0,0 +1,1733 @@
+%-12345X@PJL JOB
+@PJL ENTER LANGUAGE = POSTSCRIPT
+
+%!PS-Adobe-3.0
+%%Title: PDM Model_7 - I:\DATA\SDESI
+%%Creator: PSCRIPT.DRV Version 4.0
+%%CreationDate: 12/06/00 23:59:39
+%%BoundingBox: 12 13 601 779
+%%Pages: (atend)
+%%PageOrder: Special
+%%Requirements:
+%%DocumentNeededFonts: (atend)
+%%DocumentSuppliedFonts: (atend)
+%%DocumentData: Clean7Bit
+%%LanguageLevel: 2
+%%EndComments
+
+%%BeginProlog
+%%BeginProcSet: Pscript_Win_ErrorHandler 1.0 1
+/currentpacking where{pop/oldpack currentpacking def/setpacking where{pop
+false setpacking}if}if/$brkpage 64 dict def $brkpage begin/prnt{dup type
+/stringtype ne{=string cvs}if dup length 6 mul/tx exch def/ty 10 def
+currentpoint/toy exch def/tox exch def 1 setgray newpath tox toy 2 sub moveto
+0 ty rlineto tx 0 rlineto 0 ty neg rlineto closepath fill tox toy moveto 0
+setgray show}bind def/nl{currentpoint exch pop lmargin exch moveto 0 -10
+rmoveto}def/=={/cp 0 def typeprint nl}def/typeprint{dup type exec}readonly def
+/lmargin 72 def/rmargin 72 def/tprint{dup length cp add rmargin gt{nl/cp 0 def
+}if dup length cp add/cp exch def prnt}readonly def/cvsprint{=string cvs
+tprint( )tprint}readonly def/integertype{cvsprint}readonly def/realtype{
+cvsprint}readonly def/booleantype{cvsprint}readonly def/operatortype{(--)
+tprint =string cvs tprint(-- )tprint}readonly def/marktype{pop(-mark- )tprint}
+readonly def/dicttype{pop(-dictionary- )tprint}readonly def/nulltype{pop
+(-null- )tprint}readonly def/filetype{pop(-filestream- )tprint}readonly def
+/savetype{pop(-savelevel- )tprint}readonly def/fonttype{pop(-fontid- )tprint}
+readonly def/nametype{dup xcheck not{(/)tprint}if cvsprint}readonly def
+/stringtype{dup rcheck{(\()tprint tprint(\))tprint}{pop(-string- )tprint}
+ifelse}readonly def/arraytype{dup rcheck{dup xcheck{({)tprint{typeprint}forall
+(})tprint}{([)tprint{typeprint}forall(])tprint}ifelse}{pop(-array- )tprint}
+ifelse}readonly def/packedarraytype{dup rcheck{dup xcheck{({)tprint{typeprint}
+forall(})tprint}{([)tprint{typeprint}forall(])tprint}ifelse}{pop
+(-packedarray- )tprint}ifelse}readonly def/courier/Courier findfont 10
+scalefont def end errordict/handleerror{systemdict begin $error begin $brkpage
+begin newerror{/newerror false store vmstatus pop pop 0 ne{grestoreall}if
+showpage initgraphics courier setfont lmargin 720 moveto(ERROR: )prnt
+errorname prnt nl(OFFENDING COMMAND: )prnt/command load prnt $error/ostack
+known{nl nl(STACK:)prnt nl nl $error/ostack get aload length{==}repeat}if
+systemdict/showpage get exec(%%[ Error: )print errorname =print
+(; OffendingCommand: )print/command load =print( ]%%)= flush}if end end end}
+dup 0 systemdict put dup 4 $brkpage put bind readonly put/currentpacking where
+{pop/setpacking where{pop oldpack setpacking}if}if
+%%EndProcSet
+userdict /Pscript_Win_Driver_Incr 200 dict dup begin put
+%%BeginResource: file Pscript_FatalError 2.0 0
+/FatalErrorIf{{initgraphics findfont exch scalefont setfont counttomark 3 div
+cvi{moveto show}repeat showpage quit}{cleartomark}ifelse}bind def
+%%EndResource
+/VM? {vmstatus exch sub exch pop gt { [
+(This job requires more memory than is available in this printer.) 100 500
+(Try one or more of the following, and then print again:) 100 485
+(In the PostScript dialog box, click Optimize For Portability.) 115 470
+(In the Device Options dialog box, make sure the Available Printer Memory is accurate.) 115 455
+(Reduce the number of fonts in the document.) 115 440
+(Print the document in parts.) 115 425
+12 /Times-Roman showpage
+(%%[ PrinterError: Low Printer VM ]%%) =
+true FatalErrorIf}if} bind def
+30000 VM?
+%%BeginResource: file Pscript_Win_Utils 2.0 0
+/|/def load def/,/load load |/~/exch , |/?/ifelse , |/!/pop , |/`/begin , |/^
+/index , |/@/dup , |/+/translate , |/$/roll , |/U/userdict , |/M/moveto , |/-
+/rlineto , |/&/currentdict , |/:/gsave , |/;/grestore , |/F/false , |/T/true ,
+|/N/newpath , |/E/end , |/Ac/arc , |/An/arcn , |/A/ashow , |/D/awidthshow , |
+/C/closepath , |/V/div , |/O/eofill , |/L/fill , |/I/lineto , |/-C/rcurveto ,
+|/-M/rmoveto , |/+S/scale , |/Ji/setfont , |/Lc/setlinecap , |/Lj/setlinejoin
+, |/Lw/setlinewidth , |/S/show , |/LH/showpage , |/K/stroke , |/W/widthshow ,
+|/R/rotate , |/b{bind |}bind |/bd{bind |}bind |/xd{~ |}bd/ld{, |}bd/lw/Lw ld
+/lc/Lc ld/lj/Lj ld/sg/setgray ld/L2? F/languagelevel where{! languagelevel 2
+ge{! T}if}if |/g{@ not{U/DefIf_save save put}if U/DefIf_bool 2 ^ put}b
+/DefIf_El{if U/DefIf_bool get not @{U/DefIf_save get restore}if}b/e{DefIf_El !
+}b/self & |/reinitialize{[/TextInit/GraphInit/UtilsInit counttomark{@ where{
+self eq}{F}?{cvx exec}{!}?}repeat cleartomark}b/initialize{`{/ADO_mxRot ~ |
+/TextInitialised? F | reinitialize E}{U/Pscript_Win_Data 200 dict @ ` put
+/ADO_mxRot ~ |/TextInitialised? F | reinitialize}?}b/terminate{!{& self eq{
+exit}{E}?}loop E}b/suspend/terminate , |/resume{` Pscript_Win_Data `}b/snap{
+transform 0.25 sub round 0.25 add ~ 0.25 sub round 0.25 add ~ itransform}b
+/dsnap{dtransform round ~ round ~ idtransform}b<04>cvn{}|/setjn{{statusdict
+/jobname known{statusdict/jobname 3 -1 $ put}if}stopped cleartomark}b/solid{[]
+0 setdash}b/setdsh{0 setdash}b/colspRefresh{}b/rp{4 2 $ M 1 ^ 0 - 0 ~ - neg 0
+-}b/rr{1 ^ 0 - 0 ~ - neg 0 - C}b
+%%EndResource
+%%BeginResource: file Pscript_Win_Utils_L1 2.0 0
+L2? not g{/rf{N rp L}b/fx{1 1 dtransform @ 0 ge{1 sub 1}{1 add -0.25}? 3 -1 $
+@ 0 ge{1 sub 1}{1 add -0.25}? 3 1 $ 4 1 $ idtransform 4 -2 $ idtransform}b/BZ{
+4 -2 $ snap + +S fx rf}b/rs{N rp C K}b/rc{N rp clip N}b/sg{setgray}b/sco{
+setrgbcolor}b/sgco{{sg}{sco}?}b}e
+%%EndResource
+%%BeginResource: file Pscript_Win_Utils_L2 2.0 0
+L2? g{/colspA/DeviceGray |/colspABC/DeviceRGB |/setAorABC{{colspA}{colspABC}?
+setcolorspace}b/rf/rectfill , |/fx{1 1 dtransform @ 0 ge{1 sub 0.5}{1 add -0.5
+}? 3 -1 $ @ 0 ge{1 sub 0.5}{1 add -0.5}? 3 1 $ 4 1 $ idtransform 4 -2 $
+idtransform}b/BZ{4 -2 $ snap + +S fx rf}b/rs/rectstroke , |/rc/rectclip , |/sg
+{@ @ setcolor}b/sco{setcolor}b/colspRefresh{colspABC setcolorspace}b/sgco{{sg
+}{sco}?}b/UtilsInit{F setglobal}b/definecolorrendering{/ColorRendering
+defineresource !}b/findcolorrendering{@/ColorRendering resourcestatus{! !
+/ColorRendering findresource T}{! F}?}b/selectcolorrendering{@/ColorRendering
+resourcestatus{! !/ColorRendering}{!/DefaultColorRendering/ColorRendering}?
+findresource setcolorrendering}b}e
+%%EndResource
+end
+%%EndProlog
+
+%%BeginSetup
+[ 1.000 0 0 1.000 0 0 ] false Pscript_Win_Driver_Incr dup /initialize get exec
+
+[{0
+/languagelevel where{pop languagelevel}{1}ifelse 2 ge{1 dict dup/JobTimeout 4 -1 roll put setuserparams}{statusdict/setjobtimeout get exec}ifelse
+} stopped cleartomark
+[{240
+/languagelevel where{pop languagelevel}{1}ifelse 2 ge{1 dict dup/WaitTimeout 4 -1 roll put setuserparams}{statusdict/waittimeout 3 -1 roll put}ifelse
+} stopped cleartomark
+[{
+%%BeginFeature: *Print as Grayscale No
+
+ <</ProcessColorModel /DeviceRGB>> setpagedevice
+%%EndFeature
+} stopped cleartomark
+[{
+
+} stopped cleartomark
+[{
+%%BeginFeature: *InputSlot AutoSelect Tray
+
+%%EndFeature
+} stopped cleartomark
+[{
+%%BeginFeature: *PageSize Letter
+
+ <</DeferredMediaSelection true>> setpagedevice
+ 2 dict dup /PageSize [612 792] put dup /ImagingBBox null put setpagedevice
+%%EndFeature
+} stopped cleartomark
+[{
+%%BeginFeature: *ColorSmart Text Vivid Color
+
+ globaldict /ColorSmartColorMatching known
+ { true ColorSmartColorMatching } if
+ globaldict /ColorSmartColorMatching known
+ { Vivid ColorSmartTextAdjustment } if
+
+%%EndFeature
+} stopped cleartomark
+[{
+%%BeginFeature: *ColorSmart Graphics Vivid Color
+
+ globaldict /ColorSmartColorMatching known
+ { Vivid ColorSmartGraphicsAdjustment } if
+
+%%EndFeature
+} stopped cleartomark
+[{
+%%BeginFeature: *ColorSmart Photos Match Color Across Printers
+
+ globaldict /ColorSmartColorMatching known
+ { MatchScreen ColorSmartImageAdjustment } if
+
+%%EndFeature
+} stopped cleartomark
+[{
+%%BeginFeature: *Text Halftone Detail
+
+ globaldict /ColorSmartColorMatching known
+ { Detail ColorSmartTextHalftone } if
+
+%%EndFeature
+} stopped cleartomark
+[{
+%%BeginFeature: *Graphics Halftone Smooth
+
+ globaldict /ColorSmartColorMatching known
+ { Smooth ColorSmartGraphicsHalftone } if
+
+%%EndFeature
+} stopped cleartomark
+[{
+%%BeginFeature: *Image Halftone Smooth
+
+ globaldict /ColorSmartColorMatching known
+ { Smooth ColorSmartImageHalftone } if
+
+%%EndFeature
+} stopped cleartomark
+[{
+%%BeginFeature: *ColorSmart Auto
+
+ globaldict /ColorSmartColorMatching known
+ { Vivid ColorSmartTextAdjustment } if
+ globaldict /ColorSmartColorMatching known
+ { Vivid ColorSmartGraphicsAdjustment } if
+ globaldict /ColorSmartColorMatching known
+ { MatchScreen ColorSmartImageAdjustment } if
+ globaldict /ColorSmartColorMatching known
+ { Detail ColorSmartTextHalftone } if
+ globaldict /ColorSmartColorMatching known
+ { Smooth ColorSmartGraphicsHalftone } if
+ globaldict /ColorSmartColorMatching known
+ { Smooth ColorSmartImageHalftone } if
+ /setscreen { pop pop pop } def
+ /setcolorscreen { pop pop pop pop pop pop pop pop pop pop pop pop } def
+ globaldict /ColorSmartColorMatching known
+ {true ColorSmartColorMatching } if
+
+%%EndFeature
+} stopped cleartomark
+[{
+%%BeginFeature: *OutputBin Upper
+1 dict dup /OutputFaceUp false put setpagedevice
+%%EndFeature
+} stopped cleartomark
+[{
+%%BeginFeature: *MediaType Plain Paper
+
+%%EndFeature
+} stopped cleartomark
+1 setlinecap 1 setlinejoin
+/mysetup [ 0.240 0 0 -0.240 12.000 779.000 ] |
+%%EndSetup
+
+userdict begin /savelevel0 save def end
+%%Page: 1 1
+%%BeginPageSetup
+[{
+%%BeginFeature: *Rear Feed Unit Not Installed
+
+%%EndFeature
+} stopped cleartomark
+[{
+%%BeginFeature: *VMOption 36 - 43 MB RAM
+
+%%EndFeature
+} stopped cleartomark
+[{
+%%BeginFeature: *Resolution 300dpi
+
+%%EndFeature
+} stopped cleartomark
+[{
+%%BeginFeature: *Duplex
+
+%%EndFeature
+} stopped cleartomark
+userdict begin /pagesave save def end mysetup concat colspRefresh : 1.000 1.000 1.000 sco 0 0 2550 3300 rf ;
+%%EndPageSetup
+
+: 0 0 2454 3191 rc pagesave restore
+Pscript_Win_Driver_Incr begin
+%%BeginResource: file Pscript_Win_Graphics 2.0 0
+/SavedCTM null |/CTMsave{/SavedCTM SavedCTM currentmatrix |}b/CTMrestore{
+SavedCTM setmatrix}b/mp null |/ADO_mxRot null |/GDIHMatrix null |
+/GDIHPatternDict 22 dict | GDIHPatternDict `/PatternType 1 |/PaintType 2 |
+/Reps L2?{1}{5}? |/XStep 8 Reps mul |/YStep XStep |/BBox[0 0 XStep YStep]|
+/TilingType 1 |/PaintProc{` 1 Lw[]0 setdash PaintData , exec E}b/FGnd null |
+/BGnd null |/HS_Horizontal{horiz}b/HS_Vertical{vert}b/HS_FDiagonal{fdiag}b
+/HS_BDiagonal{biag}b/HS_Cross{horiz vert}b/HS_DiagCross{fdiag biag}b/MaxXYStep
+XStep YStep gt{XStep}{YStep}? |/horiz{Reps{0 4 M XStep 0 - 0 8 +}repeat 0 -8
+Reps mul + K}b/vert{Reps{4 0 M 0 YStep - 8 0 +}repeat 0 -8 Reps mul + K}b/biag
+{Reps{0 0 M MaxXYStep @ - 0 YStep neg M MaxXYStep @ - 0 8 +}repeat 0 -8 Reps
+mul + 0 YStep M 8 8 - K}b/fdiag{Reps{0 0 M MaxXYStep @ neg - 0 YStep M
+MaxXYStep @ neg - 0 8 +}repeat 0 -8 Reps mul + MaxXYStep @ M 8 -8 - K}b E
+/makehatch{GDIHPatternDict/PaintData 3 -1 $ put CTMsave GDIHMatrix setmatrix
+GDIHPatternDict matrix mp CTMrestore ~ U ~ 2 ^ put}b/h0{/h0/HS_Horizontal
+makehatch}b/h1{/h1/HS_Vertical makehatch}b/h2{/h2/HS_FDiagonal makehatch}b/h3{
+/h3/HS_BDiagonal makehatch}b/h4{/h4/HS_Cross makehatch}b/h5{/h5/HS_DiagCross
+makehatch}b/GDIBWPatternDict 17 dict @ `/PatternType 1 |/PaintType L2?{1}{2}?
+|/RepsV L2?{1}{6}? |/RepsH L2?{1}{5}? |/BBox[0 0 RepsH 1]|/TilingType 1 |
+/XStep 1 |/YStep 1 |/Height 8 RepsV mul |/Width 8 |/mx[Width 0 0 Height neg 0
+Height]|/FGnd null |/BGnd null |/SetBGndFGnd L2?{{BGnd null ne{BGnd aload !
+sgco BBox aload ! 2 ^ sub ~ 3 ^ sub ~ rf}if FGnd null ne{FGnd aload ! sgco}if}
+}{{}}? b/PaintProc{` SetBGndFGnd RepsH{Width Height F mx PaintData imagemask
+Width 0 +}repeat E}b E |/GDIBWPatternMx null |/pfprep{save 4 1 $
+/PatternOfTheDay 4 1 $ GDIBWPatternDict `/PaintData ~ |/BGnd ~ |/FGnd ~ | E
+CTMsave GDIBWPatternMx setmatrix GDIBWPatternDict matrix mp CTMrestore ~ !}b
+/hrf null |/prf{pfprep ~ 6 1 $ 5 hrf restore}b/GraphInit{GDIHMatrix null eq{
+/SavedCTM matrix | : ADO_mxRot concat 0 0 snap + : 0.48 @ GDIHPatternDict `
+YStep mul ~ XStep mul ~ dsnap YStep V ~ XStep V ~ E +S/GDIHMatrix matrix
+currentmatrix readonly | ; : 0.24 -0.24 +S GDIBWPatternDict ` Width Height E
+dsnap +S/GDIBWPatternMx matrix currentmatrix readonly | ; ;}if}b/cirp{360 0 An
+C}b/ellp{CTMsave + +S 0.5 0 M 0 0 0.5 360 0 An C CTMrestore}b/rrp{/rad ~ |/y2
+~ |/x2 ~ |/y1 ~ |/x1 ~ | x2 x1 add 2 V y1 M x1 y1 x1 y2 rad arct x1 y2 x2 y2
+rad arct x2 y2 x2 y1 rad arct x2 y1 x1 y1 rad arct C}b/RRp{CTMsave + +S/dyS ~
+|/dxS ~ | dxS 2 V 0 M 0 0 0 dyS 0.5 arct 0 dyS dxS dyS 0.5 arct dxS dyS dxS 0
+0.5 arct dxS 0 0 0 0.5 arct C CTMrestore}b
+%%EndResource
+
+%%BeginResource: file Pscript_Win_Graphics_L1 2.0 0
+L2? not g{/arct{arcto ! ! ! !}b/GDIpattfill{@ ` BGnd null ne PaintType 2 eq
+and{: BGnd aload ! sgco fEOFill{O}{L}? ; FGnd aload ! U/fGray 2 ^ put{2}{4}?
+-1 $}if E @ patterncalc : 4 ^/PaintType get 2 eq{fGray{6 -1 $ sg}{8 -3 $ sco}?
+}if fEOFill{eoclip}{clip}? N patternfill ; N}b/hrf{/fGray 1 ^ 6 eq | -4 $ N rp
+C/fEOFill F | GDIpattfill}b/hfMain{/fEOFill ~ |/fGray ~ | GDIpattfill}b/hf{T
+hfMain}b/hfW{F hfMain}b/hs{currentpoint strokepath M hfW}b/pfMain{/fEOFill ~ |
+pfprep GDIpattfill restore N}b/pf{T pfMain}b/pfW{F pfMain}b/ps{currentpoint
+strokepath M pfW}b/mpstr 1 string |/mp{~ @ length 12 add dict copy `
+/PatternCTM matrix currentmatrix |/PatternMatrix ~ |/PatWidth XStep mpstr
+length mul |/PatHeight YStep |/FontType 3 |/Encoding 256 array | 3 string 0 1
+255{Encoding ~ @ 3 ^ cvs cvn put}for !/FontMatrix matrix |/FontBBox BBox |
+/BuildChar{! @ ` XStep 0 FontBBox aload ! setcachedevice/PaintProc , E : exec
+;}b & E ~ @ 3 -1 $ definefont}b/patterncalc{` : PatternCTM setmatrix
+PatternMatrix concat BBox aload ! ! ! + pathbbox ; PatHeight V ceiling 4 1 $
+PatWidth V ceiling 4 1 $ PatHeight V floor 4 1 $ PatWidth V floor 4 1 $ 2 ^
+sub cvi abs ~ 3 ^ sub cvi abs ~ 4 2 $ PatHeight mul ~ PatWidth mul ~ E}b
+/patternfill{5 -1 $ @ ` Ji PatternCTM setmatrix PatternMatrix concat 0 2 ^ 2 ^
+M 0 1 mpstr length 1 sub{1 ^ mpstr 3 1 $ put}for ! 2 ^{currentpoint 5 ^{mpstr
+S}repeat YStep add M}repeat ! ! ! ! E}b}e
+%%EndResource
+
+%%BeginResource: file Pscript_Win_Graphics_L2 2.0 0
+L2? g{/mp/makepattern , |/hrf{6 eq setAorABC setpattern rectfill}b/hf{
+setAorABC setpattern O}b/hfW{setAorABC setpattern L}b/hs{setAorABC setpattern
+K}b/pf{pfprep setpattern O restore N}b/pfW{pfprep setpattern L restore N}b/ps{
+pfprep setpattern K restore N}b}e
+%%EndResource
+
+end reinitialize
+userdict begin /pagesave save def end mysetup concat colspRefresh
+: 0 0 0 sco 1 Lc 1 Lj solid 0 0 2454 3191 rc
+1989 1646 N M 0 -419 - 1 Lw solid 0 0 0 sco K ;
+N 1968.500 1645.500 19.500 88.603 -1.397 An
+1 Lw 1 Lc 1 Lj 0 0 0 sco K : 0 0 2454 3191 rc
+1931 1666 N M 38 0 - 0 0 0 sco K ;
+N 1930.500 1685.500 19.500 -88.531 175.601 An
+0 0 0 sco K : 0 0 2454 3191 rc
+1911 2275 N M 0 -589 - 0 0 0 sco K ; : 1818 1632 636 23 rc : 1.000 1.000 1.000 sco 1872 1632 156 23 rf ; pagesave restore
+Pscript_Win_Driver_Incr begin
+%%BeginResource: file Pscript_Win_Encoding 2.0 0
+/bullets{{/bullet}repeat}b/ANSIEncoding[/grave/acute/circumflex/tilde/macron
+/breve/dotaccent/dieresis/ring/cedilla/hungarumlaut/ogonek/caron/dotlessi 18
+bullets StandardEncoding 32 95 getinterval aload ! 3 bullets/quotesinglbase
+/florin/quotedblbase/ellipsis/dagger/daggerdbl/circumflex/perthousand/Scaron
+/guilsinglleft/OE 4 bullets/quoteleft/quoteright/quotedblleft/quotedblright
+/bullet/endash/emdash/tilde/trademark/scaron/guilsinglright/oe 2 bullets
+/Ydieresis/space/exclamdown/cent/sterling/currency/yen/brokenbar/section
+/dieresis/copyright/ordfeminine/guillemotleft/logicalnot/hyphen/registered
+/macron/degree/plusminus/twosuperior/threesuperior/acute/mu/paragraph
+/periodcentered/cedilla/onesuperior/ordmasculine/guillemotright/onequarter
+/onehalf/threequarters/questiondown/Agrave/Aacute/Acircumflex/Atilde/Adieresis
+/Aring/AE/Ccedilla/Egrave/Eacute/Ecircumflex/Edieresis/Igrave/Iacute
+/Icircumflex/Idieresis/Eth/Ntilde/Ograve/Oacute/Ocircumflex/Otilde/Odieresis
+/multiply/Oslash/Ugrave/Uacute/Ucircumflex/Udieresis/Yacute/Thorn/germandbls
+/agrave/aacute/acircumflex/atilde/adieresis/aring/ae/ccedilla/egrave/eacute
+/ecircumflex/edieresis/igrave/iacute/icircumflex/idieresis/eth/ntilde/ograve
+/oacute/ocircumflex/otilde/odieresis/divide/oslash/ugrave/uacute/ucircumflex
+/udieresis/yacute/thorn/ydieresis]| ANSIEncoding @ 39/quotesingle put 96/grave
+put/ANSIEncodingOld ANSIEncoding 256 array copy | ANSIEncodingOld @[138 153
+154 169 172 174 177 178 179 181 185 188 189 190 208 215 221 222 240 247 253
+254]{/bullet put @}forall 166/bar put 176/ring put
+%%EndResource
+
+%%BeginResource: file Pscript_Win_Text 2.0 0
+/TextInit{TextInitialised? not{/Pscript_Windows_Font & |/TextInitialised? T |
+/fM[1 0 0 -1 0 0]|/mFM matrix |/iMat[1 0 0.212557 neg 1 0 0]|}if}b/xUP null |
+/yUP null |/uW null |/xSP null |/ySP null |/sW null |/copyfont{1 ^ length add
+dict `{1 ^/FID ne{|}{! !}?}forall & E}b/rF{3 copyfont @ `/Encoding
+ANSIEncoding &/CharStrings known{CharStrings/Eth known not{! ANSIEncodingOld}
+if}if | E}b/mF{findfont ~{@/Encoding get @ StandardEncoding eq{! T}{{
+ISOLatin1Encoding}stopped{! F}{eq}?{T}{@ ` T 32 1 127{Encoding 1 ^ get
+StandardEncoding 3 -1 $ get eq and}for E}?}?}{F}?{rF}{3 copyfont}? `
+/OrigFontType ~ |/OrigFontName ~ | & E 2 ^ ~ definefont fM 5 4 -1 $ put fM 4 0
+put fM makefont Pscript_Windows_Font 3 1 $ put}b/xF{scalefont
+Pscript_Windows_Font 3 1 $ put}b/xMF{mFM astore makefont Pscript_Windows_Font
+3 1 $ put}b/xF2/scalefont , |/xMF2{mFM astore makefont}b/sLT{: Lw -M
+currentpoint snap M 0 - 0 Lc K ;}b/sSU{N/uW ~ |/yUP ~ |/xUP ~ |}b/sU{xUP yUP
+uW sLT}b/sST{N/sW ~ |/ySP ~ |/xSP ~ |}b/sT{xSP ySP sW sLT}b/sR{: + R 0 0 M}b
+/sRxy{: matrix astore concat 0 0 M}b/eR/; , |
+%%EndResource
+
+end reinitialize
+userdict begin /pagesave save def end mysetup concat colspRefresh
+: 0 0 0 sco 1 Lw 1 Lc 1 Lj 1818 1632 636 23 rc 0 0 0 sco %%IncludeFont: Helvetica
+(F0) cvn
+0.950
+ (Helvetica) cvn /Type1
+T
+(Helvetica) cvn
+mF
+(F0_20) cvn
+F0
+20
+xF
+F0_20
+Ji
+1872 1632 M
+-0.012 0 (product = product)A
+;
+1989 1304 N M 7 34 - -15 0 - 8 -34 - C : 0 0 0 sco O ; 1 Lw 1 Lc 1 Lj 0 0 0 sco K : 0 0 2454 3191 rc
+2135 1050 N M -906 0 - 0 0 0 sco K ; : 1408 1060 1026 23 rc : 1.000 1.000 1.000 sco 1462 1060 164 23 rf ; 0 0 0 sco F0_20
+Ji
+1462 1060 M
+0.002 0 (product = program)A
+;
+1742 1050 N M -33 7 - 0 -15 - 33 8 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc
+2093 1250 N M -1848 0 - 0 0 0 sco K ; : 1014 1260 1026 23 rc : 1.000 1.000 1.000 sco 1068 1260 164 23 rf ; 0 0 0 sco F0_20
+Ji
+1068 1260 M
+0.002 0 (product = program)A
+;
+1742 1250 N M -33 7 - 0 -15 - 33 8 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc
+1798 1151 N M -946 0 - 0 0 0 sco K ; : 1204 1161 1026 23 rc : 1.000 1.000 1.000 sco 1258 1161 156 23 rf ; 0 0 0 sco F0_20
+Ji
+1258 1161 M
+-0.012 0 (product = product)A
+;
+1742 1151 N M -33 7 - 0 -15 - 33 8 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc
+717 1719 N M 0 689 - 0 0 0 sco K ;
+N 736.500 1718.500 19.500 -88.531 175.601 An
+0 0 0 sco K : 0 0 2454 3191 rc
+864 1699 N M -127 0 - 0 0 0 sco K ;
+N 863.500 1678.500 19.500 88.603 -1.397 An
+0 0 0 sco K : 0 0 2454 3191 rc
+884 1464 N M 0 215 - 0 0 0 sco K ; : 681 1687 918 23 rc : 1.000 1.000 1.000 sco 735 1687 130 23 rf ; 0 0 0 sco F0_20
+Ji
+735 1687 M
+-0.115 0 (userid = userid)A
+;
+717 2221 N M -8 -33 - 15 0 - -7 33 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc
+649 1684 N M 0 737 - 0 0 0 sco K ;
+N 628.500 1683.500 19.500 1.397 -91.469 An
+0 0 0 sco K : 0 0 2454 3191 rc
+334 1664 N M 295 0 - 0 0 0 sco K ; : 513 1635 918 23 rc : 1.000 1.000 1.000 sco 567 1635 130 23 rf ; 0 0 0 sco F0_20
+Ji
+567 1635 M
+-0.115 0 (userid = userid)A
+;
+649 2221 N M -8 -33 - 15 0 - -7 33 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc
+837 1882 N M 0 378 - 0 0 0 sco K ;
+N 856.500 1881.500 19.500 -88.531 175.601 An
+0 0 0 sco K : 0 0 2454 3191 rc
+1121 1862 N M -264 0 - 0 0 0 sco K ; : 0 0 2454 3191 rc
+1467 1862 N M -346 0 - 0 0 0 sco K ; : 869 1850 756 23 rc : 1.000 1.000 1.000 sco 923 1850 113 23 rf ; 0 0 0 sco F0_20
+Ji
+923 1850 M
+-0.078 0 (userid = who)A
+;
+837 2221 N M -8 -33 - 15 0 - -7 33 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc
+962 2267 N M -94 0 - 0 0 0 sco K ;
+N 961.500 2246.500 19.500 88.603 -1.397 An
+0 0 0 sco K : 0 0 2454 3191 rc
+982 2105 N M 0 142 - 0 0 0 sco K ;
+N 1001.500 2104.500 19.500 -88.531 175.601 An
+0 0 0 sco K : 0 0 2454 3191 rc
+1347 2085 N M -345 0 - 0 0 0 sco K ; : 872 2164 756 23 rc : 1.000 1.000 1.000 sco 926 2164 113 23 rf ; 0 0 0 sco F0_20
+Ji
+926 2164 M
+-0.078 0 (userid = who)A
+;
+872 2267 N M 33 -8 - 0 15 - -33 -7 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc
+978 2437 N M -158 0 - 0 0 0 sco K ;
+N 977.500 2416.500 19.500 88.603 -1.397 An
+0 0 0 sco K : 0 0 2454 3191 rc
+998 2345 N M 0 72 - 0 0 0 sco K ;
+N 1017.500 2344.500 19.500 -88.531 175.601 An
+0 0 0 sco K : 0 0 2454 3191 rc
+1212 2325 N M -194 0 - 0 0 0 sco K ; : 888 2369 756 23 rc : 1.000 1.000 1.000 sco 942 2369 113 23 rf ; 0 0 0 sco F0_20
+Ji
+942 2369 M
+-0.078 0 (userid = who)A
+;
+872 2437 N M 33 -7 - 0 15 - -33 -8 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc
+829 2672 N M 0 -152 - 0 0 0 sco K ;
+N 848.500 2671.500 19.500 178.531 85.815 An
+0 0 0 sco K : 0 0 2454 3191 rc
+1194 2692 N M -345 0 - 0 0 0 sco K ; : 700 2697 1242 23 rc : 1.000 1.000 1.000 sco 754 2697 184 23 rf ; 0 0 0 sco F0_20
+Ji
+754 2697 M
+-0.104 0 (userid = submitter_id)A
+;
+829 2620 N M 8 33 - -15 0 - 7 -33 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc
+570 2708 N M 0 -156 - 0 0 0 sco K ;
+N 589.500 2707.500 19.500 178.531 85.815 An
+0 0 0 sco K : 0 0 2454 3191 rc
+773 2728 N M -183 0 - 0 0 0 sco K ;
+N 772.500 2747.500 19.500 1.397 -91.469 An
+0 0 0 sco K : 0 0 2454 3191 rc
+793 2836 N M 0 -88 - 0 0 0 sco K ; : 572 2716 756 23 rc : 1.000 1.000 1.000 sco 626 2716 113 23 rf ; 0 0 0 sco F0_20
+Ji
+626 2716 M
+-0.078 0 (userid = who)A
+;
+570 2620 N M 8 33 - -15 0 - 7 -33 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc
+1554 2379 N M 690 0 - 0 0 0 sco K ;
+N 1553.500 2358.500 19.500 178.531 85.815 An
+0 0 0 sco K : 0 0 2454 3191 rc
+1534 2032 N M 0 327 - 0 0 0 sco K ; : 1427 2384 918 23 rc : 1.000 1.000 1.000 sco 1481 2384 140 23 rf ; 0 0 0 sco F0_20
+Ji
+1481 2384 M
+-0.192 0 (bug_id = bug_id)A
+;
+1826 2379 N M -33 8 - 0 -15 - 33 7 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc
+1306 2476 N M 620 0 - 0 0 0 sco K ;
+N 1305.500 2455.500 19.500 178.531 85.815 An
+0 0 0 sco K : 0 0 2454 3191 rc
+1286 2224 N M 0 232 - 0 0 0 sco K ; : 1179 2481 918 23 rc : 1.000 1.000 1.000 sco 1233 2481 140 23 rf ; 0 0 0 sco F0_20
+Ji
+1233 2481 M
+-0.192 0 (bug_id = bug_id)A
+;
+1826 2476 N M -33 8 - 0 -15 - 33 7 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc
+1693 2787 N M 140 0 - 0 0 0 sco K ;
+N 1692.500 2766.500 19.500 178.531 85.815 An
+0 0 0 sco K : 0 0 2454 3191 rc
+1673 2652 N M 0 115 - 0 0 0 sco K ;
+N 1652.500 2651.500 19.500 1.397 -91.469 An
+0 0 0 sco K : 0 0 2454 3191 rc
+1487 2632 N M 166 0 - 0 0 0 sco K ; : 1549 2697 905 23 rc : 1.000 1.000 1.000 sco 1603 2697 140 23 rf ; 0 0 0 sco F0_20
+Ji
+1603 2697 M
+-0.192 0 (bug_id = bug_id)A
+;
+1826 2787 N M -33 7 - 0 -15 - 33 8 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc
+1953 2954 N M -880 0 - 0 0 0 sco K ; : 1321 2964 918 23 rc : 1.000 1.000 1.000 sco 1375 2964 140 23 rf ; 0 0 0 sco F0_20
+Ji
+1375 2964 M
+-0.192 0 (bug_id = bug_id)A
+;
+1826 2954 N M -33 8 - 0 -15 - 33 7 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc
+326 2275 N M 314 0 - 0 0 0 sco K ;
+N 325.500 2254.500 19.500 178.531 85.815 An
+0 0 0 sco K : 0 0 2454 3191 rc
+306 1933 N M 0 322 - 0 0 0 sco K ; : 204 2280 918 23 rc : 1.000 1.000 1.000 sco 258 2280 130 23 rf ; 0 0 0 sco F0_20
+Ji
+258 2280 M
+-0.115 0 (userid = userid)A
+;
+426 2275 N M -33 7 - -1 -15 - 34 8 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc
+224 2919 N M 0 -905 - 0 0 0 sco K ; : 107 2409 1026 23 rc : 1.000 1.000 1.000 sco 161 2409 126 23 rf ; 0 0 0 sco F0_20
+Ji
+161 2409 M
+-0.075 0 (fieldid = fieldid)A
+;
+224 2819 N M -7 -34 - 15 0 - -8 34 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc
+360 2910 N M 573 0 - 0 0 0 sco K ; : 555 2920 1026 23 rc : 1.000 1.000 1.000 sco 609 2920 126 23 rf ; 0 0 0 sco F0_20
+Ji
+609 2920 M
+-0.075 0 (fieldid = fieldid)A
+;
+542 2910 N M 34 -8 - 0 16 - -34 -8 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc
+2070 2339 N M 0 -475 - 0 0 0 sco K ; : 1946 2044 508 23 rc : 1.000 1.000 1.000 sco 2000 2044 140 23 rf ; 0 0 0 sco F0_20
+Ji
+2000 2044 M
+-0.192 0 (bug_id = bug_id)A
+;
+2070 2227 N M -7 -33 - 15 0 - -8 33 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc
+1726 2297 N M 372 0 - 0 0 0 sco K ;
+N 1725.500 2276.500 19.500 178.531 85.815 An
+0 0 0 sco K : 0 0 2454 3191 rc
+1706 1859 N M 0 418 - 0 0 0 sco K ;
+N 1685.500 1858.500 19.500 1.397 -91.469 An
+0 0 0 sco K : 0 0 2454 3191 rc
+1537 1839 N M 149 0 - 0 0 0 sco K ; : 1582 2056 872 23 rc : 1.000 1.000 1.000 sco 1636 2056 140 23 rf ; 0 0 0 sco F0_20
+Ji
+1636 2056 M
+-0.192 0 (bug_id = bug_id)A
+;
+1826 2297 N M -33 8 - 0 -15 - 33 7 - C : 0 0 0 sco O ; 0 0 0 sco K
+174 1137 N M 416 206 rr : 1.000 1.000 1.000 sco O ; 0 Lc 0 Lj 0 0 0 sco K : 235 1142 345 32 rc 0 0 0 sco (F0_27) cvn
+F0
+27
+xF
+F0_27
+Ji
+308 1142 M
+0.093 0 (components)A
+; : 0 0 2454 3191 rc
+174 1177 N M 416 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 184 1180 196 32 rc 0 0 0 sco F0_27
+Ji
+184 1180 M
+-0.106 0 (value)A
+; : 400 1180 190 32 rc 0 0 0 sco F0_27
+Ji
+400 1180 M
+0.058 0 (tinytext)A
+; : 184 1213 196 32 rc 0 0 0 sco F0_27
+Ji
+184 1213 M
+-0.074 0 (program)A
+; : 400 1213 190 32 rc 0 0 0 sco F0_27
+Ji
+400 1213 M
+-0.001 0 (VARCHAR\(64\))A
+; : 184 1246 196 32 rc 0 0 0 sco F0_27
+Ji
+184 1246 M
+-0.002 0 (initialowner)A
+; : 400 1246 190 32 rc 0 0 0 sco F0_27
+Ji
+400 1246 M
+0.058 0 (tinytext)A
+; : 184 1279 196 32 rc 0 0 0 sco F0_27
+Ji
+184 1279 M
+0.151 0 (initialqacontact)A
+; : 400 1279 190 32 rc 0 0 0 sco F0_27
+Ji
+400 1279 M
+0.058 0 (tinytext)A
+; : 184 1312 196 29 rc 0 0 0 sco F0_27
+Ji
+184 1312 M
+0.132 0 (description)A
+; : 400 1312 190 29 rc 0 0 0 sco F0_27
+Ji
+400 1312 M
+-0.154 0 (mediumtext)A
+;
+643 1054 N M 320 143 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 665 1059 288 32 rc 0 0 0 sco F0_27
+Ji
+738 1059 M
+0.097 0 (milestones)A
+; : 0 0 2454 3191 rc
+643 1094 N M 320 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 653 1097 100 32 rc 0 0 0 sco F0_27
+Ji
+0 29 1 sSU
+653 1097 M
+-0.106 0 (value)A
+-64 sU
+; : 773 1097 190 32 rc 0 0 0 sco F0_27
+Ji
+0 29 1 sSU
+773 1097 M
+-0.001 0 (VARCHAR\(20\))A
+-180 sU
+; : 653 1130 100 32 rc 0 0 0 sco F0_27
+Ji
+653 1130 M
+0.136 0 (product)A
+; : 773 1130 190 32 rc 0 0 0 sco F0_27
+Ji
+773 1130 M
+-0.001 0 (VARCHAR\(64\))A
+; : 653 1163 100 31 rc 0 0 0 sco F0_27
+Ji
+653 1163 M
+0.283 0 (sortkey)A
+; : 773 1163 190 31 rc 0 0 0 sco F0_27
+Ji
+773 1163 M
+0.046 0 (smallint\(6\))A
+;
+1742 1001 N M 432 303 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 1832 1006 332 32 rc 0 0 0 sco F0_27
+Ji
+1905 1006 M
+0.182 0 (products)A
+; : 0 0 2454 3191 rc
+1742 1042 N M 432 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 1752 1044 212 32 rc 0 0 0 sco F0_27
+Ji
+0 29 1 sSU
+1752 1044 M
+0.136 0 (product)A
+-91 sU
+; : 1984 1044 190 32 rc 0 0 0 sco F0_27
+Ji
+0 29 1 sSU
+1984 1044 M
+-0.001 0 (VARCHAR\(64\))A
+-180 sU
+; : 1752 1077 212 32 rc 0 0 0 sco F0_27
+Ji
+1752 1077 M
+0.132 0 (description)A
+; : 1984 1077 190 32 rc 0 0 0 sco F0_27
+Ji
+1984 1077 M
+-0.154 0 (mediumtext)A
+; : 1752 1110 212 32 rc 0 0 0 sco F0_27
+Ji
+1752 1110 M
+0.039 0 (milestoneurl)A
+; : 1984 1110 190 32 rc 0 0 0 sco F0_27
+Ji
+1984 1110 M
+0.058 0 (tinytext)A
+; : 1752 1143 212 32 rc 0 0 0 sco F0_27
+Ji
+1752 1143 M
+-0.048 0 (disallownew)A
+; : 1984 1143 190 32 rc 0 0 0 sco F0_27
+Ji
+1984 1143 M
+0.148 0 (tinyint\(4\))A
+; : 1752 1176 212 32 rc 0 0 0 sco F0_27
+Ji
+1752 1176 M
+0.078 0 (votesperuser)A
+; : 1984 1176 190 32 rc 0 0 0 sco F0_27
+Ji
+1984 1176 M
+0.046 0 (smallint\(6\))A
+; : 1752 1209 212 32 rc 0 0 0 sco F0_27
+Ji
+1752 1209 M
+-0.113 0 (maxvotesperbug)A
+; : 1984 1209 190 32 rc 0 0 0 sco F0_27
+Ji
+1984 1209 M
+0.046 0 (smallint\(6\))A
+; : 1752 1242 212 32 rc 0 0 0 sco F0_27
+Ji
+1752 1242 M
+0.032 0 (votestoconfirm)A
+; : 1984 1242 190 32 rc 0 0 0 sco F0_27
+Ji
+1984 1242 M
+0.046 0 (smallint\(6\))A
+; : 1752 1275 212 27 rc 0 0 0 sco F0_27
+Ji
+1752 1275 M
+0.026 0 (defaultmilestone)A
+; : 1984 1275 190 27 rc 0 0 0 sco F0_27
+Ji
+1984 1275 M
+-0.001 0 (VARCHAR\(20\))A
+;
+1052 964 N M 328 116 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 1092 969 278 32 rc 0 0 0 sco F0_27
+Ji
+1165 969 M
+0.060 0 (versions)A
+; : 0 0 2454 3191 rc
+1052 1004 N M 328 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 1062 1007 108 32 rc 0 0 0 sco F0_27
+Ji
+1062 1007 M
+-0.106 0 (value)A
+; : 1190 1007 190 32 rc 0 0 0 sco F0_27
+Ji
+1190 1007 M
+0.058 0 (tinytext)A
+; : 1062 1040 108 32 rc 0 0 0 sco F0_27
+Ji
+1062 1040 M
+-0.074 0 (program)A
+; : 1190 1040 190 32 rc 0 0 0 sco F0_27
+Ji
+1190 1040 M
+-0.001 0 (VARCHAR\(64\))A
+;
+1282 1466 N M 382 207 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 1358 1471 296 32 rc 0 0 0 sco F0_27
+Ji
+1431 1471 M
+0.077 0 (groups)A
+; : 0 0 2454 3191 rc
+1282 1506 N M 382 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 1292 1509 147 32 rc 0 0 0 sco F0_27
+Ji
+1292 1509 M
+0.163 0 (bit)A
+; : 1459 1509 205 32 rc 0 0 0 sco F0_27
+Ji
+1459 1509 M
+0.046 0 (bigint\(20\))A
+; : 1292 1542 147 32 rc 0 0 0 sco F0_27
+Ji
+1292 1542 M
+-0.132 0 (name)A
+; : 1459 1542 205 32 rc 0 0 0 sco F0_27
+Ji
+1459 1542 M
+-0.002 0 (VARCHAR\(255\))A
+; : 1292 1575 147 32 rc 0 0 0 sco F0_27
+Ji
+1292 1575 M
+0.132 0 (description)A
+; : 1459 1575 205 32 rc 0 0 0 sco F0_27
+Ji
+1459 1575 M
+-0.131 0 (text)A
+; : 1292 1608 147 32 rc 0 0 0 sco F0_27
+Ji
+1292 1608 M
+0.043 0 (isbuggroup)A
+; : 1459 1608 205 32 rc 0 0 0 sco F0_27
+Ji
+1459 1608 M
+0.148 0 (tinyint\(4\))A
+; : 1292 1641 147 29 rc 0 0 0 sco F0_27
+Ji
+1292 1641 M
+-0.105 0 (userregexp)A
+; : 1459 1641 205 29 rc 0 0 0 sco F0_27
+Ji
+1459 1641 M
+0.058 0 (tinytext)A
+;
+671 1361 N M 426 207 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 736 1366 351 32 rc 0 0 0 sco F0_27
+Ji
+809 1366 M
+0.121 0 (logincookies)A
+; : 0 0 2454 3191 rc
+671 1401 N M 426 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 681 1404 191 32 rc 0 0 0 sco F0_27
+Ji
+0 29 1 sSU
+681 1404 M
+0.162 0 (cookie)A
+-79 sU
+; : 892 1404 205 32 rc 0 0 0 sco F0_27
+Ji
+0 29 1 sSU
+892 1404 M
+-0.043 0 (mediumint\(9\))A
+-157 sU
+; : 681 1437 191 32 rc 0 0 0 sco F0_27
+Ji
+681 1437 M
+0.080 0 (userid)A
+; : 892 1437 205 32 rc 0 0 0 sco F0_27
+Ji
+892 1437 M
+-0.043 0 (mediumint\(9\))A
+; : 681 1470 191 32 rc 0 0 0 sco F0_27
+Ji
+681 1470 M
+0.151 0 (cryptpassword)A
+; : 892 1470 205 32 rc 0 0 0 sco F0_27
+Ji
+892 1470 M
+-0.001 0 (VARCHAR\(64\))A
+; : 681 1503 191 32 rc 0 0 0 sco F0_27
+Ji
+681 1503 M
+0.055 0 (hostname)A
+; : 892 1503 205 32 rc 0 0 0 sco F0_27
+Ji
+892 1503 M
+-0.002 0 (VARCHAR\(128\))A
+; : 681 1536 191 29 rc 0 0 0 sco F0_27
+Ji
+681 1536 M
+0.182 0 (lastused)A
+; : 892 1536 205 29 rc 0 0 0 sco F0_27
+Ji
+892 1536 M
+0.036 0 (timestamp\(14\))A
+;
+136 1493 N M 382 207 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 168 1498 340 32 rc 0 0 0 sco F0_27
+Ji
+241 1498 M
+-0.006 0 (namedqueries)A
+; : 0 0 2454 3191 rc
+136 1533 N M 382 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 146 1536 162 32 rc 0 0 0 sco F0_27
+Ji
+0 29 1 sSU
+146 1536 M
+0.080 0 (userid)A
+-74 sU
+; : 328 1536 190 32 rc 0 0 0 sco F0_27
+Ji
+0 29 1 sSU
+328 1536 M
+-0.043 0 (mediumint\(9\))A
+-157 sU
+; : 146 1569 162 32 rc 0 0 0 sco F0_27
+Ji
+0 29 1 sSU
+146 1569 M
+-0.132 0 (name)A
+-67 sU
+; : 328 1569 190 32 rc 0 0 0 sco F0_27
+Ji
+0 29 1 sSU
+328 1569 M
+-0.001 0 (VARCHAR\(64\))A
+-180 sU
+; : 146 1602 162 32 rc 0 0 0 sco F0_27
+Ji
+146 1602 M
+-0.042 0 (watchfordiffs)A
+; : 328 1602 190 32 rc 0 0 0 sco F0_27
+Ji
+328 1602 M
+0.148 0 (tinyint\(4\))A
+; : 146 1635 162 32 rc 0 0 0 sco F0_27
+Ji
+146 1635 M
+0.038 0 (linkinfooter)A
+; : 328 1635 190 32 rc 0 0 0 sco F0_27
+Ji
+328 1635 M
+0.148 0 (tinyint\(4\))A
+; : 146 1668 162 29 rc 0 0 0 sco F0_27
+Ji
+146 1668 M
+0.095 0 (query)A
+; : 328 1668 190 29 rc 0 0 0 sco F0_27
+Ji
+328 1668 M
+-0.154 0 (mediumtext)A
+;
+1165 2554 N M 378 335 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 1206 2559 327 32 rc 0 0 0 sco F0_27
+Ji
+1279 2559 M
+0.176 0 (attachments)A
+; : 0 0 2454 3191 rc
+1165 2595 N M 378 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 1175 2597 165 32 rc 0 0 0 sco F0_27
+Ji
+0 29 1 sSU
+1175 2597 M
+0.159 0 (attach_id)A
+-111 sU
+; : 1360 2597 183 32 rc 0 0 0 sco F0_27
+Ji
+0 29 1 sSU
+1360 2597 M
+-0.043 0 (mediumint\(9\))A
+-157 sU
+; : 1175 2630 165 32 rc 0 0 0 sco F0_27
+Ji
+1175 2630 M
+-0.009 0 (bug_id)A
+; : 1360 2630 183 32 rc 0 0 0 sco F0_27
+Ji
+1360 2630 M
+-0.043 0 (mediumint\(9\))A
+; : 1175 2663 165 32 rc 0 0 0 sco F0_27
+Ji
+1175 2663 M
+0.177 0 (creation_ts)A
+; : 1360 2663 183 32 rc 0 0 0 sco F0_27
+Ji
+1360 2663 M
+0.036 0 (timestamp\(14\))A
+; : 1175 2696 165 32 rc 0 0 0 sco F0_27
+Ji
+1175 2696 M
+0.132 0 (description)A
+; : 1360 2696 183 32 rc 0 0 0 sco F0_27
+Ji
+1360 2696 M
+-0.154 0 (mediumtext)A
+; : 1175 2729 165 32 rc 0 0 0 sco F0_27
+Ji
+1175 2729 M
+-0.002 0 (mimetype)A
+; : 1360 2729 183 32 rc 0 0 0 sco F0_27
+Ji
+1360 2729 M
+-0.154 0 (mediumtext)A
+; : 1175 2762 165 32 rc 0 0 0 sco F0_27
+Ji
+1175 2762 M
+0.209 0 (ispatch)A
+; : 1360 2762 183 32 rc 0 0 0 sco F0_27
+Ji
+1360 2762 M
+0.148 0 (tinyint\(4\))A
+; : 1175 2795 165 32 rc 0 0 0 sco F0_27
+Ji
+1175 2795 M
+-0.129 0 (filename)A
+; : 1360 2795 183 32 rc 0 0 0 sco F0_27
+Ji
+1360 2795 M
+-0.154 0 (mediumtext)A
+; : 1175 2828 165 32 rc 0 0 0 sco F0_27
+Ji
+1175 2828 M
+0.133 0 (thedata)A
+; : 1360 2828 183 32 rc 0 0 0 sco F0_27
+Ji
+1360 2828 M
+-0.007 0 (longblob)A
+; : 1175 2861 165 26 rc 0 0 0 sco F0_27
+Ji
+1175 2861 M
+0.080 0 (submitter_id)A
+; : 1360 2861 183 26 rc 0 0 0 sco F0_27
+Ji
+1360 2861 M
+-0.043 0 (mediumint\(9\))A
+;
+1826 2227 N M 456 815 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 1951 2232 321 32 rc 0 0 0 sco F0_27
+Ji
+2024 2232 M
+0.116 0 (bugs)A
+; : 0 0 2454 3191 rc
+1826 2268 N M 456 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 1836 2270 236 32 rc 0 0 0 sco F0_27
+Ji
+0 29 1 sSU
+1836 2270 M
+-0.009 0 (bug_id)A
+-81 sU
+; : 2092 2270 190 32 rc 0 0 0 sco F0_27
+Ji
+0 29 1 sSU
+2092 2270 M
+-0.043 0 (mediumint\(9\))A
+-157 sU
+; : 1836 2303 236 32 rc 0 0 0 sco F0_27
+Ji
+1836 2303 M
+0.118 0 (groupset)A
+; : 2092 2303 190 32 rc 0 0 0 sco F0_27
+Ji
+2092 2303 M
+0.046 0 (bigint\(20\))A
+; : 1836 2336 236 32 rc 0 0 0 sco F0_27
+Ji
+1836 2336 M
+0.129 0 (assigned_to)A
+; : 2092 2336 190 32 rc 0 0 0 sco F0_27
+Ji
+2092 2336 M
+-0.043 0 (mediumint\(9\))A
+; : 1836 2369 236 32 rc 0 0 0 sco F0_27
+Ji
+1836 2369 M
+-0.006 0 (bug_file_loc)A
+; : 2092 2369 190 32 rc 0 0 0 sco F0_27
+Ji
+2092 2369 M
+-0.131 0 (text)A
+; : 1836 2402 236 32 rc 0 0 0 sco F0_27
+Ji
+1836 2402 M
+0.078 0 (bug_severity)A
+; : 2092 2402 190 32 rc 0 0 0 sco F0_27
+Ji
+2092 2402 M
+-0.132 0 (enum)A
+; : 1836 2435 236 32 rc 0 0 0 sco F0_27
+Ji
+1836 2435 M
+0.192 0 (bug_status)A
+; : 2092 2435 190 32 rc 0 0 0 sco F0_27
+Ji
+2092 2435 M
+-0.132 0 (enum)A
+; : 1836 2468 236 32 rc 0 0 0 sco F0_27
+Ji
+1836 2468 M
+0.177 0 (creation_ts)A
+; : 2092 2468 190 32 rc 0 0 0 sco F0_27
+Ji
+2092 2468 M
+0.057 0 (datetime)A
+; : 1836 2501 236 32 rc 0 0 0 sco F0_27
+Ji
+1836 2501 M
+0.181 0 (delta_ts)A
+; : 2092 2501 190 32 rc 0 0 0 sco F0_27
+Ji
+2092 2501 M
+0.036 0 (timestamp\(14\))A
+; : 1836 2534 236 32 rc 0 0 0 sco F0_27
+Ji
+1836 2534 M
+0.194 0 (short_desc)A
+; : 2092 2534 190 32 rc 0 0 0 sco F0_27
+Ji
+2092 2534 M
+-0.154 0 (mediumtext)A
+; : 1836 2567 236 32 rc 0 0 0 sco F0_27
+Ji
+1836 2567 M
+0.244 0 (op_sys)A
+; : 2092 2567 190 32 rc 0 0 0 sco F0_27
+Ji
+2092 2567 M
+-0.132 0 (enum)A
+; : 1836 2600 236 32 rc 0 0 0 sco F0_27
+Ji
+1836 2600 M
+0.125 0 (priority)A
+; : 2092 2600 190 32 rc 0 0 0 sco F0_27
+Ji
+2092 2600 M
+-0.132 0 (enum)A
+; : 1836 2633 236 32 rc 0 0 0 sco F0_27
+Ji
+1836 2633 M
+0.136 0 (product)A
+; : 2092 2633 190 32 rc 0 0 0 sco F0_27
+Ji
+2092 2633 M
+-0.001 0 (VARCHAR\(64\))A
+; : 1836 2666 236 32 rc 0 0 0 sco F0_27
+Ji
+1836 2666 M
+-0.046 0 (rep_platform)A
+; : 2092 2666 190 32 rc 0 0 0 sco F0_27
+Ji
+2092 2666 M
+-0.132 0 (enum)A
+; : 1836 2699 236 32 rc 0 0 0 sco F0_27
+Ji
+1836 2699 M
+0.059 0 (reporter)A
+; : 2092 2699 190 32 rc 0 0 0 sco F0_27
+Ji
+2092 2699 M
+-0.043 0 (mediumint\(9\))A
+; : 1836 2732 236 32 rc 0 0 0 sco F0_27
+Ji
+1836 2732 M
+-0.003 0 (version)A
+; : 2092 2732 190 32 rc 0 0 0 sco F0_27
+Ji
+2092 2732 M
+-0.001 0 (VARCHAR\(16\))A
+; : 1836 2765 236 32 rc 0 0 0 sco F0_27
+Ji
+1836 2765 M
+0.048 0 (component)A
+; : 2092 2765 190 32 rc 0 0 0 sco F0_27
+Ji
+2092 2765 M
+-0.001 0 (VARCHAR\(50\))A
+; : 1836 2798 236 32 rc 0 0 0 sco F0_27
+Ji
+1836 2798 M
+0.096 0 (resolution)A
+; : 2092 2798 190 32 rc 0 0 0 sco F0_27
+Ji
+2092 2798 M
+-0.132 0 (enum)A
+; : 1836 2831 236 32 rc 0 0 0 sco F0_27
+Ji
+1836 2831 M
+0.089 0 (target_milestone)A
+; : 2092 2831 190 32 rc 0 0 0 sco F0_27
+Ji
+2092 2831 M
+-0.001 0 (VARCHAR\(20\))A
+; : 1836 2864 236 32 rc 0 0 0 sco F0_27
+Ji
+1836 2864 M
+0.192 0 (qa_contact)A
+; : 2092 2864 190 32 rc 0 0 0 sco F0_27
+Ji
+2092 2864 M
+-0.043 0 (mediumint\(9\))A
+; : 1836 2897 236 32 rc 0 0 0 sco F0_27
+Ji
+1836 2897 M
+0.111 0 (status_whiteboard)A
+; : 2092 2897 190 32 rc 0 0 0 sco F0_27
+Ji
+2092 2897 M
+-0.154 0 (mediumtext)A
+; : 1836 2930 236 32 rc 0 0 0 sco F0_27
+Ji
+1836 2930 M
+0.094 0 (votes)A
+; : 2092 2930 190 32 rc 0 0 0 sco F0_27
+Ji
+2092 2930 M
+-0.043 0 (mediumint\(9\))A
+; : 1836 2963 236 32 rc 0 0 0 sco F0_27
+Ji
+1836 2963 M
+0.122 0 (keywords)A
+; : 2092 2963 190 32 rc 0 0 0 sco F0_27
+Ji
+2092 2963 M
+-0.154 0 (mediumtext)A
+; : 1836 2996 236 32 rc 0 0 0 sco F0_27
+Ji
+1836 2996 M
+-0.005 0 (lastdiffed)A
+; : 2092 2996 190 32 rc 0 0 0 sco F0_27
+Ji
+2092 2996 M
+0.057 0 (datetime)A
+; : 1836 3029 236 11 rc 0 0 0 sco F0_27
+Ji
+1836 3029 M
+-0.080 0 (everconfirmed)A
+; : 2092 3029 190 11 rc 0 0 0 sco F0_27
+Ji
+2092 3029 M
+0.148 0 (tinyint\(4\))A
+;
+768 2778 N M 330 239 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 781 2783 307 32 rc 0 0 0 sco F0_27
+Ji
+854 2783 M
+0.149 0 (bugs_activity)A
+; : 0 0 2454 3191 rc
+768 2819 N M 330 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 778 2821 133 32 rc 0 0 0 sco F0_27
+Ji
+778 2821 M
+-0.009 0 (bug_id)A
+; : 931 2821 167 32 rc 0 0 0 sco F0_27
+Ji
+931 2821 M
+-0.043 0 (mediumint\(9\))A
+; : 778 2854 133 32 rc 0 0 0 sco F0_27
+Ji
+778 2854 M
+-0.173 0 (who)A
+; : 931 2854 167 32 rc 0 0 0 sco F0_27
+Ji
+931 2854 M
+-0.043 0 (mediumint\(9\))A
+; : 778 2887 133 32 rc 0 0 0 sco F0_27
+Ji
+778 2887 M
+-0.072 0 (bug_when)A
+; : 931 2887 167 32 rc 0 0 0 sco F0_27
+Ji
+931 2887 M
+0.057 0 (datetime)A
+; : 778 2920 133 32 rc 0 0 0 sco F0_27
+Ji
+778 2920 M
+-0.075 0 (fieldid)A
+; : 931 2920 167 32 rc 0 0 0 sco F0_27
+Ji
+931 2920 M
+-0.043 0 (mediumint\(9\))A
+; : 778 2953 133 32 rc 0 0 0 sco F0_27
+Ji
+778 2953 M
+-0.069 0 (oldvalue)A
+; : 931 2953 167 32 rc 0 0 0 sco F0_27
+Ji
+931 2953 M
+0.058 0 (tinytext)A
+; : 778 2986 133 29 rc 0 0 0 sco F0_27
+Ji
+778 2986 M
+-0.131 0 (newvalue)A
+; : 931 2986 167 29 rc 0 0 0 sco F0_27
+Ji
+931 2986 M
+0.058 0 (tinytext)A
+;
+1370 1784 N M 286 116 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 1426 1789 220 32 rc 0 0 0 sco F0_27
+Ji
+1499 1789 M
+0.500 0 (cc)A
+; : 0 0 2454 3191 rc
+1370 1825 N M 286 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 1380 1827 89 32 rc 0 0 0 sco F0_27
+Ji
+0 29 1 sSU
+1380 1827 M
+-0.009 0 (bug_id)A
+-81 sU
+; : 1489 1827 167 32 rc 0 0 0 sco F0_27
+Ji
+0 29 1 sSU
+1489 1827 M
+-0.043 0 (mediumint\(9\))A
+-157 sU
+; : 1380 1860 89 32 rc 0 0 0 sco F0_27
+Ji
+0 29 1 sSU
+1380 1860 M
+-0.173 0 (who)A
+-49 sU
+; : 1489 1860 167 32 rc 0 0 0 sco F0_27
+Ji
+0 29 1 sSU
+1489 1860 M
+-0.043 0 (mediumint\(9\))A
+-157 sU
+;
+178 2819 N M 364 207 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 237 2824 295 32 rc 0 0 0 sco F0_27
+Ji
+310 2824 M
+-0.061 0 (fielddefs)A
+; : 0 0 2454 3191 rc
+178 2859 N M 364 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 188 2862 144 32 rc 0 0 0 sco F0_27
+Ji
+0 29 1 sSU
+188 2862 M
+-0.075 0 (fieldid)A
+-70 sU
+; : 352 2862 190 32 rc 0 0 0 sco F0_27
+Ji
+0 29 1 sSU
+352 2862 M
+-0.043 0 (mediumint\(9\))A
+-157 sU
+; : 188 2895 144 32 rc 0 0 0 sco F0_27
+Ji
+188 2895 M
+-0.132 0 (name)A
+; : 352 2895 190 32 rc 0 0 0 sco F0_27
+Ji
+352 2895 M
+-0.001 0 (VARCHAR\(64\))A
+; : 188 2928 144 32 rc 0 0 0 sco F0_27
+Ji
+188 2928 M
+0.132 0 (description)A
+; : 352 2928 190 32 rc 0 0 0 sco F0_27
+Ji
+352 2928 M
+-0.154 0 (mediumtext)A
+; : 188 2961 144 32 rc 0 0 0 sco F0_27
+Ji
+188 2961 M
+-0.067 0 (mailhead)A
+; : 352 2961 190 32 rc 0 0 0 sco F0_27
+Ji
+352 2961 M
+0.148 0 (tinyint\(4\))A
+; : 188 2994 144 29 rc 0 0 0 sco F0_27
+Ji
+188 2994 M
+0.283 0 (sortkey)A
+; : 352 2994 190 29 rc 0 0 0 sco F0_27
+Ji
+352 2994 M
+0.046 0 (smallint\(6\))A
+;
+1954 1803 N M 330 116 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 1988 1808 286 32 rc 0 0 0 sco F0_27
+Ji
+2061 1808 M
+0.122 0 (keywords)A
+; : 0 0 2454 3191 rc
+1954 1843 N M 330 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 1964 1846 133 32 rc 0 0 0 sco F0_27
+Ji
+0 29 1 sSU
+1964 1846 M
+-0.009 0 (bug_id)A
+-81 sU
+; : 2117 1846 167 32 rc 0 0 0 sco F0_27
+Ji
+0 29 1 sSU
+2117 1846 M
+-0.043 0 (mediumint\(9\))A
+-157 sU
+; : 1964 1879 133 32 rc 0 0 0 sco F0_27
+Ji
+0 29 1 sSU
+1964 1879 M
+0.053 0 (keywordid)A
+-122 sU
+; : 2117 1879 167 32 rc 0 0 0 sco F0_27
+Ji
+0 29 1 sSU
+2117 1879 M
+0.046 0 (smallint\(6\))A
+-125 sU
+;
+1104 2179 N M 330 175 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 1134 2184 290 32 rc 0 0 0 sco F0_27
+Ji
+1207 2184 M
+0.161 0 (longdescs)A
+; : 0 0 2454 3191 rc
+1104 2220 N M 330 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 1114 2222 133 32 rc 0 0 0 sco F0_27
+Ji
+1114 2222 M
+-0.009 0 (bug_id)A
+; : 1267 2222 167 32 rc 0 0 0 sco F0_27
+Ji
+1267 2222 M
+-0.043 0 (mediumint\(9\))A
+; : 1114 2255 133 32 rc 0 0 0 sco F0_27
+Ji
+1114 2255 M
+-0.173 0 (who)A
+; : 1267 2255 167 32 rc 0 0 0 sco F0_27
+Ji
+1267 2255 M
+-0.043 0 (mediumint\(9\))A
+; : 1114 2288 133 32 rc 0 0 0 sco F0_27
+Ji
+1114 2288 M
+-0.072 0 (bug_when)A
+; : 1267 2288 167 32 rc 0 0 0 sco F0_27
+Ji
+1267 2288 M
+0.057 0 (datetime)A
+; : 1114 2321 133 31 rc 0 0 0 sco F0_27
+Ji
+1114 2321 M
+-0.008 0 (thetext)A
+; : 1267 2321 167 31 rc 0 0 0 sco F0_27
+Ji
+1267 2321 M
+-0.154 0 (mediumtext)A
+;
+426 2221 N M 446 399 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 532 2226 330 32 rc 0 0 0 sco F0_27
+Ji
+605 2226 M
+-0.003 0 (profiles)A
+; : 0 0 2454 3191 rc
+426 2262 N M 446 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 436 2264 211 32 rc 0 0 0 sco F0_27
+Ji
+0 29 1 sSU
+436 2264 M
+0.080 0 (userid)A
+-74 sU
+; : 667 2264 205 32 rc 0 0 0 sco F0_27
+Ji
+0 29 1 sSU
+667 2264 M
+-0.043 0 (mediumint\(9\))A
+-157 sU
+; : 436 2297 211 32 rc 0 0 0 sco F0_27
+Ji
+436 2297 M
+-0.056 0 (login_name)A
+; : 667 2297 205 32 rc 0 0 0 sco F0_27
+Ji
+667 2297 M
+-0.002 0 (VARCHAR\(255\))A
+; : 436 2330 211 32 rc 0 0 0 sco F0_27
+Ji
+436 2330 M
+0.058 0 (password)A
+; : 667 2330 205 32 rc 0 0 0 sco F0_27
+Ji
+667 2330 M
+-0.001 0 (VARCHAR\(16\))A
+; : 436 2363 211 32 rc 0 0 0 sco F0_27
+Ji
+436 2363 M
+0.151 0 (cryptpassword)A
+; : 667 2363 205 32 rc 0 0 0 sco F0_27
+Ji
+667 2363 M
+-0.001 0 (VARCHAR\(64\))A
+; : 436 2396 211 32 rc 0 0 0 sco F0_27
+Ji
+436 2396 M
+-0.067 0 (realname)A
+; : 667 2396 205 32 rc 0 0 0 sco F0_27
+Ji
+667 2396 M
+-0.002 0 (VARCHAR\(255\))A
+; : 436 2429 211 32 rc 0 0 0 sco F0_27
+Ji
+436 2429 M
+0.118 0 (groupset)A
+; : 667 2429 205 32 rc 0 0 0 sco F0_27
+Ji
+667 2429 M
+0.046 0 (bigint\(20\))A
+; : 436 2462 211 32 rc 0 0 0 sco F0_27
+Ji
+436 2462 M
+0.026 0 (emailnotification)A
+; : 667 2462 205 32 rc 0 0 0 sco F0_27
+Ji
+667 2462 M
+-0.132 0 (enum)A
+; : 436 2495 211 32 rc 0 0 0 sco F0_27
+Ji
+436 2495 M
+-0.006 0 (disabledtext)A
+; : 667 2495 205 32 rc 0 0 0 sco F0_27
+Ji
+667 2495 M
+-0.154 0 (mediumtext)A
+; : 436 2528 211 32 rc 0 0 0 sco F0_27
+Ji
+436 2528 M
+-0.004 0 (newemailtech)A
+; : 667 2528 205 32 rc 0 0 0 sco F0_27
+Ji
+667 2528 M
+0.148 0 (tinyint\(4\))A
+; : 436 2561 211 32 rc 0 0 0 sco F0_27
+Ji
+436 2561 M
+0.097 0 (mybugslink)A
+; : 667 2561 205 32 rc 0 0 0 sco F0_27
+Ji
+667 2561 M
+0.148 0 (tinyint\(4\))A
+; : 436 2594 211 24 rc 0 0 0 sco F0_27
+Ji
+436 2594 M
+0.148 0 (blessgroupset)A
+; : 667 2594 205 24 rc 0 0 0 sco F0_27
+Ji
+667 2594 M
+0.046 0 (bigint\(20\))A
+;
+150 1818 N M 374 239 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 171 1823 343 32 rc 0 0 0 sco F0_27
+Ji
+244 1823 M
+0.086 0 (profiles_activity)A
+; : 0 0 2454 3191 rc
+150 1858 N M 374 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 160 1861 177 32 rc 0 0 0 sco F0_27
+Ji
+160 1861 M
+0.080 0 (userid)A
+; : 357 1861 167 32 rc 0 0 0 sco F0_27
+Ji
+357 1861 M
+-0.043 0 (mediumint\(9\))A
+; : 160 1894 177 32 rc 0 0 0 sco F0_27
+Ji
+160 1894 M
+-0.173 0 (who)A
+; : 357 1894 167 32 rc 0 0 0 sco F0_27
+Ji
+357 1894 M
+-0.043 0 (mediumint\(9\))A
+; : 160 1927 177 32 rc 0 0 0 sco F0_27
+Ji
+160 1927 M
+-0.043 0 (profiles_when)A
+; : 357 1927 167 32 rc 0 0 0 sco F0_27
+Ji
+357 1927 M
+0.057 0 (datetime)A
+; : 160 1960 177 32 rc 0 0 0 sco F0_27
+Ji
+160 1960 M
+-0.075 0 (fieldid)A
+; : 357 1960 167 32 rc 0 0 0 sco F0_27
+Ji
+357 1960 M
+-0.043 0 (mediumint\(9\))A
+; : 160 1993 177 32 rc 0 0 0 sco F0_27
+Ji
+160 1993 M
+-0.069 0 (oldvalue)A
+; : 357 1993 167 32 rc 0 0 0 sco F0_27
+Ji
+357 1993 M
+0.058 0 (tinytext)A
+; : 160 2026 177 28 rc 0 0 0 sco F0_27
+Ji
+160 2026 M
+-0.131 0 (newvalue)A
+; : 357 2026 167 28 rc 0 0 0 sco F0_27
+Ji
+357 2026 M
+0.058 0 (tinytext)A
+;
+1289 1975 N M 286 143 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 1326 1980 239 32 rc 0 0 0 sco F0_27
+Ji
+1399 1980 M
+0.094 0 (votes)A
+; : 0 0 2454 3191 rc
+1289 2016 N M 286 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 1299 2018 89 32 rc 0 0 0 sco F0_27
+Ji
+1299 2018 M
+-0.173 0 (who)A
+; : 1408 2018 167 32 rc 0 0 0 sco F0_27
+Ji
+1408 2018 M
+-0.043 0 (mediumint\(9\))A
+; : 1299 2051 89 32 rc 0 0 0 sco F0_27
+Ji
+1299 2051 M
+-0.009 0 (bug_id)A
+; : 1408 2051 167 32 rc 0 0 0 sco F0_27
+Ji
+1408 2051 M
+-0.043 0 (mediumint\(9\))A
+; : 1299 2084 89 32 rc 0 0 0 sco F0_27
+Ji
+1299 2084 M
+0.192 0 (count)A
+; : 1408 2084 167 32 rc 0 0 0 sco F0_27
+Ji
+1408 2084 M
+0.046 0 (smallint\(6\))A
+;
+1914 755 N M 342 116 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 1927 760 319 32 rc 0 0 0 sco F0_27
+Ji
+2000 760 M
+0.075 0 (dependencies)A
+; : 0 0 2454 3191 rc
+1914 796 N M 342 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 1924 798 145 32 rc 0 0 0 sco F0_27
+Ji
+1924 798 M
+0.137 0 (blocked)A
+; : 2089 798 167 32 rc 0 0 0 sco F0_27
+Ji
+2089 798 M
+-0.043 0 (mediumint\(9\))A
+; : 1924 831 145 32 rc 0 0 0 sco F0_27
+Ji
+1924 831 M
+0.045 0 (dependson)A
+; : 2089 831 167 32 rc 0 0 0 sco F0_27
+Ji
+2089 831 M
+-0.043 0 (mediumint\(9\))A
+;
+1548 755 N M 302 116 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 1564 760 276 32 rc 0 0 0 sco F0_27
+Ji
+1637 760 M
+0.145 0 (duplicates)A
+; : 0 0 2454 3191 rc
+1548 796 N M 302 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 1558 798 105 32 rc 0 0 0 sco F0_27
+Ji
+1558 798 M
+-0.083 0 (dupe_of)A
+; : 1683 798 167 32 rc 0 0 0 sco F0_27
+Ji
+1683 798 M
+-0.043 0 (mediumint\(9\))A
+; : 1558 831 105 32 rc 0 0 0 sco F0_27
+Ji
+0 29 1 sSU
+1558 831 M
+-0.012 0 (dupe)A
+-60 sU
+; : 1683 831 167 32 rc 0 0 0 sco F0_27
+Ji
+0 29 1 sSU
+1683 831 M
+-0.043 0 (mediumint\(9\))A
+-157 sU
+;
+1058 728 N M 364 143 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 1091 733 321 32 rc 0 0 0 sco F0_27
+Ji
+1164 733 M
+0.041 0 (keyworddefs)A
+; : 0 0 2454 3191 rc
+1058 769 N M 364 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 1068 771 144 32 rc 0 0 0 sco F0_27
+Ji
+0 29 1 sSU
+1068 771 M
+-0.003 0 (id)A
+-21 sU
+; : 1232 771 190 32 rc 0 0 0 sco F0_27
+Ji
+0 29 1 sSU
+1232 771 M
+0.046 0 (smallint\(6\))A
+-125 sU
+; : 1068 804 144 32 rc 0 0 0 sco F0_27
+Ji
+1068 804 M
+-0.132 0 (name)A
+; : 1232 804 190 32 rc 0 0 0 sco F0_27
+Ji
+1232 804 M
+-0.001 0 (VARCHAR\(64\))A
+; : 1068 837 144 32 rc 0 0 0 sco F0_27
+Ji
+1068 837 M
+0.132 0 (description)A
+; : 1232 837 190 32 rc 0 0 0 sco F0_27
+Ji
+1232 837 M
+-0.154 0 (mediumtext)A
+;
+170 696 N M 346 175 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 205 701 301 32 rc 0 0 0 sco F0_27
+Ji
+278 701 M
+-0.007 0 (shadowlog)A
+; : 0 0 2454 3191 rc
+170 737 N M 346 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 180 739 133 32 rc 0 0 0 sco F0_27
+Ji
+0 29 1 sSU
+180 739 M
+-0.003 0 (id)A
+-21 sU
+; : 333 739 183 32 rc 0 0 0 sco F0_27
+Ji
+0 29 1 sSU
+333 739 M
+0.069 0 (int\(11\))A
+-77 sU
+; : 180 772 133 32 rc 0 0 0 sco F0_27
+Ji
+180 772 M
+0.497 0 (ts)A
+; : 333 772 183 32 rc 0 0 0 sco F0_27
+Ji
+333 772 M
+0.036 0 (timestamp\(14\))A
+; : 180 805 133 32 rc 0 0 0 sco F0_27
+Ji
+180 805 M
+0.051 0 (reflected)A
+; : 333 805 183 32 rc 0 0 0 sco F0_27
+Ji
+333 805 M
+0.148 0 (tinyint\(4\))A
+; : 180 838 133 31 rc 0 0 0 sco F0_27
+Ji
+180 838 M
+-0.076 0 (command)A
+; : 333 838 183 31 rc 0 0 0 sco F0_27
+Ji
+333 838 M
+-0.154 0 (mediumtext)A
+;
+646 755 N M 308 116 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 691 760 253 32 rc 0 0 0 sco F0_27
+Ji
+764 760 M
+0.095 0 (watch)A
+; : 0 0 2454 3191 rc
+646 796 N M 308 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 656 798 111 32 rc 0 0 0 sco F0_27
+Ji
+0 29 1 sSU
+656 798 M
+0.068 0 (watcher)A
+-95 sU
+; : 787 798 167 32 rc 0 0 0 sco F0_27
+Ji
+0 29 1 sSU
+787 798 M
+-0.043 0 (mediumint\(9\))A
+-157 sU
+; : 656 831 111 32 rc 0 0 0 sco F0_27
+Ji
+0 29 1 sSU
+656 831 M
+0.065 0 (watched)A
+-101 sU
+; : 787 831 167 32 rc 0 0 0 sco F0_27
+Ji
+0 29 1 sSU
+787 831 M
+-0.043 0 (mediumint\(9\))A
+-157 sU
+; : 0 0 2454 3191 rc
+780 2186 N M -3 -403 - 459 -177 - 1 Lc 1 Lj [ 37 25 ] setdsh : 1.000 1.000 1.000 sco solid K ; 0 0 0 sco K ; : 0 0 2454 3191 rc
+1686 1620 N M 160 243 - 0 331 - 1 Lc 1 Lj [ 37 25 ] setdsh : 1.000 1.000 1.000 sco solid K ; 0 0 0 sco K ;
+LH
+pagesave restore
+
+(%%[ Page: 1 ]%%) =
+%%PageTrailer
+
+%%Trailer
+%%DocumentNeededFonts: Helvetica
+%%DocumentSuppliedFonts:
+Pscript_Win_Driver_Incr dup /terminate get exec
+savelevel0 restore
+%%Pages: 1
+(%%[ LastPage ]%%) =
+%%EOF
+%-12345X@PJL EOJ
+%-12345X
\ No newline at end of file
diff --git a/docs/images/note.gif b/docs/images/note.gif
new file mode 100644
index 0000000000000000000000000000000000000000..613bc7f709dad17aca2121c691213139b2d35aec
GIT binary patch
literal 226
zcmZ?wbhEHb6krfwIKlt|do>Ny82&djG#of^;Q#;sAR#K@hK2^kpDc_F4Dt+$|HRxq
z-4udz6N^fM6U$PI6v9%A4D}2X8FWCFfn4Lj>iWREC*|kd7XfQ>ycsgJ#q(`8e_eUc
z#c;tQX})E`>xz_`icY$`OKXw;pvfH3d9W$rv~5!P9lf`^x$^g#ZDxoyQCk1OLXg24
E0N;Q&g8%>k
literal 0
HcmV?d00001
diff --git a/docs/images/tip.gif b/docs/images/tip.gif
new file mode 100644
index 0000000000000000000000000000000000000000..fe2a1d56597d8bef0fbe49f532ab0a9f7f4dac26
GIT binary patch
literal 2432
zcmZ?wbhEHbbY;+Gc+S8Oq^WuD+Oa6h;wi<+$M$Z`HZ;6<>=*-wQ%m*Ut=Yv>f}C2M
zqM|s0-ami7cJG{}*~v?zoFpU^gMzBR-`iV#Y|g!{Q#37|k_{!UZSAR6<X9VJ*;C!K
zckQtrFU{hh<mY>Pt{r>-eopbZy~iXJ4WF;=DOPl92}-WcuD*8fUX-Qg-mP0T6%FTP
zD=JEG1Q{ys?U_>S6!iSwz2|GIpI^IoZtd2!Q(D$mCmXgbol_iS8MU_BOR?IJVM?;s
z+O5}mvYnPzdpUU}_ar;LKeu*DcF)pmuca+(Ed?Yr4K<w<TkcJXy7v6LmxM%iadL5x
z*R^xkuI=4gT)p=Fy?fV=U5gT6ICt*cQZETb28L`)#dBNNwnTYt?P+OA&fdE9`PP<}
zW5<qdElysVTpg7?rP#^x|NCoe@4Y{FZ13LUsB>HAXj;xWH>Y}SPj-u!<&-H)k4-6F
zJ7?{=mg-}BuPt4BEP3tTd)ZDc#rNi9TLyVW1zB3osjj~F{`-_EQ@p%_)*ice@7lF{
z=dRt`yR|sVY46&ld*`%xDH={$`hCijYfcgz@9$k(I%P^rb@H{XYoBk;j@o*zC&=sh
zwR7j@v=j?4oU2YYbgCB6^tv|1a_`zH#a@Qjw$9nxQ(UYm@cj8bO%B87=k^8}I-RQy
z+FIPRwz}o{)_YNwmjCa~vDDQ3|Nnn>c6D}Cl$WKZp#a0$mY`$L|8GsU{Qmv>wdc=!
zdRmgbf}9K$?`>Us?cA|yL&Z6khVS3MU%GVdv9)`bCTqUGcJA8RrPX_{J%9fE`PQXQ
zngV;LWKT(s>WMOZ|NP$bwLvX&)}Gtivp3u8{nj~4v!k}QBtJj4b?cO+$9j^ZvWts*
z<{X=|RDeN1Q$V6Px%ybo(tF>ZZ*2*h62&l3K=CIFBLhPUgAT|6pgiHg@sHsohm6OD
z1qYisgtcNK0;aD^6{yt}Rw}$X-+q^cYiE*oID?<Rg(X)&TZ3MkMle@Q*ux;!c%j;@
zC7q7m;sIupZXTGZdcx4h#VEF6$%BhWQ#Va}*|q5O4dwVb(@y>oPGwWix)P_rb%aN1
zt9oNd#|+g&3iEV*Gh#O^N%oz_*DLk1;NnVQP0sZ<Hf$7rI9*lTjVs1;;-N{3&f+|=
zJDt28jZ>08eYsJfa?xPw3}b#9!<Prt#8<i$KG?AEC@YUVn~rDcLP1m2S;@(DMM*cg
znV9ZM{M>v{pv_pu#M<OR_VnotwP|O#3SMk_^IX$j>**Kwjy2u8<!q}yt4a!{o?7#-
z_U9+IRXVYKdUJms&di+R%*Mp3C7jT<mhI{S?vQ5Y<NTq21s8f5=W2XD%6#&H0E<H8
z8paO3hKM3}^%V>SN2LxNaB0?=!Li6&bLo?VESl@5EOHYNb_r|})s;wUQJEcKcvNJ<
zn+e`RM@*W#>sUP#-F3wOI6V~9Qz_!o$ty5AW;A!rhtsS!96_97sXIP0@!F(W3MhGN
zm@!ByNhC3=$0|(oQ8mt3`D|9sww06ggtwSCh6FgWOmsH3c;e1{SjMQWIM3*bfJ^;^
z4c@FBVIMrCj_px7ve>EM(mcKPKaEF)FYIC9HQ5yKuwD6T$YM|C95>Y?E{3AzC-tT?
zBs*99D}CT_q#{cr+1Xh5htdf>|38f()q%RgM-6rbNH%cnkhtKWExqu;ah|#bEsSd0
zgeIO5Kf9vwq_i2&0cQTvmfx+sE&_~=svDPhpOQMOaCP<EIWkS`3|tNe4yy{kxa6S8
zV&lZbxj5hwqnelRffxoY7IOi)NEZzsu}BSpBZqxI2poym^LWvu_;S~Tcd~jr3K(^z
z945F)S(Qv+Gjj4t;8tRFnB>Vg_r=Bl{*nug4*aZl7r7hmIiYC6%2(iU!l`3|Q`d31
z<Da;-7D*VL5b|b7I-wtarLl3*VF7~%!^TxCEvyE61er9rX9ylrl3#OhmVV;`rDNjz
z6oL;5SL_fh`<HVu;*yW?oHd(Hik@;vKE!%0M#w?4`gq%Mg}R2O4hLolrbY#E7GVa_
z-qkl-ROjmmwkXY=-Y2Qfrt-8yZQYk7tCDt)s);(AM7DRk2!9bgtk~}2=q9&bTckR~
zAoPoS&}28mV-iw7lX?z*WwpPcxLm1}(?|5iUm+K%R1?Sdhrf6_sCNBOJoHoPj6<vN
zl3g!P%n6*k@$?_jgb8lax0f|G-tFi3#BqAgj&mPt5*vDRR2V)x_No0^qH1xIQ_JZG
z^EbJVOaTo_j3+(Z3?_YKkWOG?_P@X?dTxUpvyO6n@`)2}e1UC7Jd62%H}TC)InF8d
z<B?FWk()7(3yatX2KIjf0d1?B9J@Va9{Y$}-dkd^u{(I{bN=ZKY{nTIc-9y=^XF(V
z@kZ^KV9c?IH<zL9-?lU!o(T%P2M(~P{Zr#`<XIpnpm0b^Z$nFj$Wewj4_lN(5*e67
z92ie2Fd8&mWb?bB#I?5Ih~A<F6FJZ5b8$2`a~%nqAXU@I@i&u&Urs?==|cj;<6E5u
zM-+GxH5%9>3!-#_HngS0G?m3wG*#J!bY)IBBvAgsL#i#XD=lOp*Y$)(zKoDoOP52!
zrzPChol+98`JupJ!63jlX<?VVh6YEm$V_gI&At<sdW+QWWDt~VY<%>>g+o%amBXiC
zwd@8Z&IAW0siFW5y){idd;TRH;cYNz@-<k%V$g8-(54TT4h&8_f}b0=7cFFDjd9G{
zIHAoX%78=shbk+>h9jaz7Z?kj6qqMOG)sB}G#cJ`#G?J;h+K}Ew9A~O46GfjT9-;&
zg*XmKE^A;q&n48Rx}-s5#f+7zK@XT1wmcAT+i*lbsDM#cz>)2A@DXjl0OpsxPsHX<
zXggl_a7(;~uGkU_R|Oe{?hpwliQ^T_Kjjv-N>v<Om9pa~M^pnBe~u&n?iWtVas`L@
zUnFp@w_s&xDdc2UXkuXWIKcftYeM>gMPdR4j0zqTdYCE_1ezHfn6f&qM7c0AAGBah
z7BuP=V@a0OxznszGJ!|;fD&s~L$aHOg!!%Jl0yPBUpR!mPw4b6NaAKtVB%~Ez1?h(
z%qgeAAjjg=rM<^NV8;<>g@AyV<^zYA1AjDgu^6#rhA;`XWwhytgxzi4^FV-kX9JIe
aAuCV9$~_tn4;woOu&X^_GiGFDum%7Dw$)Go
literal 0
HcmV?d00001
diff --git a/docs/images/warning.gif b/docs/images/warning.gif
new file mode 100644
index 0000000000000000000000000000000000000000..c6f3ea9c9c3295e6c51c014ce5f029e1fc605e9c
GIT binary patch
literal 151
zcmZ?wbhEHblwpuzSjYeZ{}~wm|Np;#|9-`vEQ|~c%nUjpQII?XQ^uVBm8T`-XZaYM
zi@ZPeX5Q6IdC@*UjaeDLQky2Myehr@Gk3U|3WEdR%^g+t3f+cZE|$!Z77TZ`ntFP{
zl=j78{p}CEv%k#Qu)}DIW!;Q}i9(jqI_~Uon{9WUn*QR~zGM6n94FK}i~<-KtO4(W
BI_v-d
literal 0
HcmV?d00001
diff --git a/docs/rel_notes.txt b/docs/rel_notes.txt
index 81807ef4f..ad97cb65a 100644
--- a/docs/rel_notes.txt
+++ b/docs/rel_notes.txt
@@ -1,6 +1,10 @@
-There has not been a Bugzilla release for a while, but
-development has continued, and the Bugzilla team is proud
-to announce release of Bugzilla 2.12.
+After many hours of banging heads against brick walls and
+much imbibed caffeine, the Bugzilla team is proud to
+announce Bugzilla 2.14.
+
+This release is primarily a security release, in order to
+rectify security issues. However, some other important
+changes were made.
Recommended Practice For The Upgrade
------------------------------------
@@ -19,28 +23,233 @@ contains more errors after an upgrade, it doesn't necessarily
mean there are more errors in your database, as it is likely
they weren't being checked for in the old version.
-New email tech for email notifications is now recommended.
-Old email tech will probably be removed in Bugzilla 2.14.
-It is strongly recommended that you turn on the newemailtech
-and newemailtechdefault options on the Edit Parameters page
-(editparams.cgi), so new accounts will use new email tech.
-
-If you wish, you may move all old accounts over to new email
-tech by executing the following SQL statement in MySQL:
-
- UPDATE profiles SET newemailtech = '1';
+Administrators must make sure that certain files are
+inaccessible or confidential information might become
+available to enterprising individuals. This includes the
+localconfig file and the entire data directory. Please
+see the Bugzilla Guide for more information.
-About This Version
-------------------
+**************************
+*** ABOUT THIS VERSION ***
+**************************
Bugs referenced in the following text are bug numbers on
bugzilla.mozilla.org.
*** IMPORTANT CHANGES ***
-- There is now a facility for new email tech users to choose
- the sort of notifications they wish to receive. This
- facility will probably be improved in future versions.
+- Bugzilla 2.14 no longer supports old email tech. Upon
+ upgrading, all users will be moved over to new email tech.
+ This should speed up upgrading for installations with
+ a large number of bugs.
+ (bug 71552)
+
+- There is new functionality for people to see why they are
+ receiving notification mails.
+
+ Previously, some people filtered old email tech
+ notifications depending on whether they were in the To or the
+ CC header, in order to get a limited way of determining why
+ they were receiving the notification for filtering purposes.
+
+ Existing installations will need to make changes to support
+ this feature. The receive reasons can be added to the
+ notifications as a header and/or in the body. To add these
+ you will need to modify your newchangedmail parameter on
+ editparams.cgi, either by resetting it or appropriately
+ modifying it. The header value is specified by
+ %reasonsheader% and the body by %reasonsbody%. For example,
+ the new default parameter is:
+
+ --------------------------------------------------
+ From: bugzilla-daemon
+ To: %to%
+ Subject: [Bug %bugid%] %neworchanged%%summary%
+ X-Bugzilla-Reason: %reasonsheader%
+
+ %urlbase%show_bug.cgi?id=%bugid%
+
+ %diffs%
+
+
+
+ %reasonsbody%
+ --------------------------------------------------
+
+ (bug 26194)
+
+- Very long fields (especially multi-valued fields like keywords,
+ CCs, dependencies) on bug activity and notifications previously
+ could get truncated, resulting in useless notifications and data
+ loss on bug activity. Now the multi-valued fields only show
+ changes, and very big changes are split into multiple lines.
+ Where data loss has already occurred on bug activity, it is
+ indicated using question marks.
+ (bug 55161, 92266)
+
+- Previously, when a product's voting preferences changed all
+ votes were removed from all the bugs in the product. Also,
+ when a bug was moved to another product, all of its votes
+ were removed. This no longer occurs.
+
+ Instead, if the action would leave one or more bugs with
+ greater than the maximum number of votes per person per bug,
+ the number of votes will be reduced to the maximum. The
+ person will still be notified of this as before.
+
+ If the action would leave a user with more votes in a product
+ than is allowed, the limit will be breached so as to not lose
+ votes. However the user will not be able to update their
+ votes except to fix this situation. No further action is taken
+ in this version to make sure that the user does this.
+ (bug 28882, 92593)
+
+*** SECURITY ISSUES RESOLVED ***
+
+- Multiple instances of unauthorised access to confidential
+ bugs has been fixed.
+ (bug 39524, 39526, 39527, 39531, 39533, 70189, 82781)
+- Multiple instances of untrusted parameters not being
+ checked/escaped was fixed. These included definite security
+ holes.
+ (bug 38854, 38855, 38859, 39536, 87701, 95235)
+- After logging in passwords no longer appear in the URL.
+ (bug 15980)
+- Procedures to prevent unauthorised access to confidential
+ files are now simpler. In particular the shadow directory
+ no longer exists and the data/comments file no longer needs
+ to be directly accessible, so the entire data directory can
+ be blocked. However, no changes are required here if you
+ have a properly secured 2.12 installation as no new files
+ must be protected.
+ (bug 71552, 73191)
+- If they do not already exist, checksetup.pl will attempt to
+ write Apache .htaccess files by default, to prevent
+ unauthorised access to confidential files. You can turn this
+ off in the localconfig file.
+ (bug 76154)
+- Sanity check can now only be run by people in the 'editbugs'
+ group. Although it would be better to have a separate
+ group, this is not possible until the limitation on the
+ number of groups allowed has been removed.
+ (bug 54556)
+- The password is no longer stored in plaintext form. It will
+ be eradicated next time you run checksetup.pl. A user must
+ now change their password via a password change request that
+ gets validated at their e-mail account, rather than have it
+ mailed to them.
+ (bug 74032)
+- When you using product groups and you move a bug between
+ products (single or mass change), the bug will no longer be
+ restricted to the old product's group (if it was) and will
+ be restricted to the new product's group.
+ (bug 66235)
+- There are now options on a bug to choose whether the
+ reporter, assignee, QA and CCs can access a bug even if
+ they aren't in groups the bug it is restricted to.
+ (bug 39816)
+- You can no longer mark a bug as a duplicate of a bug you
+ can't see, and if you mark a bug a duplicate of a bug
+ the reporter cannot see you will be given options as to
+ what to do regarding adding the reporter of the resolved
+ bug to the CC of the open bug.
+ (bug 96085)
+
+*** Other changes of note ***
+
+- Groups can now be marked inactive, so you can't add a new
+ restriction on that group to a bug, while leaving bugs that
+ were previously restricted on that group alone.
+ (bug 75482)
+- backdoor.cgi has been removed from the installation. It was
+ old code that was Netscape-specific and its name was scaring
+ people.
+ (bug 87983)
+- You can now add or remove from CC on the bulk change page.
+ (bug 12819)
+- New users created by administrators are now automatically
+ inserted into groups according to the group's regular
+ expression. Administrators must edit the user in a second
+ step to override these choices. Previously the
+ administrator specified these explicitly which could lead
+ to incorrect settings.
+ (bug 45164)
+- The userregexp of system groups can now be edited without
+ resorting to direct database access.
+ (bug 65290)
+
+
+*** Bug fixes of note ***
+
+- The bug list page was sometimes bringing up a not logged in
+ footer when the user was logged in and the installation was
+ using a shadow database.
+ (bug 47914)
+- You can now view the bug summary in your browser title for
+ a group-restricted bug if you have proper permissions.
+ (bug 71767)
+- Quick search for search terms did not work in IE5.
+ This has been worked around.
+ (bug 77699)
+- Quick search for search terms crashed NN4.76/4.77 for Unix.
+ This has been worked around.
+ (bug 83619)
+- Queries on bugs you have commented on using the "added
+ comment" feature should be a lot faster and not time out
+ on large installations due to the addition of an index.
+ (bug 57350)
+- You can now alter group settings on bulk change for groups
+ that aren't on for all bugs or off for all bugs.
+ (bug 84714)
+- New bug notifications now include the CC and QA fields.
+ (bug 28458)
+- Bugzilla is now more Windows friendly, although it is still
+ not an official platform.
+ (bug 88179, 29064)
+- Passwords are now encrypted using Perl's encrypt function.
+ This makes Bugzilla more portable to more operating systems.
+ (bug 77473)
+- Bugzilla didn't properly shut down when told to - some
+ queries could still be sent to the database.
+ (bug 95082)
+
+*** Outstanding issues of note ***
+
+- Bug counts (on reports.cgi) can be very slow if you have to
+ count a lot of bugs. In this case the connection can time
+ out before the page finishes loading. Extending the cgi
+ timeout on your web server might help this situation.
+ (bug 63249)
+- Renaming or removing keywords will not update the "keyword
+ cache", and queries on keywords may not work properly, until
+ you rebuild the cache on the sanity check page
+ (sanitycheck.cgi). The changer will receive a warning to do
+ this when altering the keyword.
+ (bug 69621)
+- Email notifications will not work out of the box if you are
+ using Postfix, Exim or possibly other non-SendMail mail
+ transfer agents, as Bugzilla sends mail by default in
+ "deferred" mode using the "-ODeliveryMode=deferred" command
+ line option, which needs to be supported by the sendmail
+ program. To fix this, you can turn on the "sendmailnow"
+ parameter on the Edit Parameters page (editparams.cgi).
+ (bug 50159)
+- The new options to let people see a bug when their name
+ is on it but who aren't in the groups the bug is restricted
+ to only allow people to view bugs if they know the bug number.
+ It still will not show up in these people's buglists and
+ they will not receive email about changes to the bugs.
+ (bugs 95024, 97469)
+
+**********************************************************
+*** USERS UPGRADING FROM 2.10 OR EARLIER - 2.12 ISSUES ***
+**********************************************************
+
+*** IMPORTANT CHANGES ***
+
+- There is now a facility for users to choose the sort of
+ notifications they wish to receive. This facility will
+ probably be improved in future versions.
(bug 17464)
- "Changed" will no longer appear on the subject line of
@@ -97,10 +306,11 @@ bugzilla.mozilla.org.
open bug.
(bug 28676)
+
*** Bug fixes of note ***
-- Notification emails using new email tech will now be sent to
- QA contacts.
+- Notification emails will now always be sent to QA contacts.
+ Previously they wouldn't if you were using new email tech.
(bug 30826)
- When marking a bug as a duplicate, the duplicate stamp marked
on the open bug will no longer be written too early (such as
@@ -113,43 +323,18 @@ bugzilla.mozilla.org.
check these.
(bug 66876)
- Administrators can no longer create an email accounts that do
- not match the global email regexp parameter. Previously this
- would cause sanity check errors.
+ not match the global email regular expression parameter.
+ Previously this could occur and would cause sanity check
+ errors.
(bug 32971)
- The resolution field can no longer become empty when the
bug is resolved. This occurred because of midair collisions.
(bug 49306)
-*** Outstanding issues of note ***
-
-- Bug counts (on reports.cgi) can be very slow if you have to
- count a lot of bugs. In this case the connection can time
- out before the page finishes loading. Extending the cgi
- timeout on your web server might help this situation.
- (bug 63249)
-- Administrators must make sure that certain files are
- properly inaccessible or confidential information might become
- available to enterprising individuals. This includes the
- localconfig file, the entire shadow directory and the entire
- data directory except for data/comments (the quips file).
- (bug 65572)
-- Renaming or removing keywords will not update the "keyword
- cache", and queries on keywords may not work properly, until
- you rebuild the cache on the sanity check page
- (sanitycheck.cgi). The changer will receive a warning to do
- this when altering the keyword.
- (bug 69621)
-- Email notifications will not work out of the box if you are
- using Postfix, Exim or possibly other non-SendMail mail
- transfer agents, as Bugzilla sends mail by default in
- "deferred" mode using the "-ODeliveryMode=deferred" command
- line option, which needs to be supported by the sendmail
- program. To fix this, you can turn on the "sendmailnow"
- parameter on the Edit Parameters page (editparams.cgi).
- (bug 50159)
-
-
-
-
+*******************************************
+*** USERS UPGRADING FROM 2.8 OR EARLIER ***
+*******************************************
+Release notes were not compiled for versions of Bugzilla before
+2.12.
diff --git a/docs/sgml/Bugzilla-Guide.sgml b/docs/sgml/Bugzilla-Guide.sgml
index 9334472af..8f2136bd8 100644
--- a/docs/sgml/Bugzilla-Guide.sgml
+++ b/docs/sgml/Bugzilla-Guide.sgml
@@ -1,4 +1,4 @@
-<!DOCTYPE BOOK PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
<!-- Include macros -->
<!ENTITY about SYSTEM "about.sgml">
@@ -17,99 +17,153 @@
<!ENTITY patches SYSTEM "patches.sgml">
<!ENTITY variants SYSTEM "variants.sgml">
<!ENTITY requiredsoftware SYSTEM "requiredsoftware.sgml">
+<!ENTITY revhistory SYSTEM "revhistory.sgml">
+
+<!ENTITY bz "http://www.mozilla.org/projects/bugzilla">
+<!ENTITY bz-ver "2.14">
+<!ENTITY bz-cvs-ver "2.15">
+<!ENTITY bzg-date "August 10, 2001">
+<!ENTITY bzg-ver "2.14">
+<!ENTITY bzg-cvs-ver "2.15.0">
+<!ENTITY bzg-auth "Matthew P. Barnson">
+<!ENTITY bzg-auth-email "<email>barnboy@trilobyte.net</email>">
+<!ENTITY mysql "http://www.mysql.com/">
+<!ENTITY perl-ver "5.6.1">
]>
-<!-- Coding standards for this document
-
-1. Preface new or modified sections with a comment stating who
- modified it and when; please also use the "authorinitials" tag.
-
-2. There is no "two".
-
-3. Other than the GFDL, please use the "section" tag instead of "sect1", "sect2", etc.
-
-4. Use Entities to include files for new chapters in Bugzilla-Guide.sgml.
-
-5. Ensure all documents compile cleanly to HTML after modification.
- The errors "DTD Declaration not allowed here" and "DTDDECL catalog types not supported"
- are normal errors to be expected when compiling the whole guide.
-
-6. Try to index important terms wherever possible.
-7. Follow coding standards at http://www.linuxdoc.org.
-
-8. All tags should be lowercase (needsfix)
-
-9. Code being submitted for review should use the
-"review" tag. Documentation on this is available at
-http://www.linuxdoc.org/LDP/LDP-Author-Guide/tools-hints.html
- under section 4.9.4, "Making notes on the text while it's being written".
+<!-- Coding standards for this document
-10. Please use sensible spacing. The comments at the very end of each Guide
- file define reasonable defaults for PSGML mode in EMACS.
- Double-indent tags, use double spacing whenever possible,
- try to avoid clutter and feel free to waste space in the code to make it more readable.
+* 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.
+* 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.
+* Try to index important terms wherever possible.
+* Use "glossterm" whenever you introduce a new term.
+* Follow coding standards at http://www.linuxdoc.org, and
+check out the KDE guidelines (they are nice, too)
+http://i18n.kde.org/doc/markup.html
+* All tags should be lowercase (needsfix)
+* Please use sensible spacing. The comments at the very end of each
+file define reasonable defaults for PSGML mode in EMACS.
+Double-indent tags, use double spacing whenever possible, and
+try to avoid clutter and feel free to waste space in the code to make it more readable.
-->
-<BOOK ID="index">
+<book id="index">
<!-- Header -->
- <BOOKINFO>
- <TITLE>The Bugzilla Guide</TITLE>
- <PUBDATE>v2.12.0, 24 April 2001</PUBDATE>
- <AUTHOR>
- <FIRSTNAME>Matthew</FIRSTNAME>
- <OTHERNAME>P.</OTHERNAME>
- <SURNAME>Barnson</SURNAME>
- <affiliation>
- <address><email>barnboy@trilobyte.net</email></address>
- </affiliation>
- </AUTHOR>
-
- <ABSTRACT>
- <PARA>This is the documentation for Bugzilla, the Mozilla bug-tracking system.</PARA>
- </ABSTRACT>
-
- <REVHISTORY>
- <REVISION>
- <REVNUMBER>v2.11</REVNUMBER>
- <DATE>20 December 2000</DATE>
- <AUTHORINITIALS>MPB</AUTHORINITIALS>
- <REVREMARK>Converted the README, FAQ, and DATABASE information into SGML
- docbook format.</REVREMARK>
- </REVISION>
+ <bookinfo>
+ <title>The Bugzilla Guide</title>
+ <pubdate>2001-04-25</pubdate>
+ <revhistory>
+ <revision>
+ <revnumber>v2.11</revnumber>
+ <date>20 December 2000</date>
+ <authorinitials>MPB</authorinitials>
+ <revremark>
+ Converted the README, FAQ, and DATABASE information into
+ SGML docbook format.
+ </revremark>
+ </revision>
<revision>
<revnumber>2.11.1</revnumber>
<date>06 March 2001</date>
<authorinitials>MPB</authorinitials>
<revremark>
- Took way too long to revise this for 2.12 release.
- Updated FAQ to use qandaset tags instead of literallayout,
- cleaned up administration section, added User Guide section,
- miscellaneous FAQ updates and third-party integration information.
- From this point on all new tags are lowercase in preparation for the
- 2.13 release of the Guide in XML format instead of SGML.
+ Took way too long to revise this for 2.12 release. Updated
+ FAQ to use qandaset tags instead of literallayout, cleaned
+ up administration section, added User Guide section,
+ miscellaneous FAQ updates and third-party integration
+ information. From this point on all new tags are lowercase
+ in preparation for the 2.13 release of the Guide in XML
+ format instead of SGML.
</revremark>
</revision>
-
+
<revision>
<revnumber>2.12.0</revnumber>
<date>24 April 2001</date>
<authorinitials>MPB</authorinitials>
<revremark>
- Things fixed this release: Elaborated on queryhelp interface, added FAQ regarding
- moving bugs from one keyword to another, clarified possible problems with the Landfill
- tutorial, fixed a boatload of typos and unclear sentence structures. Incorporated the
- README into the UNIX installation section, and changed the README to indicate the deprecated
- status. Things I know need work: Used "simplelist" a lot, where I should have used
- "procedure" to tag things. Need to lowercase all tags to be XML compliant.
+ Things fixed this release: Elaborated on queryhelp
+ interface, added FAQ regarding moving bugs from one keyword
+ to another, clarified possible problems with the Landfill
+ tutorial, fixed a boatload of typos and unclear sentence
+ structures. Incorporated the README into the UNIX
+ installation section, and changed the README to indicate the
+ deprecated status. Things I know need work: Used
+ "simplelist" a lot, where I should have used "procedure" to
+ tag things. Need to lowercase all tags to be XML compliant.
+ </revremark>
+ </revision>
+
+ <revision>
+ <revnumber>2.14.0</revnumber>
+ <date>07 August 2001</date>
+ <authorinitials>MPB</authorinitials>
+ <revremark>
+ Attempted to integrate relevant portions of the UNIX and
+ Windows installation instructions, moved some data from FAQ
+ to Install, removed references to README from text, added
+ Mac OS X install instructions, fixed a bunch
+ of tpyos (Mark Harig), linked text that referenced other
+ parts of the Guide, and nuked the old MySQL permissions
+ section.
</revremark>
</revision>
- </REVHISTORY>
+ </revhistory>
+
+ <authorgroup>
+
+ <author>
+ <firstname>Matthew</firstname>
+ <othername>P.</othername>
+ <surname>Barnson</surname>
+ <affiliation>
+ <address><email>barnboy@trilobyte.net</email></address>
+ </affiliation>
+ </author>
+
+ <collab>
+ <collabname>Zach Lipton</collabname>
+ <affiliation>
+ <address><email>zach AT zachlipton DOT com</email></address>
+ </affiliation>
+ </collab>
+
+ </authorgroup>
+
+ <abstract>
+ <para>
+ This is the documentation for Bugzilla, the Mozilla
+ bug-tracking system.
+ </para>
+ <para>
+ Bugzilla is an enterprise-class set of software utilities
+ that, when used together, power issue-tracking for hundreds of
+ organizations around the world, tracking millions of bugs.
+ While it is easy to use and quite flexible, it is very
+ difficult for a novice to install and maintain. Although we
+ have provided step-by-step directions, Bugzilla is not always
+ easy to get working. Please be sure the person responsible
+ for installing and maintaining this software is a qualified
+ professional on operating system upon which you install
+ Bugzilla.
+ </para>
+ <para>
+ THIS DOCUMENTATION IS MAINTAINED IN DOCBOOK 4.1 SGML FORMAT.
+ IF YOU WISH TO MAKE CORRECTIONS, PLEASE MAKE THEM IN PLAIN
+ TEXT OR SGML DIFFS AGAINST THE SOURCE. I CANNOT ACCEPT
+ ADDITIONS TO THE GUIDE WRITTEN IN HTML!
+ </para>
+ </abstract>
+
<KEYWORDSET>
<KEYWORD>Bugzilla</KEYWORD>
@@ -127,21 +181,24 @@ http://www.linuxdoc.org/LDP/LDP-Author-Guide/tools-hints.html
<!-- About This Guide -->
&about;
+<!-- Using Bugzilla -->
+&using;
+
<!-- Installing Bugzilla -->
&installation;
<!-- Administering Bugzilla -->
&administration;
-<!-- Using Bugzilla -->
-&using;
-
<!-- Integrating Bugzilla with Third-Party Tools -->
&integration;
<!-- The Future of Bugzilla -->
&future;
+<!-- Major Bugzilla Variants -->
+&variants;
+
<!-- Appendix: The Frequently Asked Questions -->
&faq;
@@ -151,9 +208,6 @@ http://www.linuxdoc.org/LDP/LDP-Author-Guide/tools-hints.html
<!-- Appendix: The Database Schema -->
&database;
-<!-- Appendix: Major Bugzilla Variants -->
-&variants;
-
<!-- Appendix: Custom Patches -->
&patches;
@@ -166,31 +220,26 @@ http://www.linuxdoc.org/LDP/LDP-Author-Guide/tools-hints.html
<!-- Index -->
&index;
-</BOOK>
+
+</book>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
-sgml-omittag:t
-sgml-shorttag:t
-sgml-namecase-general:t
-sgml-general-insert-case:lower
-sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
-sgml-indent-step:2
-sgml-indent-data:t
-sgml-parent-document:nil
+sgml-auto-insert-required-elements:t
+sgml-balanced-tag-edit:t
sgml-exposed-tags:nil
+sgml-general-insert-case:lower
+sgml-indent-data:t
+sgml-indent-step:2
sgml-local-catalogs:nil
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-shorttag:t
+sgml-tag-region-if-active:t
End:
-->
-
-
-
-
-
-
-
-
-
diff --git a/docs/sgml/CVS/Entries b/docs/sgml/CVS/Entries
index e1e2b8af3..14b475507 100644
--- a/docs/sgml/CVS/Entries
+++ b/docs/sgml/CVS/Entries
@@ -1,18 +1,18 @@
-/Bugzilla-Guide.sgml/1.2/Wed Apr 25 07:12:11 2001//
-/about.sgml/1.2/Wed Apr 25 07:12:11 2001//
-/administration.sgml/1.3/Wed Apr 25 07:38:21 2001//
-/conventions.sgml/1.1/Thu Mar 8 05:36:37 2001//
-/database.sgml/1.2/Wed Apr 25 07:12:12 2001//
-/dbschema.jpg/1.5/Fri Apr 6 04:44:41 2001//
-/faq.sgml/1.2/Wed Apr 25 07:12:12 2001//
-/future.sgml/1.2/Wed Apr 25 07:12:13 2001//
-/gfdl.sgml/1.1/Thu Mar 8 05:36:42 2001//
-/glossary.sgml/1.1/Thu Mar 8 05:36:43 2001//
-/index.sgml/1.1/Thu Mar 8 05:36:44 2001//
-/installation.sgml/1.2/Wed Apr 25 07:12:13 2001//
-/integration.sgml/1.2/Wed Apr 25 07:12:15 2001//
-/patches.sgml/1.2/Wed Apr 25 07:12:15 2001//
-/requiredsoftware.sgml/1.1/Wed Apr 25 07:12:17 2001//
-/using.sgml/1.2/Wed Apr 25 07:12:17 2001//
-/variants.sgml/1.2/Wed Apr 25 07:12:17 2001//
+/Bugzilla-Guide.sgml/1.6/Wed Aug 29 17:25:36 2001//TBUGZILLA-2_14
+/about.sgml/1.5/Wed Aug 29 17:25:36 2001//TBUGZILLA-2_14
+/administration.sgml/1.7/Wed Aug 29 17:25:36 2001//TBUGZILLA-2_14
+/conventions.sgml/1.2/Fri Aug 10 22:13:50 2001//TBUGZILLA-2_14
+/database.sgml/1.4/Wed Aug 29 17:25:36 2001//TBUGZILLA-2_14
+/dbschema.mysql/1.1/Fri Aug 10 22:13:50 2001//TBUGZILLA-2_14
+/faq.sgml/1.6/Wed Aug 29 17:25:38 2001//TBUGZILLA-2_14
+/future.sgml/1.5/Wed Aug 29 17:25:38 2001//TBUGZILLA-2_14
+/gfdl.sgml/1.2/Fri Aug 10 22:13:52 2001//TBUGZILLA-2_14
+/glossary.sgml/1.3/Wed Aug 22 03:44:31 2001//TBUGZILLA-2_14
+/index.sgml/1.2/Fri Aug 10 22:13:53 2001//TBUGZILLA-2_14
+/installation.sgml/1.7/Wed Aug 29 18:13:41 2001//TBUGZILLA-2_14
+/integration.sgml/1.5/Wed Aug 29 17:25:38 2001//TBUGZILLA-2_14
+/patches.sgml/1.5/Wed Aug 29 17:25:39 2001//TBUGZILLA-2_14
+/requiredsoftware.sgml/1.2/Fri Aug 10 22:13:54 2001//TBUGZILLA-2_14
+/using.sgml/1.5/Wed Aug 29 17:25:39 2001//TBUGZILLA-2_14
+/variants.sgml/1.4/Wed Aug 22 03:44:32 2001//TBUGZILLA-2_14
D
diff --git a/docs/sgml/CVS/Tag b/docs/sgml/CVS/Tag
new file mode 100644
index 000000000..c10f87310
--- /dev/null
+++ b/docs/sgml/CVS/Tag
@@ -0,0 +1 @@
+NBUGZILLA-2_14
diff --git a/docs/sgml/about.sgml b/docs/sgml/about.sgml
index d1b56cfdb..04e054bc2 100644
--- a/docs/sgml/about.sgml
+++ b/docs/sgml/about.sgml
@@ -1,242 +1,255 @@
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
-<!ENTITY conventions SYSTEM "conventions.sgml"> ] >
-
-<CHAPTER ID="about">
-<TITLE>About This Guide</TITLE>
-
- <SECTION ID="aboutthisguide">
- <TITLE>Purpose and Scope of this Guide</TITLE>
- <PARA>
- This document was started on September 17, 2000
- by Matthew P. Barnson after a great deal of procrastination updating the Bugzilla FAQ,
- which I left untouched for nearly half a year.
- After numerous complete rewrites and reformatting, it is the document you see today.
- </PARA>
- <PARA>
- Despite the lack of updates, Bugzilla is simply the best piece of bug-tracking software
- the world has ever seen. This document is intended to be the comprehensive guide to
- the installation, administration, maintenance, and use of the Bugzilla bug-tracking system.
- </PARA>
- <PARA>
- This release of the Bugzilla Guide is the <EMPHASIS>2.11</EMPHASIS> release.
- It is so named that it may match the current version of Bugzilla.
- The numbering tradition stems from that used for many free software projects,
- in which <EMPHASIS>even-numbered</EMPHASIS> point releases (1.2, 1.14, etc.)
- are considered "stable releases", intended for public consumption; on the other
- hand, <EMPHASIS>odd-numbered</EMPHASIS> point releases (1.3, 2.09, etc.)
- are considered unstable <EMPHASIS>development</EMPHASIS> releases intended
- for advanced users, systems administrators, developers, and those who enjoy
- a lot of pain.
- </PARA>
- <PARA>
- Newer revisions of the Bugzilla Guide will follow the numbering conventions of
- the main-tree Bugzilla releases, available at
- <ULINK URL="http://www.mozilla.org/bugs/source.html">Mozilla.org</ULINK>, with
- the exception that intermediate releases will have a minor revision number
- following a period. For instance, if the current version of Bugzilla is 4.2,
- the current "stable" version of the Bugzilla guide, in, say, it's fifth revision,
- would be numbered "4.2.5". Got it? Good.
- </PARA>
- <PARA>
- I wrote this in response to the enormous demand for decent Bugzilla documentation.
- I have incorporated instructions from the Bugzilla README, Frequently Asked Questions,
- Database Schema Document, and various mailing lists to create it.
- Chances are, there are glaring errors in this documentation; please contact
- <EMAIL>barnboy@trilobyte.net</EMAIL> to correct them.
- </PARA>
- </SECTION>
-
- <SECTION ID="copyright">
- <TITLE>Copyright Information</TITLE>
- <BLOCKQUOTE>
- <ATTRIBUTION>Copyright (c) 2000-2001 Matthew P. Barnson</ATTRIBUTION>
- <PARA>
- Permission is granted to copy, distribute and/or modify this document under thei
- terms of the GNU Free Documentation License, Version 1.1 or any later version published
- by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and
- with no Back-Cover Texts. A copy of the license is included in the section entitled
- "GNU Free Documentation LIcense".
- </PARA>
- </BLOCKQUOTE>
- <PARA>
- If you have any questions regarding this document, its' copyright, or publishing this
- document in non-electronic form, please contact <EMAIL>barnboy@trilobyte.net</EMAIL>
- </PARA>
- </SECTION>
-
- <SECTION ID="disclaimer">
- <TITLE>Disclaimer</TITLE>
- <PARA>
+<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
+<!ENTITY conventions SYSTEM "conventions.sgml"> ] > -->
+
+<chapter id="about">
+<title>About This Guide</title>
+
+ <section id="aboutthisguide">
+ <title>Purpose and Scope of this Guide</title>
+ <para>
+ This document was started on September 17, 2000 by Matthew P.
+ Barnson after a great deal of procrastination updating the
+ Bugzilla FAQ, which I left untouched for nearly half a year.
+ After numerous complete rewrites and reformatting, it is the
+ document you see today.
+ </para>
+ <para>
+ Bugzilla is simply the best piece of bug-tracking software the
+ world has ever seen. This document is intended to be the
+ comprehensive guide to the installation, administration,
+ maintenance, and use of the Bugzilla bug-tracking system.
+ </para>
+ <para>
+ This release of the Bugzilla Guide is the
+ <emphasis>&bzg-ver;</emphasis> release. It is so named that it
+ may match the current version of Bugzilla. The numbering
+ tradition stems from that used for many free software projects,
+ in which <emphasis>even-numbered</emphasis> point releases (1.2,
+ 1.14, etc.) are considered "stable releases", intended for
+ public consumption; on the other hand,
+ <emphasis>odd-numbered</emphasis> point releases (1.3, 2.09,
+ etc.) are considered unstable <emphasis>development</emphasis>
+ releases intended for advanced users, systems administrators,
+ developers, and those who enjoy a lot of pain.
+ </para>
+ <para>
+ Newer revisions of the Bugzilla Guide follow the numbering
+ conventions of the main-tree Bugzilla releases, available at
+ <ulink url="&bz;">&bz;</ulink>. Intermediate releases will have
+ a minor revision number following a period. The current version
+ of Bugzilla, as of this writing (&bzg-date;) is &bz-ver;; if
+ something were seriously wrong with that edition of the Guide,
+ subsequent releases would receive an additional dotted-decimal
+ digit to indicate the update (&bzg-ver;.1, &bzg-ver;.2, etc.).
+ Got it? Good.
+ </para>
+ <para>
+ I wrote this in response to the enormous demand for decent
+ Bugzilla documentation. I have incorporated instructions from
+ the Bugzilla README, Frequently Asked Questions, Database Schema
+ Document, and various mailing lists to create it. Chances are,
+ there are glaring errors in this documentation; please contact
+ &bzg-auth-email; to correct them.
+ </para>
+ </section>
+
+ <section id="copyright">
+ <title>Copyright Information</title>
+ <blockquote>
+ <attribution>Copyright (c) 2000-2001 &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 in the section entitled "GNU Free
+ Documentation LIcense".
+ </para>
+ </blockquote>
+ <para>
+ If you have any questions regarding this document, its
+ copyright, or publishing this document in non-electronic form,
+ please contact &bzg-auth;.
+ </para>
+ </section>
+
+ <section id="disclaimer">
+ <title>Disclaimer</title>
+ <para>
No liability for the contents of this document can be accepted.
Use the concepts, examples, and other content at your own risk.
As this is a new edition of this document, there may be errors
- and inaccuracies that may damage your system. Use of this document
- may cause your girlfriend to leave you, your cats to pee on your
- furniture and clothing, your computer to cease functioning, your
- boss to fire you, and global thermonuclear war. Proceed with caution.
- </PARA>
- <PARA>
- 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.
- In particular, I like to put down Microsoft(tm). Live with it.
- </PARA>
- <PARA>
- Naming of particular products or brands should not be seen as endorsements,
- with the exception of the term "GNU/Linux".
- Use GNU/Linux. Love it. Bathe with it. It is life and happiness.
- I endorse it wholeheartedly and encourage you to do the same.
- </PARA>
- <PARA>
- You are strongly recommended to make a backup of your system before
- installing Bugzilla and at regular intervals thereafter. Heaven knows
- it's saved my bacon time after time; if you implement any suggestion in
- this Guide, implement this one!
- </PARA>
- <PARA>
- Bugzilla has not undergone a complete security review.
- Security holes probably exist in the code.
- Great care should be taken both in the installation and usage of this software.
- Carefully consider the implications of installing other network services with Bugzilla.
- </PARA>
- </SECTION>
+ and inaccuracies that may damage your system. Use of this
+ document may cause your girlfriend to leave you, your cats to
+ pee on your furniture and clothing, your computer to cease
+ functioning, your boss to fire you, and global thermonuclear
+ war. Proceed with caution.
+ </para>
+ <para>
+ 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.
+ </para>
+ <para>
+ Naming of particular products or brands should not be seen as
+ endorsements, with the exception of the term "GNU/Linux". I
+ 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.
+ </para>
+ <para>
+ You are strongly recommended to make a backup of your system
+ before installing Bugzilla and at regular intervals thereafter.
+ Heaven knows it's saved my bacon time after time; if you
+ implement any suggestion in this Guide, implement this one!
+ </para>
+ <para>
+ 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 insure
+ your security needs are met.
+ </para>
+ </section>
<!-- Section 2: New Versions -->
- <SECTION ID="newversions">
- <TITLE>New Versions</TITLE>
- <PARA>
- This is the initial release of the Bugzilla Guide.
- </PARA>
- <PARA>
+ <section id="newversions">
+ <title>New Versions</title>
+ <para>
+ This is the &bzg-ver; version of The Bugzilla Guide. 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:
- </PARA>
- <PARA>
- <ITEMIZEDLIST>
- <LISTITEM>
- <PARA>
- <ULINK URL="http://www.trilobyte.net/barnsons/">TriloBYTE</ULINK>
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- <ULINK URL="http://www.mozilla.org/projects/bugzilla/">Mozilla.org</ULINK>
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- <ULINK URL="http://www.linuxdoc.org/">The Linux Documentation Project</ULINK>
- </PARA>
- </LISTITEM>
- </ITEMIZEDLIST>
- </PARA>
- <PARA>
+ </para>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://www.trilobyte.net/barnsons/">TriloBYTE</ulink>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://www.mozilla.org/projects/bugzilla/">Mozilla.org</ulink>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://www.linuxdoc.org/">The Linux
+ Documentation Project</ulink>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ <para>
The latest version of this document can be checked out via CVS.
- Please follow the instructions available at
- <ULINK URL="http://www.mozilla.org/cvs.html">the Mozilla CVS page</ULINK>,
- and check out the mozilla/webtools/bugzilla/docs/ branch.
- </PARA>
- </SECTION>
-
- <SECTION ID="credits">
- <TITLE>Credits</TITLE>
- <PARA>
- The people listed below have made enormous contributions to the creation
- of this Guide, through their dedicated hacking efforts,
- numerous e-mail and IRC support sessions,
- and overall excellent contribution to the Bugzilla community:
- </PARA>
- <PARA>
- <ULINK URL="mailto://terry@mozilla.org">Terry Weissman</ULINK>
- for initially converting Bugzilla from BugSplat!
- and writing the README upon which this 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
+ Please follow the instructions available at <ulink
+ url="http://www.mozilla.org/cvs.html">the Mozilla CVS page</ulink>, and check out the mozilla/webtools/bugzilla/docs/ branch.
+ </para>
+ </section>
+
+ <section id="credits">
+ <title>Credits</title>
+ <para>
+ The people listed below have made enormous contributions to the
+ creation of this Guide, through their dedicated hacking efforts,
+ numerous e-mail and IRC support sessions, and overall excellent
+ contribution to the Bugzilla community:
+ </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>
- <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.
- </PARA>
- </SECTION>
- <SECTION id="contributors">
-<TITLE>Contributors</TITLE>
- <PARA>
- Thanks go to these people for significant contributions
- to this documentation (in no particular order):
- </PARA>
- <PARA>
- Zach Lipton (significant textual contributions),
- Andrew Pearson,
- Spencer Smith,
- Eric Hanson,
- Kevin Brannen,
- </PARA>
- </SECTION>
- <SECTION ID="feedback">
- <TITLE>Feedback</TITLE>
- <PARA>
- I welcome feedback on this document. Without your submissions and input,
- this Guide cannot continue to exist. Please mail additions, comments, criticisms, etc.
- to <EMAIL>barnboy@trilobyte.net</EMAIL>. Please send flames to
- <EMAIL>devnull@localhost</EMAIL>
- </PARA>
- </SECTION>
-
- <SECTION ID="translations">
- <TITLE>Translations</TITLE>
- <PARA>
- The Bugzilla Guide needs translators!
- Please volunteer your translation into the language of your choice.
- If you will translate this Guide, please notify the members of the mozilla-webtools mailing list at
- <email>mozilla-webtools@mozilla.org</email>. Since The Bugzilla Guide is also hosted on the
- Linux Documentation Project, you would also do well to notify
- </PARA>
- </SECTION>
+ </para>
+ <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.
+ </para>
+ </section>
+
+ <section id="contributors">
+<title>Contributors</title>
+ <para>
+ Thanks go to these people for significant contributions to this
+ documentation (in no particular order):
+ </para>
+ <para>
+ Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen, Ron
+ Teitelbaum, Jacob Steenhagen, Joe Robins
+ </para>
+ </section>
+ <section id="feedback">
+ <title>Feedback</title>
+ <para>
+ I welcome feedback on this document. Without your submissions
+ and input, this Guide cannot continue to exist. Please mail
+ additions, comments, criticisms, etc. to
+ <email>barnboy@trilobyte.net</email>. Please send flames to
+ <email>devnull@localhost</email>
+ </para>
+ </section>
+
+ <section id="translations">
+ <title>Translations</title>
+ <para>
+ The Bugzilla Guide needs translators! Please volunteer your
+ translation into the language of your choice. If you will
+ translate this Guide, please notify the members of the
+ mozilla-webtools mailing list at
+ <email>mozilla-webtools@mozilla.org</email>, and arrange with
+ Matt Barnson to check it into CVS.
+ </para>
+ </section>
<!-- conventions used here (didn't want to give it a chapter of its own) -->
&conventions;
+ </chapter>
-</CHAPTER>
-
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:t
-sgml-shorttag:t
-sgml-namecase-general:t
-sgml-general-insert-case:upper
-sgml-minimize-attributes:nil
+<!-- Keep this comment at the end of the file
+Local variables:
+mode: sgml
sgml-always-quote-attributes:t
-sgml-indent-step:2
-sgml-indent-data:t
-sgml-parent-document:Bugzilla-Guide\.sgml
+sgml-auto-insert-required-elements:t
+sgml-balanced-tag-edit:t
sgml-exposed-tags:nil
+sgml-general-insert-case:lower
+sgml-indent-data:t
+sgml-indent-step:2
sgml-local-catalogs:nil
-sgml-local-ecat-files:nil
-sgml-doctype:"<!DOCTYPE chapter PUBLIC \"-//OASIS//DTD DocBook V4.1//EN\">"
-End:
--->
-
-
-
-
-
-
-
-
+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-shorttag:t
+sgml-tag-region-if-active:t
+End: -->
diff --git a/docs/sgml/administration.sgml b/docs/sgml/administration.sgml
index a35ba047d..98e726312 100644
--- a/docs/sgml/administration.sgml
+++ b/docs/sgml/administration.sgml
@@ -1,1121 +1,1458 @@
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
+<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
-<!-- TOC
-Chapter: Administration
- Localconfig and Checksetup.pl customizations
- The Email Gateway
- Editing parameters
- Deciding your site policies
- The Shadow Database
- Customizing password mail & layout
- The Whining Cron
- Why you shouldn't allow deletion
- User administration
- Creating Users
- Disabling Users
- User Permissions
- Product Administration
- Creating products
- Creating components
- Assigning default owners and Q/A contacts to components
- Product Milestones
- Product Versions
- Voting
--->
-
-<CHAPTER id="administration">
- <TITLE>Administering Bugzilla</TITLE>
-<SUBTITLE>Or, I just got this cool thing installed. Now what the heck do I do with it?</SUBTITLE>
-
-<PARA>
-So you followed the README isntructions to the letter, and
-just logged into bugzilla with your super-duper god account and you are sitting at the query
-screen. Yet, you have nothing to query. Your first act of business needs to be to setup the
-operating parameters for bugzilla.</PARA>
+<chapter id="administration">
+ <title>Administering Bugzilla</title>
+ <subtitle>
+ Or, I just got this cool thing installed. Now what the heck do I
+ do with it?
+ </subtitle>
+
+ <para>
+ So you followed <quote><xref linkend="installation"></quote> to the
+ letter, and logged into Bugzilla for the very first time with your
+ super-duper god account. You sit, contentedly staring at the
+ Bugzilla Query Screen, the worst of the whole mad business of
+ installing this terrific program behind you. It seems, though, you
+ have nothing yet to query! Your first act of business should be to
+ setup the operating parameters for Bugzilla so you can get busy
+ getting data into your bug tracker.
+ </para>
- <SECTION id="postinstall-check">
- <TITLE>Post-Installation Checklist</TITLE>
- <PARA>
- After installation, follow the checklist below to ensure that
- you have a successful installation.
- If you do not see a recommended setting for a parameter,
- consider leaving it at the default
- while you perform your initial tests on your Bugzilla setup.
- </PARA>
- <INDEXTERM>
- <PRIMARY>checklist</PRIMARY>
- </INDEXTERM>
- <PROCEDURE>
- <STEP>
- <PARA>
- Bring up "editparams.cgi" in your web browser. For instance, to edit parameters
- at mozilla.org, the URL would be <ULINK URL="http://bugzilla.mozilla.org/editparams.cgi">
- http://bugzilla.mozilla.org/editparams.cgi</ULINK>, also available under the "edit parameters"
- link on your query page.
- </PARA>
- </STEP>
- <STEP>
- <PARA>
- Set "maintainer" to <EMPHASIS>your</EMPHASIS> email address.
- This allows Bugzilla's error messages
- to display your email
+ <section id="postinstall-check">
+ <title>Post-Installation Checklist</title>
+ <para>
+ After installation, follow the checklist below to help ensure
+ that you have a successful installation. If you do not see a
+ recommended setting for a parameter, consider leaving it at the
+ default while you perform your initial tests on your Bugzilla
+ setup.
+ </para>
+ <indexterm>
+ <primary>checklist</primary>
+ </indexterm>
+ <procedure>
+ <step>
+ <para>
+ Bring up <filename>editparams.cgi</filename> in your web
+ browser. This should be available as the <quote>edit
+ parameters</quote> link from any Bugzilla screen once you
+ have logged in.
+ </para>
+ </step>
+ <step>
+ <para>The <quote>maintainer</quote> is the email address of
+ the person responsible for maintaining this Bugzilla
+ installation. The maintainer need not be a valid Bugzilla
+ user. Error pages, error emails, and administrative mail
+ will be sent with the maintainer as the return email
+ address.</para>
+ <para>
+ Set <quote>maintainer</quote> to <emphasis>your</emphasis> email address.
+ This allows Bugzilla's error messages to display your email
address and allow people to contact you for help.
- </PARA>
- </STEP>
- <STEP>
- <PARA>
- Set "urlbase" to the URL reference for your Bugzilla installation.
- If your bugzilla query page is at http://www.foo.com/bugzilla/query.cgi,
- your url base is http://www.foo.com/bugzilla/
- </PARA>
- </STEP>
- <STEP>
- <PARA>
- Set "usebuggroups" to "1" <EMPHASIS>only</EMPHASIS>
- if you need to restrict access to products.
- I suggest leaving this parameter <EMPHASIS>off</EMPHASIS>
- while initially testing your Bugzilla.
- </PARA>
- </STEP>
- <STEP>
- <PARA>
- Set "usebuggroupsentry" to "1" if you want to restrict access to products.
- Once again, if you are simply testing your installation, I suggest against
- turning this parameter on; the strict security checking may stop you from
- being able to modify your new entries.
- </PARA>
- </STEP>
- <STEP>
- <PARA>
- Set "shadowdb" to "bug_shadowdb" if you will be
- running a *very* large installation of Bugzilla.
- The shadow database enables many simultaneous users
- to read and write to the database
- without interfering with one another.
- <NOTE>
- <PARA>
+ </para>
+ </step>
+ <step>
+ <para>The <quote>urlbase</quote> parameter defines the fully
+ qualified domain name and web server path to your Bugzilla
+ installation.</para>
+ <para>
+ For example, if your bugzilla query page is
+ http://www.foo.com/bugzilla/query.cgi, set your
+ <quote>urlbase</quote> is http://www.foo.com/bugzilla/.
+ </para>
+ </step>
+ <step>
+ <para><quote>usebuggroups</quote> dictates whether or not to
+ implement group-based security for Bugzilla. If set,
+ Bugzilla bugs can have an associated groupmask defining
+ which groups of users are allowed to see and edit the
+ bug.</para>
+ <para>
+ Set "usebuggroups" to "on" <emphasis>only</emphasis> if you
+ may wish to restrict access to products. I suggest leaving
+ this parameter <emphasis>off</emphasis> while initially
+ testing your Bugzilla.
+ </para>
+ </step>
+ <step>
+ <para>
+ <quote>usebuggroupsentry</quote>, when set to
+ <quote>on</quote>, requires that all bugs have an associated
+ groupmask when submitted. This parameter is made for those
+ installations where product isolation is a necessity.
+ </para>
+ <para>
+ Set "usebuggroupsentry" to "on" if you absolutely need to
+ restrict access to bugs from the moment they are submitted
+ through resolution. Once again, if you are simply testing
+ your installation, I suggest against turning this parameter
+ on; the strict security checking may stop you from being
+ able to modify your new entries.
+ </para>
+ </step>
+ <step>
+ <para>
+ You run into an interesting problem when Bugzilla reaches a
+ high level of continuous activity. MySQL supports only
+ table-level write locking. What this means is that if
+ someone needs to make a change to a bug, they will lock the
+ entire table until the operation is complete. Locking for
+ write also blocks reads until the write is complete. The
+ <quote>shadowdb</quote> parameter was designed to get around
+ this limitation. While only a single user is allowed to
+ write to a table at a time, reads can continue unimpeded on
+ a read-only shadow copy of the database. Although your
+ database size will double, a shadow database can cause an
+ enormous performance improvement when implemented on
+ extremely high-traffic Bugzilla databases.
+ </para>
+ <para>
+ Set "shadowdb" to "bug_shadowdb" if you will be running a
+ *very* large installation of Bugzilla. The shadow database
+ enables many simultaneous users to read and write to the
+ database without interfering with one another.
+ <note>
+ <para>
Enabling "shadowdb" can adversely affect the stability
- of your installation of Bugzilla.
- You may frequently need to manually synchronize your databases,
- or schedule nightly syncs
- via "cron"
- </PARA>
- </NOTE>
- Once again, in testing you should
- avoid this option -- use it if or when you <EMPHASIS>need</EMPHASIS> to use it, and have
- repeatedly run into the problem it was designed to solve -- very long wait times while
- attempting to commit a change to the database.
- </PARA>
- <PARA>
- If you use the "shadowdb" option,
- it is only natural that you should turn the "queryagainstshadowdb"
- option "On" as well. Otherwise you are replicating data into a shadow database for no reason!
- </PARA>
- </STEP>
- <STEP>
- <PARA>
- If you have custom logos or HTML you must put in place to fit within your site design guidelines,
- place the code in the "headerhtml", "footerhtml", "errorhtml",
- "bannerhtml", or "blurbhtml" text boxes.
- <NOTE>
- <PARA>
+ of your installation of Bugzilla. You should regularly
+ check that your database is in sync. It is often
+ advisable to force a shadow database sync nightly via
+ <quote>cron</quote>.
+ </para>
+ </note> Once again, in testing you should avoid this option
+ -- use it if or when you <emphasis>need</emphasis> to use
+ it, and have repeatedly run into the problem it was designed
+ to solve -- very long wait times while attempting to commit
+ a change to the database. Mozilla.org began needing
+ <quote>shadowdb</quote> when they reached around 40,000
+ Bugzilla users with several hundred Bugzilla bug changes and
+ comments per day.
+ </para>
+ <para>
+ If you use the "shadowdb" option, it is only natural that
+ you should turn the "queryagainstshadowdb" option "On" as
+ well. Otherwise you are replicating data into a shadow
+ database for no reason!
+ </para>
+ </step>
+ <step>
+ <para><quote>headerhtml</quote>, <quote>footerhtml</quote>,
+ <quote>errorhtml</quote>, <quote>bannerhtml</quote>, and
+ <quote>blurbhtml</quote> are all templates which control
+ display of headers, footers, errors, banners, and additional
+ data. We could go into some detail regarding the usage of
+ these, but it is really best just to monkey around with them
+ a bit to see what they do. I strongly recommend you copy
+ your <filename>data/params</filename> file somewhere safe
+ before playing with these values, though. If they are
+ changed dramatically, it may make it impossible for you to
+ display Bugzilla pages to fix the problem until you have
+ restored your <filename>data/params</filename> file.</para>
+ <para>
+ If you have custom logos or HTML you must put in place to
+ fit within your site design guidelines, place the code in
+ the "headerhtml", "footerhtml", "errorhtml", "bannerhtml",
+ or "blurbhtml" text boxes.
+ <note>
+ <para>
The "headerhtml" text box is the HTML printed out
- <EMPHASIS>before</EMPHASIS> any other code on the page.
- If you have a special banner, put the code for it in "bannerhtml".
- You may want to leave these
- settings at the defaults initially.
- </PARA>
- </NOTE>
- </PARA>
- </STEP>
- <STEP>
- <PARA>
- Add any text you wish to the "passwordmail" parameter box. For instance,
- many people choose to use this box to give a quick training blurb about how to
- use Bugzilla at your site.
- </PARA>
- </STEP>
- <STEP>
- <PARA>
- Ensure "newemailtech" is "on".
- Your users will thank you. This is the default in the post-2.12 world, and is
- only an issue if you are upgrading.
- </PARA>
- </STEP>
- <STEP>
- <PARA>
- Do you want to use the qa contact ("useqacontact")
- and status whiteboard ("usestatuswhiteboard") fields?
- These fields are useful because they allow for more flexibility,
- particularly when you have an existing
- Quality Assurance and/or Release Engineering team,
- but they may not be needed for smaller installations.
- </PARA>
- </STEP>
- <STEP>
- <PARA>
- Set "whinedays" to the amount of days you want to let bugs go
- in the "New" or "Reopened" state before
- notifying people they have untouched new bugs. If you do not plan to use this feature, simply do
- not set up the whining cron job described in the README, or set this value to "0".
- </PARA>
- </STEP>
- <STEP>
- <PARA>
+ <emphasis>before</emphasis> any other code on the page,
+ except the CONTENT-TYPE header sent by the Bugzilla
+ engine. If you have a special banner, put the code for
+ it in "bannerhtml". You may want to leave these settings
+ at the defaults initially.
+ </para>
+ </note>
+ </para>
+ </step>
+ <step>
+ <para><quote>passwordmail</quote> is rather simple. Every
+ time a user creates an account, the text of this parameter
+ is read as the text to send to the new user along with their
+ password message.</para>
+ <para>
+ Add any text you wish to the "passwordmail" parameter box.
+ For instance, many people choose to use this box to give a
+ quick training blurb about how to use Bugzilla at your site.
+ </para>
+ </step>
+ <step>
+ <para><quote>useqacontact</quote> allows you to define an
+ email address for each component, in addition to that of the
+ default owner, who will be sent carbon copies of incoming
+ bugs. The critical difference between a QA Contact and an
+ Owner is that the QA Contact follows the component. If you
+ reassign a bug from component A to component B, the QA
+ Contact for that bug will change with the reassignment,
+ regardless of owner.</para>
+ <para><quote>usestatuswhiteboard</quote> defines whether you
+ wish to have a free-form, overwritable field associated with
+ each bug. The advantage of the Status Whiteboard is that it
+ can be deleted or modified with ease, and provides an
+ easily-searchable field for indexing some bugs that have
+ some trait in common. Many people will put <quote>help
+ wanted</quote>, <quote>stalled</quote>, or <quote>waiting
+ on reply from somebody</quote> messages into the Status
+ Whiteboard field so those who peruse the bugs are aware of
+ their status even more than that which can be indicated by
+ the Resolution fields.</para>
+ <para>
+ Do you want to use the QA Contact ("useqacontact") and
+ status whiteboard ("usestatuswhiteboard") fields? These
+ fields are useful because they allow for more flexibility,
+ particularly when you have an existing Quality Assurance
+ and/or Release Engineering team, but they may not be needed
+ for many smaller installations.
+ </para>
+ </step>
+ <step>
+ <para>
+ Set "whinedays" to the amount of days you want to let bugs
+ go in the "New" or "Reopened" state before notifying people
+ they have untouched new bugs. If you do not plan to use
+ this feature, simply do not set up the whining cron job
+ described in the installation instructions, or set this
+ value to "0" (never whine).
+ </para>
+ </step>
+ <step>
+ <para><quote>commenton</quote> fields allow you to dictate
+ what changes can pass without comment, and which must have a
+ comment from the person who changed them. Often,
+ administrators will allow users to add themselves to the CC
+ list, accept bugs, or change the Status Whiteboard without
+ adding a comment as to their reasons for the change, yet
+ require that most other changes come with an
+ explanation.</para>
+ <para>
Set the "commenton" options according to your site policy.
- It is a wise idea to require comments when users
- resolve, reassign, or reopen bugs.
- <NOTE>
- <PARA>
- It is generally far better to require a developer comment when resolving bugs than not.
- Few things are more annoying to bug database users than having a developer
- mark a bug "fixed" without any comment as to what the fix was (or even that it was truly fixed!)
- </PARA>
- </NOTE>
- </PARA>
- </STEP>
- <STEP>
- <PARA>
- Set "supportwatchers" to "On". This feature is helpful for team leads to monitor progress in their
- respective areas, and can offer many other benefits, such as allowing a developer to pick up a
- former engineer's bugs without requiring her to change all the information in the bug.
- </PARA>
- </STEP>
- </PROCEDURE>
- </SECTION>
+ It is a wise idea to require comments when users resolve,
+ reassign, or reopen bugs at the very least.
+ <note>
+ <para>
+ It is generally far better to require a developer
+ comment when resolving bugs than not. Few things are
+ more annoying to bug database users than having a
+ developer mark a bug "fixed" without any comment as to
+ what the fix was (or even that it was truly fixed!)
+ </para>
+ </note>
+ </para>
+ </step>
+ <step>
+ <para>The <quote>supportwatchers</quote> option can be an
+ exceptionally powerful tool in the hands of a power Bugzilla
+ user. By enabling this option, you allow users to receive
+ email updates whenever other users receive email updates.
+ This is, of course, subject to the groupset restrictions on
+ the bug; if the <quote>watcher</quote> would not normally be
+ allowed to view a bug, the watcher cannot get around the
+ system by setting herself up to watch the bugs of someone
+ with bugs outside her priveleges. She would still only
+ receive email updates for those bugs she could normally
+ view.</para>
+ <para>For Bugzilla sites which require strong inter-Product
+ security to prevent snooping, watchers are not a good
+ idea.</para>
+ <para>
+ However, for most sites you should set
+ <quote>supportwatchers</quote> to "On". This feature is
+ helpful for team leads to monitor progress in their
+ respective areas, and can offer many other benefits, such as
+ allowing a developer to pick up a former engineer's bugs
+ without requiring her to change all the information in the
+ bug.
+ </para>
+ </step>
+ </procedure>
+ </section>
- <SECTION id="useradmin">
- <TITLE>User Administration</TITLE>
- <PARA>
+ <section id="useradmin">
+ <title>User Administration</title>
+ <para>
User administration is one of the easiest parts of Bugzilla.
- Keeping it from getting out of hand, however, can become a challenge.
- </PARA>
+ Keeping it from getting out of hand, however, can become a
+ challenge.
+ </para>
- <SECTION id="defaultuser">
- <TITLE>Creating the Default User</TITLE>
+ <section id="defaultuser">
+ <title>Creating the Default User</title>
- <PARA>
- 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 were to delete the "super user" account, re-running
- checksetup.pl will again prompt you for this username and password.
- </PARA>
- <TIP>
- <PARA>
- If you wish to add more administrative users, you must use the MySQL interface.
- Run "mysql" from the command line, and use these commands ("mysql>" denotes the
- mysql prompt, not something you should type in):
- <COMMAND><PROMPT>mysql></PROMPT> use bugs;</COMMAND>
- <COMMAND><PROMPT>mysql></PROMPT> update profiles set groupset=0x7ffffffffffffff
- where login_name = "(user's login name)"; </COMMAND>
- </PARA>
- </TIP>
- </SECTION>
+ <para>
+ 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 were to delete the "super user" account, re-running
+ checksetup.pl will again prompt you for this username and
+ password.
+ </para>
+ <tip>
+ <para>
+ If you wish to add more administrative users, you must use the
+ MySQL interface. Run "mysql" from the command line, and use
+ these commands ("mysql>" denotes the mysql prompt, not
+ something you should type in):
+ <command><prompt>mysql></prompt> use bugs;</command>
+ <command><prompt>mysql></prompt> update profiles set
+ groupset=0x7ffffffffffffff where login_name = "(user's
+ login name)"; </command>
+ </para>
+ <para>Yes, that is <emphasis>fourteen</emphasis>
+ <quote>f</quote>'s. A whole lot of f-ing going on if you
+ want to create a new administator.</para>
+ </tip>
+ </section>
- <SECTION id="manageusers">
- <TITLE>Managing Other Users</TITLE>
+ <section id="manageusers">
+ <title>Managing Other Users</title>
- <SECTION id="login">
- <TITLE>Logging In</TITLE>
- <ORDEREDLIST>
- <LISTITEM>
- <PARA>
- Open the index.html page for your Bugzilla installation in your browser window.
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
+ <section id="login">
+ <title>Logging In</title>
+ <orderedlist>
+ <listitem>
+ <para>
+ Open the index.html page for your Bugzilla installation
+ in your browser window.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
Click the "Query Existing Bug Reports" link.
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
Click the "Log In" link at the foot of the page.
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- Type your email address, and the password which was emailed to you when you
- created your Bugzilla account, into the spaces provided.
- </PARA>
- </LISTITEM>
- </ORDEREDLIST>
- <PARA>Congratulations, you are logged in!</PARA>
- </SECTION>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Type your email address, and the password which was
+ emailed to you when you created your Bugzilla account,
+ into the spaces provided.
+ </para>
+ </listitem>
+ </orderedlist>
+ <para>Congratulations, you are logged in!</para>
+ </section>
- <SECTION id="createnewusers">
- <TITLE>Creating new users</TITLE>
- <PARA>
- Your users can create their own user accounts by clicking the "New Account"
- link at the bottom of each page.
- However, should you desire to create user accounts ahead of time, here is how you do it.
- </PARA>
- <ORDEREDLIST>
- <LISTITEM>
- <PARA>
- After logging in, click the "Users" link at the footer of the query page.
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- To see a specific user, type a portion of their login name
- in the box provided and click "submit".
- To see all users, simply click the "submit" button.
- You must click "submit" here to be able to add a new user.
- </PARA>
- <TIP>
- <PARA>
- More functionality is available via the list on the right-hand side
- of the text entry box.
- You can match what you type as a case-insensitive substring (the default)
- of all users on your system, a case-sensitive regular expression
- (please see the "man regexp" manual page for details on regular expression syntax),
- or a <EMPHASIS>reverse</EMPHASIS> regular expression match,
- where every user name which does NOT match the regular expression
- is selected.
- </PARA>
- </TIP>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- Click the "Add New User" link at the bottom of the user list
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- Fill out the form presented. This page is self-explanatory. When done, click "submit".
- </PARA>
- <NOTE>
- <PARA>
- Adding a user this way will <EMPHASIS>not</EMPHASIS> send an email
- informing them of their username and password.
- In general, it is preferable to log out and use the "New Account"
- button to create users, as it will pre-populate all the required fields and also notify
- the user of her account name and password.
- </PARA>
- </NOTE>
- </LISTITEM>
- </ORDEREDLIST>
- </SECTION>
+ <section id="createnewusers">
+ <title>Creating new users</title>
+ <para>
+ Your users can create their own user accounts by clicking
+ the "New Account" link at the bottom of each page. However,
+ should you desire to create user accounts ahead of time,
+ here is how you do it.
+ </para>
+ <orderedlist>
+ <listitem>
+ <para>
+ After logging in, click the "Users" link at the footer
+ of the query page.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ To see a specific user, type a portion of their login
+ name in the box provided and click "submit". To see all
+ users, simply click the "submit" button. You must click
+ "submit" here to be able to add a new user.
+ </para>
+ <tip>
+ <para>
+ More functionality is available via the list on the
+ right-hand side of the text entry box. You can match
+ what you type as a case-insensitive substring (the
+ default) of all users on your system, a case-sensitive
+ regular expression (please see the <command>man
+ regexp</command> manual page for details on regular
+ expression syntax), or a <emphasis>reverse</emphasis>
+ regular expression match, where every user name which
+ does NOT match the regular expression is selected.
+ </para>
+ </tip>
+ </listitem>
+ <listitem>
+ <para>
+ Click the "Add New User" link at the bottom of the user
+ list
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Fill out the form presented. This page is
+ self-explanatory. When done, click "submit".
+ </para>
+ <note>
+ <para>
+ Adding a user this way will <emphasis>not</emphasis>
+ send an email informing them of their username and
+ password. While useful for creating dummy accounts
+ (watchers which shuttle mail to another system, for
+ instance, or email addresses which are a mailing
+ list), in general it is preferable to log out and use
+ the <quote>New Account</quote> button to create users,
+ as it will pre-populate all the required fields and
+ also notify the user of her account name and
+ password.
+ </para>
+ </note>
+ </listitem>
+ </orderedlist>
+ </section>
- <SECTION id="disableusers">
- <TITLE>Disabling Users</TITLE>
- <PARA>
- I bet you noticed that big "Disabled Text" entry box available from the "Add New User" screen,
- when you edit an account?
- By entering any text in this box and selecting "submit",
- you have prevented the user from using Bugzilla via the web interface.
- Your explanation, written in this text box, will be presented to the user
- the next time she attempts to use the system.
- <WARNING>
- <PARA>
- Don't disable your own administrative account, or you will hate life!
- </PARA>
- </WARNING>
- </PARA>
- </SECTION>
+ <section id="disableusers">
+ <title>Disabling Users</title>
+ <para>
+ I bet you noticed that big "Disabled Text" entry box
+ available from the "Add New User" screen, when you edit an
+ account? By entering any text in this box and selecting
+ "submit", you have prevented the user from using Bugzilla
+ via the web interface. Your explanation, written in this
+ text box, will be presented to the user the next time she
+ attempts to use the system.
+ <warning>
+ <para>
+ Don't disable your own administrative account, or you
+ will hate life!
+ </para>
+ <para>At this time, <quote>Disabled Text</quote> does not
+ prevent a user from using the email interface. If you
+ have the email interface enabled, they can still
+ continue to submit bugs and comments that way. We need
+ a patch to fix this.</para>
+ </warning>
+ </para>
+ </section>
- <SECTION id="modifyusers">
- <TITLE>Modifying Users</TITLE>
- <PARA>
- Here I will attempt to describe the function of each option on the user edit screen.
- </PARA>
- <ITEMIZEDLIST>
- <LISTITEM>
- <PARA>
- <EMPHASIS>Login Name</EMPHASIS>: This is generally the user's email address.
- However, if you have edited your system parameters,
- this may just be the user's login name or some other identifier.
- <TIP>
- <PARA>
- For compatability reasons, you should probably
- stick with email addresses as user login names. It will make your life easier.
- </PARA>
- </TIP>
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- <EMPHASIS>Real Name</EMPHASIS>: Duh!
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- <EMPHASIS>Password</EMPHASIS>: You will only see asterisks in versions
- of Bugzilla newer than 2.10 or early 2.11. You can change the user password here.
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- <EMPHASIS>Email Notification</EMPHASIS>: You may choose from one of three options:
- <ORDEREDLIST>
- <LISTITEM>
- <PARA>
+ <section id="modifyusers">
+ <title>Modifying Users</title>
+ <para>
+ Here I will attempt to describe the function of each option
+ on the Edit User screen.
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis>Login Name</emphasis>: This is generally the
+ user's email address. However, if you have edited your
+ system parameters, this may just be the user's login
+ name or some other identifier.
+ <tip>
+ <para>
+ For compatability reasons, you should probably stick
+ with email addresses as user login names. It will
+ make your life easier.
+ </para>
+ </tip>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>Real Name</emphasis>: Duh!
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>Password</emphasis>: You can change the user
+ password here. It is normal to only see asterisks.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>Email Notification</emphasis>: You may choose
+ from one of three options:
+ <orderedlist>
+ <listitem>
+ <para>
All qualifying bugs except those which I change:
The user will be notified of any change to any bug
- for which she is the reporter, assignee, Q/A contact, CC recipient, or "watcher".
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
+ for which she is the reporter, assignee, QA
+ Contact, CC recipient, or "watcher".
+ </para>
+ </listitem>
+ <listitem>
+ <para>
Only those bugs which I am listed on the CC line:
- The user will not be notified of changes to bugs where she is the assignee,
- reporter, or Q/A contact, but will receive them if she is on the CC list.
- <NOTE>
- <PARA>
- She will still receive whining cron emails if you set up the "whinemail" feature.
- </PARA>
- </NOTE>
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- <EMPHASIS>All Qualifying Bugs</EMPHASIS>: This user is a glutton for punishment.
- If her name is in the reporter, Q/A contact, CC, assignee, or is a "watcher",
- she will get email updates regarding the bug.
- </PARA>
- </LISTITEM>
- </ORDEREDLIST>
-</PARA>
- <PARA>
- <EMPHASIS>Disable Text</EMPHASIS>: If you type anything in this box,
- including just a space, the user account is disabled from making any changes
- to bugs via the web interface, and what you type in this box is presented as the reason.
- <WARNING>
- <PARA>Don't disable the administrator account!</PARA>
- </WARNING>
- <NOTE>
- <PARA>
- As of this writing, the user can still submit bugs via the e-mail gateway,
- if you set it up, despite the disabled text field. The e-mail gateway should
- <EMPHASIS>not</EMPHASIS> be enabled for secure installations of Bugzilla.
- </PARA>
- </NOTE>
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- <EMPHASIS>CanConfirm</EMPHASIS>: This field is only used if you have enabled
- "unconfirmed" status in your parameters screen. If you enable this for a user,
- that user can then move bugs from "Unconfirmed" to "Confirmed" status (ergo: "New" status).
- Be judicious about allowing users to turn this bit on for other users.
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- <EMPHASIS>Creategroups</EMPHASIS>: This option will allow a user to create and
- destroy groups in Bugzilla. Unless you are using the Bugzilla GroupSentry security
- option "usebuggroupsentry" in your parameters, this setting has no effect.
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- <EMPHASIS>Editbugs</EMPHASIS>: Unless a user has this bit set, they can only edit
- those bugs for which they are the assignee or the reporter.
- <NOTE>
- <PARA>
- Leaving this option unchecked does not prevent users from adding
- comments to a bug! They simply cannot change a bug priority, severity,
- etc. unless they are the assignee or reporter.
- </PARA>
- </NOTE>
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- <EMPHASIS>Editcomponents</EMPHASIS>: This flag allows a user to create new
- products and components, as well as modify and destroy those that have no bugs
- associated with them. If a product or component has bugs associated with it,
- those bugs must be moved to a different product or component before Bugzilla
- will allow them to be destroyed. The name of a product or component can be
- changed without affecting the associated bugs, but it tends to annoy
- the hell out of your users when these change a lot.
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- <EMPHASIS>Editkeywords</EMPHASIS>: If you use Bugzilla's keyword functionality,
- enabling this feature allows a user can create and destroy keywords.
- As always, the keywords for existing bugs containing the keyword
- the user wishes to destroy must be changed before Bugzilla will allow it to die.
- You must be very careful about creating too many new keywords
- if you run a very large Bugzilla installation; keywords are global variables
- across products, and you can often run into a phenomenon called "keyword bloat".
- This confuses users, and then the feature goes unused.
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- <EMPHASIS>Editusers</EMPHASIS>: This flag allows a user do what you're doing
- right now: edit other users.
- This will allow those with the right to do so to remove administrator
- priveleges from other users or grant them to themselves. Enable with care.
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- <EMPHASIS>PRODUCT</EMPHASIS>: PRODUCT bugs access. This allows an administrator,
- with product-level granularity, to specify in which products a user can edit bugs.
- The user must still have the "editbugs" privelege to edit bugs in this area;
- this simply restricts them from even seeing bugs outside these boundaries if the administrator
- has enabled the group sentry parameter "usebuggroupsentry". Unless you are using bug groups,
+ The user will not be notified of changes to bugs
+ where she is the assignee, reporter, or QA
+ Contact, but will receive them if she is on the CC
+ list.
+ <note>
+ <para>
+ She will still receive whining cron emails if
+ you set up the "whinemail" feature.
+ </para>
+ </note>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>All Qualifying Bugs</emphasis>: This
+ user is a glutton for punishment. If her name is
+ in the reporter, QA Contact, CC, assignee, or is a
+ "watcher", she will get email updates regarding
+ the bug.
+ </para>
+ </listitem>
+ </orderedlist>
+</para>
+ <para>
+ <emphasis>Disable Text</emphasis>: If you type anything
+ in this box, including just a space, the user account is
+ disabled from making any changes to bugs via the web
+ interface, and what you type in this box is presented as
+ the reason.
+ <warning>
+ <para>Don't disable the administrator account!</para>
+ </warning>
+ <note>
+ <para>
+ As of this writing, the user can still submit bugs
+ via the e-mail gateway, if you set it up, despite
+ the disabled text field. The e-mail gateway should
+ <emphasis>not</emphasis> be enabled for secure
+ installations of Bugzilla.
+ </para>
+ </note>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>CanConfirm</emphasis>: This field is only used
+ if you have enabled "unconfirmed" status in your
+ parameters screen. If you enable this for a user, that
+ user can then move bugs from "Unconfirmed" to
+ "Confirmed" status (e.g.: "New" status). Be judicious
+ about allowing users to turn this bit on for other
+ users.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>Creategroups</emphasis>: This option will
+ allow a user to create and destroy groups in Bugzilla.
+ Unless you are using the Bugzilla GroupSentry security
+ option "usebuggroupsentry" in your parameters, this
+ setting has no effect.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>Editbugs</emphasis>: Unless a user has this
+ bit set, they can only edit those bugs for which they
+ are the assignee or the reporter.
+ <note>
+ <para>
+ Leaving this option unchecked does not prevent users
+ from adding comments to a bug! They simply cannot
+ change a bug priority, severity, etc. unless they
+ are the assignee or reporter.
+ </para>
+ </note>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>Editcomponents</emphasis>: This flag allows a
+ user to create new products and components, as well as
+ modify and destroy those that have no bugs associated
+ with them. If a product or component has bugs
+ associated with it, those bugs must be moved to a
+ different product or component before Bugzilla will
+ allow them to be destroyed. The name of a product or
+ component can be changed without affecting the
+ associated bugs, but it tends to annoy the hell out of
+ your users when these change a lot.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>Editkeywords</emphasis>: If you use Bugzilla's
+ keyword functionality, enabling this feature allows a
+ user can create and destroy keywords. As always, the
+ keywords for existing bugs containing the keyword the
+ user wishes to destroy must be changed before Bugzilla
+ will allow it to die. You must be very careful about
+ creating too many new keywords if you run a very large
+ Bugzilla installation; keywords are global variables
+ across products, and you can often run into a phenomenon
+ called "keyword bloat". This confuses users, and then
+ the feature goes unused.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>Editusers</emphasis>: This flag allows a user
+ do what you're doing right now: edit other users. This
+ will allow those with the right to do so to remove
+ administrator priveleges from other users or grant them
+ to themselves. Enable with care.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>PRODUCT</emphasis>: PRODUCT bugs access. This
+ allows an administrator, with product-level granularity,
+ to specify in which products a user can edit bugs. The
+ user must still have the "editbugs" privelege to edit
+ bugs in this area; this simply restricts them from even
+ seeing bugs outside these boundaries if the
+ administrator has enabled the group sentry parameter
+ "usebuggroupsentry". Unless you are using bug groups,
this option has no effect.
- </PARA>
- </LISTITEM>
- </ITEMIZEDLIST>
- </SECTION>
- </SECTION>
- </SECTION>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
+ </section>
+ </section>
- <SECTION id="programadmin">
- <TITLE>Product, Component, Milestone, and Version Administration</TITLE>
- <EPIGRAPH>
- <PARA>
+ <section id="programadmin">
+ <title>Product, Component, Milestone, and Version
+ Administration</title>
+ <epigraph>
+ <para>
Dear Lord, we have to get our users to do WHAT?
- </PARA>
- </EPIGRAPH>
+ </para>
+ </epigraph>
- <SECTION id="products">
- <TITLE>Products</TITLE>
- <SUBTITLE>Formerly, and in some spots still, called "Programs"</SUBTITLE>
- <PARA>
- <GLOSSTERM baseform="product" linkend="gloss_product">Products</GLOSSTERM> are the
- broadest category in Bugzilla, and you should have the least of these.
- If your company makes computer games, you should have one product per game,
- and possibly a few special products
- (website, meetings...)
- </PARA>
- <PARA>
- A Product (formerly called "Program", and still referred to that way
- in some portions of the source code) controls some very important functions.
- The number of "votes" available for users to vote for the most important bugs
- is set per-product, as is the number of votes required to move a bug automatically
- from the UNCONFIRMED status to the NEW status. One can close a Product for further
- bug entry and define various Versions available from the Edit Product screen.
- </PARA>
- <PARA>To create a new product:</PARA>
- <ORDEREDLIST>
- <LISTITEM>
- <PARA>
+ <section id="products">
+ <title>Products</title>
+ <subtitle>Formerly, and in some spots still, called
+ "Programs"</subtitle>
+ <para>
+ <glossterm linkend="gloss_product" baseform="product">Products</glossterm> are
+ the broadest category in Bugzilla, and you should have the
+ least of these. If your company makes computer games, you
+ should have one product per game, and possibly a few special
+ products (website, meetings...)
+ </para>
+ <para>
+ A Product (formerly called "Program", and still referred to
+ that way in some portions of the source code) controls some
+ very important functions. The number of "votes" available for
+ users to vote for the most important bugs is set per-product,
+ as is the number of votes required to move a bug automatically
+ from the UNCONFIRMED status to the NEW status. One can close
+ a Product for further bug entry and define various Versions
+ available from the Edit product screen.
+ </para>
+ <para>To create a new product:</para>
+ <orderedlist>
+ <listitem>
+ <para>
Select "components" from the yellow footer
- </PARA>
- <TIP>
- <PARA>
- It may seem counterintuitive to click "components" when you want
- to edit the properties associated with Products. This is one of a long
- list of things we want in Bugzilla 3.0...
- </PARA>
- </TIP>
- </LISTITEM>
- <LISTITEM>
- <PARA>
+ </para>
+ <tip>
+ <para>
+ It may seem counterintuitive to click "components" when
+ you want to edit the properties associated with
+ Products. This is one of a long list of things we want
+ in Bugzilla 3.0...
+ </para>
+ </tip>
+ </listitem>
+ <listitem>
+ <para>
Select the "Add" link to the right of "Add a new product".
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- Enter the name of the product and a description.
- The Description field is free-form.
- </PARA>
- </LISTITEM>
- </ORDEREDLIST>
- <TIP>
- <PARA>
- Don't worry about the "Closed for bug entry", "Maximum Votes per person",
- "Maximum votes a person can put on a single bug", "Number of votes a bug in
- this Product needs to automatically get out of the UNCOMFIRMED state",
- and "Version" options yet.
- We'll cover those in a few moments.
- </PARA>
- </TIP>
- </SECTION>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Enter the name of the product and a description. The
+ Description field is free-form.
+ </para>
+ </listitem>
+ </orderedlist>
+ <tip>
+ <para>
+ Don't worry about the "Closed for bug entry", "Maximum Votes
+ per person", "Maximum votes a person can put on a single
+ bug", "Number of votes a bug in this Product needs to
+ automatically get out of the UNCOMFIRMED state", and
+ "Version" options yet. We'll cover those in a few moments.
+ </para>
+ </tip>
+ </section>
- <SECTION id="components">
- <TITLE>Components</TITLE>
- <PARA>
+ <section id="components">
+ <title>Components</title>
+ <para>
Components are subsections of a Product.
- <EXAMPLE>
- <TITLE>Creating some Components</TITLE>
- <INFORMALEXAMPLE>
- <PARA>
- The computer game you are designing may 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.
- </PARA>
- </INFORMALEXAMPLE>
- </EXAMPLE>
-
- 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
- <EMPHASIS>default assignments</EMPHASIS>; the Owner and Q/A Contact fields in a bug
- are otherwise unrelated to the Component.
- </PARA>
+ <example>
+ <title>Creating some Components</title>
+ <informalexample>
+ <para>
+ 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.
+ </para>
+ </informalexample>
+ </example> 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 <emphasis>default assignments</emphasis>; the
+ Owner and QA Contact fields in a bug are otherwise unrelated
+ to the Component.
+ </para>
- <PARA>
+ <para>
To create a new Component:
- </PARA>
- <ORDEREDLIST>
- <LISTITEM>
- <PARA>
- Select the "Edit components" link from the "Edit Product" page
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- Select the "Add" link to the right of the "Add a new component" text
- on the "Select Component" page.
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- Fill out the "Component" field, a short "Description", and the "Initial Owner".
- The "Component" field should not contain a space. The "Description" field is
- free-form. The "Initial Owner" field must be that of a valid user already
- existing in the database. If the initial owner does not exist, Bugzilla
- will refuse to create the component.
- <TIP>
- <PARA>
- Is your "Default Owner" a user who is not yet in the database?
- No problem.
- <ORDEREDLIST>
- <LISTITEM>
- <PARA>
- Select the "Log out" link on the footer of the page.
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- Select the "New Account" link on the footer of the "Relogin" page
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- Type in the email address of the default owner you want to create
- in the "E-mail address" field, and her full name in the "Real name"
+ </para>
+ <orderedlist>
+ <listitem>
+ <para>
+ Select the "Edit components" link from the "Edit product"
+ page
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Select the "Add" link to the right of the "Add a new
+ component" text on the "Select Component" page.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Fill out the "Component" field, a short "Description", and
+ the "Initial Owner". The Component and Description fields
+ are free-form; the "Initial Owner" field must be that of a
+ user ID already existing in the database. If the initial
+ owner does not exist, Bugzilla will refuse to create the
+ component.
+ <tip>
+ <para>
+ Is your "Default Owner" a user who is not yet in the
+ database? No problem.
+ <orderedlist>
+ <listitem>
+ <para>
+ Select the "Log out" link on the footer of the
+ page.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Select the "New Account" link on the footer of
+ the "Relogin" page
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Type in the email address of the default owner
+ you want to create in the "E-mail address"
+ field, and her full name in the "Real name"
field, then select the "Submit Query" button.
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- Now select "Log in" again, type in your login information, and you
- can modify the product to use the Default Owner information
- you require.
- </PARA>
- </LISTITEM>
- </ORDEREDLIST>
- </PARA>
- </TIP>
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- Either "edit" more components or return to the "query" page on the ensuing
- "Addming new component" page. To return to the Product you were editing, you
- must select the "components" link as before.
- </PARA>
- </LISTITEM>
- </ORDEREDLIST>
- </SECTION>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Now select "Log in" again, type in your login
+ information, and you can modify the product to
+ use the Default Owner information you require.
+ </para>
+ </listitem>
+ </orderedlist>
+ </para>
+ </tip>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Either Edit more components or return to the Bugzilla
+ Query Page. To return to the Product you were editing, you
+ must select the Components link as before.
+ </para>
+ </listitem>
+ </orderedlist>
+ </section>
- <SECTION id="versions">
- <TITLE>Versions</TITLE>
- <PARA>
- Versions are the revisions of the product, such as "Flinders 3.1", "Flinders 95",
- and "Flinders 2000". Using Versions helps you isolate code changes and are an aid
- in reporting.
+ <section id="versions">
+ <title>Versions</title>
+ <para>
+ Versions are the revisions of the product, such as "Flinders
+ 3.1", "Flinders 95", and "Flinders 2000". Using Versions
+ helps you isolate code changes and are an aid in reporting.
- <EXAMPLE>
- <TITLE>Common Use of Versions</TITLE>
- <INFORMALEXAMPLE>
- <PARA>
- A user reports a bug
- against Version "Beta 2.0" of your product. The current Version of your software
- is "Release Candidate 1", and no longer has the bug. This will
- help you triage and classify bugs according to their relevance. It is also
- possible people may report bugs against bleeding-edge beta versions that are
- not evident in older versions of the software. This can help isolate code
- changes that caused the bug
- </PARA>
- </INFORMALEXAMPLE>
- </EXAMPLE>
- <EXAMPLE>
- <TITLE>A Different Use of Versions</TITLE>
- <INFORMALEXAMPLE>
- <PARA>
- This field has been used to good effect by an online service provider in a slightly
- different way. They had three versions of the product: "Production", "QA",
- and "Dev". Although it may be the same product, a bug in the development
- environment is not normally as critical as a Production bug, nor does it
- need to be reported publicly. When used in conjunction with Target Milestones,
- one can easily specify the environment where a bug can be reproduced, and
- the Milestone by which it will be fixed.
- </PARA>
- </INFORMALEXAMPLE>
- </EXAMPLE>
- </PARA>
- <PARA>
+ <example>
+ <title>Common Use of Versions</title>
+ <informalexample>
+ <para>
+ A user reports a bug against Version "Beta 2.0" of your
+ product. The current Version of your software is
+ "Release Candidate 1", and no longer has the bug. This
+ will help you triage and classify bugs according to
+ their relevance. It is also possible people may report
+ bugs against bleeding-edge beta versions that are not
+ evident in older versions of the software. This can
+ help isolate code changes that caused the bug
+ </para>
+ </informalexample>
+ </example>
+ <example>
+ <title>A Different Use of Versions</title>
+ <informalexample>
+ <para>
+ This field has been used to good effect by an online
+ service provider in a slightly different way. They had
+ three versions of the product: "Production", "QA", and
+ "Dev". Although it may be the same product, a bug in
+ the development environment is not normally as critical
+ as a Production bug, nor does it need to be reported
+ publicly. When used in conjunction with Target
+ Milestones, one can easily specify the environment where
+ a bug can be reproduced, and the Milestone by which it
+ will be fixed.
+ </para>
+ </informalexample>
+ </example>
+ </para>
+ <para>
To create and edit Versions:
- </PARA>
- <ORDEREDLIST>
- <LISTITEM>
- <PARA>
- From the "Edit Product" screen, select "Edit Versions"
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- You will notice that the product already has the default version "undefined".
- If your product doesn't use version numbers, you may want to leave this as it is
- or edit it so that it is "---". You can then go back to the edit versions page
- and add new versions to your product.
- </PARA>
- <PARA>
- Otherwise, click the "Add" button to the right of the "Add a new version" text.
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- Enter the name of the Version. This can be free-form characters up to the limit of the
- text box. Then select the "Add" button.
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- At this point you can select "Edit" to edit more Versions, or return to the "Query"
- page, from which you can navigate back to the product through the "components" link
- at the foot of the Query page.
- </PARA>
- </LISTITEM>
- </ORDEREDLIST>
- </SECTION>
+ </para>
+ <orderedlist>
+ <listitem>
+ <para>
+ From the "Edit product" screen, select "Edit Versions"
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ You will notice that the product already has the default
+ version "undefined". If your product doesn't use version
+ numbers, you may want to leave this as it is or edit it so
+ that it is "---". You can then go back to the edit
+ versions page and add new versions to your product.
+ </para>
+ <para>
+ Otherwise, click the "Add" button to the right of the "Add
+ a new version" text.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Enter the name of the Version. This can be free-form
+ characters up to the limit of the text box. Then select
+ the "Add" button.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ At this point you can select "Edit" to edit more Versions,
+ or return to the "Query" page, from which you can navigate
+ back to the product through the "components" link at the
+ foot of the Query page.
+ </para>
+ </listitem>
+ </orderedlist>
+ </section>
- <SECTION id="milestones">
- <TITLE>Milestones</TITLE>
- <PARA>
- 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. Or, you have a
- bug that you plan to fix for 2.8, this would have a milestone of 2.8.
- </PARA>
- <NOTE>
- <PARA>
- Milestone options will only appear for a Product if you turned the "usetargetmilestone" field
- in the "Edit Parameters" screen "On".
- </PARA>
- </NOTE>
- <PARA>
- To create new Milestones, set Default Milestones, and set Milestone URL:
- </PARA>
- <ORDEREDLIST>
- <LISTITEM>
- <PARA>
+ <section id="milestones">
+ <title>Milestones</title>
+ <para>
+ 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. Or, you
+ have a bug that you plan to fix for 2.8, this would have a
+ milestone of 2.8.
+ </para>
+ <note>
+ <para>
+ Milestone options will only appear for a Product if you
+ turned the "usetargetmilestone" field in the "Edit
+ Parameters" screen "On".
+ </para>
+ </note>
+ <para>
+ To create new Milestones, set Default Milestones, and set
+ Milestone URL:
+ </para>
+ <orderedlist>
+ <listitem>
+ <para>
Select "edit milestones"
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- Select "Add" to the right of the "Add a new milestone" text
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Select "Add" to the right of the "Add a new milestone"
+ text
+ </para>
+ </listitem>
+ <listitem>
+ <para>
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.
- Select "Add".
- </PARA>
- <EXAMPLE>
- <TITLE>Using SortKey with Target Milestone</TITLE>
- <INFORMALEXAMPLE>
- <PARA>
- Let's say you create a target milestone called "Release 1.0", with Sortkey set to "0".
- Later, you realize that you will have a public beta, called "Beta1".
- You can create a Milestone called "Beta1", with a Sortkey of "-1" in order to ensure
- people will see the Target Milestone of "Beta1" earlier on the list than "Release 1.0"
- </PARA>
- </INFORMALEXAMPLE>
- </EXAMPLE>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- If you want to add more milestones, select the "Edit" link.
- If you don't, well shoot, you have to go back to the "query" page and select "components"
- again, and make your way back to the Product you were editing.
- <NOTE>
- <PARA>
- This is another in the list of unusual user interface decisions that
- we'd like to get cleaned up. Shouldn't there be a link to the effect of
- "edit the Product I was editing when I ended up here"? In any case,
- clicking "components" in the footer takes you back to the "Select product"
- screen, from which you can begin editing your product again.
- </PARA>
- </NOTE>
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- From the Edit Product screen again (once you've made your way back), enter the URL
- for a description of what your milestones are for this product in the "Milestone URL" field.
- It should be of the format "http://www.foo.com/bugzilla/product_milestones.html"
- </PARA>
- <PARA>
- Some common uses of this field include product descriptions, product roadmaps,
- and of course a simple description of the meaning of each milestone.
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- If you're using Target Milestones, the "Default Milestone" field must have some
- kind of entry. If you really don't care if people set coherent Target Milestones,
- simply leave this at the default, "---". However, controlling and regularly updating the Default
- Milestone field is a powerful tool when reporting the status of projects.
- </PARA>
- <PARA>Select the "Update" button when you are done.</PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
-
- </PARA>
- </LISTITEM>
- </ORDEREDLIST>
- </SECTION>
+ 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. Select "Add".
+ </para>
+ <example>
+ <title>Using SortKey with Target Milestone</title>
+ <informalexample>
+ <para>
+ Let's say you create a target milestone called
+ "Release 1.0", with Sortkey set to "0". Later, you
+ realize that you will have a public beta, called
+ "Beta1". You can create a Milestone called "Beta1",
+ with a Sortkey of "-1" in order to ensure people will
+ see the Target Milestone of "Beta1" earlier on the
+ list than "Release 1.0"
+ </para>
+ </informalexample>
+ </example>
+ </listitem>
+ <listitem>
+ <para>
+ If you want to add more milestones, select the "Edit"
+ link. If you don't, well shoot, you have to go back to the
+ "query" page and select "components" again, and make your
+ way back to the Product you were editing.
+ <note>
+ <para>
+ This is another in the list of unusual user interface
+ decisions that we'd like to get cleaned up. Shouldn't
+ there be a link to the effect of "edit the Product I
+ was editing when I ended up here"? In any case,
+ clicking "components" in the footer takes you back to
+ the "Select product" screen, from which you can begin
+ editing your product again.
+ </para>
+ </note>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ From the Edit product screen again (once you've made your
+ way back), enter the URL for a description of what your
+ milestones are for this product in the "Milestone URL"
+ field. It should be of the format
+ "http://www.foo.com/bugzilla/product_milestones.html"
+ </para>
+ <para>
+ Some common uses of this field include product
+ descriptions, product roadmaps, and of course a simple
+ description of the meaning of each milestone.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ If you're using Target Milestones, the "Default Milestone"
+ field must have some kind of entry. If you really don't
+ care if people set coherent Target Milestones, simply
+ leave this at the default, "---". However, controlling
+ and regularly updating the Default Milestone field is a
+ powerful tool when reporting the status of projects.
+ </para>
+ <para>Select the "Update" button when you are done.</para>
+ </listitem>
+ </orderedlist>
+ </section>
- <SECTION id="voting">
- <TITLE>Voting</TITLE>
- <PARA>
- The concept of "voting" is a poorly understood, yet powerful feature for the management
- of open-source projects. Each user is assigned so many Votes per product, which they can
- freely reassign (or assign multiple votes to a single bug).
- 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
+ <section id="voting">
+ <title>Voting</title>
+ <para>
+ The concept of "voting" is a poorly understood, yet powerful
+ feature for the management of open-source projects. Each user
+ is assigned so many Votes per product, which they can freely
+ reassign (or assign multiple votes to a single bug). 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.
- </PARA>
- <PARA>
- The daunting challenge of Votes is deciding where you draw the line for a "vocal majority". If you
- only have a user base of 100 users, setting a low threshold for bugs to move from UNCONFIRMED
- to NEW makes sense. As the Bugzilla user base expands, however, these thresholds must be
- re-evaluated. You should gauge whether this feature is worth the time and close monitoring involved,
- and perhaps forego implementation until you have a critical mass of users who demand it.
- </PARA>
- <PARA>To modify Voting settings:</PARA>
- <ORDEREDLIST>
- <LISTITEM>
- <PARA>
- Navigate to the "Edit Product" screen for the Product you wish to modify
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- Set "Maximum Votes per person" to your calculated value. Setting this field
- to "0" disables voting.
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- Set "Maximum Votes a person can put on a single bug" to your calculated value. It
- should probably be some number lower than the "Maximum votes per person".
- Setting this field to "0" disables voting, but leaves the voting options open
- to the user. This is confusing.
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- Set "Number of votes a bug in this product needs to automatically get out of the
- UNCONFIRMED state" to your calculated number. Setting this field to "0"
- disables the automatic move of bugs from UNCONFIRMED to NEW. Some people
- advocate leaving this at "0", but of what use are Votes if your Bugzilla
- user base is unable to affect which bugs appear on Development radar?
- <TIP>
- <PARA>
- You should probably set this number to higher than a small coalition of
- Bugzilla users can influence it. Most sites use this as a "referendum"
- mechanism -- if users are able to vote a bug out of UNCONFIRMED, it
- is a <EMPHASIS>really</EMPHASIS> bad bug!
- </PARA>
- </TIP>
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- Once you have adjusted the values to your preference, select the "Update" button.
- </PARA>
- </LISTITEM>
- </ORDEREDLIST>
- </SECTION>
+ </para>
+ <para>
+ The daunting challenge of Votes is deciding where you draw the
+ line for a "vocal majority". If you only have a user base of
+ 100 users, setting a low threshold for bugs to move from
+ UNCONFIRMED to NEW makes sense. As the Bugzilla user base
+ expands, however, these thresholds must be re-evaluated. You
+ should gauge whether this feature is worth the time and close
+ monitoring involved, and perhaps forego implementation until
+ you have a critical mass of users who demand it.
+ </para>
+ <para>To modify Voting settings:</para>
+ <orderedlist>
+ <listitem>
+ <para>
+ Navigate to the "Edit product" screen for the Product you
+ wish to modify
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Set "Maximum Votes per person" to your calculated value.
+ Setting this field to "0" disables voting.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Set "Maximum Votes a person can put on a single bug" to
+ your calculated value. It should probably be some number
+ lower than the "Maximum votes per person". Setting this
+ field to "0" disables voting, but leaves the voting
+ options open to the user. This is confusing.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Set "Number of votes a bug in this product needs to
+ automatically get out of the UNCONFIRMED state" to your
+ calculated number. Setting this field to "0" disables
+ the automatic move of bugs from UNCONFIRMED to NEW. Some
+ people advocate leaving this at "0", but of what use are
+ Votes if your Bugzilla user base is unable to affect which
+ bugs appear on Development radar?
+ <tip>
+ <para>
+ You should probably set this number to higher than a
+ small coalition of Bugzilla users can influence it.
+ Most sites use this as a "referendum" mechanism -- if
+ users are able to vote a bug out of UNCONFIRMED, it is
+ a <emphasis>really</emphasis> bad bug!
+ </para>
+ </tip>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Once you have adjusted the values to your preference,
+ select the "Update" button.
+ </para>
+ </listitem>
+ </orderedlist>
+ </section>
- <SECTION id="groups">
- <TITLE>Groups and Group Security</TITLE>
- <PARA>
- Groups can be very useful in bugzilla, because they allow users to isolate
- bugs or products that should only be seen by certain people. Groups can also
- be a complicated minefield of interdependencies and weirdness if mismanaged.
+ <section id="groups">
+ <title>Groups and Group Security</title>
+ <para>
+ Groups can be very useful in bugzilla, because they allow
+ users to isolate bugs or products that should only be seen by
+ certain people. Groups can also be a complicated minefield of
+ interdependencies and weirdness if mismanaged.
- <EXAMPLE>
- <TITLE>When to Use Group Security</TITLE>
- <INFORMALEXAMPLE>
- <PARA>
- Many Bugzilla sites isolate "Security-related" bugs from all other bugs.
- This way, they can have a fix ready before the security vulnerability
- is announced to the world. You can create a "Security" product which, by
- default, has no members, and only add members to the group (in their individual
- User page, as described under User Administration) who should have
- priveleged access to "Security" bugs. Alternately, you may create a Group
- independently of any Product, and change the Group mask on individual bugs
- to restrict access to members only of certain Groups.
- </PARA>
- </INFORMALEXAMPLE>
- </EXAMPLE>
-
- Groups only work if you enable the "usebuggroups" paramater.
- In addition, if the "usebuggroupsentry" parameter is "On", one can restrict access
- to products by groups, so that only members of a product group are able to view
- bugs within that product.
- Group security in Bugzilla can be divided into two categories:
- Generic and Product-Based.
- </PARA>
- <NOTE>
- <PARA>
- Groups in Bugzilla are a complicated beast that evolved out of very simple user
- permission bitmasks, apparently itself derived from common concepts in UNIX access
- controls. A "bitmask" is a fixed-length number whose value can describe one, and
- only one, set of states. For instance, UNIX file permissions are assigned bitmask
- values: "execute" has a value of 1, "write" has a value of 2,
- and "read" has a value of 4. Add them together,
- and a file can be read, written to, and executed if it has a bitmask of "7". (This
- is a simplified example -- anybody who knows UNIX security knows there is much
- more to it than this. Please bear with me for the purpose of this note.) The only
- way a bitmask scheme can work is by doubling the bit count for each value. Thus
- if UNIX wanted to offer another file permission, the next would have to be a value of
- 8, then the next 16, the next 32, etc.
- </PARA>
- <PARA>
- Similarly, Bugzilla offers a bitmask to define group permissions, with an internal
- limit of 64. Several are already occupied
- by built-in permissions. The way around this limitation is
- to avoid assigning groups to products if you have many products, avoid bloating
- of group lists, and religiously prune irrelevant groups. In reality, most installations
- of Bugzilla support far fewer than 64 groups, so this limitation has not hit
- for most sites, but it is on the table to be revised for Bugzilla 3.0
- because it interferes with the security schemes of some administrators.
- </PARA>
- </NOTE>
- <PARA>
+ <example>
+ <title>When to Use Group Security</title>
+ <informalexample>
+ <para>
+ Many Bugzilla sites isolate "Security-related" bugs from
+ all other bugs. This way, they can have a fix ready
+ before the security vulnerability is announced to the
+ world. You can create a "Security" product which, by
+ default, has no members, and only add members to the
+ group (in their individual User page, as described under
+ User Administration) who should have priveleged access
+ to "Security" bugs. Alternately, you may create a Group
+ independently of any Product, and change the Group mask
+ on individual bugs to restrict access to members only of
+ certain Groups.
+ </para>
+ </informalexample>
+ </example> Groups only work if you enable the "usebuggroups"
+ paramater. In addition, if the "usebuggroupsentry" parameter
+ is "On", one can restrict access to products by groups, so
+ that only members of a product group are able to view bugs
+ within that product. Group security in Bugzilla can be divided
+ into two categories: Generic and Product-Based.
+ </para>
+ <note>
+ <para>
+ Groups in Bugzilla are a complicated beast that evolved out
+ of very simple user permission bitmasks, apparently itself
+ derived from common concepts in UNIX access controls. A
+ "bitmask" is a fixed-length number whose value can describe
+ one, and only one, set of states. For instance, UNIX file
+ permissions are assigned bitmask values: "execute" has a
+ value of 1, "write" has a value of 2, and "read" has a
+ value of 4. Add them together, and a file can be read,
+ written to, and executed if it has a bitmask of "7". (This
+ is a simplified example -- anybody who knows UNIX security
+ knows there is much more to it than this. Please bear with
+ me for the purpose of this note.) The only way a bitmask
+ scheme can work is by doubling the bit count for each value.
+ Thus if UNIX wanted to offer another file permission, the
+ next would have to be a value of 8, then the next 16, the
+ next 32, etc.
+ </para>
+ <para>
+ Similarly, Bugzilla offers a bitmask to define group
+ permissions, with an internal limit of 64. Several are
+ already occupied by built-in permissions. The way around
+ this limitation is to avoid assigning groups to products if
+ you have many products, avoid bloating of group lists, and
+ religiously prune irrelevant groups. In reality, most
+ installations of Bugzilla support far fewer than 64 groups,
+ so this limitation has not hit for most sites, but it is on
+ the table to be revised for Bugzilla 3.0 because it
+ interferes with the security schemes of some administrators.
+ </para>
+ </note>
+ <para>
To enable Generic Group Security ("usebuggroups"):
- </PARA>
- <ORDEREDLIST>
- <LISTITEM>
- <PARA>
+ </para>
+ <orderedlist>
+ <listitem>
+ <para>
Turn "On" "usebuggroups" in the "Edit Parameters" screen.
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- You will generally have no groups set up. Select the "groups" link
- in the footer.
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- Take a moment to understand the instructions on the "Edit Groups" screen.
- Once you feel confident you understand what is expected of you, select the
- "Add Group" link.
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- Fill out the "New Name" (remember, no spaces!), "New Description", and "New
- User RegExp" fields. "New User RegExp" allows you to automatically place
- all users who fulfill the Regular Expression into the new group.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ You will generally have no groups set up. Select the
+ "groups" link in the footer.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Take a moment to understand the instructions on the "Edit
+ Groups" screen. Once you feel confident you understand
+ what is expected of you, select the "Add Group" link.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Fill out the "New Name" (remember, no spaces!), "New
+ Description", and "New User RegExp" fields. "New User
+ RegExp" allows you to automatically place all users who
+ fulfill the Regular Expression into the new group.
+
+ <example>
+ <title>Creating a New Group</title>
+ <informalexample>
+ <para>
+ I created a group called DefaultGroup with a
+ description of <quote>This is simply a group to play
+ with</quote>, and a New User RegExp of <quote>.*@mydomain.tld</quote>.
+ This new group automatically includes all Bugzilla
+ users with "@mydomain.tld" at the end of their user id.
+ When I finished, my new group was assigned bit #128.
+ </para>
+ </informalexample>
+ </example> When you have finished, select the Add
+ button.
+ </para>
+ </listitem>
+ </orderedlist>
+
+ <para>
+ To enable Product-Based Group Security (usebuggroupsentry):
+ </para>
+ <warning>
+ <para>
+ Don't forget that you only have 64 groups masks available,
+ total, for your installation of Bugzilla! If you plan on
+ having more than 50 products in your individual Bugzilla
+ installation, and require group security for your products,
+ you should consider either running multiple Bugzillas or
+ using Generic Group Security instead of Product-Based
+ ("usebuggroupsentry") Group Security.
+ </para>
+ </warning>
+ <orderedlist>
+ <listitem>
+ <para>
+ Turn "On" "usebuggroups" and "usebuggroupsentry" in the
+ "Edit Parameters" screen.
+ </para>
+ <warning>
+ <para>
+ "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, Products, etc.
+ with the administrative account.
+ </para>
+ </warning>
+ </listitem>
+ <listitem>
+ <para>
+ You will generally have no Groups set up, unless you
+ enabled "usebuggroupsentry" prior to creating any
+ Products. To create "Generic Group Security" groups,
+ follow the instructions given above. To create
+ Product-Based Group security, simply follow the
+ instructions for creating a new Product. If you need to
+ add users to these new groups as you create them, you will
+ find the option to add them to the group available under
+ the "Edit User" screens.
+ </para>
+ </listitem>
+ </orderedlist>
+ <para>
+ You may find this example illustrative for how bug groups work.
+ <example>
+ <title>Bugzilla Groups</title>
+ <literallayout>
+Bugzilla Groups example
+-----------------------
+
+For this example, let us suppose we have four groups, call them
+Group1, Group2, Group3, and Group4.
+
+We have 5 users, User1, User2, User3, User4, User5.
+
+We have 8 bugs, Bug1, ..., Bug8.
+
+Group membership is defined by this chart:
+(X denotes that user is in that group.)
+(I apologize for the nasty formatting of this table. Try viewing
+it in a text-based browser or something for now. -MPB)
+
+ G G G G
+ r r r r
+ o o o o
+ u u u u
+ p p p p
+ 1 2 3 4
+ +-+-+-+-+
+User1|X| | | |
+ +-+-+-+-+
+User2| |X| | |
+ +-+-+-+-+
+User3|X| |X| |
+ +-+-+-+-+
+User4|X|X|X| |
+ +-+-+-+-+
+User5| | | | |
+ +-+-+-+-+
+
+Bug restrictions are defined by this chart:
+(X denotes that bug is restricted to that group.)
+
+ G G G G
+ r r r r
+ o o o o
+ u u u u
+ p p p p
+ 1 2 3 4
+ +-+-+-+-+
+Bug1| | | | |
+ +-+-+-+-+
+Bug2| |X| | |
+ +-+-+-+-+
+Bug3| | |X| |
+ +-+-+-+-+
+Bug4| | | |X|
+ +-+-+-+-+
+Bug5|X|X| | |
+ +-+-+-+-+
+Bug6|X| |X| |
+ +-+-+-+-+
+Bug7|X|X|X| |
+ +-+-+-+-+
+Bug8|X|X|X|X|
+ +-+-+-+-+
+
+Who can see each bug?
+
+Bug1 has no group restrictions. Therefore, Bug1 can be seen by any
+user, whatever their group membership. This is going to be the only
+bug that User5 can see, because User5 isn't in any groups.
+
+Bug2 can be seen by anyone in Group2, that is User2 and User4.
+
+Bug3 can be seen by anyone in Group3, that is User3 and User4.
- <EXAMPLE>
- <TITLE>Creating a New Group</TITLE>
- <INFORMALEXAMPLE>
- <PARA>
- I created a group called "DefaultGroup" with a description of "This is simply
- a group to play with", and a "New User RegExp" of "*@velio.com". This
- new group automatically includes all Bugzilla users with "@velio.com" at the
- end of their user id. When I finished, my new group was assigned bit #128.
- </PARA>
- </INFORMALEXAMPLE>
- </EXAMPLE>
-
- When you have finished, select the "Add" button.
- </PARA>
- </LISTITEM>
- </ORDEREDLIST>
+Bug4 can be seen by anyone in Group4. Nobody is in Group4, so none of
+these users can see Bug4.
- <PARA>
- To enable Product-Based Group Security ("usebuggroupsentry"):
- </PARA>
- <WARNING>
- <PARA>
- Don't forget that you only have 64 groups masks available, total, for
- your installation of Bugzilla! If you plan on having more than 50
- products in your individual Bugzilla installation, and require group
- security for your products, you should
- consider either running multiple Bugzillas or using Generic Group Security
- instead of Product-Based ("usebuggroupsentry") Group Security.
- </PARA>
- </WARNING>
- <ORDEREDLIST>
- <LISTITEM>
- <PARA>
- Turn "On" "usebuggroups" and "usebuggroupsentry" in the "Edit Parameters" screen.
- </PARA>
- <WARNING>
- <PARA>
- "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, Products, etc. with the administrative account.
- </PARA>
- </WARNING>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- You will generally have no Groups set up, unless you enabled "usebuggroupsentry"
- prior to creating any Products. To create "Generic Group Security" groups,
- follow the instructions given above. To create Product-Based Group security,
- simply follow the instructions for creating a new Product. If you need to
- add users to these new groups as you create them, you will find the option
- to add them to the group available under the "Edit User" screens.
- </PARA>
- </LISTITEM>
- </ORDEREDLIST>
- </SECTION>
- </SECTION>
+Bug5 can be seen by anyone who is in _both_ Group1 and Group2. This
+is only User4. User1 cannot see it because he is not in Group2, and
+User2 cannot see it because she is not in Group1.
+
+Bug6 can be seen by anyone who is in both Group1 and Group3. This
+would include User3 and User4. Similar to Bug5, User1 cannot see Bug6
+because he is not in Group3.
+
+Bug7 can be seen by anyone who is in Group1, Group2, and Group3. This
+is only User4. All of the others are missing at least one of those
+group priveleges, and thus cannot see the bug.
+
+Bug8 can be seen by anyone who is in Group1, Group2, Group3, and
+Group4. There is nobody in all four of these groups, so nobody can
+see Bug8. It doesn't matter that User4 is in Group1, Group2, and
+Group3, since he isn't in Group4.
+ </literallayout>
+ </example>
+ </para>
+ </section>
+ </section>
- <SECTION id="security">
- <TITLE>Bugzilla Security</TITLE>
- <EPIGRAPH>
- <PARA>
- Putting your money in a wall safe is better protection than depending on the fact that
- no one knows that you hide your money in a mayonnaise jar in your fridge.
- </PARA>
- </EPIGRAPH>
- <NOTE>
- <PARA>
- Poorly-configured MySQL, Bugzilla, and FTP installations have given attackers full
- access to systems in the past. Please take these guidelines seriously, even
- for Bugzilla machines hidden away behind your firewall. 80% of all computer
+ <section id="security">
+ <title>Bugzilla Security</title>
+ <epigraph>
+ <para>
+ Putting your money in a wall safe is better protection than
+ depending on the fact that no one knows that you hide your
+ money in a mayonnaise jar in your fridge.
+ </para>
+ </epigraph>
+ <note>
+ <para>
+ Poorly-configured MySQL, Bugzilla, and FTP installations have
+ given attackers full access to systems in the past. Please
+ take these guidelines seriously, even for Bugzilla machines
+ hidden away behind your firewall. 80% of all computer
trespassers are insiders, not anonymous crackers.
- </PARA>
- </NOTE>
- <PARA>
- First thing's first: Secure your installation.
- <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>
- </PARA>
- </NOTE>
- <ORDEREDLIST>
- <LISTITEM>
- <PARA>
- Ensure you are running at least MysQL version 3.22.32 or newer. Earlier versions had
- notable security holes and poorly secured default configuration choices.
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA><EMPHASIS>There is no substitute for understanding the tools on your system!</EMPHASIS>
- Read <ULINK URL="http://www.mysql.com/documentation/mysql/bychapter/manual_Privilege_system.html">
- The MySQL Privelege System</ULINK> until you can recite it from memory!</PARA>
- <PARA>
- At the very least, ensure you password the "mysql -u root" account and the "bugs" account, establish grant
- table rights (consult the Keystone guide in Appendix C: The Bugzilla Database for some easy-to-use details)
- that do not allow CREATE, DROP, RELOAD, SHUTDOWN, and PROCESS for user "bugs". I wrote up the Keystone
- advice back when I knew far less about security than I do now : )
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- Lock down /etc/inetd.conf. Heck, disable inet entirely on this box. It should only listen to
- port 25 for Sendmail
+ </para>
+ </note>
+ <para>
+ Secure your installation.
+ <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>
+ </para>
+ </note>
+ <orderedlist>
+ <listitem>
+ <para>
+ Ensure you are running at least MysQL version 3.22.32 or
+ newer. Earlier versions had notable security holes and
+ poorly secured default configuration choices.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>There is no substitute for understanding the
+ tools on your system!</emphasis> Read <ulink url="http://www.mysql.com/documentation/mysql/bychapter/manual_Privilege_system.html"> The MySQL Privilege System</ulink> until you can recite it from memory!</para>
+ <para>
+ At the very least, ensure you password the "mysql -u root"
+ account and the "bugs" account, establish grant table
+ rights (consult the Keystone guide in Appendix C: The
+ Bugzilla Database for some easy-to-use details) that do
+ not allow CREATE, DROP, RELOAD, SHUTDOWN, and PROCESS for
+ user "bugs". I wrote up the Keystone advice back when I
+ knew far less about security than I do now : )
+ </para>
+ </listitem>
+ <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>
- <LISTITEM>
- <PARA>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.</PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- Ensure you have adequate access controls for the $BUGZILLA_HOME/data/ and
- $BUGZILLA_HOME/shadow/ directories, as well as the $BUGZILLA_HOME/localconfig file.
- The localconfig file stores your "bugs" user password,
- which would be terrible to have in the hands
- of a criminal. Also some files under $BUGZILLA_HOME/data/ store sensitive information, and
- $BUGZILLA_HOME/shadow/ stores bug information for faster retrieval. If you fail to secure
- these directories and this file, you will expose bug information to those who may not
- be allowed to see it.
- </PARA>
- <PARA>
- On Apache, you can use .htaccess files to protect access to these directories, as outlined
- in <ULINK URL="http://bugzilla.mozilla.org/show_bug.cgi?id=57161">Bug 57161</ULINK> for the
- localconfig file, and <ULINK URL="http://bugzilla.mozilla.org/show_bug.cgi?id=65572">
- Bug 65572</ULINK> for adequate protection in your data/ and shadow/ directories.
- </PARA>
- <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>
- <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>
- </PARA>
- <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>
- <PARA>
- Place the following text into a file named ".htaccess", readable by your web server,
- in your $BUGZILLA_HOME/shadow directory.
- <LITERALLAYOUT>
- deny from all
- </LITERALLAYOUT>
- </PARA>
- </LISTITEM>
- </ORDEREDLIST>
- </PARA>
- </SECTION>
-</CHAPTER>
-
-
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Do not run Apache as <quote>nobody</quote>. 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> is a real user on UNIX systems.
+ Having a process run as user id <quote>nobody</quote>
+ 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>
+ Ensure you have adequate access controls for the
+ $BUGZILLA_HOME/data/ and $BUGZILLA_HOME/shadow/
+ directories, as well as the $BUGZILLA_HOME/localconfig and
+ $BUGZILLA_HOME/globals.pl files. The localconfig file
+ stores your "bugs" user password, which would be terrible
+ to have in the hands of a criminal, while the "globals.pl"
+ stores some default information regarding your
+ installation which could aid a system cracker. In
+ addition, some files under $BUGZILLA_HOME/data/ store
+ sensitive information, and $BUGZILLA_HOME/shadow/ stores
+ bug information for faster retrieval. If you fail to
+ secure these directories and this file, you will expose
+ bug information to those who may not be allowed to see it.
+ </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>
+ </note>
+ <para>
+ On Apache, you can use .htaccess files to protect access
+ to these directories, as outlined in <ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=57161">Bug 57161</ulink> for the localconfig file, and <ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=65572"> Bug 65572</ulink> for adequate protection in your data/ and shadow/ directories.
+ </para>
+ <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>
+ <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>
+ </para>
+ <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>
+ <para>
+ Place the following text into a file named ".htaccess",
+ readable by your web server, in your $BUGZILLA_HOME/shadow
+ directory. <literallayout> deny from all </literallayout>
+ </para>
+ </listitem>
+ </orderedlist>
+ </para>
+ </section>
+</chapter>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
-sgml-omittag:t
-sgml-shorttag:t
-sgml-namecase-general:t
-sgml-general-insert-case:upper
-sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
-sgml-indent-step:2
-sgml-indent-data:t
-sgml-parent-document:nil
+sgml-auto-insert-required-elements:t
+sgml-balanced-tag-edit:t
sgml-exposed-tags:nil
+sgml-general-insert-case:lower
+sgml-indent-data:t
+sgml-indent-step:2
sgml-local-catalogs:nil
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-shorttag:t
+sgml-tag-region-if-active:t
End:
-->
diff --git a/docs/sgml/conventions.sgml b/docs/sgml/conventions.sgml
index 66f72303c..71f2b0c5e 100644
--- a/docs/sgml/conventions.sgml
+++ b/docs/sgml/conventions.sgml
@@ -89,23 +89,28 @@
</informaltable>
</section>
+
+
+
+
+
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
-sgml-omittag:t
-sgml-shorttag:t
-sgml-namecase-general:t
-sgml-general-insert-case:upper
-sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
-sgml-indent-step:2
-sgml-indent-data:t
-sgml-parent-document:nil
+sgml-auto-insert-required-elements:t
+sgml-balanced-tag-edit:t
sgml-exposed-tags:nil
+sgml-general-insert-case:lower
+sgml-indent-data:t
+sgml-indent-step:2
sgml-local-catalogs:nil
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-shorttag:t
+sgml-tag-region-if-active:t
End:
-->
-
-
-
diff --git a/docs/sgml/database.sgml b/docs/sgml/database.sgml
index eced31c52..7ff52134c 100644
--- a/docs/sgml/database.sgml
+++ b/docs/sgml/database.sgml
@@ -1,197 +1,153 @@
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
-
-<APPENDIX id="database">
-
-<TITLE>The Bugzilla Database</TITLE>
-<NOTE>
-<PARA>This document really needs to be updated with more fleshed out information about primary keys, interrelationships, and maybe some nifty tables to document dependencies. Any takers?</PARA>
-</NOTE>
- <SECTION id="dbschema">
- <TITLE>Database Schema Chart</TITLE>
- <PARA>
- <MEDIAOBJECT>
- <IMAGEOBJECT>
- <IMAGEDATA FILEREF="dbschema.jpg" FORMAT="jpg">
- </IMAGEOBJECT>
-
- <TEXTOBJECT>
- <PHRASE>Database Relationships</PHRASE>
- </TEXTOBJECT>
-
- <CAPTION>
- <PARA>Bugzilla database relationships chart</PARA>
- </CAPTION>
- </MEDIAOBJECT>
- </PARA>
- </SECTION>
-
- <SECTION id="dbdoc">
-<TITLE>MySQL Bugzilla Database Introduction</TITLE>
-<LITERALLAYOUT>
-
-Contributor(s): Matthew P. Barnson (mbarnson@excitehome.net)
-
-Last update: May 16, 2000
-
-Changes:
-Version 1.0: Initial public release (May 16, 2000)
-
-Maintainer: Matthew P. Barnson (mbarnson@excitehome.net)
-
-
-===
-Table Of Contents
-===
-
-FOREWORD
-INTRODUCTION
-THE BASICS
-THE TABLES
-THE DETAILS
-
-
-
-===
-FOREWORD
-===
-
- 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.
-
- I'm sorry this version is plain text. I can whip this info out a lot faster
-if I'm not concerned about complex formatting. I'll get it into sgml for easy
-portability as time permits.
-
- The Bugzilla Database Schema has a home! In addition to availability via CVS
-and released versions 2.12 and higher of Bugzilla, you can find the latest &
-greatest version of the Bugzilla Database Schema at
-http://www.trilobyte.net/barnsons/. This is a living document; please be sure
-you are up-to-date with the latest version before mirroring.
-
- The Bugzilla Database Schema is designed to provide vital information
-regarding the structure of the MySQL database. Where appropriate, this
-document will refer to URLs rather than including documents in their entirety
-to ensure completeness even should this paper become out of date.
-
- This document is not maintained by Netscape or Netscape employees, so please
-do not contact them regarding errors or omissions contained herein. Please
-direct all questions, comments, updates, flames, etc. to Matthew P. Barnson
-mbarnson@excitehome.net) (barnboy or barnhome on irc.mozilla.org in
-#mozwebtools).
-
- I'm sure I've made some glaring errors or omissions in this paper -- please
-email me corrections or post corrections to the
-netscape.public.mozilla.webtools newsgroup.
-
-
-
-===
-INTRODUCTION
-===
-
-
-
- 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!
-
-
-
-===
-The 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'd refer you first to the MySQL documentation,
-available at http://www.mysql.com/doc.html, but that's mostly a confusing
-morass of high-level database jargon. Here are the basics you need to know
-about the database to proceed:
-
-1. To connect to your database, type "mysql -u root" at the command prompt as
-any user. If this works without asking you for a password, SHAME ON YOU! You
-should have locked your security down like the README 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
-MySQL searchable documentation at
-http://www.mysql.com/php/manual.php3?section=Privilege_system .
-
-2. You should now be at a prompt that looks like this:
-
-mysql>
-
- At the prompt, if "bugs" is the name of your Bugzilla database, type:
-
-mysql> use bugs;
+<!-- <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
+
+<appendix id="database">
+
+<title>The Bugzilla Database</title>
+<note>
+<para>
+ This document really needs to be updated with more fleshed out information about primary keys, interrelationships, and maybe some nifty tables to document dependencies. Any takers?
+ </para>
+ </note>
+ <section id="dbschema">
+ <title>Database Schema Chart</title>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="../images/dbschema.jpg" format="jpg">
+ </imageobject>
- (don't forget the ";" at the end of each line, or you'll be kicking yourself
-all the way through this documentation)
- Young Grasshopper, you are now ready for the unveiling of the Bugzilla
-database, in the next section...
-
-
-
-===
-THE TABLES
-===
-
- 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;
-
- you'll be able to see all the "spreadsheets" (tables) in your database. Cool,
-huh? It's kinda' like a filesystem, only much faster and more robust. Come
-on, I'll show you more!
-
- From the command issued above, you should now have some output that looks
-like this:
-
+ <textobject>
+ <phrase>Database Relationships</phrase>
+ </textobject>
+
+ <caption>
+ <para>Bugzilla database relationships chart</para>
+ </caption>
+ </mediaobject>
+ </para>
+ </section>
+
+ <section id="dbdoc">
+<title>MySQL Bugzilla Database Introduction</title>
+ <para>
+ 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.
+ </para>
+
+ <para>
+ 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.
+ </para>
+ <para>
+ 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.
+ </para>
+ <para>
+ 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!
+ </para>
+ <para>
+ 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'.
+ </para>
+ <para>
+ 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."
+ </para>
+ <para>
+ 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...
+ </para>
+ <para>
+ 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!
+ </para>
+
+ <section>
+ <title>Bugzilla Database Basics</title>
+ <para>
+ 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 <quote>bigint</quote> and a
+ <quote>tinyint</quote> entry in MySQL. I recommend you refer
+ to the MySQL documentation, available at <ulink url="http://www.mysql.com/doc.html">MySQL.com</ulink>. Below are the basics you need to know about the Bugzilla database. Check the chart above for more details.
+ </para>
+ <para><orderedlist>
+ <listitem>
+ <para>
+ To connect to your database:
+ </para>
+ <para>
+ <prompt>bash#</prompt><command>mysql</command><parameter>-u root</parameter>
+ </para>
+ <para>
+ If this works without asking you for a password,
+ <emphasis>shame on you</emphasis>! 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 MySQL searchable documentation at
+ http://www.mysql.com/php/manual.php3?section=Privilege_system .
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>You should now be at a prompt that looks like
+ this:</para>
+ <para><prompt>mysql></prompt></para>
+ <para>At the prompt, if <quote>bugs</quote> is the name
+ you chose in the<filename>localconfig</filename> file
+ for your Bugzilla database, type:</para>
+ <para><prompt>mysql</prompt><command>use bugs;</command></para>
+ <note>
+ <para>Don't forget the <quote>;</quote> at the end of
+ each line, or you'll be kicking yourself later.</para>
+ </note>
+ </listitem>
+ </orderedlist>
+ </para>
+ <section>
+ <title>Bugzilla Database Tables</title>
+ <para> Imagine your MySQL database as a series of
+ spreadsheets, and you won't be too far off. If you use this
+ command:</para>
+ <para><prompt>mysql></prompt><command>show tables from bugs;</command></para>
+ <para>you'll be able to see all the
+ <quote>spreadsheets</quote> (tables) in your database. It
+ is similar to a file system, only faster and more robust for
+ certain types of operations.</para>
+ <para>From the command issued above, ou should have some
+ output that looks like this:
+ <programlisting>
+-------------------+
| Tables in bugs |
+-------------------+
@@ -213,14 +169,13 @@ like this:
| profiles |
| profiles_activity |
| shadowlog |
+| tokens |
| versions |
| votes |
| watch |
+-------------------+
-
-
- If it doesn't look quite the same, that probably means it's time to
-update this documentation :)
+ </programlisting></para>
+<literallayout>
Here's an overview of what each table does. Most columns in each table have
descriptive names that make it fairly trivial to figure out their jobs.
@@ -398,23 +353,36 @@ LINKS
Great MySQL tutorial site:
http://www.devshed.com/Server_Side/MySQL/
- </LITERALLAYOUT>
- </SECTION>
-
- <SECTION id="granttables">
- <TITLE>MySQL Permissions & Grant Tables</TITLE>
-
- <NOTE>
- <PARA>The following portion of documentation comes from my answer to an old discussion of Keystone,
- a cool product that does trouble-ticket tracking for IT departments. I wrote this post to the
- Keystone support group regarding MySQL grant table permissions, and how to use them effectively.
- It is badly in need of updating, as I believe MySQL has added a field or two to the grant tables
- since this time, but it serves as a decent introduction and troubleshooting document for grant
- table issues. I used Keynote to track my troubles until I discovered Bugzilla,
- which gave me a whole new set of troubles to work on : )</PARA>
- </NOTE>
-
- <LITERALLAYOUT>
+ </literallayout>
+ </section>
+ </section>
+ </section>
+
+ <section id="granttables">
+ <title>MySQL Permissions & Grant Tables</title>
+
+ <note>
+ <para>The following portion of documentation comes from my
+ answer to an old discussion of Keystone, a cool product that
+ does trouble-ticket tracking for IT departments. I wrote this
+ post to the Keystone support group regarding MySQL grant
+ table permissions, and how to use them effectively. It is
+ badly in need of updating, as I believe MySQL has added a
+ field or two to the grant tables since this time, but it
+ serves as a decent introduction and troubleshooting document
+ for grant table issues. I used Keynote to track my troubles
+ until I discovered Bugzilla, which gave me a whole new set of
+ troubles to work on : ) Although it is of limited use, it
+ still has SOME use, thus it's still included.</para>
+ <para>
+ Please note, however, that I was a relatively new user to
+ MySQL at the time. Some of my suggestions, particularly in
+ how to set up security, showed a terrible lack of
+ security-related database experience.
+ </para>
+ </note>
+
+ <literallayout>
From matt_barnson@singletrac.com Wed Jul 7 09:00:07 1999
Date: Mon, 1 Mar 1999 21:37:04 -0700
From: Matthew Barnson matt_barnson@singletrac.com
@@ -577,59 +545,28 @@ Once again, you can't go wrong by reading section 6 of the MySQL manual. It
is more detailed than I!
http://www.mysql.com/Manual/manual.html.
-----------------------------------------------------------------------------
-10/12/2000
-Matthew sent in some mail with updated contact information:
-NEW CONTACT INFORMATION:
-
- ------------------------
- Matthew P. Barnson
- Manager, Systems Administration
- Excite@Home Business Applications
- mbarnson@excitehome.net
- (801)234-8300
-
-
- </LITERALLAYOUT>
- </SECTION>
- <SECTION id="cleanupwork">
- <TITLE>Cleaning up after mucking with Bugzilla</TITLE>
- <LITERALLAYOUT>
-Contributed by Eric Hanson:
-There are several things, and one trick. There is a small tiny piece of
-documentation I saw once that said something very important.
-1) After pretty much any manual working of the Mysql db, you must
-delete a file in the bugzilla directory: data/versioncache
-Versioncache basically is a way to speed up bugzilla (from what I
-understand). It stores a lot of commonly used information. However,
-this file is refreshed every so often (I can't remember the time
-interval though). So eventually all changes do propogate out, so you
-may see stuff suddenly working.
-2) Assuming that failed, you will also have to check something with the
-checksetup.pl file. It actually is run twice. The first time it
-creates the file: localconfig. You can modify localconfig, (or not if
-you are doing bug_status stuff) or you should delete localconfig and
-rerun your modified checksetup.pl. Since I don't actually see anything
-in localconfig pertaining to bug_status, this point is mainly a FYI.
- </LITERALLAYOUT>
- </SECTION>
-
-</APPENDIX>
+ </literallayout>
+ </section>
+
+</appendix>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
-sgml-omittag:t
-sgml-shorttag:t
-sgml-namecase-general:t
-sgml-general-insert-case:upper
-sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
-sgml-indent-step:2
-sgml-indent-data:t
-sgml-parent-document:nil
+sgml-auto-insert-required-elements:t
+sgml-balanced-tag-edit:t
sgml-exposed-tags:nil
+sgml-general-insert-case:lower
+sgml-indent-data:t
+sgml-indent-step:2
sgml-local-catalogs:nil
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-shorttag:t
+sgml-tag-region-if-active:t
End:
-->
diff --git a/docs/sgml/dbschema.jpg b/docs/sgml/dbschema.jpg
deleted file mode 100644
index 17e2422e58a7f4ef2680cde4c8b89fdeb351e2a6..0000000000000000000000000000000000000000
GIT binary patch
literal 0
HcmV?d00001
literal 220048
zcmex=<NpH&0WUXCHwH#V1_nk3Mh1rew;7xnIM~?O*;qN)+1WWcIk<R4czL+Fc_f8|
z`9)-<<mF_gWMmXn^wbrUbd+UeG|V-13=B<7Oyt!qZ7qy!^o&i6K!z}Ka&q!;^GNXW
zN*F21C>oIr{vTiv<Y1Y?V#v&>#K0uT$SlbC{|JLT0|O%~BN#A10V5ML3o9Et2PYTz
z|04`r1sIqZnVFebm|0m_SQr=>YZ;lC8CV2ag%k}P*@OcV*_8@Kj2b5{<WP3ncu+Lx
z;s+Juq@pHHE-`TlNhwt|bq!4|6H_yD3rj0!7gslT4^OY)kkGL3h{&kql+?8JjLfX!
zlG3vBipr|yme#iRj?S)0lc!9bHhsp-S&J4gS-Ncbij}K2ZQinV+x8thcO5!><mj>E
zCr+Nabot8FYu9hwy!G(W<0ns_J%91?)yGetzkL1n{m0K=Ab&A3FoS&sA|M_^^Oqn4
z6C)D~3o{El$X|?1<qV8W%z`YeiiT`Lj)Clng~CckjT|CQ6Blkg$f;}`^g%SK=pvVx
zipfLOk07sseMX$en#l4Q++zrT-D2QjW@KOzWENzwXZZe0V^M=eJ?{_y!&UR<S60?P
z{Hyium2Y_9eUop2C*F3SY&b1Axq;!2cJe;~fA;?j7gjF(&+uTE{6DpRw*L$#_@4he
zv}^jmX=h_u8H)cid}yk$|JUlv|DS>N!heR3CiRCnAN*(dC2C^-N8I^8!;$Nbu2fYP
zBe%RRcTdH{lPf%R))z7z&gK0x;k-<ah`_d1pK`&J-8M&_hMZtz6Kvr1w&$#n4`^Jr
z^~14tm28~}lmE^ZIDG7_bYJ*pZT_0VqY?iZT7(b&XZWI(QU61){XawJx_l?kHTfl{
zSFF!FfBTR7s;JZ4UNs9js&AUDsV}#F9CpvK&g1U(rxM@l6t6}-4)Im;-oB%j>)Xq~
z_bPkmzb%}xXX_-j9(R^kDY+M1CvZ1}Ga518Qg7MAueR8<=|{4&dB9PbOX}Zp;<YRb
zmRlE|?ETN6Ul?ZpkmW=DU#?m5|F{?aXLyv|Exyh0m7L;a$LmY>ZHTT_vRoJRpW!Xr
zEw<fr{A~VA4^U1oI&*u1q2d&+w;OIPTbi6%ysDz^ov+s+?wdL#{~7Gwu2Yzqw!Pz6
z&7qr9{%+B6?3Qiv6xU)4U|zEK!}P{4Kg6=v^JEkryL6nx{^mxRJ$)M&JgnZV@$I}#
zX#WpK8~OhXPRrW=Gc>)Z|1s<FbE_pAy0c$C&nSs?_P=~}R_?KKs}>!(JiniI=eDii
zkv#K>Y|-k4%d+_XX>4&^ab9iRueDF2S|{#G`?O|COr=il$=gD6x9ymqHSNxx`3CP8
zUZD9k12YEV5AK?L=SRD1@7C<svsZ5Me0DWAb>=*aeCONw5;iIgo0$a^+&B)YecpXZ
zgLyuN_QmKab{7`~%GT_4J{-l@`^cZ`PG*(b>}2b#B4y9)tciy48}G~!S|F3c+@Bb`
zwD_Ome})OqTmCb=(N_OAF*bnR(N!dXahPLv{)fBg3%M`9r`tAlsehJftb5AjS4A#w
z|IIWjTExaY=Rbqs*T+k9YBwK~|H5?PKf{M&^ZyJ=*KEw=6MrN>iax*jVBr(*HK(84
zQTy@ac5y-3uJ6G;f_FmdRIhB+ez{JuGnZ|C;<}g9CM{<B>@B%A?X&3Sp1P00iGdfk
z{bzWfAU!|lWBXr*E%tw8&i-dOu?5W<XqiJNH4*=GcKzmWE<FwQROWY~pXQwVEX|G`
z&t6|@aZvUsL-_CX9{U%ppi=Z%{y*2nZ|52OXILQC{-2?F=Kh~zo8Q@Zu5nzG<$ikO
zzcU-J=9>K79dp)v-nPe<=dRqi{O+7|#m|BncW#ymWrg2To4YJqeB<3^iyv9vj=Za!
za>mg1%)B_s`x<BSH>^DIX~y#0Bg{+iTete9+5XfY?T?u9)aNd{{AOv|%+K46?l!Dq
zV_Lz$!0>kRG@WDfx)&ZUmG3F(?q0pqW!9``FQ2fLPPlp7U~05Pc-Ub*1`emU3=9k`
zRdrJzotAZpJDHkXtrBP=cIbUf*>4-4kWFo3iSzAZ>P=d2KaqK|t<3J`WBy-^8TCIb
zXa8rInDxAEtLE1ETrZ`T9y+%9-c9F1rDGfc=NdaCRUWHfxwaHkThJutwoYH+zux<i
zKi9gI%U*7~P@j1s^ld5o-0s@G=S^$57!2nX-zYpUOE5o+#{K(s-{<nW{P!xK-sUD%
zE~{Pg)|F-BfhP}`FE!`{#{6gaqZSqa=hy4`Ka}?VXLxK<e<*e7e}?nxcK&B*(!T%C
z*g=+6^!$GYG*NdnU5pn-je>;L+4GO*ie0-G-QBTuMnWg|NtIcuuU2VDs!SGRV4ic`
z(}7ha5Q2-UzD-{C+Ro~t?pI&COTSnz>(5Qz)tVY`FL%KS9*%RIlHX0Qh1*yDXHeyL
z`_Hf;^gqMD-YpB5(d!J1YVd`|0={}Gs*3%i`k>;gM2_@fDT!UPG}U_THz)m^$i-%P
zyN{>y=WnTv{~0*coBuPs2muwGvHbrTgd_eL@3^X4<Gajv$<b#%vqFD+Z^)aOBy>yM
zVA(Z(Gd96!?j1c(cx38DUzrDH86IAiHNidm?^Na&--TZbAANStXK_hZ*R!7+6jY_l
ziuTAGJYn8IxbEEi{@jXvCf%N0l}CI3Y<R`yXeMXUB50&;uTy>LjOg*R-#QEDc@=-k
z`los6`%ms~^WXH|^7^|h>0ZsH%K7P;b%p!fj?Ml2f&JF9bC#bDSo5PdF3{Qn+0!S5
zUoLIiV0HG(uD#0^CT1@`X!}}HFK65B&Lsv-V)=VZqJmnQ))blXE|~iGvhwaLUuQqL
z{BDn9HS3p8aa%NVb7iI{sS0TZ3;paCxI4iw)F?cQfv@TOp*Z#{3Ylwb3>Ti1I<2De
zpCRpt!N=WhkEgylb@;wap=*1~9{!atuU-FECvoA))?J-yt^XM|CrM9i&?*R5R_NP$
z@}>E=i!W!z->z|2UDvOAY@^nzrnd@_d93f>MVv5{p0w7O<AlZym4)2LBCeQP*w{Y&
zU7??_<#^kgc;CvemTQYk0uNUfy7hkBCedzaU>m~t`|t$5Pxd?&V!1)NR{Gp8&KGj!
zP0yRuD!lO4rJNh`Jj)ZUH#i>S%X<DtVIKc~hK0e-{}~RJ*#Ge@DxcuK{7%KXhozFb
zNwsDATWXgF&AX>5a?|CY@1b{QkE@#`7<VVRURWW!ymejO^@pcDoBd9euiA3y=h7+G
z3}HUZDk%&>PUcp*$&)-6aM8cr?#fVH$JQhr&wDaIU!>rm*zy%Bg~t|#ip2RaFcdJz
zB<=Eg{zv*hgM#(^-(0Wae?^;?h%f}YBH@^yALmVcc2*{H)!8SfKI}fY`0lCM7rPAj
zHi}xLDmPUH{%7EvHvK<?-LB{VIM&zyILlBX5^j$!DF0z*X8q^a>*^nLegDtUbAjE_
z71W185xj`5Y51FDXOq69a>H?@tPMXeEz$V=;(MXm_k=F)Esk!H4Nv;EUVt`d!}sso
ze%a*p?B6GCc1K6d%bcHS9q6c2U}?edWljALpDp`;e!Xu0!L|B7!?6tJ1&en6XFwDD
z&(Lz(`#;0{*y8^TEaChAq%~M^X@i>asG|L7+D6SHIlNZBtXjHkbHes*{>l#LUj9BY
zPmQN9urZvmk!MLl<E3@b2o(unmtXSo{OTX_VV9FDgx^NBE$5#3C{ti@oS%efxZ6`t
z8G~cRw^rZ#VH~ypO4zU3c(2bb8_$JlOYe9*$>Y?N^4@$VYo^ZAOa-f~7+9-2*X!;R
zu2}Zy(DOIf1HIRHOlI(m-5$>J_8^NH<Kgt?=H?z*-{R<NCEeXAWn21KwnwV&o^-6d
zsnV!?WyOtdmjIEUlkz1d+x*O(z_+POV*wKkZ~l7L@@p;Mci-Lz{##ux?3|}Ik;|Ni
zYxUxyC4CafmT#j(&;NLpeLA1vM-#;E%+Du4cCYZf-Ncc@+;*Owon1mf@>4}}{Pefh
zUwwK0E_<hav;I-A{aKT^xMTkr`u7<=Iey^5+b1$}E>A!BPqpcO-TXBfr;B;t%$maZ
z<#+G?jDp+8qMja7ZZB{MV*8fLxFPG<+I3k`ehaH6M7`WD)l&A$OLCT3i_hh|r@5IN
zlU7)2+2t;s@#n6FoYM8R>-56jWNtdR{8ibl(!)oE7sqTp*v``x(b2@+a?WS=xA|Xd
z0$7h++~Y5|*!0(HD~VmRG#*a;&#+1D=S1$Q62HSNjO?Gk(b}_1zDJ?!@0Pdu&TX&$
zg-*(Jn`)rAZAqHz-GawOi+J?zE?L1YskZpip6C@>cB*2lvz2e|eS3Dc(#!2!x<}Mp
zKS#az_wulbLk@#LDznPMyVF-!^vCb`Fujvyx<Kalk1xZ;wK+G><6Ijl{yb#j?A&9<
z+t2l^TAh=-Muvg$PDWMnODWlDvy~70XGrZ#bY}6DVu=%BO)q=sAhYqD@x3kD-5=w-
zO8I%CXV(1ooOkZ@+i*kY<#&88PmorAq7t?6hSQ$bgQp9BZ{Bgm#(RBq{Hyc%`O8kG
zC$7Am`SGY?>7<9ty$g&UD;cb{E8hB@&updi4CXD1cI>oqU9Wq@D#qD&a)8wFZ#mm_
zg_pScPTcuf%=V09%!*qP?{3wl+?}dhs=3E`^^3CUrzJe%1Lmdn2u$`(w~Ah<<#|Y~
zSR;7SnvD~V=XtPax)%IO{X4%UXHV{mEb-#g`Kc>7m(HqWoD}w3cH@C_;>CuCR@~aD
z7{b_KxmWFz*oW!8rV?MfeceMY=hts@`L<mtC34y&Nv_4U4;fRZ30SBZoSe6X@%7a6
zKidB}&lCR7uwl*oU#_LGtOP~_V*WGq{bzVGuVVVYgW>VNG*>TJSAV?zlfRAke};tB
z>;H;eVZ4A`>xI?Kx;Iz+R{5ReH`fazy+4_sHrW?<^yRsl7e8fq?@Vm&<$ChR`N4`B
z*R`{|JD+%au9<hQP`csaHeZp{q9w_xcMn>=Q##Jr$Z%!%N4Lr8HrL*pe7fVTKj}ks
zl($V|lk((EraB=y8=p4Z;$ESyE*f|H=&jOYJL?mqbJs4L&$l4|L?W}h+MkJvv9q04
zO*q(LnNxf0Sj;}LYkr-}Z@E`Wor<emKS_J%+Y2#%|B}7>#cs+9&T`l&w6MAN3|DjL
zn?0f{)p`q;#Q0}Sh^>gb?KbI=d0NJ^-qfIjTn#5&Zk~Hk7n3}vf!EjnSXtOFo$22$
z{j^Wty`}GADR-rAPoTGz+a=Kn%B;8I`M(#nue+pO?0Z$$G`nop#V3j~OFDJ@MJ8@z
zJiNH!RDmNy<AeiW6t3AmZQHx%<-O29QMrqkzMb<@M0n5P9CJ?X$%?K|Rz1)=$MLl9
z{d8xq%V`_0l%DR4GMfH<b)i5|kx2AmG3mbDi<6I4D8FDZ)mYTU0K?D!l>cW?`Fv#m
zH?Cd(87}&Q;@A2=!=%bb@xNJP>t8He*VMqJu?T{ne0^!Ev8QyA+4RiJV*78YA5wPh
z%n;F^op~a)_oU@<iFcKc=WW{g`}|LhD)YZh>;E%+$z94IkGHFPt!CHVM_J#0)wY<K
zeGiwqbz|x212KgO)7d;ljAlx6CCeK<$bG$??RjI**@ru&9$7q|^Qx+GqH@uzwck!|
zViw?(eBU_V(Lo4pc;w=@^AhzJxIrz;Gxz^=$Fhnrp8tzFP(z-Q<4f0fv+cOGWmnu(
zlS9fpg8Mc-)V;V(oO{~^;T^|X-s$%4Nf6>|zipHFpTR+w|33q}as4OV5|IFQdsG*>
zqbUjBe7)5CqjSW)4&8;BDSg(NxoU1&3%jgh<{ULPT2Zg*v}v`OUvfgxmwdsB)nVH&
zTy5*+`E_naDNCWqx^1hPbZ^EUI2Chdhh%@cy~&Ix%*AK}F#X#q4*zS2lK;n-_MhQN
z)bp?L^0CoBs!qpj_fYQrvf`^}&a_L_J0*<7Z=9Fl&fBla6wV{@&f1~p$$y5K_y0ZH
z|M$=Zc1Qd^DEhWf@0!wwPjQhqUj{_nsK`1WF-x@bSh>p41)a``A{`B3mN)x%{rs5|
zb1$1yy!+wopfg3U%VyQ?c33YnZR5FZD~?L+Jj^;<p@E^`Y?E{b!wb|gl?>D&pLO=G
z+cs}f4w`*fOq)mQ&bGi;nHqg>>n}%fgc+=!uj<&R#MAvrTkp^Uwl_Aq|9Wnnn=1dO
z>gBG+rW<mrrH_g{v}Ia3V^ISG$13ZT2K)(>=#jQMHe>U)C)pj3`-)e-Vsq&|y=wby
zwG%uJD(U;!YFSIBp8sL~&!OD@o9LDOU$$kv&|p~91;@<uKji;ucvt^Mdu9F0oU0eY
z?H}C#$#~~K!;SEu{|uLIu3i9dEAaXLDPJa=;wpM2-M`&u_Z7XR87VwMYVA3l$IlCE
zpKxB0aJw$3AUiqmquj(LvnQ^IchAwC#6EWki%zyluT07|1IE<Ec{ffTc(&7GkNBFH
z%nL8B_b0RVE^mKV;*s}o=F>^>22QKBT>_m7IaQsv>-Kz{)qg}x>a*&%mDOUiQ*F;4
z>&?#DaPGU;TG@YZ-%sh7IJ5l}zlBW~!%O)i7h_^xtX@9%;=L^X^n%HUK6;DkE}hLP
zp{-ogQI~jXo5Ml2jz6(WjxNvqeCPhp`<Yw%UM_Ds7q6R~I8mp8?US-a5>E?*=uYd1
zuCjZwSLO$AyQ+6~N$|D}rP3WrQ<p?sf8(1aDzj?3N=x$8n3TQ(&h<+w%HuBRe)+n|
zD(CWlhUA+sx9gj%6Ju-e{Cy-~=M-VhpPv2i_-8-+>0rgV$9Y-wt7gARl`OxnnH93M
zY24koRW4w+;JK%VHZzqkV?VR={AHWW<@YoCSNV$G-Nk+L%_ZS%V{dJ@H;YrMnKx=J
z?Fh9lc<}ewvAX>abJN4GFWTvS;_Q;}ZPPvXy({6A335BjKVe31r`9{w+T%LH8H};X
zJ3mZYUby&p-ap4#=c9LB(Y+-7bM2oW&oWQ&>SW2OF+F&qkx-Uwk=(%7lrNHLaPxLd
z=kl3(=9Pufx4cd6YaV{467+iOhP6|rBU&v~xUMu+<gI<QWBWAA1yh-itK>+=dYn+`
z<4~S+U0%Oc@8Lz0-__C9?(@XwK5@OO_jaz&`e$Z(Q?{%#{@%>vQMUi&7TwZm0(YWc
zUb}EFwszesi-~GGJ{_scZeX^%c<9NK2PJ12BA|(pdH%=ge;VHIf1|zZKf}u$(+lDD
zkM(~t-mbq9?)#tN(v56LLgYiO(m@IK@&2Fc^Hf2DPS^i+Ati67c}rJCWtzP<y?ugt
zhsPz2d66nP!YwYWGad*zurqqT;9O&Ce5@>7N~iq0(a-xCyLb29E%{xk=d;n(`q(Dc
z9&6EC!usEf9xr>K?HqUcz20q~-5UfvOP9yap3+vylc|?9Nonb!jWL|w>6z#56wc|3
z{Ug2Fbldz=C5P`9yjPe^yO4EVtb_IHi5Y@69<tk7xwkA}FRQp^#CR#@$6<#pJNh_H
zHE!O!XT2fGZK4Zb1ZTH~g6pR_C;YCSxa0P4ws1we&-SZqb5%ZZeqWRGh?6I9cXF1^
z!ZPK#r(4rl-uv*+EIxXtqU!Hg+2F%b#Sv@Q%#+%9IbBD^Uz2lpkEfjX<SpsnbLw(>
zP8gJD#a387$`^}?f7=)Bz4~_bv-B%@$$}={0^HwHlq~%cgJfqUY&f;SL4vvH{81~j
zg)6qUu6;h!>a+^`cRvAd$%K#j%K0<QHs_psw75XJa?OuDnag8-v`Jf6@31>$@_Y8}
z&Shc!S;s!KOpM&XqoXpRlPz@HhdWZbHRhG<-~3)G*e73mU&?84e8#iiVHYfZA3pEX
zH^*GP=kd`8dy^jfwY%-9me9$yu`gcaT+VY|XVT9m(a0#JF5wPOE!mwp={*<NJ!;|?
zE^R&f_UN5y1<`xF&2Q&E-Inp^I7iQErPVAth5Mx|^6G*+?H_7fs^7ft_H+O3XFu8W
zZ}R@uZ!Ep7Qo82s?Yf%WbLVHj`yBIkdy9VW*25=7#J&f|zI^BWYP$K6<M~BumeUd^
zPKaUQVz8NJy)SyYo$Qs#!8@<&@-ErDZiA_Gh3eGBk>YQ>vqJA^izrM_Y|VMVXXL?f
zC0^j=CGUKVD+ztqyuG{IgpQpEO-cz*OH**)urVx5dQ){yqKlozrL@gEcN+V1-G2L7
zX~&jnlKYZdj`%ISU7Q-uRc@eV<S06Q^^feJk4%iUg_+D}7vF#RS%TT1bDfm#Y{z3C
zR!g$X-QB^W^_)BI^r7jQiK|Smm35bwOi(&*wz9l>hs&GSzkhO6oQrv@v9oty{hWsm
z?19T(O`ElKw{ONLfxaM@Y3f}bw;3K@JdkRk(BN<)p-Ld@Y4VS}L;o54E-&d0n67ha
zdYAlG&(bGq3^$*9FrS>p^E1J4f5t=C97G=$qdr(ye{laN=AHi;HmqCvpJD0da7V}p
zu}GkU%>H(r+^_bWufoJ9{+zZws%<6D$sN5Xt{1mS%Jei<g|%L9{WAN#@>_%R>QjXd
z+}u5-^5c4!*}T8MKHV|7;OFe$XXjY!dgV$#yxw8zUD~^R(~fI;%8`s(k$USSn49>F
zY+b{z?TKEOX}&&1H+j~lTPO9GY~OM@FYoBV@+mspN`-<<y8E)5B(}Zn5?RYoJ|%qS
z@oba%Latw5NBP^tDVuG(w037?Qu}Y+C!fAgOWv%<cd>DQb-kF_v6&y)1LnK!x~6vd
z$*c<*pI)t6?7w4c1eeyP18EaPW^5>KcVK^a@|H6XLzSxN(H|4{gk~>P$PM<5Jhwby
zWodr4PW9Axfs#`8CUa6&s#o4yIyvj_qu7e=0sdk!ncuc;@@8H8cJG`CYO@P9CwOc$
z_Wm~Y?-fUun;HiuDckfuW{_Pfdhq1Rtf=)Jd#p>fZt2Z4y?wf3qBCc5M#7$Mog(M<
z8)pyr&f%YL-CpUy8oqzy_A6gr&*nby=XCUnd6JV0r6)G>7+FfPd|6FYM_pX{@U4^<
zlL?;6Z?-vo@>e$IuH>2Uv^!;Lk)OZr{Mn`|v()D5-zvZT{H=Lm-09ET!JYWm$82W&
zkdfWfJb7Mz*mYA~^?<z|x+S-JovdqBdCp2Zsb#)<+S;hFF+^snyxFBQb$L@0ZCqDI
zbqaln^2sUfFnN74v2*g-$i+R!E-p;F<uYB6d0PI|m_CmH#*O^#TTa&oyfQqfFu&Sk
zMf!xJ(%Z_dT%waK@7zoc@cVx9=WNr<hoq#U@8149$*t+t-M3NZJEl&vh)G=BA*Ljv
z%$!s0ero^SnBwv}y*<8iyoEY%qB3jjS7vQn_fhDjl!-o<;oW0_m(MUf*wiD#=-y$P
zFU0Ze^1iFdnYFz4rWQUsDALm{d-P`iNqej5w~~L(f6BKeJSp9T@lsZtz=f~XrQ5IQ
zs_f{A?oJnq@v6CTz}ls~EJe#RHT`6mY9mi^xXMM7mvxu--M7!&-SsVg?!L@LpT3#L
z!N)s3RqgLcy!dX9=bF1Qx17s!3)y;?OK<1qGMVVAk#>@W>2uzMmCr0h9&1jX{_v#E
z+dY!Y;$QBX{;lO!d57v|akoP4vohbGsR`}+`}U-k_YJX#+bj$m?2&6Lye^0C*)+jf
ze)`|#-+rIHWRaej^+8)vX7$QX9SZBr^4QCxg)+D^3zyu<)Rys2dM~}E=lHp%Af5#q
zPwK@6#U9r=E62_I=ITyYhVbnhw{MyEE<^dI>YYWI=N^^saP5(+s#&qP-#_MB-1-H&
zU#GsEyXv?|)!IYbmc2RSGchNmH1O5OV;et&XCys%Ct*D$fHCGjLr47+%ZK*AxlaCP
zSP~w3A>96v{7=3L|9^)z)xQ+I%1|N_=*j@YqUV3S|L6I<v;K`}>3@brvvzSkN9zYV
zu>VoMwfrw%)$_kUH~nXLQf2>8?yCKZ;_LSB&rbi(pnSDnGA?VDPuQ$=Q*3TdKeOex
z&HCTdE2j&H#q@045uwa(qqBYv&!*3>OIJB3uUz`~==X_>Tz2Kpl)ZOs#-0N|rwi2_
zEzHwRshq;pZSy3tO@MjHWY>MI4?SxN*DOBsTPdvXh<NVO4f|jGnY-#Z^9J>;p8pv*
zzODSv;5={Ve}=l8{XgY)*cyGab^7fx?cY0(2b(@RZrh?9GA~5ySLH;9X}-M%mC{es
z*cHF6)VN{m)>xTox7T3THNF1~+xOirn{<PFdV=mXPZrm=KO-ie7BrZkC8lbZ{7m41
zxQ@y0z5agN_HX{UZ>Q?oE1o9$Pa=Cy91yiIyD7<1x?282f7bjjmapf3e|Gvm!^GF^
z7w3mu{3E@jKILA#e`WcDpYJZ2*_FS4)OW{0xnDXwf7a>N!2M0XZ_k=^@7uRrxjzxv
zflC+1y(~DYH+PNqN{J=aTO<8%srjTV?2*`)z;H4^<!6Jn{}1=A{=a0tp8x$h^*_Uj
zFZG9PSJhv5zOMfMZ2f=kYfmUfXICt6R`j@_G*cx#iQ%};k!f~MCRJaV!U&piMOM4`
zpWxfzf9<x#|Nh*p|72TSwfuJPzx~x>n^!vONWE?C-E`di-2=}_XH}GpxD1uT9v)`3
zH)`+}jt}3v_ww5HIZC@H|2DcD8=aZ5_p0i4!P{HA&UWhk%M_@5w<D>@TPr>DC`0Ld
z)Bt%kZ+>#|s@sPP(;vqRc(Q!^c;~3%mMx(bPgqv6+-97^Gxe2`5u01V<14Z`CHimA
z3)D9IR;*9){;__hve23ny6*Fp*3a$enQ>1tl`E!Q=2~5UeP#Z`wbrM1&(p5X6+S$9
z-%YM1fwS8`-}x5$>B4(kv-LJy4DZkq=0%K@va|lJ{SOb*`Fe+A=lNPaKC(YuI3o6G
zl;G0*jH_4XXciQ2XEF28I$*GI@ySZoXWd1&rhYkFxb}W#&t$(?)-6i!Py6oWW@bq_
zadW~a?g@ns(i1Xf^`6}myu7EzLCA$~k$1F70>^o+YX??-QxLqjxYp>A#k!@FkMCOL
zo;iQZZruifht6}KzxmIgf6BS|M)Rc|JMv96|7hE-xOHra`sF{;$tw=6E;<<XI`wqr
z`n%@>QX{73KMFha*y)+J$2yzjT-hW2D*u!(3q8B%J$<slsa$5Jo+B&;mzEheEzZ9i
zz`)ibzA@&GD_6z+BahD%N}W}k&gCRCC&y^(0@vF6YL^`OKMC&cy0Y=oyRXs~@7C7j
zuk+-7!j!N%h(pC_)9i%MMix;80Y?@l?fHAV&+d)o_P(Al|Ma!Tduugwx7}U-E9tzk
z&zU<;MsJoU<^8?Dce`QoiVx3EuKKZv^=D#ts9a2PtM9jMpUl{EcJG!COSAP{z+*3!
z5!GYI`jKb-qqAuxzD7@HX)0~zdf;+j^EQKpt%brb!Puw8|8Nd4J%4ZiWZ{eZ-?;Yw
zXSld+>IKZXY@WaFhpM)|`F_mS+pEob_5Q7FV&Y6G1x==jTCtj8pROosZdWdsNa8!*
zR#N#zRwlx~kmYykB-e`Msdc}_bB{%)q$RyMvN7+k#hU7Vp=^O{sfnN7)Nj@)jrO(A
zyKe0JeC>{N#aqoxes6BOXBVSpZYbZiuD$#1mg^PjTX*lCc2SI5^U#qXOZmcG_PZwT
zF9}^7z_nR$^3%BoWLrfKzPP9KF>G!A!qvP|l3(W<yyAGI8Jio*61{16<CL8<3ykH?
z)nyu<t=`{Z)w1ndxm4YJ#qx`9w+3g*%`dFF&X(}RL8XI{^Y1<L9SP;n^G`W4eDQ(}
zyn&W8?x;~+7yYU|us`f#%kNvR&dcu1SX_4QxkvB4BgH#6omw#W{p8PPDVskW+n@M%
z{<qv<=l<Vz7j8!VXE?H~`01gt)XLq@{{|Hm)y3_ZbKU!Oudv_jLuN&lQB#VJXD+q7
za9ejNU-D#jg`b)tkF#a=-`wP3q*wUIwVZd}qFH4Vb63syW0=XYwdvfcXC<==k|#Jn
z)0)ux#7+60=g)j;8#W%sg{2?9{rc|L?7w5rg?pEzT{j8*XGn`_tq4gJ{aE?=?Mba@
z)re_963@2SKa{xs@9wwzZ+-dS%4h%1`_J%Z=6{Ckm3D4#YS+uZ`WI93zUOm9)tp~u
zYagv%8|BY=@=>+<g*ABz8E+M)F7BQ8a+6S6*lC`cRh-rZZiV3{t3~$Jvb$eVZhG#q
zYs(c=mQ6aF4nO_7NI9p4XR%J9{}v6MhF0yl9S4{WRcMFx`^`F7%F7dVcKPvT9`kRO
z%bRXu=bHIDu0qJ(w(|9XMXwLu`g{IcH*c|5SN6}u9n)Mct6QhF=TB8y9V^1K%;cYp
z*#QZIN4;tHe;d6&d~KKb#FB5nZm%gTzVoy2cG|Jxr)(i<u3WdLdRXu<+?wrleR|yf
z3t!g@zuL8JHp8xFuMGlG5qCTbpYQf9*|@+iXu_E{;;j}ZEMGTpDtyTAkb0#3yVu{X
z@5zpN-Vty0?p;kg_vnyvnX-EQ+1&}M`|6};-TAO>@|w(vac9@Y-MAYU@1>V!HtoDb
zq*<%>wBntiVJ1PMe!{xbRIan>CvW_a-o3}>a#rxP3(NMjJ^FU2I^MK(N7rL+t-hKA
zn>L=;EvlLj@h)>(nC7FuX1w}`<UjP@aoqRnnOoN_`K{42?%C`5@E!fAeB`J<_g2q?
znmd>;XslPhxF$MwZ(rpe+hwmO-_Q6KwPydVO&V>Sd2(g7OP2IbV)0m<`S%Wo<UUuH
zkLo=pv2OZ&w;k8Ir)FmS3R|iYUcSIzVN%7OEt88UJyiOvGP&@Cop(yl1@?7;G5;q2
zYkzdN*r&TYtm}S2$eT$%msJ|w9hMxBmpECeqB8eRi3sC))ZsI2v=K9SR|&K%k)8kH
zUa5cY{rAk17tY!ixNY@{M;yvqHD>IYQ4lAVSM|w1-cQ@nWcN-}$u;7~em&gPrtxf|
zO}G72nH|CNHz!Y){ulRX<xSt(+z+ph2)|5nUg2K2#&$)Y?VD8ba8`pI)_rdZn`b@0
z_U)K%c=XN-r7!j0EbtXwvcvm7!<N7E6st97M#W6KAzW?t%_1ykLIVTiEz~+3tzItt
zeot}x{=Jhb{y1A)T=G$)@!gudZiR--#F^#m%8u_5I%Bx`S<TAWL)L%8zGU7qzqLL&
zR`q@WcX8#K)5}%5rgLp;e{0xu&PTPYslLMK$;Oxq?3ox<U_WZ3;_JeNrjLJA`{cUC
zoBg=ulBe?NO!bo+=CVse*7;RvEh#zhGNx|%3ag4mZ}}G6RPD;zR+#zC>E-mZn-cS%
z8*FFKS!EuZ=Cmd}yU1qa7UrOH$DaLr^h!Ej>PM4v&Tp0aO;H@DQ<_B2Zo96ql1F6j
zl7t5z!_g|~tMv>wU6UXFUh$~%rr+un#U}4HAH55e*{Qy$=hvLclRRx9E2{gETU#&w
zGqhBP{AXBrKIT8eezW*L{W14eetTTM{@&3wuL8W;b|)t1Y&`pWhfvC9PmZ3Z9*?Oz
z3J&_8Ss--e`qlUOC9kt@bF6#v@649#VYednOFeUsl)X*boaDWKmWy2VI*B=xPR+bk
z=pdVp*6dxr{KlPE+dkZh{Biw=kfZIMazl??UC}s8MlDCP1L@4FRXsh86X#fbWsjES
z{#|@TKH+kl_D!LG+Rr?WtTy5fe12l}^CV?8^R`H*>59iq=P$m0FZxHe-=}xayYAg~
z`S9fZHm8*$X%GK=x1CzE#rnMO>hnwu)@ZSX)&yJ^|J(nc5O4bF4cF5r`|bFsfAh#S
z@yf84%;;ODrRrQUGH(y^PU70Yqm%I|&araQoo!2NjbpOQZzZc-p6-~-vHR2Ie5V5k
zC5_BdY?_|P1h74kQd?Y{FY@xSya3BY<`t8!ot0oRKDBj&R&57M`HK5KJNmR&rhI(2
zYT~W*w|b`&SS$jbSN^s?{b|CTZwg=5=}DjUs^>bt%539G&M*HN*lxTsSaoMZ*shyJ
z_p-kiPmv5$js7up!;T9(yDn+>OWbxZR6c3n@#V<Q?USB9Ib$^2;lN@;Mj4ZpJqasr
ze-B|`T*&$+++5IUp7}?M&oXYCJ(nJu(5^1cvo=F8zWn5t3C@37@*Zu~DcQZ(?VR=M
zc<I-ZoPILQ(7DpY$+KqJ4bcQgRu2{dM~1HF?~^{~hdW*RdPDuw*B$TUy`posXa1Y9
z`OIZwbAg`Snm1<eFJa#HK;@N<<)^HD8jW=kNmt#cOFRs&UAw2Z@wVQ(<5y?)2W2qJ
zADLzPciH@On|o?k^OIx4{muv<&l3Dx$?;@~)}7J^ee>po7smW&=-K~-J@-FDVyyXp
z2Jb}ZjG5(s2HF1%Cv86J|7}{g|4VRab+6vLOVu9fANTE;6niSMp;9cpx+Rn2(e3`J
z5}#kb?%MbmWeD~B$2ZdoJs&Q=Vyge<w*T8Op}UojWLM?tx!D~4US4~rNh0s3M~(nv
z;+Ne!Kr8Kz{dxdiX=l@IKT}{q^8C%o%}RB3$JU^hJ?m`WZ}s2oT%M@%`M&F-?Bl)@
z^yhq1iaDS=vv|I_hO%Pc+n+4c&iS@qN%GE(EzwP?-pgsfdC%!1SL9x}?t41zy*SUA
zliL`23J#xUuejy+i19*9W_j7<Th8{qUyn?B7tF(aVzc!fWe<0;J2fkg&-afBMN7+H
z&%P=a-}d2mh1WmZz+)S=Zk}Ed>#4)I?{MK9-?qvCA^&^%vy1X#6187Pt^Cd2J~uzb
zSMSliN8U3_W7B+1TQ5|6nB*&<n##Id&f`$;8V0!t2IeLEFTMM6*6P{6&&Pf}DciQu
z=Cb|7w6aA_5f7qM9xz`*4*>q7*Du!}(ykZp*m_e}&%gC?c9_xZ(A~RIX2fW89_r*|
zQV5(}lrQaMoVK^9!SX)?YRQS77n`~mp8sb+?HXhDKz4CG{dzk6N=@qGm+xz9^V5FS
zzS-=WS#;s&(Ufi6(}E<DD=mZg1LrPnWY|cs=steymDQU#xsCg`UeRA~nj3s*dQ|tj
zBeT~{)IAdy<B$_08IkKMz2okV&#u!Jm;UWu?VY{K;a9@6qq1+dc77G)GWoHqxKwGS
z|D6dQVSjJL{%25oaD;hD-?3-eE7vaixV}R!BG2xuMzpt+kiUj^n|;~=X-U7w$2=rY
z9*w~)f9Ew;@_&2Os~<7x-?4lViGLTiD+QV)d!BGB{rxa9Bz03!!$uv>H9z-wo6Hk!
zy2qR6c2#GObj|mVOD`H9Ea}W)oWi^_HS9B6G!NhVDu(xHb;Omz7qfcS8|nAdIPmyy
z+#Ypvg?dK*l-W53hxy#ximaO0&DT3uF8$AN$p1-p)av@wjLub#`(Dhwp8nQy;>Mo!
z@4~+;3w)|CzbvM|WY4~jI<qRTtY6UNFVtQ3NnN96{+or0J@OBOZrUU?l`~26Fqrdo
z*KFs^yJvCD<z3H9$-d*oS`#E1ztv3O)==N}@O8xJdq-K1Y<vB<Uii*w;VBbyzU;^=
z6DTNtddrOM!RdLkCthD=Ao3-wD_-h_a9rHEJR#kzQ#ZUT{xj@}&=(Xen|7o}na5LM
za}LjuDJ<a^*Xe$_%kQ*TPO;g0-<2=k{#!cV`fQG!KhNpfpWg4R&n9fRt*P_EtLDB1
zyJu>;-l9*c^ZQL_cBvG}PK->Pc)iGK{^rDqZ3TxFrY6o=$@Cnp#ybAtY45R#D}Fc~
zdStKk(#BN9JYx;t^Ojq!Jnp<3PU=}bu1<b0^Ie4T><=lk_QORkpFORYEnlJStq^d|
z^~rt1TMQ>(A7H+~^%7?bi(UWWY3W-3Lse5-pVXzUy|!?bvr(RMk?Ea>ZSKkn^QNv`
zSyAnCb)8uC36*pX<$}p4rOq@=5(*7t3VFIOoX0Nh@iWWAm$ur!@n_7QwSDsQ+P3%M
zJ3npDy}#+z!)?#mC65_5hwJBmeJkxb&HHA_?Uhe<Y}>wVo`jrg*sRoceZevn#ezE)
zcTfG9amT^bexu3z?X}zA{AYLx>P!56`)~KjPv*%M{~5wRJziduK5KpU!(6HJ=LK)R
z@5`9Q%=2l_#U;Mq7xl_a?K5uRQs8o0aZDtc&tEY6bRpk#fy*gZ*f##1t$W(#rC@MM
zUd_?|Vu5fivuW1b=Fc=wO}X^PbB%xHa_Jjy>Q0xhh<TZq7|xf{;1^Xhxi!q}4NF9l
zIrB65-40Uihpen4Vj}mH7cF@&d{Sro<vl-p4<GNGd8SLW?Ey0br%I{iM)US9r+Wjk
zj2so`SDiSaKEYLao!Raq(#bn+?MMr9J96-6xXixZNBW{!*M3QDxVUhB<Ym4EeM(cW
zT@7&Et-V9id**az!#B^LO_n*n>c_8F_YYr-db-O|CV#2>D({qSlkc85IAPzhiUZN5
zKRtwYBpffi#geWd>+~bu(>KXBFmZ04($wd@talcPOuRaEj`Qx*JkI<4?o2vUH7Pr3
z$8Tb~#io{~y56B5#oP0iM!Q}<w!1Q4NFz}vmq&bJYM)2JZ^<2;n;SnrFJO4DwfArD
zzU9kfZp67ii@NLb;mqugJ3SnU6HlB_UmCGyztF4TjC-P2zk=r(HqCluIzedZL~e!x
z$7Aj*7BKFyUFPBJ$ui0Abc(*pCu4){6Hf9)Z1W6PdGhJz&&?r!92e|;*S-2i=0=A}
z+0l#l&dQvT!_U!jYIXC@si6k*6)b)q_*D2+U#McT_rL3(A77gNTiZW2s<vD4uH@&!
zoSn+Lzo-5EdEiOi^K~k_KISc$r?cbo+uW3C+|jqIEfsvt9tA5*OiG*nR{QsgCeBTP
zjVf-H(#IIAe7#*RZ>{~$khlGF`7Pg+`__7iv-4-{5xk!C`ATw=<%+NJ{F$>>?#$ky
zlD^YJ$i1&pImcPqQ%o{KRO^kO8~+pS>63%5Y>gMJD0>yUCDtZ;`?QZrZ9>N`9IO<J
zc+$?ladyLO3wgV8jyE>3mEz5L?-e$0Y=2`XvgK+*n?~2MO*X}oW;+*3d<tPOa5!&k
zz<4d{<>ttWreE*G`rnklnB*&|UUWx+b5B8$ltGu9L%fCnXPMI8YYm&ErL9Z*bd9X9
zU(uVeS!`Oo!KnpR{FZwT6&XHlJs4(joXB-+v-bR2x3_Tpi*LHMnbJ33uT8J`7`<!h
zrP*RTB;rlpGDfW9te+YB<Jcj_dx0@=Qy<-R4*aOGH9Au6?EAc&o8rDZ0`nA&^k-dn
z|L!Nbh&h3wSwm8l@6F%zBUM+wxBLl}5sr$y^D-*+_{>61ol9P8wcht=H%r{+RCu~=
zPis*Wdl2J`DIo=%)9$J6m}IHW!O|}!5|&fsG|5Bq?d1O8AX*HAOG(Y^&0hU8K6BbH
zdu{8wll8XSihG`)D!qGoU*S2cS?B*Vw3vg|`>rki&%nNY|DUSWKTdrPxs<f!YRST9
zXZEEozxlNO&h9fi8a6#i?LBl*!t!Bi&4bkG^P|@WNz3}`zti8-E2Mh4=ES>iCP$yK
zpV=|_nRa(!w(^+;B9YIPc?=q4RpyCYOsois{+lY7ep6_BhrVOkt!VDw@BFSNH{KAw
zwFJWfv>6z;F<<zqs&wn$x!<4z<9~P7m@6}cJUBgZf_oIG*^)Q?KZAYL^MCyL^*_EA
z{4#zu%f7j!|IO^vFW>9^k+;3&cKqDmKY_P9SPCC!z5N_nu*&>He06b{&Q|I5Z(^gO
zV}sZ)vux9NpSs3>MMvQBqnBr|6!ofm(&V)L-J$nC&Dj*>I+vf%IFzj&nKI$!yKR?#
z_PjfFFUo>-_B88QzBhB8Po8u2)Z;&_s&h6~O#SlL`?uHS-=QwyaTT+Ry1f(o4Qk)+
zFISmnU6&NC@=b)X-M;0^>)D;@)pJv9`eIwEu0GOGdEOf75cr0Hd8_+>1`ZU@&}QVk
z?PdMvuj}d`eEa^Np+D5t-tmHIbVZ)d`x-|T;oHZHMcN~-K>C?Rv>Q3+z4V{q`Rkbf
z3<ux7|IZ+|_@BUC{eN{^&;OCT_n+b8tEc}Nw)|&!sBo=jH*Z;`$?JZhzjJ&O%co|z
zP2IaVJg8vl!E<*6ZYr#1ICQLE^@;c_-P2j&mrajtuU%&3Ygr<8p?kls*%uui!O6;L
z&L{L7k22&rKD1SPc2D!t^COHZ4zE<Mt-siyY_r;nYkm@=?5n-^TWyR@r~ZnIf90Ra
zWfZsOp2BX8?hVGA#%2sR4os*PsFHg8aL<+HAJ+U@oGmqBzW;~ZzQtT?PqSvPov!<A
zf4QaO)TGe;ozdLA+%wiH?fBTcrCi8n@{fKW@7a}laXyDNxA1To3kV+ensJP)cYmn^
zgSd|FAD#aUX<PnX{TQ>R%=z2y?zesx_x!}OPwq^P<gQt27bO4WK>oB{{2VW({H8Bn
zohcrE-QetGmFd%iPQ6t~yB8Vr@14`r?+vTUQv^5;Jf%*rli}n2Ka<Z3{b#tL_4+@9
zt7!@5Y#n_0ruO_j{~0E=FRs6#^`GHCgWIie$C$s*|4gx!{&z6^Kf^DxOARIj=0~r`
zb7!1f<G!lf{>zD_m5b_4PaS!;W?i81R`d5sH<*hPXX`M^-0v*a_4<|FkreH?{6_Y!
z)Fmqp?zwa<J95v_oX7HeLT-eV=<ff)+pB$aSKH!8fmz!&+0MRq=jJB8*#(R4IHkm!
zuIqm{$JmAK03%y~k(cZNS=D)+%OmR3|IWI9`rr92W?}oS<@JO&YoCOVP+zX+$jHyn
z%>U*o#vNU<HR95v&`3qc*1iA<&IvrdoATt1>nk_6^Y@rq`&x(Zz4D;JH+}ips*-Qp
zW?l2RWjL)jrS@dOg1O5gJ}h`^?J*(QIrxf==c0^F{)U&<ubcJml60BJlWlIF(>-QJ
zdV7R3Zjuqc{;p=f0ehfp!P~X3#ePkhRXfKj{PwbImkwn&Gau{!&mi=4?lLWjNe5Oi
zdKax)xuf<&=B#ZSSN=HcW)$lvyJE|ghdZ}>%op~|FP2er{QR(};1owv!>*^>^B820
ziasy9r+a1bhc)8c!hYp$kt%Q3Ev=rNx;=N(>Lu+byZKlYI5=3^e?RV@{_M(*k7^s)
zHm;P{JO10~c<7eP-`*CR+^f3X^V~W(*?+f1?&GJ2l8YJ2L;_tI!mFh#O(pVg+1zy&
znQ-iP|Ea!!4afa_GJjUj(s`5n<%g7X#Gf6vBGr@&Eh}Z06rW#hET8l7XyM0-$wwxi
zX6&=oaIao<_hs3s(`w0|W)-Oy&nws<_>{q1M&6L|*2X(O&Ibr)UOS=O_AY&&XP)w9
zJ^d-OBag5P965N!GWVvA)8ouL9wv;}A~I%`O)o7hPS1bpTRh)%`{ukeo4hYf?w^<G
zFMsd214Exbf99mjf|vVTCf;`V{XpQnN<QQBztOANdKk_u&}7imvWwI1{usA+P1Zf$
zYm2&0aqI4r62HD}d*Yvi&yO1zwmnXEe`@&D?~~KN_wU1=R6V)yV^+4t+FU`k>vc!9
z*Q8jl|CTYoTISR5sp0BB93&o_FzyuVT<$2^Qh57ej%w!HlVvI%r(T^qGH18J#81&G
z(^Q^(cG;yi*KVWOTGf58Uu?^nUd@ve8Cr49Lim(bz4(UX=KLL7-}(n^-mpO`hu`{D
z<MVmyg;KZfuF-H}lRg=CP<s009rDwYlV9D_zP`Rjw6tv5rK4Z%`C?vet8@ES?b@59
z>N7L;-Dv~G27jHtNu>+;K8Ig4d0TZgcdK^2o#_46d#ArYs+c`hd6mcGkLLq;BW4}D
zSA9Brr}BRWk8O99CKv`W^BB!34Q}w7)3a($s-sMOM@{7Fj9=Xm(TBh7UhQkAy))>(
z*Nz>(vo}tt%t%&=esZMX{Qmb}tocgyO>e)h7js^?C`z#Cqo>T78-_=>IV(-MJFO`3
zr=OckkJE-Gp9c5j2e%{MJl?u1^J=bfex_;fmv85;Eto7)RGG7M&xWIHkM44(h$lu*
zdKqRM;h1pk;@Tzr+(&upl@@kheS9D$L0jqL<(`s98~+HZE!Ar+y0!F8d2z4bPcfI?
z$z0ow^bF1&XIOdQJonbh+mkN^u*J<@c9w7D%B=ES>6qAE$0eLR`tI5M%$&nB_pI{d
zo@ULM4FTCfT^b}TeFbfo;X_;Z6m}>+`s9kU37gVhNi3e_a;q++=%HU#QF8t1JK^f7
zreC)oUN7Lkw3Bb4?6D2s7Fm4XI3+el<j{k6)*FxUWzUbkEwME=@44gkCHprunuJYy
zsQ>Tsw~E#`%ThCoq7!`I+`jQJa+4DS1N)M=mmBWKW?mQC()dP?_lTp%!DNw%i923y
zbF)dFVAuAvvi5sN?)&#C^XvuAnPl2{DO9hPUUWi1Dk3fR_1ul`SvK?J{G6{9UeNcS
zA#|@)S?{;iH?Dh@Utzj)FWczlNu{NS)-L?*ldyR*XVQZC_jq>dgqtwli_f_Jy?l~C
zf9KX{joT7U9B;kU7-Ym-XV2R+`TFIqD@|r?_cZ2Zs+Tyd)oFCLWPUHZfM?zw23v+z
zRl;%h?OTprN&TGPyTt90zs~V}zRiWVLcN|mZ(8N<!#8yyWUZL!bLuY%s7ejK{MFkx
z?4ESD`6LhZ?S0QQdHhy=Ji!^n$p9NJpT}qGc<s2;zdIk<Z<t)~`sT8~>*pjxtuswm
zDnDucywP#8_u;gFr6&r{roZ_9ecC^%%X@b3e6)SrMH@@&w-Z*mO75t)J)at{%lG+m
z*5?BY_#+nWxlh$0arR1<)5ZBBFH|^{*aKB^dKe|2MldbE(coUSe5I`3Z_lf``Oh2I
zgsHdvF}dxMk$jpx!R`FS##aU$rq2rQWd;8Ts}0=R>*2rrhuQJK*085dTd$p-_Bnp{
zoCT*gYTZAww)I%+nXrj56~}H_cglJGabKo-cF%NuwZtj6*jObyI36zbNoIAsziR;l
z-=@PyqrCsly8O2M(#D(ox8CWf_L)y^z4fUwTk1sgQ_W8k{xhgC*K935eDTKdMNTF!
zm&{|YRLM-0D4#laR?zFlt$z;vp3c4HY1ujhi`_T&+`f8Y%ic21KYR16uV0#WJNH)o
zGM&#RXU-l`);m?E_Wmxz+Z~)%{d_gE)^{nyPm|ah`1F`X$o=em<%F`+yElGKOTIFT
z!6p^7fi?d(*USCCqIp3rlhgkk%I<#?y<Gogn-pYGJM(-(4Vc9rTTk6SytI4uNu4h{
z^UJctxeKm6ve+}z>)lij!)A?+6oZqBm3NyMcc$0ouW+~=b@G|prjwl39^kWWY9%A8
zANOe;t@u;beR$zZg{%qQOMJ^$@4k2EHSe<HHjBRe^!?T$J}osfLgCPcJ2!r^>16F%
z`bVx}|F!p%!}|}172k9goW$|YRQOv@&FpX^V+|%T=86-B+s;p6zNWF>{7NaW|35L7
zZ->5dsQEfw)p<NUc&18q(1w|1k*h>zdK&ke?t6L1Gf+V3*hJMQQGL^^ZcY7izV;EX
z*D;T0bGBsXwSAms>c7k2!b0Ar2Q|C5B|5Mde82YbmB9^@8Q}4Gv-zOm`FV3Bg+G5Y
zP1-ZxWzX-p#fd6*3Ujw^ez^LiDaZHPb>7^Ea?7_*JguG2{#}`S#)nnQ%km;$E%{L%
z{9E)*Z{Bn<r$^5&M@|mh-X}gs=V@LHr{EFC?w&`cH(rHoG+}%>C4BZ#?N`DPkrA)W
z&o1_U#MX4{75B9X=X3wg`()L5GOhG;OLN(ykRHvT?(J(nO!@4;&|p@iszKbnXl0M1
zvrl(Di?|?WvyrRITxN35Bu}*lbB#qiYm07vm6y!;Ree7``sTj*)jAiWVz$^7M(Q>_
zozf<8&o89;N_u93gH@OI>9?h_W%~RP_iw!tzdmc*%7@--UB4&!UiX;xOkYpIOpj-c
z*`nS%d3P!ooetdf@95Q~TdykA8h9u5eTzEstD{w_Cf0J-#E|9hJXEyn-st^jm|T#=
z_+sL#X_I4pbA?ZQI$ZcI)9J_)m3aZvc?uiMjOHHinP5D*YiC^gf;i{DI~IFiQ`x_9
z_E9$bExISB_)1(V5}aH2BP>)hXU+m0Z>DU!e4(@ItqI$kqbF|l)@QqK`zN!+=R>Sg
zG(#%GyU5Tz2d5oo-hHpZwrFu*>eOehLd?Q%axZRbDr@`cDUsMF)6?^$l!f2=`ocYz
z{xdvO|75y0bpNI;E>{)qm-xNj{B6#O8^^-GYyY0uQE9*XWw-dHxcG``zBaGIFF2}q
zy6&zNo?_?!Envbi{tqj2<{3CzH}bYI$UdAWy2HC{nxXY#E4PTe)F5U7E9j_m%-wA}
z7rfYXFY?y;+Tz(eQ!8?FmhBSQz0oM)sI=@df8$C1=Trjf%R(#viY}UdY!}P*>6>S_
zbVqI4CUnpKy%_fqm)NBnl{pRzdFb3`HdJL4{gT~XYwmnuy?aN(rT1HHg)YBUst(q<
zp8kBo*8R%02P>E8n4R*r5}I#*j`2=r{?fbIQmtR-KEIW>tm}St`cr}2wC>Xf7#FKP
zO?X@uvE%Ni+}N&%e=L&=mt@%qY}nC%VwXR!C+{t7=A94C7CH+a&N1@t+i~y4@8h;d
z8H)e${%4pVd;V{0ss3MG@OncWTj3cGzKB!(uy$MjikDT#wl8*h9(-j|wfF87Q>JF`
z+>w%eVdV>Vg)0+Y)$=XfymOnK>ZN7Tz57zOOWmJqeyV83)F*noqjh#9ZtYBL@?7_*
zi{a7Rt@GQbHQhe_QLX2EZb9Cp$kNtH&YHc8^xj<(E8f`Ed*nd^|1Lw7I)xwg;y1Td
z^gGL^?Vk2c|Hmx%PiOUK?%nsF!SeHx2OrD}*x0POG?@E0e`G)WoBz#!hRqfIh!r-M
zjGuy5*wocuRaaMk`ugO#+AH(9*O$C7`Q4lCT<wu7cEb7Zx`lC~60S9#NQ+_iGIcRL
ze)5t1@Xxx-`;Syf{`S2SzUe>1kxTZoGWP84{r=<lWO?T1?GuWMV@vJZJ=eIe((f!;
zx}z(6o{7{wMNiqt$Rl>?(<It!=I&IT@m1w|p)2TUnGbV+*#B$W%m1H&&EP-7$I!U{
z3`h5|gBL8H7k*I$9)_KNE0FiZfi_9ri4*+2UTG}gv-^BRp8x%ShAnoNAKCKxzvXsJ
zE&b0R>~VZ1$NkoaKmIdB{ppdPy`EX{?3zC|JFc=VR_`=Pw);A9LN=Gu#Ou<rkA!l{
zrNenndEA&`ul0D#q6Ul7EB|EGHp;Eor+R7HBh9#q3)vN|Dy6CE0zc<PB*}g%donHg
z%H+^@%YGzRE_X~+?<iTawe4a~ljFJ><p&mX%e1PpxiZXQKWA?Ky|0$&aFV%o{_x3n
zt(SjHb`$Qty8qs+LkmA&QxwRb=6HOX+0@@l(iNUu&va!dEO>3tulv<`#qmeJ68?La
zgjgMdET-z2EqLzPX|1O6eg0=|_PmPc?VWRN|LtEAZPo6Z=kSIy&Qe#|_U-=kq{wsM
zR2$0`p5C@SD#Cd7;Ny6<+tEjvDmJ@mO0fj1t(4x#kUTA2wST9|yszqi)ayX!T&xG}
zM(nZw6AIoA_@9CEKIj0HY|sHH$^8ErL?f%(J4<BKkIWO@e(CF8vtOlGo|N@nd#ReR
zKY6F5qNl}4X1hnbz2IBMz}v^rw$@&~5a=LNxBQVlbJoA`TQ!Nv@>A#TPq}^;JY+ew
zyyX3y;=W~@|6Ts@`CohdpWW;1e=32J;OGAgTmIPmXIOasKZD-u{(l~e-`exrzbO6B
zaC+C{{|u9~FK8^_xBu;b`1~)~`cLn6{AYO5WruFa<1gn0E2KR>*PVULEopNn?|0n3
zyuzNxaye_aug^*E`69Xy)61ZJnFr6;fB5z6QRMw&6Wb@A-q3$ESgFacB6JR`+yMsb
zkowFYmH!!>*Z+&XF8^m@T%#*P<$s1-b#nC=UjJv9UV8jLgG%7H`R((+Sp8>sdbjXD
z!%5K>A_464|1N*{{4d}BpXD+2pIqe$8xm5y{c!f`%G`H0i82?wT2=b|#r#gaa^p}q
z-^B4)^u?3__PGc355LHL)cL1e<z0v9(#c0RvlX%5vrc1HU(dkrp!K|cYd&K|)|uNk
zD~=tD{d3}b)r&d1pG>PUo*I^xmUc^A<;%<1qaut4e_TE`PjuG@{f^wXf4mp_+U!a_
z<t|hH(b!sI1_MLRB!7u@pSlonyv{%F>Xy6G$D>q_ty~cmao|?!C!OiRI$qIdw^*=t
zNFGp^JGSeT26Ow~EB|EUUuoCccb2TT@RoU+bnVZMCzFhp%07-n9ACgPftW=9R$~F5
z-1VRzx#`b4zW(KXJWH+Nu-&T3ZWGP#b(xfF%cL`iIEb_c_GlbrTmIn{hn)To&ytnf
zPxG8rJ-7Y&i70g;H=E-Vwp}gUp;z`~yS(A~LRW^$ds}NC#D;x3<@hL`|7ZQJ`ush2
zS1m{fub1bYT51=_B6{rXfp@PLvTgqG>DHq|kK~0iPU<#!O)z@RePT+p+JA<7bssis
zB*ho%n3q1=?WMuoTz$T+KR+}7KLaOQ&xWYmOIID6bs}_<h(yFwCI>YKBeRn`YR>+B
zcJ`!=<A;CoTi$<^Ypc6lF8XHwN0a_%v-I_oYyZLb2YdtV&c#fd?%1-eynKh9{Lyc@
z^OP?fzq#(|-tK>D6aQ@XewLrV|6I*W3me`$jE!BNU)A$1Z&dov&@$btJ!P}crs(WC
zm&T>VD$Qp+nRC;vyPoGcef-o@E)u}bzA~=H<ZAA<d-Vbt7aequuI#%UDR$~ZgF|mi
zkVXo_2CkdT#mSPE8;jTcvDqzdm)>cTT0Oh5<kQhLIz^l=*#ae{6O3fLMBXYZEBt*t
z?@|}Tqc3mMA3mFsJL~e1Sw?#|`Ayt2>(GfCvs@>|Z1(ULD`i(#|7<G#DxP=A<%Jt^
z>z&Ouy!@0oarw7ZHQUY!7^T-$3NE*;czqI7b3S~x)xJIap8KsD@1>qkT{f7N?g8%;
z5~}-KnWu8cF74mvv?Kcze$<;jj`MtE%e!t?#Iw))w<_OTE1~GL?a!(QJ8l^)KQme3
zeGVvq)t6VyKd>t(Ms<FdNs8w?m7S%zkusH&%${rSJa-{t@|J{@$$h?{6$bA?$5ooX
zsQ+Qu{-2?19dvz#^@sYuyjAl5coP3JJX-Oep#@Xfvp>8x=5f-K9^H$0))ea>Q1PU<
zS$pN48BH7ynk>(jObLYac|{<!T>X-Y=0hhJzLN4=`^Z{avu*W?%8B(^+>w+2nuW=%
zUcJtZpCv`!*&Vg0311NCAeUb-pHDA+%hW%)ZCj_Dn*TBMRFRiasj-kn@u>;b=`793
zn1v@_-0`FLxGukWytV!4uHa)c56+K>obzPz>D|+8tLIsjtd>WwvO(qee+Kjvh*g=)
z_x}w1>+)3R{>hZ6l-bSkC)5Z$mvI0xmqCrfk#Gs?Ze3%xYx}f&kB<qSWmysA@#JI5
zn{`VPns|OF^clu=x-wMW5&C1-c28se@glz$jZu*{(FW-XwU4(Y7*%~>_`<ZVqB`t@
zc-xw@d#Cs0q~1T%U%syM^ghq@!<M0GX=%9&i~Rkj-U)P&vG25re7M)&fAi)IAK9js
zm#VE^p3}yC<4M`kCn^sePaa_TCwd3E%>`|h`Qm@V`#~qYUI(2~cufAE7VO+i)ReTU
z@W=9lhS}y;i+*f(`}|J#;r3FiDb`NME*VWcS3EP?=9{eb*C_$)_C%H!qv}LMzPuOt
zq3+||@%B&j;>zF{&jRIKFCpbj>Ec$)bKKMNJP#(ZF))-)31C-e@2U}ITUoi{Kf|Hu
z#kNN;xl4;(S$N1@?(K>Ng2$du+*DNbd=4wqbM$NhYEPLz$b7i#!=343pN^Xdy{c*k
z?~(R>azwzLMetnq5~Kq!G)CF**`v|0KpccJ5MiM`-_H1w&CSKVrjdJQ#)(&$RPPL~
zGIV3SrnH=ANrAuD3)D4OR~XO_+C)22(-c~7;6I%c)anN96+=C<lPsg6`D^p#7V|cH
zcCTDCDdTb`_>9Mw2PfLwCr6h3)4%ZU-qnQNlU#Or%(86VvoGMYh)LF`+#7udCvzMz
zyf>%ju!10=Q$kJE|ET_wRz2-ru5v$ZM|PwTcV$YwW#nPERja%$Zk!2qR4jP@RAHw0
z5v!6(w@;Z$C~uu~>CwZMjhjRxW{TdN*&+BwCv<Atn|Ze-0$9-xaQlybR@)Lg{R@{4
zJ^J?OowtSVJ=NK7w|%;8QkUG~mO3%CNzCGY?;dk|%_H+aOv$vrc|Z5_^4rgT%DLZE
z{p~)p_qI*%zO=Xd?aZF1pZ#75K7J7Yk$X82_oH8#72b_H`ON7j!&EItmbS3qrZpT2
zD;b(N6a>Q{r#j<3H7<L>q6W|kRn%kYFnk58=}^sDllf2ma;dFLgoFO#T^X}dz4zKZ
zx?Q9ha6~fD@nGr8SK3MF2l=4vAO+1p4o57CzR#rn!@b`6^5yrS^Dv=T3RwhiP4S8I
zvC!u>x2;rPzg&dzP9W$^T-5!t>t@B?nbmWR`*Cf-U1yPEk9n^1PxZxUp1-*faw@um
ztSk78Ts%8Ap{FvUZG1&rQT>IXV*la#50hUSMt0h4i}dr%;n(xH$GKa6_NiG;d$+fq
zmt@y_eek+)#imF98FGql#m3#fZ)~@?SfX=LL__>$MZr_WToc|LW^D^?Vz@OQZ9k{+
zqWijsqPO>%P6Q23CU3lRY6+V{?R*ucQ=D&iR9#@Lv@x&RC!1~Bcj?i?QtQ=6*q%if
zZ;O0dxT)gUk2yLEgcwiUn=4(gzVsolchH8uYu^L<^%uXADw!mf8Ku9)#?62`;goWS
zR%}Q5EzYNXCJGl#rDs<x_m}w5pwc1hGHqMN0l|5pYa4^#I4JMM+yUHR{LaR9P1bgC
z^Y1H@vrA2OWe7MId{*eY_Tt>xJ;&OM*%QR`*e-sqxvw+*pY+}-uZ51wE_q+Na_JL}
z>qfVCt=QHjye;F{kNFyRR^+VID%>-5BVTuIQR{<`$2M!Rr|3+)v4LkzXuH^7XC{s}
zj-u*lt85uAT-43i*;1kV{+-S5*1MDU>^rLCwd~u^`B@Wo-+q?6yI<v6YjLvczU=nx
z@iN(JC9dT??#VktJGnf5+c~I4FyGJovJ!2<Gwi6&e*C*$V23N?O*o?G@714lzPSI5
zX#IbN#km?7Yqul6{VKiMe#BP)t<~9YOZR*2yZvoTW6d7#%sG{T%VWNuckC&iz;_6C
zJ|R)`<F_UirTYacrg`5!8~#^5pid%*H|!aU%Wu`)4^)b@{ytB>yf>r%kTmG1=xaOw
zGc@16|IZfY8&pyEKZ?8J|NPCK|HF3ge}>1PBjZ3h3{`MY8g(_+#(W`YLVEix$i6cB
z?fUybbJ8_;z?0Ge?1A9(SW#Agg`^*vrFBPjcl>Lma<`J6A5GuEtIwaOG(<YuZs(6;
zc&V|j9&K%w{X?|HTMPJ_x<Gpo(1g*~bTPab9A>Sw5x2P>$NJ&x(IcBc!(f|Fs`Nz8
z?eX$d`Q&Ny3^eD|HK6TO?d}b2zw#Mh?Z27k|CVE`ty^`7r&;Bs<F&?1a*FKSQn?N*
zYn?GNp7j>3jmCKLmDG~WFUxlI9{HXxx3<vs>Z<z8v#HE3W~#duJFV56`iSc_!|yYn
zg?3L33Ey%xe_hU_Yic_u#CR_LQS|E5LpvYET~n8r-ELU9xiYUo@6E@!m97kxb;}>A
z?`;p-dHHLEUP;?WCTHE_-xfzlFJU?;EuYzA*je*;f4OAwmcO6pT|Ojq=j_AoNWFK;
zJBmL2EOJ*qwM^e|&jyv!un8<TY!2Dg<ekntc?W)=pT%0?N7LJv&3feVe6r6zkAOS7
z*7U5;D-bTbW*vD_!txg9?=JVq&`ZDW`MPDZP6prap?3Mx;^|z)mnVbvNjBK5BW?%S
zYkeZl+Af)twaws8>_O8rg|>5d-Hnm73++?WW1eP{{5}7E@1Dn9$0vRE*sgx`y7>3v
zgBzj_%yZ1&{Bx3$Nw$>wjM$|fhqd3OrXIL`Vga9?W!ub$tZj$B{}rwAuIF3w-Rj5%
z9SxNoS}HrG=gDkn_}KgAvE^q@D{-m5jr=WJcCPu#`Rr=^+kF9>?w843(ODY7$ux5t
zBil`{e;>c;J=i?mcG>Jly!N3xvMcPai#+7+c=u-6w)6l8RhJb@8&n;&=j6paR#uz+
zNY*%PM~2SxiE|VuavxO5HezC|m^p<rc<Rpy8-7loKO=>C{)NYvm4EcseVcyCC;h^j
zl<jxxRSre$IeBGQTaiS9`{&}*ljoc`y4&k~Y`$Nu-1)HRo*VZn<y>}4KmR;4%+7G)
zq*s<Q>2r#MJXhT~y2^Q(XR*{hpV^m`uk;nZ;pBS4e3IiyigE(eQ_=R~M|ZWZ{d;zD
zdeE%ua8C1^CA(){l~}Zcb#d=>>sUYIJE7g@1z(DpecLV^?{@L-vfsrVMn6|KHZ5dS
z5jwG;Z_SIvI<Gj`mWs|_mK_$gf0k}k=_DQTwr97zD@9};Zu3}m+fRb+7-ty66B+m9
zN4Cnr-kv(^7thl^K2>+ALz&k_!*H$}2ko^5j6buc#WZ*@Tv=E5`Jb0uFX#x+{|tYn
zGh<nczt8^^@Fo8@Yy5wP7q`6_UJ%^@TgM;%WA8(M{vVsZAHH?udRg%;rOh!WtdEjT
ztr0ED%X#>Fg^XNP`jU%#!XN%;5O^cywl%q0*+uPB;#{Auc9~7-MPC`7@CY}bWeET9
z{ZG41<bQ_5i2n><x~}cwdi3RQ*r(%1=4o}^Km2Rjg7)Cvo^6|=S2cgL&Y$vg(!%qS
zFZ<kW3s?SU;N)BRpTQ|@=YNL!HT!=m!47$D2klQa2JKJ17XN3W`yUmn<$pP6J^%X;
zbc9M5r05lr4gS}1w)o$FhDgxd#D@v5=6_Mkp8x&V>HiFqG?*cWN_&+0{}MJm|NC$1
ze}<DH^@p5S)nAyouKxaO{eK>?f?n~e{R^M#_V2$=2hD<Dx=HiLqqn*K?MHs~-ff+8
zYi8fO==2o3@SDq%BpXgG3lX}L!(8@MOCt5frMRr9<L!^82krYU(H%0&VDg+;XVE*_
zIcM&s#Oo|(KNlnCt-T@F`>xZkU$6akOh5Qffj_YzPl?;Mk6U6%H}AiRmvee5jw{si
zp8tXBY{sK6e{EY*lBssdlzaEtj2}hM9tSu0T-VKCsdXgTSy)V9-?KR!O)IQDZj~{x
z?%miOdhK0_Y?b$K4Pn<zJ)!>$Z|&1N;!dT7O;_E<a_{WkKGE4K3JhiQ(L(G$LknuK
zJIL(W^>^Q5(?9<iZqMFhb59{6Pd{Owrbqy<tpuZ$!KdqQrP)s%*17F}PvOqCSc4z0
z4}CXyHNBiuZRQI1Ox2@z=I`g$VRdS9n3ALCEO7Ly=xMvFRd+CK!HC?$A3}dlkDPUL
zE2sYR-`1vQF2<j<n#rtj=7YzAn_iwt8<xv>aQwaXc+a}}e{@R%(6h%;!w19V;1&TP
zH?6BbF#nUkjVUM#$Nv@Cf|@25qe`M4@r!)iFFEWm`_8Z2XN_HjZ%Bx}^4=YtlKI$3
z>F4I-f=LUf%wboTl+{k!`JX|u{siCce}{JE|C@H$f&Ipx#QzMAclrM_uw1VH6e^$m
zvHdT5iTxj8-~S9JLm}fNR8SKZ-&v};C7<inucf<=UA`IVTPSscGw4KXgN4Fl<tqWK
z_8Wg3{@1)q{vYSE{|rx7*&Tn(|BLTM{SUR-{~0E&mJj-<-f6P`ZM~hX=Kf7vzFu8^
zW0UN~`Q~D$CmG$}nSXx{pZmM22RnBCcJI+u`fVdvJNw8o-H&S5rdxU2J-0t{-|o(T
zhSHF-1-$)ut>Hhs&-hyD>f&O)>8dw&T$cNHPcYeb)^P=npgZUFf|7op5YoH&dsBfk
zPxzJ6vqj&XQnz2tRodMheEG_WlGC$2%{+@bw=S4?_>KCH?*fm{_-L}OU|#ZDzQ_KB
zHE1w>R{lS)#c%3B7yi5hU8|M3|EJc<dllV5?IC+6DQ5nipS<$c%S{I^8cqwFf8y_>
zlRH?rzqS7KGOOAAnfJa<ReGms=T~XBJ$*+a?qzMCm7>YDe}>KEg0Qfp!V?WE9jxZw
zZok7Ig&Kb$wf)EBzsO$r&+x(5{6B+gn0$Lp`kL2a&z{NZd2cLSX8U)K(y?mOJ_muN
zJLknLIr@EqO6=nADG%Bt?tD15zI0{nD(%xV)F#RHnBDMCR^Xk#m*vQ|`%@k{6dW%&
zpyA1Y8cQosy$YU^`iByagjKAvwmw^R{b<;%xRsU5?j9^nEi71@o$|rR#GmWIyO{@B
ze5(1Hc6p(melrD;iNe_~pUwWT{Ajq?r;|J%?Y4Y8DJ`0kSXki5Qp92NZ1<_pyJfQv
zZLWxp`tWb#BVDtT@A6B%D<4<iSUgqCd*!i$<IP()8QE$u?LGSClH-cQOR{%Onbupl
zL~)PNv}xKa^~+*3?-@$J`Lx|}i`Kj2)0hQvV(&`Z3;1U3ntSWjv|n?3_svfGeo1WB
zk?um{pQ;-T4#zwT3rpPE_i#h*OZ$fersfv##a$07`&c(w_|^6Mw}M`mZ;ZR~^GvdU
zPI-L#y}3%KbaEEterAhl*WQ_Vyi|98V~wur({D>F?G~m?H}WiA?VGXbR8qHKr=r`$
zr3w!f1Am|KIJ@(h-=o)cJpXR={mYlVamSryz3tv5x0dd9XIZmm&8hlpa&iu$b5`&-
zFmP{AMxXU*uqeB-)%!mKe_VEP*7eh+=?{ME2AQ<w>lv2?J^gdd^?=QSQ}PqrdDgZb
z&s?N(%}(oT$>!?vQl`kL*t}g+P8`dWdzg|qPef3tri)3B?`q7f$>=up|M2@G|DVA*
z4s`jIME#Fd3@^0jf3*MOz3=oRm&d>L>u>FSb6>9f@8_+m55(;JE`C3YKCKs0f2jPy
ze}-RDU+n)#9RAO6G=SZH#jUJK8JSB|mk4FoDNlX(RlD+?&6d6!Ig!bFT?gLwpWJq*
zL3sBWX2st0SNUr)zfG?)eIsUO9Q$fpRol!bXTArnd;PlJ#w^UtI&Ff7qq0)%DhKDj
z!-Spw>}#)i)K&Q-Qgushm!4bsx3!pU+O}!W?&=AZ2K@Z2lC$fiNWz1Lg%>8(91vfz
z?fRG4tbez-)%yND5;w9t%DP56Sud5hS$NKrTMl&*xrcT}{AVDXUi1!o?dg8FzGdD0
zBT`c?h+mxj#$R?v2ea)yaczMbo{yi?8z)tsZErtv>-6bIYmGfG=kZJzxcjomZqdb4
z*CwuJ^_}N;Ak{OEL+@t%mYxU446mVwW+3L=orBEYZA;hQ;TL(mPh$7Rc}Leh+~uKq
zdFiao3pb-S8a@j7*(E=f>(dR^wj#|}(+X}Kxb`ddPH|LbRa#5VdbJ}bMU=jFpYfV1
z&E+V)lhskM$%BjIEn3D{HRqq^2cKU{=Pmxvz?s)GU2LUFR(Mc5zs&4%WhQ^=NoFSw
zp5iNr5a6ja%?<l?IBdfOQ||pjx2>X;UYSjf*4bFuudsttN#ZfzL?xrX2%A;WT5j4e
zUECi?7mLkSoBhpSBxie1$HC6%kQ)bWwkf)ulv84qls>NIXq%2cTNb?QqkmJr{+qmK
zAM<*AC-0eX%v8haXHTp7ydsaVQf7;vClw|vVJMw?^7XA0sr7wZJoHp{yTls(Jh*lD
zw7Z+1-QtTf3v#zL?wi-N4n1VUYWMA4{JLJ?%l<cW!;bxDIC*LPp7WbxRCXKdE;HUT
zC!Kx$!UeqiKb%YU|NM2`{zG;3e}?0r$$Zoel(6AyRMCD^ZL1eRhQ0}!^|}6s-`38w
zz1z3W_L`Nr!gR(>=Iu8O>t$DQ9+><rQ}CASGyAW(4TmQ%UO^vDLK}m+3Ys#>T;uS4
zgWohGU$!T6mgqJ6-!7C<%Dl4k@9o7~Pc;P#9y?sjbHezGzf4?oq)K@BH}l-`6)I)n
zIv(Ql(pK6S{j@CJ8Kfw!)pVO#&yyv9JrRAQq5KDwVWDt+_MX!2+wb`;uWVWEUA@-H
zB46RR_4L*yZQ;LVdd_a~>6Hj>lGwZ~*}?4em8|V`O5I1y0$yI5mp0>H{4LerI{Dl6
zoNJyvm8jWa<M!kA=h_Plg#0*v^^awr4j=oN@zFc!;*7PjIWzfh<=MPk(&yIm{$Wyx
zkok!_%##*RoWA78>A0yT=KHO3`d3EZysIK`+a|wYJMY#@Iwx+Lz5abY$1JqXrM{w}
zWIn2o0?~b3R8`++`Zhjn+vT-+B^k?iRoA|{wq7~HWWwDO-#)FFAvTqFlcv4;J<GrY
ztA6Ppk<E_3I@#~?R$i%;S&uj#?G<xbcf9SLlTUWh5#eto2g=-}`<}=IfX_cd*}#bw
zuA%m<72QGC-ad{Eh%))~a$41-y=#1>R^8#WFAJU7sg-1J=2p%>C3)T^@azh~BnFwO
zA(&k4Dn9lf<QJ;wK3=u=*^Cd4%jT=U`J5Gg$?J37OXr&7)gKP@&zIde@p8P+-&tQO
z_S}D)FAyJ_E*F1O(YtnU@!Z>=Z!a@!zHU?9D#Cd1#i7dwqx5_49lGVd<x(Ec#^}9=
zH)_ka?q<37v_mGL^uPgT2CfUcKDOR%3GXglctT&HTFu*IUEs_|yXG8f*m$VZG5pk%
z<;+3?o|3<M=YCtf=#Tq`%es$u?Af&=L#gxWr^DhKw#DylGHxoI!&Jb@@WgGO>_@em
zHE*qsJ#wFR^~mPzOUA3BPd_^>R(JBVM()kD)7u_TQ)gkwvG2-P+*3N+ry=Ur-P;jy
zC#I+Dit$mpr5r55FJXLqnoj$B**y$bo_%Efw(yZIYvR^Pyry5fX9rrv6l=C|FDaR3
z!^5mnJ)QL+=d>FIyw$z@N3L5fzB||4*F$Yb*Sl)fYqL+ys`yq}WN4OpP%b1!o7I}l
z@pN9FJ^znox=FXb>b!B?yY<fYjS=-Z^HtNPrtsbTEk2_tZQ_P_hV7txj<3YaIL$Jf
zyDBE)#Dv(4;OrosBDRccrma263T!IA*OlM>{wTM1&5vcLT_eT4H*Vka@4}`IqxhMM
z6;J01PBCmRNS?d=$${`YYtESURM&I-XtKX^e))~NH}vM4&E)O5b(`biw#f-8Vcx0}
zK1ylmoGGw+@@$R&!ir<>eP&&He`3ch&xEOY^P>+RNu1y@J21y3`I)53LUjw3h6M~&
ztfDe(Y1=#3Dfd~PVpei{dNo?6;Rusk^@H>aAybg=2xE-<cm3_H(zEk#sc--MsAA9S
z@|!BvjnWf$8=P}|lRbTQ<esZrtaBCYZ+^XfGV0jpH%}IBz4@O(URYgqVp+nGC#AEP
z+~jthJaal<JNmfH<Q6rPiKn#9ELa;<c)lMzzHptNw7!tzx|mllAO7Wujd9s%{>M+{
z!0|Bo7c=i1aFcjGQ6%|?D?{?DeO4Q`eq4O&p326y<9@r_{da82-f{KLjzaAg^{L^L
zuIqScKJjC-OL+SBU(Y<%kK*5+-tV}6>WX3$|Avz*Is)VF-Ou9R{HL*}uj2QS4PQk!
zCZ|5~*5$KR_)+h?bE}}l(%*g?m1p<fymzU7QR2*#Nk{r;Y*b$xyy-%XbM}%ftCU}E
zvuoKFHR|1Z9XE4c;1hSo)7$|?rzKRro>cEMU`+Py4!ZVE_se{NJF!P?=k=!+7j2ua
zn|Hocb83pthYc#4?X5xL&yt)I%TCtTuFm+Uc2T#d{MKo+`L)kf*H0CkoU`q=N@=Aa
zH)|57#M4f$1rxOIX3jI*@ky<XTiW}_qllD!%@Kc}ys$jdbxqCqq>jPj%(UBEjG0xp
zO@Ab9eOr5VF0)(D&D-bmI{$7rW)s?z_vXp1Y3aHWs+}iwjy#!jfvxs>xB7+)f1)eP
z3)Lo;{hAeVLvOK(`<qKAv-1Sz7^@vPlbXPJ=)Hxy((2QXqP_34W{GY4b!Yl=ziYa=
zOLtseH!m{kn)i;L#5m<=hM(e3>wcek$#I&^T#qgFLayt*SN~^7e(7&AY0tml*F_T7
z+`2TjH-7VzP_baQWb$NpJ7DT7e`MCyKjxEO{0a$jf0`%ox=3UC>3Noq@Biy4&&@a?
z*W_u~baMe$L3Y`#;8(Y%b^hI4y8LBT>X}_FQgfy!{9Pz!spybbbjnN8^M+wt(BXHX
zCR5+6D_wGR-5&RfUp6b$uIjvtlE|I>=AzH1Ep85z>OMZJ*HPIWo|Sv^>B<{dOX`KP
z?%%S@>tE{nck%LV^NXKm7u9^6d)wcvoo8Rl4CVegPt3$6-!J%aJh<z{-5WP<E&Uf9
zytzI6Ht$O=rSxZ)++8a!I&do}7GC_6!5kcVHGiF*LPpuP=|-;0ZpCd~`$(VZQTgUs
z0lgO<nMT~+wQ)vy-!>aln;Tb6PA;8Py!77elv!>%=cV0cPH<YPtU9%F$E4`AM@7eF
z?jCQ|*E8+*4gV*wp3Aj1w=Cc0#rjiwHi;%q&)@iTXYJqOogvS=?tGZKZL7eQ^`^VI
zy{&uQ9_F11`<|BDemdfi!Hor?9*<et63*`EUCh*A<@NjzC+JR{!|~s^w*F_h=pD;i
z{Er26r_RImzgeUHGrU*|8p1=m{)?#TH9YEf?w2{wyT0x5jvdo161syg-}6*SSk<Mk
zs4}U7fv-4LwfLVAX!phTzpW+r|LV3i@T2!p&|0gjojyljUSq$-?sDPN{|xE3xNonY
z*gu`~e%piMe=C1T+UxtdCAS~3N<Frs<i+y|=l3oSH}FuJc-?xUs`kb^xjCygDkndw
zS=+!>kG8H6qh}LRW!{~uw?{jFRaUS&&&$QPUu{1vlfO;liCgaBmCA-E52*av_t=W?
zH4H_J{^*^V)%SmFKk#eb+~UN_N40$3;B(r4dnxXe5IC&3$%yl1tg8s)@p~1`5C8sW
z_||@_#(m+*zY8;T*6n|kDe+lR`okW3`PcCin?IL6Nchjt(){p0!|i>y|1)sPwSVj1
z`geQ%w<Yzj_smx=Gk^Ry{&e5mkMpuOtl4R*xpt2?Z|k9B+oqTO+&Y1Yb0(*evQXiq
z)<}jY9Z%I;MHtWCdKJ&R=FdmD{R{ULyIhb+zZ#TrN$vMVx4x&zJr9^Vm?o?;Y?bJ_
z_s2Y&yW9Mu*=#Mpk2aG|ub)2Oa7V>QW3QBeHRcQw44%p>&mFzrnYMlV_4kjq_f^|k
zvY4&l4Bx$r;a#uv1jn>4#m3!dg!DL>R^O@U4w4hAd?Yq8>ta@6=BCc1G}p9U9yN#M
z9vm>TI<+c#@%l4|Co#t5raydoY=x<$jpt&??`wLRBLYSGcHDX|Fd6AgA|dxj{OuoW
zXQy|3G5nUjGe7A+L+6ruol8Gw-+upjzLg(8b2&polK0&Dpbt-vyk75{S<CctdQ{(U
zZnwsXxo4`UXP<g_n$yiPCine3Q=RxDf^qJDmrOIheSV(K)d{y`gqV%Dzn}8=?yD8W
zTizU&ZIJo9Zs~_x=g$ki{w00f#Fw$HHdL)wDSxj>#=9_!a|{{{np}$|0=uQsJ8D>$
zR4%)I)GF9hkNIrzTJBB>o`>ZpmCY_rQ!H+X?2uG9dGk*tbNf7r3-1)KZpkcN{d|Mx
zn#DWAQZtuyrZO4aZVY%=P~1~IN9x9&k2=@x>9qSrSKRjJ7ZEp)wCKtVb92?b=<(@M
z?DA>mfypxL421jq>!!!4T=}{-i<{TkYs=ORyS-B)zx-4$J0s{7v0*NIq{lJqkTTFk
z;IC`7e@orFB>8U3iBjpwC6U+erb+a=nN3&ejPBd#7`*vRcmVf&LYXKm=GVWynQM<f
zyqR`6<%*u1u;`~-R!5~yOxJH~KdajDTbZX*{BMHA&w^{Ze_U5a$C_AmY?-F*>sxYr
zcZX8O!OW!2hZ6%f3z(mpD0(_&N9`$*E{2_$edNe*zuxt){o{P;Kf|WdXzBk9>R$Uk
z+np?!^ybXA8Rsq)&XL>Kwwnv*5EeP(zM<9D(zSMMZP)De%%*vE-0_QZ&y@N6>df)m
zHicn`;*jfQaz5y0!Q<U47xhWX7lLmUe0gx<e+K)+FpWhG#$V0~`(4~~e?#=oxID(w
zo8N|>yK%kHS~+I!iXEXR4@jCWbVa&^6~bmbc`Ga6#rel;gC3@2=&Y~1sC0}mX=P&0
z5uORgjjy!r;zjOf{Mxs-bZxYImhPG@Pdw^w@48}h`Mksgj}TFxDSSs68Tn5g(9HEU
zI(9#J_s6Y}lhPI_&NLU?DRu0I!HFj+!k3oBvmbf(%lmG8(7qkJyi0}8K3VOQFmY+;
z1b3-*p?9{Qk&t0<lw@JHv+oc%yWniSQ0BT1_x^T8w_b7F;P&ar?px2(Ik!$V3jUkO
z*;gLc_)+%D%cX}Cmq+>5*XHY9h}7Sh|J3co(n}%kdJ?B4{imdQs%J`PJ^v=M|K>gS
zZ_ieLTW@~uclnHYX>W3mot+nUcTeuk?e=Eof3C*-@Z)%}<+t48+SKy==k?1DKQ)<D
zc}`_^K}pKbCtT0D4BW)Co&>Pf?S8bnJ7a5g@gn~xH($)Z6|R%-qSrXB{w}ke$7DkW
zNl#{-a;8;sNABtDXph*t-75SS>$HXWiMsc1u|2E2COcdCxJBj_Gp~mQAv;fXPmdGb
zxO@AR2bJp%WmzR<PMWOuO;BSB8_!ME{|q%Z)6^~GexBd{VRcMJcjUgkv))-}eznkB
zygf4HXn|7G{nKSKQ?+$+>VlSTYq&jy(LwZ!ZFSJj?U&AN&X>QHXL|d!#o4X5b6tC4
z9v5&l9uO2^=qp%PaEJMy@Xo~-mtIxBv^YZb;`3`cqI%sX8;-0vntF;+c%n{?=7idJ
z71G;uYxHxozP<gnd#CHZ<%KJq)&+BX)>(MDm1SAlgq|l)`aC37Wj~1KfAhMVQ$K&{
z)>^w*qnnb8<&(Ef&`9ZNVfirev)boRe3dy38JSjRkA7QRo>;y7Z`Ui1MLRjvg#Nt>
zR`5N-z|wH!_msTAW3ro%9S!dHZPQJA9uhYB{EqEycdty`qLZtvDU)tFb@Tbe%X?43
z7e#1yU$#kK{c78<Xy=C~9?uWk^gDN!cOBE3EalHUX9T85PBqKni!QjM{9JZv^2>eF
zn?V`Zrc*ut&05<nKg>5+FSZNwPT<-8E_`C+$;ZnWEcg09YMY&ypIx%(l7;GJrK_>}
z>%;Dqw>caQ6FJP8ddMuisAr0F-<xhZ<&UhNeZFlo+oZd7-NxlN@5C-Wc0Igu?Va8k
zk{!o2f}DlC1%mUUwkUqc-MV(~6tSpjOEac@3%KExIFUK#pn#(2jfGln&wnn~xNrHq
z^~m&p!cD&ev!`CkU;A*{JMP=v9yN<)K076AoQdS_Q|b{|vzYs`$|Od)-bbvvt|(l-
zbj?M0-?HEL9xl<!eRoaydt1RV-vj9!41vcCr`gmO{3^PCd{N%kZkKJ>-rc#|_|#Ql
z!X}N|(<gBBUHr7Vc$yFIZQh3#f=SuBZoiJb(#%^DJ)>q>?RKG`mzJrx#V-B!_~{)p
z#(93p{Rg9RqD;?C+kE$@xRi~R@y60SioGeJiJu<VspiZ{Zanagar)XH%VXPac~|Ee
zamRXD@3lNrbhpXwd|~m^6={MSgoJw5h!+Iho_ePzwEI7UeB_NE3%8V++3(ujbk5`6
z57pbA2L0LYZ1?9GK3f)Dpe$5S)_ZH#_SUysGuJ)O-o3l>ozTUa6I^M=xyHWI8mWnM
z&lOK_WGK*b`|zti$FrVqVQs$5rzPLTChS^Md}`IIHOKR3Sa=)^Em)$)p|I@%*Xu{p
zC%1O@D&6-w`$aB$=d`2=KNCZa+&(1yc{=y^0-oXr+oyi^d~o~s+wg-?Y71A+IQ#VM
zlwhwDH~AtR?|u(qa%5>R;8YM|^O;bQckXt?ziXcAzl*(1CY_3?`<N0E)RN5T(8gfE
zT=%lbFTS*w-_w`fdDEq&o%0?^TTGL9GC%Kc_o3#kAq56jWzW^s8caa*`r7k9sQ;OK
zp11yn*7g4kuDT_n=YI(Q^L*a6|BYz&e}+ZV8mzc9plec)Y3=!Yua)-y@JPQ@GFR`|
z^Ecln+&QUx_xHhn8=nR&(9xe$>GEXal|a;s3BfDM@L%>gs)XS~vH5=nrHca?bo~on
zU7s~Ot04ZSV`gb$neN<#oyLpPG@kNEERvhl*i*K)i$Qxn{@ds>nDvht-aNfNW78eI
zCBCcMr@y&XdgN8oXXP1*i#w;+&&}mfnD|NjT}WU3TceYYt!1MgZk?I?RzGddw9BPV
zDZP)T3Wo7(pXxZiH&{XFftada=w9Z~k9;#1-HE;(cV6jE%;G%)t}K&I8aOT7rlhIk
z_Q8YM;^d1Z9ruq$3B~EIyz;=vbiqCrq2M=9EQQ78HTs|AY_yOJ@QW;Bd{$h$>h_`a
zOK(QSp0~Z<u5d9gDpxzOGcjXQ=x1TEH7P7-DijSjl-~XHB39aRPh?^JH`_GmwQ!rR
zE{0wU*Ws>tM$36KkC<c_2Xpy^AB#O_oqP7=tc`a5_A_0NE=8pM>=PEWYR^48HAeH!
zffXlNLT$y5Zkx6C>6^5SKl|U>Z-{)`d)S&gWbV|1Ph<UOaVQpU&XnHOP%<UV=AXu;
zghtiR%V*bYcG`G5%G;)OQL#+>X;<B?F}b?EJGIZBF_xSEsM^>6$o44LRh~-DsjQD;
z7g=_NPT6O+?`}(CNR!07(~RGx8KkG4{&DP^$mZWRh4<?-4{v*SETiQ1%*UP~a~ICj
zxXpD#<AK0Y+4hg&fssX7!O<1dq`6yrbM@YS&Q@R%HWEs4Q+ce)wTbbh;3<DD4d(7$
zxl*srdtAJ0<5tqGbKWvmKd|f3vxi<Y?%uPQUKVjuTc#<6<KEW!D{j8@`F#6^<2vtU
z_fKb=Eo57|EUVlu`EVh3YR!q+){7zqH&xygc)*msW%oy&Yu|qT{S)@_eEM>QwyTU<
z-^(3jFD@?P(7EVhU|!kedQc&>x?eEM`OtYAr%Sp~x_-K5fjT}X)?D}GpOJh=g3UcL
z)Vrkg=Zqo;%P-qMoZb9-TA7sJ(&Qzt%i>(ml+Baf-T8QOw%XGpECMI~T5ts`7*6cC
zvhic>o9z?-Gh{l}vhI<5cHU)waan<b&iee{Q{}6ZHqUu0{b70SX=?S7YRs>F{2}ag
z;f&S#TU-7!ym@bWti68YzVkYMzx^l9bII*#ypk^JXKQ`<`>dGzw~ik@9J055Yn*R-
z?rJ67^DH)*8}yX5nru&b2ret`y0Q7k#AWv?lAU+7hh1EHZT-B1YMc6=MowKeNp%Xx
z;XGF7od?euo-4>s`g~+_bj2oF%iPDgHZ}n<cT*l|E{&8F+3u=*y0dIv#9h~(0vYD^
zT5H#9YfWeVaa`i@>)L{k-l9+HB=*jJ^GSD)=CL1+8mhgs6D?9L^7kCtqHhy#J8yG&
zZT9lJ>lUueoc3+o%EG1hImDi+&AiF^iFwCu&D2{vmDJCj<1OhdedOyOb#1|hD<-SG
zqq(<ibDi%$sXXVP$kJ}k3#C(flDDRxe_VZfuCe=$%ee`C-nYH2XZKsoWZi!2iAQ1#
z)9!z16FX%WXqC+rox;q=8}%}A^V}`fTla0;`#VE7eZ{H#B^fELXExP#mI-WPGF!}}
z;2`L5&~Cd(r;51Pu1Q%@>o#Vu+`Grh_w^FN=&jp6NiGO0><~#&=QV0FoWAa`=SQx&
z(g9cXOZQ3#U4C<MN%dRZ=q%Qtb88x(JPqfaaAfX{TL#?07yksWig~dsZsn?ogBhD&
z3Ezl2(7Wf>{&^pcwz0hbc~#j$W~TYmP!9#!R<u=eFEGyg3t)G26+yZD0(1ceH8H!q
z-15Jj{QY0^)zAIry}1*7RP&*m(4(4NpZ9E)=6}n-<%L}Qx7r0)*6qJ6^0TbHj-C7L
z@ptpTCma6R|GH9g(q-TF$a>k#a$co_)z#lBrHq(atGQEEQUvG7J4el$-uC9J|J!;y
z&+EU#{bTKFd)RIqpWU>Ro%i>%Cr=72UQghu?hSnM(Rb+<wu&%)0qM;D43{LQCH|dp
zsej6c)syyXJTA(6<r{v{PUYrnyKF}mam&k3t|V-~oOkr<`DwF_Wi~SGi#dKKKtPP8
zU3y>Oyyky`yY1h`zm+$txBl(?+d1#y_A|frZ*IK&?#*-A^77-Na<d<Hl-w@c66+o`
z?QHJZwOcp)DMv>Xuw5~1O>*F3-kC1(uu;c@-M;eC-?-0*_vc<pzPM~^skL>n>AY2X
zx;Ini3Qn%*R{WPBAtDjUtZgWro%H&saP+I`f@@pym*0xJ{qno<>?T!V-={e@<qk>O
z*Nb_UDnCCohxf=n{;p@&UgmAB^{PJIzAd@#p2t)cp`RPIRvlA5P;`8X$~%QghTY<F
z;@fs!m3wpd?h@e`*K*rQQ$8)5XFD&Z$7?!EWnjS?kvEd;x;vQW&3$yb`>Y$s@=N>9
zrx&h>&D`Mst>N9LLusdTm^)4#xHEZ&xwO~AbGGx3N?YHx`uB-rP5P&jm0u$iw_ah{
z#POKRD@G&m$%*n62ksfk&!3X_O7X+pIr2%jRi3}8YCX14E}~fFUfF|+-;2-J@a@r8
zpL2cdhu*pS=Gx6Pefss@jBmZkqEjxl_Hh@P&A6Vl+WZs)&(k@Khk4IV;P|><blb%8
z>bzMw)AMtt@vN3vwN`W2jtaBh8w~5td~&cnsC{k8hpT6w9$WZGb#IQR*g`3eX~9aa
zv#rxoog99a8_P9Ysx!>$wUHP0Ewuf%er5c5>zf-V)vJ1SXZBoNA$V*t>x}0LllWP}
zj!v7++k0(sp|D5XzXvg15<P5!?qcG7vy+3*RjR*W(1Q+1Fv>hj-9B~g<37(r!crbj
zMQ6(}9S~xxe(?Chb@t>(zfZ?=X8hW>Jo{Vsw+~m(tyb)NvC8wQ4sX*!r+2jvp68$Z
z%z8p)zQelM8t%lu?fFYiSJ{R%xcVUo3*{E68KmWLR3x_B@izh3yPfwLyEFr97L
z_g~>RpIm;_^eIK0@mrL~JINc3|2B$gMouhe-ol!ud$jtzP}X#*YyEOFa~Uo_z4mOw
zv`F=XbCsK%e#Glc+~)CA*3C!z+)X1hQ&}sHrB}A<zxnyqQtz$O=2=H=7OD11`7umb
z^`GH%`nhKZnH%SA`SPB7OBH{+?z(qR`u;O`R=i7{bz`OQ`KOz_B6dwWcxIANfyA_P
zj?Wr2Z&ds`_xmXK;*}f!zP<CU@YwW&@2+{c%%0_8_GjXJ%@4ObE&CgHyj{QM$L^4P
z?jLQr*8abB|4m<hR^^kg`bnNw5eze(_j9!c?$8T;pu(uAeIfEktxl=fj`o0kV#^}c
zy?I|LdZy@{yU8WH>D=>dV-4L2Y*%ml{LuFO&H8u2yti%(Q+4M)X}n(YFZskX=T8q~
zOfDPTV*2-?cL^&O;{}Jb?21{BEFRBUV5E{48@dsGt+r?2L22iF5r31(yA;BvIV_yh
z_`UA}n|~aGTm#a~S-AZJ|DWpfr2aE(2wnfLD+;u)5~V+adOIR)Ut96F`cDC0=l^Dn
zsDE*L*9-0Wn?Yx-t^pm)diXzs+uiGkJ6Bmj=L#g>{L!etRcw2^|30%tkqX{_yAmst
zb=K|Ri7hzsxL9kYc7xy3yBi~_(z<Jx#qB!2^7!9rdFnf(6LUMgPrZ2~7j#5~S6M(*
z<U_;8!+8wL_E~NCcW%f2NvD2khg^Po<?Y;Q#@|k79GX^fpvawHUMR=j;&IzS^FE!o
z|1Lg%S+yoUtt0mQzB~F;Gs=@5Zo04ar}y{f-|wgVd*2-LpWz|PEMKWuz1lFdCSAE&
zse_ZQtajyD)fE-9Q)q{v`>BrO_a0B&9vt!E__y`n{xkeapZa(GQoY&#R+mrRe*WjL
z-uthA6@IV!e1K8Cd(ES3dL`dB@4KB{E;{$<{V6sxo=i<P<au{G&uG=31ygM{gevw-
z`=_yO=T)H#QL#&eW4tq2U$cM;sDCM0%;GGSL7z^Eys=Q%-YqB3e?Lo3>H4hfl?s>R
zBev}_u-$JoBVlVv#gY>TjNG?wk`b5@+ph8=>PK95ZO}cp{k>m)d*AMLy2Y61vM6)U
z-QQ2{Ijg^adVpg|&CKNH9Za_N$7jWUn`6qE`+iN%eg9l9&Af-lXEU)HZ3tD}=ljZ%
zxy;e`^;u8-p0#V<<}JNqa@Xrzb^11;s4bZ~yVa+k>b>IfPC|^wtSS15y}tIW*AFV<
z-7at0-ThLIJC-X~%&pI0t<s4ND<`B(Si(`2@b`UQ^2QHFQ8&(VScR^cbob^R^KWTW
zwr!l4Z*+<=;LMq`O*?fQBn~z2E?}Ab<52O67vHAca=mr3aOKwCFTs`3Z#}kWHmG=R
znY3G8D<+r6qDD6>l8Ch9m(P9X)`2St`+MboCzdMp=SAfHR@j>Hqwr+RhP)&FQyx!}
z=QgR+vATWdR*JRVkDO`RD;<LtSuP7ZGEu`u??ACk%0?}3hLS1JBNE{0{GZ%^h6&HR
z?cZq2|C<<f-7)4rL;L<GmXFT=<~shLVM*B53*e*Gd-kJVbA!I<R^;pBmFj(4+%G-e
zGOhHoez$AMTd5QKau*yZ<q2qVJa_FJ$ANPX<M^4+iuJC@<gJyTSorXCuBaYMdO^mu
z(oC*&i6g5V?%wFLnm0N4+L|r>8nGsCRd#CfZrw6n$Ux$BPH*J4o)x-1Os6<cO0F+`
zG*{~U38T3DzKm&wCW1DgdmU0IUJ&gwZgSqq<+Smf$OC4%=Z9|{Tk-u@>!XNU_dUPy
ztKE`rpJx2cyKQc{M{>~a(^D**xA5LKE9-cC!Sr#V*;*Z|tXIqt|1Nf2%)7fN^|!#*
zTbF)1to(ickX%FgiJj{z-g{nLI_qZ5@7<@XcUNb3=)QeA;qbF93C1FB$4{$;)Jq1f
zp2osGZP%~4?xEZEWL$`TRe0mpDsAy8TlW|}W>%SyQsg1QwPX&fT7%&m6W(fHF{_?{
zmz%Q$?G~wS&ED?ObT_8+)25#;lXi<11f&;QN*uhg>2j%tO=#hYJEluE#AHsp_Q_K+
zCErSYYNy}?2RGsRnu*(Go|`7g3%r~zwea%ddCqp<dSebMbh*d8bD6U4c;VJftB&;c
zPyDn^W%IQ!um3ZEPA!Y6oPSHK?c4PyiO-zOQg_PKul3{OKYO{kftTy_^)ENK>gu-6
zc9&b2_vq0nPfo7Q>RJ+w6M9eCS!%qqzP2>|Rn^sL6Q6P~o4aJXs^Ye7lODM-OXf~o
zZFX@g>&AviM@wY|iSKdzU7$|fy~=YFQ)fQcF8UY~b4N2+diU||$X&P}EXL>a6aMAR
zuGd|2t3_(+o$JsJ+@YIyg--NNK6j#>K{$H4oxufNJ>@1}FSGLPeQzWtE(v6w#*}o5
zL$GGKk?__cbHN>H9yP&>{nLv}WuGN(zZLP*kGtKXcX3RbYw;l?Hol6WV+}@^5A4bX
zb=<_trdj!IPkj<|JX7e%$CFzp7d`Y)ocOCiWSK*<vf#?3c?#1$*}qla*mRHQbK03_
zZyq#6#?}`texDOoJa=)O$oqBw)Vdx$ca61q*Y`P~+PY<)cvr;6T%8*l2P37QIDh5~
z-NeRW>hJY&?&6BN^P$()ztwe_mD+muP{-Ubv7I^#yC=CFI?PbdcPZjQ4}&Lv+k52?
zYOM=rD*O(c|99@Q9m$YBo1gKC-i;HidLFGj{^8TP&)&0tN4*b{TKf9$s!!RrK@SD<
zDik049xRj$5quZq&}%#=tmU7{<!i6qn>f}z`*(3~wi(;Cl<G1;llgm`W;zwjF}pu?
z``@c-o8JG4uPDu2*!JD)(wD2h-Of4(^z4$~d{QLnN#(@1XEx_ZD$9A=8%!)~aQn}|
zuL$Y2r7pJHy22*tXr=55Xs7K1r=w2JZO+4*hijjSR5ZKK4!-(i+y15tcB@lUH%UtD
z-7`7z+~>W!4Fe}CoopzZ6snrEUytwUvdtCKXZe(`PqtmRTv$guEM-dN6!9QSd!31F
z1y<_Q!mHl}$FedMe*O_1czxZv^`_bD->h8vTO#7i$!qmLzD@HC>^{x$>J#(!^go;B
z4S8IHW5wS4Tzs>~-uBP*>(_U^-0xm6e|M|i(aXj;t_N-{5N=}Gto1}QrW|xF^1Quj
zOU3)PxLtaytC#-o%s!s!;krz%pK~pFHttlncr1I~rubU8edT`!Rem>6>)=1bzuqki
znBUF=EoT=4E#aNH|EF00wu;058lvR?@umG|coOwOV*y|Ns1kC*Wzz4XVz=t{nCx7u
zcY-tT(%lu#B5svZ8dLY>KH0o5eyWEg%LF60y19>E>pJQ@$u$nz+VxWRiIAU?lEpje
z+}#^IB_6q-YGBj~na*Y4!FnDwTI_B<=KsZ*QUAko_J4+n+4kNaFJ;9k_nnCJm+gHL
zc6RxhS3Bo;O%JME&Q~buo!H<|;ICzTq}*OGx4m7jbgsSomGy~jCt`(Gb**~FI>+UC
zp_Yr!x@gwQTili$4yLGvXZ%j@v46q3@IS+YXZinJSDKy|zWt-xZQGUgZ<qA=ylRuw
z%UzgpV`Yxmq);a}jzb&2ojAGZ{gI2&nY(=NSk>Nr{c7FHT-Mcx&Ukh{ecIDx#I(3b
zqWPHdEQWskscN}+|C)7AZ!dp2YwDXKo5I_^0-a&c+#B<l6e>j<KSfvSiPS7fFJoN3
zs>XfuHnH+DvCDT~y4Oq(&uU;;bjo`}$C^|35*?+Bb{8BGl5Sw!`0czz{RM8&v4m&t
z|LJzWZIk$)!9kb*KLfjQ{U=><Ilaxz!8<N5-n?(;u5D8%MLg&*<k)yv`4romO)GYE
z<i_k&e;Rf);={F_`W+@G^HndWU%q9%^X;CMOWf5@O`NbTVB%E|<&Er;5=o5l_`Nln
zpZ+s6V=rg;r`S~dGno8XZr3dn@e5hcG-`f)@mw}#O<hR*kyUHL-=%A@6<9vF9{;e{
z|M3yAf;+tWZ@=vepDJUuqD@`e&)h6hRrk}ph&j(~o=E*->SB2K$A0C#OsV{yt?>fR
z47)b%{_T1z!muQFn%J3|y$}5rQkXAWoIK`}zxGwYkM^M0s8b#_TP{9|uCD%Om^bTF
z$Y;R=LGGG6jMlx^S;<=9w`^u|{>r;QZXNn$Z*=W-fWVpA9d~+@b0kuVj5uEgsW(5$
zT&KS8>R0Wb&#TRh{GY50%r%^4%4BgRVYAE=A;$+@3?}bIwk>=V-K&|qR>bL(virBI
zzhe^lY)<N)YT9VXoXwWxe5|bDc)tCb9}m}U$rsK%ac$bI7Af1eXW|pDOsjm`<0aDB
z)cE9-<aNf#W1;`@rwCuuZ@>II$@=G3?$;d;ras@kW#-kzO<`eSsn#`z51(M#JeBbS
z17q3K{|txrU-sRz?QQK!8{TF9OAbr>?9P3g!eORxyJtlY!`W%}N8-5~I4;NR*?jfu
z>Wt*ysaKC}n^qR+Z`r5vpTVIkjkRf`>!A}B!PD}ZRT_T0PTg|M*E;w5l-JoD^Oc^x
zvYwpvVRi1$@UsRDZ`fQ8OfcJKs#l|*YqQ;4@b2B)v1hCFCp}VXT`<LA+mi*UT8_OQ
zip{l;-1rRKANraK`|_wve3PfLQ^<46mP;OI-o^JMoO0P6qQNgEz;=OwEoPq8Z{M?v
zGG>*3n<8FxIG^QNy^5sDwn@*Q@$BT<xJJj1^T=|BO`?YPYaH6nT{~Qrxovy7eo61&
zr7OC#OS3awf?B61i>aOq$&n23yybT5#^w*pW+&;m?wH6r_s#T;t+$NM%1mUjkS|o8
zoYem?;zBxiSMMHmCLQ0@755|Vy6Rr(F6N(de%qsXtB@ldr?>38Q?tA6fbq!_Y|%At
z8+}dUJ+oCjm7-$~Ofo<7ZPJm{%)SdwQ#{u7otaeA!@qCmOOv(!zk}ayQnAi`uzS)i
z&GPhfpFXU+aX`D1rL*~Z+QY+K>&@Ftc6Xo7?(VR=_$117+3EiKoB=(|iZz=z1S>Up
zKFTbf`)pliRF0L~^!!9-kC$8tCpB50=B;_>AU$`+wB$RJsxPpfg3cf+&pEU0)7CwO
zCoP<kJ!KYcPHu=`ayVZjQziA_O-+1d_CsCy@GEcYF4o<X+Icm_@UEz*&C<pVAsVsg
z_sG2cX_v5*W%3Kr)9V{^>^HpqGBZDaY1@6T9hZdMGY<b0&SAH3FxTj0u=w@P<^rRB
zx1P>}EBF30c>T7SRTB{B)AYdZw5RN0YXSRfN=LPg^d6KotU0=4@;@QgT~~5KqE0^X
zT;rR_a=PG@%<+89i8mP}nLM8MXBST8vu|6MWmO{Ry)rBQ=I2*MvA0~)O}i>xyroR$
zFe--rXP9<=?%5`GX4~wSa?-!ex*y)qUvjs0X;P(1>!!^y5^<KXoszl7A|>W=CQrVv
zAanP7-`DDX)|gjjze1{N?_O&)Tb&U1!Xq>}<lZ?m0glh16KZZB__=5E1arO8^zN8x
zu|fG8Z)NNXdL`b;)2n2B@)=VRLt4Z&&H@hWJqOC#Tvw`m2%D|fo4a(&_d3^o{boHq
zvgHyf5m#sY*>S&PI=jS^57pv!azd{)u1~x8>YDhrz?=8GkMw@Ju-TKR)j*^vF7^id
zGsD~fW&y^tx9-2*_D}j_+}f3~=XSMCT~VLGoo^u8Wth!!HuKY;HM?aW-EA_LH<sQQ
zH!-I6ep8N4$=qna3tMjJPLG?Kw8zk0#+!xBP-b=ko1MdNH|g(_QhJweynz@8kNMBg
zX#ZqhMfSggVf%k+W-mbBzRGw3I{b&Sy!!Z^j3~S9ANfQ6UAwd<|Ib{l<EMYe?(*Jj
zboaS*<FNv(Dy|7XvLAlBz4UO#JP85Y-LWcd*Y0OKEfAX^ldyni$#%ybRaZ~j|J0~D
z|F>z4{g>RkiN_z-`km8_T-0azr`@Au$6e)oEk?^7$qYq7<^ivTv>A4<RZRZ$K!c@!
zaRr~-#kj+V?PT_Cy{dQbrk=vq#))M|by^#_oQpYQ()VxEc9Q4(!T0#hKlk=Omio7n
zj1O))#r8Q_y6AP|XZ>?~`s@;4Y0JA@D1CBe!R{+bb8r6>V%wLgr`EdU6W^S~pnn0O
zcjP%j-Pso=ex8;2aBb0dw`~{Z`%JoWvm)-j+wYXiE(x>Jqf5ekd(Ln8=~HxKxx{0e
z0CvY^Ke8Ww+nje@Dz5Wk_Y2WeCeyZU`?Mm5xhX_&jzHl%t>=Ff=7CN(4hA(NO6>pm
zhJV;Lzg}$dima%Pt2M7X7H($`o^<6zn6Yxfw$mH*Qf;Q`_*Dcj=0UdaINHenXK-2u
z+BW*4{>Lo)hb$lJ|8mWe|Hr-XKf@!~`BwB*Wno=w{_yM9W6N_>AHL_Y`IY-7tXwI&
zx`c7gawpNgqNfZBc@w!lUfZJh;rij%voEKzbw2FOJ7hdV=-S;mT049DE*LjFSZUj#
zyf%FIB~#0FrY|NP@}2y8SMC>~naa0S0%!Xh^v_mUKjBFeTg9<rx492b?{>d5C*rv9
z@{adkxt9es%y<&Lwa@L~&(26i*%K1%5*7^oVVCV>GH%K2+Iz0`;jyjWZhQJqZ`rO^
zaqM353C2ya49{71^?cGgvP=AMN8RCPFXKe|e>=-3-ObOlyF4fP^yBB}p1z#F$2MEG
z#<s9{$&dT~Tl2S^&Cj%(y!?Pepu{Az9b7XlT#ueHOh`z&$?v0e<D*^k>eo`eS1ue~
zbu@eR%fN`U`Prt6DpMr8x!WdKh8}s4*IxPXheb?7j(N);ws~pq`F|AFtPJ8bPGz{M
z{PtFRpTv6~zU4)~x|T0^v7djBccSXM=@0MopJyo-y1iL->h78oPm4b_894CRhEDmu
zTKtylmwV>huT45+wtZ`bqUB^E4>P}Iq0$>$e!DSPsF?f=QxcAn6Wz9Z)8+NL?{!nQ
z7p}Z_qIIT(x6E`QufE-$2ecj}Ja{5!CB!I?o)qOjG*#IDYxU*-&%k=&Kf_1Z@pxz{
zmJ((ATXb~3oOM2GRwgzfD(d*EWhWAP+`4C5ClxGioaFf@d&Ro?!}mYQd`$n_n*5*P
zl6KS!4Tg2~$KpRRZ~M=%VcqQi3`;j$cMSRJt9LnaL$>yni3`%*|K3?I%;wIw#7N*k
zTR;)VO9#n1^-FqN^*5bP&t<vfyw~sb&o?QI8^5Qwh~56wbIeWRttBgiW!3uDud7#A
zpDx|KWlwFmd$-rV-7{uL87&I9yd-Ol%=UT5(*k%G<o(>Vi_n%VhTtoEtXF#Huid(E
zOXa(--L`IbRi{q$I;2~)?qI}9wYwi1?z->e*rQ#X`{?y~K}VDNjCo)Ej!pfxcX9M#
zna(Xw1HT{HlovSd(?xFvzuN>YOMMx~w`0Rcjonj|C*9M&J^RJ-T(_s^UiP$S-A-|p
zlq=Tz5UuEWi~DKHhtRb%uay4vJM{Ri+2p%F!>)5Yd_2o$>tUk}4>y`#c{!ngC873d
zQVGVfNSNmzY0v*?H?eeO?X+m?47EwJugc@kCoAyw@3v9cc7IBmk-_oI6B>+!%{jmS
z!?u-`%d;<>u4O%YZSlh&B?k*$KYc&f^+2X%h`=hJQw7F-6%W#$tz7sjTx#0-%G6RB
zwRfj3-LvsHarUXV@rl+cX$G$~99~b0nZ~STtd4f#75Yv+2Z>+m&0lTp-f?%&e2}~A
zc9zfn%vog-XFIoZKJ%Vd##c3oF>r!-i{Q-)?VxR!*Q~u)?erlsW7-?%ZQPM}Og2sY
z^hK*+-|}@<*PauyNaWdvcT0BtxRPMjH~;qP6(W_9{*%86X5AI}^KjFF5(WMl={>u3
z)jsKFpWV83<E|@Ts`ol{=&Ks6?E98z<uBb*_R!h&yMykthWqMgFQEGZZBOMD#_8G1
z&a$msklAx_@7=9$pKYytI_V_W*>4TXcY7wqJ!w_Z`^eMYWOhB1dZ&M3jP{@>kd4cK
zB>P@A6|866H|b?kM(De*+}(3m9Q9^UEn`*{U%p@gZx^(IiFL^uRL<bphoeiccg>I4
zRjF#9-lXyN`;Oiy^{Iz9wcUDd#I$?L8_fwt6_f0_GcNpRNbh*_ZEZ{7VWyw!x2M#<
zI^6TfxBXe{?`<1(3_MLYx-t~Me6W_y-r{(+O|JelX4NOBF0|a=n5g)ft5Ky(%yx11
z)MI?01K!jR?@#@$|E>O){Y|^$Pb)9w+<aOYdF)N)y!eyPYX9!nds7(8D#9ouuy*U7
z0L2MQG6a1l8H4UANb;61^0a-eANS!;)bGru?9PXMr{3I|$g*B||GOpq86~Ny{~03Z
zG@moPaP6oFW8Xcoi@j^6eZ2X1p7~TY`LwAIGwvouOgVPKvHyF9@Dt^yCtmm^Pd@mI
zWqZK6TR90Xv&HVlPP@~uarm<n|Fq+$l4ff8-QjCs+zIg(Yf{FoYnA1vQYSv&Gb?<`
zrbR}(H&3g$ncO3BV~Vx7!h^77bC=%A^emW`sig8<C}!7|b&t<X+-@0r<SlEbwHuqK
z#gnV25Xa>&>cY!r?r#tNcXaZxs>#mJ4(F~qs`8(~?7p60X67@`3(u4CY8Rw#dr;&W
zVW+ug_m!x_o|hGN%v`!t;AC-GVxPy`Glgev3hvhCT%sYej-z*W8P_vkF^;^g_7b=6
zxXN7cUb)Isrb{x`cj^X(=7TJSU6cO_S}1M4{Akma{59{^Bvpic)7M-!HD<L}%4fl;
zGw+Jt-1bg~^Tf#$Y_`jL^;Gv<EzL|g-oD_&-*xM`*x3qXe4cA=;XR_rlCO{xQ~T|<
z>hvQVd238PLrread?UnOc6qB{an5S(O`4N(y8<-bGWjlVw9B8p;EF$cX5r5Z>*wjH
zU0QreW#j$d+ZxSVe{Ou1$K)RK?nSMGX_72g$mX40wZ)-3=jHCso9E)*oq6hQ#Kq(X
zPv)$=`#rv>VF9yF#lCmG=HBye`)=7gKX7lhh3~vYlWuQQn&fYodW+K`S?gxNf%Ze&
zL~N_ycL?0PbtB)`?Ap7h?<VfwvQ;oQZ*8tdSHPw>Nk?{`>TTBIwD!0ilw~J4b;+eL
z?$a;R{$0&}eb@P{%M61p(^MvNt(qgRTGn#Q;pf!GoEP$(2W7<OCtt~5v+nJm_g`+*
zESuzSd1P`PU(bA-#+Zk09EaY<bTOQsfBa0&y8JgKm1>)to%*9Q({@ChaQB><ti>$*
z<cL*D!bWwig<nnMh5s|8#b!;Y?LYIIcj?ySGg5EO-#0Dd({uKe%%|_lpL6ec{Pfx3
zAL)M6-=4OZmyy5a$CsCnr={gySU$Ud#@weJGdCUWw2|AXws(7LkJ0@*zUy9XH!q*)
zEPg9?Vedmh<6XI*9*5eS^mrs3+$9jM(2#zo;;F8UZRScplO@@^H)pf_XSlU0C#EG`
z_glkG?v~W2#(Q#)8GKcn``GR3vx|!^fBEr_ZNYS3m5X;ZyA<<{T$QzxjTCi`axiQ^
zIbmU^_xul?2fxMCXWXyPs9pbd|E>64pZC1iK6!V0`qY1`zgOJsDek>*8nf-f!|i)F
z?a5xf^PO()^9E0w#-4fE$KIVi9(%Ee_0S3x1~vwUE3iDVPVfHlUbEh{SxLt(UiRBG
z>BB+31?z2GLpHQMvt4jd^Psfb2d*9Jjk~w3%gblG9UFb`VD-wZ@XW$g(-yZ(fvsDF
z8e{{Tn2x;lpXKxxyq-OH&&O$t6aOy!HkTQ6iKo=m>%Wrb>s@$%;9=#CznA~LNwc5+
zH(%Mzv|d83_mOn2*;Ab$%cpH3;a5cSo*M0Nt$1+ou0-0wq*HDuIf6v;E?n7Tp1!I+
z`{yUW{kL{iz5M(p!R(mL9nljO`S;D$l^c)8T;KnpckaJM*L^E%g>3JLUy63th<LK2
z<@h$YpXKt?RDyQiY@ECB!vW^WwMEY^anD{obKSdyrqf4?ZIoU<HsZ(+P~hVWS@kru
zU5j7zlJBF_9i`p3i<j0fh|CiECUp1jg1q#(i8nXd6t~TFPFW|;>OE)0q{j!Na?h?k
zy8C>YP<5@--Hy@|(I;ItP5ktg$6#Ocx~i)u_n4>K-!AvG_?@;ee}!k8j3@u(Eqrz_
zKM5<Z*FEu=LFVqfjcc>2ROc>RaPfA`E33Cx8)scBI;zn5yez;;k!1}pM`9a8r;+qi
zkw2>CV#^a3#oU({JZ!fyL-gI#y@jk#&NEgDS)6HI_<P-}7ZV$w_V#XVsB3zDxaj4#
zLjPqaZSQ=WwPw~51D_L&pM9D#rZnt7Y;x3GPG;S+TZTc=6>+*M(cZH6me%JlU6^a_
zo6Hg6(YrX*?N-kbWg~vW6F)ckIV3O^ANqb>{1=aZrTXkrmd#PVW*7DqAJ#r}DOX1C
zvt;h#Wp7d*n{JG(le?UDX^ThhyIE$t%O^d0a>Uc$Dm*iVa{}MlcL$5l8P1uP9n=7>
z44;#^^O3La{68<b&7iZT`2R|mM@@KjEBEZnP0ayYroB<NY*Y&?SoO@z+VLE7(~@rr
zeOsregC=Yu|1)d|ZU5K1dtLtFF!6HpZEwY9%7}g2r+nr8)4k!oo1ea0aO-gU=c3nF
zL~k@dKYxP3nsbl$g4>bYH^1&R({_5*RKCmA=}eQWbmuWIfdl0%a#NGOhg~kY-mCwW
z+dF)sN=f9i5S<mf=k&~TTCeg=X4c~`x#9sIu1$Zax#(ib+%JFSytP+bo43ZMO+Qgq
zKldufUEz0%o4lEuC%N0Nf3dyFylHE$S+=#W>*YgX+cv+QX%=m|>yEtX)O|HVo;|DP
zY)Q8^+|^*~6dUc^`rNaW+vDC{*=ON19eV>qXKc4&*rcfPg>U(e71v`g-uLSdj14=w
zCiVW)JKZgY`wpDBk@Mhz^5hqydwGjLzbN0hy=&duH45hCw_3Mc@CY)S<guvhPO5p$
zzNAg3lJ9?NKWMM1w&}}y-fW@!(RZ@NCi$^<{AbwW9ea|cPf4nNy7Y$LQ1dm7ZXyM4
zjtS-y_#W{_`|jG&b?<(_mRXg#N3RqfH`;8Y^1y?^Qo~<*SLmrnU*7Y@-m;tW=$OS^
z8~6GZu|`u^jw{_=Q)I?}#_J@<JBI@n2aji>+_oY4D{T4S#oun+lUI6l?wxmL(%sz>
zhn3SMelE_q&%EsK@(I~|zmE&ts0h0pH|dyL)7z&NqAK#XyHqxFRx-0L=-A=Jc<0ob
z@M%I7lMi2)nzvYTTkf`9Jx+(iB-l$gO;&hSWW;l^W{3St>(9S8y54JEnRQQNc5rUk
zZ?C>{`kNxT9rONWS$L{W_&IT((W%bu%yOQVhcB>94>!&T-<99~$8u5TZnf<@b_i~H
zc1dHJd5^$CrJ6~X(-*v`&FDWWTxlHbn<#Nj==*P5-J~75B9kRt9t%xjQRv)msKIgT
zU})ck8&&nq`Qm|>N?t$PS8MFHW%uT7d)t28_SDJAjS{%$tz5HelUubg-y^n%;W~e8
zYnNwkQ%#uk?6c>UC%bf2em}i3;i!t&GxwaI`$D?xY8Tf;yPf#9f#J&RBj(f0RJY1%
zpWGe2JG#u{nLfA9XC22&LCt06GAlz9!X<8<I=j$p`O}KF)1IG-zs>f1S9AA%`KgNV
zJi~J}Z=T!azMp6Cb+xYlkz2wC%a<IN-Lrk0kB%NszG9d4jC*NQ+6*Uz`U!|VteSLN
zY~JFB&P!eg#8r5^ZoK?tvj2`PlOA2-NcuD{a&6OzaON{NR_o06k8LgD=3=;W(Z-u^
z`^v1a!rLbWHx)4(vR8Gcw#-j{7Jd4-z24zDlU7e(Ua>i1$Hgyevwpj7+<w`Ve{*hz
zsra;%-_A<zQw&zkpXGY@^9Lih0>-}E2fxo^J=R&e?A5Pn3uYzhcHO*NJ4gSf%%UAU
z8&{sn>GPT7`KjwagIw0U_6Iw^tW`fWX;-|j>5>5V6%qa`y-l?4Mg4gx?U8&}WYrqO
zPpv#5VuBBtlk!FG`LFX_n(-?|+(>`+rtI09d4ekAB4%gn<j-Ael6m>P&VsiZ<|iM?
zi*9eLk+s{tB6CyiI+X;Sq^U8dUe9@x_i}5L(~T3o-l8m`GP^PsJ$oDX-gR<hzu(@g
z3A-*YuK4%$?4g)LXEs?KSE_WCW|?EWTzbk>(|opyzTbz6j%F8Tik;SVvd-1Yt~Xdd
z@BGt6JEjJidvqOI!n8ulfm?F{-zQoBvYo|Cefg&<xoj7Ezgwx|{HYr!<c$mtGfrSW
zRy_T{g>|_umwvqVi&W{$d{a`{`uJF@h{>hHPbVyy+-CN<aN4nZ{>rwh48_DO*`e{m
zU{V$t4~j*^f8&pFF0N?1?Yq-kq^~luRrD)s^iH33f^ilG<!+K2A~sFj<RsE6y=3;0
z?f3KdUd}b~)HCG{nH4NKJEcfzfx*<Gy(#HjMhtA0|I$9~%hdm)oL;|T>*ct3m;Q3r
zFVilZ60_7(G<-X8U+nRxog(YX64Enj3^ua2y?MK}|82^o`t2s0J$070zZY|L)o?Qq
z;YeU+Fn>2)<>_~Z)c*{Ja<*?eGD~$y`O1<H&Y3owO$_&Ja`>(q|3s(3X~luooS9A!
z5<B`1ADOjm>7%_$_pCFNHcY$pCwAd{9rf+=EF#vw`<Kc)VY&9s6qQyj#tZQr5su5<
zvr~1x6*-rEFNisy{8_P#r-9*Az^Wt1RC$(Xu`*9(@yvW!oh^OW>K*s)jjEGkR;Mf!
zS9^HPGs=H@Q%b;p2DJ<P47oounE73POio|(b1jQN%ya+Aflc>)cZ-MHMdh3+I>Pj`
zSl-aVAwozd@26Xi>*LI5$N9nD+S30S^xoaO$u@E2(lbR{HZ7@kp6cVV`=HhVJ;}N}
zzq`KXhXr14dz-PVZ>jFA+q0vy)8@Es+wg#QMKafs1`+n6bB2eRBIfK(K4f%$sZZ0V
z-$DC!?cN|9<E!PYu)XbNilUFVMC`()2@dxsUwP=jpueZ^@61H?+i&0G>Oa21Ht$jO
ze+IpaDF)mPK2MEAjyas4KKFT^;pdQ9<-OA3v)#J=FF)QP)f8(o*}Y_$M(duFB0Xz+
zPPA+mQDC~S=G3ODSAR&I{bu3c#kGGIe%rt8KSO5S>vNy?tXD6)J1_j#`n!+Q49}U@
zTrIlo+;;EVsgLW{J>Ri)`#eUKPi#h&>!o*_%a*$th;uENz#zfE+<&1avo`TTwDekk
z|4E*~hkI8ZRGA+AWS4-e{EQR}Yi^USkf$eErg6F5dTHtp>aX0tAK7hh=ApF7P+0Gx
z%JkrqOxguyD^h|Y@+^{DRT8dW{==P^xtyDO_wBcSS53ZMR`lN1TeCWyOO~-yVD3TT
zX(y%KI8L4^uM?f59qab;eW`BJuZOx#Gv{&4wL7ovE!m%wHT&w^8SJbPtvpVXGMIxM
zujQGhU3s+o^1q{n%kOqa3izn<)vS1OX9?q{`NlmB1&oTGT4vg_Kh#YxUw(L%f5r5S
z@89=la#m}3TKqi|I9bstK<MITR_8660ZflGUTQFm_Ay5L7(=Cx5vF|2q}J$|r`~##
z)f_I{`MmBdI)3DKY^QZy?z`Q8Wj}b@%tBfIefr`a%X0pXlG~?GOMHvkx9PRANV0TH
zobr+IIZYSypOmmP_dIGaGu<!pa-XcuuccR)2;^_;EiPK*d)edUw6FslOw;a8o-nEK
zQ&E<><J6~DOmBS2o#lI|W8Jz~iCdd>ayZkOPZb?4V0@Be`GoQK?H}1On=h;tc{$13
zcHhheZWr85qGx$WPn(p&vLU8bd6I+WgIPEBU)tKS&a`{AcP8ib2=5j1?w`n>D1Kv6
z#~!)zcUQl!4BjuVKC{p33G;&3Jjv3zR;TWtp2z)KbG`D;K8I7GQUZp35(cv^&*%Mo
z<Skq7e&tbLG;i3kcb2LK$_EQ3u}#n{YG^*q%DVA7v#oY>^TA(#&$V1L&y>1*c3Jkc
zOTH?nPO0wN>E1DE)lQxT+njik->p1!ZRxw2tFyL8P1`Lu)pqWkz({HB=*}czPt`4(
zJx<BWP8AE8a(H)H!TG7Tzc*N&EX_6JuHWLjBFdfZr|_A|DS9ssOR{+$3vqkWcU#()
zmveRIrs%tO)D~u3h_qgMrQ2v~<Al`1a~^v2c~~5;`uux7)2ok}Qv2qAn`tT%D_6S3
zNMKR+$psN}8`7-hOM)zmzxTeG^Wo@L)Au}a=L=Wz>hW)mUb}3HZr$0ZE7`8Sii}ha
z`{~T0Azr{aiP3_cLDuQ@F6);UUumzpv9)LSpWPD++RSfA&gPvX!%|esw0+@Pt_N@S
zm{!^zn^{_&S#D|d@=BilmL=OOLv$w}>N_peagcB0Th1MQ5)+EV_bgz79_PbjT`%%-
z`*o?gTc=)Ke16%zqv=JeJ3~Ozh~_d+Pcb;$RT6!?Hp6*!=63UCr+A$%MQ`YN#xgVV
z(CQgC-m+WpaZSF_WOZG?d`VVuO!h_9mf7mpOK!hVHFDqPvDj>0qP&@7yy8g~o{v4x
zdaVynFY8}wv9V9xU-14bai67(h9|aX%k(yX7TV-wJ;8v_pn!4b>Wang7q?iJR?mJR
zbyZjDlf7ODcna|(@)Y8`e*POZcf*d^zvZdzE<MD*<+;SCpFcnEtV(~+ANBD1;p^g7
z{=Hv*hyC`s_HFV@s~Q$o!A|AuhLw|BVqy-9v9ak+_;P4%zwisIeH&NY_2r3L6SiyL
zRMDPm-!@07Pjj5HVMiwO)EGau7v=Nhn_Ew?7hM0A`7CdDBY65yL0YADcfc>hdoyJH
zo_-becl^jV`%yHfe#!0`&zr0}b8k+(x-X?@=TA=w1va@=r>d{new$cp-uw3Jk`29U
z-^OwHr5u^WJ9*_)w>OD)7aRCEdF?_wTCTOX=B|6Q<@M?6(~-J&vdT9prnw0nS3NRm
z@w!U|TstHzEZO^78u9{NMHnTTM0ZrTb{SePT6{tzFEz-kscHhZA@jD!uY&?z8Qf(A
z4t=%>bn7>MKXs~u-fgF+d;P8kPQJl-3v|2OBQg(;@8_>SQG9g%H_`t83?6H<7cAf-
za5}g)^x#X>lh#oW;|3p5{GZ_=fdk@U2W{d%9UQzk5C4hfqi$k&(na5JS{L)9-DmT)
z<V)%ETy~fA{%5%2ksPRObbOb?ZjsH(T5SoQ4^k$Eys^n%@G3sd?0WFqoi~y)bDnj2
z)KunpFW_3|cO|*u4cAH)K?ioUOA72!lTApOoatp#c>%lWoRbqh>dqEi^jKZ=iSst+
zRL04vyA37?t)0g&bG-H=`{8X-KC?P@&U+-fMLhdSw8zma$5c4@3{*6n->4Y)&uLh&
zfng)Y9R>ZUHwK6<EM0T!=F1E5-lCtK&F-$|ZTWP<$jIESBep{39W#4#^HKNuN4)mF
zn>O#>^*h4*I44VHs>!6yBI(Dctca0ab)<>Spty@+IU#FA%zH}&Z6+KqwLPqMK<d`H
z%t=lsHfbF@(c*Di#_o#B+tbMm6XGgvAKs>8bJw{fO>Or1Hc8d?jE*zzGrEGyrz}16
zyf8+9Ls@}P&=vi7?X*pL-Rz*PzLV^JuT^^`s;HbP&GWIr!=<=ydFHXKW3wN<l@HyY
zEnTU1>0!*VpjXGL>*pubHk|0<eq;UZ>+NaB7)==E@kda&qbvB*chqYnFs>^AP5qt!
z&wz4~#A38;T_OUx*%b9|3-maGoSi@FDA3)mgD#{_&lj*${&Cpp$NbgX=B~(!ipuF^
zZM}Tl=m<~X<d)ONIF&8q>XI+3ggtNhXYu24z@6TQ_HTc@eH1cr%MVpg=6QWjomZT@
z_CV{&mje>((|3F@Z(VQNeKzX5<HkMv_S}5#T`n-&T0HB4ozn+~pAP5Piep(B3aZq0
zm!~fOu|DdG$xNN6-N9|%x5MYk+&-qOTXX%+Og=$#3+8EDY>XCC?MKb0S9M2ZTBV2!
zn`~E-)XO_#cv5y}pXF>N^VCF>R;H;31vlp%j5)dJAnkEN?S7SG}=HT6`U=&ZeR
z(>4}?3WYwyp!!4VEMZkOVNtzb=U(mc=el?FsmZ0)Q!{<$B^hnDUbNfn?$Jg|NlS*~
zTRtv5vVGRNwK@_XzR1aMz53AM!8zv6IZw?RceE(<KH=@|-*-D@(~m~pt8FW_md!4<
zZE|>bt89^8?$p#WS0mqzUaT5t6>pWPpZ#1S)%oD9p1qam=c6sRLaJP*S^sA!yP)=A
zznRV110JvE-sNAxw#Ip(*R*m&|8-g0jn8h+y?mnMW3FZFYAKx>naNYF_q~1>Ai|J1
zUpVXgrXNYs8YP!=YgeAkFV@|+K)o&F8fUzrMZXTC^PCpzN4HOH`*mUKN0;kTOZVg^
zN@ad8-!4_V<<WzgJ{NxO{(gJ|tN$JECfUxPMvK*RIv-jHu1&M*{d~`P1+SC$vQOLZ
zcs`XVc%XJ*nUXNqstR`NO+M59iErC>Rp?FZ-8}+#yvtc9i+ox*&-Y(Sms7jS&rKiB
zgydT=b8lgqyS`gb`tao+UEjSvZRvmW?aG2_+>JWD0=^GZ+_*P6EfEme^~6BOfZM(F
z(d)NH+9%e3$+#V`ty)R<&3c=o6ZO&!mR&FDf6lY6Yy$h;pF6GdqJFrYyYDyOXV#}*
z?|rJ>Hg=uLbUMzuQ`#qcW9aOs3~WW`7#_AgJF!o=@mkp4EBWi!EuD7FZRhM$;kWbk
z=L#j6gx-=btBXBeDfu9QnLp%OX>8bMuS-(btaEQ2+;~;&e&8fK)|EQ~MOJh@$<;dY
zr@biWX~b5sf0nakSz>NyZ1T*{et4pErd;-;qoI$dtZ|(oUVg?Q&(<-?LxKIJ{X^-^
z|E~VK_*wn){w?-f%-%`YoZs|!wyfQ|bA{K-YYIaie+Zi`)?2)E&G$OjWBq(RZ(_?i
zk|RYUYIfZ3j8>O;P+;9a+~lWiYx1i&>CIQ|xBmI59{)Dhw&dqG1L<VBJgz4)=I>`u
zo_OH#x-!U;h0&pt(V>%}GISCyAAdPlH|}xZl`XeJ!l&e!XK&E*emW^~W0T~>h<a|b
zJM%b~qt4K-*(-f`dclu&-#vRa_NT6Xt+&b0&2a0{M>ejNCv?UBxjT4RoYP=Vj{fL3
z`{AYYt74-Z*?wnSH`h|RYtl0_HHV==Gxw$?r@Fklx#~5YH;?x3*uQ7v)~#EnCRfgT
z!Z0&L`OG;cLp_6?maKktIedKg4@W(n*P5~1XHw+bFK3y|nk*OHxfFG0%VY)BrYD**
zlNislTs!)2>KfO=HL+3A9zMGc#kzd^=N!|q@2H6DgU|cR*6;P2`{Sq0nWAt7S*F(o
zr`No^7WOaZLwuxfrR<p^wxAUk8hZ*3w%j~dU4C9D`t>f`yK|;byS29G+D6ysCr!#Z
zPE35-_UXU_y})BtHN7vgi5ot-+OHk3|D$~8v+Wm^H|?2q+GmEd{-n>_PQEi%d@V4C
z#V#&#ib%&sW~~LX%fG$r|J(m}{omEee`o$@u-~8Iul_#w_s`qkcf7vdrMLC2+;P9=
zz&%%Ua^Ixiesbq*L8r{@wx_p_Jb1$7X4UoR%U$s!W_`DoKAn5_&d2QK0RnrjJ$sZ9
zbs)Mg{B(y!+LIIp!42mR)^;Xb(Jj^0k8VHwNnqOdiQb9nI(AtmpN=Y&>6~c!_p<w8
z|G7Wnl35Hd^h$Hh&ONfOUh8y;^GU@;<!Py5X+;MaSe{JNc)<7D&q``}>Z4w{U$t2p
z>leu1xb!o8-KAwWJ~W;do+pwzWpa;6o_*Vn{|rBzzDn2gXH84H#QA>zL;md--#&AT
zpO@-+q+`tuMbC^rKgP$Gdpp0pjWF+;#%r%zxFR|(>eRpBPSK?8VTNofoD&WmwK*VO
zKh0Cwg5ibz_LBNH^>6FnM$5lB|MTx}r%L<k{QKwb?>!#3C$#>Dmr2=mlfO#VFI0A2
z(UtpjJ7tB-#C3NB&-pz#vW}5OdCs4$CtvQ;@5q(i>V4XJ_s&Px{T3)zu04C?!q$fE
zGV7-c6r4SAf<ZZPe$(#>QE~mk8PgxT{?^^OWq;p8rAbD*_aYOg`pi()xfh*xb3fnl
zNp?w$S3u(n?fH-9n*DklylvC2EtOwx-&pg`WxG~`@st;CkLT=k;E-P8w5N0}M`^Cv
zvoALtS44T23C=k%S=%DCSXy?$bH;-~)dKEOPv3p%^~>(9QrR#$<=4B}wJgg#zMT|F
zyL?9Z*$M3@mI{sY4Ch>2UQzV!;+N%OhDTmLvi|Gza>@cVOR=}f6F1Z)g?YFau`wRw
zV=&b#ozMHj|Iph?<{P&&Cq&sk5x6CBF|}V|vQU%AyG#+Df+*ML&qNpM?OuHNo4k4G
z#(wac@`C2Kmd9-N)z!R<oB8|jwH>7&z8*a{`Ejk?)qR&u_b&P6H=mKwCCTH~1Fe*Y
z;^GEJ8ymY*Yz<Z?ANj?%eodBnu(Q}|(RJ&Wx+a_MU30DT>4Y>LJt>E$;lho(WS_S`
zcv!@E$Mo;4%Gv84#A}5#`J7-oDW7-6uBUt%d+^R$*We2^&dYvGJLG*=@0sO;zDLnz
zDW&-{W!BXNxp6SIui7;4Yk%#Mc;Cm>wV67~+124q!ZQt3np0k-2JV*d-;%)G<m^8+
zNzruS!|3eYx>ld=eY)mdE;aW}N94qojVB9LR=nOahiM%fAD`png$mNhha}K)ww2wy
z{9)M@n|QsI#pMbc%)WK$Dr>Q9I%u+KwOx1t*Li8ZYmy3WECn7mqRVbCn<?dA{xstD
zt=n5tuZwHv++JWLyOULB+E1=0bIcw##;S@ip1l2o?bO91(|*lcDzjmU;f)hKE;rqU
zPOX^OEXiZ$ul3B~N%Nd1%r5o(Uv89iZdtK@tIEb%r{7FEv{{3%rZNB7#@mzr1+6&v
z_nt%U?6&MRiyDmIZHeaf_iH*GzO^~DPj|Wb1$VXQ%+jac-jaCog?Z%xrp;gX^PR4l
zB_fr2{acJx?)_O(Hw8=zyDO8pr8XIrPITiq5c7Bfc!X%j9?@mDqAI0ozL&XKcf8YG
z+Ie->%}IB28+>0K=+`Wp`*7b!+X6S)=ZE{Zyka_~J%3Y0iOb<PANIv;+-#Qoezoi&
zBaYhNbpbpn&zxU~1hC7mt+Bdn`Znu%@ZNp<jC@5Vv;^`gg*PrpbvK;J^zi1kyxV)G
z9rMkpKV+W%clF=J&-|a)XVhop-ZA?*KlQhnRqfq5kJr8X@n{?3AYs_REvYo0-{qio
zw|d#E>D<bWsny>)#SFMby}8pAQX1#*2S$GSvFx||)vvGDX5F$5%uQXc<oxaKwS~{-
zRUBz@TCgf*L74^zM_m}Bx5xJ|v0v@oTh6BYUrpJ1W!-Us%;~`@8@A37+$N`@ylTgT
zCrK+;XS~Z_vUl&t(yvD^MX#8b%T}7<BV@ACh~sT&(YmMm5)M3I;y9te@=s&uN5_kA
zb$l0Yn;nrY>lSMtR@*0bb2*dbV}~QjEE6}p^KI8Uy6W*C7mxaF%F}KgeYeKs_w0|^
z*(-HEDKtwj-odq_&1Y8+v%-nGy1*UXL6=0=sP3G7w0yc)d2ZQe|3!D7-Z}E&!K&M>
zp&ZX!xKErsspD6>cYW)lzjsbQ+C4jP`Prq%v&|+}KRueMcK)tL1mgoYh9d6?b!j<z
z7kJMLXBVrU*_9)gqMu*5#4FvCLvQo_%A6Up+m1OtpYSC4+Ps;M=9ZdNyY0EGu=|RB
z>F%?3B5iM2Tzl7XO-q*gv--(Y6{e$ZZ^W#%W|{R}j`6Rpe)Jl$!*s#9rLJ3!WnAHS
z8v@&6x-q+SVbtE;=|?_w*ZMsUYK?c^b;#zlM#-Z)LNjMM8Bd;MsgTrQYI0vJCN3`W
zc;V98dH0^Z%e74vXFR#9#Vh634$1cKMhs6@3$Z0LJlpW5CT?5Urq@D0C*IuFy7;u{
z-m{O5oW2X4YuK}Xa?h0eiYyO{n;b-oq~G%&{HD9%N6+8>fE`zq&$U;cnOu3h@$d1w
za@7w?A6D8to5T5Vb~Wo3mydQrr%s)-<m)WoWxr{+jS>HygdJ&jin!)35IyF|aH0PZ
zi*bf={E=DNd(8JIO?y}>kR!Nfqu#fjHxK2e`b_!H5aE<O_iEDZxU27LLKix1`_{Sa
zUgq?0;hfz<?@}t9_T;Q=^Rdt>*Lyl;TBw%D<$qT<{5$u_e#@Rz$l1@|Os~(}EnT?z
z%|E2mpJkU`YfY|R9($n1Pi2$$)SMUPE-|y)BULl)FaA(-<^Pn+@PY0Av<98}L**t_
zCcBpW3dv^KW%KK7)6$D+(<G)!tl8<HRHWM9YQ(?yJacLHekrr**(>&~Tz)*&c2%_3
zO4UnmI19C11*iEW8A(Rh-F@hAYV(&hrrSR}|5kdmrT@{++<5=#KHJ<bylcPlb_tiH
zveF&lL+)p0pFd&wbo0Xc+J}GLUVVBNQR6l_=4h_mlMC<dORjy|v(c)V@n`eCx}24_
z7+F#Tc+YeH=#v+^8FN-}OZwIwW}o&>y|ANkc9LE4WbPfg6CF?W7$lxED%YNTxyF5Y
z=C`*plPczY3om+ad#$q~vX4Q6n`u!4gG4CvN=uc=#s7qL_5anDp8q2l_n+b8EQTBV
zxBf1hTb%x_^X;D>^YpFme)E)j;Pxc%jPZnOsi)7b<(ua6-S*)BR$KNdY~!BamKwQb
z^~aB#Jed+Z!_ZPTtzlyOTK*qCTlW9_dfonmYxRGIW7#?t&4<nE6lw$4ex31Ne`4;%
zXs6xMGab`3f6tko>U#I&sRMH-H5h%3myL+}aq(%sP{iTn<*|pC--$H6ll3mfV(KB`
zQ>#yAPg4>3q|PjFQ1tCTgPXt5kM7?^?~i0Z%@R1sek0|Ii^lr={H^Ra|2Z6Ux2b&;
zQPp*0<Fy+5)P={FNb43oyW)~G{jC-2WAMc*b<cUud5fvk9PPBtnmhG)du~auyU#p(
z;ros&7I<&lb@Bbor*bX@G8<ZCHXY-%E%JQa!w_*f>B`pK-L>jR%*6}+(-+^2xwCfZ
z>FCXOy;38&ZFD%f5+8=N{+u!4M(n2e_^ey@om;$<Wxs7YyZnA-XZBN<l-s)7PRho)
zI30{=a<fcwTA{-AJ!;wP!Y97G_q*QeKkiJN^oy72@tL{o789dx9II4q6Uo)NUDlS6
zvhB(r>-6f>(%ke%9B1e5`SxP|jp=73ygu&UJef1C=wegEoJnW=JkK(u->ukG&C7pu
z`}A_5O!54cOM9DM8N1Y-)tR>KA?IPE9G+ug40H58Hx+5^*{8Z??}xC3+4*ZvR+YR>
zx^^qN*XrfdscTbqcN`OaWS1<j`e)Pq%DF0%$tSOL{XYCL`_ij_{vG!+RV)82zwn+X
zTiI14`oJfPgb5F1o^YzjN;6#5-($Zz{&1y^opP7QpS6c%`98Yri}`q7?mxpF+1pV@
z><cFOBy7uInj>|0+mv71mM*H#xtsYbZf3FGLbm0qH|#T9`#b`q=WLqP7F5QQIAz1{
zsl|~O)i2xFe6G)ZwSAtFp~M@BIBzNMihxazSaVx_8t1HT3ynQ6QHWvL>e`2Yqkp@f
zZ9h_2pYihT@;g7HWS^gxyu0Ny<6-@oY8;QBTk^IZixGbwu%kO--<6u!<ymcaqEGX#
zZ+}vueDLQPyVTX27H{A`dB^R*ja#A)dU^AIoBtEy-*&$~qyCWNH~k-frl0&&zoqW%
z_7iuX*01_myxsEW=H1WMO+Flawl~;kR;0RB?8|MQOOnof+){X^Ve%xeHLGTKs&30u
z*C{;v^OpLp&Ch?V|84)aKKI|*e}{H{s(EjI?(Xh4_ws+;zn5HRe9Y|6*5t$gRJLsI
z`t|MG@tCgnLA$e8CQ8XZ6y#kklYPV`Pw=?h8!_qc32%=wl%t<2-H)2jviw;OnyzoG
zvCS_OnQ&fgX3ivcrKu^2LQNbtP5crIcwrmI!AqH;`*<vWBX8$*FMV{|@sX~!$EI19
zsyp{ix|jQL2Wt@L+#cUUJHvZLw@tg{ckQ6k60~#TuGQ{u-`ZW9?Ax8%ojEOP?Y*Vn
z`nOoj{PT6kPn-4n8Mm%Woclas=7DnzY)993m1Li{IbONRA}RCC<s%=Cebm1<&AdR&
z<Cvpf%L<<57KxMOMKX;e@7$TWyfydR&xtWn-aPjW4<)GwyxqBJb*uFZQAvfaXMe08
zME7dlxgDdrq>0z?%Z;?1yLax5yxPQcmZfK<ki4$9%k0e)m^I>O9kG+V7Vo*MEi<{}
z@1kqZZe8+qtG@bKVTPCIyimSHzAI)sO_*KIaI|9qZ>LTC!o#V&cdi$?OuAD$Re9RI
zkm=`c#JDAC@3Gc6wUS}m)7x`T&w763mh6<%x@XT6#mDYFV)%E~v0$Ck`Nqm_qR!Sc
zPS1I~{@erBb1Jp=5m)j`qIZ8x=9w1Nd}oh=$2&3OTpdT}snWMg8aHocV3(PCy7=|-
z*HZRfB`emn_I!8K&3bawq_0z@=-xr4bsv^2W>lI~w&ADO_d5(`Y9HrLj>{I?aQf-t
z#HH>l^%mtmna0$oV%>Iuc?HKBv;F6%F;B_K@_i(0bU#F@Wbz61dmA@*s2IAv?OpMy
z^+sR0p6CqWy#{uv=k@M!U0HB(tE|$!YR`lnANE+8lnYraS6<XPC9xog$zZnS9go{R
zGS9Z?+gPvkT@~jpxaHsZeOKO=YNlsKcndo|se7Az%en2h)t{r+<r07T-Jii6bpEK7
z*}@fDTh~6HX?0qK{kxxlw`9V{eC7NZW}9=)Jz88KUAeaF>DwCfO7?GlFBR;Que~qj
zG&nxv+3&Cm7QYXl_vxEsuHN$%em@0cd+}plrc?i(oq8SACz&gwdfB5#dAm;6>t~+5
z9TEn&A{vfs896ff|L`)I|K|O+pO@c$uIX2PGwJW*GsoV}bGvU`c7MKf@#bg0_gt&J
z-u7Po-?iH+%x`DiowiUe;-idx>K%Uhil6+Am#01{?yB0~qMx6qpSQT;=D7{KdIWW!
zY+HIIQg>t6EW>@qbI*QiJHa5or+{%~{@RLc*NbnCE_O^$RQoJq_U%kJN7&!jR$BjF
z2KLF$(Qva!;#~Dhyjy9{#V^0_y1n99w)66r-<=9w?0@e}_X(`anX}sd6np3`Zy}DO
z)$x2;RaP&<t8(}DY!BNQdsKDJ^~o&%89b({rG1{6Ql4<}!L-2rh53^iv*ylk+Nzza
z#vxVhY`bsf5{Cxs+{!h}DkFrqD@sfaxS^6Vce#Xutm^l!l3dFr(W}qvPI?n5DrhZi
z+2ONs1;e|f76G;*kHBdbD;|EVYcG1LuzONC$B|Xhr;b>yOlxob&k!dfl=z<^f<Zku
z^~R6th{@so!TY@>RIF}Zk(1Dq3)uL#;Z}phv7Na$EDlJ#^Nra0;qDXpo7PJj{`N=j
zy`pkhE_wFbXott|`E8A?3hvA^VpN;|*w^m;;V8HDHsOVKOY_vdJ=Uhp3p{YgNhx1r
zN#p*E;GKSTspnemDPK}>cwZ~&zCC)zOvXZ+oP!}p8)^<kPRR9{vx}$Z^*rAi>D7Ae
z4_hWGO#1C{`L_Qg3DfLulY*KBD#9*}=LPyFth1}zuW+vQe#?6vDVwnTq|QaRT&A4}
zcst9bVs_@;y_0M=G#I5Q&W)FT=;UB#QZL}TCadb|l(Nr9ZpGf%mOe>6P%YX04!4GE
zL=RI1*In7-jS;{6=2s@K&Hj8w!EF2W!aKJ&d3b+h2{hU?l_BBi1V_uew`Jad&t71+
zfB60<U&ZEshc^CacqzKJMD+ZR>VMAjbpA7JSX2MYH9MA-0e0%(V5dc&{AUoZ2`*gz
z$Lj-Ie`4j+6Stbq7K=~e3vv_CJSls1c^tpw`PgN9llD3MxV-j1L++n|t7b8k*S=Zj
zEc$8o=7wGA3(g~Letxxmh7R)a7en9Zul;Ikb?e_bf1_)!RA!0aa(j}%HAl|PQ8w!+
z(See9|3{hk+BDyw%h6Z1ynMR7?_TKE2+7#wOi9nrNkx3AbuDEp{xdw3yK4WU_`3c3
zv(x`GC|`GU1<w%oXU+d&`Fj5MXQ%%&OnmX5p`|+HKf}WFG5;C%o5la>hs_Y%uByNA
zd|mzh+4}$77ylD{8~m@`w)o$loAsY;p%cU$-&X!-aGtmGKSN#4{-1LFKis$a|C0H7
z{`cq9{|qO-LMMooZ!Q1JSM~hw&rSaso>bY7x{2IyN`0|Q<6`S;)4zAWeBUmgF{^r^
zMAE$|HwM8)D;SgG?rmKOxw42M&^7V3)Ul=6Yi_)(ikq8RZhLjlcb@Cvy-bUaT-0N`
zac7dx;SDb`n2Wle|3f(`4ec<q1$<4TDv%C$8?f-mnzwd+#cH>U>$iIMGP`BytbMX$
zV)8XroludD%w`ADnXd$}N78ePM~r=Ejrzl#HjWQ(rhND}<x}jdO|?sJoia*0yY%$j
z=kn%fn2YZ)U)$aF{Ezd02F3H7{~2zC`TtegwSf18Lff@_+SL_{+c+ku6dqd`D#F9S
z@PNVMs3$z>!dp1V=kZXDjj`!}UDHn6>afct`LY?)rIszsOlHoUeqvLs&qmFBvkMQz
z6w(>yR7)|u)>v1Mey<>w``ziT>b!5!r}N?0)-LRSJ3U<LR^&}rn`ai2|1xRL5aT*3
z&aL>+FLD>pBpvrhr@N<a>N@ZB`Tf%0fwTCxuyX093Y<|+vMbX&oRHAit`od8_0Fq0
zwt3OBJO1P@gC0$$>vdy`P>0x^DZEn^jx7;5xbLGfyTs|Mru#Wwe#rdKknoX3+*kaT
zSmhei-5&2!gm<0P$TytobmDQbNlssjh7VI&Lyr67-fNnxjxRZ{b6u)#a)Iup_m;n7
z&P%xRw(u-hFF(D%!K;-eqyA8E<>oi_Hz(BR{Ab9hPyZ>OZJ++x?)<koKljDG-4|Z3
zZ~fz#UDmTNoqL3H7iC`ie$Vh??;WwI)IG;|{bXC$+&}BI^EvBDc3U^Y=Cc_w#QB5a
z&d%$mF4GPj;#J~*n>}OM%!fPn+~iX6={VxC;_0Ror=5;dRkj^6yH<O=Z+qtbTVYb=
zbCda|@@*_jpMPqi?i0RK$^mQSd|cH+Hu1du+2<+p{OTTAt;jv`0=c^H*9N(WpI&+E
zr1qMgwF-#}DTj>|4+L({;NDsnwZ7Q=@XNK2w`~8|H#<H3o5q)yZx>#9d+N@u1qmB1
zYtJz7E8J;~er}o5;J~(Q?jxOw<FOYWPk&qfJit@v=CcFaw~Af6{lvCl_ne0gKj-e|
zeY5plO>zFR=;&jty?d^kS2eB9y0x-N#<3{5#_QDcVzHo&tp{Qc2#7G5t$$#)Z_<~F
z{a(@SSA+w?rKZTMG>JAea2~tX>ouXMu1ukMOV``_2Q3k^P9L9UW*+EWs&wb@id&oC
z?wEdVs-Z&at@u2<*ux2uPo6M4<;yOvPqCf5L@sV=Chr~X`l@Z4{8WE$bl}j|Ioz`{
zm0?f4nY8kTb^JkBZG=}wuU%a6>5{hDcCqbdr&k|Vy6fCzwsXQ}CdY(WuAS#~Jc7*8
z?i^jgykODJ{|p3fCZ)2fb@j*VKl$5ugEk(o|0{9@<3@Y=UYpE^(d(IhwB5UZWS7b1
z)5~I(6dtb^Hs09Tz`%A=<zpAadyPe14D`a<^FQ+cX}3}T&yW~t|E25IE-sAHmahrA
z{+!fl43gFF{C)nXMwR*BruF|BzT_?~5j}se{-pE8{cl9;|1&Jk)nE>?jrN@#GTXa5
zU`wr&$bH>KXO@M;S*DzG_&I%&b$^u3*Ie^}9lN$~x}vL>zNL1$;bEiQPB)eL7*EYv
zDPh-sX@{-wF*(^yyZ)Wqd8NcsxjSI@USHR*(ZN!kOQ&8xEq!KQn%a$`Rff+JI}YU4
z>3Vza`|!oeWY)j-Ox5<bbtR5Azt-;TdlV@o8s4A0xw3wz%Jk42qd!ZYF!1}#KWdeo
zslDQ5dDyHuY~SvkoptSLZ0OQi7C%!@oa$sw-Y;uB>%!!KmRRR}k#9ZE9-o*RRj_XD
zQ%SQ`58l=8j?O%O%De2~r@z5RX1VQGTUaye+3aPuhhGL9oAhd1T8Y^AUY$w3n`|n$
z)f`kN1vKq7kJ<E*tubew?3R4N7dgAaRvVuz{JWCT*eUm&Xj<}qU1iDO$^&XnZ+myB
zFkd7TChNkd{;}S*L2B9bRP~PJy}K`eId=J>+m)Op?*AD=qTjsa_$+D2R;<axAg`&~
z^=m0g$HLv_!>!w=3k!7$4ho4+@|4h8)Huo0hJoF3RsHQ<_J3J(>L0&<WB>8P{Er|1
zGuTx9XIS%}A$|SU^dB#l|5310=<|Hge(v(~R=LV)D)(LlI+iKAMK(O?+j{u*t^QW^
z{|qhjf7?fVc<}j;$*i>bn*+A_82t82il31aKTF>A<==Y@wno0uzU?9H-qQoN_&TNB
z7hUYLC_Jt*<ebOP=n2;HUdziLX<L}C*42_s*s*KYo9Gy~$-LigHbqXI>E>~wn?WYs
z^6mM#_p+^2_UY_VKRT^{`Ms>NT@3<R*EqBGc^&+>Wn0?)T|5u%g3NeNPt%I7Xg~b1
zqS>v>*WE2KaZUWax&FWXE*w+bA+94>U;XU4(GiIpX3Z-NoD5%1=O&%=wai<-XQS`7
z&T`AHCpLx04ovuc&RFu+jUom`&o^1lt20;EP2*h=#eKZYWxKKdj58}_8)BYJShL1G
z;lLNu$3?HBO8cABHuMKwTK8`KAI;n)BF*8O<<sX`JmY;PKGp5c8H3>RyLofclY_3*
zXx9E`;1v6te0XwwW_DG{@w$aMHNPYFo!(;>Jylx$r~f|ovnSY>xUPx3=bBiUSeaa!
zU9RmmS@neChjsqbd)gBMo)#G}%lz44^8Qc!f*TpP`c{-$dv}=pF5NLV_qlt*y4{PJ
zpB;-yPV=}sv2W|q{|tv57t|jL{&xR|#~1s}Anv!j{~2ygs9*W-%qR2Yy83H1J6_+H
zc(&o*d*|+hQF$|S*ZioneDq=J+m?-L%X1dQp4#@GLI3_ios){Xmn~I3pI~2-EvMIZ
z;O4sdJXM{$Jnp9S6)1&HbLkR_V0-vvVnN|4l{Mxfw=Qn)%GXKV(H?eLq0QTW^XZan
z*V8f{ZJ#-pW%n$T-)p7CSr}Gu=c(kbi~D{|PGZ-!t=gSiWwkQim#o&E_IA~wJ~_!{
zl_DPNLe>1ujM|HywuK%DOFg~w>K<+Rwmsp+xoa}FU6(pGLq~D*{IITP&pa8XhCZ8q
zre@M*){|u%6Ibf6g)-Pq>gwZsxNCdYqk9q0nnL(xCT>VARaR)SQ0OZT0^euQ_n+a(
zyo%}n4u;47(p<d&y)wXhL?qRkr0B;_hTA`q|H)V3|L@SI`j?_tK_e&a|D5LugGNr~
z|8gyLkOki{0=j2})|l|6Q*4Ls-`qca+dH<;sTImc8s1Md&vSfrIQdDbbo7NQWmVf|
zuZW3_zL_O9-T0Q>=@}1a#xBg6*v|0OFQiA_`DM)9bu(8xuE{j>UFw(n=IidePTn7N
z;yn9OcWE))f0oBq5@eRFxKo+sa`)k=qt|*@Wt`4bUAyz*JCoP(+fTA|Gh3}%6n#?Y
zXB&_HnKbEhH~NfsHCTJwmb+ikIs0_l>g3`q)d-#oca#@Q?BJT+c<fQ6gRI}f*MaNy
zFIzkH+Csaf%Z@KU^n&%m?x5MRf>U<Ou&P%aIC(;&_;W(x`-f}Y!#3}q^zU-e&g$L0
zW|~S@pKR9o;8^<Xgqg!4+u5<_bs~34yRp6Ho~s<(9JTXm@`g!I6|cK~auk`^sowGO
zbdFbE!h-hX31{|bD%&tIUdp&N|J&Z4>3058H@$myJMZnyPiYm~)0x+udAzOgeAI<?
z^#`j;cEz_%x)y8y+y1ZKyNI`T{&$Xj7qZen;nkz8&oIF%+!5s<4Z-s^X4^j9iSd>(
zaA|!q$&G8pf|N=A42<Wp=6`$F|DVAzTK>oH-~4}S)c@4fpO@SJ+WzM2x1oO`lM7e=
zFpt@=x&O?rU6<b}wwg2Uyk*8^R3WKSx~@L%!x~Vz;Qx32G6$Rg47_SHm%rhdk@#)S
zk-cX6XZaU>`S+edHf7ef*?cScrt2-tnALJ}pSIgfmvwtSt(-IQ({_b2yQzNfkAxLu
zhed@L9V{$0y|HaaubTAR%`BU>jd~_d6l1VBSA2V3-si)+*6h>Sqw>lhT6BBoOk4eA
zjr?nG&DnJ?j9Y$s+%VURSed)%l_0p}7IPDmI{NqJmG6g=1@3T9<JfOMd(LTr#0@;l
zgBVnp*KE6{^W^fhSJkIQZf8s{p0UpPxJ(Ww|DMN&bJw;jFp11Nw!~`NtnDuoZnZAh
zQ=Z~oZ1l6|RO1cSbDmtMj+F86JI9slw{Lwd&vrIZuGjYN)&C5wx?7qi_;UQV`FPwQ
z-(dHO+cVp^@_w(q-18<YPITJue?q#yQiLIec7^lvTSvdeKHPlO?c~4U_l=*67_U&N
z$e#YUbH#rKP>H?yKf_{3f&KgXU;l6E6L(9V|8;)4Z1rQAYtldLgCWKBvg0xzE4;oP
zikSE~K<{aE{q%L5X`Y;UGf%3|bFlI)Kk}{Y(#vC)&hZ9$+U$Hd!^>tz%`*X~-v@H?
zGdFO^EIQ-%Xm^z59#_-7hu3Xid`sn5@xfx92{AJ--IMIu$T@YEiNeb8`x6!>>)h_w
z4t>8kyI=7B-^JdO!mpTAdn#_KoM!3SR4Em(Zb|Djdpn`!1+1qY9^=-F{nz@<p8LnD
zk2%XX&W^l%*{A8+tH<YeOiD`WGn*Fsep>mC5XmyGj+qHYD;Qsb#(_o8|9Jn;^Lc0e
z8`0AL42x!gnziNs8B{(W+5e4e*MEkKzH}`9K*ekEKSj`$I4%Df-e{};n;07ox)Z0P
z{)y#7``=tA|1&HJ4<Vs?h`A$Yc`<M8qaEA3BWH02*c7=hirchn;si&*geJ?gp8pv*
zr%nIQV7Ke}KaTbFKh83gh=hZ7m!JsBf0&tB|M~U0`UhR#|1<PlV0Uya{?C9acyZLE
zv(yVG=3`avvw4ctR`bu*a_YD1FBi%$<5;lUMI?0wpT}z~36h9<b4k^<*=8%vri(4i
z_|>AhFWPmc&x$=oC+9SN)>kQ)+Y<HaR_^CjQCVWs`Cje~lbm`ocEwEzTeFjr=NGU1
zr#Qz}=+d`SuYX%Tcl`|Q4L#{OwkR{T^wTjPl+Mum!`G$!56AOHJKVo%HFZrugx9wN
z?C!e)^VQF^qzj$eEF(X2VVvV(2EK<|@5<Jl-yOP9KJ(L_o;&LAYwq5QyH}U{J37zm
zt;IRs@Qokc`d7qdP1|ta@mc2f%=E&U!A$PlTX^K&+-58AUae=O-GBW{XP%Ao`j=K=
zz07}?9}fGKV{|OYe&d?{lGO)~DLxRp<;~mKlK*h>k!#{fhmUOZU*>Kie(T+I-5oni
zKIu)_JI7U8dZycp8)i>lxG@)LFmL&H_u_xhUcs&Z8MfxsZ?=E_{VnH{zi;=~Ti1P;
zt@`MCZTI3EFE3=7&sy8Nx94}w?3wEXl_wY6*&Q)QrorQQV9cIfW!t`e|24&`=G*7k
zSF0-&{Wsgb-IH`x;Y{jjCl#GJPdh%%-N{p+dGkfpyZH+<Kl$dal#SBv{;2aS_3Y|%
zLfMn`Jtrom)F_KFN{9xCuq7~9cb|>+z5Gr$_kAh1cjmkMsauMDR$Ml7IK)(RT!)Q)
z#n+W$|IYr|yS>1Cw)R0e7519W-9`Li((=kHZry9!vDe?_n$W$gI$v&FdzWjZZQZib
zK$<;;w_{mX;-2Vc<>XU8Pi<~u3^}=~A~{^@?B93uK1t}#$ubi=@lY(fEu&|m{@ISx
z94c&126gw<W9&ZgZOSco-#+b@=GJJ5C%dLD*zUf=A$4MOvQkrB8t<nGmh637Rd#Kg
z&3$gtE3t`tcUhlVZ`3TcXtiNp1!Ibn=L=c?!Wi54t)<qy`T>{L>Mps$w{oHD(ygyd
z3R~w?{!97XR&b+i$33sg9*>%)!re}v4^Pker@XuCm~mn8nuvQx938$3++MpnhuyZ^
z-DpJ;n_m&*S%wlRyX}0N^%m*=+17OFp;BMQ6TZ!>9Yqcvlt~tPysvQ1=cuV?e|Vj$
z&Mf`Ca?4DUE&H#Wy%P3GV!J>>YvlPUXLhE$+ZGj1zP8JY;rz9)_HSb4YCRWzPTY1I
zaz3ZP;WLvLo;z~qx5Me&15dh4WBq?yzX@DoS9|p7owAFryYq^tm7O#EbZnCyf9z~`
zm9W;rUtygqUd+#(oBQwP->I3Z(>k;FCg0~g(pdiFu|=EAKL1~KfBt>Az_xUKXX4I}
zsn?oxpM*C`baqOlxwhU(-f+8^kH2`oLN4p3`$uOTsY+YCX0F)r-^%{eUU)qYthZgf
zed5KN$)C#J*+mO1J@AC-@Y>*fmRGydre_ytKa%whykhdY{Yvt-inoiqo;}<?GyHFa
zhRWyE!0C!M2P$uA+5d2QE*0`!XZoes{|s4oW4)Kp^@`to_x9c^J;{cZ^TN*xr)b{d
ze#`%9It%lXo!8dS`}gd=$7SVx-r}4U=Zl|gDC+tb<FJzNx1|4>z`9cDecw)tMP0g|
zZ7#;i(lIeII!<R2o10SFlw6GiqROY<pFi8gW_jN5Rh8b_Ri5cfPp(v3S+JesrAeXg
z?vCV+HM{%D>fS~dvD<98`KkBo{X=25)_1MT-{ZLC<*rHfX;F?cm!lTz&stxQdZQ;|
z!OzFG{sBe>8B7m9+W!guoRxImh}ZGUkA+4bE^%+pYMm{wHSLxs!&H_BhBC(sA9XIf
zWMf;s_=bDIug43TtampvxMs-JYz(O@JKn=kX`9XO^Pz3Y`OMU3=NI0{3@@KvmUbk1
z`;5;qF)WOcF-lALFU$OVys)qN!CzPXH6=UK_wBuucr`lccloWbdnun2cYYQ&c$24=
zn$wfwzg@!FL7M-O{N}&Ae^+}o>Tg-Gcu$wL=f2DP&wftsO-lDTKj)~5!-C?y4(f#r
zm%ru)M@+l-_K$tiw+XQ)IVa|qpXXU|o~5tjqSjm9XS}x$OMEJOXRR$Ccro7bVrivn
z<g;ztujp)LtS>IQF7$Vj=Hpo|X=Qpf3pNWZNY2(Xx3+cXZ+*V~3YYtW6Q=ra+xEtm
zoD}qUkiFU3ttbAhLsDALq6I<cem<Oeg5A@+^Yf#dHkPUB&+n?u*S$IO=}nG_Q3e~P
zF?Qs5thtjKI^p5=!j((20$%-!-TQ}IN#*2ZnFZ{fyNoPY-j*hWwkL7CjhQ#`VZT7;
zKBLY1cU{rR*YycMUu;w6E7JOGl30k!nIjL}RxM}GauWF(WM(7&`A4Q+_>6qLckdJO
z-yb$TGU?cjw^K?jY<eCv6lpM{cXqE{2)BQ{|EKyqRnVb|*Z*~8F}%Pwrl~#o`j)xo
zksq&h=C8{9HvNL$%$nD-SG2X-KIgJIB)AoLoZq=_6WX{S1Ns5$CiRCnAN*(dC2C^-
zN8I^8!x7jFHR^HggGE_fe)dZ1iv6CQU$fu8)hyk8V|`A|Gs6xs>-C%8`%O$0GYc^L
z*{tV0_09rWcY;UIAAdRdsCfGxrGJVaS-(V;ew&i_Zhc;<`L??yLHAGjn?@RblH4%!
z=eEro(pXp7dLNm7E5Ef=^Xu6lU;BVvAEs`;-Q8Jt?rim@2dAIvOH46#ov>J0^Kuu%
zTl<G7Hz#ELXJ`>V_@Cj6R!02~z4reMo$KOW2bF%TTPu`x{r;`M?6Sbfh@WSa4NS`R
zXWW>pddQ^bz`IY!WLR`}uFIVMw5H<Q`W2q#1>c2NFERfl-e+U1G3(^@6hjS;MJblW
zPv=b3PGK(oC*aTipW(tv&?Q*A<o~Jl|3JH^0dgY3fU8>l!|Bj@pDQ-O>4}-FOV?Db
z%4y>`lCg91HgzrwNtOA>c6B}fV+)$F6sx}xX8%`dD`>)31AdAN&QbB5{}}}SGn^<s
zRR2wM@_z=8b*mSwt3P7@N#?`+zpW{t!~Rz>V9i6=@)hBOQ`a>?j#ve)OFVqJCUHU5
zwYSBYE8TLB?%ehHiCdRh2Seo5I}8Vnm><k-dAMz!cF~UC{M=d7s>+&q!Y@R}X5N#Z
z?PJcdFYV-w=+=p$4Ll1D9cPz(+~>z&%HRFPWW$cVJ9bYx$6el;_B(gawzKjx9tzG(
z2~BA2Gk=`Vd;U~`<D<WP&mL))?4Foj&T;W{zD_Q);UUgu4TI?_EJC^WCvGpxp1t`)
z*qZI)*M+^AYL~?txpaQz?%pi0ZC7TDWZG%7kS7TmCy!a^-4>6N-ZTGqbj}3+ZP{f}
zEtSbf3jR(nu&I6g#E#uBeBwC<Q^k*bGYePAT3J3ZexGsmj1b3?(sNHdz21~dM{BL|
zxbah7J6TU(D)YLXV%xcU@Ax<L+CBUBD0AxKTO0Q%s)Xe*b91UFIZn;pW6rjc$m<0%
zk3QI&^w_W6ZBMm?POgo8@gnDPp7T1Bem03lMk#d(cX(>a?#xN=xxnt3|L8B@i!&?B
zl}<9>UUJbpU#H0B@`>aQE2FlcGZrj-9Lb+1_;$}1csZ@<`I&ic)!B_%A6;1{d88Vy
zStuy#ZF%Eh--QAr|GO4X?)zUetryBJyvHq(Kkc&Tt~QC3@}5fbaG_Nut&Y|`={f?r
z{NJPVqP*vGzP9QqH=ka3%eCUxfh);dw_aJ^8R<IfcCI-`*NdwCT*VE0ITe_f{AXxc
z?)JIlN9(h+E9Ko0E&h8?8LeJ-CpD6r_mqQnn+ijZYsH_~B}bQMe!g@6=l#qreJ__c
zor~8^PMoOI!1hVmB8jJkL3F2eMAt9<w)D&TUuO3>OuQWxuX1t8rBgMhJ0DGNpD?W^
zr)IZ+rzIETq0jF>eEYfOt=%<e*5iLXbxUS%{JXR`U#imau-%D`-&*Z5f66T9?&*Eb
zAiLzA;$_{hj>|o5nrdH5TQoU~<lVT{uMykvyy#(MqxEIxXECqB^{W?V<v(iOx5*&d
z>C$nP>4vdqdP1Gr-M2}0rKJYV%N9)yi{Ux8<SSyOK)C&5{hy4t>u-en{%5#!19ZvH
zF_fD%K%Hcf0F-koWBxw>GsRZ=-@)+z48P1S?c#d=-u}tL7x%w$?f=hkaoZHeWVer^
z^VWTe{<*=mX40MYH*FqVl6bhI!shHA*(J+k5`=qZO_KZ~n;fFgvMcx7!lk<vQ&Ofy
zo8_$LGfGy^WGS2@cx&fh!sjs+`ulu%w%BZL;<8s#eu|fE?CttB<~<FvzE;Te%&ceg
zniPkdX`u<S1xubV@Sff;{v+(zf!C*3zTE7nd&G>tJm1E5n*OKNc5f0{dY+^|jXm3S
zWyk)D&-e8E?A*O^(#xfP@2;7oSgewm`jFpxib&l|$>0~+{nPzEvL2gSZnLZQ>zUK#
z%e|%U{q4<9jmVo8DPE$Q^y$#2#*W-$J|Du?#r`OI`_A-r$C~8N?@RBRJyl_4_RQzp
zqT_k4V3}n{@c9`2*%SB{;h)-DSL3~)ySlr1?aO_xyIek>{I=w_&<Vz#jprB=9D}N!
z_gvT8W#18htSaR^OXsqvta5R_iCcF?vrf`HWRoR+Hr+1aGxvs{ce_?=p7MOSp6m3o
z{|tvDpTC^o`giIgU!EHrHQg)i&hO}{7tWonv$yD`y}5#H>a(@WUVazb_I+3D(k<Wf
zH{G&a7LqwzA(7ECc^WhGm8z?!K5hF@x6343Tg=xp==I@gRlZlujH6bqKDMb{*k;uc
z_4fr*0>|4e?DcAc;3ci`*S-F~#ogxzWz^ir-FDLc?Do?w2A@@46mK-QyI^#?z*4C<
zJow+a-y)g(^9w7>Ww!+8-JbJw?&hAFjcfXwucuu+DY`JGZt9{eEA`vy(e>NvQ=>dn
z7e&2~_<pERA@--mImLGU$^ZKI+wU=9T$%kSBCjU0bU}Be=mR&UBsa;4iRBV+%<dd+
zzVrTsv}4Zpk7*m_X0CXx?z-{ciOWxS3GKKNe?H^wlajKCKXZ5YPdlPnV9BuIb;#|5
zR_kUiy>;i-kM^J|rMy-Tze>EFXPxnA=Z@TGq5m1exHxTYhNPbGH;^mq>i;LO^Vn3|
z)2d&l*WcP69`y2g(DXOo%ifnNOPq;IpZeM5CRbV0Z|6Tt4>G*eD_#A3|IY1~OisL?
zbo5Z1@tvPKGK=<47tnIvcP#j`Nc>#4_j@-TowjBBt+Pj)9F<hU!mf9#G*0Z8xm4QA
zfYsyE?$4hS8vBaRRL$#Noi!=)Wl@&rsu<lvR=zUcd5<I>Y3n_nJAZfBoyPMzW;Kgz
z%Rfxrw))ZP+3y81t@4)4zd3D!yUDc`r=P99BUz>_reRlcKKKgH94Uq!HU9q@ME=~G
zvH47MK&_pI&mNPeH@6n19Y3{n+aw27M++Wz!#fp=GPm^e$G!L_c*kzX3x&RS4-N=M
zvCr2Dm7lxuF@v0c)ZxoEiYtw8MOJQpQ6?37_vzi48^zu}v$-zL$PgCJv6A`Aal48a
z$qRni2YSDj)r)+;zGOye*p+>EzfIjf)8<BA&5<+K(w#G-l_iDW9uv60_TZz-HP2OQ
zn-gWk%fvp${4_IXd*HKa^OB6#Nk*yZy;IaIb!Mo{;nXqhSB}~A;l`!96RVf+S^DS^
z$1QtRpTN|RU5!S64u)1R6iKMtuXwS3!HZpcCaw7#9sNoys$u`mo!OmrCq+J<RWh~~
zw+o2u2r%3_U3%`kUEQ;#J8e>z#jmN{+U~!*&HavDc%^PvPw5l4{|wW2Ea0h4K5|_u
zwq??f$&QUCvu7-4(s<{3<ct`nTFNw~Mz-Y6gGc(z6H=OYM9e-i>)3pqX}{XqnPY1w
zMW0B#{9f+CX&GOMscuQm&yqrKED$)ZFy(b*x#uH!0ba*E6I*Y;J=N76B|D$&*#1c;
za&c;8XJ1&o=_b2`<q5f~kA1H+xg8zLA2>g{|M2_|J(*%vHP3$9><~Y1*?aX{^yYV;
zuB!gNp?v00^Rxr(nJgdfMjtKA*C}??V(;^~VFVf{l@V~aTw^c$pW&p<NBzG|>-K*M
z4(;c>aVK*g?}az|%Aek?E%{xM=6m36X|FR+A0LOU)_#=9J<zfdEO&#f^N*Vx)O|ck
zIkRlqbmRXFY4L2{tEV+O{oFREE#l7PIfZ@C=UKkip1<cm!=(1b^*6NsGyG?8yA{BQ
z|K`-h<14eG!aMf3mI~c6n^$_<x-zg?G9`1t=5DPbCYF0^Pt^YDpDf+EIQ~_5o#ADd
zpj*+IPfaK4E-^6bl+wP^Uupeu&(mmCf3^7ce-=p3&-vK?mtl+jADOfN8BT1e-F!^`
z3)6-F3?GWk|1&5-drmY_v$bzmc(?sF<^8ix9eZS<TKV>^+I88*O`z*E?UO(A^DA(j
z3t>ONz<T>mpo7eR2DIyA<x$+UwOwxM%FH;WkD^z+Gj3I0&w2aQjVE>DvZix7D^G9;
zS8Z4P{>jcK&rGNEtk)y&YF@qTzD<>Rrk*owayFjW_I+O1{V7l5oE4JQ&o)WC$-TiK
zrnB&4Xz#Vfg<{={#rN+J7izn<^gyCWVPgHos@z_G%O~>}>_m;Em^*U%SC(F0bY;Qi
zFW0W<Z8<9x6d7gkwzS~mCUNNw*OS@@Z$<V=TdWp-wd?D#{flpG{kkMSecjf%kB{cP
zn(mbo^&qk4@)p*l9jgCQ!yij?usz4`-~Rl>g;~?ArtN>^?V)eHBIe-JJIB&`!!&2z
zQ}O64H@rDjLU&(gS@IdJ%olRf+xA@7H+e6RSvI{e>ZYsh(z$m$jc%%35AWHy!ZJk3
zw3WlpzGQ)rs4qha{?u?yzFB>y{9(UKC$(SO$@IPYxFqT5v(|(__1&A!IUAl-vN$eX
z`Cfy0{%@4qix;Ea&I>*lkYpvR{s~l{H02lB`bWUAq%`EdjId;2{e`z1+q9N^?0+aX
z=j%Gq@-CF)4l|e+EW(m2(Z$evRWHyNK{Z$*@7Th}wy<aY;qSNegMRz+>bWU4vr;#2
z=#Sdt%5r3RYotTq8wTdBdFWSGMU)wz&Hhk-SX|(=ijsD%>a&Rw>rS{#kn|S3$Wnb;
z_}JZ>k4^pF$8-m6x}LAQ^@qHVZ=S`q__yLscOU<jQ91r?#dZntGuGSrB##~bx8VYN
z;C}{=yy^cL?4zFl<Ik`E@zveF<;(2s%Jk~_0wTTK8~UU6mnrakSgom3+o1Aooqx#H
z=T_<Mx4hS@dri{bZ<PJFC|cr{%OunG+&h`OLN!ti-yNK2S9Y4`;!58&vg*;hc3*wp
z`n13K!OkOk9~5_GygTf>IcwAQ(+3m_4{Gle&tMO%ez=$4zcFpszU#`pOZx=sx9j)C
zxkp?m)GtewyZO9pBf9&F>Qwi%ZhhUMzqM2M{p8roLdOoSbK>rfH@eyx;m^miEcltm
z-6`6;v!<^10Ucf`a996d-PZGe<nH}v`1s2HA@8OC49{Q3{AW1$_WgebIoQ#ZXu{}s
za6yL-2${9>KZE4nLlw2GYoB~8_FNHhM7^Qmh1@&UoD_iym4qg~0!NtuMsyF!e`tGI
z|M}~>`Ul^>|7YkAH+x;Y{7#n9;Z<2av(k1aCTEIl&sSO!EFEuR_sD1Ip6?7N;?t$g
z9xc9T%Io*|xLwHg4Y~)e=v{ht=T)(%;nrY{cC%`m9pX%ELQnFfE7f8Q*q&Z%UJ!Xl
zchB{G3ZHM?i=NtNn;bB4mc=P{1)Y{jJRN3zeidx%(34qQ-miIYt-Mc^-h6uP^1)v{
zzgq0G@2XCHrrSMt=UwJ}mK^C&ubNfM%c^?gV}J84UX^+I)&BH-^N&d7-&i~Eamu9V
zjhn+iU70iEq%iaLrkXR~7w|RzLye1`AO4=vEe&^mG*>USP>$NK-Krq7eRe}#VuPQ*
z#W_C9-5L3Ms+XVCW{2{w_|Y7=afa?i#@vbPZn!ir`pot3L)}M5#aM>`%~w|2mWs7j
z2?y*B&R_haGda;XPd<I8$HSzXCrbkxp6i}endGS;+j39jV(tW+@4wD?#0D7uX!`1y
zmaxil_R1s%*^^A0zv@~amhwGxJ2uNs!JMb@8i#4ETc(7N!y%QHNo6~kC6z2W9!m7s
zi$)*KDCM>L&k(vVn>({4`=$E4pBGl2ta_=_dUblzTUYDwEXCMUtK71kzQ1|B`gPUP
zYs=Z@7bdPfqPsp{$;eUQHxt98xu>_;f9dRcdZls_pJ(nG#-j6nAC7)LC}Y*%A?7*v
zam4ehUnOF!RwVVTSJ3+HQLwh@^fZPQYFjZAZk$D)u>0PtDZ73L$5u@D-?3$1#E~SI
zv@MOd6f7f7d`=FYyvz9e9J6O%x)`4SXFyN)YwCq6vJU%Se)DeOj;nDlS4-Y-e$8Gv
z;n^p_Q#P&sagY1<X75117m}RbtBRcF<#5kj_mEv%E-Q#{7t6XHuGMu`<dXYgGqwn~
zXxW{wd#<$-=qX*7`(@veoAW>{z?0|M_n>^Un`@7}P}`NMbo$h~)y#U5-&T80loNT_
z8tl)XT~;S|@onyxm;dgRcxQ7j*c9!VtL)ZN8Sbf|ev<XJnowl3#haN7Z**z`7rzpp
zwRDa7h00mEw<7PPg&df8=q)q*ZnJ}PgkGKQ>DpPmI&)jtcXRQo)+GW_JG?tpXND#w
zi8MT!qp5hIp?;68Yti>vZp)2-^adSrl8@MUW$o-U{o<Njx2C)N+$3-Ij_vPaojs3L
z!mY|ym&&bNxvhU?)SZ1Bwoh9rdUX4(MS<xutQU-Jbo^9;)*XJDbodz;2YY1cx)<N9
zN~C(9txnEQw!5$PEW5?y$sKdOYwGL@LWWmD>ji&woj*Lw_v)2P2d)R+@-NQM_{?$d
z`Kg}WTF)mpSSrY*o1VV&;+{fpNvxa6zOD+TJzW)F7N%|IeeNyOb&0cm@{W$rivB+{
z?(2ojTE4a-IAGg{tKTN)E<Cw%>HT)yEh~a79~QD);M}%(%QBnZOAEt7&jrj~eayku
z2x<K;&)?$6%^$wCSFgUm?{u`stnh;j+pM&nG(^l{Fg~deD7P_PWq0e-&aD{>CTWH}
z5&D;Hv|QF~BbQ*Kb*BQK<@!gbrF;Dk?t0ofr!MvCwfTiSnmc&UUEB~j`M^o#wZ*^Q
zHCL~TyXUPoeb=>5x)Qc~54+uQtyI~(xc7+cio-S&s+g`YUWtCa%l7__e`i<SIQ#AG
ze}<G#?*#W<-2DE{!Jpf{A1l1Kq(AI(+EuknkFMy-2eg`>&e*IuRlG0Kc!FK(lfK8-
zc2@7_i`{!{Z=q;UUG2Nw%kC^`Sdgjv(5$u7@|?(VL$1o#jh~C-JwCi!o&PAp_2!j%
zmo5kIxuT>NotR<s*z9hD=G^(h587`nc(2&OCBeMlicS22m$%~9*WH@C<mHlu<`WNE
z86P{WpeVhgEFpxsXP(xRUHDJ1zJK`Eoq2NCOjeY<yd-*2FGuIm?nyWQY)j#m3EQ-Q
zFHy1JSdHOr!B<jiDjs`(l-s&I?)Z|M{@htofelOiv-;wN^17bhvAo6H(4_o*mhYJb
z?F_ODuWq@z-<$1<F6-mnO3^c?pGgbhJD^wO5f-MrA)!jDxAd;;mlt0}ujWJ@i~SdS
zVu!Qz8=kXm=lGZ`?HZ#mT-RS&5f=UahsXAp6MX+JUHkH~>_h(f+2S|L+s=nVSA(9l
zEjsk>`Vq71{L9=c)IU1iz3uR>`E1CgQ}1G)u=5Iw@@{_?`qc3bgEjZuJkeS`Yk9q|
zU)9-!Wg3=G5-&dEasGrjgMdNg;~=*;UH>GnF1)gE-}Y^nRW85%a=Ud)o4BK-;ZH-4
z<)@FoJ9d+SqmqHA)iSVsX~dmOtADM!f9m{i{b$%ZHDp85q&qRXmt1ZanR7gztRl42
ziCJb{iM-2IJ>5UC`MKqPXPYfA<6Zk8_Nl<FgOa6Oubi3s*p*qBo2(k#Qy+Kauh}Z=
zrY*@fKXGNZWqKyN!Ia*8m-Zx|`uk{`H{(-gwfdH?!j8PBSmtRwb$InK)|uhd!6~2b
z7_i74VU8;=UYs?{zxhvYdR0!@tLWU48*kp$w3JV}C7p3af5vZ-eJ2iB9J_Snt#bYn
z@>g|Y+aQFxx}6~+pZlf$8qZZG##@hUTJlM8_mo4Qlvb^tQC^wa;BxTxgi!wgUQhA%
zEhqGI^A(#so^Pw3-Z`z3;q2k}(+lpl@!ZHUP!KTe;X1tIquNHcjVtB#j{i0~9=hf7
zx3|S6_o{C9Jhu)`_TO!h`}pah<YK`et6o&>yX{-vR2{v0XRctvra3yU$`ij!FaEt!
z`nzkCDZ^?*NxR59j5h*f<a!_Ji)LN>CAHz=!ugSx`4;pkO}%zCz;(Cw4oUBs)0qw5
zJbyM>=KAg*%`3d~(+iis{3Kp0cRSQ<;>+*iYYWo&T$nr>1m@p;T;0ZASN3O#0KW@T
z3!GVYkN%Q<8`V}^ICov>)Z`Ow?}E8cbgf#Kc=zcvMq&0m$52}b)A?&FQao9AW!_5d
zy^^W($(!}+oom0(oPXxQ(;;7ybMr2@rrW9Kj0~pFuKZ_sD7fpY&Yt;}dFAn$1$noh
zoz+=2$#FM(UY=_2_U-a7Ef{ptCF&I0tfOn~55?zP+4E)l?0~)dH(g#n|F4px(vmid
z##>S4lS-d+TzkM%vxK2^R(wmzYgxHNrykZ_Hr={(>gMy){EgqN-KTa-y2nzt@8`i2
zt0z}f`^<Y0Ya_&Y^ws_Mo==>guW?eiugzz(am)I<%9iYEJF4$GojzJMy>%=1dajeJ
zIZIA|R-3I7XdLac>9$HkcT=;*!OOO_Y`mV!lwu+?H@K#M)8&r3c30d>G5A!Y&YeAc
z9bU`Q8)rUdpL=GV(YY;*7v$M)-HG$r-fOwJ>+Sm-yR)^nyAP@?_<7)G&hAY|Zy2id
zTV7!e{2Vj+P*liDu4z}MKJuMcQnmDy*Xtb{_?1q`IdGd@IP&&RVb83?ANA&^FU}~6
z%2>p4BTFh~<I5&T8AHRpJ#1X7e6pVU6>vR`Y<i~`F+X_!#*b5%{%7dO&B@WtHSu*y
z`Zm2N=1;fk$|A>3jsvpW)8`*yUa<M%p5B6cQ<}7+qg^*$Ui(l&;8?*W83u+sVW!+C
z0yz|V->@C6+~2%)TJsSD-6v6Ng0nB$Y&u?<SjZK9SNo(!clClu>668B5BsN`b$41=
z_(wN2sl=ZBVCqBuH*3QlX<JT?G>mprjrg-ujmf20?WK|s!;-v&vlB!t1Najb?WnHi
z<qp|+W$S+ip(w}7xlYgc^`04<WNq}h_EE{DcxT_46$f)advBIY44yVm<m$V;H%H&M
zndG`1I(M&rQ}nBH#jyM5ca#g}3VIof1m0e7yESG*&|_&(efeo;?%MT=yFQlQZ!XE+
z&v$%TwC$|Bn<_WlbmyN_v!iBtz|U!}$G)&9@iE-FyKM5m_D6S%eY(5Dy6y*ryqV;4
zS*6k4VaWk`iIbHoDs%5JfR<jPZCXb=01ivb4BJM`nEwnYO9n$Ppe^!dC;=^gBnB7N
ziCtE>S|?SJ#NDZPQQT)sL2lmD?KwZSEHiF;%6vIzRmHUvy`xk7?R~*~b{jq2eD%$<
zJhoJ{d=QXjKApF=r-`4XN5JtMhjLfnzb`Lu)oo1Fy?g)0TGN(oUEaMx-X(ozTe@=m
z%RhT{KC@12Jek&Oyx~!UmH!XtlKnq_UAO;GUHzZo_=^7wE#}_;8RoAo{?EX^egB`T
zo%Z}^s~=gKa96+n>vfN9`_(-+6n9NiE989=cx2rZl_iTF<XNX!SnvDXEW2*;x}y(Y
zOaG2_`t>>Ns*PspihXZ9cfAz4bM)yEwxb89wp|I_-Fv&=gz*M?KPi^Au#RQdv}ccl
z4CA9>UcQ>}(>r^$@5)u)Gi?r~Pi0rFS%0^w?135EpY2Fj5T?Ek%>3?j>eRnS?}SSW
zH{E};-Pqy0LhpUnMX46I`U?CkWIsktoxk?w{M%AC-@MHy8s|>p{Pylsnj62&>>~5r
z(y&_<76%{9VmQ9z!@c%Q+a<>LvpZGqER$gW_VnYuhf+=!)BC4Ne17@5tM9zihj$AL
zOY<{VWgDH&`mGjvef_@RN%qgzD;Mp0l9J~hx9ULf_G@|SP4ACRuc|xw_K{R-Yx^9&
zyvVDm{sufX*BKQ~^YANISjSwol{+8zVcpVYcVA7b%8HIzu<6RXwfS*jvmQlyA2;k>
z7`x!S&g!jx?6(~4b&?r`BFtM#^*5XDecyFWdhI;lBj0CjG1&Jf=g7K)c1aF#bx97A
zDxoL0yyuC2)$BJp@FT<gs$=I&Yh8{?Z!=qbN(Jc<lyh>;d>ifweQ=SQ`?WhGTrgtJ
z!L*NOc_ywYy1n|urA=?sdlYjQOiK+7h}Yh^JS!@1`ttY}R*R0CEi`@mS#OflmhFYU
zg*u%ZB_3X!cr5yzo_u9&{}!gF``f-)?|k>L>32+}uByN}`|bK|$2B%Fp4szf-SYnU
zn5*U+KCG!SUAA6r<C>+dkCYD@zn=bjZ)ACMvz`O@G?o6Tp))s#OvwBd`t*CJO{nhv
z4pUuQw&hYY)+TRHRew`<-|(|i@w~$8GJICgXJ1_V{*Uj&{rnM8FSnWh3Y)vgnfFrc
zeb3xo&$2@$Se4U$CQRMie~Zm7<pJ}Ot0nh&UtAaa_Psn#J@cL5J&m`evVKpy76u&Y
znA^dyi)T)$Xq+wop-n2cK4rxzbSnFAj!}L!{o|>#J0vb%oa4R!`A^~Ad*xiWr(Ctx
z-Y<|Pr+DFQ+`D79<1c^t{W{k5+4k&?yI0?wd&+gO_G`uyiQfyqO`K4u+Au4+S9U9>
za;?+nBYCCK6&IFxo0tW)aJ5X{{9VASwa@>g0{2udM%8_jAL=GYY!-ZFr(EXy?8@mC
zS)45A!rvb?-oSU;=1gV&XJyO7eD0C<9bdYuyMI^eFaB)ur1L#f)BW^F&Ra2!tr9^;
z=I`2XoLISz|KP8^SKFpPTrFWb|84Y>Ez#9~g%}yCRr_xCYad?H<kDwmwD0aE!PZl)
z8z1bhURmS2_SWlJG9T{7XNGNhWuKX$+7~GmJ@@pd-D3Sbfy^l_9oos<JD4wN&;L06
zPs7{&Z?u>FXLy-os^0W`*6RcN<aX?s=DB>j&$ddHiQUE<J3UqAd8*I3QfKs^VS?=T
zzpW+r|LV438L~Tmb&K%IS7y^cWNp7ydUZ|Eq4gPx){~qi6I?d#crEnhc-4(X4VM2I
zexMvS@umI{@_7}o;U$#wFE0LPKs&JlJi>`_0EYV?)FUe(gHR|3V90;yM?OU3^#ZCo
zsrzcl->l<-7v4Vl*tRL?-`BNIby=r5byqGu^`Bw!*Sk`E#Ru&JS7P|4AAK1LXdI3v
z&c0Gq5%nv*_36jFP4Btich0(ZWJ>PRqWv%K$gVl8yis{?$&>(gbMw~q>jG5%>0V29
zc=a&u-qD8Cgj1E<UP&<VCo!(H$8rn^0Yg18Jd8d1Lf`*UEMNKZx|#Sqz3VDlcXd9T
zX|vmKr-Z;^rTfYX^QK-2MA=FM-%Ults_m9pYIF5(mEV5;*1Rz8^ylqoP2%E?y*_3$
z<A;pwp61E3UO&v0H0}5rnEr33$a)k1XFDV2UY&YMt!&xfH_;4vImW3C%CkS}EnOM!
zTgc;`Ve*@|+-J*F3G-PIXS2;`teunmy=yjCU+eb&42&C>R%{QrQsbo?cFlcr_3hba
zu9x#fqC0%LpKZPP_i|fC!wm+7Q*55jJD8VjzG(8A|IL4f&Cx&WZ+>e#b^Uqr(?eyc
zl{WtwR{8n)pT0hMR{ld?-nVac|D9Ain4LFmwN#APY84HGji;CyjTk3x^F915|Gink
z!;fvtGnZ$5-!(^obIq5Z>;2|kyBu{=+Rf<Vn*N=7BEnlv%ZbP?&lKXx$f|1ZH1QSl
zd}bB;^>XYj=e(0L(@xyWc`2-|naTCQ%(<!R@A>J^7+z_tlij*E>3+~;|IO`Qze{f2
zitsH+sJQr_;Ze-yEk~V&B19Q9^Fl+-`S<Y}hg~zZm&iEgy+V1b*sM9`W-o;wW$M05
zZaHCBqvt2-$P*wQv+eBx<{gXnyt{pL*OWTZrf;Y2`)+IY`|xz#`r@2zZ?}b(O!#S-
zc%X%mkzvArhMK}pe{M~eQ@N&a%~bj6jsFa35wEt*s=K=`ZT9)-!a2{gax%ZC^X{qH
z;ggrZcc@Ea0oQjiv+u>Xd~K?qY?*SF@s8VZjf<0y$4|Xc{Q7m5?wj1V>bqxgeDf^V
zm{q)E?mNL`_IdNQG#+2RZhCaz&Q&iK9}}N0Zg^KE>gd+BOR{s7e=<e9og&+KV~1SP
zwj*4TQ$M(U5PQ14^Q+;)(<@?br{<b+ynRxsleWdYVE;7kqay89o3`xW{ydY%H6-=e
z1->R-VZY{x>0y2MbHD8VetK_T`5Lb~=`tNkvi9wFp41BaO*;4L!tF=gD}6pG?Pk~{
zBwdy8@9lPmpE0sO>-TuB%R3x!ZT+9nhpRi+>nd;AbMf7}Wm_5~#jPJ`v2-iCYpFQM
z@W^;LFgXZsS-`VnkL@z&#BYi${enCCUe1bqGRb|KdANI}WcNl^Vd>6?PG2Ne>VNUI
z4%xMR=br7K)3zO-a{Ff4qll+3IL@Evai9P0@j`_cfexbYb8^3Oh)J*bbK+XWGv-2x
zin}S!#}{kOuPHtn-tTgG;pHvAIo^J|{qkP?O@^|&{L{?VNn7uG7xMYDW<rrf^FmjK
zqUQ&<Z5N-c``9n%(eCQo{F~$b^FDZL*cI4C>%G}n#^b4cu9PvP=DNy<X;ZbFmTpz8
zn4CUWZe`J=UGH?5Pi$hJz;t$tp>?@Tvf6fy1w58}6c?U(@OP5Oq8lr&UHdL{IA3X1
zE8{~q!5z0m3r-cS5_!U)b!_&svwSO8W|ikk$HeYBF5%?SchBZ$<{X~6XO$=SG;79e
z2*?iVV$h!d;rpL<o5=qRi4p%9zI0s!ZAu#Og@RB1=q__y^~dDH5pki|MS3$c9^ATn
zI`8JEkfMv5CRx6mQ}RW$7;WJH@a5&R{eJ{LjE&Mvak-qcW?ddblHl4uOC!4*PqTL3
zb67n0#2lG~%NzE5)X2;&O{^8URlDTYn%4=hb)G)!$mw(z3lG%3w@Q&+KCRs*VF$aX
zd8<iu3cu~Y%|hZKJpUB-21L%#>PveS(ZF8huo7e7e7*U+f6{;LL$>eQcXLVP-51}r
zO{CtQJ>#(VvC1ayl}v^KtJoMddS<d%SiH5nnQ_l}Uw6<oy|-IA-Y5E+UDBS;mR&63
z+Ob_SQed~AlvB$J-p~5exEgXYtn#J`PWtY<>&kNJr`z(kW|<qWNSUy>Vbe~AHYan&
z8xJ0QUbyVlv{_qs$3)spa*$bd;-Zz#9Oj+e46+;w?J+Cg_!d<8Za%8p-TnIQuK69N
z(VCB<r@2Iw$L+fks+^tQ8+}H8kEDV@jK<;3yR6Eaw!HYyu;ty`bxI%hE<M&RetU^?
zam{IMBc*r$89c08cL)l+S~%6I;f8|T$&klab=7vwx}`qxY1`vBms&edc-kz~lX%RK
zlWN^BsgSNNdi0f1oXS7#Jyugc9cEjdo)O>|W}O}GZMLJZC+DZ+$(lb6#+ptMbN<Rj
zSN8_K{qi=g`mWXcBkLJ=wtd++P5({L+s^?_x4jyqRW~(EipX2Q_vrXhDZizavTNsD
zKC3cQE9_EiYk|k)y1V<L6W-LktzDv-#G4b|`y<)E@32eu>gwOS!}GaceDYMeK6w*s
z`HT}wp6;2VwY%o1{7#;8JD%G$K3KhV&&6eir&Tt(7o3>H{cLY*+g0_GI}+qVPAW`0
z$tUa1rNO*p&EKR;r#_uk-oJC+JwYwjiu{zVsyE(*-j~+2)M1GE<nh>IE!UHON=GyP
ziFJ9u?$mwz@X8xG&#<QtIQD0CMr_vRVOZnm`Jmx2t0RM$@`rhowa;`HKVnF#?cE)<
zKfv$8eNCf>Z4yOB#uKjys9^Rpf4|h%-{Y+|uT=Ym!sH{1?(XS4C9nQl!y}pfN60pR
z35B@_+75F(z4CQ6Ki}=FX+oZ*wp-sVT)M>EXqr1)WzyFBpPAl2JDMx@$@9o2F`MZO
zvJ4;QO}fs{u=69^7uO=ct##r&9uoQHEPs|O$n+Wa^h~M<c5Qv=ng4Z4<@^+{dkTA5
zZ)fJ{zu##c+Q**YpY{Cf`t1=hcQeCoom;YqyOxb*r*YmC@qLrbCrsj+p2}RP<($kS
zcr<)xAIBcwrMF}6$9CshA7#3B;e5TGL#_E)j&t!w!rBS>It5SJPaXAOceo|q9{4`=
zt8Xf67yGV>Utd4<a16R{JhQAx{F$;P!%7Pt&c4GQAFeI`mcJ=0>ha%I7xfeFu8m(l
zn>(3j_fpAY;mWJt#We0n*OzL&*81f3OYy2H;<Mg<ymITFN9a9?b*Uk4pHl)3wiFz3
zJn?Dj^!{o6d>+RS+w-J<O4&YjqVDX%*t6m{(sEKge@ZUu{W$-jlY@2x<0bT7c<B2*
z%uC`UPv)!M+p&8?;IZvx$IMwoOL-MzPaQBgVWChM>ng$sx^7H*>3@dv*LMDAXuf^_
zpDje&&6C->_jW!x-KaD-@9mM!i901sT0|44+LWlX$Ov8ubP#=$v*_}h$6H&US6sF*
zKKI%3r26!th_CM|US8VxC-pyrf_46Hu9y3NMe~-3p8s+BpF`RGZ=#p$zig8te!Vql
z4L178DeIcBEa@h^4!lci-qO{XyG(c8$(q%=w1?-RnD@$Qs=7@D+ycf8ezv^~F^e`l
zxURpIyQ6LX!q{%72V3v{{H-<RoODi#WO?7I7Yz^Q-niv=<b!i*zV6;5foEA(1bI9O
zIQ7bnL*av?Oj3jP@l`j@uJT>xTr9JFg4)kT{m%@Vd-9KScqD|FaWi<FU>Dcg+uJ&C
zX1eU$)+J)oHa<@=a8q_Ysq)aBS!ME%tDuSuZT(WXBibt12A#Mc@t*syg#D^W|J<_i
zT$uLG<UUVjt-yPx34I3^6&;wP)z`qNVkdW5_p9@Y<19_JZ<Q9#a~8?FdFQ2IZpZWD
z)Txfv_tl@}JiPll{M)7M{Wre_C_An?&a&Mw(zD=H+a>YOaS|sgXBX?#Yf1zy`Ot21
z>vQN;8~2Ad*XWsCELWSkLS;I?NSg__?F#jisxfvU%+dyilMZYaIm}QpZJ*f1HGe+J
z&inDKbAiEm?XyxY_p3B6o{V^G!LW#7iB?ad8;6bll7q}gpPV=QnK*OF&fU{0xm_N4
z9G~$fI%~%raqFV!{u$5b|7U2q_o<#gYt|OA4en1WvhGJVsjGfeS!pej#BpcwslWs5
z>sK7@^*=J}h*a<G$m2;lIbWk~jZ$XDpRp_4uB)}d;(?!tqO9B7<L?BxXI*buYZ`r8
zlg037{jK`^J$IGc%EZ<)Z4x}SYraMk*W<JY<)s&z58q1NdbIV3fybm9Dl3_FJ{74d
zoZSEH@58i!Bl{jj<h?$dc>BlXi1`th{ii4Yomso;?#th0J7&o%=CKveUB7q1-8p&(
zKRx`sGyBCq#gA&6muGPA_u9Pg>XvU;w*Q^y`MA$ifOmGy5!D%IcUvB6+|K{~1l!{u
z&d$}<-u0V2HbmWCy6V_;p;afjcyx*y4)`>r<W4U5Is5n7*^@G6mF&;FpFe-g-J{j|
z=kA+atgMz^FYzh)K|$FkKEKNPAHMI^KYUxc+A*7@&b@8z*BMGh@j_mcH@YeGp0Zgg
z!%+3BCt?RNa~KR|B7v?9sV5)4H448n_rZj@u8$`@|Nbdqm)0sP-W$CKLJq54o)SD~
zg#sv~_U;ML5wdbG(CeI4shX+E%=O85qmk&L$CcJ)YK9vNPtX4Ab?fnw-fG>YUpODx
z+TFV)nULeOF4t1B$Y_znVTL4E{XfxR&t^XIO{#UfxL$dqnE9-=&t`Htt$)U^az}LP
zj5$RLS^<2^%N~AbV0$7bcUgCxj(QWPQmw6O-xZZlti37<n{w|q&DVP9p;)%=f`Q@6
zxccHpuTSsi%eKp%+jA*%mg<#VJ;5$fl6j&}JG6N3o2af`XC%$C+WpQ3DRH8^8=rS`
znrgol_PcD_edFEbz>l(T*Swp!DNSPDGk<-a_fyig-w1h9=@Y!|vA_5Al6sLpenNA@
zj(xiJ+<*V&hZ}x7c`P%T#51j5C2vCKZRNI3Ws8R^n6GH8vFA8%a!<BbeVXUIYmc6t
z@YNQp6yv-nTCTo&YLA%hNp<F>c>(Z6@G<`x+V?-Pe02Ud*YW=hOTxBZ2uC}#m7zo=
z)HXb*-Tl%#Q|YM_Zr@g)Y3RV|ar|CQ`h?Zf6jCPeF<P)aMLAgr6w&Bd^!yK$159FB
z(KpoxusdQKHpe2yuK!T_b*=rw^{vl#O+MYb<+p_6Ex$O|J`<U$%^Kg%+k|`aoVF5o
zRA9VmS8<asv}>LOb59??lYyHf+YamepDK2O{~313|C<sWQdM>5b=0-_simv3Jaf*k
zGg--c`$($b{bLhXrYbfBRNQi8$US%Il!Nt=ecLAo&N`TK_KKmqN#~Y7E1n*j^X17g
z&_ddk$}>|dC%QBo`7K?NvtaJReL-##iS5eDma>k_r`~MM4SE&r>-8)rD)vXc`}Bz2
zUH)1n?%8wC%ytNgJ-hS1_9oM!{bpQm;yo*CA4QscUK#JmGEY_P?GwL%pY}JMoF(iJ
zE!|XckmVhVnFK@G^jS-n_8wik=e**)m*0-c1lsgeGHm4H3}KxjZV`IN$jvooz50y%
zTMxYwE57f$Ix;g(q3yV^r=lA7k}igTNh&!BvIn~-EZr{3l3}-4C_3x)!ffHYFFgOw
zeHN#-;JcIVcb)AOJJQm8H?SnP$wgQnyHqZ~?=q<(u_7ok*?s0Wmo*2(bC+(|w>)d(
zfj69QgTkk`Z`yJ7i{}2V>a#tYk1Ufldh*K1%BwfwY@=rV{j|qbyhrzU86MOQGx2o}
z-tqDLRMR)y1*Y6vc5b(tbIB(+<dovsdFS<54>Y#yly1A{Ih}{`rAWB>1CiPP1Y*UW
zJ^S|V)3bM{xI35anzCCgV|wEa1_O)NCoPlCRCzIISuSt8$$Va?P_fkE+(GbaqIZxU
zhxX(j-J*+sL}}`;Q`x?~J$OT<YV`C5rN66Glg_L$VA^P@-o(r!%EC}8cxKa{6N?;@
zYI}E?fg731JO+m+PMp)XpwU0*QgFz$%jb8_iN1Ymv+1T>PUFSe$0FX|{j_T}@0y)2
zZnujbzfVMjx$7-o8&OeqJ7mKo@0D-Ym-6Z=?wqp8!uYi4y8jF_#OuwpGqz9iQ=PE!
z$qt4uj7D1zA7Gh%QS_wYh8RPI#EngL!4vr0C6Bpzs<(-^s!lTjwKvZ&mfecxepR+w
zhVQ_<tIvO3zr98;Z_Dc3^q@f2ea%cUGq-zj-}jV0;mPW~sd2|t#f?oIk5=C~&Jw3~
z>Fv7r>yB=l`=~KHBYppL1-seLTGI7ra!%b~KFy-2`DxM;<}KT6^$rJL*9-c5`uKFa
zg?k=J#JKk!J#lFJw2ALx?`SPf$Up6#TD&A{*V$<+^Gj7WpIyeOb9Kt1*_D!!bB!32
zybkXW@_J|y`=7yFzt`!t)2G}o-Fv;b&zAjom7A}k^`0l(Xq9s1CXIwc7D)<ED!oo0
zKkeSGlKgOfoAFPh=u;=Ao!znSS@#=bGovMcdM>*CIR9axg6IK;FJ7QcZXo=exc1(T
zy?*zPbgn<K?c%GT$i1)calXw{JW}wtb&){p)b{hw8y<Si_;j%ITmj>)khF@hhq|{S
zj=bx6DVex)st1q5D+iqg^KQ4Vt(<$V_i@ODH+Dy^U+~y;=F@^5na}T)RR)Pp`<xMa
zTfuPV6X&U_oJq<%)fyjVyi48Hl<V2^z9w(6)ntK>(l2JIbb7z-y>-KD)#=TdiPM}<
zFnr-iZ+pspP^V}?nbV1b4XH_MEZ#{7xF>O})b78yh5PdZO_N3Gm-UwJ-Z|CoqRk{v
zDcj4ZcHfhnI<re~lIp8U^$B_2OI~e@6Kpzn@16JR*V!HE>3xx+%UpIu${Acb^>&)W
z$@a<Y7OLS3*gah<|IY32%ro`XiryU?nk-&!d|KxEsfkCWV@`Z*%Sb<M(4TPQq?Ujn
zV~=>&@+BE^`a7oGx*oUt$}GmJNpUvfzImIHxEtO}FFowJaj8K~V^UzNlIdv%#uuIS
z=_+BHj+ZkZFYn)Mb%JBIR!oll(N9fx%2>Xv7Jc^1uKiKq>K}2rY22?n*Zf&N?dkf^
zg{^i6E?QYt&bK-CaPIcjoYnpF<u$%wKOm9P2Kf0aU-w$Of138~an9xRliPcxB9|RA
z&*@|=KcFyo!God#ZTsK;u~+S4jlKV!Yx$&K8o(F6YD%MY<q4TiDYe)G4<>{#l!(fF
zGBNvfYQjnDMPd<)wIol-m*gp=e0kFN$~F1m!>!dF>rJzN@AY~s<H3C5;_b!E6U11p
zIl_KU*-_4-f6lAP9JHERy|dK*$DjSpuDw<6%S3lh>|Z%8<6Enxy+XGo!~28U;U@R_
zGNpVE$3{gQ)0gG)tkg8R<FS*S-+0m+3klXfrp60gR~Esy9HDJUn|c9bY03ib>2`9L
z^^TsO$<p=RoayD$u1e(zUdj>8i&wKbZ*-cwBqc?DPjOs5$BWNPXZ<WMnC&uAY0|A<
z74kwxTV~IdF`kwhrrN3UsZ!;t^?IQ=$G>a0S@7TZx?9)IX5}->eW!QKtNZZzKKpX+
zgU?mx?OwUROX}Dc$6Ri2mBQQJnMQ`8Jb{;<Jky*x)%mBF=+wwf#nMcS#X%q1+E?9P
zyXV^^SBC9k%dEXSbEiIJXq4ud>8!xo5OzX(w#3PEaho4ne)ShPUi>XuFi-F8x_?)n
zpW5VhVVC)@9*KKyf^R-=*Ji2Rp;&O^Tb=#Ybv3s2tJlu^@t<L%`c*~!WigJjn-^)T
z=qk_MF1>yJOtV5si^IITrr%S&zGZc9<hr+CZYo^bQn)Hc#r3eY;m#u($9s}g&b09F
zs`H;ynIPo;(DHou+pU(mIZ17o-bJr?r!+6D{Il{zE)I#DcD2}ZC+_dbI4pX)X1CCf
zc+bgx8#hLzH%W7}h@H(X*D-RJV95C_*gRD+Tw#vTDnAdloxkhFvJM^l;mto=$vd5Q
z?~`4jM|)D=seLMZ>Qin%{nO6Fyax~cS(0aX=g0oYjeXB9z10=_Xxg~!xb50G-@U}&
zWEVb@5O|+-r+2}h+3jZzawhOK6BB@EtK&JN_yx0e?R{f-Qupkea)CD!4`@wr>Qapp
zJ+&wA^bWI2<$9c^^NSz-^*VewEb8d7`SRz!8+hhhZC$)uVZw0@p<*ffsgu_59i3in
z5HVwN^hdG1OJlOSntiA7%DcA*?JDcMx;*FnK9krZ3W@wY-Z}3!r9WkO3+gJLuIJC3
z6cgw7!Q*^oA?uX~=hd!F6KXT(-p%DcZRP>#Z9UILRjSnHir?H8{rJuGqI*X_Z$E9a
zFYVjwb2Tq5Y<TZ5Hum}4e-(CJP9^(huKogl!I$5@T{z90BwCz#;`GF+LTnPuLYnoD
zZf!R?FO)6(%B;6iwqxU-tNA7;f<)^LD%BpWS##v^M8=?oQtR#fI~Yt%{<6N)F+K5h
z#{&D?L7VT~I%sUAB%$1}U^2(qsr{C>cHHf|X(fceqf=2Ef7I&O;)lFt)}9HQ_g&uN
zJyU<VOP!vWr_$epd>k>iV;;_)IHQmM%+`gE<i)aX*)6&z_TlfkSC{>}-i2(xv`)|N
z)|(W$D2bC|KMiG!-~ay0cX$GC_j#V9yfbnYD$OUn;$3<8xzC$<#lp|lt8UZj`n2+Z
zV$Gq0<y=>GZ4TQJ>n2_C^oqjvY0~vZVXlX#BrRzu;C7qyRwcRdicIy{vS0U)PI!?q
zttDnpkh`%NPhswa6HCog=gg=Jo;XoiV2#3L^(K`oOE0X84%yrHu5jgjr4ti3C5An7
zJtleMfvAP#!?N|(MGmGWzQ(`h-J4D>`}{2SlE2;EeI@6PKAD{7clX?x+wRO3GK^86
zv#wwmZIR1$NA#}37RC$V_KW{B9GM<g&o}?a*Nl1Z{gSV^KTGl`u;3P~IP~}8Cf5M|
zX=kdq&R;V*|JK{Y<JoW9D?&?;Zh2TP@g#WSF-I-8zy^g))_QKm4pJf^1(LJwsqN^q
zc&@?IDLp+jr-)gAQ}TV|e8(U}cLm-VD5|r#tajDE{b9GqmaBoLMxSoSJ#pOr=5o)8
zGCPK(9jg9kw-nB~W>sT7OXA6n9sR!7^#5ICocMl9|67ira~52FPh%RNEuX_CljrjO
zvj%%*VQqe<?GodYo4j}W81OE6U(l;4Q}Q#g-)`QH)uPX;+7IV?{e8H7$DS>_?b9<-
zuIZIaZwcE_9W1qwT_Yvm;@^jwb9d68nX7&1+g@K=USG{N^;vA}o<&#gdaIN@UAVnh
zFZ7VI<l;~A8Pa^J78ChZnD?|*<OS>zI<Cc@qSGV67N&K$?_ncLnL^j3o%Q@b0!{Yw
zW$jX#HqC6?_ww?b`N^&c7rowuY%-}X*D~;3V)am@$U@{RKiAQPe@s5=O<lTXI)8C$
z$w`^A3CGU8<qTM;(95XKyit8w6$9g~FuVP{dookk#KqRmyY4#8`)B{O_#*Dg<h(f_
zRCEv6mrFd`Y5ya<ICf{{;>$S#(f7D5bVE+ein+9Q*RgLuLk{xtOnSnixWwYTPWG$&
z{9CpEvc0;d?JF7dP%lVUb!q;l2$P9Nx^>)7J-xWNT%y-<$K+=+(;2>;>hb4}vE6lA
za;{+PV;*y@jf$SK4yqB%_cOn&<9mIu>d5tVUEkD>>2I@1T~=^CK4VYY%Y{?T5|x$A
zJNx3bZr;9{?R>aSs8;;Qb*Y7yzpMy*?%&6j9d!F)=`^=b*NgsKd{c4RGXARulU8de
z!y8bEL<m3s!wEV+?r{7!uC4zWE_%nZ7L)~_&Ha#lc$2HngylE39NjThVrAdm9&O`1
znFWI4ss~vebSL)o{56k^&R(`l>gk<Xvg<p}<W^P|95UHvm2pGzHp9_pn{v}m6rH#|
zb9N!ams8p&-)+75uH>)T!><<d9y@klopCoNyXfVI&AQKSFzoCRsxM2qEmt;`<v#<%
zv1c<gS7uu+nYL@*)|KvBKZ;JA{uU{9r*={Nmc?g8R!uGJV+>$Cs68cif$US!(?85U
zhg@B>`)X<6Q=faW%Wpoazq9zzjybEIJZwGeFKPKS$tNXo_6nqtN$vR`XWvn8zYulL
zKiy<jYmZX}2Vdj6M`6bt*_+%r6rQsP9%U#Ioxd_ubCq}I^E>Bs-#(3;b<?b6=EbRx
zb;{oTj16tO7V{<daMz=|c_qJl-6BeTJtzBI&(X<Mn)dcdNLO<9v-UflQ?}20Aj$pa
zaoU}bDz$|x?^HZLHR~Je4yo2#F}LUXWvZF2N)>o^K7BgV1BXK~y@&HvPPZ|<*W2pt
zZQZ(k<`c+P7>jvs8ILt&8Wv1)oXB?Z<avgxr#_Zn`JQ<x&UxK=y>0XOucTj5{2ljF
zXT4!g%-eG>q$`vYZmkM_8fv}yO4hIUH%euL{pN@Mw*B%?;d0&4obS>qlkWD;+COc{
zlVct;WcLU^OW(^-Hf>jqS^4+t1zQ^K?ea89Y1)^x!1r-aQ)r;aIXedjmW_sc*UtRN
zV?OCl+K(tt(LFj3a(i}3Mux9EDbVESaBIi0$Gh9NwS9UNYv+D#Yrw7k4pV8#rn>@S
zH>KXTcv$Hhtbfn`UPMUr3M<3KD9xJe1-_NlmODJQuGUV}ef;lZ!X6jbThT%WJ%%bx
zXEzuN1qd*{6qUJrIH&RXG>Zwl7NjRE*lZ9g^IgY*d8b17%pdxJyY}4swQnU$;atu8
zk)hYrr+K9RG`hsJYMajfeLn@K&v_sy7Pj}x`xO;VnSZ=j#5<R=EnH%As50uvQN~I9
z_e9+o%f)8S_|L%8IK{Y<;|k+z&^V0f*&k1Q?n(FNKIyYOw|sfWJr})I_jB4=RwzuI
zcT@7K=q0qH6EYZn%lFv7um+vwGAsX|*Wx#I2LBlrylel@(3H9Vrxtj{1uc{;$hx&`
zqK;wqwhO-bIxD%d%<Q$;%eWSKM0TsiUSzvA*=BQ&=!MYg-_o`Iemghp=|8g-w64Qk
z5VWjAdEx|rFNTe-i9hUvc3-VgPb^%a)4f8;bnk<LhQEu{487`{!lf^E9G5umH+3iW
zwI3qjovRp&G;9Ae2+K=lmSvx*O7UOe<Ib8=aKVYMYPEK(5WB*$oeDDMsK>Ihii8xO
z*>>&IxkpYD7nTVgJ9mU}o~R>u2j2otEz9R^*X~7kcP6)SOxQEY<6x)=&m_+W43=jT
z|1Lgi)o*q!%*sZ6YW1hQWsjTIiukP9Y11Zb&X8K<cT?fR+KwGvuLEYi58K^)q+9pT
z?yIr>r(Sa$@pvr3)3JQLrH%(9dzbE3?vBYGTXtW~y?N+lb%yYpk4=R;Jl-sFu*>-w
zeQK&gLjm8B4{Oiv*<d+Ar6aJX$jE>txh;rmeu1OxDlZLYd!Gwm_DY|%Ds2(_<lAg>
zYW|)%Jr9=@fA+XDd1t4}B+rwk3tbUsZorN$4p(2Fbt|v;@mitBAy;&D5^{}xih<`n
zp52mRI>PfnxIZ~IRfO^Iy;t>o>%WTbn}1|i_#D-~qK(;gF-4w|L46<BG|D!*JZ-cH
zm1SV^D4pLv?bpI9$sg5v)bCx=l1=mp+?`&$#LX9Ja^c&Q0Cu+N^Ld5ty}SQUh*xsK
zuI<%fy<aDsmeDh~c!a0LsU;z|KjUZk@72AWHogxe*Xcc<eZ)?F>U-U5*B*GTa5=5w
z71N>>E%Ep9x98=Sk9M8XU_SrO)SlUS@xAC971Nz(J*sWlw{Y#ux!=s5##=5ia&Mlr
zX35W-+lMAk$b7Ngj-%OkZ+pN;`Syp^yYFx7c=Po@)ZHVVf~h<1Ofuf!mR3JyzUjfc
zlcFzcEa210mglQGpP%>Zef!fUmZ?FOTQ!~pKVwo!<9TAeL5F)=#QVCsvU4%p<(PJV
z<hj0mpW21zTcv8Z&T-t@kdi2UCRR1~=Oi;B_nk2tiuM~=h`tmFU<aKCdcXNU!;5Ut
z-tT1o{|ut;f7I*v|1&IH@BE+PV2}NuP|)>EV!zHGKB=d#UN4k!=KFMkSU<iEyQ3n!
zB<|?XY*jw(^MLoZTXEMUdx0AJ?l-q>+!yw5jy+v1{>NAOXWH~L_wLuv`FW|JLV5=?
zvuvvf<MUs2yB}J2^A_3WAK51ZZECMpUZmJ$!NqCRb2H-e+||7|-cC+>9sHxT_DSvX
zBfCQ8g?KZkM<1Ur^~H0e`upqC9{GZo8C7>_F!xVCBG3P9PxeV0_k~+8d&}G_|F)$1
z>S7j+u=`VE#HHOteojh}eLK_Sz3>llFYlJkAKiL7ZI4XXTf17h-^lIG({jsO+(KnN
zJd+AfuG<9JW@r7O{x5Hp{6C(={|t{nOOoG%PQ5aHQUAlR{Xat&Y&{?im95&}qW|Wr
zt@BayY2pR3w@$8Fc5=Z4kKS(Ugo4A(O&ou;S3vsqny+R}vGQ$>yQ9;_QX*u;_<L(Q
zSL`MSjs@?MZ-(|~?F>B6VjlMC_8nK53tp`%eXcy~mLxRsvj`s3mUo?(t$lNg^v#rM
z5dr5j3zdb^w(A|x^Vj)Uv*Ngphv8<K6Alb_koIgaz}V~R{|QN-^`6h48K2uy{O$D4
z-nE<if2G})d~!m|Sxe%EaQlg)o{wHWYd^e6Md&2=-I(Y|$wf))rOsP9oogv6*d(-k
zBg2C)YddgV-@}mjck?mi;|MOI?zsnFDfV~%QLBD&^KDi(>TTW(dCMM8IIXj4#ZDVh
zgY66tH@V&QHTT|fDfgDN%LMkKPd1zOZ1T9ltoP2_@Bo95A5-H6#&9Ce;)3p&<Fj|#
z{;{p|;ag+Re<v<H`^~!~>|Xx2J*W34vEJ?9ER!yI%-1uOziUn2R_Tr{u@Za#9@sI(
zY^xqK$Kr18f8CdJvMSH3{AG`H1znehdVGP*cR8b3_aY{HUR+S_v|6X?Nb7`&-`ie0
z8CiYe_{z4+OM`jxrH3EGCMRs0@M4#7!+YhEYFjlkRm%0=6=tzT&YaD_VBElPVD)@d
zQz18{;Xg=VR1I4A1YcRZCv?rx+|0sd8P_i8zFm7{((zT^+N@m_PZcz`2Y7P!EnZtX
z1)~SaZvWu^PsTg{8E%9J{b#sz6LebJ!Tq0@cm8MCux{yphNYXKXRS;Anzwy<#=oF@
zcXDUt{51Qx*xTgBv9}Wy^nS1iZ;|2iV@<sGW7nrsul=&$^1b)C9QR=9({GD)_fO@j
z3=;jhc;>dr3cZer{j+7guAb-p&#*i;>(-t5uh;24+2s14VP3&)Zxyed@23l$oRd<y
zyU3|ImX)D$Z+rh&?=9OVDsS95<3;C+eREUh<y<<Idt|r8gguf;40nZBO4k)#VwL=E
zXLG$&pFhra&90!IQgw@qbxyd<t2!`2VD-1^X`dv1zA=7g%)7A7oWVA!i{asyy>*|1
zeoWALx~IwF;g<bjmz7UUlbtT0Qsn!&_?ccT-_b)m4<;0qnXKL~=>16gMya&FzK_50
zn@@kIncQt>tSc;fQx`KY+2`xex|c6B7Vz8e{`mFi)}v<^pI+)*o-6ui^6_Ggo<qvJ
z`n1au&N1AVnSCH>kyAKNSCO*6Tvq1Fin?naxvJd(9y8a;CU1>AGij4(cg=G(Q?C2F
zKOdQWoz;1@yvw2noBjSDr)^7WdLOX+(%OIbm%se3TlL}8v}>G3clN&*Tz0E2W17Li
z#V02g&t0{3<HKI}qgMTGB@t`aD)gCMTJxkfK5)*Nw26y&ZYKsw{$@J&an42s1DWq4
z0c>@Xmn@qq@}J?Q@!go1)6ZjK&Tp?-zcoNeFw{*@ur5@-TwP^S321@=gthhZ1zt{g
z)$AjD()QU`Po=F*o@ZD$Za;fti3^7%>$fIGTgGE8AGcilbY!w8^DfcIWUfd~`HDQ2
zl+q`HuXq{UYwOdOMV_pzFK1o4rsBTICyt9n4wA_SPAb%y_Wx(#ls)>NL5gpp?VsH5
z`ssza8UArH&)kCyLLc{D++=X$q?k^P@$$%f?zIZ@zWp@{d-p4C=EV-hGl_jSwx>^&
zaJAt{U@+5Q=HpckpY=%dYiyk-OP=(bYhsUXu^&8fchaZH^L9+oWMEp7cXub2RvN6e
zMhP7jw|m*y6_F~_e5JC=^73?4rp)a&I~E|rP}H;T)SYx5uZIoFL0t^Xm%a*kb&b26
z>qNuuV;@g2WIS=#cv0YSYSX4CLVQM?5~f9)9$Ze_{E_wO-OX+~?*mSjOAAH6<x+Mj
zdEAg3w1)Hei53R$$tyA1=`#NrdiFnI&;8Gk7;FBY!8;MWOh>Z*1mEp{hj!)vn|62r
z?i4Nl$NQgQg6#Rft)=>Zb!UNAhDw7LCe8oN^(y{Xv}p;r!OVF6hxtE;a{F(hSN4C|
zmi0n={)hZO4e#pTXs@h)nRE35S{WsJ{y)Q^<fV81?6RM~_C!Ven<Jl-)pyN2DX^IF
z+_i$j9;Qe~h8J2mdlShA**o6nDNXzL?6OajI#2Ez>9@RQ{BF}+0tA{ILwn2_I@vtd
zo&p_Cux+ca_mhiXG9UHsd;4wKK9__N6(|2WXZSxD9g|>gXIQEJN7;Wx%|C@J%dbd$
z$X%eDo5Ak1Of@Mbj3F;F%AxW=z|rgliyE|V+=zTRt?=fJD96lfxiV*#B$Jp)ej)`%
zp7y;Fbhr{rYfjY^{Z+optxk#_QlBX?fkC~$XO}=F*YRvVt~n_TC!(Gvzy4+}<jS{v
zx%;!Ms=A-KkM4-XG%YdVIW7_Yc+LZ>V@J%+2=I1k?d|=#Z*jWp)iv`{^e1ozEfMfY
zO|{TE(8M)?L!pULGzl>^qXFLTftvP;|DkMb*~LY-yTD*WV9)=crae)#WTydY4>F^r
zy>N``5IUX&I=n*D`<;z_vfYN|jit<5QJS`#GduWpo=6s$u<jDaIY#@<rgwv%UHR(&
z=7m4oX)lGRRR)!J%jYy6>`h9&<L1fOz_#?+>g2@2?A+pFshHS(rz@;ZYMx-v;`4}U
zI>Mvz<N;IGkw<CUr-BA2P6<k%XuTROBebB&tvV(BN~o=|^QABOCNHlEM4vR{`K(p<
zsmQo(;`y`6MSjmzCV8r>Tx$ij&OUTS->>@|w{w2@#C?B^H%9xE-qJnz>89h!V1;s-
z)RO`3jue-MpxYJZ{;>bowwM1u1DnBrhL0hP7XoAcGoW|7<UfomL+OWN3y_F{ipz(#
zhYLpE{xRKcR%MI|<Q6>(28Np|^9-Y>Am6LRcz*w%;9rk+{47};6e#I<=yt5xH@)Hm
zk$zV#l)uj|kX)K%#kIaZIe#T+v(Lnz)3yiN7^^)pS7wq(DKg@G8ThjBzH`FHEMs@u
zL)PnOHA`Qx{B&~z!@c0l90v2e1I!|fMbQ2N=xkrU`eX5*n74sifwTWJEZqQ}_CT+3
zP>KM22TV~*&hkG4+kb`=e9!+K+BN;(w6mbaQ)pEVxSSy>?=xB8>cDwM)N#+tUeENS
z>d~V}wRy2dH=j&$(>ZrcRb^78%DiIKXhDu5lGx$)5Bz_s&yxZjEx!I=R}`osRR1&i
zJa7FCt?U08Ty@d+LC3^3rf0J4HQaUa-G7Gd`)-$gy5F51kbBFM$MKy-WbkQ2jUMBv
zigtldCpE|}6+QYx?A)bG_pb8wm*=i^Pw8A8yLI!S%`ptSPwzaiqv+s?iRF!-We-=}
zzlBoYvJ*Ny_Bz@apSw*j@19LdjQn1-PSZHmR>Xc+x<k^|QlV;M5NORZp4+{PKh_^<
zKa!ng|M+m^G*2a27I8;rBMte(N=qh{NR&>P<kP^1INaItKLg<kW~cRBGu!mzQN4Tb
zUR$yu`sK8Ik+NMq-%d$B-O1z8c}2)c;pBNo2ia6`lLB=Ow)-E&UGabZX3zg&yZ1lC
z<15fI4OI|*y|;rbE0IR+s>pYq960M>{?@~#Jb`DG>ht1jKx^lI?tm<wTa9-77HAD1
zsH8<XlMCaJH0X^us3)gkF{$XAob(0AE$hEyCV{V6|95Af^uz|Og47cyl-EXJY$j;1
z;?f4K4MyF{-jBA|9eOt@ferB3&D!`U^5Je@<Ab}N{+;`6r|i{r^9xP%|L&|P+jZ=y
zAI}a8h0+ClkGeD#@YNqjyNeX{ko=3N=kveNU<SDx^_2I;=!dd{2ktQrgC}3v=UV2V
z${OdKiLb6-H-EeKmBHOxXN^U>PR2b?j5seBF)=AnkCUfn?+<AP@JV;-pb^Uu(1>L$
z|9=MI$nSA-A4KOZW^I`#c4^+L+$Abf8nY9UTQj-bT(UeY(hpci&!6&m{$=$pef|p9
zKhBT1Uu=2(R^#s7xI3@%b9cR1x_`>NtWC*Jj1!GN=cXr|;SQ}XuA9E`)%3~tombz<
z{3j#cxNMUBJnv(XA;%}Ip1VYp%W&rp>Dvmjt@B&<@UL*V9Q7mFd6MZg56^#RI}#t4
z^&Z#0IkkPC#iKPCHxlrd*V?XKI;AMaF@Kroifmt#=~jDorPLMdvy1rrIOyoMnT7I<
z4aw&YcF#JtxH>a`vG1y^OSTU$E7U7#@61u3^nfX)x}qmBZ)x%t4wV3rRZI)KTp3E|
ze;|0nL0mrHc8eeVsktnh|1&Jf5*PdKZMINnl9rCKk#=;>r-Y#7u-<0&l7RbWFL@bC
zCjZbsXa>3vt|I&J2k@nyI*OsL%qo+@85qxH$Z>thj<I1rRAu(Xwa9O}1Za`rwuJdp
zo-j{5Ryc8<-lJ$;?}vR`Qm*B%GoAk7&*rRci@v!F-03)MP<ryWHT%7N0XHP_gL;Iy
zH?DZapT0UK{zjJZ>1CN!bu+8~Gsyeu1Vx)n_cZA#@|nN$%*>NI7v1V|7#z%0KTL0Y
zFm>_l!%{NQH5>Q&nyEUaBy}u2^;Rb$Im7a4#m}}JjL>FZ<6fkb+JB_{dV$1bmwmf~
z>pm{svN=mwvLUsANy9qi$y>o=#Z$s$Q-59+KQ=Mb(BER?{%NufC)5rfo6w}@^89Ik
zRb<nSpZhNA8J~3E<ww7X0PS`JQ11n_liblp{y&4$GSDQ~i~1k4$XB(W*^zgB+mr3v
zyDSpAgRcl#JPugZrLV@oV8Os=7^{lWTLf3#v}nHb)gPGu$=}8lbf0njUlGvSZnUZw
z+!+9M2q?nq?LSPan8eTUqbzWJM%lHs%WtVT)#^F9J#lr_{Wg{7$kaH7lQw*XagA|h
zi_(4=J`CMH$>O=@BJe!qz1n@80glSHn~Yy+FfYMBskrIw)>=Q_tlM6b{&`Pnk2TY`
z*?3H4p7L_j6Z~79nq=F!R()6?^U1ej>s`Nh9tpK^)-2&y-=*xXSga*<?Sre7=Wgax
zH~ur2ac#U|@cN{J^!((H?SI)z?EeV+{%1HDDpUAlRr*Y&kK*ljAJ$G<^-^e3?-n!Z
zzuL`Pr#$$k@O||>;e9)<{E=RG|DNZw*x1Z(pM8Ei+<7ZC%|eD}QdOAjx%Dg0uZ?*b
zc>iS1<m^R9)w?XtOmH!Ix>M0yGst`8$<#cF#y$>)3vKqIF$*hfTp#`nuvSdDq?#ZZ
zv6@eBR~w7qjV3MsjXw_mYu+XQk8|07h9|4~4;)JUaHqRarO40J*1_ZBLf5q4DK`~8
zRd~LgJic<>B+vl}s5<P9Kj#0%_oDuX+U)-flUC1f4)`c~WLuu;+3pqD<+qX+Z0YGx
z=v)_J^>MO+04tBD1IL*hM_rj&|8|#{oVB~VRWqgh%CyKWSGS7u>E?y8q<#J<CSewx
z!Cq$88q>w_LcRZJ7`S-ph88a-ouPpaCsk&zVPLmhWbr4|_{_wL?!)gs>^m7+(&_1T
zOPcrJ)PuK96;umUUsr#m8ytD<kMx>O{e-O<HJY+tK1M5f^Srky?i4Tc)MANObeGxY
zKf^$K!N1#A>K|(U7QbbG@jt^uh2LUlyZ<f!ZG8Urob<oxXXowR+^50pj5Z~`c%Hpz
z6zDeNNBaDSSv=xARW7N5i@v-K3^LC)zBQFCj<}kWBOEd5oMn83v8U)BU&ZL^D_sh$
zQ&vq_+vK&)t;k&9^t^xS*B^aYaW(ada(1u#q3>0@RLWj$yyY$B6yV0^DZkHp`{pMr
zlrv6UV2}J}FHwJ?95mNva{tfN!1MB5YjdCO*zr-k{b7@ezRILbp;e&!l+7a;_=+RT
zqqc44+qgQG*ZVKu>F7-xx=x?)T{C&@s(s&&J?^)iSrE=U_vm#l<1f{f$(K!{xo6*e
zuej@D?DyHvSy=bX)O+R^7%soJQN`}3e97Adye`*DHTCq~UOx6uF!RmCd#_A4Bwf&w
zu`K+yXGQQqb&2;;XzBXw%WJo$Zav;;a^Ki@zW>JhFO_fAGUvS#*)+|t!0m#v|2zW+
zBc3zO1qbe5s?dM(;Zn4|z|FgNZ#wM1(<a@i)LVR?qsyq$;-t!x3vBkCx_dn3=BHi%
zwQj2IimN4WKOS7>DZKqxip62c8+?U-)GzmKy%TQ!c%pGdo+&7kTg{uNTq&??b?qj2
zpFRZDdC*?;jX#P1865BO|7T#iT>mN5Gk5j<sQb4wZ{3|!c)IABb@u7-yDaYnXJ-a~
zKK3;5b|%jP2AgB*B8)rX3&KPKSZ%|7+ruxt(^1b9RP*6fQn2y88q3L^y_(@vwE%zC
z`bDpT<5aF~e=QR=ckz^YCM;~RXOyQpsy~?+Uhs57xnk0Zt1BbRf90HA75S=+SEgKW
zN8b}eg_!6+_Z1c7LT6XaNmraADrC5T7q%Roh^D#r{LP@V!q@y~xS@6UKZD!d>y9zC
zM{XU77x?P`X128SnwMdA>9^j?-OqoY_px`QUG>*v23F4-_zrbF|9A5-|1ZXj`X83F
z|1(U?Ks|sNbSDkvD(a7jn@_uEekC^g)TO@p%hxS06j`d?C2V@@DThSp$<rrydbzC&
ze|9kHSKq>w{}~P)n0F)YAj`=WQA_6(y((7e&k7UPJ8kMTSyQd>+4j5EomxsPrKrbz
zqaROxfzAHrR$u2M<@aQ#{rYw9*!{QSNw2u)Zho`FcSF-ndyVovT!x?i&JwC(`tkAA
zKh3LVm9M|$zpdTnT{|mjpUcIc^%)uaiZ{8QTm1PG|INf>6`!rRwd2JiUzu-zzw~9e
zd3bfmo?EATCu$~5)QEPK4mt5dU8lV0II|R*s~FF}oYlO)OIIMv_~hz+t1HD8rsU1s
zvszVL&Re>u?8x%mbt+s-x9h8)vEKaU^!&{~st*}w*QxH?x@GUB-Y2(u&wii!Z|0`^
zC#BDcJmgv8c3}0}w9+!3t2fZjVn>_&bdZrTe|G%PK9NdOP7z+Nvuocf?Voh1Si#SC
z7prEac1?rRAI%V!q~N%nF$4}z-va5Qq0NJ#`|$#3Y>JQ?^jp5{P!e4>|FP+DTKP;r
zTJubDr7ZYn7O7Nx&5WH|v+N{SZiBikxXRwMs7r%+{>S@&CZ87qCG*$+8C*@#98>Wg
z`8L;eS-YlOv+8Tl7di$$)kcR8e5lRm>m^y1=UM(bu-b2{IQ*|6O8y^T+JA;8QD~0R
zs~67JU+!un=*}g5`*o#Wu;08N>XQpTy3O<Pk=I!jv9GMDCHZ+w__dnc6;XF|s%rO?
z>&wmLTadJQ(~kYohZQFax|=v~G=AEkQmVMUc}uQBLmvK^i>&I~xzhICs!6wAZp!>-
zb+mPgw@%Kxx7xSNKA#g=KI^E*Ils%TH$PvW9CT%CykJGytI#d6Hrd;!eN<`_I(Fe;
zrC7w1cK(gC8)jR`+m$o$o=5fF@@3AC)@ogS``}_pn){A<52jyRs$Q~b%NmQVGI>Sp
z+pNBV*EZlS4ZzD92&#DS{BoVb*+QL_E8Ll^r$sEjs;Jd4f0udYkq0GDCcpAU4}|NE
zG5<EN$mV_|YwmH$x2Ha9%g!B>s(0M;*FII@a7bJ4&CewXo4&H!>s@0&jUcq5YK=ur
z;Y!!VYMZN*GZJ=RSblBo+Qf<5T{f(7KV8Xjc)Bq2gzn8OHUAl^mTdo+wnitvWy8-+
zD%%Qf-}7D?6LBo=QNFrd$noNz_1bd`?#Sq$a(l$M5p`8T<jd?w2iKXc)tkQ5*P!Dt
zOa7W2-X*!Mhu&^sd1tuLx;r^vf~9%>lDl!y71Jv6-@ZxRHUG#y?-Ly!F_~V6JU*W?
zW?|^r#=Pn2zK@gYrCtSAg!^9=<My|EeCWH?>6LD`)Or<C13#yyrRMZJZ#?mi5$zrU
zceE^){3=f6quTVp>z^NAYW^*3-mWdb#hiB;KYMhu$SwN2?(ffyC;py~@ho1K6__1v
zW)-_`w#?_(i;gaxW+oZ`=IQ*iwafJ$tY9dd8n82d4}&TGkgX-|xSYfCUKjnAr>CyH
z|09oI;6Fpo%MY;{J3mEPN3Y~Qscb&0T&Fsv%^<+zphBp^o0x_&w9Jc^If%SeVD<;Y
znS0EYW87tm=lTa2spQ3m?z?H`ki@8L`@#5y_L6n=SZCW|$1utKXK1c}!d?uT=JWo~
z;GG7Z=0h6;1@Ae<=uM%IfkNiqWCWbE^F{aW2|Uc=0qKyjF)$P`$RsUUW6yft^m=2B
zZDFC#WPiPxIiEb0#nO|7CVARS^0!=jia}%1ra#UreV1lTj)_{6TlQXd?}jNt^Geoj
zbc<(^oqg9kc}}{dO#tJ{iguq%>%^`-s+4;>!9zDUVbY`8naY)Yrs<p$dv6>oFrK6}
z|BqT!{GVU1=l@Uw4YrvsT%2*ON^H)wvdkBkeGXJk7fN887RHc2aRayElUWx)=XMF}
z>i?@PJ^x2A?mxrFS@sW&F8ybCejRjvzUce^43glS|DOR}c*Vny+h$r?>wZ;WeI4=e
z%@X%}+m1b%uh}qJnvLQ1q{0SAwq0Jw_k7qlxprl*TSR*F!X5A0-bJ)Mmh3pWRf69*
zS(Lx`KmwD20b{%Uk+*#3y*FRcpXME*ch6sA>)Fk1eYT4{MJI)Yb4BoW`LsOeD9Cbt
ze1dJog>Ca|Wq17c2{d*W{2g;K=6LQlBh^#?J~`~ST4CLIXQ5vye@jVm-b9Xf7cbuY
zcUkt!%Yvf~>?IG6^l*eoq$zVW{}31Qe3&a0didsZxym5bf{?RXXO%V2h3+{L&SM$0
zI8%gie&(Y~^Z0gL|7sntd~)}W)(6JUf)3O5x!N*S1ltZs{`}xq_FN(KbiT;Vm>*@=
zqa&XDwmo|!?8Qo*pb3}!6xmDiPPjc|dDzER-4oU}ed(=?Yuu?RlXSS={b$%S^=Z<%
zr#Ge*MNB&5=V_be{aU)#?VNY?ia#gfSsIRdC^W5EV-VWN(8eO*pwOhj+#TOpcKL49
z`TWGPTalZlz5C?UA$M0y+q0!5|EZYu`WYH&Dm4op&prCFZBE`gMT7X<?z5ks^xa(c
z+kL9mQL`ic#eXIltvuE9TzjXZlK&6qFO2!RyIyWw5_J1~)~mkLGnR44TG*N$m+F7F
zN^9K(hSk${sm)DYalSr3f77Gfo7Oj0<yp^9n!MHAfakWuodaSgB^U7gXZYc>W&h8w
z*X=*JR{v)>2D<a{H0VIi*y8^TEaChAq`?ONP(}MuwZR5MM$Muiyt4J3FDiZHKh)3r
z^79=}9{y!fCXI=0feM0}T&GR)mZY;UD_T73t#<px_v=jdx7i6?QJS2)ckj~1Jx+^x
znU8JUZ7jcI<9nfLUpkr`R2n$dKiIBa-~M#Nj*p^utaLo$yeoCSJl*cfUa9K4?E>S^
z&9Bdf@BdL*`*(VJ>f#@ZyiGRm5I!(n%C_gC)8WE99UGP%zjN~rfAQ;Chp+x|T=(i8
z|FxX_+~=Donyh~PdZCW9o%e0FE;d%TJ0@=$e{I}UXB46DSiL&iD)!joWhYnGE=vA8
zBkcJJ7lYZmmp3^|J(dp9d&0k`sV?bp7sEOm{ztz#7H+y|r{tf$EZSwl?dbDMqR)L?
zv?74}VR^}yKfmU(eK0+GZ?5XP<&Uyo@89yK`aq73&F)SSjXQyBZ~yM@ndA^EX|dLy
z@6O#lyN<Try)r%BZ?D+LJ6<a`d8}nIdisqurdgAj%Yu33N$V+$(-&k+tf=;mwd3wo
zYn0iNxUfx8!e(k{n@NE2<ja=HXR`ub8H!#%_}%j9+mFSe@mk^YY@%-PPO^J@&i>+#
z<h`G&=AM0(wfA|0@)ez<bKmW*EzVNSJYpR2@?Ddg%I3FbH|}^Fs;|6Ln{CJId?Z}x
z=8o%TdJEUy&+KZtWTeofwlm@NF`oktB8I9A%7z<RwiIRmdVArr$?vi&ODEnBicGs4
zb|uDQ>&^(l+2@Z$B;3qhAbaDMXpsi9bMyz>bqn*q^;RDVFE@x%-aoTGeYw@49j9gX
zZWBp#RKI;|$@GICUlqpRJo~8o^^PY~>uz)3dijZMf|lrKk=sQFT~gBLu)ghj{>ODy
zw$=US(ut~X#Mbh+D({=8o#L4|_jzBT(z}zY4&6^Q9#1>@nT@qX{&rRWA65IL-|oNc
z|ES0(-P~Az<v&AO<?rI2{|sw>Zoa;)@F;_4`h&8|lUO!>6kD1#L3xQb>)a-et2c~W
zk8Wq2!Q}ADL2dEQ4>e`KifdON6~7p9JIaRr?AFWIEY_ZozC1fer^5Bb%T~#kAygk#
z@wmsoqu#i@%QWnBs^^olYa8z?<=%S!S9+SXF#C#I`<gbt|HG$S@_OdukGbFGT|D)x
zahKUO!zINH#l}+`Js&InOWf(LX`$A=HafCB;_AA#rT^Mf*WQe9O?{$v&GXvT`0B@n
z$LF2dq1|@w(d$;pU$%QTzMQ4odiKrt33n^j{XYA-iRqrt^kQ|5)&2JlOp>qZ-&J;j
zW!kT}$=QW#^?E<DS^Ea4OpdoH%v?Hg!rV)KtC==(ohi>#Uil<#H!riR6x+0I-1X&E
zT~Ax4JK6sER1_#)s5?#PW>Ul?zwG|YYqx4=_cLYgOPg&sKj}Zii_f=wF56zwOw~zx
z(7V8GzD+_yisVeThmHG}e272!aLKkf#m&2SZ)&XH$zv|$D)oGyph(K6!bzSd7cd_q
zW`g?o$I#wm3m?|HNo)K${k7w4iaBHVjPo-&pZBSR*nB8FFS)i$gK6I6mCkEkT(erb
z>%@k*+s6x~PB0{_Ti9TslFokR>M6`UQ{V;{XhR7I2hR^`yB)H5!_<`U-JU!_0!(7Q
z%hQU#pPH7y9w<Hk;p(Z=SH0XEpJgR`#8<+b``V5vhL&2n&$_vf$6nHWF2nrA3Ovcr
zh<aob=rSjiQ)Dj$Fvk3y|7VJA`oDu=^1sa9?c#d==0C%eg|F?uac%g|aB+JH<MfB;
z1>$v1X4hsbN5^JMwa(pp`%Ye2$*hM5ZZ>zc6pFHJP*}le_HfmqACE*XZh0H@=$K2>
zYp2;!6O$(xyKP*flPt+#sFb%;zWjdAZhrnB%Z>*|Pusk4N1OJ}_qlJ?u6guvE;ABO
z)lQN5sMElfCXqLjq3hc}!H+EUJLmgv+`S>zF4ss}a_ct1!?|h)POO>ct@y|!Aacfo
z(vxQyN@v+^t*u;hKQpRtrtI9KbN2{O?|Oc&FHqZy?eJDV_NnKd22XM`U^eXy`<h!S
z%O}?5ZeG5YYtxw%0^ODKb=dg~T5@et+FmW%^Pj=JzQZc?=(p|aEh_tW@A1%$yZ1V_
z{rnNPFrlW6YrNXea&Il0voeV@>FP$-`@N>OS6g?#XT6o#zwA!!BF4gXD}^?@s<_m>
z6Mvx7@_GB*9p{xAbTa-a?7Q|SbkVtMo1$KR-(`FD>5k~$*G9&-W}IHfb~7~MNn*qO
zPrFk$-U{b`xSub3SKQ82+dBo^+}@r#YZu1)_~<6)wrJ_!R8BuWRqE*zb%r^UukU~?
z8`^38ULyA9{Z}5lWG3Hy`F%sAr%t(s$}G=G!V<mG40A7Q<i2U(5r}vizGj`?Z@249
zcU+k!tL<B%_tnCb_x&0x!wet0_*1$O8cKJKjP6GBUS<%AuXz01=#c;R+c$2-A78<1
zd*u7S*hME2#2IFuO400ToUd<v?oRTvmAW<=x0bG(^DAz??3?eN#o8+6-W!(gSuL_m
z)3B2>Eq3-cHg=tpmo~pEu^0B&J$s}oZ+33E>5F~d9b1>_vMgfVuF4!aRpHnYfrI-#
zDzi(dU)&R~6}cziR`mU-B^~<Hqcc@YCr(|$qp~UGu#w_{!0j2_TkE12`Va5ZsLo~g
ztnOI8Ygewei_ux#%kl<yy)L}FRm99ZP50_2Mtcp@jkS+XcbIbO<eIGC8dIOuYh;ke
z#N<0;=VytDhkD*Bq&yH}mQg(1d}!C#y-l~&CNF!avu4fX39tKi*>BoyW5oZ(Mx5t%
zpJVVArX44YB7W2#HJfgD*Ec=6x@1@56`sqlRm3OUmd+8F=4ICMhQU(ud=|rv%QcaO
zm6hqT$EJR(uAaSf%hxF}>}szBH7931NRz*Ff_c&!56K?pS*N#sJaaMQLQM3FO}2Bl
zwPvr0IjQ?Gtxr6XTS150TSHKY^FUs?kxbqsS@|OqYP<9Lm&$K^B`(!cdF{zF&pmGs
z{AXBHd-3@`_Bip$=Q58!jIGj@dhQ*o?)yp4q@pA}d7a%uo@}Mn{9kPHkF1^CQ(z%`
zK+k`D_G<C2MH3D(yRN#OxvS>mjtK{!uieG26~J~YO(<dVq(~#CHp`;Zg-bly{xkgW
z;9D=Zk$2}L&v#K*bLBoJ^-OyE<b)4T_pz7eW{*F!r|zs=@MF{C-=U8-UYg|ndw2GO
zO<C_g9<`B+JH)VsC*-H$yP!J_1tD{;OvwDFzjH^|xA#6<GPt{^TzdEQTE*LE=iW@(
z);eRgkkj;(;HCw+z6)g8+m_FkS~k;UlV8d1%Q=%hj?R3X@pvYqy2{kZP;(*goI8FI
zk5I3l45<^^c5RW=)MwihGt&!K+|j++b??pD4L`Fb+@wXAR>~wyI3u}Ta7#kSJnR1q
zlPVv@|7MM?f3XZSj*BtXe|6=`%(7WqcO5R9B+w^k-WA^EahoMomLt_dMTp}>l9iCQ
zKI+ndirGizf9NsY`t(X&+N_H)KNqQ<xtCIC@_M@p?{38zGM{%W&zZoe@S(47o7lHZ
z**l)hr#_w*{qoW-rRY;yYN0Y)@{Xn>LX5U-D!V>x>#cmksq@X9$D5&zGfv{3>hFyn
z9Zn}DPBO}fGR{cmDL(q@p6ZpYy;|H6Z{PCXoqM!%Z<wx>?S(6sL<P5>adCb7&d6&T
z!?6Ot2j=z<6|dQxf7AQT{#O01{WtgL{I>pS|MBIwz5o1Y?tb_0y<B?yZ2Q9wvMjR*
zou*u?YTEJDwXJkVSNJ>=@uH3(_pq=+zV|wYd_S#=ybWJ@uC%dV>AUKsUG1S`>V1zM
zU2~RDj9obMkshPUilo`wo;<cVdCYGqO64UQ`zH6vmBjrSpG$dyoTcB{YgsxSmbElo
z{`6he(c)j{7Ov6nD7mZbX=eC$)um^TJl{R8v{|qDkeOr6?#<68Hl4mA^JjMi(~~-x
zOG?|fY!@@!A~wx;`C*xsUEO6IQbrOJ4s=|oxoJ~9=Qw}sml-+la(j%=Y?rP%nWy)3
zR{oTyhT0oTZ{18i%)7>$N65Fh;K$>jZa3ewZ^teiEMMrqHahCCa$aX*ME|r;g6(>0
z?26)P96$ek^~`^CHX`CaXX57+&zy(b_e}TNv9V|Gk$ZkNEBl^*`WJ4IxWgiTO79Wo
z1sgx?o4kBWK9BL9&a!-$$#+j1&+KuNJvz73ez$djAN#VbT|cxP<G1i{I(PAWrtZYn
z^=cW9n|yaa?&W^l>33DaVFwq(0nzg>&BLeNQ=KRMyIL}D`A7XppOl2erGhq0via0=
zkU?3u;mywcJt^~#?V1uNdikqs)8+F!KI}cW=~dvi&cz;*AvHH|&Wu*Jd{AWFP&$2<
z+T8lT3%|{-H~#H(Au_h+jm-(SKl<$bU)P^F_;c3>gZiY*`+2|fZ~kYvWOx1B-QTzW
zmQQ|?cdYQ=`lrYJew;TwP0dj?D~>(3%N(n-D|v+6Z8zW9<Fok$Tb_K)?zT4uX@?UV
z85(;M!eaZIb*7!Ow*Il_Ms9I_?vp#764NdSCAF0Vv2-=|RL55+h}oPtwE4@~=!h$S
z5*JJAE$F)vl~r)(_7eZjCEIuQ2`l{ku+t)y#n2(P==OG=T5VUWxpSv&uYb71#`*8&
z<p)a^JwKW8HgAc(O3%H_I~(6lk~rw7%+eUrys?P!p8K*h|5Rs(?#wvln*S|Y<I1GK
zh_<OW9u%F~*t_R}3x~Zm<H{H!ul7V;VUBZ^FJw;@AI6wm4CXK#c<m$c>k-kn-5393
z0TqA`*Z*dX`p@uU>AI!{E+UV0>SE9!a~-*M|A%+eO8Z;q$!z*v@@?YDrO})|hKJQ>
zv@viQo$6caSNV8*OuB6=XyI8?h5f%)U;h6LtQY<>d^BN<%V)n6Q@i;5N4M4bw~_?>
z_gy=<=f<%&%4xTs#n0VgQ*->vMf2u&dUh9||5zM4{jDK~`u*&LdpXHvf}3+c>z}(L
zXP5jc>-Zmqd7ve+!Jz5l68k^C^5`pn7?Tg*V){{b=H}sgn{SK%hUl~I@#I&TyPC(t
zQeEBhkL9_eSR9AGZsr2Jqbo7WSW7?D9;&Ra30$>)s`hy~-5j=)@@3EEU)(Xg_tVzz
z*;muJ&j$owi6x!;9=mVnR-rAAB-fODcT^UN{5Cr$Pj$xREAQ;KF8t5Hfwr8>9o?4<
z>96V-`lCPX-@5ho>;DYucJa5~l>979mpt}5x#vO27g5#ojkmttdv@>rk*FyjVlApW
zo^IZdI<p~wyE(T_L5actyZeIG1Q$tNV70bq-Zp1~YJbO8?T|)U#R#1@0&eRL&e7A|
z!E-=}J&4gno_TZh(%lu^K?bV3qn4zdJDhds09z0L<^)Bq1?!!+RE3@=utX?>X?KO)
z!#`*5X<UsyJ5_zM**5l?&h6RrzvM;a_{c5J`o*=}zCqROQ@6eFtFY~C5AL~ZMc&lY
z^Z3sYbz33m$d~*XVnL_;IM@0UvWMADpE)Mt@2*<)BiFBmU!Pg29?i{v&+{a&LUgHq
z(~(b(mNq@lwwv&ZWJpEb(EWS&mG(5DSdQ<XPo8v%J+dugb82Ujr{$`8^yGz+QWziW
z|75&fe<R%YKf|RP*$dWK*oZ%jj_z2e`^R*#vyGperSgW(NC}xHj+iEX$RKzZ17?R1
zTW$vJp@L$~d#?g++|9i9X-(_<cf5OC9S$UlOnSQW<u)^!^htJ$o}!-s3EgrhL(Co@
z(epR|Gn{n3R{usc@jt`jyw?lX)t&$6CAS&0*optIbh(4%KcSD}-&&8}n<}zDch{CH
z`n{j`+%(%bd*w9|ThAl`hCK}3liW|p?d$v~Xyf?o__Es(_hLPlpR7;K&R(fANnp33
z?15V>Lc&TssRtB){;bsbQZE#7H~P-O#V?&QRCiA>y!OO;+OuGt4)>dO@BS`H<}uSa
z$IaI7d-+fN!{23Qw^EnB5xe$G+nViqgpOf@p;Y}Mh2+*yUTs5(--nBZ7*~q->b`s4
zm91g(SMlkV*7x71-uTWD$v!Q-@b|aH|L$2HpLW%^PB~)Vto+4WCx!It<)wSve&+45
zNNCOB0><to+m@#}%GL4T$w_~COT4qa<(<h&8~er4+{Y&+KYevpX4}!(C5~RVjoMpX
zGI}_<pDeq>z_8(-?A6Hk^^c}~_;s){MJHu@fA}Pmh;367cIP?<ol*{ReBvzdIAH-V
z_j>X8%!zTX^^4tZwQjyCn4entOsBKhvej(&l6s5O;w=q!@6VpR?H}_|Y^73n#hRL_
z+pd<}wm#jV_p>j2+CBFGu5~ZGyoAe~g>D$Oo(?Vj@SmY8HZ}XUwe;(isaq$mOS|T^
z?{;O)i^+mFwchgYw%2>Sr{{w~{Ezyh=C`_I*3RwSV|4dmbzvsoCZFQ7oIQ&Tvy~oq
zEN0QxIP~SDN<&t3#jG@e+nK*&rke}h$>O`{SyB8n`p(ZFku-L_Gp~Y-w=$^Y2Q0Rd
z!?%(>=5|H>QH_nJQ|I>fUJ1JEvEAUc>ipaz`$|@J>dY*ge!G8q!40-b%hxvMiDpwD
zt~K|ar}3!Tx@0@o<e6<(q(k0o%v5zye=0NCL2ByRvyZ0rA8mH=&h}{!xoP_9XsL#l
z#7Q2V9g|eqr`_XAp1`W=kT+?^-eAv<rq4EA*4?^fSJfSrN9TM~r&-3C@k&qp=2me+
zQ#!|!>1idqP6U(7$7zdoRw!LCcQ0HK^K#mnd=bg?&ZW{fa(^b?=ALv@k3+%jFwdpf
zA1Bv-@vi>NHajQoQFi3~pexs|-Lp(8>z$Z#<IIyyhVc_pLnd!|=xb3@FXZ@5cbDCi
zy5lQivIL(;PoAmvc{}sJ&hPH?e#lnD`CG2LC;L(D#-6!W$L_gIdwFKV>r2|3V!WT7
z6{|b>X=Uz?)Whp8wy~=;xR*bY+^Ri)`;9wy4`-I<Km6U1tQWHCe9gmy3=hP7w3Amz
zSc<O9e^h;Z$F>cZzSM8=FV$P(xO2av@^9M<o!y3E32XOE5Ru)l)wumx%<g)w*VnFX
z`}T6l%cTn2FTcGqxA0TgxnLca{|pPi>J;2tyv*wAX<7LrvugjCPt5og>?wZRto_;(
zg}=*6=lT3+SX7qEP{p^?<^oIMk6S<IM_m)TWPUOCk7e%aTZca9PMID#pNC0cX;ZGf
zG3$*b>4n_WCheViZp*B#*E`<JyH91gwRG-jXWmV<voz<0b(|3Lzh`s)Y0LDix4ye=
zwwehavQy~yn{}|{w_vter(CB}eeU+NLhM{We~Z-|P^qhXZ(rW%{KC%g%A;N8WoBk8
z>!)0K^YH4o!&OclGk<QGcrnf-fawHBOi9fwhSw%LpS2&^b#AiCCSM^H^9!3ds+rC>
zu}rVXgP(hc$_EuL1`h3_o%Q_DKbrgnUPZ0jy6ncywMRU2rEcFhIkS>`-<f8q<{c-M
z^X}LMbp;3<+XXth8*QBh=)`lBwG|Ckpe-ks{~2WeGn};fsQ<TV-Tp7ZVMpKg?pw%o
zxKw_o)M=RmdCL6KYdR{vqz1q5t5{QyqBLZl(v_{+k|ou-y16{RT3>EW-^CMV`blka
z1(&0W#KGIg-noTaH?W>G@wJNI@_zgITX~Q6PJf<1D`U^z-s?S;h94}fE7{cz@BFCt
z*)49DBBXui4)^kDnos&1HF}fy`qoJD9px&UIB`PV$8)mnou<9cA(wQL`i|Dz-`;&Q
zGX7tzUUJKp?0M!-_XYXgJ@77fMvZOsQK_%jo7SxhdvxjUS9`vgSKsnk^wy`X*eEQS
zZ~VMyGlPn>*_3ma=P>ZQY}~m0@|wq6xAvcIHFD62nB=K*=D6yNNuEibDw90b)`ZW!
z>C8KA=d#QV5t-XMlOGuiO4Y8|?iuk?U)j>Zk276)<pYhA$9((wew>fIw)X59tC;CY
zkA13tSGe|k%a&<S^e(p9>Dm2W!DF}kyORfb3>fc$*4VU}R<HGb8yFXJ&}71!#BGPF
zB^h%5zED%$_Gh^ebDMP=qm$>Oe4+Y72G_1n5BxbR+qL*v$8_V$iAOH4yEDP;O<O|o
zxkqz1Ij}prR?b`dDAqgT(t@ph_b%MMc_(7_)ufAy@ACR821?f)af!S4SY>4bPddvx
z=Ahq4cg>rhuR7(P^ZjM3OfHwRwp>;`yJFWp-HAQz&6^p2{Qi0Tw1ezX(WAG2v>&mW
za?5t^8nJ1`_oDBeG}(S_vSuL5MYl;hDytb4YHv$620VCYUGP_}b>)AC+#l6GSNF_U
ze|v3W%+KiUIrkd3J!iH!XWZx@g}2L`_*!b(Qn}5^OJ8PZK0lvtd)xFv(z=Z%-cNg%
zYebx}t1-K~{7KFS#w2^bOu^_|(cKcaxV_abKkRdgb=}RvE6L-L;F4jNGtc&1a{HlQ
zK4#@+$0VOc_wGyCE?#uj{8Z75sW*1L&Dr#@?V4&Er`nF{e9_p7;)l=MpKY&@v-an|
z9eX-&TkxHe8iMKBCiS|T=C*Lk7pRv@^gIvzdN$lu&S1}uoqaEruIaALRgTV-KOuBH
zXTcl3qX#}u-KG$9W_^=+!va~={?;#ZZ5LN0&VAy&xk_c;yU00bk__JIyz%^d^LA5#
zt#Rn}gHc?67t~HG>#O$6>Cvq;c9#*#y)TmypW{`w;t=bB05*nowWe$9gRa<E|9-#O
zZP)GFKA$o--|D{c@3_kDmLQ9iz|YI13-r1kH*UGH`P$d+)wg}kJ=?vu{Px+k`J~PS
zYn}S^JrRdl!eZb2KAE%W>5Od^w+_g<KI>c_|DPeFcG>+i|1NA13y-(vHxk^>eem($
z>`w-Dd3$)|Z_Fycz3=w7`Y-)k|8B4Q_Maj4$xrExbLv<BEWEtW_-ql8;|n<z@ljVy
zt-Ehm-*_@n!DF8F=B0NcbXre0OY|jqYHtua@Ze`dLb3|8lRkgugt%MxoLMHG&-tz|
ztn-O+cKdz3hr4+sH{3{YP)L>#ou2&QwCd)*bN}?sq+@R1t~3{NQ{BQcW8qwpMx_PG
za@X&1u=X1ntXtH@aJt`j<{xjf)kPPlblrcmEpVmEqK&-T8xK64nJis-phKXpj5!Fj
zz-)j!vV9ziTeo-JyQlH6Nrh9Ua7CyqGh{h`P?&tvbKLjbU3<zPdj1FUr4;Bh943qx
z0$oK&+CWEvddBlVg#URyZ`=PyH2XipqG_P5>gZi`lz}qLCVFJmy4j}R7B9Txa<OH@
z-t10i;YrKxWo+0}dRJ*);Q@PR$ew-T+VJi54{z#iooVXrn;&#}`Lui1m0?#CQcHW6
zq^h6oJYhNYm*B1Kpz+avf^UQWwc8f|`*XAYlkEt<c8|^%7=DfW&u~b*YTn%9#L7o+
zi@c*(%#)madb9MzMjj*GPez<CV<E|x@%#^zrpS_yVhy|g?6NwuaqHf>FL%z2oEa_W
za$+ghCmEZL15F&aCpa=KMr+Olf1JDK`mg>royfKF{yVSS)Yr|+J#*5kyK)Ib?*Rcb
zAx3uIjr*H<7<Xna%DiTD>vVqpChv%)ZR&bQ-cFqQM91^z%$cIyW)XAdJehOZpCcnP
zzdZk&rxf?<@~s*79)(3bENtsji0BCD;obOFUh6+YY2oqXk9(bXrM+V9eS54j!e(`D
z+I(r9o>;NcK82p6M|a4DG21=-+-K)J*X4@7uIbyXO9u|hUR(T#Wt->no)Z(3eY=8=
zGHd2^bUiLO_U3bs0N>)@!hXNYZ`YmwH}Tv4ZSU{hf4yhEa+z`e*Lppx@?({&zU>nu
zbbE=#UgP-L&X-m8?6|yEW!}B}N6as2ZPZyS`a(@*$_i_V?dti~ArF#8FJveO`O9W!
zuJX*(dA%&6b=p-a(}^{=H&5z`SjaN5_v{?ziE|e)J7gNYD0}ydcTRbEu~lb$@Remc
z0nClhHl2FH<R{!<ZunsGOoi?HuO?KK{xv%$aVa9LB`V(2?0N5zF2Ce{i4^DiHqZNZ
ziv+OM;2)!(@vg>pS#0-wBTmtGd90UDi+pldnBumP-93z_J*m~&<HQO3iswOH4Cl98
zG<hwVo4S4bP1Q9)hlQsnm7O^CNlfL>nKNBSXY2U+75U{vMBIKkt8{DYoVwVxYdm>0
zcg$U}fK}3F4ujRzE)9k?fBjuIUH!ATWb>MdDJs{l8%3X3@K}4FS=g<DCF=^jRw^qb
zJMH|N9&k<kh*jRiC9@^|UCk^mRQX=GXI}V}4~;Ehu{S?^987)1R~Ng6A+|#O@b+CL
zQnknC@4F=Jx=G;YCDw|NM9~lT?e0ukx+%0XRk1JY$vnBss<oc?I61GxS?bl-t8p({
zwRpkZjytSAM!A-*mZzF5E2zD~^@4iqml=<?I`TYSn|Jh0(bhZ5!e(gto>$DhRMWCd
zV&Zo09tN$W>pGW5-gPg|&)<~s@8ZVo8;{S|m=?$RPd%V^V`Jmd!e72upKk9=Z~J%e
zSoF$2-cR;)w6q?ZvPPxfX0d?-$LR!Xz3BIn>L1rF6>ly18<?==^E(^;;x)Ub<Sxp%
z#1<-VR+bia;#`GH-ve0}g0mbamt|~=a-WqORyHYyeb%#Q-klOW56e%Sx$PFwdX6zo
zA!W{|U(-8nJeU4w$o~29rSIRV%h#>7J38TA&(9s(VkS=ed%Et=gChIl>q0TFXHAK^
zdbV$R_OjzPzg}$2Ozmw8|81H6IX?6B4lM?m)DXS!_Y8cOx*pPG=>3&QIQxT>&)h#;
z-m=N-*ZFqkU3)SmHdZc-5b=EXX7hwIMIL>I$L>|1VnAPHiuI5U*q%Bf58L1)W%!+`
z{-n)^>wlZp)_(~CpHa|g|72c8_P>K+`+sR>FId2|lfcGtNKX;eTO=8ScSxh2the}|
z@P79H3>U61{Lk><nEXGj2IxlWQDt}oWTnE#<*j+^l(ujGsMl-qX@|$-zJF@zNd*jy
zn>=lj8qCpWJO<SeENB%FGRABxVqSTVa_9p579!{_E_Qp=P3<>!Y}~$k-lfdP_f?lH
z%iw!tX6e>5&+5;*!}H@~!tDG0Gd!7BG5z1c@c3VvtB&nm5f^1PGczHf?{(mAvy&zt
zXA0@Ksx0kd3%V&NdhB8E&F2ydg8N%c%(rjZ{#&J+b?vUGHJOE4YbGo>bX<dn<pi7C
zO>_R4`}f@3Sp4v<(VLi`6Fk-z7wFB4SU$;;WszxzmDPq6YZ1*`Zf=ghkK5Fq?@ViZ
z$6NO3o@M&wlG*}KnUqCmu3Z;URJPQRI6kN5c6qXH&rI=vYbN#5_fD^rmb`Lw>1}`A
zEqQGoPiMU|Np(x!*s{ruL+5bPW<HMq#w$@jqTRMMSp=Ow)2p<jU0i6-?MvlCKJt~;
z-;J8e(?6*#xwOZA`HSn~;$ri&Gv5gcMe40j+nKZ?Vg*}x5`*4zW?A3DU+w*--0}Q}
z*J^J0H0$J6!))2!qenJ59KEMHaj|u7XK#q4eAV>N28NP%7pAWCO@4IO?Vf7S(*Fz{
zNB1mkJQ29mT`zpz?!|%UD%4*wSbJ$V@A^1zVYhchOM!o3;Y$5Evr><K;LI(4vg&8R
zhMWzlswWR<x!EQ59roNaJMiL~{5)Ni&GR1JvrO4G*?M7GfR{`|5$AEo%L^88PYHAd
zcPa1=AQYEx%5r{W*3T2ZaoN0IsgF<RBqzmA^I$99!}I5LQ^<pSnfIp}GTa}YRno5Z
zE=-no%uKmeV|c=Q#rA~8#fqIg9KGykCm-K=rr<}sXWO}FHxApJF5G@*+M{=o%YOO=
z3+)z<T{|tt;MS212UV`iXFqzIq|dMVbnd*VtiA1RYrb|ajF^*N<P*g)#Z1tngEe{X
zjNj|$PhYU-qw3S`9k-n$9+(Hm-ugTB)ZC`Km)vWgTYfgoF74qd7OUFEV4_o_zvSgx
z>BBtlm11XKRQX<X=2@~}dtrK#|GRT{gd1PZTDOnuLik(eH=DN<-||jL%sx5G;=$y+
zACH}WCk1bH6VPL7Fkme%o2PiKWIm5m-n+-U_UyTyzvl4{U%Tpl)gbS-{|rHW=N0~*
z3}EK%I(<d)?m{AObeO<5>9fn__5T^R*j>(lR-X~Yt-XG3`%I4etq(r_+xk<&-aL+t
z|BbKp+xxk{?SHx7`gePOb^W?eHN7{^*<by$<K=zHXB)q4zsBCb)w}wx6X)9GOKavh
zi||Vb8K0A!Ze$>-ar3c?h~!VByRHnWM<2d5;=UbyB4Lu{+j&nPrOtCOF8KZQj(K9U
znKTav3r{lBrZ+W`DccHf-aq>6aQ5u#e6>d&N47Og7BOBlK_!GI`PT1)3>%-hiCzhG
zkSu(;*}gOFYF?Dl#OS}%PMNAq2~%8JW+Ag#Cpq6jkct1?0nk$4VxkURgLSNlI(&`j
zLm>qZvY2iA7=8PwjDbs|a-S*JiUkP_><o;@w7d>~nDaU2#dm(2O<s?K_dA?B+7Y^Y
zW=Qc34F<jgjL}mV(2m;9Ua+nnbwMX+7FPssF^OJm!uafj4%UI3LkA9$P~+8^tMjJw
zu8880ySr|Zv(ej(5T;Aab3_=YOnYI@AGI^Cu10yqVcFkWKVPSp=ak$qTKreedSls1
zv1q|3q79n2_-`&&X;sc(_q6Z+A`$P-z4DgNti6Y$Z=Mu+apKLYBNNJt%r*RsKU?*E
zT`0G9+1XXTOOLLIvRlZNKkZ^#u$I2ergVjx(<fz*uPw@4mUVvhtyj;z=8EMDaNpFO
z6|v`bMcskiay$9V!womWlDG63PZfMACwn#bk2l9|tI4;bvdU+*xSY<>WuKFFdjqTS
z=0`OGze8l77&1CDl!;Yso4q0?Hu`3k*mUDtcBf}NoEf_?XJR|UQ@@ZNdFPkm+WjB4
zO<x(2Wq8zd%7=)^Tc%sI%f5a3sjMMp9jVOZ%qQ^9nBjSjyX4*2R&coms^Ul<#2H)z
zEg&x-W2)EGSFUW??HhGBaknRjJHPZ%?V~EWO-6k!MstKXSyBvTIYp<V*6fpyL`_?o
ztk<8rbnU|V0ej8Xe0S_Rw$J5KKBI?9vxIfU-4myt7cgv?Cv!<q$$!JKm$G}V9ZXd{
zeB4;uOTN(h^d`-;oJmEVPoC|u6TJ9v`;`TTchAk5x?}4u^YF{(&I|A{u}wS~`1|<p
zCAE)Z{+{po$|yEBr^zDkS@n}?k8F(|{q)>A$DxqNN7i}T-APCE%;p|x4!l?6xaaa3
zsp!AvZ?5}_uKjddRON8q1y7TU`@H5`a7QndVVn#q?yY*$58X2FFz*dIe?C&l;KaV{
zMW^OGun1y)tFr0cxnru+*=J39e)v}Ejh&wrCdNH`5Nos1U!{oCC0n4RG~q;<M(~!N
zp62g;mDT-HuL5IVX>5q9Eaz9<*F7btbMX#uPu}xqzuWvwR!+BzNGiC&_M}d0mz@5#
z%drpUU3>Q~+9g6~Ik%w4liFi1{=IVhdoirnLF<g0|Fm+3EPjp`uM_jrCf+?V!DhY8
z#(2NU&)oIZ(!zxd(yTjl92JBwBq!k-!;C9mSTX6d_m7HuE(PY_!kgc0<uG4qy~NOW
z!VP8Z-%}qXe5!oe>%Cs=73ZVVy>{2Gc_wV#yM6N{mdkmnMx0`5nRS=;@9I#Pttuhp
zl0I=y0`nHwfzzvsUzSa`S~_p3lIOSGCKDA)r(R*5ocG}r2M^y>i-dv@!6vPzL{<DT
z{@fWCUtW&Tou`|2`SE2Hf75^2DSV>Fb3UllReiqR=>Dzt$v@rx;2DmxYnLwBcI}~x
z-sj4-!o~(#Ot}UR7^2JG{Mm8v@!Oi%HLeez?Ag5e(t?c}K3tu*(L`Ig=bdM_qfpx+
zO+kh=#hc|zKY#inK2K%OwvW;o*)nXevUkUC+8MkddY8xhJ<sjZbn`Yg_9dMUJHXcX
zVc(>jXIll%Z9HA}eW&-%(8n`R>RsHCd+~X3ieljB4aX#&IX*nA{N~%Y_sKFF944)D
zH#E}x%qV2crh+*1{k(kUBiVG%4@cDAy|Z3@`fS;+bJi`FpYQk-s<I>htHzs8{CB1@
z7~EL1*Gcx4xSjr$H8!THYhp4#{&`=_GVSx~DC<p}JVlM_hKqkjY8`kJS-zRIvy<Va
z?v`k6U)TIck^ipf3Z2<~=fv+vPG0YLju<nY{XA#;naU^ET8n-~zh*vuYw6y13t6sh
zd>Q7a*u~z%Dfyh|^h^n!DLEe}aq;|_nFl$l9MnG~cEJ~{zd}_1n7aL9nyn&x@JD=M
zmT`sn;Y-WAO=k#xIh_`<xa-U+W}!ceOIRSAr*r%l-3OmO^0+rmLdofqr%IXDiUlc?
zeD^Uh&$$-YUt75JkKu>5g(9<a-@eu1eIzQ8A!piqbH?AJ{S{NTFL4oKR4M+ozr*xy
z^ub?ed*AN)R-`tywzfpIBmHD`!bOJzD{i;VonRkk=6}qamEoQJL%FN=FN&|*zdt+u
zKZ7#nc<{#erMc<eJFb-6G}YhYQ@@$(&QFdu;qsCX9?CJvS*>>(zfbT#6H^#HPj=_-
z%F=G`-7EFZ&8^aXyklx$%ETy+)YEUccCrPri4?F0PjXQH&(KmG@}FVh`I!F<`_1D2
z^t=C2zP0=>U)A%!KR5kncvAI(h#~s*_QV`Tqr-Ti{*dje`U}t3)!(13|IdBJ^NabA
zb5)LQ<`Gn^RGDNg8WLdSsdk@%@m%)&$?@0o+GZ}ly=|#Z->*rh&1P*|^zi7~QwMtP
z)hQijJDtn$?%0LZ6GMpIJH=2s@x}JbHYdgVOs7}Gr>xp|19AkAJoE^lm1rS<t^V7+
z#s3*N{cr5M_z!frGy9EgIq_fZZ_cZ`^Vt5iUC!6Ha|(&vC3T8%qg{7xcE0Y><9((x
z5<0n0s!Y5AK0?Oq2LoSm5Nf!r^Znz${^-NNRi{_DU6<-_efPD*<L%YtEz?X|7WBwW
zvac!6Pd^#pc5&)jZ=yCsF-T2*vHcqOY@f%G;EPE-WxG~sNUBWEZ(w+CI<G%l_2}JQ
zHNLwcC(caw(`8zCc)FZhh~|UIJ>_fm%H50ja#rlnvv1WW^7e$+KKpr)F<;Gl=j17&
z$KNM-^6zuMYn|n5bvtO=jt^?HpJi@-`Az>{zwMH<#&?~j1s&7lxW$tB`4|VA<ID+p
z64D2({C~J__5UUF_5AP8ss9;HeC>baEA{WP|K@r5!dcrlu3No4jq~wVj-Pv4ih@M*
ztUkE=`)Ma1tXFTFbhD!E+`D(DSpPjSxZ^33J@1E0;N+9XJk{0ukxx-{kcI6thtV?s
z8Bhn%*43jOorTgOXSKfTB`v+y>R#xCy?+mG?^q$hqckaIyRF%=!#$teuf(jYKVtt$
z=EMBItttN*E@`iN0X}DodH%=ge;VHIf1|zZKf}u$(+e1V0m$wdl;cRz4AP$ek^fJ-
zjrxCv#7O%uU9WcGKVbOzpK{Q>S4Z}L<J$F~;i7NoJDcbS)jQv+%|G%>`edf&EatyU
z1#Uc*GOEa{3r{@1ejVt33X96G_U*w3Ce|PFUh2Fla#^JA*8NHjmv&Bae5TU4ZS<
z#oHAte!A(oKgwq~T$pKNr}*KIe|p}vZI5i7R3jcGwJZp@as1uo?a~#;O|Jzy$kf;=
z{HV{*UV7X0ku7iHrEPyZ>$fV~g(+pUTmQ?Sc%yjU&evzdW4#}4$`*XJIR3)Fn<DE?
z{Qs_MO)3uy*O>in+21$O40$=msSV0I*42If=Oxz*TI2Vh;jeV2gUsJ6_j&S7Ug)TN
z<eM^W!!6wj9;TQ1euyL{Pgt_x!~)@lpU0m4`*`-`*7@zzr50RC`KZ>Des7ZzZ=y?(
z)#L0vPQHDQvmVa$lon=x8dEkUfSuTjRfth1r}&>?!t<8@3~#j6|4obycXW`!JT5qR
z{*iyIJFn_|)wBs*T)Xb9ibrf|N`RQ}?!y`d60)lb4m?<)%n}~y%24ofWsMnVX;SH5
zo~X0Sk1z9>e{1FEXoZ56bALYY`1AGodZzv#UVqH(yOXax`{>`UymiZ#X}9jEt(M+%
zFWcqJ89t<@&^wI<d@`@<`FiJETYO|!&~e?{_nw;WT`zOav#j^X?8WDvop4(GJh8{{
zOmoDK;&0W}<=1QMbp%vaO+35OU1`37pt3=_;@!rC*iFZ)KY!j<?WMuozwIM`!&+0(
z{oO~c!f&-Mikx1XVfSOgq}|OP&IUU7El<}RpXZxVf2jPye}-RDU+n)#9RAO6G~Ce@
ze0($7iOG~Gt7Drdy`J}EVZKhWqu%lrHbrg+r(U_|<H%CrDD!NW7i6V7=%il|CTYkW
z?eqzZ@dxno^gap2ZB7$hWjtc%tkMXGoUvKXdYa1QJCm{obYMXLq5j70hvoT>)<2Ps
z+_Kt3R{hvX^J5(X%?Iy9=vhCPeZ64Tp>vPl%GE9r`nyb#<@aOWXUEJFrR^*0${u|D
zEFT;r)j9jY@z$_=9*^fN>jIzXRr&3Qsv}F!w-e`AtmV#)4{nayc4^7}Nlz88`*xq#
zDeP45czL#n`E9_0_Qa-Ddo<W>CNW;~O-wKR)^B%-v+lA$Q|-sL&&kpodgt%iZ(UIF
zvw!8HV~5WBZ0<XE=n}Vg#OF;C%7TlYOe$F1ILY%*c6WE|m3L3t*sng`;948^%zJy6
z(L&vPmcS*mH`uK0|D3Q|wwZ6w<VzKPza9sF$ZM~!RG(Q|y8QN8<G0MkTe2b^6c~BF
zbdZ{Op69%gt4<#1e7XoB(CK~`-lkgEcG$kabsgj5ccry{wOP--`u=&R%#Ib)v<W<x
z(xkXt_ax^|uSv0f-r5C6cnaLw8(U64+$r|R<H?+?s)mV=ox09`JGseel85Bm$^F3&
zvZ~?H+$NvC-E!C$vfiem2fQiWR^ollyyeAJvo^-nvn_n2-I;SId$xGMwf9?&I%Y}=
zI10yXD1EG!pui<DsX=hYjiw0Z4SOzZsdYLNdGBSIx!IzyInJiLtT-hmo!`;}Ta_=j
zeaQ=}*8R6k-`e}`Y`Q4>=k$-jYof;@o*okcZ#CcX)AVoIi_BTIyR(8$ykDuaIdgTE
zo=nu8H5_N3KhiPC*>-{NO)l3?QU4=R%Qmn5VIC<IcQEV1k09%pkG8o?le|~)TuATD
zq!5mMPJNa+^9>RL*cW&wE(UL2&rB|tnY8|PV#OtgORP@&lIE=uadWFY5O-sx&X>97
zejY-{{kLrO5WFPXB<d)&o2_7n3|j&x^Gb$U&;B!P`zrs#tM2Hx{x9`EJnW8cPWsQV
z^52=y-=0hUXNdfqzCP!1*YeC2uV)=wot!Z1$h5*!zYfmwSo<iG>-N1Rfh;;pLt1l$
zLN^&t+|d@mx9Qno_wAQwzYUva2-&yZD+b=SK2OX>=}F0<o-eC;6Vv{sz4nj>E#x<B
z-sf_A>-p8Zoy}Kr;~nG5h&%xB+R|%l*BoAxb=^7WKZEn8Yj4&lZTcjft@1i+{oao|
z9-mK(5j~t<SbC^|_iVV!<)lmRRGZ(-3O-u+cS*jOsjKJoY15p{o)|T)E8<o*dM9}{
zeEZ%HYu6szvdi>)`&(0oNxn57XLKtoS}&O!I<+G#d3T|#zq0As7vDY|UzV{=+<fyr
z=h8>J-<zM~;I1@^Ju_#~I{RuSkJ?XmFK-8B5_#C)J;pnkQ8`v_)AJLVJzjDpoYZ7}
znz!bigY?`P(~|E@s=gNAgL2QtV)EKoq6dG3AG>~i+C15fSJx`%ItOguI`Mf|&T5ry
zpHFQP+*t5*?Hmzi<^sijuZ@c<-sNUJb~nrnJf2zi(NU+jr2MGy&D!-`vkhJdta_)j
zT;<OWNd?)ZqGx}!AMst3_02#h$R{uNiQw^PT8q8Xx3$?m&rC4)Gdl3Wyk=ct*RQ<&
ztJXKIEA^h8@op=}`n-h(?$4|q>OJYuFmyV1FobcUoZp=ZmI_SI(HegKLD#>AeF)vQ
zGB;Ot-9p{BYm_)`j>OpBDHK(U2)$x7$td~6-3k0G$JzV#Jhqax&YAY<R`e;BpK>YN
zH{INKdHd9`&KW|C32sia7~W{C%Rg+VG5d(Q(CQoRxy+H#Sz_z9v$;)@JTu#T-2uS^
z-4nR^Dw4Yne>CqYmFBJ&iF{d@w|{fjvy7$lLPOdt*5=-w$<XsI;W~$tnd8q*uMD;@
zzJQJ5VUFNYaa|V7lH}L-6uKR94bJA<T)cO8c2Yv;(~`eeCgpK-ow@(&V}r%HDlYqn
zS{Jre&c9VqX_r6wdCJe~edoW;dH;KN&HVXgWsmn&tTbIKlC5-d+P`<ls<r#KINPr1
z*^saMSfNvJO4BCue6PcMev~ggou~UYZQi|$Nh#4{)(_HuYi{NHt7_5Fdg#Q?Tm1J<
zD#)@;UK^QR=&w52|6jlUWF!Av6~6wh@vJJL`MX|Km9ME@FC7_moN3kHMXzEVbN;Mg
z>Dky^{w?>D-5K{2N#+U0%37O~OT#a2IWO{J+V-F~8?U_I%DrvpPV@3-`r3l7LMt-f
zHq<GfD^oLKKl{CBVujqzBf@*n-d*#yV0w9>qn5{Ht2<jSEllgT7K)T-brRw~JI{b|
z<;uG+SFg$3_Py--rC3*uS+_iL)~WQFr&esbq%=iddxv#D!;{C&foC68d&i5~wU<nC
zsXNcI@lH;$w8?rcmNf3Ie94UE2KV9_Qi|1<FaJ^Jo9w&m%9huXTQyY$Zu*<9I;pg4
z^(m%(oG~nAGJWnVSG?b&pSvRaaLBB8Z<waN)?GA3&?{l$($3jW?{V#(_A`RHfkRoL
zLH@(^7isr2C%yA@x%MIE$i(PVpS)!bo=Fu9*({_yVJgD}fk_OKtA$^0>wXwn<Cw2g
z6xpp@Ei)<KHRD@8%R_I*{%@XgEgxg<UT=81sZ;&JSI)Cf_fM3ab>~Ef?!wMAmp*er
zGlT6yyq8p#^jRdy=J2vd^dC0(;c@H6`6axzCO7k2KOePrf68(9n!f53^Lq;7%F8?!
z@OsqvXO=!%a^Y=|r~l38)4Y58l*2k7IdvT^+j*wN?3y)KLeD&NZNB4&zTK+ZQ|giT
z?gVGS#wbH)5w}XQ$jG|bCz}`K&+L#?U@%~N3LlS$rBGyA^!&a0lg=0SzY(qf&#*XG
zdjUpg0p9JC`OkoH%jYBcpL`Ym{|;@ce<^ykgy<ES)SXx&?%XqyXCoNG;+8&=HTK#O
z9o_k)dYhxd)~!w6o!?S=pIKa;qvmFwEP3FZ$70Yz@vu(QqpOZx&--}$Hm9TJbFbGT
zsUI9~?!B_j@>t>Iqn`K<EMqwTpP^;+aH$30TY*qd)uQAuu6oXh$XE3|HP-3%nXGr$
z%nDuhBfZC?x8p+3$_Eb`>bY+GJ9P0s!^Zy%o9s8Oso!k>{PdfbPyW8WUo2hs-PY=J
z%)aThg^3^f4;w|DeClhuY<iXo7iW*pg(GJcJjr7`Dan$;(_~?;pMFKRZ|>rwk2uw*
zy$&{;bZ<?--({>~m;AT3U6%W^=u@)1a-Z?%3EZ>V+XC0T(cMz<Wwl05s<Csf-K@<H
z{c}16MJFt2c+RuN?stliqu}j~S>L9nW-oj3>)33u`RVzhd$`M&?YZ>Ug?n1*Tt;=t
zhwf3!7rd_Oy|;1M%{wub6K8CVc&aKQ8FlNOhH}|~hh5Xu^F*fEFg95J_~ZUa^N+3C
z8q?hQi655E+whS)<NPf>N%b_I!Xvp)8%`~dn;mIT&QQgi@vXe7WZJH|b9?XKDzklH
zcKGy;iB7#orOUsIOR6-iGAazy$<g_8+TzU{U4<=M`>hq545jou)wwJrRpuYt`JaJ1
z`ZRxsO~R+R^H%#-%?@&CQ2(XEd+aLvV%8_~1gqcaUI}0fy>{rV&E9Pj^g)|um6=oe
zcNh1&S>IP*dFS4;HR1A!tFoMra&6zf`R}x6@2WGHRQF6P5)l&ZGYfvMa%$tGXFkiG
zOm%o_z<41pBg$@Jn$G)@)zY&Awfz)l-IZnO@l3zvW-fHb^HsTgl&LMZ`?Wvo-{xu^
z`_FLl{Pb_TOQxq4&dFn!Jn-^`cJ~E+8_!kIKk~Ha3wp>$UOcz3P$#UQtz|(olgvtn
z?Q^H=$;d8G=vNl`x?cKKV1?J^xUOd<JGx!AUwOWLYu{akNY$VKpUc~x_1^Vbb@X$O
zxyq&l<~=)`9rucxi5F&W?q1z6UF_2;^SK7SG3>$L=eTtokSkkZ%dpa9H?JJGwP(p}
zZ;7{IYQME_xizvB2|Q1XGuy~@Tt<dDrvA^l{|w(v|1-Q3+x+;We8=(+UuJE%x~;bT
z(6p+<M|2n4XY5FsJHzm};Pz?ES`AgXDF^Q`zG(Nn9CcUsw*MB$)?CqB8#XX5W|rV^
zTA_X6t=!c4Vrw5p-~P|A!Fff-<$JL<<?-pBi!#*`x;~!VBD0aJ<KSLVj|W^&-o1V5
zu_v8p`{p~2^^drvH5W}#kn=g6Hc3NkLC<kbpXUl%6P#0fW~H86n!eQb%*U6TGwnZ2
zJkPMTBJye3<lvOZnnMQz7Vk*dE&Vsbx-owO^NQInmrHqdychqSboJSeSTF9=5m#29
zDX6&=E`50YsUrfhlG6*$Wj%?qo!ftV`K6pUIqTOOee&CO`1_<HXAkkr8Zq@roF|{8
zo6dhY|89Im-${$@+pb2R@_+Yp!(r>sSDtw;$*amcaDaiYsX_B4DUERODVW$tG9?Rt
zWIMKd&-U(ixg6|2^ZV(HZ7Y<@9#8X0m_M~rdBc}AKWzk;%I3*N@f+QGcJKa)EuVsH
zqW-iQTztwIAlf1L{M1R^4I6c1RYe&4vlnPp{%5#V{`s|CjxYPK8nNdox!*5T7OI7Q
z*xh)-+BG8r-&Jo7hF^Z>{E2<2&As}s6{l{gwntvvrBY#qJF6c0xk<CjJl>XdWS3aK
z`Hh;pTF3m~{Hg6O-6g*{S>n@=pN3njlHc`vo&SJx9Z-n~<LR3fO4q%9=gbOQTANr}
zskP^Nz!F~NRqt-~#HsP0-l%tQN%Hr(tDXM|&NX`M_gigkF5CKD@phj1Zxhp|`Q-8)
z3=A*uQBZWe#jv&uJQ539naMQw-BRA(Yjg9pPQ?9taQjFI51XK;Ui7@#$%)4*m0#(F
z+hb`F5OG`;bS)cVQ3k3pqUV3K|8t%v{GVaNn)$z6ONqR$a5yw>1P`;Aoe1Js+{wLp
zsw)?_u~_o)q9c>4C;56t)Cteao-6n8`83a%tnwF<H#Tx@FV^a-W@TW!!Ju74#t{(&
zW&<Gu@}OjZ4>Px4SZC@j&-QYb+~Nmw!yccw{AlwIf3uU1C+8$eB%D7rM{e=NTWcyO
z{%1)3&yZ4oX#2i@XZ|zH*WFb=`TO?T^Y;1oo-dEf-ms{_;`d7BeU}$pUT-ITKPKYf
z_LJLYmVEECU7Ync*p7`+A$h?{*4w(fZ?8Xm*2Cf3>#UFc8*(#31U63m)+53=gY|{E
zeAH`=1$=R`evj^bdiF`4F>B-9*xcVPC$2F*y=Aa_Moj7k3(1#Z_74@W+Q0C*ZvX!4
z^#2Shu));{ujYSI%bx%J*XjQZleFfP=kl#ITPc3{tfwjG<dp5%-x#&m%NYM%tWvZ3
zpl$oo(kTJ#`h3d^^S{+AABb8LpVo1Z?bwERE#vJPJ9hjGe-g(oukl4RE>n3&*DcL`
z()T@O*Z8vTvU>T%Ra)<uD_i|kuRlxpI36!86A56~|GT{K`Op6h9~!gvmCt_ubM_kZ
z%Gox1fBtsAck|Qpb@!}7lHN|c`}X?7XG;{SOSe`WzhSmTizDL1Z#OQ6GfZEk`$0GN
zvWwS6{ktFN{J=NuUag~ue|g?FPRkVe-39;Z$`>AVD&ErI?xm0x{bOr(e|vdRwj;yj
zfIexKiL=u#IZIDEkld4JA(L`F)0Ls{m+iNeOK<M-e5hOW=v8Ihqi4mclV++UPd<Lj
zlZ#EzQDv3VIzQtu-9Pc=<+gVWD%@i#byWq<*_<}qcuJ?CxbXa`R~28so-GwU|D*b!
z^E@3;2Co0*n(e^;N5yLSU(Q+2|Na9_hjyL6ruVfr@7A?b_FS*F-T!E?dFHcu*}feU
z?;KYa-d2{st9^m#jX-P{o1zUw;GKbDM=PB~sdd`kXz{fG$Jx|0>YHIyDe_0QnM<`z
zWii|MbCTY|R72^8L++&_eU)EAli&AQt|k8%9N6Lv?fD<R|7o|0{LhdW@t@&K*EP^C
zK->Qeis!}ZZ-m+ZRoV(UmkcyRf{aPLPH41(btN>4P<j8@@hfZVr0=}4id$R0+&{Tc
zWX-irMkcGyK7FIJM8H@f?>|FH;T?vOd1$vi{`}AIt!&pd)7a?fU3;&+U#FX!6e>2^
z=UuPLCF3n~wlSwlt4rD?T7Lb-)WD^&F8+~8_@o-E>+=o=&iCKdba7qKBQ~wqPwPIc
zP-rq|)t>X8LA-7XV>0@Q?D0l5oL9EKO@G97xbTsz=bE>=&-YBa=G|WLJk8oKWSjA>
z*q;Ya$}Knjau+-<<IW>+ThT+QPet!ssECHnnaF<G(?Xu_JWW+a0vKa3&ve<B^5gBw
z>|5qX#M<s3v6^)A?(Kt>vTMruCLTCd)}xV=UK0Jev8mQAgZbqy?dd;?MW593ZBgHU
zCH;!t@-5NRcg*d!uH3(e%Ts0U!lvi;hi@+}g@ksv`ubN@SNnEsh&o<&?YsW+r5oEW
zoLcaAMfch_tIGIQmg_mZ-aeu5TA+hmy4w0jpBKm8xox)8(0o<Dag>Q&h;_`nHnpwB
z%==HXm=rgxF?iBmqB8&3bfd#7S9unfiyqT`6LmD`is7Zx?ZHYqCwLD_d^)#-C*Z-8
z@MVDxGV!g6`)civ8aWoO^t3(uGTVEt+wC`#PSl-bV!M^dz;G%=UZa2d;^Ns8ZvR+y
z`{1r!-i6O!FVpPpuKeiT{^>tMneh{+{q>tQzpE6O*m&0#E`J%|o2@=wIZG^H@)nsT
z(*xZe&ks$LyZLz5jRpM1Hy`y@M_=wevTN$nIZ?B1#5FTIKCJZqv|PxofJZ-L$)-7C
z+D952u3Xq!FLFO?SMn>f&9{Gkbonl}KUI^ZVC#yq$(54A+>??%oqnQjZQr*W(J*G_
z`_FJBDC)IQX4x#Yr7O;h?kN}Ay4qn?x3b47{@GeW#lm0Mx4Qpl;N)BRpTQ|@=YNL!
zHT!=mb=&{cs5<|*X^s7t+`A<rjG*hQombUgn7OY0{%iez9*h48$p-&xIa~biKSN~w
zC)W}Y$ZR{RDg8e@O8tKco1XvuH}yZmNzn^|;7N1T8Wy9W6Ekn_qt0t*lP6tzAACi1
z?-el(T^EmgF5>=Tk76epEI6{aT=u|&KSvm1{xh_+gVr(`gVr)#i~lpx9j)?SU-<Z}
zp8h@O{MzCylOLs?dJEgX7e;yR|Gp-o`9RO4262Tyt8V0O)Bh8jp15M`>d5<Eo#m`O
z(+!SDS-ev-eA~M(_wduH65GrY9v9YVGN3s$5F^l5-l<r*&c=0d#7*aN*)6~3eA^Ub
z;+3>R(6R8D(mb!J(@f<Jf^K`pp5k0BcF**3+V)BB9&zusw%_Qv;$X3nX7ub3uBZ@>
zGY1$x&Rr+Eudwxm0)r=p9q2)-_)(+n(4%L+J+G`u>3rm}eP(jn%q0aATT06Mb)M*P
z_wHofwvuI1#T4gMo=GpQCdHjC{FbrhTf~v|YKPTCxBqmh%sRWn&O&?c<6H*JRDf>T
z#^lm(w=LfB?)moSCNIy+trr^=nr}R4KB4L#;Gr;^nyF;(e}?XNU(Q-R`}g^f)swPq
z8*MJz&rB;@)D-a`CglP1rCnX<i(!zuUg(XwSk~fya-h{4-S%&^<^N5L!oDh>-5%{e
zJ?;7EeOCsg-TI6eeZTZqR_V9jZ<#&c`t-l^yR+x+E`F9KnRI*3$A8-`pTB#&&#e_)
zv|`*Uj^4e26n%KDs*vxsGxJ^g<D9KsJ@<+A3ttuO&@T(Pqd!&0t04KOv(CbU&wHw#
z?QK5z>(4#S4|ChL+s##*_r2qs?%ZzC*dv-JLr<hKHXe7At-8SWR0OmA3R_79r;ESO
z{}k{g|2J#=e})&gy<TX~-}9egQv2fi8(RMv{xi7U0^Rir+30}Ln8gSua45hB`@`iI
z-^%)Rck9(R^R%w!?the6$>q#qHd|16=Ok0+5}x~|>_OSisAmSiu8jS*@;`&~yq*6U
z>T>q~l<P-bXZ8hhvl80!MzlqLpp*bQWv@SL{uj&F^S?hk{hwjt3yejQusd>*S2Hdq
z&rM-<yO-7H{-_SVRP$c_?X^j_D|eUY+-ogQR<<}-I5F}+!v{ick<0&W9&!8lgS%0G
zlaF4x)jnDIoxPDtMo98<Hupb&TdQ3Qe(B9l`IeAzUr>Mf_F3-&mT~H+@>@@v<;s4-
zGB5I5U-Jg0ZJ6N@`u<JsS6i!Rhd$XGU3;b8mU74KNrE#^pPQqtwmhm|(avmm!F>8Z
zL)u>BQy;$VTwQtdx9_d!%ILcHQ)X{Zw|Rc<nBlQ|KOf)Gp1%1*>%IBR&e@ON7Fpbi
zR8u~^*|Ji0N%7hJWodRdA9rp1&%l8ip|EYI_!q1)ywF%zPr!W(*7N^eYI5HE@GZHu
z&y(L=&(D3D`}<y2-rYGL`_(0mTklSuAAk|*q3>%H%U3vTxLdJ1W|HYN%Z5*Hj>(xv
z3Vh7JIn{rk<)a2GZf@yXW4~=1Hus<2y0ufW)m(V12*YCa$qnpL8$p-Jqpqwye@)l4
zR_NBXZ}y^D+wDIZY;JuxPujO{Qp|B_=54I`yPhu;VZ4Ew>+zj6VtN5(6(hTS`hNyh
z{z%Y8-0lB*cdu*O@w->*diam_Rkh2aU;J6Cbv*y3{_}0;Qg@%LSsr`W`nk;Gl`Boo
z^S{`&cJ&>{!bhwwJLcVKzn<@SS7fcQoSIFZllwNSk_CL5x}N`Mc*qO7tLAmge};o^
z-~VTjTl`PpuKvHet>^#9-TTk*@f9c%^87hop7^lp<Rebzeb-X2uQ!yq<@fB&gU1Sd
zMn#8vQo24>)Vp>^Zo72r@e#S&qkFD%9FE<4OU$e{LjHcb<<!FC$(MJqN5<@`i28K$
z!OqL27E1ftq94gUyKq{v@73e;sW&z$-dP&JcDIM^XQgxw`YqP(e^76^X7t^|&y{hj
zZ+d>Ml4I#Y=S9aZxk)aLxRxp;BOo!++=qYn`(tstm*4YzB&qXe*3Yo_p&PHLw7+3p
zJmtuT{QNCFi`<l3=Id@d5o@6u8M=!f?at``3@xaaN;ha9ewcm2v|BSgxZ&lrs@7u*
zWp{3|E1Z-%yTIt@?6S7GC!~!V7OPLn{*iy6prZIpw5Lw)w_DO4dOBNfEZlkfm|SLb
z`D}$-%Pm6H3pFZkFZ|Dd|2}NC+WC$DPA`j#?(UY(RGW6MV)5lQc4xC?CU~g28@$gw
zb4J9Hhg)k^@6zHZ@mpexSH38Uy#Gqfy!fQX#A~&tDO*w{7<p8;i%RhS+g$c>&fA|F
z7(UwkrIz30+LqVezso+#lx;7YaM$J2>+Q)(4t{qyPx7!C-+m^cK8K-1N^R!f-o*zK
zpI7b+dpu#cV7Xy#$4+bIn76JcZ!L85GmawiZt**Ef|r+V?+TxMM8JAMT9<FthfP9u
zFK=5)%37#Y35PtpWMi72y(;GP%It2wsk`5<{kyfUW{u0Hc{cZFKPk0IUuX5vLAF)&
zd4XQPVVC=+k0oOM1-eq7e5;D3{8B#c*(CO2pUeK;CxUi95t?tBlUXN!u{4`?ciZD5
z9Nc^IWoEs7k@3V`<3*vNWLQ{CljAW*Wwr)A)Qj$RaXt8x`Owzt_JMthbM;CmeSA4x
zZ;@}-$14+s<wBP#wr^yS`+5(NBV+zEwC{gn`RM#_uH*k1mV|A+5N`kQ{ZGD%&HoN<
z{Lk=GbS*;(yb272?5PFuF%RL~`JVyxd;p};rZCz63>{0hUQ4<3*2LF4aGrL>JJsy4
z#!xZ0i6Qc4Au7+*U+`x!+*z~}bnZHGQ(UC}5OQ-KG(-T(<tRgrm<`+pe&p$jSk}U-
ze+$=U?J5cTP+=b#?tR<4DXv<<>}a9P8jBq^Z=KlpS(UE!N9_ZMKx<{ZeE?8n0#qxb
z40eK&C~9*bRx2a>1ifPdZ7QI3Z_paHB8;D(A3x9U%YWpCp04h?XSH$nlolu^eAfK5
z&AsvDt&MYvivB$azx2y*Hec`Jh?iw=l^s*_W%uMNvUV+MWqH6jhu<--{?S>z-$&&X
zKI~hm-txy$@?yU4!O$HWrLQwK{AY+OsyXrKon6r1kFn`!eH2j1S&!D6lK+6}bLIt9
zi$Ul~4yXZ%-ftq;O`<aUw0CYbFn!<pb+(7<j<);fCwaStWTr%1nJ{^Ca&ce71$Iy5
zA<3A(&;LxZmHu}y{6E7lvrD_Up1-$$vhc<IZ(RHTGhEy@1%8?qW?Q@XpXPrCw_NGa
z$^UFi?mGAvxrg>Xn#T06G31PFrvgiu?S?8Y2G|%Gh{o8&bofVp<o+#}-z&5qwp#lp
zd(|t8d7QdVcKK>H>@%bL<}_ZuJnIHV50i>X4t%F4T4F%!ViKPZitBXu@7_G!Vf)rA
zk1x0WTc)cz_oDRE47G&SyBnTPWtvx)yOYOg8CqTxoxaAucFpPK(*10&by=4lKCNP8
z+P&u01#eC#-gAbX#rG|aSuWuCayB~hN@=guiC1wk%D;VL4H~)ca7XWW=sYJevaMXe
zpxlgU?o!LY$-!6G|6#Vi^J??1*Ks1dud4WKDd^r568p61Q2OaaYt4JH8^n3|Jl`l@
zd8hmD{F4gq(C#-EB@}L4<9_N^_EcP4Uh7ZyfyYnfnpPiGDfqkl)Q|jH`EPA?x3`vj
z{5I#gUHbcfHSh9v{yu)KL38%(oi%~WZ^g!X7U|Tuf2&wBF)(8NH)l)r42DVP-d^6v
z#=sE#;d^I|d--zRzo%>G=9hSuiqyt=hivN#P}WKk*gpGP;WM+xY7q=`n*6Hx-&*(E
zgI2q6hko93-~P<q#NB6ZK7D`wmfg4W({0N>URu0)cdp%|SC39Ve6}>#_V)XoljJuj
z``lF5b3GREwDaUwyDf~#hrUnmFRV^p5tHRx$mME2dF9bOb(f+CX1|M{PEj*sNG{Mi
zGD))VQn>oEyW4v6uKkKXeAeq2ThUwD^*5A)ZZNCp9*{i1Y<FlKdBrkKGc{&au@m()
z8uZfR_(!$P_2tWN9yD(&jn=pwdU><Wr>H4DaZZ(-#^$yb?CY1CFy09aeZT(Am(!N|
z`tKfW+1fAtY@VZ(o(Ho|g`^7qu^qMfkNq3B_}kiV{dd2R@BW<|ZmIX@)ZVn{c_1@?
z_D0!?1^f<+R=%{FVs)-Jc~$h9Zq~PZ$_3XnuyMVTU~Y0NsP&Cmz|^H>`MmAgz3A@F
zWbhs+kAtBiJd->hFj$^tNc?g5`K2`r;%8-+M)T_#p0+!^;z<tQ50^5#t~FK6v8=^q
zm-Rbs9CPbACT^K)$}{b<NzUrxf`^l<gcwsix)a-;)Ne_VIX>$peEu0U@yLvEKeYaW
z%t!VDw@vrWt>s%Pw|&Lw`eM^H7gt9a-<c9R^*~t9?gNiZRPwApPB<Iuih3;)!>8TZ
zxna4|ewWtheAO_`H9r(SjpuE?3fJ`1+^M2!34(nuZu6{hKRu!FY+i+vt(CrH_F~V=
z>6hR5%}+{hi;%kO|6XrXkl4ZA;(1)_B8(H>-MQ-$9#(ZYYgfs%e<@{~{`NhyoFFo}
z#8Xk?xmH*JU+s_MQOSp*f^P58x-~)X)p?7ndNto}afBNEoPCP-j8on%ZsDFe7Z}$a
zG`V%WO-^G;Nqcbl)Ty2v`%`wrY+rEalu`8r>+9+d?%G6Gw7c5hyngNbhm6TbSD)2g
zbMd(9&Fb8<dmH*9C6=_DSlZpnGKuMW;j)ZtyWD4g%gkT$xp4Q}^3Qi3OCGbip1Zd?
z*(QC#T13(Pd2jIHwrBqt;`jgNy?<NfdXCt=N6JbkrajfUl-4?>sbT%BbuXKoCLHH7
zj1Rw<m#}T`rY)Brce`%C9{TUpt?awewKHz4zq_@kS*dp6=9UL`F@LX_zMK-kKKuAG
z?rd3(*J0bQSA_(|P1x}AGh0*mOsSiTn~Xj=Z&Fk`cE=>URaN5cs;aWdD_s{xieG+r
z<@SqzvY8@>Znxij7w0)e&nPw|Wx?qp29^o@tHSE~SF3GZ9u<H4w!iG!yGzUiZFal4
zG|b(><B?!E@4mr7n+MG8|IW)PU8{Ln^7`53JR9%lMt7plvi)eA`gGE(hyK%Ia;)2~
zox41tASdIO^o_WT?FBddMUQ{G`$gCzaI<Vz_eP$Wzo!egF|9C|dCTGC$uC?Q%qJdx
zxO--v=)B4;yEm_h{9$%f$JyogqCGA<?UlaGl~~3heZ5@bPVvg><+opc`mrwM^1jpa
z1u~~^y2BkTWy5uC-KWYKT&LD--YheBzhO?g`bC9_payuGhwKGoSH++c9>14oDl0E%
z>37Pu`yFyg+V`68>*K2P=Jn0$Iw@Eh`e~XQYvE^p-Gc|t75D8FVLW;7rF`yHalehZ
zMf%#IeLvT#x2MjD&I_wl6=wPS>_5YdHFe1kmrA<asM*(ic)s20N1fN7wZ(>17V(9C
zi@JU6hV6$JuWBVDO4(N5s943)bklxQX~dR~S`mM@J@Qx*GP|Pvbn&w-YYxTVop$TM
z_Om<IpO2a+H|dzKknnP66#?aw(yp4Pm#liTsXb@z`Dg5RZss1>-MM)Zqd&^!I#)rP
z^!EQ$pQj4yC13y7m4&o)U|s#;`=4Y!rvGhC25s|;dVw*s)&M?_8MK2M8C#;a&tv|h
zZ9hb81l;)>Wn3No*!vgE3t+qL(P-xO3pN$K4{rN9hi%{Y`LfHuOO;Wg{@XYfJ6pT$
zlsIhFKSLq+z_O>$c5(k_5Q=<xJ$%}w<JM<$MYqfjbblZ9D7;H0$m3`CGP@j&JDdtB
zJ=Xk8zJGh=rmudr@vb9VzgjPIRMhM;ffE~7Z_cY^wo~#EV30R+JaKSEMSYN9R@J=a
z^|DXTbf!M#wf0N>wC}97&zfYT%^v1<ks)nbOZ3mUGGw?v*3Miw`}E~f<x1K2H(0yf
zI<?O~>6{s|x#fV<@xp}ViMJv|b$8+$Kc1)Wbz%M1Uga3`V0VQprlvcCSH6tjwZoA`
z!}+$|^$@<^Eke@YGmg$l*&n$mbN-E6Hezz+v!CW!a&Htb7Q4|sd6Vh6D=~9diKIL>
zVO)sZ%7n48%v$Y4t;x`~k`guODLQ}M-MEM!)xmo%ul;wimUYRd+lM#opQ*G^Yqz_)
z3S;BR1-x9^=icvAG?{eHWUsedcKuuXP0@EWqo++}5wN@|Fq7wq%^Ln`XAW~MGS~6w
ztCxGNyC$nD$LyNfW!G}qJxWg}&QrKv7~P&REm3*(nt2JTNz6|r3l6SezNp?Ly}B~@
zol;+hs?#KQrMB=O14s5Ij>n?s&o9otRk~;O!@F5#(wu#_Bi(m}<`jqpyw+fuJn5NF
z;T8siil2LeSN#mLs`>tHT2XzDyR`j#(XY&ZSA6uCkT+#2*T%NeGtD^*3%Yy0&02fE
zW6?+6DORP+XD+j!{;jj_wDjB46Yg8?bd%TP7u;v{=Y9zT{#&N6+SVT}&e-+nhUJ!?
z7`u7Xl5*O1Wajk*w>-(ylsk6d_wGhZ7Ov+{ezdM!*IQmM{Bk?T_SL!1qg9HcZ!HYZ
zeQUTg;wj6j1$QnO=q*`ruj7DhI@&eesJ3rCdGfJsRc7LqN#`zQSG+TGUv_Kro=qMl
zo68$bibN)e<u+92@bg$Q?c!&CRh+f_h_LtSTUje+&G1;4vq|Chw+udI>H7?ZISt33
z-KjXI!Tiiu`qBI&+P>4I%J$b5t9)wcG|4Vi-krc2thBlKm`J&;QTFve`j77S+?s#m
z$UmWtW-GOv3r)Y|W-2poFP;#utnj?(m|JnH#qGGA%U)XLff|2t^D~o~EzA0@iFSG?
z@Jv|1^MG-FVz>r#|A%MG|4w|M>m7C_@%W8*U%h8{ti65a*y)uwr*d-dUdS+E=eM=p
z#N}`4#M%%48KO32NAF&;YwuOvd(v*bsaoGBFVsp=WMu4o^6mYFr;92URhCxwx;yQg
z_vqgx?f|9Dn<AXtE^WK1Tz&oC`e#!Ur~WK%;=IFPb<)O5aZ{UT$y`tUv>m@qqN;V0
z!Y3zA=DPi7k<He$JMuE3=RR&*+<o*~@!ia68*bkBEUbUtD0PH?(gm-HXH;@;hbJ38
z5n7(e6)}bP=*b25eHR=~)Ng)w_u<~(Ibm-zlX3+2Y!*AZ?RPxq)|nsV|0e3sE4#LA
zD&NATv6;p04`oBcPF;F-=WxE<e3q2+Izd8R+bvv!B^io5@**a9GkC74xD)+DEc>is
zsph-=8`>6Z_hres_AkZv$w{p~&NR1kM^j^$Y`gkw_o+|Sy~0PhAHIJxn^!!v{oF;x
zi|d}w<F+h6E@id)80)Jy`S(uvdH3(W%x<@mrPp*%&>ka)ca5_&xu!X}-?jFHj6*pH
zA&t+1CW9FL!>%m6xF!2-(8H7rowZMPOiX6j7!q`ZXM%C#D{a1fnaJCJ7oWfMHDcdc
zf!*_Kcf@O5cz5)0>b}sQ(%;j+-`D(mpKXgxc&6UMhq_URB-Cel@AlMfauC?@S!CG*
z*^7SW>8x#quVeOY6kECKKSTb1hNFh-T>q|LsyF-E$vtcL)t~>*An#oM>))K(dwV`G
zUW%z$bnA9VwR2|K2j@c3CEr&GpK7Z#t1R50BQyEg(Nik}_oVcg-TB=wYI?k5OSZH|
z-s5fagXdlIZtL_3XVTEKITCy_Xw$L9&$yy9wRbw2p1+f69{gkD*NqQWZ!?Z@Eml6C
zzWj8_dZ|S#y3%$YQd5pI6XGnA^khwGyMII=TP$dO``6%Qk)YcI%bsc5TbwjHyF;?>
z=Jt%tJB^zyxQr@Qm=|pR*xT^o%l5b5UM}8pQQ_*7${<6Pi5`;#4^7yY{w`V}vB=Hh
zrRwuuot*XW*Dl?3r6<f>@OI2y_xyb(l|p7c44jqRlA#4%N96a2h^lw*xM<_BPwwBz
z4HruzYTgRTO1+DGuz7k-;o?<$65`e!`}?Nl$&TN94T?7wimfdCyYxSU$gv&!bFb!_
z>TPpRpZKkQ@;|$scfZx`Nv?P9bFkvr<H>sWY>Te!*QuAYcvE#(uW?z@bn_XvB5T{F
z*)bwXMIpl9Ta)kAxVV3q`fUC3%<x0WOFdUcti9vaRN@-@w)a7+vr^u<y9b`xK4x3}
zGiv#_=ijFPQI>lCr?q~|o;^3~&riQumi{*WgU#dHvajuO<wK?)z82;GNBP!+-{$Sl
zFWTIRthtxvv@g%@>M@%+Z_iur>M3H}`N+0D*mIh;+GM}JTla1~56BcVs|b3OuWk8r
z0>{KWmE;Q|Jx?cBSbqGms6seu*5SCx5gRVPeY;hB*CdPnTS~eH^Gq@>3Lfy-)LPi-
z7*@j;;9LJFqjdTnf8N)c#kHxd3+HLPl?=*|ie%LM)+QI+DI>FMV#C623+?z|tGDNR
zS4GEG#7FM9y7hGZo0odY(Gd^ZbT=h)=*4G*Rz^S1pLsj)E6+j)TcfT%PO0pQr4=cS
zcbQFsM0HyFca=>tvMTWSqPAoK)6V@ehql{E_puwXOb)($v8Tw$fbEmuVNF*59SVI{
zFQJ{Akip!4?H@};blf%dE9**m3)5!jJ^Xf2-<8WQGxW{}>y6(I99XCH`&-7IzH@FH
zKH3Q1<;m%*HWo5hwoG{AF8NRR<?*Ora$O9MzvwgE%KRsHS!cc8*Wl9pOp##e+Psg-
zdMlW70u>mG_!yX(H>^b)*Iy0Y?%`ar|L3pk_8+RN|1%t4(S9(Br>b}FpKY7(-HlGU
zy>DTq>HSHb!8=*b9hBDEZ*cJO+7igjCnKz-;VKe<F&$&)t9;a|?mxquZJ+jU+Ma1u
z{?0qME#LTb>M7Ze%l=wd&zblwa@Xf)Wn%T80=~}w%^Fev;`Xj9mrXTFqr-PJri6HR
zzCBUE2%ekad|V`CyYcc;hJx&e5nE1vm3(7z@=|tezHi$h2iaTNq23x#3@6XgbX3~S
zzh{-Rka)LL+Ps&Ky4|HpKE8Un>Yn$CxY=RxW+z*ZPg?e%chicy*&T-sV^<&ebnd<b
z=#ZdQRr8keP0gAvyr!qWkaY(KqxI6MNx>&&@(TR7ReeDm0a<x(<-^0p_3Q8dZF~QA
zQua3P{6fKrDc(iXGL4;1IXZ-&4KF#U=#ktiv3~W7?FP|tH={B?9$j?%^{W32skx@_
z*6ur#6aMbjF~^B^7j7OZkk_kwE%k-hKd9Ynt9R!$H}@S)cUTzaUOKf=^GTn%h5BvV
zs?bvmpDVr`%uQY>n|1Bid#^6-OJcHi2^YLRD@U6YxW##txu`_kZtE>rvRHPjzu%=&
zjV;<rziMyIu9ZK$R%u3b!Ef8sCyiQ<d9Ui3BAMsFFp2TYY3|px{(jr`Z=QT+>#k0<
z)^8JcN-!;FpE$uis?XO;bjR*3ttmV9Y}+2)wylTZ%(@r_){dBsy~kCOWgf^}U}yh3
z&&GAl&r2__pIvsRV*0t%9b0Gde&p3Yt$Ov)e4QOP%6Zq$U9Rxp#>Fq@8}?kxd$?hq
zcK_SmFVrS1PO}yjPm<XAd)nh1)__FgEsc{WzYqyvpLqD;?wK~)HlH)g(*rht$nA<~
z>-_Fo(OFdI`qs+ON5FjDJHs8%gTDK3zx?!L%*o}o)9n;4>!<DzTV_%rx;FO7X9Llx
zk?Coc)^$lY&iOA1DL%-1b<ei%g6<|l3q6%5I%}_#P-s5LQrN}t;C)H|wpZQDBev}n
zpStRJ&9%vgH=Wbnu5B}^v#IWL{h2U(!w;8w7UkH*J3c%=KlG!^>(9=5t88|%YyH;E
zeVilrqomZXXN^^J^aQ7E*FHM5IZa&PYUFY52xDJlr%vrjmG3Lw<m7&NZSgiY`O`z6
z3EW~Tle~=$Po}9%ikRf7GRboR59(Dl;f^u?8Bh*^UA+LQ-}Ik>zy3t=(fQv*`~Nd|
ztOXskh}v6YcmW#ZMaR$oaDq-uIUN6uYwLf8i{7!UMc=l^f9S0IW`6DSvYt(wZ{Ay!
z-*r#z=bn{jpQRRlX2@Nn(wWS<NxRth>Xy4{ch{Nhb-MJ6wWwEh&1tQ+0~V^Dk_Xx4
z9yRDengNyZopt6f_X&U8xA5WLVE5e_x`JGHqfV?lcc$Zq;kFBG5}$W`ktsgFzA9Y4
zaB<YD{|o|O{kNR1m7lsa;_YwMKi_Vi*<N{m%In?BYaY)jHH~-svG+l4e$vtPj@gDC
zUKj5(=WkvXviTu5Q<b({OHbphE0@*VULTKIdUVgmvn;#p=6yUV%@!W4dy_@*AWQKq
zhV{!T>Rqqq#y#Th7tm5Y^6iP;?kc_)OEYGCG=vrypcPZ7^Oiennf(QSwB20$<@JkF
zjjwy%qJPg^o7Nk3ao&?fYt}JsNxjD|xKO$9eotH0^4#22XBTJQ3T>UYlx^*@A6}mh
z&RzSYG3d?OO^cSCVKTfcojA4QXAz&}0=~;=v%`J(XNG(BbGR>eeXLuOX_fP<w)65E
zpMulO(JTKxz2@a~!*E^k!O+ueIkLBB7sobbZtdr>3G{f$x9q*P)+E8YlLb5T9d}Mi
z`L0mDfaj-;{i365ZfE8eKH|4~bT7LlaoxSQ+|q7q_}_1yb85%qjW6##N1Z0VdisaC
zzt}y+i~iqAzwZ4brSdWBvv;;h;mNYN+r{|_%G2C56^%5L9y+QtY<&q?-z2^CKg0QJ
zJO48@-@gCP7H!)3Ds+V#>RdGXTy-ofy^RXDe{3y&rN(aB#^W}#zj6ybVoNP(dZ%<o
zvfy+p%R822$rDEz<Uh2%tpEIVUHyY^-~Ti82cl0w7w13Rx@pIi^o^IEw7xaH&2qWL
z&>*@x&1_k{qB}?Lu6lz7jQetL9v6Hu%lB8s^S9!hPw%QNEZ4cTY_ifx-OZ9N+Nv*W
zCmj=AsAS3$vL>1NbkYK8@mX>cGgll<So_HG-O?@dUYT^q?v_5{W)QAx!Pq&qa1P&2
zr7ia8OApptTe&QEo5x+N926T_qgtQ4a&o%Sn(u2iFgc6fG+B3AEtXsSmXQZ{tlGNG
z2UonBrkh&xIsQkp@80bhIZr1Ub4eS#xuiA4M<V4!5}&xmL6(LRG@pm0AF?Xg;n6Zr
zLF2@kRH?7et}66s{{2@}<Z(dxsikty=dydEU7jUB(=V$V#r|jx6hC+HV71fryoo#i
zGt4hb6wdk25O%atVVdRg6)&wOXM}J2`0{&-TK^;M2<3?Ar(ruC^QC$Uc(Rx@Uad0w
zpuxOm?}vNs%MWahjnAHV?9y=#``gox>npFxu$aEvs6XfP(bQMlc8Seg<-T;mN86`=
zR;-y2{d&5?q}!*~#XSsHO`N;yv7niUDs%de$%n%xc&@m;u2c2cbm^DkZiZRk?NSzf
zax7FcIIFTuhCMHKy7cB*7j|}uUistjUH(?UdA^OjcZ6Sl;9TAqb;`o!kkXo1iOxkQ
z+@BX7xDn~VZ5_+?>J_(Vd*@rdlpWP>UA09oW-O0rIb^0;a9CGRk89En79nY_a*X&{
zm;c)=+gGSOZTG~l`GPlMqjhiEXHE@#yM417+vRPXsW%vIG*9(i8h%lOc|OLfgN=VY
zAFk%L_uss$?Qv+OaOmX?>Q~n-bDn*|UE`CeZFQg3*L9DmFld9>UIVq=*!g+C9-H~$
z_>t}3iYm*)HoZ1>`t5k@b#Xz+gAWA`ucN2SX>8keRqn#A*gXPwTr+K7wR~DQ&v#x-
z4mZ2X&y7W^Lh>b*dAI9(UAEu$hjm@1UHRm1ulL5?K6`t2+V9n^cYAssTOM<b+4W)1
zb*ZICy6dGfzn5?O)p~~Q&P<;RKcme&_ptikah(v@`SZhJ<qVdIKX#pqO}gzLZT)t8
zc+t(<cYivcoa8ahS>xQBb(e+p&oCyRY72-+Klu1G$ClTTy!%!cOI%v})$`pfiT@0x
zxe7I>HG{+pKAlW)@H~HF4dd<k`OEL|i@)5q!Swr0ozm#t&zqu|rIgOf9?axDuBn$Y
zvrJ3i)H>&tsj4N4AM~d_e0^8_x4V7jhd)y4v!B%7*Hnu)m)?1P?%bV^^MmIxSaUsp
zV-uTRzhdpGoA+J%%WZqgja|en^%RZrdh2qJKkd9>W|oj#P_trEy;$b8>p};<-8xxu
zXR*YW=;J|-$9Xmi9KIvOpVfE&uzdQzv;P@<?taq^dmr?lA++~j{VhAcJ-NT#<BB&g
zIL{z>_OW($boI^mC3n3p>b_aFzr$CGZD*4L_a=>^klvG@P6+NRJkHzk?Bmh7`)}F&
z)dx)~a_{_pyY<srzBe&u(NE(i?k}sa{WSmXhiq9piAD7pf-4SeihUU#740*PYm<lS
z&CX>7x0lU+qB>)O#GHoqvUkl9AC7-p|Ls4+uk@+lp7y`h<x{tx|M{!;{_9_b->W_!
zU?DCY6z#O`XTI(K==ilmFW02)=z8Wp-`6v5>f?}5L7(FsGkPm-c&MI8RS|s+pG0D|
zkN$U2%H~t1z3G?e)IR+wmA@qnyLAt}XIS?5dwJg5$nRG7zx96;iPAk*zt!ws=eLs0
zzI|`Ewtvj)(<wN7?hgBj>;>!UZXcGv`JdtTrkB^}r|rH{UMc)D`rqlf@9e@XYJ7Dr
zeeVA{yY5vFL-5Ay@0Wc{jEu5>6TP~-TiT5Kv_IEM<=+RUMIZ3|S;&+uy;<E{y-PNy
zw0g?NeWkmzcR$&B;d@lw*G02j+vN36f1X_tBEh@k-Ge6AlF2oeAI?-oY`^p+*W7<k
zqsYzss*AR4`?QRwD9_$_!l@-~_GTP8O<4~<96Kv=^LXX9SGG>MPPd-8o(ZyfZy<5b
z>*1Lk#-I~tjCSu}=sCIab=0<%vh!A|&6*W^==LHN!&BS&68nNKy_3B8`)KTnfDgy(
z&zObRi+C@uSoQ39NY|SMmvz-6a&(sMiFlg6L#XECF+V#O<^svv6WC1`7B9N5`uFUy
zi7SsMO+P31G4A%cq=%w5Cpr@ZziIW)u=>+g_V?{Koh_joujT1qs+3jTv~6?56P-6K
zx|(-lJ9YeL-=9BSWzGl2^S6Gq{rb;v=-MYoo2LH^f!FkOa%VpHbXO^QrL*js1=>sZ
z<Q=eh)gW->t?5^NVZVPeAI@HVwpp&_d-$@;Av^j{g|<aJn17~6vUvql#<u5k9yb+F
zUdZ0C<)+>(-!yCAD3<E>ZB4H(MkZvwQ<>#t<e}2mS>!Gks4RUWWZFNj&6mHfu3oEi
zFfoz$*1f+?+zBhvKB+a{5OBMDS|x_D@oBnbQ3kW#{UetTX0NVKdu{mogHn`ha=reP
zm)}l4&1mtvz!KC^)0V*YK}CJeinY8>y2-9)=ITex%P)IZvu?U+yN6rm#3k0^R)2$C
zNB22}Hk>lf4UuM<b-aC@xX)Gl&9l$lFK1hxpWLwEyhx|E+ZvD1$SB2g7UdI9=H6hP
zH+}8db+S2G*NmdiZ$H)c*mJ5{(~So+rp#<RX2II&Gwqn0V5o!TU+JSSZk5bax>CBg
z;84=e{oVf4eIpVlG01s5_LO72uh7BVI_1e?fk;QwVyF4xdoJA*{b;t-yn}T@VgAa@
zL)Y#ui(T5qwyn>tyG*d-B)7tgqrN%j?O&^RuMWFndgDpg$$Q?Ox^G&-nVf}>$lloO
zc0{MAKsg|qoq=hY<(jX(c9EvHUnX45f19hiebbf=TdE6{y)MpO7y0DX#bf3LE4al@
zJasTPnd>E+?zZu&?lsq@Z}+S_t~oHXmhvzjRJO2Nw&_pme+C8X{NG$J_y3CK&B%yK
z|EAu)<*fR-&-)H%if*61J@0Rac$rb*oODUk`6zcWXJDDo+4NOk;N`5)L$~huE8pG3
z$+~upP>la(m3+fvYaSXI?v^;mR^%G|AN}wR*jiY;M{<Cy11<IP*|PuV*X#BlT&w>x
z9K$@WqJbNE7OLnM+dSouyqlw6Ucc}v@O4$s_V30~XQj3-wms<@8N-@!dJmtnliTC{
zk~~*;E_hXtwa@C>^X+|a1xrqgD80HAU3PwUSw*C%r_9%5R==cf{JXy~ePhHdPuI6^
zu4$aw!L8%1S#a~<0RxK@=lrZ?F0jwP9i6o~<5t<!#PpSpt26fr?b(o?U8xYVTRUgP
zN@Iqea<?0)Np>;Kec8o_1YcgPI2|kHH`{K0Qps;&8KVQ&Ue#BYPMWZdCwtC^(4vF0
z*~^~2#XSvjd_jh9VewLTv!&m*c;uxQu8igUW;ijKE%*1S)YL<H2P`dEo;0{W*0v2e
znz`bId)jjGnHif{?uDwyHoQG39hR7{EK@MiJT7!+bw5x1$xPj;M}+sTn^~T^Jo6F1
zp{#E2mtbq<brP!%=!WboTAQz~JT2ehvPpKV^4Z@e+b>n_xchDQ&v%7AkL9wr-P^ly
zp7Djy?(Wyso^KWB`A&*GmDrH0Ufq((@p$>Ep2{y@k1|x=TfgYe!QAT9%;m?$y7Skq
z{yTNc^<CS38*Yr>oh`}c^4mF`^FYnc-)pjt&3xFpclU=kQd_4?pJo`D<r7rx*2W<B
zh^@`6WizY8{33Ie6}@$#DTjW64gh#)zpeg|^uqrP89)Cs<o!Fp{kQuq<7bugqTbz~
zSDtQp-g0f1#sYrx>t8;qcjQGq_S-i*Xma%Br5kp(UCR{B6@A;i+N)vJF<JFu=?Uh%
zKTd|NI5)ev@bT-UUox5brf<(gb<efDxukL7424-Q=X5TrQRX-_wV$J9r7JIJo_*r7
zi5efun;zBbS$z4OYxrpQ*1Z?h_J;2MdtEncc8pzE@w18jGk5-dpmy|Lqv_u19gl0x
z-aQW6`60)kcI{hk?_#4RFO{}*?~wF=XSDmq96fW^vsFveU;NsX9aXyY@7^sRZ{5A+
zTq=BeONs~Q?S><5%#v?E^9Y|~u%OAR0XF#--Ly>~j;=8_X=$H2!FK2N+tMCqx;Ba>
zOR;K+a-Lcd;4~p5FSHu>n9@cER?)b7zwW)O-jOi5X4<5VbZL(pPsJQ8Uw_&)&$hNW
zOoMs;$NPUKpBMVia6{|$e+F0664CQNP_E)bIwV$`%)OsX8{h9yf4JB0llSTW4E!&{
z%Y%|@F5h%l-p0VJ<L1Y}{9!HVmd^hSEy4%?Gknp?sQ;nY{-2?9@jn57_WukQR)X$@
z+9m%_Z5J1$4Uej9z4gcS2Ts%kK3b8tW#^W=+}_@*y_2q8$g6DLc+&OO4z0t_?#`dW
zQ@%cBQG?BVx4-jkWS76GbzQ&J(`G^6X5Xi7@jbgbJ{(?nK&ODe_-v`1)P*nm`72I`
zZMdYPuxV?ow!gKaPo9$Z!kztLIgHaR)n#VA(MDf+bAj<c1BZI^e})$!7ydJRh~@v!
zAng7}VIKc~hK0e-{}~RJ*#Ge@D!8S)zvqi_;qusJD{j6091~|`v}B`6cy8X(lT1lU
zx5TCQY>@Qyd29G`7VEUx58rdF+r036@v>fx*|#%wQuZWPoy-$l(xJWWsmn}e!Ir=c
zqAa=$IrWF;f8hUCexv@OO!LXlHE-|b%u9QdESL87ci|t)+w%(NWgVOOVf}$y?z6w;
z^V~T3>~Z<6E8w*+mu^>mJ63VtG3MUV+*L3CiC$T7Rp+aAuXDhMsau<7<UZM*sdrJ2
zrR%Lkj_jr7XO6I)JZNFD(R9(Bit{mMze;bv>Rxwa>)uC;ja-F}W?biz5mHpsJ-B)M
z8P*W-V;2~2Mf~tTT$TEye43p6rL}sC&z)Sbsn0y7iBE#3r^)?sl=$~+ztZLw*H@}f
z&(0P;Yy4I{OGCAfU7bO0>d}|e*lr*1SE;I*bn3hCmg~k5o;)9q9qiC8lQ>=|=B4Gt
z7V4AIkZAGb?H==b`<AUU^xo9Ge*eS$dDkb7EuM<z;=2PUE}44g@4AE+Pg8n5P8+A>
z#~zTo=o-F3?Dg_!ZVQ|4Kp~FAPd;%`3AwQ?Ofw{;JtST>hQS-fpp{h&YwCrLFFv`<
z_3!p&2UkSR-l62NtWlL)Ws{EAjXVpZqN>NXRbfYq>#Q2?{D_=<YWGyux06q7>sIzs
zj$SeI)X#c5r#8ztHzN&($p__x+*`vB-ZE*tpKbK=Lz3Z^xo0Qv88JLo*ReR}q5i?W
zW#RT|As@<mtrv+!EWZ4J=L!EVa|WZTB8RU^8@`;iy&iNqb;IT5+b)S8;Wu4kpPC`Y
zVZV8<#7`Gyp_zZqEi5`eue_<U{Blg@rAXH$_uW_TZ~iKg-|ckxZTXIELZb0MvlWxi
ztm2rg-Cnz2gMCT;Ax_W<x}qlbf5e^tGaR`V^Gm)V@lxuQ;6t}eKB^wv658+6VSG;Q
zlg-AR4kxESJ*ikdiQUxivvd91-u$q>L&bGAj>~6f9x_aA&YgAU;(vxxub->l?6?CO
z^k>@Fzx?(~!HkWEm)EBs&VRJ~v01JU2lLunPB#^p)~Ga!wmF_!Vfm;*W!min*PPE^
zwPDR%c4L#r$Jo1>VYgE`rM(KeqC)Lr@@|v_f0|HmBgi}R!ETeeTm9R&%_?lW`|jKM
z<u`X`D5naYu-R7Fad@S|!w!3m<fHEE?wa@Nn0mWh{u=Qt+Iz>A)sbILcQBv1;3+>_
zWnH6q(Pk~p1csVzkxj>U%$g(B-nDjXOW(Wu{+GX;-m+`Q{w>okChL8Bv;XzfBD154
zDk*xF$J`wB(1Ynp`or(dQ4iJaL@#b%WW=Den7d73&N>7CQwAO<o=coO+s}H?bbVuu
zZGNH1g!5uEb0)bfO-)G@YT~eI;+I%^is9M$!|&O)9`dWvUYzfe!Vu{u&f{nqlQ4fu
z!o-Q^3@6W<)TP0IevuFOTD~5XLo`8)=8;Yy-ue6dPmL<`zfJ4^GknQiT7q`Siw2ga
zAY_{^^W+O(HA?bXvwkf-bmBr}+^g+EItgN0(~CDUtMELi>blT;<iok?4Vkwl-HBdO
zq`TUIWwX1o(UDg>e>xi(9BJjsRXxO)JwHQj*N@;wtE(%P%&Lr!@_5|qZM<>E4h9BG
zm3f9ylYaO;ddKT?@74Z{UAw!u3-xavTI|Zbd(oMON5040BN=Y2Te2eLwS$=bL!IU~
zJO7>A_wT~*_#68-*Oxx8yca%qd)a>m?Z4sgjrU7Dw%!*tsa~jK(pjZTrP|%EmrOj`
zwWjb?x3t!Yh!d}7gq2A0l;^RQ>z|GI7RMwe#kY9b;lgE`;_h`HZ;I72&iuE|#Bc_q
zq{GR*1qU0sch2XDJ9@o2Dxd$x%cNSfhq`m`9A5FVyEu26O23}&t7Ohe6C0jr$u2Kv
zVThT3%qn(EuxH`(gHOGga^~7BPnqi6>14^H9Qv7Ci0!^oPXC09=G_Y7lOk_sUcc3P
z>9kI^?Di=v-2(k*OEYCdR@tnUd|vk9u)L<y-s6p1Uf+Dn`(^VzXR&!X>Ec3$lb&;2
zT+;WTe}>9+g$Fgqa^{5=xIWB2En#wU%UeH|D{qzNS+3K|<=J@0<lUrm|DsMTja=ez
zn0KqQ!Eql3kDB}?`8wU@s*7HBuJ)|hAg^T|9?4OrKIh;2caID27;x}~Tr@qs*Z*kL
z+Bx60mlfWQjI!9etCv}&@4IwIiq1N&B{i!JB$V5DSPFh9ozu1Y?)y9B*|Fy?&2Goo
zXKXy87W;c+(-GglcbN8mZY*}c_*FYL?RUskQ)%y=@76xp9=dgNhNzg@)J^3cPbQ_=
z9(Qz*hF#GH+D?-Gy8f23`#fLuXZyNyHXi-dZ=cL&n7SkOfykY@cW>{mwtF7^@8Z8h
z-L5;%e_M9@qTRV^nH%qJ+wf2K;?X{d%G(V;c}qmk->yjhZU4J0*6Q<{>s5X4mFl(Y
zZx-)8e(E@X=h9hmh5t6^-wkZwDzp0g<(`hVw)@}i(!#>zw1btI4?|VzD}+v0aN6rB
z_#~I5JbUudd2QeNqIu@$w&#}DOxq>*+W+2`V2=%lpZ=^X&gW`o+%9`Zz+>H{{B}FZ
zes8f~alOl4exIN;+xp3tuxa-~4)*yTe^w+JGU52MgS-=bW8@@mE}Cue-t4aX3f~pc
zF&#U*+~+=HmOL3_+1sEMDcKfY&LB9`)HXZps`BQmDwl)3cSM)Cv{{BdJY#q&D)z9o
zeZ}gnTyhfcf3}@^|ERO%y=cshR}*8WNTn`$&D%QVdbiA)?@a#lEKVLj(U8Y%UBvKg
zi(X0ell?n)Tr#zI6ZG@&J?-0-XJV9=&lJ>QvO601nLU1@-~GM&j!x^^W_9-HFMs7F
z+rqA8%e2mIXkBXEy-~IEbM@y>PbSY}u>2h_a6kS>)IAUN3GuJ2jvnpZY$F%F#Jf}@
zdFvF`lI^`W*kuElB<3#LxAalw{loJlckQ{Bd|}?JFSoL$3;y)la9T$A=fq}%QU+hK
zJD=wi_!X5Xd=Q(hdfRi&@yyi@{RQ7H#71fB@Y)`k?BV9gGU1}0$Kz8f$<<tw?jH=R
zs@s}hx^#w)j^gg<`x_i{M0xJHT(D;1xV<x_yTQO_&0{@ZhSb|XW>x5x=D)d{W?RSN
z?Xf2R>8H7NH*MAmblzg<3gn+~hT$Gd%jc=08)eU}&wU)tYgE1B>E-)AJ4#PA>s)fX
zcKGbXh5*jbF*yP3HFH`$zV`FS=*?VJpKd;P-#cEvd&e0a=V=Os^+rrswP}m<oPzht
zlWuP?6+4-~b*^=+XNpVLsf;j5#grtqjCd6@u8B{RGbMlSJZ9ivY0vd~)9Y`$N)LW?
z{jlT8TIM}!2U)iinMBXjUG}MI%fxMUVU-?&J5p7|;x-??HRaa2PTr%Jj&0BQ6n&?o
zk@LCBTai{H&zpNC)>R%eZa$iPv!dv^XS<L1te$eIxTe-O3%75q-y$$!kM`c??K5h&
z=Lw2zPUxw<yz*hSbT==X%AWpHyXHl%d)8i%ulj82vyAV2(uot+J-nV*VBE!UgY*hx
z(;w%RzDqME$3(5kEqgD!cf%B+c_r&My2Z1|&c5rNJSSb!CTuC%X7L6SlU%9uPM0U0
zJ8LVIIfLKmkq^VAQwMlInK7o>OpX#kY~_~ui@c(Ir>*tjut|}bQ3)4Snl9;!#P7YL
zo%La{OVIn%x(&=n0vGyx>fvynICb5o?{3%ZA1cldyHx5eoxdf@IaejTjNks(_NmQG
zo7Ie;O>E+KbieT@@jrv(UH<<JESKv)g)$UYwN0)5W~*ntTI06&wjEcMe%n6l)mto7
zzm$J-?)IKG2B&p`AGZd)mAGe|WXtyJ>enUPw(Pc3*zsZN7J*m#d?!<PhR&2Pc`#Mz
z`HA!IIe&&cX+81U?)YQ=Uwkj>f2hs=&oF7lZ}}ek7uE~^Gd!4;|IcdypTFOwu8R62
z_34`?F4(cX%R1WE-fgmHU<vozic3y!HoeR6oUtJEM!R})?uJ`Vv)A*-WJS457youo
zdG5P)ytBQEKKedA#S!EZ`P=MXgqx5_+8LL=$#3cm{xd9i*Z!ZODRci%t^SQa4*zT3
zCI63e*?)#7tH7J0C|C0At3RLg?7yIuAm;TslVdkTS9kPuD@9M)>^Vy;h>K}o*6wAT
zT+T8YM{DC<cQ)PncIvW!pRU;b*zn)lnd?h)za=N_FS};M)A_CKoN&X>;_ngHBfr^8
z)L$qE^=nM-|Ct*3>+JC!lWvK3^;^GKmfyV{o%`>^%);kB6Z6jB^7s9Dye7GC3uC|B
z4Ba&)%4?(U$G!}7t#UfN{EQT5TuOFYAIIsFd?#AEr3)^u6Pc2{ZRN{beoMt#Q{w%1
z2j?&TQMx3UJ5N4+XQf)ej+3Q<lbUr;FbFx=E=Nle^2s0D|FW0Z{}J~6&u}t?@$`R&
z^nSr?yOLd{pEI}1seYcBr<>MX<Lve6WNE?j(|TsIhqKc&Pgodb-jj})?^S;3iCS#Z
zze}&rcFy3n&%Je&lf8BOp@ZA(gsnX!Ep62a*mjV}Q3v(pz)R~}*L90byEXOZ_R9+W
zkrVg*z2X$n>B(?Utw!ffXq5kyQ!~^`t6t(yja>gEFTZ_b<NfHd*xYZCdZrx9KDVyy
zO?S>0SNy>I@AElzmWMMt59U>MJ^zO{RWqZnR##u0VW)MiB>S!2<M@lyxNleLKFRn}
z>C9TH<#G0;<iRhd*C^j{3Th_6u;}@l{~1m?U#ov3n)sh#ao+0%>*~(`^OD;Px}$~v
zuXMSCxZ;OzGxJx;x>=|Qzt0rq`6RKp?A&vY?i_dP**dE@@BOqlP7m61PdfVRkN(tR
zzKP#bty&M=J2y?JvQ3%iUi{3m^PR~>%861dBTn>k26ahXFj?OIJLnoW_mfPMpGmVm
zahq+}`?-QkW$OJ?yLRNy>AdnbEX?xA7RDEoJuWJww0U-x#;ynv;AV(^rjWoq`98w~
z;fCbx8@F$n_bx;Ers|zVndcsr?{MvrtEySCxZgkK`rI2YKmBJ&zT=#{#9c)GR#i;n
zn=dQ3JSp0qajAaM2~SoLwoG>(4)(v{EN0#Lk8OGGWM0o)WwyKKx_D2|N*!O(+tDkF
z9A<QEYd!W}hb<`B+Jk*rU|jgJAH_kJ_h>IWy!gi5Td%_7gm!wjvo4;vo+-M+rSFKq
zE1yPY!3}xb4IDy|nZoP3SDP+fr=v3M_}R^yFFd`xu;Nnfb&Kug=@VxOZ{4t?l&iUt
z)q#CcWLCia*etV;I*o7iSobV#IG8L_^tAHjHdmR)6Y7?^@7vxV*miKq(JL1{O)|Iq
zInl~2^X0*b`SUlf%Rlh#f<ukNwXpKCZ9=aS-zM+eK23N-w8MTaFJ=~=H473L#JL+7
zR+`G%-TC8np;Y|xo|A0zD>-&Y2mOnF*Rmj!!P+j~UQ+qJfy_1z_CVLl{|rrAzHhry
zvT0Vyx9tHh{l#_~-`ZlIx%Z4kS`ovJoV5o(i|qK>dH$Sv6)Vz79-!6rZ{h<#{E9j*
z^C|y|j(3OT)I;1mx(!kf>xl^O5bQ};7Gb;)7B~ChTVu~1nQtCUj9J*rd|suSONi5B
z>Wq%btv>@aeuno?N$#)bT|4#IV%xsyD*Bo0Zm7*s>}<My+i<J#Pc93W+{-^(8F)YE
zowMk7xs-qTxP8VBf4!Hc+&j~zn#>gQ%$;#cF;d_A%`}6xoPsNomL^NcMT;`L(>G1o
zawTa)bmsG2(=Ju7xTL$dqT?9X(-{m$PVG3y9y2jae@*UJX-nO_#h(>xgqTGYnz%M?
zI2gvlBq89)(8RG`naWEJs#t^fZ)*?mfAf2Fq}rC5oKxO0@?DFcc+4^3rlo|IL&6;y
zIlkM6HhSvK*ZGz5%zM8;meS7~7Wx@cZ!ekKe|~pHDR=&>8yi%Fj+=ayRS(ML`gYIO
z?oG?ZKd#v<+1xd&u50K%4(wy>b#Rppb-TyPP?h@j>%RF+XG_(mOMA;Gyj9l+tuOeR
z7Wj5v#hSh0N5yWXt(2QKZF>3iPm4A=<_QQzSB9S6w9f0Wb?GssoC#iRk3rM&9x7LI
zue(fo?A`mNd$GjU>iI^2l?pp1OQcN-=40Njce?lH*^HQ@T(9aBs{7w+q_;=3z2p4y
zgXQvpwW%^niGpEzJuVkhlt1rykfXCemUVuY?z(jgw#>Tp?$R^w_AMF9IedcGI3-Gp
zq)BFU7KBVapfKS^@XomMzq3u3by{zZJ@IRM#~Z!1)85SAa%#o5+czgOXWnMn^oAkF
z@zk<Qt6z|Q7cbG9j~O6~y+mL%<LMtozwY~dn70%%UbZ4@vd?eNTixZB$&DuuurH06
ze>5|BnQ!&Vj9+V~Pu3Bf5hptJhPOg*WX-bD{28BCdH2-bpIIJ!;meKE`K(#LVh?+4
zh`aY{+b5G0Hm>i*E0q;`9{iHpY1Y0f%S=r+JiIBA_3qk3wX@Ej>UA;J*>Nj&#^&5x
zo;i%$xj3vFROB?ag=eU3+1>OZCi?c@-b0cRXI34YqAhS@!O5MC3YEgiikz!HRGhl?
z?BT+8-z&5KDm^+UDP<Bm?~$<DiwT>1CT+B4v+y&BFwjz-bx8Yt$F}R8nU>MoZogg5
zOE0QC++nuyK#j`xgf}Oo_vJYy&2P7{ueq#x_3M@H-0U@3;?utM=Wo4wFS~`k&MnFC
zR0PwKNe9|*w=Uo`SugEfyzoa^cCXa0+~DxbXCK{;QW7ZpS$*!=<Sfn4&U)Wu3OtHL
zUc^@HI(Of%Ik@fIulGLHuKT8alW025x>LHPckk5MPg$lqoMU+E_Vk?W{&v%~M&A!z
zGpp*UOPjv<Zq)3{Nm1;KZ$pJ#?oaSqX=63%<ow-J)pmY3bvx|h+AS;ICr4M99KF1#
z`n1W;NdjF?Cj~78cc)ag=tU^CYJ`|Fl=MDg`FCT|Az8a$k1SL@^z<IOW;~cWH8QmA
zy}^f%lTNid)J$T?-Fo|I=D(RLR(7k4v-6*?iitk7N$1ny9X1{dx3}HtTd-->v=}z)
z=_OVDt+N9@>h4>0-K<No;%>@sp}*@4+U;V>85<*JH1G7<sQ5&>A#qFlp|kSceA~X8
z&Ez}3Pg=F>RY1s!zRal`RlNAQH^>~9)bW~hKq#i-w0ry8c`^61ew!|eRlhk?{;l=D
zH-$C#ZQ4uX_5Yf;|9-S&`$yNU=T=N>y7X3I)}v?-{Rs7`CLiB_Rt}KZp?qrkw1DM_
z2Q6c7meuo@ytaSyw}1Yo*qQ#kzfXjxPZq!TIQ{0Ee|c-a)z$re_H=#gv+Y-PpJe~I
z@4sd5jw`wg#GZJm%|3g7pYIc+x_>bYUG68RSy(qHZ~l06?!URq@7;b`wR-Irw`Usr
z&auo-4`_XMbGK^9iPf#AH$D};(q<(myl=;qKhg{D-}8JH8=Lv<v(ImbJ8z|?S;+8A
zstT)-6Weon%Uf2HyM7$+x6HNwZR1;<k=hq=qPy_MCQaTM0nIxaxOrrn%uIBRe+wVJ
zl{Wc#<^9AhUANEP-d=Zvd$**;IpdyL3>Ox4X^gIu7+ohZi?-_|R(y#qi=O>K&nB=Y
zy**&sDG#}WQWt&}Z_(Q1HIa9+$Er1q6YDBPT5g?cPmcKT_0Y>%%fA&@-hTJs%G);u
zB9f0Ls%Bj6<XWxmVtJhJlcnx%CJP(O;$o3NwZ#$_p6r#Hb^Bz}%MzLM-_|a@c_8rF
ze+JGDf&H34_hm8kWLNbqfBe#9b#}k9hg9vAY?F*-Zo7IP@Vz=C>9u_BhQjaH0uH<t
z-TCmXS8ljV+oPAs(OW8Y-?=!nd|p)6<up^}&Apy*o5zv|A8ma5M|^39)fuU$OLk2<
zo|<2}>(1SnJ3o81l{d5M9htLw(n7yy33Z>=W>v%;dvw^bQ(yVhy5-ZdcP_jmeX??C
z<t*F7Z8uW1ca+|q!}F-YOq;-Mm!OpgkkM?0MLX@Kev}7Yd;26;=a$K*m(yout6o_v
zwdxMXe})Rl&`zx+c|Epr`5DP`cE4wSWqv(Qah_pv#`oVYMQxGGrn;<pW;Ssl&%|BJ
zuDO4{!p6YRx$%JY$z>4&)}0)BD?hoND>@@muwYKgrz*xt1&pTCS3Bpgwa$25`t)wp
z>C}3KPbUxQ9-pzV`I&*$*T?Iu()+jkC@tXKdh|}1QS7b14bh%DP3hYO?wz#hmhMRA
zT4o*+8X90A&gh_?d~l!Go)6y^*V|qRQ$Dw4>vrSYJB{Kz1*hyia$v!c{%4vtJ5N|9
zUu&@DT3=n84_dD2`4qHT)7ta&iPutmwvkh+)8}c+AC?o`_+kC6eMi;)Gi-Tt|6gY=
zo7r>uS4#c%6@TA6-ey#M{C1809uLKByXGBxbWeY?TXLytdY}2G@H-p_&XjSLed6{B
znWOfd;VYMRbMwKdDORm>=G89jy7$=Z{od^_KP<g7sih(JrHZ}`AEU!+33&^~>^+E8
z@<>;WGJ)7=3nf9vAR7H=m>|3TZ)?f@zq)PM_cL>8ENbA=+PnAb-aFq54yyeGotteo
zaU<y1?CVcUZK{4fTNA(-bN9^Yhx-L$?w?VKRS$AhJ#$*x=yr@k$h{{_p>hg4leY@L
z`KfM{wu=*I%t^&ZpImV^VN=>GiN&*AZq<bpJ@l(8O0GYBCxB&wKkwB&;bNbTn+Pqa
zc+%Ufy;2gg#(mPx-}701lsyj2bv60Vu<^d#e+HxH{<FL-Rqr{QeQTYv&#U=!`mFVd
z5BKs1UtYWZ&HJq<b@LW^F06lh`XOjz2U|=}lhp<GK-c2`45-VUL(&gbdEHTAdwxXv
zuH-?ft3P8j8J_OB!~B_tsi^W;K>_2Xz?i-B+rHR3vCX>nJ7$vUG!M^zclJqC++AFF
zX79|1>c@Rr$59uTUx6NVgnu!(gDfkNM`ZnHKr<hGT{*Evg|n~z6Zc_x`=7|_hi{Xz
zcU!&{j9e$h^wBUijBB^KS;5~ceEhb?JJA<_SIQr;Z<@8fqb6(fk4ojXvu`FY-*YAZ
z$&`~8X|X$#J_&D5v$);*dY%UJO_O}lAN5D9*(R=yxOd_r=bjnq!Ac8{>&(2f*TIsR
z<-zCBH~$%)EPQSMjcdbyhKt)vpZqd^b3JXge9T9dPtO#0NlUm?t30-t_&qQ1#P3!9
z?0r*T%oDzlYh(Iot+)54Y41D~FMfF%wrfY_?Dk!8<}w<G`lmVso?}?Rx7g>(!mGJ)
zk60%L>Zxy6JiuNOw8f`Fz4wI2x8r_Oi}u`ixO}8eaa(q+)h}5u+x)<3|DI(>E)Lt0
zzEfkhcEei9^2Q?>9(T$gE6!R;>@uYc=BwJXujqW~<@zV<X3f2O_V3wk(a|31s!?g~
z<r$AB9x>eMs4f1}^Ykb02{-Em`u)0(MZLIGa`Ve?;pI1GJe<b1J^1(OHB(wQB*#2&
zT0M>DhV^!{<((xnN_oo<O&7}icxSe+@0}AD+CPQAxhzoJKc%u;@cj3ta;64Tov$go
zucU6s&U~<|>k{`$q1fdKQ%*2Fjc7V><mNGVAK@s`C*N+_ZLrbWa6H{6h@byOpx36`
z)=eAFYVPP=EMb&n<m|%tjCZ?a0)OIzX!T8(@{XBBpDs(;-f8k|Lzl^?iynRKWhp_g
z-jwH_Ha3t@oWb;LBisCy*=AO;w_kbMO#6Jt<=XVi(Rx=hrZ!jlE$vJ3Ns)i_^1ie0
zWra&?Z*f=Z-IY8&xwKsOa5_W5C1U}Lmvc(Lnx6f!?|8`WD-kaZ&wpF|@UNeQTIaT$
zxo5XeGyfpk8RX{id&xJ`zF#H&xvRIeE<T^R(EeNb%(Pk6w>ryWHpf1?J2mpVL!h6?
z&xRc7j#~`2N?pf4+^H&wDrp8Eed4p^IL`*tUGvybca0=9fJ-z`sfMTM);e1B&;Ih;
zul&4jdL{3-A7@*bYV4%zdzdA<<If=hCjWP*n;VLjwmW4ouUNF_e&D72XFnQk&dpBA
zb-EU9dEIkT=Cqq(@`ge0tB&)eta-TDX2SV~W3KE@x4l09i7(3gvh&GB^=U5^x>D|P
z%v{{z@l0vI);>LkB!-hS-W3)#FqDajU;8z0Zf<?L`poQ7Az$vd%0&jOe*DS`eOr@u
z?r;BgI{m|Mhi%c8I`_0SE=8zp&xlNA7D|<1p7gt~@Lch^;#gJiP>g8&8?*lmx9sx;
zAH6vGWb<mloyHR+_@vn_&Xv8(NiI%1D#93-EnVGxI(udEeba4^IduwJ+qhX@?v`ZS
zI6<;O!8q+G_T#<LsuBn2<!fQ~U0<!wiXV#FwmOkVI5zT@XF;d6sPk5DnFlEkm<o?o
zr4~<M+~`{QXP(8Li+QP+^Gtrf_4_ATc47mwrMB$W)hB{aHl%jP@UVvjd8a;R4RNbU
zT)oHb+8wt`hu5f-hZ`9LP5YEJDcY^0k)wE%TA0d8h9+*A2h0~Sj-L&;U;N{E;5D@m
zJGOVH&iQnd_swOmwI-A7=3S32Ta#G!=i;OX3-2sp;l94$-~E068Cv%Lmj7-1SNLDu
zw>$qC&fDItJOAYC<G=a;Y(HIKcXTbR+TUSX?JsucmPnti*<F(dZIbOXm1FL9bQW9`
zVBmPn<<9cSn^`RK$F$EkBVOIVx&2yI#?*B(TX_FX&i-aSvuWi-fy#zMOImamYj;W*
z9$;S*7*{Ud^R-%EApTa?w2w2dJzTJT>-HVIOq+Ram3b9AV|u@*b|*h&ZM%Nx@rn;q
z|9)G#(Dc}n<lhl{_q1L!yR%Ap=TuS0Te}-VnN^qyCmCfh7lEpGB+TdUd}ZOqJ))~$
zP3Km2Os!sZ$75qd#H!eHkd5eCN3Zv+T`Rbx);#Fb!|lIQZ%bU{UAi-!Tc_)sG>>xG
zt%Y+~4{L1`xqNBM`M3KSvuF9wee!qL`|xd_%ii7G_v#_^Y}%lT?gQU${o7<J9&38f
zyJXw+x3{ulHz{r2U@*<1_di3$O`Uao!cQNxF<jaEktyPpcD~vC8eN}_2fqInahh}@
zG_WATI(07F)3AVOmfp47<qjXcbW|p6^UeENQLSh1Em7#Zr1H$Vdb0%U%&FlVCr=CT
zT{4PjIJWtL%QYKkxmDi_*!texdMg#JI<4Z2U;8Of&r?nZId3hHeRp<8Q^1SNc@qE5
zUDbVGck@}L{VjR*sXc#JJxzZ-|KaWJ_bneUWe|_k+r0hqf-4U<@7sM@?qdGZy=@8`
z59YZ&RL)OL`{}3}VBBCCxU*Q6$gSu6p+AylEpK15rPEYGGIz_0FAq(RHl4XR#ffDD
zTaL>akNe-dwHB~)wXJJ<d{{o?-=+TyKDWQ!4Z9rlpCNSaJolUb{Pw*2Z69a2f8lWj
z_CKl<YNy-Zyng?deD-hgZ~5=`yth8}dE2}DPwQ9xeOCThCcXT0)U3Frd}|Z77p&>v
z-jgrWz}Dwd)Ys0^vszovQQ@(|#O9cP>mPKKCRcqrnQ44><+{Zp;oFibL|ZrAemlwb
zaK$ajHm-+VUvHm#*12?9_u_+z5)C@lonqf!vm|U5Q&f%<E%IYmm-Uv}2<~5lmt2kZ
zvq$$MjP6Gm-un@-u36~(&v5DK#V;-Y86rzpI9m&z?6NKsp054((#7MFHVkQT%NZK5
zo?Hu?Lj=*J-)RaRV`qH+Ykk9d)7;{?>1JjHuj&$h*SPFGee9dl?Gq)p_V4EZeSe=@
zU|m36V*8{247{(ehs|0ty~=dyn_rvn=$I9p_%7gReEarck=<t^BSQ|WT}ugJayzr~
z*!!484VJZO-((9PUtF8K&wIsJ?o99V%kCWKQ`q4dFEry@(Z&tIbA;UZP2&#|H4LyD
zwD9@E@s^w#?QiQhdhUN~ZT_EOQM6<4&f~v27N5UoUv2TWXU?a8@*ngzF1(RB=_ub+
z(QC866>T%{d(C>LljXum>yuBLHd)LO{$%*~RMT<Gcn{EGXs-`{|Fu4{WwSnO{8o3#
zQJKwInmm(i3XU(IA*JEryw6xKLLpHxUH#PYb5*=i7x$#riyoV$-ev9WsWeO1>C~eu
zG5PcE`D^@~*n4r;?UT|Iq#2KeHXeMZv4F>(<HhHUIN82K6}q~2Vq#7yY)QK4vdQn0
zmZsJotsU|uB`>3=AeN56PyGiiCn^4hd?3XOZH%SXY|Cb@bY699?-6dLMKS()&JEx_
z=O6r~Cro_XH&^S(2j|j!-MvQw&$6rt@^}((>XjRZ!Usp0q&@Fx(Hq+#Cv<7r-G^aU
z8q32fkF6|zzU_k3%IRnB1>_|OmtBaMlk#j`<}A~76QBK^75&oYPTud>Ki@5m751Cn
z&X2osUh;+Z^bajnC2>aA-6k(Pzx>8ryCdLE#r%7*DNA&lrJmb}#%xGCcz5Sko9vA3
zvrLpcmQ2%lCwk8~>H3BZw+>WZd*ys;rb5F`#Y2V<eHluo&R_ZB+OGXmzs<~F{Au&{
zH`71gPPafDzrNo7s>$n>Th8;(?$zV?a$?bL_iZ~aKEIO4m(qWtFl+5TonxCs+3mbG
zc05)HYwd5}>QQQ|bnM~sS;s2Y>ThM=Az7)HyZDArA9s>lVah@033cc7)#pBtT{e4}
z<I?CYVxMAn8BbSx^)9;Y9K*vUX$pmxEndIM*nMT;2Gw=fJQm#N$+l!zeNty$)B=WS
z=N`>eVf@@zkyB~g*1BqaYw3z7+b6tYKRi9``o`!Nm!h|xy{+`%w6W#ynBCJHWJQ|y
zo^$)kyYW#yZ<OlUPqISZd+kIn&JBOFz9>HT%UeqsV~^h|NzbP#Ir){#G*qRE9(`q%
zbN=z^YSoNm^H<nZtv#YLXV0|7i8+rI-e)s0SSX2~Gjjem1vbIP5a?R`&ve_K-5=JT
zG4tN#ti!7`qi5klVZ|vXS&kEZ5)bys>^Rjkxr^b2#(LuoA71X>cJb}=Et6smzh0kx
zqT6@UA&!N=c~*otoI5koWG0V%M%lzoOJl@#E?e_U_1(<c%G8=|X8Uh_^Vkr1+Sp}%
zMcZAM!j*~gQw481+!E0^ajJ>&g-AGY2XXAUXtMN@P3WqF>A5OW)i<L&_|Jqzp1#8w
zv+?(*se*Y)-tyB6Z358FJjT2`347<t-A3SU^y&OUkzz+Jkx7;!M!P09ao7mBORUsb
z!1MbpxBHbxleGV89eZb~D!j`-ZxY)C4TmR!r&$?`uQSVP%yzo?PIcR~T&-iCx~Z9O
z@4me-V@cY*b4&WCcGn!~^L)NGBhW$e<-&}Q_oD8(FO67wb%_&q=Cr%ahb358+>V77
zcpP{<+2z*!sgI;})lZ(km8-t<b9wE3&4;l&j$3}-Jm=%~eH9lluH=>$x)FI^+go>u
zkjK5a=M@LlPbYnR@}FVTkquwem1nKbUzqW2`lPt%%rJwy-um-ZF5X_W`(&H+X~s!6
z$|YZa-oA1zmj<)m?ZZ*LbN5X9wo7d`i;zmk$D>(YYu1TaDDVgz6cD_hao#Z;&*i^s
z0+CKfhp=V#x9hL{a-Q>5`1eVbW!rYOtu#5mW$udY#nUWg<}g$Rs`u%<o%SW}W!2g>
z*Wyz@Kd3HvXLnJv%XVM1!Q`nYZ$z(Six3t4vRdTIAJ%md-ZG!uOUqXuI+=G$CE<EF
zLyP{WHp|E5lCO`Zznm5NpP{4F*X!H6cV&J4Z;nMSy{xi1_S<zMpNmV3{(aD7wM*0e
zY@P5RCxEZv$0n9N0^ZBx-KD&Fx1M?XRAlRpDT*F3>^c!YH}Wh<kv@L5;YdXLk!i($
zyK{>Bw`GY-)l>!^neg*==ks^-6+cvc+QV1q_xjN1n5^kSx_>g4-@SMHmAHX)QL3@?
z)0~@XA4Kg7#T?z#pC9Jw-ALTc1P;9R$7jWUn`6qE`+iN%eg9l9&Af-lXEU)HZ3tD}
z=ljZ%xy;e`_1PFZRe>8ZG50gAruIy<@tF2mC+D(BpO8Uc-^HhMS`QX(SJ-w{VU9iP
zkNm*)!?$F9wJo+O7yG4j^Y-$a(=6B4T<KiGzgz3fS|Qd`JPgk4>ZU63{12_v7A`;c
zD@*nEfk*dF`w2w0wf;G(%UE_NvLW2M?MZ0-bjbzW!aoibuXyoo+AY^xCkt0@?fnv5
z8U5B{duD@*=axyk<+WmRc`RylOQ)W^Sz)?H@v_}%yV=>Q%a-Lo@%A-LXgt{ZFeT#Z
zrzNYO7aPyL|K_24BuX-o_@}dP$7LJob@4Y(KD`_D^1Cp2<G-}1g^i4W)m2NI&|IA$
z?ZYc0PRkyh!SPXH;^TRRGX7gPZ<TFkTD#4aabKu)c5p0c+rRC~m*8#xp1FJO?%tN~
zw0q;kIq4QB)|7wP`t<er;+0ti-nAy%RQ7IN*kvfY_V~Qj8<!OC?6%O|EusDCLpei4
z|Iuqjuf=Xv-MpW>YxlHs_uik9^O@wbNz$!6wQR=Bx&&^y5TmBUcKmV?uFIoN<bI8w
zacpY-D*uuT$A7QRWPTRuHDP!AG;bv)zdF|hzB|8b?LJiO_ubmKe&5ODRd?^(2;Gpl
zD3<Y#+au4?vsmTy#(=iaB3W-u?S=e}HS77~UfSQX{O#ZV;G)fa<##_ljehR9d#>iq
z+w;;@b3QP5KRWB;`Y1)Je6nfVLcaM4pWhmuR5{IcEIxbk_L@^i8u*UIFdb}|9MBzc
z(YN>HN8Y<%F5Nqrv&}!B>9~<eW6Z<gGkP2ICrnK+>bV`tb|CAX>^`wyUyrWYc-Qvo
z+jT2*Gn7BwIGv|x7dT;?!GDHy2WjTKM}F_7suH!u*yzjYze$h%KkQqmx4rE65f8D5
zniWh@lDew%OYC>wotkk#F0rtwNaAy>d;3<+t+7JV-AjA(E<V}5Q;<pcT<0xKu9V4}
zs|;g4_oTCT9pCif>AA^#GxSX*-kI!W<-X~hpY)$0Ls79JyqZ1V;Ah?)CC#*h62F%R
zANpo4CdK1fDL=K;W^?RWz6bZb&uX8!_)f;`uwv}tb$1@5i!g44oe36mzb`F1pZB<R
zCzt!mm+uZ)+`Q3P$@wru==cpL|E!m26Kp1ohkq=8e6982>(hJfWR*jA?r%;Ls_<Q9
z_F(O~{|xu^*>@H9JJ0&uoByrzqwn|ma+A}Ommd0Ev;9{3ESqF|<C=CAxs?a(7Mp(A
z`?Yo6@^sa?f0u}tZAz{&KBnS!kR{chorU>FIRDx|Vjs-5Ki~h&{f3^}?cc9Cd7=&b
zcgq|0G&X<wuD;%cvG{PD<+fcP)=ey|7u#(5WLv<VPwtCiH|=R<OyY9g(o|Hmr>Zb&
z{)d^F^`Bp_tAEh-{Xav`wPll+9bTMq%_?@c$A!q~<N4Aaj!7#PI$AKKGhYZj#Q?fz
z!sya}hUeE~{xcjDegB_9a`8W5UHyNxrRV<$#{FmbIO~PR0=}FdTkgiFuA96t+kEma
z<NSH2ye*UtGF0|ktvsmvhwE*_@yuhqXN`UK#Ja^sht1;DU((?$6QKF&?c$S3t0E?y
z@noFC!l&H-BzEgY#N`^Gt_e0wc6SA-#R6X*gjFouKK(!H?L4SQ0W)M}&YEJicJ&>H
zP2i)OEEwK(g?09`eB8+?cjM)yHU2E-VV`c_ah18?)vD6x%Cl}sLK8oW;4$rUUwCcY
zA4#Wezr23omBrV-O6I>y+d9iM+pT(1*QOm@7pGUqxV7{iuQQTdHFxW_)n>iRGsDEH
zrbum@{ZRWfTiNzWtlpcpo$8uwz;V1Jw=GQh=?RNx4c3hhbv1MEiROBUm!{9jnr>H}
z%c3>2=Im3pXNu;ztewaFvYyRc9Q9Hz|K`$tlg}P|zxDq4;+}Mg&#~LSzU}!quW4sJ
zaVI(jAKTVlx!6gi%QLC(VeDfw-D+;$HSBZqme{PE#KApDMp;he0^8&J(Z^RDPPmlx
zDr3nklUsEuPK|w41u6dLZ(OXe&0m&z-5gx8Z?w5=cL{t$Tu}kz%NV=<WiIp7K5YH+
zOMIeI=JyZoMz<^l>%J+A-($JG+Wpy--i}X)XB@YYi+k?2f6wOY3jY~e%1^aDKK%V&
ziD2d=&FZU$CYdVh-sC-V-m&JkLsH~~jk;TyZ)vPI|LDY>Ykh?2y!XD}dMh8UShM9t
zuF1>Ue2bocPZi|sX3A)j(GRk3-B=vFLHqHMUA}hSyW4j(PJFgu!k)s1p*`j+ZYy>=
zlo{+eJ>MXqGh9Kor7Ctw)RJ2hJf+@++}!6Gdq`iBV~t0T?5YS2>8_?Cht((@vvB*z
z(b=c>bKN<dvU`cqflHblr=$dpB%R%sNQxYjkvMp|XT?bi(8jdS*8F_4cjwC8tM*jA
zEFW9Br(?@a9fdCW4X0XNc;1{8_MC9=TYILoR_MX(Sy|^7#l4(<eOmbG<m|ueQ@UB_
zY&P-w-jRF7U22-(&p_EFybGOrdR8dNHM&;H*h%l4d}#A|v*~4}-1clYmUd*!FA49M
zuKpzM@?w#L%vJ9mOZQdx3VX#WAB|cgR(8p8`QE8Z8vYzjowN7A)YJ0&H3P+-scigN
zE_{@s1bL?tX?ZZ*z7mw5-2O9c2>s9SuXoG3Cba!`*ss?C<^H07GW)h)wozXhf6w#j
zty{08mVgt^-E$ESKq)84`>}Smb@a+oUh|;M^KQOvnYLESTkqu4Pm4<ht=m|ec^6Fk
z$$$FPvwiK$4zKy49e(MZlxx$s@1ff#E><uI-#yn;k|mw}!j&>RHt%T3h3sBiCq?hJ
zZu@uU(zI(vy3ZmVv?OQF+z_tX!7LF_p2x6Lyl3sa$0ug{URgWOy5nu$nT^YCd!}e9
zxu+J%?4L2?)9JVO%-^i;1}#_XJCtkp>z?J)3f*_lTqB-O4V^jF?Y%+4B!M%H9zIQu
zu~*;O7=G)2tN-OJ_>fcmuaP&O)XsnM`rP}?Umr{Vk|~}q-zaDkpSync4k_>Ioq3|Y
zlm0FWR4LN*R97$7s%%hTbXwG^*bx@M^{vj>L*)J)@7m&JW>c4(=bBxbdHSxmPW8-W
znT<y(L(e;JDQ@2QpMf()KK1;!((m8eZ~Z&^clPh~*5^L$dAoc2&-hpSE9d?=E_wIU
zwc7QKb!U?^bN?>h{pQ=O&~5LPrS}~*oL**LxZmRVhp#_(g`S?zedhag^Ka8X9<8`F
z<4W$CZO=R&=WklOF+AW^j3}R*WP!&kMiwUPcrow#N4eVm+b%EvEqizAoyn(uGd5+Y
zdfenc|3@b>IwQebF(|xHqU@gT&V5(bM4!8s`(?|f%X&hEvddl{+dchspuv;IIrXbK
zdpG@OxNP%9s=oEv<*&L%AN3z6=S^SqGV0F1pX-)J&RKr`_Xd?X#`~Y<2>G84d0WH%
zEnC_<|E=u(^evaxZm*QM`%SZF_r~45KabhBuRnXK!A$3m!}MF-(TA7cmk!jKp!)Bq
z!JduN!eiL<cBB;UoEkFqfO^rp<JbP=>bAA7x^r-GylW-feABO!Vi#%b@c8y_a>nGM
zRquN??K^%rK{LVO%4L)2w?<#D+4|YP*<5IQ>Na<dS6p~{!l!8p3o<1dRxEE}?UODy
zo6i$yzlGyULZsf8)oXQ^d9y~U2)#LS*&_F{?<b)%9z1>y&btfP9ql_6Ht*W?+o$}b
zN!hfb+Rkap?eij)dqtZ6ZJb*sv+ZE3LgS7rMHQ!RNhE$Yx$6<<S^bSUY2)HklYgqE
zhG{)D2++JEvErV&C}Y?3ed4nNW<7gV{p0AJYu~gabx*j?x|TjOKC{Tnc*m){bBxlP
zin#N+&rF|o{d@Vx(-pgBUdiJLduH(@f78|tAwh2fST+12H#xrGU|>%6zOwM@8nJhx
z6B)~UA5UPoc%m=x!h?xZQ&Uf<$fO7vWIauPaV!0sYtOWM<+Jy_d-lBS?vBsPD$5?L
zFZ+|e&-l34g#}#Saqm}e*Y8=o=55~6D<*fn&Q+&x6N=iBsk2*s`l;S4F7G77c+8rj
zpV;eb&+U!&ZI8UTe#`E*i3xkRPrB#U({M1>YmyPiIsS#~@{S)knVoE+@G@+ZcX@ij
z{hPCbZXI*ob6SJd+1S{O>&ZrjWG=q92c)Lm)7UmII=fO=@9ny0d(HIoHJmPZDP%Xu
ztQJ)`wxDV0z7Oo|7VG{QZTr0T?c0*OUZ0*ld@rPt&}-zo<&dP&nTH`MPs9`i3=fM2
z#r%j%-?MZ7mi>L&$F3Y(oR_-Y$X&X2YHruA_MitViVRLSxd(8lbv~@za(cJ+?(QG&
z)Eo7W%!}RG8@q0uP?3Y)QKu=ld*(d1d^~|$%D!t&>F$o?t!;0Wc5OEgD?TeeZF`_*
zz`2G$515ts=Z2R(2rqcHU3>n;KZbv&{%!m>^VxrfluX}c{~1=@e)jH@UET8hUww1_
zzS~oL0kORV)Q$zM@kiMLy{-xS*ac|dkQgjFe{Hr|72Awb>F=N3hD9u@<YZ8vsdP-T
zQ-PKBp!x>3CBD(V69q2^Y)L8UyxMZgS!eAwCCew)JevQM51eI)Syi=eHsAWCcOv{Q
zDf!G0a&f4by=s>b-}NxYDc=<2u0+1NmAA04G(UAkRLuE|-+IYysb#I3++>)iS_T=^
z@-Iz)EvIv7i>!Ij{wsOPZQAUHQ!^LeHSTCxD3JI2sXy0k&trv6oDA#PyB=PC`>6e>
znyuW&08aJ!g13Br95nRuj1iJpWz1>TGnIMP3x#>ot1H&&KJCj;bpRjB8Dzwv+{E$R
z)Ia!oNv-gyf7h<&<k-CVS)aYbWBX&tV~>n``sOX#x%;p9!*4U!y!;jWzP-ji-)_Mq
z>9lF5?uy=&GQDBMsOPhofq9O+pM$lR_T+lr8oOTE`z{|2EmB!`CO7v$Xy>+5{xU4d
zZT5#MELQ5&s6VjvJ7;~GpZ`bEyK6pgW^rq%xE)k@*l_S5OPvVgmB1LO8#PwhYsJq0
z6FkrVcXPO-irDGQtamGtD$O^<G|lLpUNntmVw1ZmXx$Im(HXFXMX0A0T*N$MV^rZU
z_+bu1H+TxF_8)!ERZ)L*`aZd9YP&bjyC^#A;R1bOvCxFon~T%=?>apAeA#;bho%bq
zf33d!{~1^>{Ac)R`n=Bcha`WOO(^fR>1MMRW@e^r+!S?-_q;)wrN-`X)`*(hn?E)7
zePO(lxnFpX;HukOzWr0b94LB9u+(6C&I36y-z9xjk7a9lBk&$``{+yl&CdsK)g8YQ
z^*dzpDUR1B_d-&CoL<q-V<p3MoZ-98^}vT~`Mp1U@7bEot8|E4JM_|)&znS!JyO{v
zJ>zTI0m<Y^g(nyAO|p&logFgUyE|Y@t&_-o-9=}Xg~VB=oOAd&eUf#5)biSOKXSLs
zRNa5IWbv}I9kS1N^q-tulXytTkMBvsjd#m!dDCA^o4zeP{^oTn{h2aRt#@B#>8qrf
z3VUm>pJtTu+0g9p)WCjY9yjLVZ~r8&e(B{u#CD4Nb>x<}ns4<UT&g?yoHON<WasDq
z3}xXZei6+(HU=4SOEJ9A+tSaIInTBC*;3oJN58C6%-p*2(zA!tTYFQCe)cUmQP41z
z^>fdhD^+R>7v8>;Eq2TI&*bx|)vR+b?7#YShPGi$u8~cvUrGuy_bwN$s+8h?N+0%j
z1Rq-La&hewh8Ld8n{!R~zn2uea=cJy<GYl@jPlb~Ps=o~OlXr9uX0;%dTg&ygy*K(
za^HPT!79}$UB;Qu1V5*Uev+Bsa9-kE2J?#ku*+#z)h<1{qAMTJYJNInv*uLszDVN<
zcBxPL9$)L$jrP4V&t=0EUA=iGy>}C4#;n@)&Z(e+XHWB;BJJrLE}2?<^|iX>%_+pq
zoAf;>`?5-!W>Ef?w=Rs^-^*vlybG0AelUM};lp^o*cUG!ieyW?y>!@V)~&Yz%Y+`@
zy4msIlefF3ju9uz<P#^@9oJX1`+m6EQod{HnF2@EBVn)3z1nZQBj(Q$9tLlD*D%{v
zM`mrC&9{<oy57Q!SuH2`X}isIS-0oY$~hB1ZC5C>n>zo|?d;uaIm1p}^WOPr@8%t!
zlvBb=yPj!EFg*>o4*06H>HU|z9u*5`ojO&&>CWAQ#g^sUC!KR@GPvZi#^%Y)FarVi
zDR(9s+U#SnhA%GzEivn>e7JS{v`3F39yY1yt4uNob!AqWRKdVk9292X`6f^QOQ7tU
zx||DlZ{6iM%#b2*US`cIKek5#jg#0sPBKqmlwIFda&zI;yyv^NY`^?QPq`y*@2Q_b
z+J|{o{qAF6KgVThdBF0ysQMpODeLT6brWU32*qZJ^;hO@3Q_X7p2zWAy&x%^p-J#u
zUDVS@m%f&4znY(G;`!y-&TIc}Z8)YY^;Y24l6;lunG1zX8n=ttEcX245;9NXV(D4q
zfQu?ua-K}QXqvKXW?JWwT-#f|(uUIJY$5igY@Cvz&lzOd7C!pR?sw^H^|vc;)qPbt
z_w;dIoM$G<$Z_}ZW~K!)DIdd?ujxFQUa)7Q*;)}HSFJlu@n_RQ9xuD5=wzT?sKR*M
zt~~R>-;#>3&we|6y{dQn^ToV0yPrAhio?4X-5o4hG7Am)XQc(P-Q&~=FOI#CUwZoX
z$&^dqqwcvbX5YRe<95e-m1!k~JDRsjq)*~^h-$Fvt}S=p{agO#)@aFnclW=U7kkM3
zmRarJ8TMxPew?$uGV#@|oLft7#YD9(ekHK%XRcVP(V~y1)r#29?3s9{>bidU!_(V$
zTwkZOvH$$u>m|3ROc3E!-J^D4qq^mx8P62`Z42!3vR}%{Ud{dE&9U2R@~x<>@>wk|
zr*m}K=cL`<z-qktQH{Xw5ZNb&jLr<@u%0X(d$Cn=OZj>qtc?%Z5h=y3eK+ipYY)@W
zpm${oDUEaZ10&zBeHHMdJt#Knlt;~$i;tqKtG^lM&H5DbS@1xRyXFp~b?<dnvKII)
zZ`aBFYR~y9Onl<cY1^aPR`Q(O(R<>0ahs$}Pg7M$=Yt=!vOC{zt@Zj>dGBn`<eyq0
z(LQOt4t=H)I>#+pCR8Xj@LC_$T~RUZu~&4qtH7R)i+{J)U6*j~H}Wo8u*S#X*1;JQ
zKF(cWc>DZoJB#eK(noF;nJ(S7kgdPESo}t*>b&Y?p;o1Y1(il^r3b<ar`FGY%JQ}Q
z;g^3m`u^oQfi`DVzJ04!n(<)j)TuN5?i+mg#IWY6Lk$B%?9TcR>%Uyi*WDeT<<Fcs
z`K7_J%X+t~Bbj(R%pPkgGZ?4#e-uCTfN9^_N8B$HCY{TUG`W2uzhq_E@xnbb)c1yP
zJ#}C_(dSyqI-MnPhH$5jO>KJZqt=U8Zv6Z9uG-?U_k-`*DoVa*Rix`Y&QJM~dt}b>
z19!?^=(jv5ow~kM`t|FTsaq$mOZznS+wIfOU1s!(mbKrVKfUmtTZP2N^oL(IUWs}n
z>+~aPX3AV0^A)YC6E<6?Xq26{p1bDEf^81c;Ti1wYk%yIopt8buiEuD9@q26zY23*
z*Q~rQcc$$1%p)h(98V03pTY3NSoF?E@gp2H#s#|XFZ*^?=uG<d&T^}uw9&?bpc^7*
z-tpua)a+Y%{!AI@rc$;Ow@+uPEnn%GR&w&o>gqH@)~(y8C}_2~NlZ|7;GSkvJjrt{
z_k3RN?v8hCYgam3M<35ESJ9O+y^|5q@H{Qx=@aWkpU$5va1+m9EM9*${}Ic@wz<mZ
zjgMXMkocL)$&*rMUBo4#<-n5W!I=20X5$a*z^kUVVwGP@8uP>h_O#Z_EbpCo?gd+!
z`rTV0g(m`zPg984@!{^=a~uDz`Q-oY=`=~DDF%OU9b31M;TYFMlLt@4{=QD=QM)bW
zHfffPxWUn4n~P`5O)m)N{=GT%Owa1A?x%Oo=y~$_y2JstR%l;B^4GiNe>)$(^$+`0
z^M1oE@8YL<xA!NB-JT<pE^&^x`1?GgD>?RC>@F{;tiSoKIcV2^2A|-kw`70F=$p&$
zs=wQF{L_DiwNKKQT-|b`bgtBI?;V+9kUjM$cto#2H(oAZS&?@><lptrPv+KdE%|!+
z`Hcg)J(WAOCluV@m*?ls+_#hA`2LSy=k|9=yC*0AUcE!-N$>ln*e#PezHKSU{rOlf
zD|I`Qp*nlUU733d`>xoyE?8r>$#L1fjm25&-hHVC2TS@U9dB$%=`VV)L(%9qALE^T
z{^j3}O#kpo{MyI!TK<KZ+^de;tXj3|Oxe%omLAb?E~kVh?!5K#Ef2aQw(a$G`w@LR
z_H?yq`@20;XN69%PEVgvls0igJi~Sd1_p-Hn?5dD-kPU>*?)5C^mg5?t$p6hCeHDg
zG+$>olc${jeM|K+kH@pc?-}ggy#LC?5=-^Xm)|FBniTOaz|&;1ikhL68Kd>GfZI12
zBosEDT3P%+T60Urm)*7gL7SU@8`)}=wH%3hc2{(2==Wm>1myezG=H9};>q%TxZCpI
z?OmS7Z<})0I{6qp@~D}+pzyo@gqgCHdF~Pnhvy&Jb!FGF{#4PqON8_`T(g?Qz37Ge
zO{r4BjomtCo3?p4?=<_gCc-oE@oVe%B6@wxj(^`?eDk<eJp1lQMWMV*h1;LpYL*|)
zQ+Z~`_IP_xKKE_!72RKU?`|txxo+tc4adSf-BXEE{<ImMubJd1ljLpBzqD`Bb%9sn
zhpwDfd6~G^MN_AB=50miZIO50rlqoOVz{;2!SZkV(OZiv;*S_--m1Tu|7EXTruw8z
zJCF3B11zUxe}owI9xPhVsKCh?cZu0J`p9*`<1$YfCn^`cTHEK4#Heih!T5#td^@ho
zbqDJ+)OQE2i1bdcR4Bb`KjV|-gg-mNc}>okHSFJ`oXP0)MZoRC?W4kHRo-=oE}fu}
zu2B1U3*+SL4eSd<7*#<D8|{dfU0lym51hq4k_j5kM8~N=n!RR6UaC8pUo5-jbzy#?
z%qExAfQvqp8bXXFar%_XX3zi6&?1!ar1Qbm<Y3(+;^M#GdRML$eSEi3Os3M|q)zj*
z&vvnkSE%mx(qKOSM}PV2d(yvMu1DE?FFcx=x%AfUTP8}5B65ZIBA;@-{(V&XKSSA>
z;u#Y{rr+b)eSP88{KY#ad+okD=@F;mp6#AJ24{H$b{r{su>Y5l)rKU7B(BMq_bh5K
z{%R|AJ^a(Y%er6c!pi<m`d6LvToQ2+#`H(|+-Dz2cg)m(ysdG~x{}{ZvWt~Hd7jz+
zmagD<;CfK8-Dc&{k|_b~?5lpL{Y;tk?%X@;mTi@JI&W>}ZmQfA=UjGliT>6D6$L9h
zKJi_8{r%`!zTA9=i-}uzefaxrVX4V>@nX-EYbQD``>V|6I%%QUP&k2G<Av<5>xr%m
zg;nN_Y8UfN3dL5-Oq<3p^6A*M<u#jCr{6SMzn`O(Y1^eWMf_)*8*d?9*^V9q`1phm
z*bvkE<C@O4HFc@8j<|SmY<G6YrNn)=4ZMvuYn+r6OknPLZo9KT=%e54?8VvJw}pqz
zYWZcmXVabA&P7WnPK<a{ld@2i<4KuKVa(rc-78!l@k(i$L`p<ti+^7pe4n$&xj-*M
z>CeBsVjah}14eT_80J*_v%g+^X#1?vLs`LhZ-Guk+V<P$+9LLHmly}-fTx@tHJ6Ph
zn0@d}S|Iy$dY4J{%daaI?Q5t{_I?_-+iQ06A$A?Vioj_>eg+qJ{FAz{asTEkZyxX2
zu)7I72EobFaYIGM;K73?d#<O?FK<n_rxjuHXX~+rxs}=4KmAlfyY5CDk(i+7%q{Yn
zA@*OSO3$O?O<(>-9W`B9T4+DFas_wCtVbU6-1^^qSaAQT)`En9l?(}@4>lY&U|aG}
z@pA4S@AQX1^O9qo-re)=Sgf~Ts?%bLb45i*5{i`T-(9%;!cN)yuI|#yr7n$!;-bVn
zkK{-^@R;-9UGPEK@LQ|z-H!dwa4386z2n&`+d5M#^G!~jV9|NYyfDE-MP9T06u-qe
zcGKw(bM=EZTuJWA)_kyG^Oo$4u(xlYesT-YDcj`6(k7#LCynvkjXvXD4dy2Ic{8j`
z565Iysm)HdR&<+m?W$7JPIi_R?2-(RZ-gxs2>{(O0LPJ4-#bd~^G3K=uZlU&A{67A
zx8~jI&(^Ky&o~@l+4v<i`PNo#{-fKjmq!V$ow{av@zLt^!Y6Jg*1Q%y6J)@8YF*jF
zSFQ{(wMpl0uIqjKw0BRzsbrq(%F2SA(G?aq4wjqUnLmN;93RVstXsKPkA!{u)w<;J
z={&u~eU?*aK2&FNU_9wmare^B$~~6l#g7t;ZF`Dt@e8h7z&#~FIo8BwQ^LGO2@LNz
z*q57R-jmtArB?H3PoY&s-+zXHU8x$JeXhGBp5(~Sm^w-DPGdu1a|7R^^I?}uxw}_a
z>pER}R_%VXSjJd;i|!<Y2Qn*9O>BNqtF8C_*gxsb7q5r@ySZ`R(RGhEe_pVwcY?>8
z#jM+tpYrbAc_P5iVqN^<dxBRc`$hA{alhWW`J(EjrntM&$8$9bB~n`sv;|6jYCo?g
z>vn%?r*)3^@`|R%Uc2YT+WmT#y8H6d-u${_+c&K-_txp&CA6_JvC`p)*<-Z|Z3o#U
z`1^s9*Go#LW%R91QfX747h=vi<FT8@yTdkGn>J0VU=gSkJ^7>E{Uh(QJ!0oLS-Z2!
z%<~koD;`eMc+#@ld#BG@iyIZJ!KYoGY|ywA^&>3w-^tHgPS}?}ioWajT#+wy-_<9l
z>i68Yk$82O`*J>mtn0Dei*H39uPk15<8Zc4TurfOL07+ANIs7r*V7B>%g^mww0Q5e
zX_rI#jw(z_+V&|nW=rCn!$KeSYc-vDcSq|%9;YJ9lv@=$-s+dk7kRN>t^3>Sj{V#9
zf<z`6YN>4BC_2gLh~A?~JWZ!RZ7!a;<yA$n@9e|B&Muo?b#dl@hKDj6xA!hqS<{<!
zN#{u61jc!K3)1Ul`54Sia%)X>*?glu@xQt8XxcN&NsmJ9Jlev0yEj<7-%)um!PZ04
z@|S&2{Z^B+`a#ou=AF9s?_IT-IPW&^Od)rVBddG#K1;^!<U7$|_NMDU!-w8i)9Zxi
zdqvOCNtqtHYscjC&2Kq%c*|85a;@q9v}-C4=hMh3J@bq&`(4$kG0a~2s-I<6>+?>R
zYp;3YB2vVUz3kUJQ1{L<MN*lW^ECeq<_l;GBTPY8`0D>;yj_1I-1k4jr5ngQk3r{l
z)_wlxCD#i&ujoI+U+K(PR<v7Ov0oGgx;X0bm$m-Cg%3nMTl?ha{lwi@-_@+WUH)d*
zj@+FGj}`VjxH7%YBv<cxU~RB}->K@5ZBv81m);P16xOAzGvi2#(YC+44>e9rf9ZyI
zTJYM^{|s$!zDln?Ju_vl+Rm<9wkHmM_s!QnExbbE&%yilW+87Gnv6KuWc!bJOD39&
z*Qa<}#66PkzOB7}tAlEv=nigat+s+hBSUL9DYY1(kV*L+1_zgO&(wL``)GS`jp|O0
zY32L{y3@>yc4$6Z^KeN_gQ7Zn(etEy?%Q!MlTHWj-o4*GBf5RwlZ9o<4C|O$LQ>ew
zLPL4h{d{_3l0R4Gx>*wfRq|^KWlv7BUAS<PS-8`jWTt@BTL&8}WhRshI2gX&Q*r&<
zwEH)|nN9y*oR#itpL|8kyY@drdgkFZx80s_iI|__u>K&ig16ZBW9reTPv?|Nh2MPp
zF7MgpYk>tavsbt*^IhFIqrO;y&ugPXngL(7lRp2Vtu5QFTE9L$I`?+$n#;SM-Z}E&
z!KxLZ0euw?dwS+fIx^u$-Z}n_xs!^&**ZNA=-08Fly6;NQ+x6GKK3~A$>$s_cdwT_
z^zGN%rAPNJ_Rm}v8z-GD8)EZujRJdLQiFu*=@ru4584mcESTh*9Mycx?b5}?(=O!;
zc1KRjJaJR}Tax!iwqpnG$o|m&%wT0LxbQy%*MA0Ivro6Tep~XvY^L30o?N51+qX_o
zxY3+vw8((jEaE?dV2z%M+K0Vcc6IFc-n}DTYSybrrxtOsM|YM<`kzRa`F>JG@EC*9
z8>0G@*RT9>U6p0eZ#p;1T7F~H`9=QK%kLg6-{s1tbn+SRs^rN$95-T^)_&&Ed)IXS
z@XO>CTaQ?^e%NYs(kdc9kjq;!t?Wd=+iB(2kux208qC(+%6xD;_2RlO<yW?9n*3Zd
z?~ruaM5bE@PH)djWP2o{!K?O7;`L{<2i&v#HW${exO*e+<$s2xT}>M6oH$$d@0xN#
zxR8NS!O-rh^pwK(oR1qr9$!xEj@)@wbjjy;x(~OPs^oG@dz^BYJeQjD`9{h6BJkcy
zgFmVDwM#3sqpz48me{jx)3l74w;8!sTJL+!<iOJ4#>pVWc;ft(J-%iW%ga(OJ(>4O
zyVm?n8~348XA28etdsdfi<SuQczb^;?-q^Yj;k{_ytXp^Hof4Ij`+4u(I+lWkkDQk
z<mL!E?QFh%>)Un9jPKmNd)j(w*PfOIdbw$t6Fa!rB4@liz%0vjfwf{!pb_u(Yl4SW
zq~=tWzU+E%Qbt!L>!OiR*Ez|hjr^x}==tA`ne%(Slunr7Yi0k57he2oTb{>yS?e^5
zzF^PPW5!BW7CPqclXg5^^}J(?r(gFv$7Rvy3v1V$-kWl-Yun_Xnli;H6G8)yN~e}v
z<b}u?76*S=HhbmmzjIrrUEno(?CtS(+oC1L9EWoy6a<t4_O{!|9gwKH-&J}ecggl`
zmld{NS-ku5oa4GTl;3<8w~J~^lx9@aICZd`m3L?CiK8()uRYtg|0CO?nv-s`KD^vk
zrsULZd!$pk$=@L*^I?w|i`t=^j5osC);_GxjmqA6>)pG1)h%1%jhJTk-1fQbc1kiL
zy?D+O0S6hb_3CYJ*KOVFrR(jz<x0u!?|naNSE)>KE$Y~?LF+DKZ?cwyx>C%<sVvO=
z?mMrV{Ab|FtZIF?+V=0=b=z%Quk?TF-ZJUu+n+I0eb*!xHWVn|;0QB)A$oFsOYWA}
z(YoRuoBHni*802(FH%~RtEn+l(5dnK45h$N6O?+}9J%Lh0;dY_uqawr26UMH>3<Go
z_rHl=uK%)43U^@)Dv;rLP4#=RihQ3vlg|BTI3g9g^h(8jp6?rvy`I2vYVyPhj(@WD
z|52~w|Ie^+J?IR?9{WF`3?(Ar_Wv0;?}N^O&jy_VpUnTCLDYRz-JlAWAjil4Tz6w!
z^Yb6YN@YGRn0Q?FkI%Uy4;YwJCRH3|$P09(bXlGI>dehqlQRpm#QIk_&3?Kia>}Xh
z<2o}>$QylfFMJ*H$MTW3z2Hl;?E$Bm?s{gjo;|wAN2NO7%;449J~zh)6O4PV*|tqz
z8C|h3%v$sD<>cM-o^-cwpLWxy$th)f0?TV-lbH$s85H=nn%vGjKKfv<%MWkQONv{X
zF1dbK`fRRUq?3E8(e1x)cb<z>QEjm0eC6g~-ECX$ensc((`l=di?dWCcrM&gUNEtP
zYj)$YN0AP)eh*(qeES~9|MAQB!rJ*>*Y<CEDwsc2acAIO(eH{s_XU41J{Dyre>k#g
zS@(*HK3}I-k6kB8=*{<PT(dq-EWMBW*tD>Oz7qjU=9;IxP3)Wb!o)j!cWn8QUfVSj
z4;EL89^LbF!kX3JGLjV-yqTob&ONZ|NuR?I(Z|bvs4C{XNK{_$^40IBP7S)JaGZPE
z3!}Qg$#1mw$Z1{<_sn$<*|p`eg7|i^tn1-gU1vouxgR!Ti*SpU-TAub;v?<s?bF@&
zZ`nHO&CBb{9(h;H6!R2aFiS`6)9MMSEKl1RzFM&NZ~O3U>++i~&BMa1rp?j4AMC#|
zv+eZxF6-`vI?h6qIUG8SL^p8;7?~$9U(h$rHTU1Kb^G2cy1L7E*G{{5)@ZTMO=b?x
z(=r<*<Q8A+G|e@W4U*N1b-HNEIk_gR*QhhL@@cT8^3yzrH?`W`dp_J-y8Puev8dRd
z_X?L5TwbDWyXV@aj>D{dFH>EUIqu!ea46&Z8LFtAWbJ)BwmPKsOZ>K5udG_kR~B7z
zQ*2NPSbmQ4{xfZd$g+i!nxFMm9jv-QvpX={m-%p;!{^g79<c$&8v-I{X!TW3Q((L^
zLCfp#$Gj=GuC;9A&Xv7n`*!wep4nboJd1@-PPikuF}m-s<x2-~-LH4$-oL3&yPA{s
zyX-&1rpj`T`x!UCe@pmtyZW)k`yl*DHfHbrcD;L#<92i%v$y*mdpR%2A;4tXhuKa?
z<~-+0p3!Ra^}x@a>z7oNhi?C<qx9yLe`e;&ds%|Qx*N9070%8(Aad?}=LhGv0p$~p
zu<|hOEPb@w<VxJRbJf!QT9-a$F3UbJ@u2F?7L%e4yqo_P==f`~JI}h2{oCZTdF+9G
zAuCyCPT-wncXvgt#CspU<wd``KAV5ow^6Uh<m-i$zIW#jg;#0r$yB&qt{D-g&|+CT
z)05+#xb#kjN!rDsmrWB_yb`;R8GPsPitI9}hTUBeEd|E~xAMstx8GsiJx6PU;`BLB
z82A>v-eq;##65JQkhAc4E$Nmsg^NYX6X%IWMta&XaoBXN|Ifhb)_3dK{3Y(SEYqV}
z7vGD{naVNA^mdcw$vYBL4=A)0&!4vQcRbgr{WtB(X0pHg<6XV-&J)E`+i&fe>HmH9
z^JdwI#H!p!zS167zWiqpc)9s(qGE&HrcEa{xw$x1ADN|=xLd_&;qL_#JWj|wU|!%G
z?YLvd?j63)zSC-TW%ZUsPMmeo^K`rADW2n#`0SqBYVGf+abEDkll9p8;*5UYBT9zK
z3o2%%WlTNx$gFo?ruy&I>M?>b_ghS4<6VDCzY@&a9+W8+9C2jR*$m|g|6VKIQQ!&r
zsmyDv$(-k?+I2kl;o5kQ4|8r6y_|T*U-aGVibdxVw}p1D{eEm&SX^L&*6xi{1fR}4
zJ&WOsSI<H27}dkBl5+(os%V*OZDeh*bx;kNct7LIN{t0fXe)CFo&NLuz5SDgFYbTi
z+W(*7;<l+5FjiQCR+S=McYu8QfW6n1{|p;#Sl4CU^Pl@odT-qGQ+K!5onGAr9hny=
zZeTvmm*2NN@<Z7ArFTraS>L`}ov-ZXkg&eoY7%%=)>>ch!(~;=zwMu|^7`-U<?H6#
z9b?W(K6@~xx$W=gq9O~K(i5!J>xKW$j+pFeR=Ll->|^xNXa5=2wYlnCdM**WNPF>?
zIrEjbeLWZ7ZsS<9S#|B#HNCl|YqG@3zULS2ym=|RojHw9N$^OB(1E4}EVtX%x?f(p
z`{Nm_?#zFod#5g$So!IVea6HtiJJ_n`^%O+EIR1%d4`^|;iAKb3L;)<7v1Xpdc-jH
ze06@N`4r`*%%0YpUJHtkY+{g{k+>^`i9vIHpQ5j{-&H-G6c4>Enp;<jSu&esOC369
zIDuJ6?e)a(wLeromVTXib>Wqgj0Za|zkRz*SN8c#=FTM(nWx|2a+wzwd($yM=B=V*
z@;`y<jNGR^F?a7rFPmvMJ9~Mo*TjP|LM&$zANQX*rtEs>=nV#cwbd`8_!io}TVGwP
zw>jhcv~L&ITrU^+yTX(E)b9f=Gp5>CG-ya9t>4S{D2B=PdY-ALjeb!-OX2xdr-iq+
zzSyyShht{JeeDKwjZ{gV#eD5e49R}Cj~lx#b}Y<abmCjtEzxxwi&eHCon;Z5qSLTJ
zS7(8XhdSfVJ0}WvFWB~B?-rrkF`nh+#pS#&_f>a#vCRu+j&6DwqQPXwz{>sI(bDp4
z#UIgSM;FJu%(lHhv2gL>#n$4nha|4KhRN%hKMFf}%tD6mfykHlg2~6M-nGl@&)#p<
z<T35M8SCB^+qT_TeBFBIIT!nxw>R=r-)PJ3F;BaGDXvpJy8Vi9Ksb+`CyO>CgJADk
zsi_K2{=9Ky&y<F@A{g5rYyW<$eK6|Y!etUipKhJ9+2z~~j!@6L-y?(=RG17r7$)$!
z)h&ILxutveX0_=m-zP@D+?QeyCl;37-Klt6qG0t@g}KM`{;bGd=w`)>X9?k&pMUgo
zOAY5ed-pE#u1@F^RmS3MW1k*}0HZU<%NQhHh&5;*ebhN2ci)CSNrfwqFR%9rXY+WN
zsT|fhVM<uRSsjkL(1S&Fubw==TX8XILw}@HO<%kF6;ta1y_sPViWNO6>kMZKUObq%
z%Vz3v-EbS%MP4PbMZ8A$s=ME&#lBYi61rvnNsq^~Rhm|{Y24P{dAMl7$L?A4TTSlz
z-GB2&Wm`k$bg3x!+^wRDGu)&z4l*<fwZ5@@@QvZ{wLih@4(F=w-8PeT-BQ_mbDmk|
z9h6VsvGdavV~!h~oNi&<J2Y}ny>rugdTzVv*8dD0rozv>Os=>4Zr&&)68TQW<Bm`j
zv$8)=!Ujb%u@iiUwwUH~-_E)md+vI9+2=c|i+)ZJIg@rPZI)TUsl(QDo+~slJP56{
zG0!bs`zkOiDt6i8rT6!gAATFCvPgT1YincJ3!ZGrAVy1}Cp{|^B&uxBtz7;i+53uq
zY2^ENZ%cQ+(OXhKC3ea5^ZBQqtjbN6?qP0}JK(f&y~8@+8s*&OQ8zPoxlSqjmHjF`
zX!k@>;Y?4L6I~*FH3x<Ir!<P>7;(gWMQl0^w@10U4|K)&vG`BS+x|0bSU3AW!_p0)
zlVQ*XaY2hB(J;IH!}mY=DmMQ+wDCW~OVPEUE>HD8=XpB+88)n`|K*w;i*jo6{oX|5
z7Z;9Q6TEvMPyC$Ft&`<4*;_Z9&z0o0xVzQqKLcl?`iB5EJX;_VYx7sWymtLtQRTGl
zfhrgFT{2f@2zl_yh~sr!{=>8UXRq4Ws_kBomYliz=Kk5sQx$`Y_Jz1hU$gi#-!wp6
zdu!K9#hrb!2LBlj?fcL>=|_>dU}VlD>AOnat=<a+M6#1EwwC7`{CwxMPFja$r-Izd
zkT+X3^4D#Zu9)WVO`Pdo(1C=FU6w_AzT8&oD?DKz{QO&3ns=>IzVM4*(-vF52-D1-
zovAuc`+$nEpn7zrXGXEINzDrDeNJIdpSAsGxGi;Wt!&G)KNZdXW|v!%PP5%Mow@km
ztErzuZx-$hX;aZ-U|$dzm!JDEV###>X|+bhs`oog1#8~Oh;Pv?dnrBt=l3*0v-4kb
zB7``TXAyk|ff3`YsrW8oi_2e8k@xY-+o<Z<(XY??oj)|KGu`G?lygPXi}wL*PUVSi
z6F3z)W&f%BW`4~X*FJ9VOX~NT$F}o|!jAN&0~>a9pK6)YKmB}v#q2Y^o@u-a%*8zo
zRji_Ce`pD_^_pZS$}VAgxM!m1nrRbH><-tNc1h?0@9in;KZ+XF%a%|#HO8P^0kMng
zIqI=%C5$WO)-F4{%6I9}6;XBzx$>u7Obgc1m)VrAP;>gE?D4f?QQKy(wCPM-5fy8b
zDZT5U(azA)J1q}BNLI4%coMFkxFoCa)vVGb(}YySq>jE@a($V{nV=>2GjDY;=ijrt
zwDZm?JNJY3dT;(Sw3~_NF8vYq=H<j2w<0s#bYHv(dbs?zP2&Z9%fGk9?}$IE<L=qY
zP{s23aCW}#(IXoVvv|aLswAxHV)In_z##K%(>wcz(jU#{W`3LhW^LH9N5S9X%}>v>
zObNJob57F%?JrLl?zJuX$U8eeW3sdCp2;WH%UoO%v?fnhHa3!*Y4?>Csl1;yG8l4s
zu8aG|>vZ~H)V%feA`|bv{LUQO`aB}+U1(##rZX4*y|G^9$@k>^yP1wG?^u|N?*9|`
z&%hOVvNHE?`{G;Y^(U%a{Au=5r6VFo$ADXt&+tm(-q#D(>3w$CbE#ynsE&Bh&OMv9
zS6Ak5xwhTAQ}UZh&&k3WH#}bMon7|fK(gYT>w!xSny%|j&My>QVth1T%2RgM)J6#n
z7B_xH#s~a90j#HBoeLO^XDOL{_m<mx!w+wYzOkjdV7l0Kt|Sfl@4-u!sC@{o6KK8r
z>AB>AlMA@J*S&bZ+<nEm)k)Wk-hX=MdPw4aLRyYlL4n}OFI@N9);QOv7k;Z(ddFFJ
zS#TcjB(~4V(nYWP_w2X&Wbw0o#X7yyhr=h|$($a(ZF=$Kb#vVw|Mv1OpXzkeM&r#!
zjUIv5au;TIJnUpwOxb+dG*{}|<)DA3=6yajJ*;=_+NB+y+n#+)>-|?AdV7;yUG9NR
zAFngWI%n^)`a8dDb&}oXr<IaB{O|qTy=U*9KexYayHk3raE{c*?E3WD=YRX&arY~Q
zHRY>0{EO-SK5^s4HaEv7;d2i@`0HDvy~0s#w*0r|A7-~b8>aVcpSRLtlETdgc^R9E
zw|qQ#T()igQq%sf^~>9CS(toY7J2J-$G26@!gquk-5tbS-u6|zC}7-)Tws&Dq8)8E
z;RVJ?WC84s$QB^6+1W0i&Hk|bXt>y?lRO{owtPG(Et-;8Sm4M~#9{MnP1ZeyebYE~
zo^74%yQl5D*Yuon>61;>R~^=cFvxT~2@i-YaFcAbIKT1Q9&Pj1t?T(;%PC#XnfL5_
z$o6^Wd%G+HQ+CZs=c%xcR#v{WB>F!Ci`A*?`)oGu+chmZQtDZ*+tv8oJ^M;LI}WY8
z@O$&8ch)D)Gc!nu$=Pk*_tELatDO4ka@#qDOFvX^og}FCY!dH&mGo0JW{>=mALLo5
zT&l^qHFw{_B9k9ayuHij+>W@bd-P5UlZ&xqtD#?kgF{4KIBOf*tFo&5%{rxGJKB$z
zDS=mB{9T!+=$WE(?xqCN+NYedTg#ggcTCFemy3#%-+VHgeeUW*Qn$plB7<DCp3I&2
z=iQnA3<`>yJQbwG<{4%83O)Mcxa`i99c|adFPEC`+CC{VHaR5IOk0uXRrC{!FqS;a
zK>0svQT;Q&`M=@+F{3`~KSSzI`<&R>`%ZrAH?O<@wZ84`ezUvxcdx0w8-7T0S-jUh
zqm5U;O73Y=n;yEQD?wrMnI88oI@J@qceTeD3#=>qvi{-T@I&1yv)UFuS}n2c-&Ly~
z&C=DkZI1RX*p_dycvDf$F|PIuR)$+_2N<tK{aBRU8+6ZXL$As2-M4$~ZWR{zEX%05
z`}^??rseNc5Aq%PGc$1VwmJ8#KJBqhU0t7^{?<-@e)Ok3{~2~aRndK#o^Sbi<8GPU
z7sW@dYyA&gyR|5`UpjL=i@DI<gDJPBZlB8YDgU!dkinDrW^s~Tz0VmE%O1Wue#r1g
zb#S}?$D_S>x);U1oR!;iYwm(Rk%=NKVT=*~8CLf?mgTXltIT3}qxv!R=n|<JdoS%f
zUz#Z*&ZNJE&9y7N#BJt*Bh@~6mjw3)IwqXIwE9lPQ(YU|%$0s7OR{%w&Sv?~aBEdg
zOiQ}%w}zeEEvZk9_v9Wk`0B?Se9%Dkp`6W@?CzF6(_Oi7!a9b>&RkU5R+q5mO|e4J
z?~bC!UHxzWas1Y^e`vE2bc@{W`Yrpn<kq~mKJ}?Q_xRL*tG`#=>?!WOZ^{sJsV2O3
z-H(13v%*{TDR(2|P2Nnm{_f54@ko@B@N<XbPc36lD<+AoVBfM%PB;JH#4M}S?|;<G
zjQo>DK8j5a*`B|Jv&;DB%$J{)HgImyGhm3Hw$1*b^@sYuyjAl5coP3JJX*oLU=ip(
zWWPW1{~4U)+W#{&OVs~Zg|3RpU&`NfePfMtVZP3U^I|iLAURW5z)_}&-*V0G`NBSn
zvU8oiC*69a-D`VI<2_%^>hAekMsF4*UY*!|%v_Oy_l?AZt9ybU%uRROcj=u?^kV4T
z#jAieu2&%wC%F~W@}{o+&(I{Bntfj`;(n~R?wa0Wv&C8Kx7~}kQaO?so>6=AXSwW?
z^u`9>j+)3qvyG{FChNa&-*tL)NPGVl-cuiRZht@CXLP|JM(os+jn1u>W%n#+=}K{T
z*NVAs-gaSaY4=RkeL5Epy;e+NZOlw%QgXE5J@?GH_eR0%I@$jWE&EP|eq`+tE3;}n
z`a*y0t*r}%jvM6bhPJf1S57@YV~LtdNWzZ$D`oEUFS@v{Wb4Pi*-v6JKD;=0Jb3#Z
z#om<A#M^bMIdhU554>Y6s;!QV*b^$!#v!E}cH8&z^WGzE{I<ClEQ1=%E*nf{nKS9+
z1QElHD_$yl?Yg{w^H$lg+NkIqH9MYNQJd(y=~Pqh#c7|utx;L`EoPdAx1@yF>8qyp
zoWA*My^|m3O5D94<5(*aE;U8YDdvFkr<1ooze(nCJmz`8x@@xRw2coNS9z}a&v58i
zA7{RtW!mOh{~7!fR#^&&aU4;4+9vvIvw_OSB!*1G(|S`M+;#GP>$%Rxp=(xW_Rp>z
zlTJm>PRhS6c(2Q`M>8g|z({+|hrM5q{%aP#=lSfeqt3O-zFYL?d^q)C%WQY<J;$Om
zUhbB(I9pV9Ykt$0iMcv;W?S}ezjR^S+-2LArilqDXIu^3=awWmlYPdMnw#nh1{Xej
z@2b&Wnla(_-HPpp-<G{sJ$kY`sAKtD?Jb*FPO_(cPuTff;+($;<E_A${|xBU5b_`9
z{;>bowwM1u1DnBrhL0i8ql3|AHLxf{>$PP3XJ~m3y0q8yMg0%M_WulBYwCq6HXp8<
zH$Oc+@e!}qyH~#9em8l<H=cOgeZuol^W+B3KN`$C7ImRsxQd0(+<p1M^`#%xyJmY|
z*>XF>e#>K?=~30^j_y02dm?ovgT!%(H<izO{Wqdqnq_1ApF#1wSpAJK`@c$C*V|vK
zajswaqUzn8Qt6ipdp}&gw`{Vn>?$_bn;Q;FiA_|TVBO<8{eVQmsbdYc%=quxI{x=v
z@1y%duf(P9JhP7Hzvb~M)}gO+>$>`i(^9L=%#3q`jGtM&+@M#xzw>Lw{fJBVs-Mog
z6>Fq#9PnE?=1|@{9^a$;k|liCEo>_)Iyj}#K~`nrk5%HWsvpJMFFvcCsGTX)^mfZO
z@xR)Ww?;fDWBIlc^$Muf@{!y3n%Bu~=#T&HdZp_2vAkOnXD&1+TZ<O#@HfsDTAsjQ
zB(%PH|AG%kzaIV9m9lH{*;&%NR|hKw@H9z2>5ObRaL0+MfZ?PCLji+k$Dfev{CWG7
zKKz_382ebtW%tyG2}}C7rZ9yz*nXSurQCls*yf~o#~!=)+;66adrX;<yKuw(moc(y
zma}hU-y3{=>t46Z5m(l{eP^@dNK{CnK$nkiak-9=)sv!wP7`-)arJSWFtbtQJ-Tn<
zqZ#Yg?YnA}wSwoELF@4wZ?{cj?!9r$gF$!_Q}Y&vh~M(ax2!EjivjR;&lD@!xtHnl
zky%Ukw>{eVQKa$fT$xwmLPyg%GQ2np6i-dyuDn_F@Zha7j!%Yu&yW67-gkNJ`kX~`
zQ~D2o+qJnnI9qo6Y>g=s3$F7>IN2=xx2BC@U$k`r<27ITuC)_v{waO<0~(TlDYQc8
zjHtVLthWHeI}Z_O`L1;Vd*qZp{8=G8VN<5i2A(yc?c%Y{OdM|<McW@q_qzRi^>yFf
zr?)cyDO}dIJNZ=8Q{;4}-rxHbp8I0bRm;|y<yp72wXS_-KI`q=tw)djNcng3-foff
z6Z`r!b~676?D&4p&)<Y`A?h`3foJi!N%Z9LNA`mL4_}%luFm<*->UPqy(8MK?qb17
zYlGxI<$N8sP=+tJPB!mO`W$wxWcBUcoTd6(PE2}f^z#^t@1kcP7fv$`u;|aK*}dK3
zPSKkJ2e#ukQ19e(H>uOw=J5GP_u-F<r4HwpcrDm$5Gr%GRL6mNr$U(Rw8iWE3o|}v
z3sqM2ZCsI=DO2`Q|K_8fyCM^WmTXyYV6plW?SoD?liM?wFI)bgpDW}0ul}i->aBY3
ze9t^|*j~(IsM9X(7}EDF^q@`iG}X3O3@>%I&h-xRlskOvpWrT!dnRQ~2j^&8=Q<RY
zA543|_q;J`elqfnaH0LGOaE<utnudSYj4r5wL+inRcBjws@<A&l7aP!R%?071Pw0x
ztCl>K+!reRemxHUkk?*csXnu`bouSG#&4O6w`4^;C@}JT=^%=FquOfuBh&7w^!snl
z{u}N!?@HFLvL6pFt90J}Yb2A{^M>8xpYY4$QSY=-Z!<7qyg>Oxqx0&_?dHo)@j6|K
z-q7=mWoG1|)iZ9qWw+qtntY?l>RQ!Y_OR{EZf&+wzrC|-{!X#-SQy}Pv9*I~DbtDG
zIlVjk8Q!rJ{gc|Td*|Nm8Cy;~*uM3n-12(eSG#iO>zA@!ld+#YJ#N9eBl322jxurF
zSNvPH%vF;1&{c`&ip#wGbc#xOu<rhQx92>a<P^btVcwDy<|P*veDK|5xANhOJ@!K4
zVr$EnuhHT*)>GD-ds^gY@k#Bsf%kuOA1=P18Fs5@SLpRyTUlaFTP~jMWKjy4%-h@h
znPF+U{5==PpC63A`icj9l$q6f^;oxxL9E?W=E%4`I_G7?dv(?vl%259(<<-et;4d$
zNx90w-A4}n)lr$n{K$0oDNhL{=4IW*YLe|t&L@7~U}>m0!5*>wTmI9xyBqi1jN|yI
zVEx4R_JpbpH-5^xUHf91wBxV6&!>M%_ZQACUAx9PpzVJCNtx;PyH(u^B&0KM7f9M?
zPhNf|ego!x2aD%b<mNuzv16J=LMQi0l^)SRhm$Jv7?|f=ncDv7t=ap~4{xS@(^a~o
zdUWfd8C~puue{Xc+#_<oMX|hQ=dl8#45mk~cUix@_)2@#jjcVq|LmSv&}M!^ayIWA
z8J412rtJ$?3*5hXr*{5{-A(aZj-)rIH14@^?9Q&o@Ac2^>9b3GrQN;h!__C>rBbiH
zU3%xq>*awv{#}}M_i4a3e=chsFJ%_1<6G1oStL20h}8LVHrj3PmMi-=E#LEL>D9&A
z*_lZ~xjXknF0P+@wd_s*{MiLMdrA+m2i$tsw?F;vsvG@Ve#W`w34h<0_g+8W-t6z%
z?XqQa(%IHT-M@Li@;^iJ?xx2lrY@L$a)SMIrN2*dN)jhds1$u(P+=b&&-F^cbJ_8~
z3;ywLyOf~%SoirVKa~!%3h7xobKcq%6&_Dq{?a%3(dw5ExApPbyqs3H?UC)O1xLQK
zEC{^7I?+0Lo|O#h^gCKZgW&Ke+1G2KpP$1hgKJo5&;19}yPkdYZ~4l;+pM#kZ@Kjr
zgA~!o+2>BOOkymb!2Dvzlcwz8N8dL8?fkGmYHA##=^3YUCNuv2XE13=Sgfogu$%vT
zaTDWug}-x5=WnXm9(+mmfyeu|EUWiCyyr2yHLmh!oRb^p&*B4Y4R+J9w1{BmBr~kn
z|B?Jy|A)t(%*U(EW*uGZ>)@Z2kTY{J^ND+Q$vevqbDnst|H47`c-PnYKiv1IuFiV+
zz*AROWtzUtLn(*lN%P!_Zo4s_JjZVOnf<`o^xw*lTBrDYaOYbnGOftwxWtKj3;o>B
z#0t8{ygO#(%21n+G^PMwPK-s2-F(rp%UN}XoobWVYkfmgdo)wjPThVc-6$zr$x_uE
z`RyM2)*ag?J-U7*yy#%fB<qu+^X8l`*vzWuDR!gaVZh{bZ+M<FZAERtt&{h;x^*u5
z!>5h?L7$`i+0WNAd=k)IeNcqSwwYy4XVLA`sZ#_5QZty>G#_}IT_}2Vf5%ph^sYNm
z$5qP8xK46d3O4C(5|AtVvf}L@M%krvrj^}#`^9Y2(I=ifWmZ*-k59Aa>dp~8z4N&L
z+`Yb1-?p!~l`S=O?%w0mCAz)(lmtCH*X2EJa*yeY&<HY5bqqWx$@aWu{k!+7*WbR|
zYVlPtapi1}<u0y2!#E;V=RVkxR&cz3b{SKT2E+3F2S47}9bX<@vFO+B6ZdVGZYkSU
zRat-NU6<~T{|wPh?ti{Ke_!nP`p`YK=xbXq>{Ieg>6llt?Q&+=WV@HLCnvlKIgrMC
zwNkOq-{Qi@vi-FS?|ADjc00+}x-z~pNH6qh%fY9Udt_?f8E~AdZR2IT_U`=gs5|CW
zEz_T5PE)g7+9~9_FZVwG23B>;gIs$O5++16xaU7O8{};%9`>>J>(i@8;#{vxeEBVK
z$;GD|TBF3R9m*bTlsA?$?z-~fdYkSa{e0WKOV3Pl)NcQDcIy_c-X0+qK{rlihRO4H
zS%p1?%x;AgAG;iVTF6(0?*%xnRcasZ5S(~@g8K?nRT0M1haddzuHXDqPUC9QZxc5T
zv#1;TQzdUtiHWXR{Yjs>e@YeCdi@6F*>CLfcGs$ZtFt@0>$tyt+A+hY{}~q7%(%7J
z@Vooc)EDCORIcj&F&91Gv4nrki{}A5rfFL^I|Vp4@`W@+pF2IBkMHsZ_laHQcKRP>
zzs=39P8E5rQYXLl>YS+A5pVb0bXn5fwj<$?;8XsuDF&>cZr*O-J?nnp+vd32uV&5f
zSa<K8c(20lotrOrFV6paBRo5&d2btot-s7H)epAoHYa|o+~Znao3>rZe%iOHl8v3)
zH%xeNTX272fq%@j^OmdX6n9+7f44sR?Y-D#^B?gVU4An!Xv##NZIj;L{oXSB>9L~l
ztjB4OcVuKl-CJC_?&j^7nEW>Xw{u@_bgSup@u+)(eXB%&&66je9fbIqH{IU5>qmEx
zfbFhZdy>u_&URYR+S9)|VFAwpea9WYE|xz`3(C{CiC)R{o=Z|~`-Y!0Q_d)>-JYb9
zv*OL!<7zv1{BeJz`NvjmjcM-u#1Bj7ZTQHYasHN`q<R`p;gQ^@4W|~!&5krE&xy;r
zb#7{Pd7|FZZ!?8r)#5D<bZ&{cXJT}06}#YD|LJAVrTb$0I2bO(v)@slzWu1ws-Ho7
zK0dm3AZOzDyuyFIhh^VSzVa?VIP%jEnal|hTjzJ@Z@Id8it5hjY>CH#+6^CDBSdPR
zG%%jHzj52fz`&bXR!_c*^_y)}pT6R?RNJ(P$Mc2$&eJ%1(UVcj+lz<GsLpARi0(9t
zvRPGGbsQg-_1CZX88)dR=-rb$=R~;64Gs&PDBL3I@h&w+_=IIrMBV~kUTfEjPcFV&
zv&Z-&_nU8Pb+QZp&N2BKYP7*8O(JAXAKTTO=VgX-l6Iff_LmBqo}aM!q?N;L!Fv`L
z-paDwxEjD<z`$j}w9`^o|LcB9_w@Bq5o=e!m_F_E?Z`WxW>=<pFz73WXzx*JbO`*n
z@<j59xaLFU*QMq+mstNkX>)q@TDyCh^E0I9E)F`*+&IbKi{Zw){Nu*D+uI(`J<_Ut
z<;(X(nVdHcds;rM;!J+SsJ^vi>iHiiix2G|5^)Y)J=)oH7@F2KbukcmrX9LjH}Gti
z*%)(gBa4;Z=JZG08H;=F#JH!f;JCtEuxXR4@SNo0CG#R!`%g=IH+V8NSb4!_3}7_c
zL{I4j^yB9i@N!%Km4EBIJmT(+zl*<5-nvCd?LWiUHJdC0&;L4mu>bq!dBuTeAH}lW
zIuUn%?aPf(;vvF&FKLOT2x;8$GYV*9-l6bio&Di3@pAKRZ^dTHh<)3qeC7Sqz2Ux_
zpT1jg>u~$$qSseMZ!|wYe?lkYmfpgLYxNHWyDmCu{qmR1wD7R9e6C$*^(Vaf&tSbu
zaF_ZW=agye>?#d>laJIXZT|3Va%ri_2Gc8LlkeQVWpl`U=cmPbr*=Mhz~{j(c{aoJ
z@2tw%>mI~wg*5q`U^^+Fcg3!!d>MQ2&RW;XeM=wOMqNG>Zsq>X{@b4EaZ+0^O@H%V
z?8G{S$PI6w8`bPy>a^5RIZ=g)t;{smI83T<VJ_QL+cQ>e+Y?uC?^xR5&QmBI@bIuj
z?Sbf>hgLI5R-SWUc%iWW!@Zf6D{kJt`!Z~L;QM|1+borPuPcbn3YF<;TC%ySFY8$Q
znwvk`oi|;5BVW7rj<;4yQ@CyD1`i%SN680G+VU=2_HNqs@7&IdH76cj(R&{pSgCBd
zVpe2q&Bn><Gds7*tm>(pkz^qCyg7H>n;OwYk@2@qW|wEDitgF4TUp@5Le5h{9M(ma
zFWd@>7}%bIHVh);^jEv)e~Z7dq@q0fe7WqFP4A9RewG@zu_@X};xhBHzsFlm7lyun
zll#@y>e-=B_D0uUskf!vaeI>B%+u%QXsf}r_ulevwaI>$liSbEdVhA}zubKxhU?F&
z`_Fz}F*&dJ_n9xjAz%E34zGO`HFZweCzqT#4QCwhEs9K3zwvY0r;q1PZ+Nb<>glb_
zc}m+aewALS_PNHn{At9}Yd5Z+YBT$Et#;;(JA1ZUTmAcd`ur&^>wNZm8RAl^*JiJN
z71fm4u}wR@^jpFHl%lQ&M#q+GZn8A;R6nKtr*Z+O$$PPEaVfj0YvVJvnf*#z_$_xW
z+oDfr=4YgMd}<R7{_L@PUmcsrIR-2CBj%G%o1UFF_1j#fd*MylEi-;TU7R#Y;sHnb
zstpQ%4)$HUwf0l~^Dp+S=a**MiA=rpD|4+<ldaRCTCd23VV|x)_qgRO_hM;iV*eD4
zqy-!LrNt&@TUp)7G>a;q`~2>mn8PcrmroR!6+Y!>=N^wp?+siF+7A7BxpNysPUfxo
zx8HBg&R0ME@BHrQ+}oR<rAaKk+f(>&yTtQ%&-by(-tSY~_#tibBh57_$^qM>`xRB#
zPseZGd!)ILS;bxYapTTy&0B;HG#}g*`fd06`>(6mW|w_8U-9j7Y_z+!MC%sLg9;PO
zSAQtH^Zn%M58qq9Zr^$-W#5(jEty-^YVn$JthGC<_UEXu&y!vD;h{cdpS+ozFR**A
z$(EYBZgcX|msO=p?|cvYe8)I8&V;L5*ky-wa*?Mo-{FO;UO(!bcIu`2hMueoam(iE
zD(=vm<nv;Z-gOO$1)j`1Z%*Y@ymhds;LCpowtISum%O}ww&qt_Z)SOVZZ+@6ZIdEy
z+}fhJXPVp3(3GBUYO+Uo4=w5Up6%G~_&doX>~ySM?Uzk6<DRCrMJP<YG3m{d(=53Y
z3>*&#uA0Sg=fc;s!4X}j{=5`$UvmG*=IFDs&wfsnEMGXys7qX#;cfY00ZYlmm><W_
zU8!--OkU<+`nOxeXtQ$4-8>^sF#*Oqr=J=%9!p{6yCb%){_sAry_bcZw{5;?zqwS`
zN?+@9#GK<=aje@b4mEA6+~odDVs79!hK-G%L_=54V(VX7VfH<E|Fu$S&o8rM<rr1(
zl;ujFx@hys<DJcM)qiE>7C+B4^azwQlndaxc<%7W>3<sD?ti1b>_5ZH9Mj}OW#&@p
z%_Y{{C;seS9cy<_a&m!nY;wS1<>n@Suk|PkNvO9$3BDeFQ5OS<ef*<(>y~`+%!@a&
zr`2a~?F%$oKI`Md0}3(=*%!;7+wq^F{XX9x?PV6%b-t|E588S~|6yDH7O%2JcYL{e
zmu@I%;B(&}mwicl{)hZO4e#pTXs@h)nRA5^-&hFa{IxG;m3Mrp{4zJ{{#!BQx1W{n
zo!p(xCbN>Ii1ESo`9I<x<~Qg5@m>>ibaC!%ud7MFg=<$OKTW!KFYwrZhS|@{Y@V;P
zDvVng^KbIM)<<jW&gH4>oo4HF=Uc^}84D7OuTEWbnsEZl#?R9Z5V<p8Q5VDWKPY3&
zYk7^GE`ISh|E=z|al_}0&uS;#Rl48v*xKQoQPr<m=RbV^({2;_pCK{gKf{-<YdgPQ
zE6vy^7gN!?_3icR^W>)ocU|&G`g^2FwdQau%dw>g6#pDPRdaam0a@jWaIdYG-sgO&
zwf4Qtdy93-;bgg!4(CrRC9pejYf7^7+|crKwU+05E#<m;-OQDl0ltO$vkUm9Jrmrf
z@u)YcH$7h0$z><&Y;~1fnK1bd(|+O1?c2+yZN7WgdwFJO-DRh36K-!=_xaD}pJ%uZ
z*eqb5R^EDd=Z%M}j_rRGeb)NOhVJU!+Z(dVW)-_AZ}$$Z^r@csefzvmKa0fK?5FU~
zWY3w&@Ji?LteX#Nv)=p84=At5UDkBt_N1lGTe76wRp#q#JorT6@zb-O%QB+uIzi{X
zy$myxE3-MjDSAot$2sX4lE?hxgJbI3p6<Q$=1X<rit`2A=c!(KICq)HrxVLQZv3?1
zSe$Bc-;>7HLtXigVvFt{S{(B4@}$VG^4xb{Ypv&r&Q<GGOpVyEV9J@}o!s*$R{p--
zU~AO%{7ZJPo4&xSDBr)|Z`Z8$&fcimnSATgo>M0lR=L?s2r*2Pv@Clp`X@MF=bplc
z>f_ZmT(efc^Ef2%pW(&i?bcJ~b%i%sl)c}wf<4f+@SD`KB{l)8tE=sA=H)%#)}R!9
zGF{P8G2(HmU6IdfNxhU)d7dGB!LqFkB7uSDrG4{tJWVE8FASY#uyn%2?`;p<+~XYO
z7F=MhcyKv4PgnO**CokE+f%mohK5cO2rzKGqF@)GQ24!em1T*pT>gfiyFz>B-~91g
z>~#sa8}#v0a@LpQcjcx&FRR+OeBmF<i(;4l`7CeFdp~ua#mUIzzB@<i-WfExF_cT(
z-SIhU*0F_;bhUri|5Klr|IKa6uKj<i-1g<Heg5zH!rS@3`{tbfT)+151inMBoi4uL
zDq$*pR_oZKU%dN#&s=-)$$iVa*fnl$oGQr+7kzfR_?6o*y?SZHom-tzg*?|@yiiH<
zw!37wV_K4b@Qz>C)hpM%-v41*oa(07zkR2Jw{EmIT@@uVF(KVZJkfCa_p@8nSvrn!
z-r?=g{~B52a3SVZd4XePVPR&j3TLkFN-Y(wje;}7N+V7tYh-*^S=|@RAnS0c<m&e7
z(#vmI`17`{muM~9qQwz$;usgh8Ky7N{cAmSTjzY*vgwwiO7GKm<vl_*+w|r9f9rVj
zI~7^3x4xYJuH=5Zolujme^9uU)!mcdT((5IXv(B)ob*^w$Mc!i1h>yqEPuvK{Num=
zUdDB+D^)FJD>ENf`)1ranzuA{?zM-f#BwGIembB~bBA}`o_7piTsLg?*Uw$T{nYF8
z@s0yGmEYZYe6jEQ$yep(E7$B^E9`rD?VG%ue<znXF4=vGr*KWd8Xf*QJ!}^Qn)k0@
zyeQGUoqhJTuV>R8`$M)(k8VEG{9Etw+v{d8HXhK^yQLYPq5NGj`GK)G<7^}0CY9>h
zyXX2{cHXyZ(kJeE!KJ&swHBQ;S~~r<z`g^kr_NB6c6y?~Zkc;PmN{cqj#cct)`hi`
z-76>9EIMS``8d*OnJZ`Sx=;!2d999zbCtFT)tdXcZ1T+24PxmOV>s1hTK4G?V>Mgi
zR`((U?fDy;E_;5w-l?bD<sk2~dFPx(dp3F8%f08v7TL!Tu-JlY)nW#&XMbe2?Rwu)
z<1My4wPw21y{Wl+i&@Xk`S!cq_K?JOqZL1u4Ub3`?mwL-({_M;ML6pE#jN8k@7I~y
zv%M()KB;ngcvS74%XSyct=*RPu`{d8n;L%%-`d8Q`$r@ccm61T<T6j=spGO3i|~L0
zM#m!kZ4WazzHu<U6mI``|4;RKs-WX{um9`H!Yr*Z?uohX7=yALtwFCoJHx7U?dksv
z8JXL*eXzDYTzR5X+GgF7{T8fCg_!)qc&wf+*>Sz3+S}s2UTL&MZff`WzDzyAz{jV0
zA9fy$*~Rna=k+V$^5$)(+O=}`qAk?7?`c0GzH7?;gx~hJR6V1f3Qjpa<Fv>$o%c2h
z%I_Jp_L!MRneBhL%*y3g@0GGyYcIR%T#%lUxlSSJRl&r{`Fj-`v=$gQoNwI2d`WBO
z)h$=|d$V29WqrI`DSGDgGif1w2lR?O!orj{BveVQf4J5xSNhN{x9J5Jw|ol=xP9W{
zq>xPtL2eEfC%%XtpUu7dKZEd(N%yY%^mLZqwTm=mcwwfyr);vw1Q{~}4&UAT(sNqm
z4H;f3eDs^O%R9?z>D6U38TRhj9JXs`NLa?QNp_MOj1C#yczZr3ZS|{tRu@XLd(-Z{
z`($W0Ic55G!Oq~qFdZfh9lk#;5*Gg%qUG%k)|6lT<D8w&u&K!--F(;N%57)!)E!MP
zdy2({mPSYxoZlMd)A3<BkG35@Z}!BB@PJFVeI}pZ@gaBHoF29Aj9tCzVI6;No=c4}
zGy71Nc!zn*<vot+h2NyJPrudD_4}l6C+(g6(R{Y#$?%>DYhHzVo`@-^dTg5HTkhUn
zKXcWM<<oc9y>5{%`#F2_d5KS{=a*0W&v4h`+50cOe!jthTlx;UH~nXb*mPyu7f*>U
zmG(EcCmziGeg5Wb>CpCbGnJp+mR;YP8vka#wNLZ+I@P^b-W3TvjeZ;Fv;6nj&j<U~
z80<Csz<AAZb>{YP!RXts#3uXe?%365@hmL8Wez6;yDI17a<82+adRJ@-tB&APQ-EH
z<sI+8axV*NnDHcfYoFV}pPiA4vL__iB`n?|Cb?HUpC=t%nWv}PC!yr@$y1p%B*4g1
zy@BDmscPbn-M+i8)>y0V?e^HtS(sa}OsVldL#dUQQ$DNtLyp+{dWCa%W-;v8^{($%
zNmbXYZMw;N{~7e2#3=TDV@o@n&dw+^-(l^GtRv>%%H`8P={=bK)==`nO@(|j!|i%I
zexLrlUb%lpRoA08drT{BkIgKt&MddIdU++!e#?^Wl_9#55A~fE>Nv=^@h#_$K8XoM
zV&1mKVHelun(Dt<`QBz_X~wNvw<20*=jDrK+<#sgyIcABvpd}SvIUG+%yutcfAf3R
zHs!Z=;S*=K{Cz)r_vzc`&+gC8Js!JU^5AN*?cd7p)!%scV8<ub47E=w{7+BpuauUR
zNJ)`%t-K@0f93k2T`fYH8~-z8*f-~HnZa3cy7JZJP9@%XY|pyYt^H-@6yC`E6&&$n
z)vt=&#m)X!sdLxv=+9bVXnRmYq=YfW@5b}Kb_QwCS!kj%xUPL#vZ#TpFGF#s!{nnf
zD`aD|S0qSA7|pA0V`#q7kmaSpfb~wYp8ZeQbN@3W#+v_U@J>YAiL&$e`JWn9=6{>k
z|7ZA;yR<~~{Jr{<&KLK;5v~8vusBzPc>%t$dt|wF^#}KVV%`Z_@xAmv!_v*+jxqlk
zn*aG~ePjEX)*ZV4v$Bm*{;o-`C*DpeNqn_t`9cvKt>wsHZ?8V>Z{KQt*6RLS@e5Jj
zx_hj-e@@a8TD_&H$U#D8)}#0P6ip_bGui9ymR<kWepB=v&FE=USp+O^3e4m=VzY*S
z+L^;#i_CRA7`}LEpMC!E-KJZ|mM=S;o1AMBUU>VEUZmtB-g40$Wu0k4R=Z9<V+vES
z3!Kg)weswvx#6caUVgrR%jU_ylPqrjXQ)`eLjJ9LmrHZWk`<vn#_Lj~Q@LAWQkbu5
z+Xr8K`_*5|z4Gn51?MN0=4$qNoIF-3WAsE*<KV=ubx$os=dZf^qf1}lrt|Ws%2~-j
z>ocam*|_h{PTtS6rzC!Q@KO5l`m^6%YqO7pi`nU3Dyh)RNseA)GI6T#xx<ArZmRB~
z2P`Ir1=uAW6y;3dmh<n{slOVV8MP((NyIzlYD>eL_d-64&hB$M(lB}A7TzVl(|hb+
zurB=1@ZeegKi73~&yQc9zTHY{+s37tMy}u7uc*vc)2{B!U0-uUE#9<n>!N;+GhEv^
zPaat7oiAFkI%MD02)5bFRL{N%OS|>%SY+z<w97|t=Ot>Tw5b|yt*u?bjAp^&xAP4C
zGb|7TEee~t|EJiVd!LW*Q`jZ`{Z`r1<fVtrrWRJSZuw|>c+1Mvbh|5Q6L=5!+~8VR
z7nbI(GI8hX8rLgdUY~wlk$gE%h}Xz_hPshkcS+clbLzc5_mYo9h}>9lxGmrOsTPCP
z`E3=4|20I(|Km&h&+sJ5?&f3uUyK>`KP+eeXPB6A{ayZ-{S2?o%Yz*YYjc<1@rq-a
zbXQ`PVGN^U=>x_IKi_e@?O*!(`>g3l8q;;32p;EM`fJ-vIhPG@b~Gwa%AY;ou;@jZ
zp6EGl=1Ghjznzz;zrYRJ0e$BFpKkZtHi`ck9CZ2rGq4-if6^@x31GJ$c1rXgvhSH3
z@X<T|Ad9$rsPD&vhEv7=^4*q5TIDbCPw?gWs4Kqej@x(a-tKGf+f^GV`)+YWVANa3
z!_y^B_nd6<tNYJjn>D|E{}anc=YMk@|Ie@_Z0phg47pj~u6>i!n)S(g<<k#S|E&}e
zIwYDnr8|-*VI60;wFA4JLDAcZTbM8Do6I#2*s*oT-pg<G(zn!pyX4EY+vz5|hR3Nn
zD=g)jFLiF2Yxe9*-1+6Vyvqaw{64I<2rX3VJ(A9NAi-LIKkD(@ul9nj*{h>YtKJE6
zo7S86YsogH7c)~+N*%c?9VRSrea67k(&W{{sdRO#=Gr$V>)&d>&|7{r>e!>q2iwKV
z4n*xez_K7ivhT{zsf8OqxP6FfusTsP*X-u$gUfHZJbSpVTSaThnNy)l9@KtX(sb8D
zCA8XB-Eq>rSC3BnUykApHNSI`M<eWGgz$8QBnM~V$#dS>ZSB+BYW`8Kec9o4$4z%`
z-#h7D#)F<M&p01AEcqmQ>{+-%!k-@@)?P&~AMGuQmAE&z$m02y4^x+I|CX<$dp$UJ
z#tA<+7nfCRT#Qf4HWlw+zF=DMtkv#nV)?Qgu_rz{eK((WEa3Hymi|tG=QZ>7&r~Kc
zoDM0w75ent{U07Fm$vGwh0MEt>T*w<Pxt)!&nNlMp2u-e=IeQxJw^9kn$OeP*&aCe
zR=m*54{s+bD+)QLtz#1?^)xG<C+dIiwDdHoeaqEWE{{D~uY9n6P29`1Dak#qLeAgj
zu4~cz`~1!6xn~YPuVMW3mf@B1rIH(^o?AV({C2sb<~!-`8ZFh*$89w!{ZlK{H+)$=
z_3#htuxokt4`r>EE&X=wnu*)~36-2uM_zs_Fk_Yc+45xDqoM<%9ClIfz>NuJJ6&$~
zrn5PZF0D!48nL7?(Yu60c|x-i>oK#93==Orp0&}mb?)(7HorYofBQIbem^FCwkPk9
zS>2~UZx23xX18pIEfdvOL%k3Wld{S($of8Qns%+&4aL2)OoY@vZw-w3WE9iD_+*>)
z#q7kz`xe`+PtQ!ce(7CP_Kjp`<u}%mlE>9q85HJmJ>FXQk6LqSvP>CKHf3eo3SWk4
zW@l>5yCu5aVZsSc#fyclIg^SkpImA7yc~A-?REbxkhwO|TNhR+CM!#5FdJ}R$g|t}
zyzoc=k>DRyz7bis?G8WmwoQB_c5(ie7$d(k5|2A>pJtruU~9H1;oZhZ{%<pRkM$R?
zJ$IJ(UT>M6Qj?0-<+vF)MZGo%uI!C<&dcdB-tnlx+BeyyJ+y=M)5H01#U|}JWDt3c
z^IED?g~f>kTl2~N5%2a`r<GLbn4DN}x$dOaoygf0PD_N??jBla7j{~^A!O6;p5B}5
z@;=92uYahs$2(>BZ`o<fvy<wwL$+ut9XOYwcPLr^{p<`sPQf1G9nurBs(PPyzc1l`
z8?Pl{cTwrAi1%}u<BTCcCoF$=_Sm~Q&Fp$EhZ?L7vS=54=N3sScXgkjap%;MsVrX=
z#FE%^k6&B)YF7H~HSZp8oBbv{yij+~^oe?E5eMx{8(9qae)}s%Zf-tdS<k;XW1q~A
z+_+3Nb)W6I=R^c}5?X&cNH9DoKOm{{WZt9(<tC2Y+(+BDcUdHKGP%oSi3U0xVBlk5
z?g^7eZCK$v&Oc1PSAEv?1N#(rY@g<l-tDuq;z@7UCWFong+532ITzTTiaz_kU*NsT
zUA14IqI<QfBXsqBw=L@my7lXk#lwmq`#F6+lNAHrL>#!G%);BNeAImUKlADC)1pOt
zT+803tf;%3|KzMp;g<G#ZLOUX>s%l7h{;UgJG9|XCd>6W){ne<_XPRc>`Fc5E|V2G
zx5tNpp~%xFY2(-b41#xF#;NYy)|c(=!Mk_f@86f+vMwkt^FFcrYJrcYgu+5yr6=1&
zGcJGSt@&f};p)9<lj2?pM@DTqtKw~KV9<1?{5-$v#&eG<UldOOt;>z?+M4~=+W*7W
zGryKD>$lmyFz?yk*bSOylP7Ibn8K6C%zQ?{ATFBO@>7lTm4y*Ov05fqp4FS_%64-v
zZ~tv^r)Kec;peMecc>Y09DC>>*XdeZ$A5j<^~9?@yV_>2P@Vh!=A+%0C#(rtKUrkv
z@fm;GCQf;{zkO>_`9AIanYwFS??_e6%@wRUKH+qY{nj}3KCw)T8xvO+F!ye1<?8Nf
zsDd4W%1Zb~)|OlE`tw<je15gf&^fo?&V7e##HP0rcRYXAm83rZF{N+8m2#_X%{ddY
zrbo5S7LqQj$a^|dL?UwW$#C^|VumTrO<vXE>NMzAFS)j5KFhY1+^=`lx1U>B_fRSO
zMdIf?iQEA3iqjLPN=Uw9Un<q!QKS9fb-|>Vm)jKADQ!1!`RL-Dq;XJt;vu(-!hdfZ
zur-Xivrp_=PK~Wuuk8F=PxgPfx~(I<DMax0X(^vIpYpZt#lLT46`jp>U&DgkIp{)u
z@IN8#+qL@VckR0N<@Jsuz7mrjaoC;mxO0Y`&2oc8U-92}4pt}e9w(vYUH#j7XG+(t
zcbrSQ|0cOBB+WNgS19>8@%pPCtLB*4=k2ADHIWsbSLXZgx$?G@L1EfW-SCqU_SdEb
zoBh3z&iQHLhP;@Kam|Nz1!r27KJw0$5x$dEzTJO&UJ8Gqvhqe*&;Il{2Zq9)0L=M4
zcasmd6)K<hspzecyrBVF)oObhw5U~7HSx!GuiR{>Xx43gFXg_SecI-`G)iS>=aUn8
z95>b;ubcB_0r#|D@A}KX*>BF;W?Z|w{-(|Dmi#R_zkeIl<?j7Br+lUI)h#!-dT!aV
zmD~M_qVK0$I;T=yA5Zgn!auW8dB@jvaqkaL&o5jb<C-i#zk1!v?V1W2Qr;E53zPhc
zTMf@R&8vD)bLaXc8|ziKe@qiBD^=gJ<;r_gj?QT}qWCS&ZcpG!Pe1ZQ@!JaP6G=>M
z40m>YjGdLGpPp{pdwgnUrO9Q}2ObY5-8m#>8Nqh*-wrYLsmu${=HQ#$o&6&|V!E4D
z)e9r{^7Mz=dqwV<Ovv3mWsSCglgz#|OIq@|d+#)Oitb$Xa@K|`rQ8`NE8itvG2PAU
z5PMX|$s)PqRy&{M;de}T&xu9|oIY2?z#dR~S2lH)@~Ru1ik;7=@*YaFxY%XA;XK!x
zHB06(vdFpeuZdhg+5Wap-C@-w)9b2Z8fRQjytjC<d;7_n2BW>@DMjD*iB7HGRP)w|
z|L%`z--CCaaGsjKwbE$*d-L;bRvQj|xqYl|;ltdtTJ3-~YuiiS%YQV9$Yt^DJ$vaS
z!|Oj@oZsFzJIJQ3eDs&yb3^v+UcU<mrmsv?R(bh*=gdP>b2c!nu%1!MwWjcB_|=*~
z({0=3CN7U~FE3PHW0$g>O=DV``xLh`E1n37_#N-*{qVu1b-I4+h5Y2bd#3wb`g1zs
z(Z$xidw09bJ<P3C*`&ml%Dt8Au?k-SuejLmukk|Bp3D4e4X-Hd_gI^^?|i|8y{nuy
z9aVdJIKM4Kxk|S2SCi-gQ{9?C^IOwy2W;rOd+GacyH_50JQJObT_zoE)7a@29&(ba
z=2$4#?d{>7ado%Uzs2=UJDLA2yEpxaSb1UO^m{L#Zqa-A<Rq_R-!;$JPRpbN#&e9T
zSQ$i7mtefWzY-VY42pHc-|~fi3ae;)<+4{{vzGi?)^)A#J4e&AQ!ln;8tXajI<eqQ
z?GiRs`GP*vpM|sTENZa)&+x-*-}(Oxin{DE8}I&G|Cj%5_22r(H%@PtseQZiyyU@y
z{~0)^P5;kex9j;oj`j6F&Vo8u=K8%~R`hV?md-g_$h&K%N%xEplSw*R-Y2D2NG4wS
zYgE87&v?`Hpv@ba&b{+|w@$s$F=O%Z$=XNWn4ehYz>{;teQ(o)4boF&PrsI~bvx%B
zz2eV_c$S8v9turs))<5~GPJP>I4Cq}>)k$NWxH_Or^mZfwiPS6>VEm;7IWg#^pbR~
z_j|k95<Dyv{w!vY_*O4$k{hD*((HQGlut1_hK^Yu#0oB+R@$lNu!8Hb`l+WW64Db=
zQZDZ)xHb29yW*B@lOo>VGug8{W15M3w%Sg?RX<ysAD_;D93atqv|W1IJn>68>1`2;
zb1H>?UU0i!w5Pzpy@%s*npXEF_t;fTk7a5W3*M@5cHX#a!;Y<6CaG_5jV_JuEaTlM
z;cS$5>z%T-`3Btvwh9S`{(nNR<$rkpXLu;}=|97z{|tM-?au%C{8|0#&o%Gne>s2u
z-RHo&Kd$?3zLs+7Nz<Ei)4B5^1Iyl}Z4IdVRyg~{?t1QDJYS|xH*YuT?hVKax^e7!
z;??g@9&CEdvaZ1YRJ%%1QpeX`vxeed^8Ky<nwOm}Ul!Y&^zPn0myIoMJpXd?9zIs{
zZRBW6V&1hua8A!u-W4|KOKbv83uSFSY~pEBba3(AQ+<64r?f?M*a+V5YiAJ*sz0Q-
zu)AWRx2KZ8?Sr|(M+>z)MGD#lTS^m7IZSeh5b!ACRCu&ap-DQrV(r^UeG*Cz6OT)^
zh6ETeFgGwf7GZ2hPb=~tW@aK?mwDaMl_B_YX|!zI-Q^p0_LaCBo)B;AJixMe<x`oI
z)CeZ)#&GS~A7cbwUVDDj;HcESOwZ@ON-OwHSG5@(@_5>Itvpmkf5r-bhU=aV$oIBO
z7H5bRziJMw+^T3%THCoYMkO*P`McLc!{f?%{Fdi@vjSZi(6b0Kzxbcre})OqyY1g-
z%m14gb**(>>*5=)j9-~mh4$|K@_Wzg8Mzl#CKukhJ%eY?1kUrpk*Mmgn=go~m>jbG
z!<}$Dr3rSM7teKi6tU(ZFQ+3Li)9dFzO`PAg|**7IX4DtZd-N7&D(cfT(jk`8HbAR
zce8*)U2E2HJ$=l~V&Jq>dG3<3mG&F9)W4~J)Bk3*{G0PXKmE3<w689|bL{@!^L~4-
z^VvkMyPp{lbNjAiZej8A7v>x`4IhuIUcJ0zzovE9REFd-2N{9N)$M`Tb@KEhzjo>+
zTsG~twG4``XpUKXaQnT>Mk^!(3(6{!Y;vTxKWnh|$kBQG@BEV}NAa7B3>-HZ><dZH
z3oQH|{v?iFUgL}Cw0UBe-8SXNUAyEVbnlXOblSGqZD;c?i<G=s!nwhK?d~4Aif3Q`
zrXP`-wnJp^*S&MEEv!y_wsEt7+s4XQ{R}E+E~kmASfu`Eh$wr@Ec#__c;JWghwC|B
z337hb;G3dc9kgoclI%hid8_sEMjWDr(~Q@78%Q@;A71iu*`r4fUVfWbd-%xblTX&Y
zj56X$?KAS4z%}`@Oj5^}xn{CKxk0*ipyRMowr6v7##TI>FRA=Aj`NMJcKfxjwZ)!0
zuIireNY4CH&*!|dvOcXd>RXC&r$qCljfO5ftDDUAuKATm?73cg|A)7}&`rI6$5U6{
zx-oy&Rb4KR4aPIMH_SNw``InwCYNN;?)WWjhtA!9^UrmOVC^hr7HMVfr*36W#pO%u
zTptvE>URu-u0+#5oS2^ftzPL8$G)?IO}rCZKP|Q{>h9mQU+IIzPxl3@KD~&txu5vC
zWVNLI=8xZWuf3={+mn3y@snd$U-s{^)$YEaZ{xWt`bVDjd_fQS$cyI|7V3l*w6!c~
zW|CRSuzl`yJsH{M3H{0<?`q;7S--Wq_3f1AHIF~`*{dzKnr*yYxvA4roVVa$i}ES?
zS0@s<pKjjHAp30bk{8CH^``UYFWY-ZU&^t(m`mL4{_hRz4lBG*Y~T+*uGU#HmpyXB
zZ<||nvmvWZKP-VPHf=J0r^oqv(#_|lCx5g(4&1+MZ~pemvRU;VCa3*3ReA-v8r|~V
zUw%(0f4bz!*wwwW`yMV_m|fNTY<GHYVc|YW`)%dxj!J&gU)-hV@J}Sk_VeV)XBkTH
zcYwFVWm@Gen!NPe{LGTci&ReAXgzXu(`npf$#rA`zmumZ)%(XMP3D^A2FV7++Fkt0
z5u6g9%QZ8w@?pFr^Rqn0cePn~W@FdsQMX&%EzNCfbk5qE+e243`P_+w9=GmEo`?F_
zJk>w07CrmNu6NOo;)h!+m&}-Jba%T&fP-O^_)~@i=EnOBDU&Bvc`=~1Elly89K5Fd
z!@fzM?s{!FFEZWo-iO%Jf<7C{KAqa|Y5NAA-)8TXbtgxQ1hCqg`!suP&(M9cyChxD
z_v)SPymJ^2dz^82ysYs0m8<nauYxn~iC+EcUD~^R)23OEOeY8}oyg5l;CRe^#agfD
zf6D(esC+)M{~On?{|py>9b{SEZ3ON{pUy87DR$HnnPe$qv}<A$hmC-{#7d0?JjM@o
zHEu7_x-}&+cJ4ggpl6n<NepNDHnB};SjAXWz`)Ghb)!ji+x9LNBavPv%}H)$3Oq$;
zJd@vfs_*qg6zzo1o0n=2yBu~`PdZ?WfbH&BmA2Gd7gn$?VYkp=*3`X_C$}{w>lV+p
zZ@*4lF}dEbWF_nSIjvp|Q4X8ZC62hxVE)gb^QrE=Ozrt*Q~QmtIz=YcFOG@s)p39N
zu8-qg>unC_NgV}YqHc`-H<Q)59HPbIr1s2v?6Yg{mfdsamb@~TzZDd{XO-B=hwiDJ
zE(z@s-&*dt^LSWtG2Xy`243jp_{+)LFH3z7x|}dS(ADh3_N>#^0()GJvpG(aP$-^w
z;B4ZJ%&Mu|yF`;W&9gPL-ucdBM|EZHloKjy-enAan~goE@qc3Yv_d84oK!`2%=Ql}
zFa2lOtTL_E{m{2r#zwwkw>=koPMsCALDkscnZffXd3Ns}@H<#-o3;IA!mZW?d&*P1
zi;aHvoNBzmdd`#U)R8hCe&=xQ?%f}r-oBH4T`=PK^Lwv%<(~53Vw-eNI3r^6oQFQe
z0?X&^kT<toic#x|&R_Ma{$_pB#D{nDZSRy_I=x%Yf96!TW1KlBl70AQf0q-v)*8Nl
z<Mu0GUeD$}@#l2(ig}Wg3#BJE@)%i4vV2*<^}TBT&9A-IzJ2m$+564he{TC3aBRQH
zT)X_ak9>EYe{X!zH~6BBH{bS^Sz(2@PYP}-Vm4&2>P&5!pZqNP^l^K=!*eFBo}Rg^
zqU*l<mAoah&wk{+KQ(E3baK3w#O>3O-_nzdKHYiq`uBN#dyN%u_sCZ+h{>29mA8In
z7Uwdh8*ArYzj^5I#8cW0r={jBJMrYC%6yIWAD=a-T;3D8CMM%o*w)%bH*UY2)qZo^
z7OC#jMzsqkDxZ=F^*^ih?&l9lWebKE@&fm~b*`ILh2JXau8iYcCzSkrT5p#}a)aW%
zRR@|svsp)HZ9lnx{)Io{c2k%92nzRpxok@p$5(F7ubOGC(Wm3*DrfRkFPa+KW*4xq
ztLczUPL%7K7q1JK+|0aJKEJ%Mm~Y9uc`i<waly~jJ}Rc_9nfl$=Kj3w*$u{x%d_h9
z_g!7PXTJV#ySKU9^Ulwlku<%`@c6Gg$@6#5`yo+YXVG^2;4J@+Wg92-I^E5)X_+9e
zTX*ie5bqJ5i8A?pY|n1-UGQe&XL}ib>)rnPwJ)S{Z{NAM__l9puFRSwu?y-fO%C_g
zA3R=sUtRz3J>hHju6s`U9k}n}vP)Z5nA}j>^4nzgXAxiHNiY7!h8o^Jsl&<dAgi`<
zO;*^hvwhQ-zPvWQ_-^$1g0rO+7qoPIg&ySgo>Vzw&DXZFU*O-X%Dj>l_S<vyj?I)Y
z^nJ!QDYPp_rIop|T2l7hnH9a~u5oZ4zx+qKVpref<?*JUU(PaJdUx*DH|ED~c_t@k
zU1<9hDg88blJSih<pSnhlWg^J*<{(@b}B~emi+vF=~Qa<)M=6lP2ox2n<wiCZgV)u
z&fvBxgE^>PB=X>j*Vo0ZLSF3RoBwV8mMsaMCON5}#Y`;}i*v6`kZEu~B|7Wyt9uHY
zH}Bf9@53MdCr8pkFTam^a6+W_1+z=<Gf|aA4bGwpn^J`RV=m}#jqVq9<vP~6@<m|8
z?bFJMHFxf&$fPvbT(LY}XWSg}<#vThtXplti{c;kK3gt7&vkq!r9SEHX6ZHSk}9Rb
zTs=3PD^K$?&&y(Xi}U`?c9gZ4S;t%6<e8jjdr>An@n?D1uG&4uY7feG9b4Gu&dwr7
zXi?1H=YOWyO8+|;{-5EO*`-}vs7EGF!7&$1;0W756#3LwajF+evRk)bHQj4=tjyuH
z?A1#yM~mDXlK6}`&Tm}6%lV+~)xGHIj>WS$1C~rYv2f~@9s$P(O%_L!f9O@N+r$0v
zb$4gVtjdzp>61JqHd{+fndJFoQsr59%(IXq>bO5HZ_TaYe)zh&U+Be!^I|h|Cb_Hr
z@j7uxl|>+0q4}5w^B!W3&miuQjZsxdhmv$b=8op0tw!Cdv*2>ny;F}4X*)ATw``fj
z8oQdCRl&`jkt4)HMt1cJZT-XdKgoPd|J$1UpW%{r)YHpHtnSQ{yZAM7tK=ooi@NLI
zt8VGL`Da^-uFCd6OTI+KqD4H0w>4ggHCP|HRC42@pviAn7mtY{P7Ab-++M`o$7Fb_
z|DjD!NN-}=zqHpL(r2ftPd04c=W=`N`PICg%~x{c9b;n8?Ou8O5pU|`@SdZ~v&F<R
zmvb!s&k$OqJ9U=x_m4AGG<)|OZS(G*np`h%|Ky|JwsyL1zu)|td-v`v&!@MR7<MF2
zFLqcmv!~<Zs?8oeDbo}fPG~T1>G!;xcvbDH(&e|p0W;0K%Qmc-dc9Bb<0QM#2lEbJ
z+Vrl(+H%@?*UL{fZrHGSn)b;xxeK`dGw3Xe=z7@D>oaj%QSa_&3@e}Q+|NDN$)C4E
z-K9Bv_g3#-j(fIe0uQDBWZe;Q?8i+rMoanf@)P^b@7<MKTf5@+E30=q6IUO&pY-AC
z(vQ^{A;&9D<lS|P*ru2x(`wzJ-7aC>V9i-$onHJ%a%=X91v~GGZaOS-q3u&j>$B8}
zp68^$A7NrpmaTmBWR~A-vz2@+_2y^%YSG-Jy{*+}#hwrAdm2BRGkmw(S_D~}t+8nF
zJhNH%A|_=jlsm1~N%U4!e$RWLr*BV_t>Xf&j|Z3Cx)T+B6m%3=-pOpKRjXAL79=#U
zaHv_}@c7;DkRts3qH}M)*7`gDC|;zy^v_Ixw!8PWZ3-uCIxf4j<L{kBmL7(8hPw-&
z?c$#Ow(h{|ZJpI>3(FHzvsWGyy6Nn7%(G|O#Z}EMsm)2xtJlx)OjihCcdTFX!rW@<
z+;<C?zufeS@lce1A(zR*=_L)yf^&L|6G{%+ZB>2Ny7-k?(z)+m8+UFM+VV(p?Zpco
zN2b*-NiNhmGH-d|*L8Kbqp#%Um2@vG?6&ofo+q)GV~KRgw)u%+$Iq<0u;yTUCIicg
zlTW_#y2tGOQFJ))n#zva_(S1QJxg^T^|)L-&VQ;o^Wn8L{yCpdRn{`FFSBjy&lkG6
zcWF=IT^F4&VJSwPtaUDm^_@;XTl5{w3wy4VPsp(9KA&AHHoN5WuBfv-uliC_f{ok`
zeAQZVLgWj}hOg`D{{6~TkGq;LC%rf7vB!l4W)qjBoHm*4sZrQ5dG*#klGX*gJsI6z
zJ^gZ!b$jEVI)&`*yEg5xntw}AXX!TmvTYlDpXW^A5w=PFv#&w)akid=t&^|1@9dEF
zkm>%QJ7aH(-ga6R5?2v^%;D$khU)oI6LWMfpT3>R1m2@(VCM0AyTzB}y`QS)o_&>d
zRD?0^*rD@2oBPfky2R}r@p+Skvf!d8lL{6$PV)SdbyOsPk@Ta;{#pNLm{j>F{x@rE
z{flMmnl}CMUUqiPkMQtIZ*Q5-`*te3;+B(BTZtCu0d+~cwgyv;RaIe2`PMJJegD8F
zC7+pwrx+?`FIH~wyB@|GQKry$wFq%;KdAry9QC+BY`e%jzUG?c2IcDMI)OTiHQTz4
zW(HO~oovbcEY9PdZI;E>yK?#4E2Gx-%)j~bci!z5`?O=l&x$`KXO|woYd5ujQB>T`
z*!uLC7yD8Qv&73+uGlki#uZ<kb^9VtPCj$wHeaZl%^5=p-n0ALww~_i>ec^k<gxtn
z9{uvg+BO$+ch7QZ4PA6tNZ4Rr3P)Y(<M+7?@9npj)c@kT@t@)N{Tua<AKE{D{IBBc
ze}>3^=i{>`yt<Wje`#};SkuS56Lrs=erBx2o*-_iqOC1>!@!oesOo!b>imB~^>6+f
zF+Ts1X>!&+!R0XjmS?IjH`Zm;iZB0Ou`EaL{U85F-qo>2Myl6Kex_VuUT|aE$6G!@
z4h1(3D4M<dId_vl%@O7u^tdLsEQY9KAa-oNUQ+9H=3ZphHgmH@p$%tw4_R?aG_2eq
zlczd`@ya{7t$y|5FAVnei3e|)X<FU3ee)#EixY2#b}GDkk{2*1{aLB(>*@8pSyo%;
z{+a%5*3{E??__TD6kD%4Grfs>y_w@CR>3#7-c=@@J#ovxJi~WMR$;}A_@ynA9ctXR
zS9&V5IFww>OF3-tz@t*WnqdOJB*R<K&J`Hewhz7XpJCI#qsoVO-K*a5cIosooB76|
z{mnNg9Gf9){?0~oE!X<`<ouN{ubY8yC=IkRR(oWw%p{RgWW@Q>LG;~M`^~SV%4W;h
z<y^1J>HnPjX<=_&rd7>->m##^=if_TG;8^yifOX>L08s1-abh=<q2C7-&dj2oOZ|0
zY@gm&7u#;B8m@QQ=cDMp{uOsU&1XN7-mi63Z`-kbA%@$hZGLm^*wd#wZ(jdCFRm^y
z@OFjWXNMgZ^|suN54s}k<GL~0dj00s-^x?M8K;?A`c6DK$<r<{{_$A`&*c@HBX(T;
zvNr3t>&ESuP5C$HW|)dkOZn}r<UYk<)%;nmcRznHaw}lGV5hieTI9N%FYC9w6#KMC
zI7a38d0lCd3C9_n_l7pIKjSIeb~S%;z5T);dbQe~AC|0}e%UuuMDUfE@T;J+T-&GZ
zw{p8A@!eHxHBZe#XHnLciW^(HBQIWi?78Xkp7(a|9zB!wyld0Za%s=<Gro_UPQ^Ba
zvY3fK_dUCTIoa>Zzx%bTqbu#=zt!Hlop*P>vB6QjH_829cO17bxBX!7?oT0af3wMa
zLEmIWsn%V0DmfMGqW;c(ry|`Usbq0qhWG3i*#*;B<ajTw-+H(1KST5dliS;O?seZb
z>(wpGh$FfS{5V+}_r^E(J>TaS-@ZqE?cQ~hRlhB+UF^FwGaz$=Yv#91^Jf~f(p4}1
z+O;Zq`=kgVxdtoW<cKS4OJ~dKdtY9w_k7p(c@Jm3`nVt@VwUQG+tQOfXOzkE22Vd?
zpK&Swt^Su4s{5n2UY0wU_BnB$r?NYPp+l6R%)&WuPOUmowjpLtt^L96-78*Nm41%5
zo4GhD_U7%l!!@}}rkR<o<;Yi^xGywP*|xL2khx%`@}*}N5--%<m?XOCy8rxIon_%W
zBNL}_sFtbhwlq2@ox&qfz>>AB!9@9E+|s|(tJj@ha!ao{XSy-xqkZY~GLr6ZbLlxE
z(9R)QU)j5c&sTibv!#sHzVU~zO+Kf4JD};_sh8{a9BuOGeqiEJb0JpBfbq^@*2&E=
zckeg#UYk}jm;X>eMOEsS9oy!8uCa?fWx8b}$Dbo=k>Y16?i(qb=r3e!5WQsk=6R%?
z@|7>A_bU5e+H!j9+;z9q)A%mzdn&MJCf5eD;^tEi<O&$CINF$peT<1dEpx%E@$n=x
zo^?x71l(B!&t>zYuJ*s$&w1lc<~-gDZ}gQvy<1!IyCTi^z}wPZXP!Pj4qL7LsH;NI
zmfP-&x$@8a$Eo8-<8t3kU+lUfb7f)DM~)|2+&0w*k1SU)QDEY;`ubQt@cJ1!gAe|<
z>@#MROuhU);??%TxGiyIHaGmw7Tml$^{JZ037eY5OBrg_mz=CM>rK{M$y1QUpD!Kj
zDtT(jQn#-%^O#dg?SsQXH4!D4a4p8y)CE1)e&x$qQ>@mmzT>b-OZCXNCl(Cvy23j9
zSw8OMl)Lfr(z@{3FQh8^kC>g!Umowg(tYhKqx*NxW}9SP>-nxKnpz;bSnq>HFQ;_h
zpA_Q&_9cOF;kmi1&MwZp71}y)Dcjm*KfFF2oV)f(W6+zmn-(oO!(@0@I&o^p&mum{
zm5Q4#FWdjoMJjB1ZF0h`x;d}&w&g6G;$ILiwkCAX<Tic*j!XQ;8EOt^7+;Bmn?G3L
zBV}@NZA;k%?zT@ZVVk1dmEOi|iuUk!FwYCxe<bAOpHlzhVe2cuaqQouu)qKNjNiV^
z@ouU=%hV^xiWt}2n0X@N&;}JwV+YyR;8-uod9SQPCq0VxZrMK1gh3=NB<E=d3(Lfa
z2lI^B{6(LCBl1A!BfFdqS3gSKd`YFN@{jw{yOK(qQ-xjRuFgE%dbr`VwHfCvZ{eON
z4OJ|cOgtnNCnd#(XNj^f9T5B3A;IwE`vD7<2NG}Iul>p)l^tnw;##DldZt9h-Nl9H
z7i;s^6dtX-|3~@Ol*}imb5$l}if=Qs%35T2GymI<Wl4K#UMNI|=oC3epFAIysax{9
zmiwUj^=-S#ztzl=+g`q6s@O7_Bb!g|S)ic(ZcCbr&3Y}ypq&By9*Z{pv0Qd`$&b2o
zmtHQeKG5d9Q(0xrbUyDhj};0o8E-RSILE-;bp>+R(9Zu1vi})Q+I-ai+q7=~mtgR^
z@V@^HPv%uj|93Dv{+A}`q)8l|y2k$u9JOCI9I@Z<PUT{%hmzxyof{`?aB-FYbh2A(
z1v9%A!;_FIom{i!k0mB$DwJQj8WwSAnp4i&eTh4u$9Eil@!dT6;4i(ox>qLOKAie+
zb;sdVOlx&t-Z5H`!s-$@@08UfPlhkv{(LtNu8n)O*_HL^mFsEG?zy+*Z#yICbZSkJ
zn@glhvgPr-JYIF*=<oYu?JmSwuiks0wdPo=Q<rzLN^4p`HJkFnb@m?DOK+bSI`m2P
z#)kR9dp71<t_{1MqLv!W!TWs6l0!RrCpIfGFf0kbXydy2cE+vPf9uz}YwZ8<<kp%?
zC(~?phjk_>PE|f^pp>R(E_<}jUq^Ne;|<S;YuR%3Wc6Z&eQWK+?~5*uTG%N)FVwK1
zF6{~5^K0vT6VnU7_1j(Ith+4GRQs{*bF%b?-uZj>TNhOP>|eRwI$r4Y3e#F6?cF=p
z>*|>-jWqRmn>x*G=gv=eV{>Pyoo)1B&;Ik|3Dc4cS@)QYJNBkuQ`y<<b4};VQ_tK-
zyhYpD?pOPqT9E2`@aEHwj~nvt&tiD5v5ucOf0o0K<7S*M*1Gs$+P1>XFvDAGf*dw1
z-Nhn!!f_(gW9f(nj~9h!Ju9<~RX%5)&CFln(J?=B-knostA&_ZQ*_v#AGl)>F+ZT9
zmWk@?Jnu!m+?Ch9I5W)e;tZ1~ZTGHaFWNnI+fNP01JXCl?itQ~!nb3k(uRxg-dxjI
ztCP01OH(IQ$Rx$%laPnQ3vmsR_5PDt3S;U!@=T?FufF!Xe0t{cAI&~neydMesuHZb
zWcT;lhiX3y=S;n|<K~WcQc_~uSKQ0qR(4%n`r+i?=~Zt6=PUiPSoDPdp_}r3OG}#z
zY>!?{xczEc_%ylLMbWosyKnC^5b~(d*dcMyO<wbfMkRy1o#U#E39rK5=Gg2|*s;Si
zzsb$GWEJ~~;|qBN1-G-ENu18C(8p&l_@k?y-*Yu@boz}N&Ga=kPPdG|b+>umY?djM
zu1qjm!M^O8kL)!Y&%bLGcU*i|y7T73-51v#Jrdy38kK!nT4`k%ld0kA6}e|8ww23(
zis2a9XS>(^XE+pDG3{jeH)~zLYe)WETbU8$+BoM#Y|F9u`(_vB2q{ab7nmzt`6_*0
z{N4-sTl+!`Y8ScA(wKhEvX5!yXGQ<JvwQDavhl@qwlb87gqwf(W!C-heB0G$lafkK
zm)&{j$Z(7!ehOm)AA1esBtOrW<ZNT<(pbP_`Gs@Aj%n{*uB2RkKK1lTmag=z6FX0;
zDIHjOGVM&R+_T*C`<I5d)k{0IS$?_Ce|OhzMyo90==Rv-nV-%W<ysd`+`IF<>7_si
zng0xE%m3wbKDPg5*kb=j=Inol6I(BktET4TN2B}4r0S2Je7@oH+pV=xmn?&Lg`Q=`
z99z9%-Gh#^|CVf&F0lBre&ve={PS%z*Ze7sF4W2liobnietN{#ip8y)nEu>1c2|}u
z+%bvIugG0){zJ>JtLKYm1^s9`b?JP7mED|_u4~0w&HG+ko{;u?dpJXfjs48kTbL)9
zaBjUTcaOXC`PH1Hw%c+w{RLecQ*RmWnEdI_i__;nYRWn;dL4W5P00&W>9b+S?j5V$
z=X>Tl$HbF6@?zKc@j0j@uUKc7&yyAQ%XZJU0{{F<{to?8&3y;I)o<~dwDpv-=5)hp
znmUp9DjeMJF@(&&QPnqp$;-{r(b@KS?z=P9w(Q)Ty+vHO^31wTiw-yoaOXai3=P>d
zEsNoeK7pI7R=&J7ch0PJYjd9*%r>cNx}A52IrikYh^2RXcs4lq6qOyH*UUWq$`{%6
z-&X%l+3K-R4*T#&%F~Qz;_b*&O$A3*Z`#oQ{c+xbw=Mb8EzX{vs~p@MwexE7hDlEq
zue*M76q(qm-tqEuj#pm7g7)MIXZC0++b}Wis0m#BpW%>m=EAjK_-ji=E*<OClK<)_
zIHl)#S^3BQpQ-A;%a-`o`}W=U$-e9D+f?f+a$D){YMnPuABANk*&-4e&$%<3p8Zkp
zb9HTLuiB^QUh^bw|4u%~tK)LJcF|k)?mC(0S}irRH+Y<vxfV5`GistZPm5c!#$G&g
zd)4~(l<gZc#UASEt`j*DVE=Bpr-$!@Wq%a8cRxL6+&I}mTs-#TeZT&|*s!B(Qtv;#
z)7@gY@4%TGIS(EvPkte~mp7vA-?_(c{<+=}`nycoMp}jU*)g-H*X1kgN}m*d<`0aC
zo!+)yeaB_J^|^Y_)nl!CkAIso?Y&m(ri#FuNr4iI*K8M>3mz8Yb2^#6EbEr(+ht4t
zPPKhLRd20ybhNj?<lM85&PxAzw|aX@&7a$isgKt&ShZa*DgABtHtb04@>8FT3+C_r
zTwYmS`E&c*+#RpCJhm`Ry7uqf@AJQ9?}*E}tYx|9)A(nn_<QB##XLRDC)QgxAN)1z
zM|eP!ubKT@_7Az+CNt_w=Gz7psyJ>waOYym^UTMS`>c8Gy|U#+<NbNJ6l6a4*}QeT
z;M-6(^&P5AeGNLDw`D$Fc)(l)Y9lY6$C0=8>GmC6mJ6nGdCGK2#(ErNk>gPA37HbW
z7<iV&Ttld0@l@v3t))E7+HAq+3l0cW3-Efn62I(^v44Hm^;yZ86CxrV%S-Faawn$m
zG*Eh^sj3s9Ja3|4Px-3<3@9bpmWuX&&hvypm#fVG<ysoc%214^V(a<4KZ@h`d^|Vz
z(M}Uy{<qi6Cf!#5<G1{I;m_!QwjV#WO-W|AORH}QUqEh|NKV-r&Yr&F-u`~QzQrOf
zyve`K&Y!%pRPea`4c}vN0-`c=(sd{Cw4@8JRFIyJ>fPGS$K<~-fiAQxHvi9{bX~pl
zqnK>@p<S<T_-2Z{Ul^Mu)}OqBGrcj8&E_c=k5RKy0@Iz<f9`9XJKpifvF5Vv+TJzY
zx!G$nzm<z;7H++IFS}ehjV;OWl*oi5la7eop0<G3AK!+xY`uJe_$)c43t`fc3YX&}
zc5W43dfaG6!Y+5u<O2tc+;<kl2+YiFXLx+)k8iI3;ix^g3@_K+Fsb~iZOr@Y%m*db
z^YdmK$}I3$qJEAuEa(8w1isB^`|$cvtv|ov`h4GOx_c~i6NJ=`R;(*+oAl1<l<Yjw
z8F}+W?>H8nsxMdIp2Ahl#qj(e>ef26{e+-Xx~Q)r>sa&ZxUAfj2kTQ=mtJkXv8}Y}
z$+_Mci>DYQbyRt=8Q$8ajXufKV8w;2Kl}Kd;x*MD?W^ij?nm5u?6vW;-SxEZ()+8+
zdvd25-d|Td@v_V}^c5X1m@JY%hMp2{J`yKCm3fnxuTmJ})UFMWUav@Sl<iPjf_h%_
zy86S{rFvVhPOja3X3G^D$CbBgC!Y$KxMJG7*x&m;POgbK=kzuw=Z?9=`R>x{c&?XH
z3ujp_ujh=-+N?9NcheoWX=m1yJ!qUM->Oh^?=XX`I{K-@Ds@_|4?SyKAAYHvpW=1P
zWx?)T-PZpMUQgbJS;#ipuCir%_q8T^ZN_!0>)+;>nN6FdSn)VAsZy%wkh28CMy{5c
z)t}xzwoJQlEq|S^X*|C(%WUP{SL7s*T_|6$b)JLe%g;*lY;BDlM9$P{MYn9v7p$o9
zdvR{!T&37Es~nQpZ*6kWSupQ*`&!R$_7e3M%0YV}P454h8uOo_ZJnvC^AS6VtLxwI
zyZCqU!{4(v3U-E{NUt_a3EFWcSwSNqBH`(6Ww}NNnLEGIyVik<xvPKdO@tPDDo=Kq
z3Z7=&b&#d7Yx%N@^dnL3vvN!KYA%`1_-yCpck5IVj9c%kJ~q2JO|iHkvO`kcwpE1j
z_^Udpk7nzi)-FF1X81Gm_BZe7(>c#2&rhw|y{r73<?-O4%w7ClCacSu?jMoLUTj&E
zw<hnMv;}k9q>mjkCFiVu&3difd}XU|o%P?mXV=5}EY^JOwza!<%{#Q>qgB*uNj~Qd
z!Ir69CyM7xV_{{ugBs81M|bc1{Wd>(i%_P(o%pyjyKY=QdWJJc@1Ajr-X`<b_JaKB
zstz}-@_w#5+O~3iR{oOAx7FXImv{Y3pPXWBEnVI5s8@}{t7uc2YtPC%9AQ3!4pL(0
zA9<hMpZd|hUHz_*pUqk=w=?;3`;T6~o4dC8!h^?4-B(uBAKA5a*X?_+qf92S^ITjv
zy`Wp2CAVOEf|Y=W#?9b6QqR7~<_B*6aIH5tzi^Ypm-T!(v0a7F??^0t(*MYn`L?8l
z&9$T7)~>meeJOL>uIV>J|2XKlG_e#-s88#>q33?@{xqKA=AO2|Ee$!f{m10L$b!m5
zU-SPAsv!mLk5;d)Sf~5P_2JJ2Q<;yeRJp7H4TZU0<4~S+EpGDaZ2O!`OLtw_caitn
z>dGZEd^nm<H^jW1+97FdxLs0VRbq!=lX;j;o$^PKe{z$<q_&;k@FVDaL`CbC^ta+X
zlQ*+jJTm)qAT@yBcg+mz25WxQBkxZ)M_yUC{?Uf*ANRMU?U~AaJYTliq;IKtlSu57
zru}BMmM<gA%RViMGj5B%`A%W~N7mjc7d-^{)lxTmiiifdB~MvaJVDe$anmthx7$J6
zHg3QCcFE=R%TGSa6fe2xbIIRW*7^J-MS%d3<G&A`-TN;hT5G2&gB6GJ$Iz>L!o@%*
zpo0hhY?Z>ogN!(oUW11J<d03;rxnliqjjC>TqzH>nMElcUuFi*tXXz~C(naj_Cw)|
z?Bc`ryY_vQom7~gyK4KC`FB4jwv|6$d1kW5oiBGA8yMJ$9qrh{+Sbpr;bynD$b=*F
zLX=F{Pd7IDuKs)D=9Qj;rELbjsV_Eexi!Bh$#Y5L{ov5ZWUffgP1}CL4(GY9{&2VS
z%{PA-^Yd4q&pG>W<=uB;8n*&kZcgZ&dc(l0XVdmm9KVlOFnsaAyWmyhlgV96-T9}s
zZ1oV#&Apwqpf`4+OXds7mIRGgPW@h=ch499(f8YL+uluGrIYOWZ@oIF>$|4xUe2N*
z*TXRei5#EWe{GUr`kC|gSUYjOV+PsQZLN!M9@r4|GR(kfx1mhfi&bWp6D^p3#LjGA
zEaa}X#<X?z&)I7g^36i#`5fc>DV%rRZjG55f8f?y)`Itsq<`APr!POc;(qP?;N817
zd)n*{X*1+0dY2(G*>IwqX;>y>&!i&^lB~hR9<MWj-vR#|`?|3Bwym05=X1T3T6*Z%
z=6g4t3zd#>1e|N^kW_iBe&rfsom%jwX5Z{;?QV{>Je+w#mpnwv*64^dO3JV(20SPz
zTfbn%(+gWF_Z@!rGR&wx{qdXVwHN-*mN-8B_{rYYm*q>U!sou+wQqU$gXqef_fNL@
z3LgrKn&dL^*y*BYnnjb|1(nr3bUzXB=j?f(yx6Q;XRMB`Eiu*qVy&BZ>X5d+qS+?D
zZL5CYm+rIqmU=M8tXw=sgW;9l7G1gDfz5$?F0IMaUvT@$owIrUD%E~ZZyiZVnB-<9
zwZ1a(;a+EFp?kM7!>t_d*2rZ%u3&q!+jsJ(&pT&quRZd7*0Z-;@A~-*WSsf6CrQ^m
zV*ln^i=*<tRwov%x;TG-&vD6`cRyzq1k|iOd$e%Hts0%SV~>8nHT!;#Yv)eEpI+Vh
zPaU}yEwf9WI^&&Aw9bNc2R~h4Uj-UjE8iY#cfsM?>#UC*;ouWvdlD8v4vf809Fg(s
zinv_u(%vt|Nu1x0O<FTAc$?tnId5w3$nU!OqB!R6zx6ARugWqnynkXsM7CH|)=iGb
zhF+6vXBY3(-e2+CJ2_k9r?A4G+be%mJr3NkYg7LA%4xIOJ4~%X3y+0Nh3=l-Uw+Rh
zzgzM|?AqShZI2jlc`kXmIcvhJNiV<kuW*{Jv^yi@RQGwVA1CCE3;2s)2kExXs;tgc
zh}R0AXXD0pQoiiDTu=Ev|KOc_eIph%Xy3RI`Epv}%^OjUnb~q>&MZkLF_Zj63XDAM
zdm|Qgk+QZH`G5^%_PV<B|GeZj|7S>8&Hq=rJQi(VBg16Bk9Ex}Gp0+OiJH5ls&?;@
zX`k+RTd{<>-<))N19Q!qoi^>k_qNz?-Ew!@`M(P@H@y^nd;46B&zchpmfIWXsw4>B
zy;3fEa^2ju2N&!K%=~=3kZpTqft>ti+k<V9X{D3yobbsy;<c*gjO@G&X4PW(HXGBG
zw_Zu9p4*ryeLij0W}CArMIzIxx0IwRhEMB1^F-@|hhp)z25auzXx}|MCf&Opuw`Dw
zJ(r3{Gb5)?SW)0$$?Cm8dE3Kzi#ENl$$z-pR<<<$?QF?6QSYqnt+-d*Wa&F)5M5>$
zaQpV0R+h(I58iHx-s^VX@8YC$mn5Hj$bB}QZ{c(0wf9&zt!bQG_{r$^l*zlF=Pdfq
zAa?l0t}EBde|6t{Z64lVxNK_MzidV8<GH2J4FdUYG#obLw(~r3sDYcIN;Q3MxqD<<
z$E$5h9!Zr?oeO66nI!eSF+Q|fTT{Kkk$qy6=;2#G!b1O@{JiCaefgv4yME6V`9k+y
zeR8UP&wU$-SBJST=QBvpI^Xf|vPpJt(4AXxj&d^#SGcV%VfNd&YQxP2M<?m&=OyF#
z-kGRe-EyPUqhx0(H)s$2$0(Cis-@4T`aJ2Mx|4b1mv#IBAGU3_o4UeTcHT?X%YPiX
z_)Xd3p1n+IDE+6(^1J-t>gn@jucm%XeW)H(Yxg;L>lKEk=#;JTstNxYq9T26e|Mat
ze#-6O&Z46ZR>!ZGRJ_+)^W<ty(5p+zwr6w;8XxvBc<*|ywL{^_#}li{=ILL^t1(S{
z#93<X?Q8c{<f!VEml8aV)|_{HAM<dqJXrZ<&2C=(plu(W)|3SwUv|9Q_M|v}zV4=(
zEG;MV4sc#e%QQOp&p|GfrFZ7?#Sz(3ZqpxX?=11&x%~2$N|W2OHI_D?4YzZX5u2ds
zf5+VI{JA}~Zx_h6o?E-@<{kI^(iKsTHvLj6MQ2u>ITxY8FlW+H8OHmW$DLhfZJW)v
zl5e`+!i-rhC--T)&2(9}=hMnL6F+TND6^Y-@IS*L@fEj!REKOfo8VvjpMj%xUw^)l
z(Vx#+ek!hM2f4gmiVFDU=EUsz@NTt!w?3!U<d@%P&0V*EMd-Hbs-N2Izb>6hyT6O)
zp<R#}@9Ak;jQ2px2*c`Dul&!D`nSuyy>!p_!rR_@Zz}E5LZu~CH!JoUSmocT2#yks
z`*-Yq@a1(m`pTbm^A=U4`5wu0V=*}KBt`gAgZAB5_3774-kMp|++6qPru?(pPo1Uy
zTq^mwue{Ujx&5B=uBQGjA9bwmEnOLTJYU7_<O!Z5vaeL93Dx$`%-5IsvzxETYhCQJ
znUAz<<pXz3$~Qk^UKiRGo7-EnA~|0-{pQ@>)2E9!uYYf|=g*?W+dkAjYb;z8o4IS>
z(iLhmx|6n*$ES0DbJtkMtdmtVTY0j|q?$$hkIw=X1Zf)!7r%_U`mH-Te_57%+N}#&
z`Z_1SwYl_bB!=3XbnkxtAf@L4^MV@ZN}bIyH($nQUebM9p|-=be_oWCreYsMd(~<t
z{xcG9b64G0`&aM$A?8=u<cFTI`pafr(onvlqkd)SEYW=3x{}@{hVQyU!z6w>wP|s4
zeB78Rwt4Z|W0O;tSKh0=d-ROe<Xx45oJ%YHXUsm*I%PM*DvliebF*hBupOJb^6$Ri
zVcR~{?0@rn>$bbQ?a~svVs9Lme_hyD_pbUu;@uyQq~+N%?UZI6b28;F-SJ7tp=RrE
z>pLFi0!A){`z)kqXIMMxaM(yMjnCfo_uuvfncMS=tNL?IuWl*Y*b(h8M~IWTYCpT|
z`I<TV`78XRt7Fx?-@5&Fo9%UJ!R3Um%Wp2_p9wTM=e_uAX~^+>l?^Jk3?;LUZCn}k
z+RQ3$`tqpQ^QHN=hfS|Oc382|#Jh2uxyodNH&#;X_G!$_SvRSg<Jel(SDBA4NjJSz
zIoGN5wy3d-WrFqGnE{hz*NCh0`+vxN^vcR_Zq4=c%QCJ_FDtvg;l6aHYH#mqC+U+Z
z`BTF@&L<__ak!)9@nz>0i4ys3Dy=zNFF(KUtvU5wSVU?QXKbh5IiC$~H<?*v7^PM&
z;N^8cdi@rU()XB)i??l<sFtzseC6{PW*H;@t(TJ)&7ElRGbM31gAm_Cm3u1JOn#<p
zzhYt`_4>`Ed(M3GE55TuJjyt-%2-I=SZLi*hBix<<x$74<eKgmje50hS9|;VHP3c#
z*}3)dtw-5u+qT>nUNG^S*SVC0f(XSM(pew(&JTQ_Zgt|L-123yFQw|HE{k3Bw(O#{
zL0Ri}jn*e8LK`>Fkqc+|+`zYp^Wm=TU61ZXJZlQ!mzlUBwNzQ5$wHy8IHJzzKf?ss
z?SETK?*G+oTT|h8?6J>>y!OOO`RS$E%Woex%45%7lO>T-P~iA7^iS%41_kT<-&`;E
z|BB{iD1q&<EBdFufAeKie(t#Vy9YC~<yQTEHqTK?FXx@ZX*o7e=8vl}?)pL<=nB01
zW0T0ozzezZzLjq;N$T5Ou2amo7Jg%)h_-mm<EPg4*IZBDKfp2{{bI5DL*)<tGyIbJ
zV*f|t@PCG*VN0sE%{E(UHeGBXXgTA)XxEuOEA|wfoYVMOU!`1bYrA=G&f7nNx$Dm;
z^u2oRmFsoizj}gP?1rCfx;#!Nlqy!d?qb-8xwzOJ{f4s)?=_J(kJcB~S0-m?XKEe$
zY<q&yXodUCIV?#riA6<RbN<|5>s|SuA^XP3;wL|&_1@)fdv|xfT6%X`fz_LH*6A`|
z7x4UN_<{c>ztsyMyLZu49shUzgZ#Jk-}?Wk{tBP_cj4cK+kboU?n}Q}ceZbTdAh~x
z-TN%oJ?dikyk+MHqZik!tbcsF<ZG9$zM<{z*64(78;suGn!#MiCBinjny2*V?2_r<
z|8eZQ67{sEGC7}TdqLctDCZToW;~xIEa{eXV8<hkgIuQ!_8NKGHHMs9yKL>R2(yJ5
z`m#5L?wr||Y_y<^v3Qcxrj4@A%oi@Oi_89JXi~bSyFU2%G^KmD-bLS7W4|T0X6mfa
z3D)Uyi6>{d9jsxx!@$5~LX^wOGym>h{GTEDKSTC^hO8U^8Pe*{zrQ7X^7rk!e`SB)
zS$%!9q&C{O@7|?{U%6eIzFyQ#$(*9|=COvrbDoGIhI7>c?CRBPe;EA^jPBf1o|Nmd
z@!U80ThpG2PcvH6J9&DHk>ag2tGu2x@7$h)o{U0f>32N5YO-7U=h>x;VsA#pa@=|$
z?lxaBpoyJz!>ap7%6WK-7uu~|cB|9(*uqSX&Ql&KGsBZP{#@eoXL0}h`1hVK&l-&W
zGoW4Hh;f<SS`X7)vsaI_t81MuWj@_59(Y{l)R_;H8x<IyEVRjc8T#=0m;0M<nqFJF
z?5OP}r$C{%k+DnJ6MFl&+q8cBvAtc++}yxbPbf<S)TA!n67|~I{FchaRDl?0X62JA
zts$$F+MdpweVXCH^su-^D-S-}>$#}w*JIBu{l4al{U>?6pZP3u&wqx^GHyv+!ROxZ
z5t?syq0Wn8Cox$g<JbIeOK0zy@OR!T&bWKem~QtJX&!veFjbjvNkgP;G_%E8E(XvI
z1J)nv5qDdz+TWu8=BusqQS)iy1+lkIu3C0-!32-qZtH}C!_7?`f3#Put4Ccej(JEY
zd>P*S&HouDwXgZla6{|xe+IX^7>9M5=$7cp9S@uzxcSnW-1p1xK94z^*QqkQ@7bLL
zDNh>ws%EWc>t3Y#Y;obzTQ_dLD$4JA_URl)%Zqo+bB|}9F6wV%w+wPzXS*kT-OC-H
z-=y#TceX3qdXIwt*1L7TPvr^x%=yod-krts{O!kN3*V=cv#m_OZ7fyW_^quy`tn+J
z|IJFemrwIfG4lB9@$kFW!q_!@-c1Y)cP`iHuFQC8va9r6Z+5woE87i|Y2G2NQsIn=
zk&S$D>8jfw^wjJ;X)PueHSO=OtLJ7{eYB`f+rA;gM|bPg{<AuBrY0E~9!xx!J%7X1
zua>61R`0xj%5ncq`tF;pER&=$Nq)=Q62<cO_GvNi(&Vil@K4XrbddbE3pBufe#Om~
zVP@Yizx%u{al6YT-{Zx32}VT@>bAZa(0$dSv1@ehpShdKT)An<r!<4|6SK>9eofqH
zP}RHoh1Su6s%b0NAFp3~=hmx>$3^FDOkaNM*2%2(a_Zip$%-e+xYBhNM)DO;I?w=W
zYEE8u@AjSBcVB*+e6Zx<JLPGjsWTe_xSI@)usCr3d+|k7_FC)W`<WLqug?nYJ=!B(
zGdpwb#mD^_w|0m0@Gv<XcZ{k1wtej_PLqy2{q<?FIhl{1v1}91m)s;CDShbh4)fEK
z7Uam9*IZ3H9CCfD`6ZKYdw=s@K3Z>la+BoT-n~Z(-6pfBT1FZx9SeEKqOHcUfN#<@
zUba_v*S>jlIjt#LW5RK+#oD(fJW^~t*wJsG@q2%@>??0sZuiSdecHTQ$1YhsHD2VH
zH?eiXN~Z^mhecJ3ud~Z)pQqN?Um15|+Pt{i9^$8_KJOQ7+~j_D=kdkRTTw#at}&_Z
zwX8dxnXKD;c9Db4ii?Y<-C^En@o@3sZR|dV$D^KpnHwGXJ8i1&wWZ%W^0r2wRXLR4
zA{WE-JZFu=$(g-7PO=8`IP?ha+W7dRe8=(+UuJE%x~;bT(6p+<M|2n4XY5FsJHzm}
z;Pz?ES`AgXDF^Q`-i!ZH?Yn>bm4Mss`F0Ds)OT-p^*pWc_jdcS@`VSTinlbld!4_m
zU!!&FPQK{(_GceeukPYZ+iIxuohvY2Ax|%0)oKRsngvA;XN##mL}<;+bWS=}H?`}X
z_4Pf)<+@KQZd-evdunN~5WA{j+954HKjRRzEvoKq^`*6stW_S}yB(UZX}|l~VV?Kr
zgJ-Hu-1%}hGXn!Z%9^ME_`TQc_7C6x<g3{H@6g8o3@=63W<|cV%9}GmwQqiA)&%7x
z+ALa4re!=23oLjJ2(bq-nodVmUiAKvY~K09w~k&tw%Go5UuSWBR+M$7?vjiP@@7{b
ztNc{h^}vVQAjNjRg6z_JlNYSYd|$cz<w6}<p`*)M4fBpp4RD|MN$4O0cb`+^ttGoI
zY^i?h#_RUkYvYc6&H0myO?TN$d}}>DTX15Nr^Jiw$sc>4ez|`ASBbgcB9~t>*Z!qM
zUsatPkgDULu;K5m!X35uI8K^)u6R8^uid3RVuDrn{+sWsb@%w{OqgqPXHLUH=C&M7
zE{0pXr|wHQAlq=M<m&$Fub1DlKHjza4oCQzv=EIY+l)NIQrR~oSxK$WT=K#=vy3x+
z`OEdo54|o;*>I>$B`-3ipPAv$kv6#{-`C}PUfnu>TV~MRtoV$!*P(kZ`KYltK0TmU
zcIpVv%o(?PCWIOs;W#M0dh(oCQrlZ=JXghLeNU@i&wMk+YqgA`w^7Vy{;!n`Q|taS
ze7gFvN9_QA0<M$4LZ&|dr+%%*ae0<`SXK6Y|GzVrx>i2d-0bmmV$Wf7U(Fcz-xK_&
zZfS_0`04S2i|b6K_Y3`Ke=B}_P0qSYx9(j{3fyk?!Q;&Nt2>JukC~g5*X(96SD7af
zCo(Mpe0iz?>+Q@O{gt=Y6j(D=2c);=3Ef@V1DdIsCOtEx;RxRnrc<16cT`=A+gw|i
zx#~xigvw3Xdka3CGi%<<y5<w(dH<OrA78$l_4JQv;fhysiXV=xt*`yo|5l#=&fSh4
zuYJzeH#aLyJ(euV=*)DOUGJs@!xzw;nlb*7$k4V8o9m5Bm+(G2HTmR>gZGtkZ#}=-
zcI4nIv-Jzs@jLAKsJ1fy;f{4Rt_rp3?pCcwHbx$j5^Cb%C|bgFuPkOqLD}3Uo1WmE
zAL~2bZ+V@4TVr{o@`u0c);zj$>v-<7Q>rR4ria-C`ZelTD>mp)J9menl>gzCZ6Bpx
zn{U6S$#u7LV(X&AHj_5l2rk*ocBG5tOvi5K+JieLlxJk_5^sC^=G~)9U)E|_N3XpQ
zvvlpAMAci7k}?{H6W#~$`?;?zqTYFYD)_fA#o4MmUeZsys&x6wZSCFDZ|dGUG;z;b
z<vz&|++sz0giju?dO%!Zcz0vv>TIjfw|851O}~}mSu(TcF_YTG;))BWrB=weZ?%iP
zJtxny%tC>A$BJk3q*M59HXdoc%52TbI<slT^PNcyvL~5#RO`CO%zJe4*)^3<UuBa6
zE?u&C`zU_%QORAJ3aXx&j*V{qC&HUrHy!7@?C<M;P)_9H`>*m^m;AY6@64Wgs4?%E
zL{cQ5S<_0{Gpm~_*>${muQ0xt7N>flRAu5D)4gUdl`AgZ;$Bj)=IvI-gAX<ruooX#
z>-F%-mi^cMq{`0Qo0+t2{i3+&^SSATDz}3o6&Uuk2CVxqiIvg)*K);v#VUTz`!QK{
zycgcTSNW{BZp-h=Wwi_P%6h$J_}DycHJFoj{%4S^Kf!nV-=SUk|E3*|Wi9@P(s9Hy
z4-A_hCcJi;*Ku{`+PZJtE25;2l)7&h)}OKFM66@X6QNaS*bA0?5s7?tD{o<8X@2U8
zsF?E^zx9&aQp;L5xydk3wG1+-<zHIx=+L{vNB&7~-*s7;Nw+*;nytew+1G`#cMd8u
z>-Gr9m))N!&UpNcPDQr+M;<w?O}nlvm}G4oYgFyfxb_;yQhmnTc@tM8G78RZbJK4<
z%xa;>c+E9&@r(I+SCY1D-0*p`?b}nwCgvZD*wcHgaGIsvvi`Ss<$ufnj{hBY{I~JH
z`nn7A{O{fV{(1ZR!t3ir<BxnZ7yqTvcg@}`BkyfqOJai&M|xjas5)~Yhr>x`m6XO4
zr}s7o?6fM|DBk|0DLU5Y?&*|Ghri9da@&*bnRQF`r`HE3{OPbfe}aMgulmDp=imCe
z`+qogdWm^__Kvpu!rDg9eBan5M7jLjeD(U3up@Gcm-A}8D<A$?mz?W#>7I3GGT)Nc
zqQesBiVT)KDNyl$A8x<sN6|akV)y-fH}-G{htAgvoOR24^@^vx73$AFo$2y=QgB#B
zz}J@B@mfyFvrW^z8<$KzG%ZZw?k3ONZ!=mBE}9zJEoztbq`{GK=Q$(B8&R)!*?yaA
zw>W*(jXMzscc0tY_E65^TkqMOjRy`W%=scpcq`82cE^vhXOFF|E*JfB`#-~`r`w`m
zuC4hlcHQ4(;v<2Ls|CLod01c9v*g@a%(k$ya#5D&!=Jid*=*G_S~mQ=7rAvBznPEO
zCC5~Wu;Pv3`%f`gor0w`5Z#ygaGS&D(=wntls5!K&d}<so~FQfXM&d3;g5M!Ze45H
z#+@sB$@cB+(>$}iws;l`pPX<<aAS1eU(1&c;<{h&%DsP6pLR7T?RVLKhE0{_9QQMB
ze*c#6=XUjDi}ykJk93IHd%s=p-s89(UB~S0zQ<n93vviBnf76}(~&vPxsqqJ+I&6m
zbLaXc73HDZKk6vGdF7v(x$<6?ps?<SEpmmk^A3odJKy=i`E5Y?gd?mxj5|vo?KZg*
zckW!ZbidZ6PnpZI4@^9$y0gWkXan!&zXdw}TI|lVZe;&9`D`A0U|+~emYEZHC)wRy
zQ7iG@hi`e&uddJLANFn3>oNIyA*Ju#`9tAVntL)8ZkKCDgekOG*3R_gxF;^XlVOr}
zap+~!#1*f^E@TGZIlLmfOsZjbS42y}alx&8GREz9Sa;9S+Mqan&JzZ{1+RBmoi=d~
z-6-TNd|pes<xJsXk@CcOqLGoFHcT8gUGfo|<JIc7Mf`2^_SF0HZ6~wgy2E?j-TL__
z{bWe3dUxXK+Zt`H{|qTVZ>7lZ{;2zIdGUmHt@~M@Qtj{M&*LdgY<;=C=dbgjTW5ZS
zE#xVyUNYVPBa4R370K$^OD8d2|1m}Q?R~ZetFysJfALLDxV~L#?!rd>phIq+m%kSq
zw`$!?U<@cXcqJO~xNG^kigv5{-&nUzWm|OJV(a9$#yJfqKAu#c@<jPR!)cAVGm@2S
zYy=fk&tET*zVSX^^|Hx+qiYsh67%!(E*{?z9p|aj(KyrTt<#Q^%yXDskFNV0eq`FE
z%*pqCN;&i|X-BW$d`Cq;Yr>k1o;wR}Kb*>OuRWn|L2Ci8cf5%2x24;z=qPV5+57MO
zu1V6(DgkFMs%%W`(hHn=)yQeS;Z&z>Z?9hPWx>A8tRQz$ed>#sIn(|#r0uv?<CtD9
zI<xlOylAI)ay}C-NxV&&dSmi59cIhJ<_k#MY$@}fp`-qZ<wN`5TqplCEC~-i{bP0D
zWrdG^3#LmQo0_lw$8)pHuNFg#Px*0~Mr#iAxV^g5SA5L3R8A3ef>z6ahBw;k|0c$U
zEhRK*;2;;jB-=`Le`lh2oz9kOZ(qO90UdLr4nWRRl$<+X_(A)v1@9F*xTNLY2VYYB
z5V9-z-iuo;-}i}cxoorIYqXK>y2Qx3^v|k+4VM;%`5xEsmx%dIU@AiLdP(WDjK0-L
zDsAfXLd-d5Ja*G~ci2X2)22xkECQ7xjL*yMR4zQYwyred>scwtDpRr5IV$s%m+NlS
z+~ojYX3Bh}#&X&ze~#7-zm*Pb-=3PVb)IGzYjvlJi<(*ri}G@YIVoXJukBuZ<K=}c
z^I2<q_xAj*nLTrzpz`E`JG&$1$TWBy4~!CF08M0oaQM{M;c-&c{ld5JW!1@leqVZ<
zZJOo#wTC_PIkyVwG|sjNmU*09{C$I6UTx6kFKhjOyT9GI$IkWW+&j}Q9o=1K*yeW5
z@Uz>+eeAx!{S_{-&wTak*@W-cw||?bc{y2g-P$j1r-L_te$xHhHuq$Y&oP_#>WUvf
ztrk3YXF~QpnafF+^HQ&Txf`aOzrwjZ?bp`sbH`ql%$R9(@re70gHt^jHZWJ54o|Fo
z+>v9Wow?pKS=q7d(;lu#{PXS#MYil|Y`WkQqsZ_sHB9?7FE8OOZ48xj`<5=b{bJk3
zlj~n3W#?);1xsAb{q*UU->0)ebAR0JVesVg=AXecv4~&bM}6?MMOXAoWu@*hKQdfV
zX<jvV@g}!f<&!oEOxpCsXR(AzAHT%o9sNgzD~+Rl6D6(*egAE%o3uk$WU_?IW1%T5
z3Z2^xH8^e^4DGvc$@h`;X=$NbeN&&@U3+)!Zk1y3)@hZ~6kcjN?w0NgS+zmCCpR^X
z;nA13$%n)Gms(t}u@{Eitr6>WM_8u2Y~zU=^)seU61>ycP}tm4q4&k~!@7kmv(C5w
zXV@ZtaN8{(mRDs*_k8s{GLh~60oZC&+oD|mQy+P!O@8wHt=Z%|KX>nYKjp)^JIQl?
z-aJ=v`@T&up~GrcF&=ysr*%R6pOBi>y(x*c`F>ZDCYnmfpKa6M^mBJ;%+6E+`_tRi
z8+Lad72mbJ`KxVa@NZ|YEuXe>ysx`)>x)qozh3I}5`&-nb<X#$so8RTrslo>44*Eq
zAoj$X6E?0!S<Q|g{`F@nIrL31*{*hvX+veUhVR7v9GBf17{5;owJzg*z}{?{YaV{3
z#=m&kE3xT?-YZwHY)UQO5`9?AgIz(q&4KgSgPoEr!q>v}*Zk<Uk$;eWWt~aCnzu(!
zVdk`ROAH<AB2N5gn3fo_udHd~%A^HNi<4yi%XSto_2r+c<g#7t{cfd-^QUf{kT)_o
z%s7GhSn>1&3>VOc{9b5dS$(KI|JtA8hxvS!uUBVZGyCkg{mk~y&S!RS?7yoQ^TF{!
z$@8VDKjI(tx7#E?ik>U%n!WQLcX8pjY3(U~3l=Dr3;aCYc&e}cwu0<Z<a;P#Y{G{V
zFDb~}-f4VPbjeHAV?QH9BTOzD#B5)^*ln@;gaAInAbbmD{>kmQlB2g~_S<`@%N9Q3
z^#k4T+tTZ@z3Bbj?>)009V-&gPELEc<5*4f>RUg;J+AUxJZt^K>vibNl%Cvak4(0u
zCU0lqIq^r6`PnxKhIfPxf<OI2ynOYeyV-6#ukGLRaO0LO6S<E|ofbZEd76;K0oINX
z<)`t}^CeH4%+tBHevgfAsdk0Rp6xenj3O5t`{|SV(E5Xi>f=vNkDq0?zH(q;UNEa7
zcY@8Q<3i#gJa0tA(zq7Sd)mQJuEI5G&;Fn*Tkrb&Mr)>hT6S6QjqdV!*#$w*Uc53~
z<aNsI%}>S1nhkf>UMgY;%jJGc#45fO%ojA)@tyk5aKvisz3%1vmaEN4+kPeL>0<B7
zbUW80fybvwKZ-24Z^sxjoiXIC=9P-<pxKch)=gX$qmym>c8a->PC_fs3yH=_enz#v
z3|XPp9VRyd?>*CY@m!}=o*C*;xn1d)U)8>+J({m4EGQ8z+Vh{`h`Chn->a`{cc0#J
z`H$nWsM^V=f+lHByA=C---pRHJI;B%jmf!F&cJu+x##8l+;_R}zWnxlu&dy^;AyT+
zXAWqv9+XI8QegSdP*TO!2f7h$%L|j&XSI$!I>x)tcgwXGACGUzja}u&#;B0IV4dwB
z=X&+-H(!2im43hZRe5<?ruy`(3C9%sV$U*7N;6VEw(6{c;iQNLW`#9>)qaO>{V=`p
z%WO{5$bFX=Nv~Ad5bba4q{A5g{YU?4rX(xzpTUzq3o*VBj>z~{ReF4WW-@EnEe`ej
zQaVX@nG>aLDzhYa*f997Ty)&&;+GSPyAFG8+|p<1^I}5ulEf6PfE^44M?GV{9z5>#
z`9H&3*(i-Y-j9q|<m~^?&|-J#gDd+~6+z!^PaB;W@2om?Bz1=D+ewG>?)rL%Tz|a(
z+PmD+jK^K)BQ{@to13yVykB_fs*Mw#ShE^W3s}=`c{0HvfbSxn6D16nyj-34?e+3o
z9CCMa;|#gpW`qcAoY*76ID_?txqQ^4_gnYoUGQAuTv%Ie^g7vJ+(321?uxS$cAdB<
zCVOyS%v9!tm%E>>TYTvI^zFBJf?g?$d+S^@i!-ZHS=YVih*#z8kbJHJ=>mpi1}5+S
z4E&kfzy0cx&UpL$ilEE)vKK2YQ{;CS{5bc;Lc_0Y0>{gs$QR$rzPATWI(OvNrz0Eh
z+;`4Vt}I}ye7fz=Vy=kC%#*t=ENU?RQfvHM@9ZVdeHTk@))y9A#xC=ec=B<QQ)5ej
zr&h=6$vxNVQI;95Ua+qIc>O1T8*k7eq4j@75SLRj9>0|>@M50AN1gI*RqKDbEtI*i
zM=JEpi<jTLOHNcgPW^r2@cOJt=VLycn_pO3n7Zgy*yX$Xe$Q0=aQBwU*-1rDoTphP
z71jE$Eu9j;&d+m?WBcZvo7)d<KAv5={jI?A);uTgEl<lent7W~ocG$9yRIVb)V*8x
zF1ub?&~)|m?c?HY@2(~$NeDGKx2jk-xqt6pxo%Sz!_(_W>g4_P^QNv^KUMp@oQ-t_
z_zaN0=Xs#(s>1(W{V@M8gZ}=<m*3cb(z*Me;rRYPAOAB1{#*Zd-n^?f0v%*(cCBxD
z_M3n9f_Trr^ZPgEeK>pbx0zwT{&#sbv-Li;7hk%5?_7H%$gEfN>(nckI@PDubH|@i
zIn??@YoTtd<BrLP9?Ken%!zI946pl}5qocspWMy0f7I(aTeof6__JjWbj~BoJ2w1K
znN`oP-g%9+`L%ZMt)9vA++8v$&w6$-2V^FrOeBEao`}P1i$475Km6@KL;5F^wPE_3
zT@sqp+w;Xw^}Ic$r}z_gYHD0;_@Uz3_OloCm;5__{Koc*v^U^Yg1`GGONTGBd+}x6
zp)Q8U@3zKs-p?|~GM~lz_2?Jrn%Oh=7?(k=LrgevP^G8DBra>8@D-h-bKf=A7H6qu
z9x<*+dka2@W*JYO>Ws-(-q~#hd4I-r8>4OS^LFViQK&B6T5-JX-8b+hhMx)o*b>AS
z+^Nm-tZ{$%^J!-4rLB=F`TE8C+w(c?qQ(2wPyQ2AZC_|9b3M?Nq3HD^d;aCqw|iX;
z2Td=?$?lO>sl7d??s=Q_ef5=h?k(GVJK)0~`J3%t8?KhTfAcePk#{}sJ)Jc3^Rp#G
zJ8IU>y}>ShRif>7^PNBk8S7Va^4l)F+p<>ZaOlOwJ5Q8v{BZY)Yk6Yi^&DrRT#2yf
zESd+I*@O5+Uu@g<G5Yq6Y=eVBEPWP#?5kFFu`w_>H!wUFh3xG6qZSqa=hy4`Ka}?V
zXLxKneSP+|TW9AkojP^erpw!wC;VsFbMf7yfR&}f8+AUmGH6Yn<nHwry1^Z^i3b<n
z`P=@dM%DShO>6AG<lZg8+-LCQ*S4nor`va2F}Ym1TyfVVOErI^t7Qo%94#HUe%#$B
zf8kp7kM={mo;R;G^$mLNE2X!nBeYb#`*hmx+tP*Fd%foL%n`Ah>UY@t%Gx~vt7WHr
ze7W)N`6AcDw@>FRb5t~n-oR8kbC%DB`U&h)9hK9H-<Iqby#2%b(6?{jf^XiBeEH~9
zG54*XA3elOB_|%~(7kai@*7*7(xEv<7uc4~`p0>(#(QN%=C>%b*()M$>K?r_;V6%4
zVv;A18wdBs$juGR$Ev$ts_oyr{kQx4a+dhC4u89!Og{tX-Y7eNH-6$yo0{bpuFt<w
z5glnKxBKGK&7V?sf2dtHL%lNKxa^rst4(H?qW?u}o(MAFw>)4ad^0QR?7!``c8#@J
z>oXIkeLP*9x7lQazsc^$TA$RO>h&!Au;u{Up-CCc8}MB4j^8oY;#(hFQQWk%)=g6=
zavk^T7#*dj*OT<pKh>ATYdL8DVKS&>Tlr)9;p<ZC)-FGtb36Ch(QS(s@OUyzRFgjD
z_Vw@W!`tWS&G~Xig4sFzqv*VewaK|Q8~E*lHg7&7{N`du`V@}?{~0(xNu)d|wfyO^
z;%mRi%UycYZf*G<*1vr1l<AF^o|d0ly*Yo%@^;=mJnv*S@s)o(`|_UPl`vni+{pSZ
zdb(RfCuOel+TD?`Wg17y$t1s*h8BUROy1rxmipD+x^?E4wN4UmzI*D;f5Z_`xx(nX
zxwi`Q`i~mwxA*ZflncGyWn-WCxinhhKf@NoZ@Skx>@LqqKK=apxu-AZ@3GC=yS!t~
z^K0u%RxWM2_ey$mZoc#x^E;0?mZgPSs58X~826;_m)YO>MK(U-O5U<I-7xLgc(1Nw
z+0~J2g-<J-iHI?2Jhe`pxy1TB|G`7gyyuDsOg|!ZCh)~3js4ej^xc;46O?Sb6K&}B
z^Us}UnohkfslOUL8Dv}VFNBeade?7$d(YaiWBzac{N0{=NPcs&<!8&EhFf<%emCFi
z*&CByKigoxEt3wpG#!rEdu7&_lagH_v)@_=GUWa~ek<I1s{4r_>QC>UKmTyO$i3+M
zM@^T^W^dR3@*+VfT7}c5NnmAO$AUHNX#yvXZrG79<8(v0)cdZIyW(!U_lk#2J}<iW
z%7*CLrJ?JjSd*3XgQsdaC&=zSnioF*$Kk`<{nOV)zPu;@yLR2uMXt+l9nOEE6zwTE
zXJP8ZDXeS}r>5L-JAB~K^9vdbIEUJotg#n+>AN<=J7L?!yUO=&?%8m1%W9YDhBh;K
z4@!&fcz=1`6vm?au@~R{JN_*<>{$Nx{NL)+3wpox&aY47Kf8UOao<-J{NZ={?vJ9k
z?@V8JtV#a-zVxoyQx#Tb&wS1;I-chWmRWWLpO4|6J?ocyduepN&>_8ZOTJB;HTT&<
zL8IH;j?X2xy<zlu^J6}X-BtEV9*2Mf($nL#H~YH2dGmbZj!$d#)n=vb;gk`Ip5g4S
z&2ZcPI@6I)3rZ~4w(Z~SZ(MqZ`>EFi&zTH2mEYcKzu5QXz^iio73+=bxnB#tIP4$G
z=JD>$AJy_jvyV;U-Ci`cHHpJ{`pqd5dLI_<p1`TJ-89xXOsa2TF56VwGgfWe6IXEW
zSlZ#vQz#wq@UTVgf#{uwRx?Rfo^xP$#kYI$n$0ey(Sj<5HlG&m@HsAJ=w2rIFm&pa
z$p;jgPptaS@L@{E+jW`0T*@zamad4heY)*rK&Nu-4&^y>4|c{dakyLl%$~pX!<yB9
zCqK`eQ1|}G_FZ$&ImxW9U43%Oe}>9^6^2*a#FyPuxwxg*-~S`uY@2IB63nl)b-Gnj
zT-5h?E=rT$<g6vXi<70N@f?Gd2mZ6S{Nq0IH9veT`)*}%rpSwr(W|W&os>GS5cB7V
zK+Ca+-%iKpZaw?M+41U^_>KD(imfhHo4C}p$6M!GlO_MVO}d8|j`~kBxNJ1R?1@ms
znzDORSHJXgo?WgtQ})QmxR=|zbe>74M$Ecjla-qKRE%l$Zb?VE$T>R~@H-edUFR&g
z=$7u1;>p!}YK>z8e*kBwO8G5YEia7)OvF!_SpH`a_|I^n_)z^f(aHZAJl3t&KeA6|
z_mw=G$in<&na%fp6qfw9<a9WzXs)`LWzGuKhw2vW{eGr4&i@${&vX7~xDn?6S83O3
zIpvR{^V>~kuU@&daoyrA^Pb(i_)Ku``Kgj+q36{ZiX1G?WiZeF$k+c!`fP>n93gJ8
zD{u1dI9&U9SSRo#XW8_knNfusK5#9c)_F1^a0%hKBXH4-2L6M?8Z0VHc*`z%YrihN
zvbZA8G_~Zi)Rl8Vk3M)y*Dp!4ogJ(`_rO$%-#6Zx=-U5QK71=}c28~JCGDEZd1+<}
z@q4$Hm%QFu{K6_wZ1>``-`;D7Zk+tv-ahwsLHnB<=W5Q?`Q+y9_`Up6%Qc-_uTp-e
z_D`0dHhbC=aUqlSV%Opy{=A&<WYWRu4C@u7M8ahL>0d~!mC;+CX_WPyH$Pn^c(L-P
z)k2PUPuy8(asJFJ>#Lomf6a~^emiT~(q%Uf<f$~KR&N!Y7M^;0=eFJ-&Qt#hNfh^7
zU|TBc_dM)!&O7DpyRPUe%yaJ*vP=t2OV<%#@bgUSV|c&i@xs+p7{c`*`SZtQRrRFZ
z+;;1gAvbSCg6y?ZKFupnoG^C%^x!|klK1D|9W530!GFLTL*m^RR@2r#>fCB}HGj*B
zH;;a+PS_&${@LP|Ns;_Br6238m|bA_Wbz!_<d^?=_r$t;US2=z=a;imm)@Pb^-cP5
zuFA%ZTQi(1b$UOoIw|?a$GSthwM_o@F8gox-}Zl7+y5>7&%eJ5ZRYRY{{DIXy~pe0
zwA`<5x$*X`o_xTT2>n>0Yi={0&Yd%A<SRJZuE6trD?`z@I=Ow9x7-%m;8|R`<W*6u
z*reJ|uRM|_sTM15tGTb`DsOjjpYGz6>WGMIYqr`8XZW+;n=DiI>E2C)4Lc0?v}wFc
zuACJlam+E)!Xdi#m3K}oulSLISF>V!|2(^NQSZ%Ky_Vb(?#2ESRyZ;@-3ZNpWZlMQ
zd0~Fo<y@C#j{~-}xI9%c@>#vHr7n|Qy-E4!$G`WgiXCL;Eq>^{<aIz?g}3X*%TFfz
z@7OZw(It+gPxB(zHk}A(K67KW&TRkK)*^1MNw*JvpT&Btvvk?3U(*)MO49ARdAD|s
z{!N)hJ9sv(JeAYuGs*K)*MA1N>?Qy1Ui{DSLOc0CgWUYQ{|x;t{~7x0f4;r`H~x35
z?W?)VyT3@!=Z&aniuJp6*?+IAp=YU;8?%7lq4MO4!%U18TD2O?vo8>P{&TReNX*^U
zcVBGEHhg(~*BbGtl6?7lJ9l``h@9pg@x)(aal+)blE+1p_H~;6oxA^*&F>vbzfGJf
zzn>64)${J~wz^k;dQU!nYS*^;%iMJLt6zJQwAq`y-`a(2-d&;*^RRq{icne8Cw+^<
zI?Xat43EC%vsLu{K2&rxyD(Giw62qNu2y!v!SZ?MpDx-lHOSnf>(COW6;ck|n(G$2
zT>A0aFH)s1^G!)*>*HgsA|{s(Kb^2-a+}%b!fD6u`77J1y2}V0`fL;E)^GfN>Qo24
z+fGmS`dtm2e1q{;gUWjAJs<pLKDItDaVyJQYKo`YaxVEz_fB-TZrz$V<5P0-yf;g}
ze3AI#_56=5sEiY<zY%8tS83}4e)((v8PfKD{q#ak;otko`Stvl%U%ZmV{sF{P<>@S
zubn{lJ(-VdUuR!DVe+40qmg^%@+^OjNlq8%q?vgdHr(W4IQ9L(^?l&I@qZL|#sB%6
zJ^zO-sONE|{*d(2{|x7^?flQseEa@C+gR4bAE!S3_WKaFy?$AYdwykhs?JBRkClyH
zn)$mY7&jEoX(;eeNN8~X&%lv4{Xc_!)boG*`Sm}(%718kS^xR#y7~v-zW-<F50_tA
zaXjS1lIdpNEaKd`WeU}+XV0B@BIwf9mg;xvOlA{KJdr);;AX9&dTa6gBey2i&iBuC
zvktiRg5&aL$@L+xKDk{ubo&@f;i7jE^^+V77EfZlh3-^$RIgk;{-REM|5a0cw%gw2
ztcy-Q*&OkH;__W?m*)kWJ)bbG#X9F_bIr#mJ8k$5zpYdH&(N~}&Ha@B44vwKzWvsz
z|9sy5wcX|2??3)qetY>@2X<7mF@h<g>fXXtw=0glF@2Js$du{Lx~WrHD^I^>ds^xQ
zc8iX$5(l|^Dw}*P>J+lACT!bjRsYL%?d=mKud`b|&-vT+@!x5cOqJf9ajH+Ra-09z
z95jXT4k6zizVYMOKilNssixktQTApD+qb<{zp3c3D@&4zGqPsKpO-2%+du4+WHv3E
z$GUfR;D=3j{cB}^?|u71+)yaURXnIwb6Sqt1+(7c%*^T{jOwWVyXx<FS>e*2(zOTk
zRc|lOoCdiWVZPa$f=k8%7BA<Nel@*@ae51<j>3nv+dK1x{kz?|<22&l=3Z0XrFAr7
z`tkEkUUTLxX?_`G*S#q7(%tymw{E;Fzdp0`D@Q_?W%r2#{4-YGIeO}WS<#IL*V&i9
z`Zd3;r21LcKktLQ`#aV*-F26fiqN~FXf5i;nXbZ9^n3xA*weGm)_t2U7Byqvr$<*z
zDwC`x-;$oQ_fy-c+p>%7CzefORIgXzV=&XHv94V3=UUaY_SD+)r?-yER7G~(KHYzA
zdXkem`x!OQhzUOq{k_Mz)?01nm!0~hcZ1#bU;gG^D)J#}Mv`m%Jx*?$O-yW}%{<9@
zm5*g^-N~}*+xzgX+oRv5yDOT0-H59664O`HzA<rPoAgwt2(vdErOOz%JbqQRZS(pX
zoBc*val!5ne&|1!a}wQE`Dl*ko&>>0vGBwgV<G1rU52XWh{*jjcU@xpoa*`HOv3w#
zW^apM9ZpL4Djj|yq}<AHc6EMne);lS{;ZeVcl1SsPD^8S(Bn8PAjqKpd+~+PQyNTr
z%*4t-V>G%7-ES^RDBP5Y*D~I&vE%pZPx{RLQ>wToaVT!x-gWPu#=|BRPMN|Lp{~pf
z3>FN0hCzW2tm$_%qHMn{W?NjjG~!OY<Mxv~XWf<a_%`?S)(-HnjOoG{xuvVJKi+>`
zZnkSn;nDOpkuSe(+Z46>c;}_75hsddn`WNY2y>qEWP^eRdxFVa)BJmXOMW|6yj%C3
zN%XViR4z^3o=KuJ9p6awwXHsh|G==F*2Ii~6TOpNR-xJP>N>fHNtg4}=ba3E!Zpcc
z+9sh8;gg1jJPyB?v#rB3A5poldF?B+I;o3m*S<4zmYe$UZ1+Y#o8QeMdnW$zSWum;
z%s%VJzN=ej_g49uT@U)LwZDV4V}e6p5dWKt)~qLf-~M#4ub^<kDYFTDn+T7KPdfaj
z{^qs&H}ARMs9Eyc{^rN0KP#lml6!X?Gd!l<f2lM#{q3xf?NQTjDek(OZ!(#)QJ}Jb
zd+w%<%xY<7k5xo{44DkvULEg0Ql~Wk@TIK7VK=|Yb49-97ueSGchSR1WeLY+-0ns2
ztYUn*buxPa`--p_In@h!pl$5ezT8}|>hSUQ@seKUmA(&J*;Pb;Zhm>*>(RTnPd)ae
z^K9RI$Fcqqx3uP>2?}yPr_&~BXf5bDuIck!L2H6@YR|0RZA){L^OxWDTy}o>$wwB?
zJr~VfGB3@leZGp5!UE0y@2#_||7_S6TI9u0#UgyTG+*@So{eW&R>)Z@C!Bia=Ezdu
zDD!LsbylV_x{3r)703LY|7VJA`oDu=^1sa9?czdPuvNmiqBPeu_tL|y+>Xq*w_fr{
zi(Sjr5am$Z)L=B}F5AP`k)MC;cWnJquxsv;ldJET?wvEyucz<S8c+6e<)W6y_QosT
z$K3qTx0t8=&FbfC=ic3TIpI|Qmx^~sZ>vP+xK9XUSe{{@)-y?@cbl-!)%oFDub!J~
zrE^a~d{eZ^#>#CU{x;ltS7Ud%opHmO<C!w)S`1bvzUJaNuQ_A$)h&0O9=*DEI$+Dr
zc^ALM9OpUpmOG`#f?ca<Ny0CAug72d`Ce`Nr`i%b*YmBesr6YWrPOU=&F74BZ!pcg
z`O%J}b`{?ziH3#iDx$rwtTB~%H0xA_j?P=DTcW$GD{CfB;g(%9u~D&|qg=9~c$;$1
zy9IpB!56mF=AZg^?b4e3KXZQ8XK(i`OP4(Mpl}Y~yrw0WOXixpZO^XN_usOyan5e{
zY_20qH?VmGuoW<z->`ZLW?TlIwJ|#(SDD<&y^5`ji`$qr@O;q`2J1<zo)LArmu5#@
zn07FC@h<nhn=2D1XNGm^B~=<pH<@V{-d}F3!Sr<B?!|Zi_P@Ecw&#A{{crwy52fEq
z+x<HuKRdrBUG|j+-muG_PQ>jmrbLEcgSp<G@U&UoH*cO#E_@ml=WBAdLdZg8yFpuD
z7~{73b*!CF9bObi^VX-$OMAUT{M1y1$wrKu+;4B?Uo88w@yfgSz__%3;@4C!w$0nc
zGx6@tA71ZW&3jd(^PXyR9T8~P->j)9eduwyf{<%o)~>WQrm{}Ac(tl$l=9{s4iGQ&
z7U+|BWVY~dTfy&!?ZvHOEJmN_G%#L~EyugN*!i_s_LKA9PRnmNnW=hz-gSjE(;MY0
zUR-?mDPDnRee6w{z3W?3<KN7;_G$iJr@HsbyCQ+7(Qo5?mj6Ec`C#7~gS}=S=dY-U
zj-2mxMX~RE$)uP66k6G5HR~6bY;v&r&mh!PyZgZf_Q+Kg`yDUkNPT-8yv0EERfNY$
ztGah-1xurK7_|7F$vUl;DGdD@FXEfK_V|*_Yl3(0c)aGHse7<Xb>_sUf}6E0SzLuT
zK8CDcI(>aW)-PQOpTDj1@ASn>H%0%Q^*Hh)>)bnGso!^1=5p_-G;;Px-a08f$uD99
z&vTx8jSlE*Mt5;N|AS*gVevn-<wo+oUt*oU+Bi+Sr88?))-Ri~fHnCX0%xWDPQ8D&
z>p|X3uBmq%oeB($cRrH;$yee3@6e|Dm!em*VqV?KoqMG0dsOQZ;S(Phx$B%-bLMFi
z1LsMdzyq@1=9HK)9=}&n9y<N#^p?4vUw)tUyB@&AnLFuf&D7?<nW@J4ci9T&Yf7^{
zJuSL3ap|kDdm5pArz*bOc=vp#(!;k;w*@Oqn5lb%(dx`uwFvtY%%>Ji+-$3qbt`Au
z_j1k^Q6^%3FH4oqEKNv}EO>4aw0IJq;l0J(5u5jP9eQ-=)3I0A-i7t5c~5YD7&BjA
zlJCI6Q%@4uEPoa_SbV*>HM34GrlN9-?DlJQ^3#2~-gz$i`=?FS$GJ_#?I@$_pUsDA
zme1Yz<G4#k(0_)LmviO)r<zz>S66Z^;Y;41bHsr?D|aIMU1i<_7E0Sq@}+LRick8T
z(Cq&^ZGLh&|J)+GO1(XIH>`8GbNH0Saou^%q8m%=7w=olHnFli>H4L&^Q1MGfbLMA
zdX-<Dm6L^!3)I1Xxh(7a>RYd#d(9Qg7vR3BJ1b((?TWesx#f29nTH#0ge7n3GoH#i
zZ|3TZ>)U2c{}%FnUdXO3xw*MIPQKgCyG`;x?^<_v;^)tKtke5;yjH%7@3P)ig%w@r
zo*yxIX;yTwc$fCHSrKWxPfl_lS}V;s$NYVx!UQ*~;sfmR{~0*q7Uw^F8+7KDqwV)U
zir;?O?m2P#^O=<v6GdmUXzB`{JYZ8*_!6|3qu|%{*3^Cf8CtsQX0qJB6?Jc};XQ$$
z-!|4xugLitxT${1?*}z^zKgc!KbmXy>v8b5O}n;Kez|>P%{!OvS`EfiUbsD;v(te?
zdWqAX(gl3=;TKHX_wC)kC3?rH?A5h`n=)*ED*ZbjU6d@GhP3o5BYaj)RPLEwuJ=|8
zZoi_qdvj&(y)yIQB}Y!q*Hf}{<5}gw+8})_YBxt|uGzCMHyu|*d6x;!IWSq<BD7dq
zcENMTgF)2-?ooZuBR2Q@Wv|fJi7#Dz_dx1SPML`-SoVFK<7TcG!^DtK-No?mO^xmv
z@QSPS&b3?Ca{45NoIagtecHsUxc9~ZmI+HX{A@TWu5huG*FUN|VDH70?F~PAvgCYk
zA9^!!+1w{<T9h}z7h7$>e=%6ZhaZ=Huar2i$apXNd++Pa4^ERcKdbQtuX=YVS1waQ
zNa^%ji=zzbFYn3h-cqZ1w5QOjqVGRLz^+sc&OX=O5l?dD5lgIg*9spIyCvVE-giHA
z%dX2N%P+rMu%X&)j^QT;%NbkT?C%IqD6ctr{2ud)*++hU%$X;%Y4hiIll`Z?IrHgF
zi^p1t2yccXW-4KMMypN~+}?5J(pHVqTD^P!SSJdloa_r=K5|!5hN*1V2Cc&zS;`jh
z*}Xq3e(~0iD(+Z2%j64d76i#XF7^wGkUr)1lTji1{hiYidWz2zr)Dp>sJrfM>3t!S
zZ=2j%&%Oy4`#jBQ)B2kWdm0#ZI5K8iH@q^OSGW^$DV^x~AJzYy=jnhB?5qFfnhjbO
zk8;!K1$IYVtu%tIt&O6sbA;AxjB=FeewJI(!(?-eUyc8_53_ubQRSN7*8IFLe@RX|
zb=hm%CBEB_J{*^FD0_G<r+<3ys)M_8*=@pP+t#l<xhnH|QT&My@vp^qWk*Up7Ic~L
zcX{?g?){a&jh+`9{JhUlv%AtV&s2JU>*R>r_iJa}JAN?ix|+RaY@W>xweaxsXACy<
zF7<jiW7<8tD2A{6Z*=8<C;yKBt#$mj|G)aWbMwmY-v0h^_q&hRmy5;+UD#t@n4T%N
za%pBz)UCHoH}%#&))afRVnt({xO!59)dySc`8z(ct;}5cN-SKwKCRvRckI`rf41#Q
zGTlCHE!URp<}H#lnAT4JE!?-}cH#ZV{kyH&CRTkvcTK9TTl3!qvt=cj`Qci1XUbS_
zbvP)PpYc4Q?I5?%weVZjy~X<9)PDE;U4BHWb;^FFKNpUEJKKG^r_%6~rFEscy2&5G
zb+31AJvQHN(e&*6m6>fny0>lRT0f&h?6h#@yfBrVnU2ceD-|YB;QIucPF{J(aoM51
z?}kxIzJ<cOy;d=w-6>{NeD%9dqJK;)^Mch=pMN}Ez2siSs%Nrp<(W0!%MWjJ>1pv~
zowY;4@v6$ra}}ZX)jAH=-gDJ`_io?0efQ<J>P;^X-*MN`I&I9bK%6D9gQG$C@5L8d
z)@!-l_g!9adA-SM>23+LpJtb%7ay0qxV3Dhgak`tU(?Q7?XYWpi<jSt&5ElLzjgQD
zEZv%xkUovx%gQOd#~hz%Jy$H77qb0a;n%g!kyrPKKdRPVJ@di8Qy29X?4IG&aL<pY
z!H~63F1f|h@sD_yqlBA+T!+bA)7*P^OMW{t-(I`=m}2Z&t|l=f!=?sfhP`Z$UkBcJ
z5oI@1q%a~g%xvOu&ACF{B|SQ=Ug8XV5-YXm?XY+mQ{VY@zCh-!-mCLweZTylAuTg7
zuJTmQCCij#gR_^t!Ug|55q_GhApWFg$CZ6o-!J^QcVE}^k8Af{K4^HRa+2YuGDFSV
zJ@z+0ah_yMKdoud#qd(>&{><k+a~CP7MUnBr}XbG?stPONLVc8Hw(1xp>{#z+iO=J
z3#_}=>c}lAanM1sA+EXb>l%B8+oy9M{$4WeTlF@pbqhbA5fJR&8S?jN;7Qhg*@(x?
z45cEB)9W9;HT!oz&^cFj&#xwpdGGFus_Qg=&y$zD*Urj$?h>P{mbb0kxqBa81x4PN
z8y7LndiIOlmV7;i^ETV=Pf7HaNhm6e5(!|d>t9x%dUKbj`7OQWQ{U;OYi~KJEHlr@
zBfy}GQ#DYusBqT#kN5vfJ}>m2;fB`h{|v6CC8Fnly#MF<ytDp|Xz723MY9_Cf1qvU
zw@2L}j$_0BsH*n=49ybtKUQIc#EK_4x9PFTqaWIUeg;J-<k)C}$~J!cZLfU(cZ{6>
z>?f7;5^g`s|MV^W_w9c%rFV}<Z3LZ8P0)xP>aFYK?xyyf>sa@(O?qm?ge83ogw`;=
z-|{PD3gh|z3~0w#1Y+*9kDh#<ckQ0-;zGxH1Qjb)CN{0okW`s`fT4I6&xf^#qPJ}9
zyeoOh=y0*t1c}Bg4Uvwv+xepy4r3fSu=t<we)j(i7p^b-&+y=w{6DQ-TpG;t|1-3_
zKlq>Fi|LE{ABOG!8M;Q5p#{h~{_r1v7rfY~v-i@|O_RR+H;Noxk$IidVrJLs<a`Fk
zosEk9+L!0q7VUX|Y(K}B`*IblWaC4wtb5p`t-3Y3Iy5xt;LYvRa}P@tnZ5mD`PM=7
z%l&>k=6%~U^Yqt!`OX*OTAK0ZNJ7ow)AtO|Sv_w)?(?o9JLb|K=f}EH{~0{?H+{Rh
zWvxwq>*p;q_4=;KhHh{RdC>DoYhUk&_5-)nj&(aWy-F15T(VE?alOyR@KbCmrJ=GO
z66~TYmpSsT@7wBKU9q^0V@s{Aa-S*Jibc^IpqIHXT$)|*%4|_)&F=K-+p{eeXEGX@
z7@e4}?=xwm@q-e{*F9GzX794OpZ95Nw50v!&)@ED=cqf|^Zd;7C&#Y6?%!3bJ^RDG
z#+5In9^a4AnS8Xoux_bJ#`zl;-_47dWs}UQG-tog(LECz1l}%x$j=>r>u=xnn66)s
zq<J;B9MX@wx^_v}r)G{IlY18@ibr-NnDs8%oXhY|?%z4<qnoRDh`s!{O;~~NCZC)5
zdL>Ja{|tqDdAaM;{>9ziA$@l0gMK0AeJ*!*vajatpLiuV-#JEZ;-dTh53P4Undj>q
zwRLY`zD~Q)shsE&hMf{mU5;s<v^?~8l|y-Ix7$62tGsPXm)ibkxV6wK<l?Qfg@<hK
ze9+NXjM*5*rm3Re6#aHmIZp)h4uUsL`3HUUo1HGYar>?<yXQT8>r-&NX!k71=Y4_(
z%qk0v(rx(+C(e5Q)mJ>=qs*+<tH-)k3}Wr3GDpVk(K#<8-mA0bpzMT&o>qA$ZylC3
z%C^#5sJF6|>&2!x)oZ&GS2<U#=Q|zR{pQ8*?K=v7Cr*B+onj&Rq=C>)!r|Ke8!mm-
z&KJ=-o@!H-Q(k;$V!^jhw>2kt_)L4lFgGo2vX1-{#-{-uH|HHfy&bJ@bg$fi?Uh^q
zpMle@@7A;VOWbQ&rbo3dz89S{m1C0W?Iz2UcO<4BP-rQhKW*plc&=0XZ`zg3WPkU^
zyL#oFCyJ-G-`X?N|NHFc&9V`RRk@FRr9G~E`OhHma`V|l#Rj`gn@((Ub8)IZGD|IS
zw~Eoi-wP&qoRE3Iyret!;<Ml7Q&-(M`FH;OZEtrtf6Ga?OSe}u+a6PU`DMu0_X02M
z<P7h<nr=4HuU~Z6=3P1y*L-3<f5wr+C$)czPUY>G`z<E2@vgt6UkPSy56YAZjySUE
zY=-iLf3KD9DDZ^*ROU6-WX^L`?K+<OaBaNDhdH;3UQWE@FZynF#iDbG+d@0nem}M>
zEG{rXYxl+}f=_3jp2hHmnMJo?I<H7tiJQxW6?ax05o7quFg3`%cJZYpi%2=3k$L_{
z{y*(D>i-!MBkjL*z1sB0`{C)mZjX;n7yD*-+V*|Bxc}w}Q+O^37eyI(o@$B{DsHIw
z@;La2{U@0Z^Z&M{fNmmPb!E@hEqCo6UAy-^V9U07Z@)#mo1E%3PT^5d*C{%XP}LvB
z@a(HB-#6{QLB4v2ShxQ>e|h0nSC0?NIG>dXD%Y%5Qr7G*;E+$NV3+)**1TSADeJw(
zBJb{hm|*(Zv(Q9WeL~4&uIZne);;*)w93Mkn}5!?Nm;jYtd>~C>}p+<C9L*ityHSe
zuFt2I6}g|f(|F@oSnd1nFVeEXewS0Pyyd<7_u%#})4AqsatWt-Zyx(`%Z~BqiMYKC
z7C&s{SFUd@<xsht{O>|N+wDvPp^wu(UsV@!k+$JIE9O@=&(h+t)91sx*6h>Sqw>ms
z`Ms>NT@3=>In!1@StI}2TXS~Z3*(lb9yiSOBGv~|ST|@ePmYy8qW{>|D80$$vaYFh
zce}@}yShy$MIOqTazEQV-=MPfM$NmUp;Mmnb7$;o?c2PNd##vv@{$++OV8Jx=Zv1l
zo4+~jx?b@2q7C;}_ugex2`|9Yhyri43l}e6l2sg&eNnY#w)*vw+b>j&+_!lwHk+3y
zZ{`@Uc#?(ZW6!hQUdz?iE<3!+dFkmDQECf~^1CiB3)Eh3vnpMsX6*^t{-q2>zslS7
z-pYFwCd>HEQ{I0?Z>ASh^2EGrmeTCcR8v~Y6%u3;9_!ZF78Wo0ao>My{+6@(nRb(x
zA8-him}IttYo>+k(KCh#2}w8keYC!_$6mY^xyWj5$0Uh)l>v9ul6xf<@8<ci>eMOE
z2Lg^yLQD34xZl3TIx>0pr7dR_KYmM(RBmItKV6!itN3)`^~nwr<#jT<t9z>+X-oY1
zeYf0qrzfMsrRYPs+(N~3H2ac7K3`{k_H0kt^{T8)q4--Tb4Ay8={?DmoY?GMbX}W!
zMUbE5yQCNa4wXp^l55ZUANkL4^VZU%({KDaum0Qq`RBs<TVuA!8vd~^uYN95x>`Ky
zSpVOd7T5AkR=kZr-{(5*sgzo8%BR_dIecqYopKYMo#)TeQ2fii&Bk%rk5lLVy$;y8
zXRBen?U|1^O@hQ{c|-<GHWqG_S~W*@B}ed8j~gH2&p%wUGcIw@?%jJE_wVPqF61qp
zye;s`gHOgyj3-v=**Gt_^J>=m_V;?Zl5cgUJ^E&Omy095AmPBgMhD%A4J!Wc!|LWg
z>dg)n_Dy|w<4D-K)rGugUv@q9cALx^ai+TbXOa7aa|`UAo?|FtycQVwt8V$X)2Dx1
zCVtXe^OWo4ZpFumyDY^Uye3YZlVIhsVB4L!TnwN?qA<3Rfd-;cmzf}LQ3H(#AY(!c
z%bA00)qUGTW`}h9Z}D|X0UbH9C_K(0{g}tk@TO{hul1D=*Rls}-@1M8MU&ezbcIv5
z6h|#yqupT8(4%pvvGIki_Uubrb5mYf)gHaJ^!dTswfA2xx_-jd<59<5BQu9PDRNHh
zio`RYde=Oc_x`Bft#4AXRZ;e1_FV1XkqL8irO%~g#2n0;D6Bs1)w|XuJg0XV&%MdR
z__B#3?BP2xjU(^6`V|6qPW9B{eC42Xgzt9$+Td*$wp3e)amQ*M;|Nbv?z$`LcHBsv
zp`LrQ!IvbDC)dU9DPI4&y7S9kvq~NL;2ob$-g-D}))70A8de&#z^nIL#qB~1`Mmyl
z!Zj0r%nrNy#_q<l-+tyn2h;PDvw4F2F6;1`JhD{dmfAGw;<gVCzjYcI-nKHl=9|1=
zeTUHBEq_h2{d!&&B>HbLTETI|%v^w3Yw`^P*;hyBO<wl$yLh-*RPE9&-}Co9^GFQI
zoUQWogk<tGb@eO1uFu@x`99wyVvi%wkKN6Oe|>B!e!5dl@<GJiZE0pnf}XcO3D4o(
zA$qA|di<3yZ=J)N&MqmK_ABbJjJMp^>h7J1Wlle0e>=UsSJt#xS@HyXrfcy(;XPN@
z<>o)Sa^#VB^nNY-t+qRNXe9OiXQ)z8Gq_oHfT3nKr=+DVD}(5K&~3gt*Qbk3Gdx+U
zBUf_Ct>LuN27!0U-)ERz*!e^zdDeyX_I=TJ)jl5$H+W^d+xt<ho$Mx+6eSOxs|OD8
ztyDW#d}!tGn@Nm!@SIwl{&JT5&9|khSDrNe%JmD@eISt2`k$d>Vy@t3Gx3z{36Yz;
z<roh<|FSkZ(yDKMVd=`s5AoUMzcRLd5)86fWbV^D!CaDk!s<D#w<?3~TOPl*l{Y=?
zLwx6(b?efbe`~w!YI>K*#awA&#BfCPNM)bEQ}z#Wnk<PD4OJ|=#QM!|)ZEnqtqia2
zF5M-+Ia%V<kDrEHtCHXKdu_NTmj5hoOXHrKL6yc5)=zwQ$NbuGV}`BU)i0ulf6R~k
z$ToMy-N={gYwf?KO%;7UXW3chX>P_mcTJWS%D;283%kTv=YG1^`)%AWdFk6PR@O`1
zzH1{ab9|<<w0g48+#QGi&R3W-L9AxeWbn~kht3^8|66v6*uR>!HuroIZB9zRw@zLy
z!!!BhYSGg_*zQH=^WRn3zWMIPtEK$&5*m79Pc46^)#ss8@#?sQ1oH~g@4I6_KGPYQ
zy)ORPtlVP@W@#TxuC10`w;*kvHuu7O1Lu4rrgbU(^2X~54lB%CthB33gZb=x-J0U`
z3}tiS(-r2iCs!PL_`ppnvpao?UD<yIPbP<MVa+>y=Bcjz92JY*H*L6*XUZG>Moe6)
zxjwx<J8Pw3#WfD+pG7lctU9^>UQgguc<_YZVNrw4xm@k|t5V0x#j9Fpzbd?Y^JISA
zzK}p(*Jnl^HV0JQwtuqO*lG60f}`r|taXjG^^c@=-FW>^Y~TLr`|Wo-<<hR}RP;Sm
zej-zIar?f92VQ6_;L{JiR9gP=*DEuz?^*r%sZ#e;FGL6?&r6%D+Fcj3#eb{cvBPGL
zaS_GegR+0QPTl?b?Ml~Ww{G9K8Ruat+H=n)vq)u<Wy|WPY!lbsuIUvl*zM=Zac`w7
zL*<X_m;Z_Gu~M1!MBvA+TtP+e$oJE<&u`tk;}%C6kBZ*mb$otV&!#SU_44tzEBSBV
z-4wd_&1_Hgf(uqBZFHGj#r`aen4B%!JuPO^9mBU8kSOdTKocsInLKQQm#v$0t8Zm#
z<}wHUJe{lS)`g1B(p=Ktmcz55XPb5Lb;;GU=KkyFpSnEjdYR#WhKw|hx9grbew*{q
zi#31$+ye>e@A;#i+;{)TyLJxKDNe;X_g?uvyKTB-F3WXamB`A_s|l%x?XG4TDIc0+
zuqyN6ThN(bwrlsz1)ceon^+>|ovFJd<3hjIOBI%%3cFJdc^jn5PF9djoBl|a&2iPu
z$e3G>Y)y~uJq^8>+!$tX^TESFx9~X$#~%O4vaT1sdB?NtUu{pA+4Us(t=<))sy(-K
z&(CO=$dg}IxHa<gF>Sri9#@{#3$BXraDFXjHFb04#79pRqk~?|H*<b=_rU!vsnh4A
zbp49!USYOnSHs1W%M0oS_bs?^;={X$+kOUHTHN03%<O#OX}ziX0?RzPAN}c%qz`S_
zH&u2`+5G$+6J90kF?+*z>69>&tM>1sIxN)_-qqfab^rFR|8M`_^?z3<|DE}t!G3>+
zzxw;!-#>4E-|_l-*MkQirtR1#+jalsB<_xqS|Nj^NlO1pm%P_mF?-YO1GhxBpYW8l
zI4LD|OK)|y?6x)6s-|8&mCYV7>)xyE{H<Qg&aQQ1sa6a!S}xsxYRS7hWej|q-LCv+
z*!m`A=ck&r)630nm*<_IY<zULg=|^6?B>3zYpuoqxGyig^v7h{rkDR2ZvJO@SzdHJ
z^Hbe3^Bof});WbFN>;EmUfKm|0Du|+AgpEiyzSb(=<d$sHjW8<CV3nT72%oW`GCRl
ztY^eO^^H6BUvw$k_;a&!d3K31590)9o1#rCEu=e~*gPbaRrnlO%JykqPHPX{J@3_}
z`~Dkt^eI+-*M91;p2ukQI|~MR3ymkw8J^DxnNP${iRs<mS1;WU-Mi(Y`sG>Aqkm@|
zme`WL#W`!@o{4#BEgqNH?nHd*RsSd$RFUj@-Q=vZ%jCe#liXddPI{F(OI>iw_e_(V
zBRO{@1O8r-P)QA+!%!mC-u*?^+WYGJ+reArnoLpqWTEa>aU+FAxt#9|S3}|CqcQyv
zn<vE{`gG*hmH<zY)kU23rZa>4W=FJg9GH7#0=vx5yUUxuUVIpR*6N|D=DW8xmc>hM
z*DlKrWZu0<PeE`+QOgm#%$Xk26)GEJ&z3vxy{@0HI@$YfcBNR4+`Wg3^OW{XioAI2
z5#N=>c^<ZmSq!fR(}6noKu2<baJc<r{hy4t>u-en{%5#!BYVNRdepmx5%YKK_9!b0
z(tj-XzOwvE%5?8d^E~z5irsPx-(H>BG+kTvN>T4UkI&L-Lb1&|6hwXAWk+dTbDgaF
z_ioR(aQTe3>Ojead(p=ng_Jc}Q}XUj_5UaMHuzt=ZSlW9H|syyGNj&rDK%%-vc;LQ
zE&Z(jHm0uBeKE;U#FPK#cIBqq-{)^OGh59+*U0_sHtSfn@BaTzPP5fF((laAU-xHP
zk6~B*Rwb_^8}7DF)9IPUW!TdbcKna>t>u6Ds-FM-x#>T{lPdd%a#!tN6koT0e|GwR
z2IUKE@oist{XMSB{d$-(PkVRwS50NNx?}w%pN?F7Ea55g^k<sxlOBflTzig+sDIbr
zl<j&FeqG>3rtdPrs&8v^m9|fjaGJR6TTjQXGtP`#a#d&NJN{?j__p#tgY&$d{~79X
z_WzVyJpa)3>tUa6->KLhIg2x3$;6ZSNvB@9aVXqQXtFrU5dJ}Q&c)2~aP#t_xY(_S
zBex#8sdqa2U+-xlKgmavV#<uogQw+f+PT9<w>CRpbnpJ|(isVzOztve-?UaNNMK;y
z#=zVYGXFz=*8DG)ujhY%cKScV#23s97VZ4c@WXwp|1X)Z=YM}r{m*dXOZ_3+RrMF1
zudBa5TmPT?0=}jlzyIn7$!Vl*+BE;ocJqRmbFpuqY@V>7$7GT=zolAe4~yVaa}^(d
z{a$|jCh=4g9Go$~_{TXroncdxN4oj0$(7sA=BYcHUiK7=3oVV1EI7Y4%BSPQavtqs
z)YKr4?yc#U|LCqcxHR*_$@Fa=TmCcfA9{S&xqaKNOm*4%Ru8+so3ex5K0Li+r+7JE
zUnluy*00lRdIEcL3oH5s<BGUl_fNba#An=f<v&A9b;y5)h38}bGwe5u|I_b|mP{C)
zJos>Jr+8~AukMzUHoyDXZfBl2l(DUQ#ii1W{<CwQg&t1MXMZMp`mac~d&HG3f5m*=
zVhe>{yI(zgOz3dwmcS)5CLWn+k-`^cqT4Xnt2J&js=wU%Ti36hutZMxT9VV7r$P6Q
zI;JI^so3@^Vv>K6=K@ZX_xFE1kK5V*tWDe7T0L*ZOrA@d9^X{&c)t8>&l3SFu4fNF
zZ2h`Pr1|KsGaj*XRz=@fp>rm(U+k{8kmoy3Q+0H|ywF%zk7_?gxGq3HYXmKyTs<r9
zDrK-YZU63l^S(WPE9_sQ%oBau;{cOMD1%P+?Q0FDp!x(G)}Flc%HoTAN>|*8z4gkM
z_1Mg`iJsZZ{fm}Pik@^}#>55%D;b$m(QAPYGP{2CAAb4t?WL`upO#iWKHi=WzQ;s<
z=fl45CtsDDuUzrw>v<kXr$}#UuI=sjJ15EW-d*f-Q(e!+651__bY&<aW(T{>ujg%f
zYg9MvxLB&W=4sKV=#vk3Z|l9W?~~Vz0?+)}c6+{p&j5JzQNI1b)YNXTtH~2<&aRs$
zyN9K+N6trH{l^S8yCo@~L*BfvkzIcKZuHHHtarD#x7;k2u@m3rI<vq{hQr`6j~oBW
zuj?*#F+6=!<Nolk(K%~tUhU8=Tl=jQn-6cFxai5Gf<-bsll&it**`S8^q=AR^_c$*
z2SwliXOLV6y5R0V1G@04^q3DPckI|<rML9?9UFg}`5$`kzMHyO;aJ2^OH~h6&zF6M
zv8f`Ar`LD<v6~lnS34AZAxuTthn$Ju^9p~@lXzb<Z+UUmtn-&mbM@|B4~q4Z4TE&A
z<fQg`#DDh`yD05;BX;6C$F!3=73|DA7ByJ>ERE+p`%T{5Vc+E6_VP)0AI{$VEhkwn
z{+*pqZrqIDi!ZG)@AzZ)FYT>%Xg=sZq#tD;z$@B+&x^?Mkz1Vgi|duf0=_uVaS9th
z|2w`kYa6&X<KLbyd}iXl&)XEA_OW?Bx!V83XUqPdU$5JLaIOB&a4dTP<nVVC!HoY5
zEvLQzGt7@I{?EV?zW+}eZ2AsWbmO1MN8Y~v2X{Sfo!hrl_3E|xg*=*n+bhhi-443>
zL`bTXu6xu49ty#hVks5VCVc+3eC)-?dv<M}9J<kawMWl)gRO_y+YA`>Ue8(epn39f
zr6r*8S4;Kkw@#O?D!5e6s+`J_^(K@%<%47+!@MN|+TEA`=+@nOu<gpDeLF8FUD3~H
z^7^*y=(Ku!u2lkO-fnx)7Jh5zJx2wNtp5xjy0R~1mW3C^-1lD<mBn@5gqJ(^Bum((
zsD*Abwxm}kTZSv=&sBK(GlB2(?`YqfIsX}MiOtrV7<YHi(<7(Oba54bX1e6YD0|nv
z&~@J0Wv|4=!@fneE<N+Df73IIwD62*mBa&<!BdslFZ>GEUsRD*9UJeod*_ykN7wFK
zs_k8>667uNUHGVi%A!^6TB+;_xAv?^GKku{t##$yA7cJIXP3C=mgg??T<X3e##=H{
z=E%l>uhX7?nz0}$Lh+$pQ1KS#HJh)O)H<EH7n!xq+-y;3!&%-#R-6(ID|g7`sZL?M
z@=k8+^i>t7eYbAE)Hk<s*}e0t??_kkUOzSA)B&O6X9A8hth+xo`guy6c}nuDS$Yc}
zS(<XM?iKS$*j1~=wrOug<U9*~smRDCYelC?C3h!pZL>;y{!MN1e+Ewf+jZyv_5Ww!
zWWQbhKK`ry&3SHb((PZ{#gxA9DRz*anEfm3rlaY-rOOU|ieB<|)7wb1O~&uSEbh!s
zp3rvSgquymBmcK|<^MHpv;X-0oBWR-{y%>FXP9SOf31G=^;<hEh#9F4j{C4?^M8gz
z{(t8$bFlf(z^gWM`5TTIiQncN*=weMmVeQgfA1M&Q}AC+<M;kZSV4AJREW{R!cx;4
z+jjJ-Nx$99vRT`xXW~RL28(mWx98;%Hzd9?chM`sie|SiUokf^siS{iUip3~S>O)$
zG>-lDv*(-^NZi1)JcvPsc@J#ZV9nm@BUbrsYn1n1)k|*T)Kl6XRv!9u?xE+;6cU&s
zeraud8#T54(e3QrYdOPCUGv`gXz%77pOjO=O1qwEN-#YQw+{HK)Szd#F+JzH+qX~0
z?pdT7wq;M8*wM0fk4#R&?%8?%Cz#XOnU0u$E0<6Ir1xO@TSLhQHx=^D47cm;_<j2G
zdgcBZRb5Y>eRz8Jd}r&KZ-%EcY}|G==mj?PmRuA%*;Lipz`R32ZqBv3jf?I_RYc18
ztIe<fyRn?hm-FY5@asWGT8!p2@O(JC-DXCJ>=LF0vP-It&YAR1e45(TMNJ+{qbGR(
zTyttp$*m(AZY=Lq8Z4g8A+(S7n%wS(k@@=hx^KUnkoTFSE5*{xp=@}tQu)+ue(5kX
znPe6jo-ZraE}2^F@zK9@$a8_6a`c`h6PpyQGPWBf&L~i^>EGMn!QRu5<NYWiar-rW
zseA65FV8>e-qTjSvf=0A&MLz@rv-j)O1U?KwX)y+qy4ujQ7W4w|IV^a_V?ah{<)k{
zG2kty3jgfvyqJ^?o_r$e7G+g-OIO_bJLz)ZmMzo0ujlLOCG6as-7;}r_$-F96U~h3
zeSz0`1U>|Gnat*XEo=YqU2l!@ze^jPZI5K^b}4kvR8gOML};yzMnPSYHv?M%BRO3Q
zs&3-IwcL<i;t}QlWGB6joE);{+E-nx%G}4>r{;#Sg-6_S3#z#>r+H@lLfI9I8k7mP
zKs6RH<8QMqYQWzrU)05b)`+`^(KYGPU>Lj(34QjV_UO^4Tc6z1xSFzS>)mga^R6A(
z6Wu1AEuFK@on1C#QG*U@mu4|)h=~NSBp<qdy5Kwaqq`}7FIIfwu9iKs$}_<K<|YTo
z;6F2dX^{XH^o|uqaJh;w5O4$|MzAlQerUS68|&VWZkx+l!UgVB3b|*jdMnbc)D*;;
UljnG$OJf1wq%MsG{QqwP0Pqk@W&i*H
diff --git a/docs/sgml/dbschema.mysql b/docs/sgml/dbschema.mysql
new file mode 100644
index 000000000..c75c4caa4
--- /dev/null
+++ b/docs/sgml/dbschema.mysql
@@ -0,0 +1,309 @@
+# MySQL dump 7.1
+#
+# Host: localhost Database: bugs
+#--------------------------------------------------------
+# Server version 3.22.32
+
+#
+# Table structure for table 'attachments'
+#
+CREATE TABLE attachments (
+ attach_id mediumint(9) DEFAULT '0' NOT NULL auto_increment,
+ bug_id mediumint(9) DEFAULT '0' NOT NULL,
+ creation_ts timestamp(14),
+ description mediumtext NOT NULL,
+ mimetype mediumtext NOT NULL,
+ ispatch tinyint(4),
+ filename mediumtext NOT NULL,
+ thedata longblob NOT NULL,
+ submitter_id mediumint(9) DEFAULT '0' NOT NULL,
+ PRIMARY KEY (attach_id)
+);
+create index index_41 on attachments (bug_id);
+create index index_42 on attachments (creation_ts);
+
+#
+# Table structure for table 'bugs'
+#
+CREATE TABLE bugs (
+ bug_id mediumint(9) DEFAULT '0' NOT NULL auto_increment,
+ groupset bigint(20) DEFAULT '0' NOT NULL,
+ assigned_to mediumint(9) DEFAULT '0' NOT NULL,
+ bug_file_loc text,
+ bug_severity enum DEFAULT 'blocker' NOT NULL,
+ bug_status enum DEFAULT 'UNCONFIRMED' NOT NULL,
+ creation_ts datetime DEFAULT '0000-00-00 00:00:00' NOT NULL,
+ delta_ts timestamp(14),
+ short_desc mediumtext,
+ op_sys enum DEFAULT 'All' NOT NULL,
+ priority enum DEFAULT 'P1' NOT NULL,
+ product varchar(64) DEFAULT '' NOT NULL,
+ rep_platform enum,
+ reporter mediumint(9) DEFAULT '0' NOT NULL,
+ version varchar(16) DEFAULT '' NOT NULL,
+ component varchar(50) DEFAULT '' NOT NULL,
+ resolution enum DEFAULT '' NOT NULL,
+ target_milestone varchar(20) DEFAULT '---' NOT NULL,
+ qa_contact mediumint(9) DEFAULT '0' NOT NULL,
+ status_whiteboard mediumtext NOT NULL,
+ votes mediumint(9) DEFAULT '0' NOT NULL,
+ keywords mediumtext NOT NULL,
+ lastdiffed datetime DEFAULT '0000-00-00 00:00:00' NOT NULL,
+ everconfirmed tinyint(4) DEFAULT '0' NOT NULL,
+ PRIMARY KEY (bug_id)
+);
+create index index_7 on bugs (assigned_to);
+create index index_8 on bugs (creation_ts);
+create index index_9 on bugs (delta_ts);
+create index index_10 on bugs (bug_severity);
+create index index_11 on bugs (bug_status);
+create index index_12 on bugs (op_sys);
+create index index_13 on bugs (priority);
+create index index_14 on bugs (product);
+create index index_15 on bugs (reporter);
+create index index_16 on bugs (version);
+create index index_17 on bugs (component);
+create index index_18 on bugs (resolution);
+create index index_19 on bugs (target_milestone);
+create index index_20 on bugs (qa_contact);
+create index index_21 on bugs (votes);
+
+#
+# Table structure for table 'bugs_activity'
+#
+CREATE TABLE bugs_activity (
+ bug_id mediumint(9) DEFAULT '0' NOT NULL,
+ who mediumint(9) DEFAULT '0' NOT NULL,
+ bug_when datetime DEFAULT '0000-00-00 00:00:00' NOT NULL,
+ fieldid mediumint(9) DEFAULT '0' NOT NULL,
+ oldvalue tinytext,
+ newvalue tinytext
+);
+create index index_43 on bugs_activity (bug_id);
+create index index_44 on bugs_activity (bug_when);
+create index index_45 on bugs_activity (fieldid);
+
+#
+# Table structure for table 'cc'
+#
+CREATE TABLE cc (
+ bug_id mediumint(9) DEFAULT '0' NOT NULL,
+ who mediumint(9) DEFAULT '0' NOT NULL
+);
+create index index_31 on cc (who);
+create unique index index_32 on cc (bug_id,who);
+
+#
+# Table structure for table 'components'
+#
+CREATE TABLE components (
+ value tinytext,
+ program varchar(64),
+ initialowner tinytext NOT NULL,
+ initialqacontact tinytext NOT NULL,
+ description mediumtext NOT NULL
+);
+
+#
+# Table structure for table 'dependencies'
+#
+CREATE TABLE dependencies (
+ blocked mediumint(9) DEFAULT '0' NOT NULL,
+ dependson mediumint(9) DEFAULT '0' NOT NULL
+);
+create index index_34 on dependencies (blocked);
+create index index_35 on dependencies (dependson);
+
+#
+# Table structure for table 'duplicates'
+#
+CREATE TABLE duplicates (
+ dupe_of mediumint(9) DEFAULT '0' NOT NULL,
+ dupe mediumint(9) DEFAULT '0' NOT NULL,
+ PRIMARY KEY (dupe)
+);
+
+#
+# Table structure for table 'fielddefs'
+#
+CREATE TABLE fielddefs (
+ fieldid mediumint(9) DEFAULT '0' NOT NULL auto_increment,
+ name varchar(64) DEFAULT '' NOT NULL,
+ description mediumtext NOT NULL,
+ mailhead tinyint(4) DEFAULT '0' NOT NULL,
+ sortkey smallint(6) DEFAULT '0' NOT NULL,
+ PRIMARY KEY (fieldid)
+);
+create unique index index_28 on fielddefs (name);
+create index index_29 on fielddefs (sortkey);
+
+#
+# Table structure for table 'groups'
+#
+CREATE TABLE groups (
+ bit bigint(20) DEFAULT '0' NOT NULL,
+ name varchar(255) DEFAULT '' NOT NULL,
+ description text NOT NULL,
+ isbuggroup tinyint(4) DEFAULT '0' NOT NULL,
+ userregexp tinytext NOT NULL
+);
+create unique index index_3 on groups (bit);
+create unique index index_4 on groups (name);
+
+#
+# Table structure for table 'keyworddefs'
+#
+CREATE TABLE keyworddefs (
+ id smallint(6) DEFAULT '0' NOT NULL,
+ name varchar(64) DEFAULT '' NOT NULL,
+ description mediumtext,
+ PRIMARY KEY (id)
+);
+create unique index index_33 on keyworddefs (name);
+
+#
+# Table structure for table 'keywords'
+#
+CREATE TABLE keywords (
+ bug_id mediumint(9) DEFAULT '0' NOT NULL,
+ keywordid smallint(6) DEFAULT '0' NOT NULL
+);
+create index index_39 on keywords (keywordid);
+create unique index index_40 on keywords (bug_id, keywordid);
+
+#
+# Table structure for table 'logincookies'
+#
+CREATE TABLE logincookies (
+ cookie mediumint(9) DEFAULT '0' NOT NULL auto_increment,
+ userid mediumint(9) DEFAULT '0' NOT NULL,
+ cryptpassword varchar(64),
+ hostname varchar(128),
+ lastused timestamp(14),
+ PRIMARY KEY (cookie)
+);
+create index index_30 on logincookies (lastused);
+
+#
+# Table structure for table 'longdescs'
+#
+CREATE TABLE longdescs (
+ bug_id mediumint(9) DEFAULT '0' NOT NULL,
+ who mediumint(9) DEFAULT '0' NOT NULL,
+ bug_when datetime DEFAULT '0000-00-00 00:00:00' NOT NULL,
+ thetext mediumtext
+);
+create index index_22 on longdescs (bug_id);
+create index index_23 on longdescs (bug_when);
+
+#
+# Table structure for table 'milestones'
+#
+CREATE TABLE milestones (
+ value varchar(20) DEFAULT '' NOT NULL,
+ product varchar(64) DEFAULT '' NOT NULL,
+ sortkey smallint(6) DEFAULT '0' NOT NULL,
+);
+create unique index index_24 on milestones (product, value);
+
+#
+# Table structure for table 'namedqueries'
+#
+CREATE TABLE namedqueries (
+ userid mediumint(9) DEFAULT '0' NOT NULL,
+ name varchar(64) DEFAULT '' NOT NULL,
+ watchfordiffs tinyint(4) DEFAULT '0' NOT NULL,
+ linkinfooter tinyint(4) DEFAULT '0' NOT NULL,
+ query mediumtext NOT NULL
+);
+create unique index index_25 on namedqueries (userid, name);
+create index index_26 on namedqueries (watchfordiffs);
+
+#
+# Table structure for table 'products'
+#
+CREATE TABLE products (
+ product varchar(64),
+ description mediumtext,
+ milestoneurl tinytext NOT NULL,
+ disallownew tinyint(4) DEFAULT '0' NOT NULL,
+ votesperuser smallint(6) DEFAULT '0' NOT NULL,
+ maxvotesperbug smallint(6) DEFAULT '10000' NOT NULL,
+ votestoconfirm smallint(6) DEFAULT '0' NOT NULL,
+ defaultmilestone varchar(20) DEFAULT '---' NOT NULL
+);
+
+#
+# Table structure for table 'profiles'
+#
+CREATE TABLE profiles (
+ userid mediumint(9) DEFAULT '0' NOT NULL auto_increment,
+ login_name varchar(255) DEFAULT '' NOT NULL,
+ password varchar(16),
+ cryptpassword varchar(64),
+ realname varchar(255),
+ groupset bigint(20) DEFAULT '0' NOT NULL,
+ emailnotification enum DEFAULT 'ExcludeSelfChanges' NOT NULL,
+ disabledtext mediumtext NOT NULL,
+ newemailtech tinyint(4) DEFAULT '0' NOT NULL,
+ mybugslink tinyint(4) DEFAULT '1' NOT NULL,
+ blessgroupset bigint(20) DEFAULT '0' NOT NULL,
+ PRIMARY KEY (userid)
+);
+create unique index index_27 on profiles (login_name);
+
+#
+# Table structure for table 'profiles_activity'
+#
+CREATE TABLE profiles_activity (
+ userid mediumint(9) DEFAULT '0' NOT NULL,
+ who mediumint(9) DEFAULT '0' NOT NULL,
+ profiles_when datetime DEFAULT '0000-00-00 00:00:00' NOT NULL,
+ fieldid mediumint(9) DEFAULT '0' NOT NULL,
+ oldvalue tinytext,
+ newvalue tinytext
+);
+create index index_0 on profiles_activity (userid);
+create index index_1 on profiles_activity (profiles_when);
+create index index_2 on profiles_activity (fieldid);
+
+#
+# Table structure for table 'shadowlog'
+#
+CREATE TABLE shadowlog (
+ id int(11) DEFAULT '0' NOT NULL auto_increment,
+ ts timestamp(14),
+ reflected tinyint(4) DEFAULT '0' NOT NULL,
+ command mediumtext NOT NULL,
+ PRIMARY KEY (id)
+);
+create index index_38 on shadowlog (reflected);
+
+#
+# Table structure for table 'versions'
+#
+CREATE TABLE versions (
+ value tinytext,
+ program varchar(64) DEFAULT '' NOT NULL
+);
+
+#
+# Table structure for table 'votes'
+#
+CREATE TABLE votes (
+ who mediumint(9) DEFAULT '0' NOT NULL,
+ bug_id mediumint(9) DEFAULT '0' NOT NULL,
+ count smallint(6) DEFAULT '0' NOT NULL
+);
+create index index_5 on votes (who);
+create index index_6 on votes (bug_id);
+
+#
+# Table structure for table 'watch'
+#
+CREATE TABLE watch (
+ watcher mediumint(9) DEFAULT '0' NOT NULL,
+ watched mediumint(9) DEFAULT '0' NOT NULL
+);
+create index index_36 on watch (watched);
+create unique index index_37 on watch (watcher, watched);
diff --git a/docs/sgml/faq.sgml b/docs/sgml/faq.sgml
index b7ca03201..79fa528c4 100644
--- a/docs/sgml/faq.sgml
+++ b/docs/sgml/faq.sgml
@@ -1,4 +1,4 @@
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
+<!-- <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
<appendix id="faq">
<title>The Bugzilla FAQ</title>
@@ -106,13 +106,9 @@
</question>
<answer>
<para>
- There are many, many contributors from around the world maintaining Bugzilla.
- The designated "Maintainer" is Tara Hernandez, with QA support by Matthew Tuck.
- Dan Mosedale and Dawn Endico are employees of Mozilla.org responsible for the
- installation of Bugzilla there, and are very frequent code contributors.
- Terry Weissman originally ported Bugzilla, but "these days, Terry just hangs around
- and heckles." The rest of us are mostly transient developers; Bugzilla suits
- our needs, and we contribute code as we have needs for updates.
+ Bugzilla maintenance has been in a state of flux recently.
+ Please check <ulink
+ url="http://www.mozilla.org/projects/bugzilla/">the Bugzilla Project Page for the latest details. </ulink>
</para>
</answer>
</qandaentry>
@@ -125,18 +121,22 @@
</question>
<answer>
<para>
- A year has gone by, and I <emphasis>still</emphasis> can't find any head-to-head
- comparisons of Bugzilla against other defect-tracking software. However, from my
- 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.
+ A year has gone by, and I <emphasis>still</emphasis> can't
+ find any head-to-head comparisons of Bugzilla against
+ other defect-tracking software. However, from my 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.
</para>
<para>
- If you happen to be a commercial Bugzilla vendor, please step forward with a rebuttal
- so I can include it in the FAQ. We're not in pursuit of Bugzilla ueber alles;
- we simply love having a powerful, open-source tool to get our jobs done.
+ If you happen to be a commercial bug-tracker vendor, please
+ step forward with a rebuttal so I can include it in the
+ FAQ. We're not in pursuit of Bugzilla ueber alles; we
+ simply love having a powerful, open-source tool to get our
+ jobs done.
</para>
</answer>
</qandaentry>
@@ -498,75 +498,21 @@
<qandadiv id="faq_loki">
<title>Loki Bugzilla (AKA Fenris)</title>
- <para>
- <note>
- <para>
- Loki's "Fenris" Bugzilla is based upon the (now ancient) Bugzilla 2.8
- tree, and is no longer actively maintained.
- It works well enough for Loki. Additionally, the major
- differences in Fenris have now been integrated into
- the main source tree of Bugzilla, so there's not much
- reason to go grab the source. I leave this section of the
- FAQ principally for historical interest, but unless Loki has further
- input into Bugzilla's future, it will be deprecated in future versions
- of the Guide.
- </para>
- </note>
- </para>
<qandaentry>
<question>
<para>
- What about Loki Bugzilla?
+ What is Loki Bugzilla (Fenris)?
</para>
</question>
<answer>
<para>
Loki Games has a customized version of Bugzilla available at
- http://fenris.lokigames.com. From that page,
- <blockquote>
- <para>
- You may have noticed that Fenris is a fork from Bugzilla-- our
- patches weren't suitable for integration --and a few people have
- expressed interest in the code. Fenris has one major improvement
- over Bugzilla, and that is individual comments are not appended
- onto a string blob, they are stored as a record in a separate
- table. This allows you to, for instance, separate comments out
- according to privilege levels in case your bug database could
- contain sensitive information not for public eyes. We also provide
- things like email hiding to protect user's privacy, additional
- fields such as 'user_affected' in case someone enters someone
- else's bug, comment editing and deletion, and more conditional
- system variables than Bugzilla does (turn off attachments,
- qacontact, etc.).
- </para>
- </blockquote>
- </para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para>
- Who maintains Fenris (Loki Bugzilla) now?
- </para>
- </question>
- <answer>
- <para>
- Raphael Barrerro <raistlin@lokigames.com>.
- Michael Vance created the initial fork, but no longer
- maintains the project.
+ <ulink url="http://fenris.lokigames.com/">http://fenris.lokigames.com</ulink>. There are some advantages to using Fenris, chief being separation of comments based upon user privacy level, data hiding, forced login for any data retrieval, and some additional fields. Loki has mainted their code, originally a fork from the Bugzilla 2.8 code base, and it is quite a bit different than stock Bugzilla at this point. I recommend you stick with official Bugzilla version &bz-ver; rather than using a fork, but it's up to you.
</para>
</answer>
</qandaentry>
- <qandaentry>
- <question>
- <para>
-
- </para>
- </question>
- </qandaentry>
</qandadiv>
<qandadiv id="faq_phb">
@@ -606,9 +552,6 @@
<para>
Yes! You can find more information elsewhere in "The Bugzilla
Guide" in the "Integration with Third-Party Products" section.
- The section on Perforce isn't very large, but as the maintainer
- of the Guide is charged with Perforce/Bugzilla integration by
- his company, you can expect this section to grow.
</para>
</answer>
</qandaentry>
@@ -677,9 +620,83 @@
progression states, also require adjusting the program logic to
compensate for the change.
</para>
+ <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>
+ </para>
</answer>
</qandaentry>
+
+ <qandaentry>
+ <question>
+ <para>
+ The index.html page doesn't show the footer. It's really annoying to have
+ to go to the querypage just to check my "my bugs" link. How do I get a footer
+ on static HTML pages?
+ </para>
+ </question>
+ <answer>
+ <para>
+ It's possible to get the footer on the static index page using
+ Server Side Includes (SSI). The trick to doing this is making
+ sure that your web server is set up to allow SSI and specifically,
+ the #exec directive. You should also rename <filename>index.html</filename>
+ to <filename>index.shtml</filename>.
+ </para>
+ <para>
+ After you've done all that, you can add the following line to
+ <filename>index.shtml</filename>:
+<programlisting>
+<![CDATA[
+<!--#exec cmd="/usr/bin/perl -e "require 'CGI.pl'; PutFooter();"" -->
+]]>
+</programlisting>
+ </para>
+ <para><note>
+ <para>
+ This line will be replaced with the actual HTML for the footer
+ when the page is requested, so you should put this line where you
+ want the footer to appear.
+ </para>
+ </note></para>
+ <para>
+ Because this method depends on being able to use a #exec directive,
+ and most ISP's will not allow that, there is an alternative method.
+ You could have a small script (such as <filename>api.cgi</filename>)
+ that basically looks like:
+<programlisting>
+<![CDATA[
+#!/usr/bonsaitools/bin/perl -w
+
+require 'globals.pl';
+
+if ($::FORM{sub} eq 'PutFooter') {
+ PutFooter();
+} else {
+ die 'api.cgi was incorrectly called';
+}
+]]>
+</programlisting>
+ and then put this line in <filename>index.shtml</filename>.
+<programlisting>
+<![CDATA[
+<!--#include virtual="api.cgi?sub=PutFooter"-->
+]]>
+</programlisting>
+ </para>
+ <para> <note>
+ <para>
+ This still requires being able to use Server Side Includes, if
+ this simply will not work for you, see <ulink
+ url="http://bugzilla.mozilla.org/show_bug.cgi?id=80183">bug 80183</ulink>
+ for a third option.
+ </para>
+ </note></para>
+ </answer>
+ </qandaentry>
<qandaentry>
<question>
<para>
@@ -813,21 +830,6 @@
</answer>
</qandaentry>
- <qandaentry>
- <question>
- <para>
- Does Bugzilla allow fields to be added, changed or deleted? If I want to
- customize the bug submission form to meet our needs, can I do that using our
- terminology?
- </para>
- </question>
- <answer>
- <para>
- Yes.
- </para>
- </answer>
- </qandaentry>
-
<qandaentry>
<question>
<para>
@@ -1042,8 +1044,7 @@
<para>
Check <ulink url="http://www.mozilla.org/projects/bugzilla/">
http://www.mozilla.org/projects/bugzilla/</ulink> for details.
- Once you download it, untar it, read the README and
- the Bugzilla Guide.
+ Once you download it, untar it, read the Bugzilla Guide.
</para>
</answer>
</qandaentry>
@@ -1084,7 +1085,7 @@
<question>
<para>
How do I completely disable MySQL security if it's giving me problems
- (I've followed the instructions in the README!)?
+ (I've followed the instructions in the installation section of this guide!)?
</para>
</question>
<answer>
@@ -1108,7 +1109,7 @@
The Bugzilla code has not undergone a complete security audit.
It is recommended that you closely examine permissions on your Bugzilla
installation, and follow the recommended security guidelines found
- in the README and in The Bugzilla Guide.
+ in The Bugzilla Guide.
</para>
</answer>
</qandaentry>
@@ -1231,20 +1232,11 @@
<para>
If you are using an alternate Mail Transport Agent (MTA other than
sendmail), make sure the options given in the "processmail" script for all
- instances of "sendmail" are correct for your MTA. If you are using Sendmail,
- you may wish to delete the "-ODeliveryMode=deferred" option in the
- "processmail" script for every invocation of "sendmail". (Be sure and leave
- the "-t" option, though!)
- </para>
- <para>
- A better alternative is to change the "-O" option to
- "-ODeliveryMode=background". This prevents Sendmail from hanging your
- Bugzilla Perl processes if the domain to which it must send mail
- is unavailable.
+ instances of "sendmail" are correct for your MTA.
</para>
<para>
- This is now a configurable parameter called "sendmailnow", available
- from editparams.cgi.
+ If you are using Sendmail, try enabling "sendmailnow" in editparams.cgi.
+ If you are using Postfix, you will also need to enable <quote>sendmailnow</quote>.
</para>
</answer>
</qandaentry>
@@ -1325,12 +1317,21 @@
</question>
<answer>
<para>
- Run the "sanity check" utility (./sanitycheck.cgi in the bugzilla_home
- directory) to see! If it all comes back, you're 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...
+ Run the <quote>sanity check</quote> utility
+ (<filename>./sanitycheck.cgi</filename> in the
+ Bugzilla_home directory) from your web browser to see! If
+ it finishes without errors, you're
+ <emphasis>probably</emphasis> 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.
</para>
</answer>
</qandaentry>
@@ -1438,10 +1439,12 @@
</question>
<answer>
<para>
- Delete everything from $BUZILLA_HOME/shadow. Bugzilla creates shadow
- files there, with each filename corresponding to a
- bug number. Also be sure to run syncshadowdb to make sure, if you are using
- a shadow database, that the shadow database is current.
+ This should only happen with Bugzilla &bz-ver; if you are
+ using the <quote>shadow database</quote> feature, and your
+ shadow database is out of sync. Try running
+ <filename>syncshadowdb</filename>
+ <option>-syncall</option> to make sure your shadow
+ database is in synch with your primary database.
</para>
</answer>
</qandaentry>
@@ -1762,14 +1765,14 @@ A: Sure! Here ya go!
</question>
<answer>
<para>
- Try <ulink url="http://bugzilla.mozilla.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Webtools&component=Bugzilla">
+ Try <ulink url="http://bugzilla.mozilla.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Bugzilla">
this link</ulink> to view current bugs or requests for
enhancement for Bugzilla.
</para>
<para>
- You can view bugs marked for 2.14 release
- <ulink url="http://bugzilla.mozilla.org/buglist.cgi?product=Webtools&component=Bugzilla&target_milestone=Bugzilla+2.14">here</ulink>.
- This list includes bugs for the 2.14 release that have already
+ You can view bugs marked for 2.16 release
+ <ulink url="http://bugzilla.mozilla.org/buglist.cgi?product=Bugzilla&target_milestone=Bugzilla+2.16">here</ulink>.
+ This list includes bugs for the 2.16 release that have already
been fixed and checked into CVS. Please consult the
<ulink url="http://www.mozilla.org/projects/bugzilla/">
Bugzilla Project Page</ulink> for details on how to
@@ -1810,8 +1813,9 @@ A: Sure! Here ya go!
<orderedlist>
<listitem>
<para>
- Enter a bug into bugzilla.mozilla.org for the "Webtools" product,
- "Bugzilla" component.
+ Enter a bug into bugzilla.mozilla.org for the <quote><ulink
+ url="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla">Bugzilla</ulink></quote>
+ product.
</para>
</listitem>
<listitem>
@@ -1864,17 +1868,20 @@ A: Sure! Here ya go!
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
-sgml-omittag:t
-sgml-shorttag:t
-sgml-namecase-general:t
-sgml-general-insert-case:lower
-sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
-sgml-indent-step:2
-sgml-indent-data:t
-sgml-parent-document:nil
+sgml-auto-insert-required-elements:t
+sgml-balanced-tag-edit:t
sgml-exposed-tags:nil
+sgml-general-insert-case:lower
+sgml-indent-data:t
+sgml-indent-step:2
sgml-local-catalogs:nil
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-shorttag:t
+sgml-tag-region-if-active:t
End:
-->
diff --git a/docs/sgml/future.sgml b/docs/sgml/future.sgml
index 4cdf9e6f8..54f191349 100644
--- a/docs/sgml/future.sgml
+++ b/docs/sgml/future.sgml
@@ -3,326 +3,617 @@
<chapter id="future">
<title>The Future of Bugzilla</title>
<synopsis>Bugzilla's Future. Much of this is the present, now.</synopsis>
- <section id="spamlite">
- <title>Reducing Spam</title>
- <para><literallayout>
-Those who use Bugzilla frequently are probably used to notification spam
-- unwanted or unnecessary notifications. A number of proposals have
-been put forward to attempt to reduce this.
-
-1. Reduce CC Spam
-
-Some of you probably know me as that guy who CCs on heaps and heaps of
-bugs. Just as you get a lot of CC changes from me, so do I get a lot
-from others. Why should CC changes send out email notifications?
-
-It's not necessarily the best idea to just remove the CC spam, there are
-other issues too, like the difficulty of adding to large CC fields.
-
-For these reasons and more, an RFE for a per user "BCC" facility exists
-that people could use to silently and privately track bugs, in a similar
-way to voting today, but applying to an unlimited number of bugs. See
-"http://bugzilla.mozilla.org/show_bug.cgi?id=7345".
-
-2. Bulk Changes
-
-You know the drill - a large milestone change, a component movement,
-whatever, and lots of notifications are generated. If there's enough
-maybe you'll just go delete, delete, delete, whoops, there goes another
-notification that wasn't from the bulk change you missed.
-
-Shouldn't bulk changes send out one notification? A proposal for this
-is at "http://bugzilla.mozilla.org/show_bug.cgi?id=26943".
-
-3. Configurable Notification Criteria
-
-It would be good if you could choose what you want to receive. There
-are two parts to this.
-
-(a) Choose a selection of bugs you're interested in. This would be
-similar to CC except you let the set be computed from selection criteria
-rather than limited to the bugs your name is on. There is currently a
-limited version of this in the bugzilla preferences, ie "all qualifying
-bugs"/"all qualifying bugs except the ones I change"/"only those bugs
-which I am listed on the cc line".
-(b) Choose what changes will trigger a notification for the bugs you are
-watching. With this, you could choose whether you want to receive cc,
-dependency and keyword changes, for example.
-
-Both of these proposals live at
-"http://bugzilla.mozilla.org/show_bug.cgi?id=14137".
-Note that they also live at
-"http://bugzilla.mozilla.org/show_bug.cgi?id=17464", and the change
-has been checked in. This is fixed with Bugzilla 2.12 and is no longer
-an issue. Woo-Hoo!
-</literallayout></para>
- </section>
-
- <section id="searching">
- <title>Better Searching</title>
- <para><literallayout>
-Current searching tools in Bugzilla include the querying mechanism,
-special summary reports and dependency trees. This message is about new
-facilities.
-
-1. General Summary Reports
-
-For some time now it has been apparent to me that the query bug list
-leaves a little to be desired in its linear nature. There is a need to
-have categorised subsets, and counts of each category. If you don't
-believe me, how about these facilities already in place or which people
-have asked for:
-
-Most Doomed Reports - Categorised On Assignee, Shows and Counts Number
-of Bugs For Each Assignee
-Bug #15806 (Most Voted For Bugs) - Categorised On Product, Shows Bugs
-Voters Most Want Fixed
-Bug #9789 (BugAThon Tracking Page) - Categorised On Developer (Subset),
-Counts Number of Bugs
-Bug #9409 and #9411 - The desire to be able to report on more subsets.
-
-Hopefully you can see the gist of what is desired here. It's a general
-reporting mechanism.
-
-This mechanism lets you choose the subset of bugs to operate on (like
-query), let's you categorise them, possibly along with subcategories and
-counts the number of bugs within each category. It might or might not
-show the actual bugs themselves, and it might limit the number of bugs
-within a category, or categories to report on.
-
-I'm further sure that many applications of this mechanism would only be
-recognised once it was implemented.
-
-The general summary reports bug is at
-"http://bugzilla.mozilla.org/show_bug.cgi?id=12282".
-
-2. Related Bugs
-
-It would be nice to have a field where you could enter other bugs
-related to the current bug - it would be handy for navigation and
-possibly even finding duplicates. See
-"http://bugzilla.mozilla.org/show_bug.cgi?id=12286".
-
-3. Column Specification Support
-
-Currently query seems to get what columns to report on from whatever the
-user last used. This doesn't work well for "prepackaged queries", where
-you followed a link. You can probably add a column by specifying a sort
-column, but this is difficult and suboptimal.
-
-Furthermore, I find that when I want to add a column to a query, it's
-usually a one off and I would prefer it to go away for the next query.
-Hence, it would be nice to specify the columns that appear on the query
-(and general summary report) pages. The default query mechanism should
-be able to let you specify your default columns.
-
-This proposal lives at
-"http://bugzilla.mozilla.org/show_bug.cgi?id=12284".
-</literallayout></para>
- </section>
-
- <section id="trackingbugs">
- <title>Description Flags and Tracking Bugs</title>
- <para><literallayout>
-Since I last posted on this issue, we now have "keywords" that solve
-many of the issues of description and status whiteboard keywords. We
-have seen a migration towards keywords, but there is still further to
-go.
-
-Description ( + Status Whiteboard ) Keywords
---------------------------------------------
-
-Some description keywords remain. I'd like to hear what reasons, other
-than time, there are for these staying as they are. I'm suspecting many
-are not really being used. Hopefully we can totally remove these
-eventually.
-
-Tracking Bugs
--------------
-
-When I suggested keywords, I did so to get rid of tracking bugs too,
-though we've had less success on that front.
-
-There are many disadvantages to tracking bugs.
-
-- They can pollute bugs counts, and you must make sure you exclude
-them. I believe the meta keyword might be used for this purpose.
-- They have an assignee but there is nothing to fix, and that person can
-get whined at by Bugzilla.
-- It would be better to craft your own "dependency tree" rather than
-rely on a fixed hierachy in the bug system.
-- In creating a nice little hierachy, many bugs duplicate information
-that should be available in other ways, eg
-"http://bugzilla.mozilla.org/show_bug.cgi?id=12833" which is
-about beta 1 networking issues. These could fall behind the actual
-data. What tracking bugs are good for, ad hoc lists, is what keywords
-are better for.
-- An automatically generated dependency structure between one "tracking
-bug" and another would be better than a manual one, since it gives exact
-rather than manually set up classifications.
-
-Probably the only feature preventing tracking bugs being replaced is the
-dependency tree. The quintessential tracking bug seems to be bug #7229
-"chofmann's watch list", which probably has about a couple of hundred
-bugs at various levels, which allows a nice visualisation.
-
-Before keywords can replace tracking bugs better visualisation is going
-to be required. General summary reports and dependency forests of a bug
-list ("http://bugzilla.mozilla.org/show_bug.cgi?id=12992") could both
-help, but neither solves the problem totally. Perhaps keywords within
-keywords would help here. In any case, I'm still thinking about this
-one.
-
-Some tracking bugs could definitely be turned into keywords immediately
-though, and I'll point the finger at
-"http://bugzilla.mozilla.org/show_bug.cgi?id=7954" here since that's
-what came to mind first.
-</literallayout></para>
- </section>
-
- <section id="bugprobs">
- <title>Bug Issues</title>
- <para><literallayout>
-1. Inline Bug Changes
-
-Why do I see so many "moving to M5" and "reassigning to blahblah"
-messages, and in other circumstances none are entered? Why aren't these
-automatically generated? A comment should be only necessary when there
-is something to add, and if I'm not interested in this sort of
-information, I should be able to hide it.
-
-At the moment we're in a hybrid world where we don't get everything, but
-we can't get rid of the bug change "messages" either. Furthermore,
-"View Bug Activity" requires me to manually cross reference events on
-another page, rather than being able to visually see the chronological
-order. Shouldn't I be able to see all the information on one page?
-
-A proposal to allow bugs to be shown either way is at
-"http://bugzilla.mozilla.org/show_bug.cgi?id=11368".
-
-2. Hard Wrapping Comments
-
-One thing that annoys me is the fact that comments are "hard wrapped" to
-a certain column width. This is a mistake Internet Mail and News has
-made, unlike every word processor in existence, and as a consequence,
-Usenet suffers to this day from bad software. Why has Bugzilla repeated
-the problem?
-
-Hard wrapping to a certain column width is open to abuse (see old
-Mozilla browsers that didn't wrap properly, resulting in many ugly bug
-reports we have to read to this day), and furthermore doesn't expand to
-fill greater screen sizes. I'm also under the impression the current
-hard wrap uses a non-standard HTML facility. See
-"http://bugzilla.mozilla.org/show_bug.cgi?id=11901".
-
-3. REMIND and LATER Are Evil
-
-I really hate REMIND and LATER. Not because they mean something
-won't be implemented, but because they aren't the best solutions.
-
-Why are they bad? Well, basically because they are not resolved, yet
-they are marked as such. Hence queries have to be well crafted to
-include them.
-
-LATER, according to Bugzilla, means it won't be done this release.
-There is a better mechanism of doing this, that is assigning to
-nobody@mozilla.org and making the milestone blank. It's more likely to
-appear in a casual query, and it doesn't resolve the bug.
-
-REMIND, according to Bugzilla, means it might still be implemented this
-release. Well, why not just move it to a later milestone then? You're
-a lot less likely to forget it. If it's really needed, a keyword would
-be better.
-
-Some people can't use blank milestones to mean an untargetted milestone,
-since they use this to assess new bugs that have no target. Hence, it
-would be nice to distinguish between bugs that have not yet been
-considered, and those that really are not assigned to any milestone in
-the future (assumedly beyond).
-
-All this is covered at
-"http://bugzilla.mozilla.org/show_bug.cgi?id=13534".
-
-4. Create An Enhancement Field
-
-Currently enhancement is an option in severity. This means that
-important enhancements (like for example, POP3 support) are not properly
-distinguished as such, because they need a proper severity. This
-dilutes the meaning of enhancement.
-
-If enhancement was separated, we could properly see what was an
-enhancement. See "http://bugzilla.mozilla.org/show_bug.cgi?id=9412". I
-see keywords like [RFE] and [FEATURE] that seem to be compensating for
-this problem.
-</literallayout></para>
- </section>
-
- <section id="dbaseintegrity">
- <title>Database Integrity</title>
- <para><literallayout>
-Bugzilla could be more proactive in detecting suboptimal situations and
-prevent them or whine about them.
-
-1. Bugzilla Crime #1: Marking A Bug Fixed With Unresolved Dependencies
-
-It can't be marked fixed with unresolved dependencies. Either mark it
-INVALID (tracking bugs), fix the dependencies at the same time, or
-resolve the blockers.
-
-See "http://bugzilla.mozilla.org/show_bug.cgi?id=24496".
-
-2. Keyword Restrictions
+ <para>
+ Bugzilla's future is a constantly-changing thing, as various developers
+ <quote>scratch an itch</quote> when it comes to functionality.
+ Thus this section is very malleable, subject to change without notice, etc.
+ You'll probably also notice the lack of formatting. I apologize that it's
+ not quite as readable as the rest of the Guide.
+ </para>
+ <para>
+ <literallayout>
+ Bugzilla Blue Sky
-Some keywords should only apply in certain circumstances, eg beta1 =>
-Milestone <
-M14, css1 => Component = Style System are possibilities. See
-"http://bugzilla.mozilla.org/show_bug.cgi?id=26940".
+Customisability
+
+ One of the major stumbling blocks of Bugzilla has been that it is too
+ rigid and does not adapt itself well enough to the needs of an
+ organisation. This has led to organisations making changes to the
+ Bugzilla code that need to be redone each new version of Bugzilla.
+ Bugzilla should attempt to move away from this to a world where this
+ doesn't need to occur.
+
+ Most of the subsections in this section are currently explicit design
+ goals for the "Bugzilla 3" rewrite. This does not necessarily mean
+ that they will not occur before them in Bugzilla 2, but most are
+ significant undertakings.
+
+ Field Customisation
+
+ Many installations wish to customise the fields that appear on bug
+ reports. Current versions of Bugzilla offer limited
+ customisability. In particular, some fields can be turned off.
+
+ However, many administrators wish to add their own fields, and rename
+ or otherwise modify existing fields. An architecture that supports
+ this would be extraordinarily useful.
+
+ Indeed, many fields work similarly and could be abstracted into "field
+ types", so that an administrator need write little or no code to
+ support the new fields they desire.
+
+ Possible field types include text (eg status whiteboard), numbers,
+ dates (eg report time), accounts (eg reporter, qa, cc), inter-bug
+ relationships (dependencies, duplicates), option groups (platform, os,
+ severity, priority, target milestone, version) etc.
+
+ Ideally an administrator could configure their fields through a
+ Bugzilla interface that requires no code to be added. However, it is
+ highly unlikely this ideal will never be met, and in a similar way
+ that office applications have scripting languages, Bugzilla should
+ allow new field types to be written.
+
+ Similarly, a common desire is for resolutions to be added or removed.
+
+ Allocations
+
+ ?
+
+ Option Groups
+
+ ?
+
+ Relations
+
+ ?
+
+ Database Integrity
+
+ Furthermore, it is desirable for administrators to be able to specify
+ rules that must or should apply between the fields on a bug report.
+
+ For example, you might wish to specify that a bug with status ASSIGNED
+ must have a target milestone field that that is not untargetted. Or
+ that a bug with a certain number of votes should get ASSIGNED. Or
+ that the QA contact must be different from the assignee.
+
+ "Must" relationships could be implemented by refusing to make changes
+ that violate the relationships, or alternatively, automatically
+ updating certain fields in order to satisfy the criteria. Which
+ occurs should be up to the administrator.
+
+ "Should" relationships could be implemented by a combination of
+ emitting warnings on the process bug page, the same on notification
+ mails, or emitting periodic whine mails about the situation. Again,
+ which occurs should be up to the administrator.
+
+ It should also be possible for whine mails to be emitted for "must"
+ relationships, as they might become violated through direct database
+ access, Bugzilla bugs, or because they were there before the
+ relationship was enforced.
+
+ As well as implementing intra-bug constraints, it would be useful to
+ create inter-bug constraints. For example, a bug that is dependent on
+ another bug should not have an earlier milestone or greater priority
+ than that bug.
+
+ Database Adaptability
+
+ Often an administrator desires that fields adapt to the values of
+ other fields. For example, the value of a field might determine the
+ possible values of another field or even whether it appears (whether
+ it is "applicable").
+
+ Limited adaptability is present in Bugzilla 2, and only on the
+ "Product" field:
+ * The possible values of the target milestone, version and component
+ fields depend on the product.
+ * UNCONFIRMED can be turned off for specific products.
+ * Voting can be configured differently or turned off for different
+ products, and there is a separate user vote limits for each
+ product.
-3. Whine About Old Votes
+ It would be good if more adaptability was present, both in terms of
+ all fields relying on the product, as well as the ability to adapt
+ based on the value of all fields.
+
+ Example ???
-Old votes can just sit on resolved bugs. This is problematic with
-duplicates especially. Automatic transferral/removal is not
-appropriate since bugs can be reopened, but a whining solution might
-work. See "http://bugzilla.mozilla.org/show_bug.cgi?id=27553".
+ General adaptability raises the issue of circular references between
+ fields causing problems. One possible solution to this is to place
+ the fields in a total ordering and require a field refer only to the
+ previous fields.
-4. Whine And Warn About Milestone Mismatches
+ In Bugzilla 2, changing the product of a bug meant a second page would
+ appear that allowed you to choose a new milestone, component and
+ version, as those fields adapted themselves to the new product. This
+ page could be generalised to support all instances where:
+ * a field value must or might be changed because the possible values
+ have changed
+ * is going to drop off because it it is no longer applicable, and
+ this should be confirmed
+ * must be specified because it is suddenly applicable, and the
+ default value, if one exists, might not be acceptable
-Here's a fun one. Bug X (M17) depends on Bug Y (M15). Bug Y gets moved
-out to M19. The notification to the assignee of Bug X gets ignored (of
-course) and Bug X is now due to be fixed before one of its blockers.
+ Database Independence
-Warnings about this when it is detected as well as whining about it in
-email would help bring these issues to the attention of people sooner.
+ Currently Bugzilla only runs on the MySQL database. It would be
+ desirable for Bugzilla to run on other databases, because:
+ * Organisations may have existing database products they use and
+ would prefer to run a homogenous environment.
+ * Databases each have their own shortcomings, including MySQL. An
+ administrator might choose a database that would work better with
+ their Bugzilla.
+
+ This raises the possibility that we could use features that are only
+ present in some databases, by appropriately falling back. For
+ example, in the MySQL world, we live without:
+ * record-level locking, instead we use table-level locking
+ * referential and record constraints, instead we checking code
+ * subselects, instead we use multiple queries and redundant "caches"
+
+ Multiple Front Ends
+
+ Currently Bugzilla is manipulated via the Web, and notifies via
+ E-Mail. It would be desirable for Bugzilla to easily support various
+ front ends.
+
+ There is no reason that Bugzilla could not be controlled via a whole
+ range of front ends, including Web, E-Mail, IRC, ICQ, etc, and
+ similarly for how it notifies. It's also possible that we could
+ introduce a special Bugzilla client that uses its own protocol, for
+ maximum user productivity.
+
+ Indeed a request reply might be returned via a totally different
+ transport method than was use to submit the request.
+
+Internationalisation
+
+ Bugzilla currently supports only English. All of the field names,
+ user instructions, etc are written in English. It would be desirable
+ to allow "language packs" so Bugzilla can be easily used in
+ non-English speaking locales.
+
+ To a degree field customisation supports this, because administrators
+ could specify their own fields names anyway. However, there will
+ always be some basic facilities not covered by this, and it is
+ desirable that the administrator's interface also is
+ internationalisable.
+
+Better Searching
+
+ General Summary Reports
+
+ Sometimes, the normal querying page leaves a lot to be desired. There
+ are other facilities already in place or which people have asked for:
+
+ Most Doomed Reports - All Bugs or All Bugs In A Product, Categorised
+ On Assignee, Shows and Counts Number of Bugs For Each Assignee
+ Most Voted For Bugs - All Bugs, Categorised On Product, Shows Top Ten
+ Bugs Voters Most Want Fixed
+ Number of Open Bugs For An Assignee - Bug List, Categorised On
+ Developers, Counts Number of Bugs In Category
+
+ The important thing to realise is that people want categorised reports
+ on all sorts of things - a general summary report.
+
+ In a categorised report, you choose the subset of bugs you wish to
+ operate on (similar to how you would specify a query), and then
+ categorise them on one or more fields.
+
+ For each category you display the count of the number of things in
+ that category. You can optionally display the bugs themselves, or
+ leave them out, just showing the counts. And you can optionally limit
+ the number of things (bugs or subcategories) that display in each
+ category.
+
+ Such a mechanism would let you do all of the above and more.
+ Applications of this mechanism would only be recognised once it was
+ implemented.
+
+ Related Bugs
+
+ It would be nice to have a field where you could enter other bugs
+ related to the current bug. It would be handy for navigation and
+ possibly even finding duplicates.
+
+ Column Specification Support
+
+ Currently bug lists use the columns that you last used. This doesn't
+ work well for "prepackaged queries", where you followed a link. You
+ can probably add a column by specifying a sort column, but this is
+ difficult and suboptimal.
+
+ Furthermore, I find that when I want to add a column to a bug list,
+ it's usually a one off and I would prefer it to go away for the next
+ query. Hence, it would be nice to specify the columns that appear on
+ the bug list (and general summary report) pages. The default query
+ mechanism should be able to let you specify your default columns.
+
+ Advanced Querying Redesign
+
+ ?
+
+Keywords
+
+ People have a need to apply tags to bugs. In the beginning, people
+ placed designators in the summary and status whiteboard. However,
+ these fields were not designed for that, and so there were many flaws
+ with this system:
+ * They pollute the field with information that was never intended to
+ be present.
+ * Removing them with a bulk change is a difficult problem that has
+ too many pitfalls to implement.
+ * You can easily get the capitalisation wrong.
+
+ Then dependencies were introduced (when?), and people realised that
+ they could use them for "tracking bugs". Again, dependencies were not
+ designed for that, and so there were more flaws, albeit different
+ ones, including:
+ * They aren't really bugs, so it's difficult to distinguish issues
+ from bugs.
+ * They can pollute bugs counts, and you must somehow exclude them
+ from queries.
+ * There is a whole lot of useless information on them. They have an
+ assignee but there is nothing to fix, and that person can get
+ whined at by Bugzilla. They have target milestones which must be
+ manually maintained. And so on.
+
+ Finally, keywords were introduced (when?) for this purpose to remove
+ the need for these two systems. Unfortunately, the simple keywords
+ implementation was itself lacking in certain features provided by the
+ two previous systems, and has remained almost unchanged since its
+ inception. Furthermore, it could not be forseen that in large
+ installations, the sheer number of keywords could become unwieldly and
+ could lead to a movement back to the other systems.
+
+ The keywords system was the right idea, however, and it remains so.
+ Fixing the keywords system is one of the most important Bugzilla
+ issues.
+
+ Bringing Keywords Up To Par
+
+ For the most part, keywords are very good at what they do. It is easy
+ to add and remove them (unlike summary/whiteboard designators), we can
+ simply see what issues are present on a bug (unlike tracking bugs),
+ and we do not confuse bugs with issues (unlike tracking bugs).
+
+ However, there are still some "regressions" in the keyword system over
+ previous systems:
+ * Users wish to view the "dependency forest" of a keyword. While a
+ dependency tree is of one bug, a dependency forest is of a bug
+ list, and consists of a dependency tree for each member of the bug
+ list. Users can work around this with tracking bugs by creating a
+ tracking bug and viewing the dependency tree of that tracking bug.
+ * Users wish to specify the keywords that initially apply to a bug,
+ but instead they must edit the bug once it has already been
+ submitted. They can work around this with summary designators,
+ since they specify the summary at reporting time.
+ * Users wish to store or share a bug list that contains a keywords
+ column. Hence they wish to be able to specify what columns appear
+ in the bug list URL, as mentioned earlier. They can work around
+ this using summary designators, since almost all bug lists have a
+ summary column.
+ * Users wish to be able to view keywords on a bug list. However
+ often they are only interested in a small number of keywords.
+ Having a bug list with a keywords column means that all keywords
+ will appear on a bug list. This can take a substantial amount of
+ space where a bug has a lot of keywords, since the table columns
+ in Bugzilla adjust to the largest cell in that column. Hence
+ users wish to be able to specify which keywords should appear in
+ the bug list. In a very real sense, each keyword is a field unto
+ itself. Users can work around this by using summary designators,
+ since they keywords will share the space in the summary column.
+ * Users wish to know when bugs with a specific issue are resolved.
+ Hence they wish to be able to receive notifications on all the
+ bugs with a specific keyword. The introduction a generic watching
+ facility (also for things like watching all bugs in a component)
+ would achieve this. Users can work around this by using tracking
+ bugs, as dependencies have an existing way of detecting fixes to
+ bug a bug was blocked by.
+
+ Dealing With The Keyword Overload
+
+ At the time of writing, the mozilla.org installation has approximately
+ 100 keywords, and many more would be in use if the keywords system
+ didn't have the problems it does.
+
+ Such a large number of keywords introduces logistical problems:
+ * It must be easy for someone to learn what a keyword means. If a
+ keyword is buried within a lot of other keywords, it can be
+ difficult to find.
+ * It must be easy to see what keywords are on a bug. If the number
+ of keywords is large, then this can be difficult.
+
+ These lead some people to feel that there are "too many keywords".
+
+ These problems are not without solutions however. It is harder to
+ find a list of designators or tracking bugs than it is a list of
+ keywords.
+
+ The essential problem is it needs to be easy to find the keywords
+ we're interested in through the mass of keywords.
+
+ Keyword Applicability
+
+ As has been previously mentioned, it is desirable for fields to be
+ able to adapt to the values of other fields. This is certainly true
+ for keywords. Many keywords are simply not relevant because of the
+ bugs product, component, etc.
+
+ Hence, by introducing keyword applicability, and not displaying
+ keywords that are not relevant to the current bug, or clearly
+ separating them, we can make the keyword overload problem less
+ significant.
+
+ Currently when you click on "keywords" on a bug, you get a list of all
+ bugs. It would be desirable to introduce a list of keywords tailored
+ to a specific bug, that reports, in order:
+ * the keywords currently on the bug
+ * the keywords not currently on the bug, but applicable to the bug
+ * optionally, the keywords not applicable to the bug
+
+ This essentially orders the keywords into three groups, where each
+ group is more important than the previous, and therefore appears
+ closer to the top.
+
+ Keyword Grouping & Ordering
+
+ We could further enhance both the global and bug specific keyword list
+ by grouping keywords. We should always have a "flat" view of
+ keywords, but other ways of viewing the keywords would be useful too.
+
+ If keyword applicability was implemented, we could group keywords
+ based on their "applicability condition". Keywords that apply to all
+ bugs could be separated from keywords that apply to a specific
+ product, both on the global keyword list and the keyword list of a bug
+ that is in that product.
+
+ We could specify groups of our own. For example, many keywords are in
+ a mutually exclusive group, essentially like radio buttons in a user
+ interface. This creates a natural grouping, although other groupings
+ occur (which depends on your keywords).
+
+ It is possible that we could use collapsing/expanding operations on
+ "twisties" to only should the groups we are interested in.
+
+ And instead of grouping keywords, we could order them on some metric
+ of usefulness, such as:
+ * when the keyword was last added to a bug
+ * how many bugs the keyword is on
+ * how many open bugs the keyword is on
+
+ Opting Out Of Keywords
+
+ Not all people are going to care about all keywords. Therefore it
+ makes sense that you may wish to specify which keywords you are
+ interested in, either on the bug page, or on notifications.
+
+ Other keywords will therefore not bother users who are not interested
+ in them.
+
+ Keyword Security
+
+ Currently all keywords are available and editable to all people with
+ edit bugs access. This situation is clearly suboptimal.
+
+ Although relying on good behaviour for people to not do what they
+ shouldn't works reasonably well on the mozilla.org, it is better to
+ enforce that behaviour - it can be breached through malice, accident
+ or ignorance.
+
+ And in the situation where it is desirable for the presence or absence
+ of a keyword not to be revealed, organisations either need to be
+ content with the divulgence, or not use keywords at all.
+
+ In the situation where they choose to divulge, introducing the ability
+ to restrict who can see the keyword would also reduce keyword
+ overload.
-Note that this would be less of a problem if we didn't have so many
-tracking bugs since they aren't updated that often and often have this
-problem.
+ Personal Keywords
-See "http://bugzilla.mozilla.org/show_bug.cgi?id=16743".
-</literallayout></para>
- </section>
+ Keywords join together a set of bugs which would otherwise be
+ unrelated in the bug system.
+
+ We allow users to store their own queries. However we don't allow
+ them to store their own keywords on a bug. This reduces the
+ usefulness of personal queries, since you cannot join a set of
+ unrelated bugs together in a way that you wish. Lists of bug numbers
+ can work, by they can only be used for small lists, and it is
+ impossible to share a list between multiple queries.
- <section id="bz30">
- <title>Bugzilla 3.0</title>
- <para>One day, Bugzilla 3.0 will have lots of cool stuff.</para>
- </section>
+ Personal keywords are necessary to replace personal tracking bugs, as
+ they would not pollute the keyword space. Indeed, on many
+ installations this could remove some keywords out of the global
+ keyword space.
+ In a similar vein and with similar effects, group keywords could be
+ introduced that are only available to members of a specific group.
+
+ Keyword Restrictions
+
+ Keywords are not islands unto themselves. Along with their potential
+ to be involved in the inter-field relationships mentioned earlier,
+ keywords can also be related to other keywords.
+
+ Essentially, there are two possibilities:
+ * a set of keywords are mutually exclusive
+ * the presence of a keyword implies another keyword must be present
+
+ Introduction of the ability to specify these restrictions would have
+ benefits.
+
+ If mutually exclusive keywords were present on a bug, their removal
+ would fix up the database, as well as reducing the number of keywords
+ on that bug.
+
+ In the situation where a keyword implies another keyword, there are
+ two possiblities as to how to handle the situation.
+
+ The first is automatically add the keyword. This would fix up the
+ database, but it would increase the number of keywords on a bug.
+
+ The second is to automatically remove the keyword, and alter queries
+ so they pick up the first keyword as well as the removed keyword.
+ This would fix up the database and reduce the number of keywords on a
+ bug, but it might confuse users who don't see the keyword.
+ Alternatively, the implied keywords could be listed separately.
+
+Notifications
+
+ Every time a bug gets changed notifications get sent out to people
+ letting them know about what changes have been made. This is a
+ significant feature, and all sorts of questions can be raised, but
+ they mainly boil down to when they should be sent and what they should
+ look like.
+
+ Changes You're Interested In
+
+ As of version 2.12 users can specify what sort of changes they are
+ interested in receiving notifications for. However, this is still
+ limited. As yet there is no facility to specify which keywords you
+ care about, and whether you care about changes to fields such as the
+ QA contact changes.
+ Furthermore, often an unnecessary comment will go along with a change,
+ either because it is required, or the commenter is ignorant of how the
+ new system works. While explaining why you did something is useful,
+ merely commenting on what you did is not because that information is
+ already accessible view "Bug Activity".
+
+ Because of this unnecessary comment, a lot of changes that would
+ otherwise not generate notifications for certain people do so, because
+ few people are willing to turn off comments. One way to deal with
+ this problem is to allow people to specify that their comments are
+ purely explanatory, and that anyone who is not interested in the
+ change will not be interested in the comment.
+
+ Furthermore, one possible rationale for unnecessary comments is that
+ the bug activity does not display on the normal page and hence it is
+ difficult to cross reference comments and actions. Hence, it would be
+ beneficial to be able to do this.
+
+ Bugs You're Watching
+
+ Currently to receive a notification about a bug you need to have your
+ name on it. This is suboptimal because you need to know about a bug
+ before you can receive notifications on it. Often you are interested
+ in any bug with a field set to a specific value. For example, you
+ might be interested in all bugs with a specific product, component or
+ keyword.
+
+ If someone could automatically receive notifications about these bugs,
+ it would make everyone's lives easier. Currently the default assignee
+ and QA contact for a component will automatically receive
+ notifications for
+
+ Question: This moves half way to a BCC.
+
+ Bulk Changes
+
+ A very useful feature of Bugzilla is the ability to perform an action
+ on multiple bugs at once. However, this means that similar
+ notifications are currently generated for each bug modified.
+
+ This can result in a torrent of notifications that can annoy.
+
+ Furthermore, since the bugs are all changed close to each other in
+ time, it is easy for someone to mass delete all the notifications
+ generated by a bulk change and miss an unrelated notification in the
+ middle.
+
+ These factors can lead to a tendency for people to delay bulk changes,
+ or avoid them entirely. This is suboptimal.
+
+ It would be better if a bulk change generated only one notification
+ mail. This would vastly reduce the annoyance factor, and prevent
+ accidental deletion of notifications.
+
+ One problem with this change is that some people separate out
+ notifications using filtering. This means that they would no longer
+ be match parts of a bulk change under different filtering rules.
+
+ One possibility to resolve this is to allow people to specify groups
+ of bugs. All bugs within a group would go into the same
+ notification. The filters could then distinguish the different bug
+ groups.
+
+ In any case, it is likely there would need to be a transition period
+ to allow people to alter their filters.
+
+Nominations
+
+ ?
+
+Linking Bugzilla Installations
+
+ The first example of linking Bugzilla installations together has is
+ the introduction of bug moving in version 2.12. However, it would be
+ useful to be able to link installations in more ways.
+ * Dependencies and other relationships between bugs in other
+ installations. This is difficult because dependencies are
+ synchronised on both bugs, so the installation that changes
+ dependencies would need to communicate the new state to the other
+ installation. It would also mean that relationships and
+ notifications that refer to other bugs would need to communicate
+ with the other installation.
+ * References to bugs in other installations. Currently if you type
+ "bug XXX" or "bug #XXX" where XXX is a number, you get an
+ automatic hyperlink to that bug. It would be useful if you could
+ say "YYY bug #XXX" where YYY is the name of another installation.
+
+Retirement
+
+ ?
+
+Whiny Reports
+
+ ?
+
+ Group Redesign
+
+ ?
+
+ Hard Wrapping Comments
+
+ Currently Bugzilla "hard wraps" its comments to a specific line size,
+ similar to E-Mail. This has various problems:
+ * The way it currently works, wrapping is done in the browser at
+ submission time using a non-standard HTML extension not supported
+ by some (uncommon) browsers. These browsers generate comments
+ that scroll off the right side of the screen.
+ * Because comments are of fixed width, when you expand your browser
+ window, the comments do not expand to fit available space.
+
+ It would be much better to move to a world of soft wrapping, where the
+ browser wraps the text at display time, similar to a world processor.
+ And as in a word processor, soft wrapping does not preclude the
+ insertion of newlines.
+
+ Hard wrapping is too entrenched into text E-Mail to fix, but we can
+ fix Bugzilla without causing any problems. The old content will still
+ be wrapped too early, but at least new content will work.
+ </literallayout>
+ </para>
</chapter>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
-sgml-omittag:t
-sgml-shorttag:t
-sgml-namecase-general:t
-sgml-general-insert-case:lower
-sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
-sgml-indent-step:2
-sgml-indent-data:t
-sgml-parent-document:nil
+sgml-auto-insert-required-elements:t
+sgml-balanced-tag-edit:t
sgml-exposed-tags:nil
+sgml-general-insert-case:lower
+sgml-indent-data:t
+sgml-indent-step:2
sgml-local-catalogs:nil
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-shorttag:t
+sgml-tag-region-if-active:t
End:
-->
+
diff --git a/docs/sgml/gfdl.sgml b/docs/sgml/gfdl.sgml
index 1091631d4..7d8d9967f 100644
--- a/docs/sgml/gfdl.sgml
+++ b/docs/sgml/gfdl.sgml
@@ -1,4 +1,4 @@
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
+<!-- <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
<appendix id="gfdl">
<title>GNU Free Documentation License</title>
@@ -450,19 +450,25 @@ of this license document, but changing it is not allowed.</para>
</sect1>
</appendix>
+
+
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
-sgml-indent-step:2
-sgml-parent-document: ("Bugzilla-Guide.sgml" "appendix")
+sgml-auto-insert-required-elements:t
+sgml-balanced-tag-edit:t
sgml-exposed-tags:nil
+sgml-general-insert-case:lower
+sgml-indent-data:t
+sgml-indent-step:2
+sgml-local-catalogs:nil
sgml-local-ecat-files:nil
-sgml-local-catalogs: CATALOG
-sgml-validate-command: "nsgmls -s gfdl.sgml"
-ispell-skip-sgml: t
+sgml-minimize-attributes:nil
+sgml-namecase-general:t
+sgml-omittag:t
+sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
+sgml-shorttag:t
+sgml-tag-region-if-active:t
End:
-->
diff --git a/docs/sgml/glossary.sgml b/docs/sgml/glossary.sgml
index 32525f737..faa4d1781 100644
--- a/docs/sgml/glossary.sgml
+++ b/docs/sgml/glossary.sgml
@@ -1,108 +1,321 @@
<!-- <!DOCTYPE glossary PUBLIC "-//OASIS//DTD DocBook V4.1//EN" > -->
-<glossary id="glossary">
+ <glossary id="glossary">
+ <glossdiv>
+ <title>0-9, high ascii</title>
+ <glossentry>
+ <glossterm>.htaccess</glossterm>
+ <glossdef>
+ <para>
+ Apache web server, and other NCSA-compliant web servers,
+ observe the convention of using files in directories
+ called <filename>.htaccess</filename> files. These
+ restrict parameters of the web server. In Bugzilla, they
+ are used to restrict access to certain files which would
+ otherwise compromise your installation. For instance, the
+ <filename>localconfig</filename> file contains the
+ password to your database. If this information were
+ generally available, and remote access to your database
+ turned on, you risk corruption of your database by
+ computer criminals or the curious.
+ </para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+
+ <glossdiv id="gloss_a">
+ <title>A</title>
+ <glossentry>
+ <glossterm>Apache</glossterm>
+ <glossdef>
+ <para>In this context, Apache is the web server most
+ commonly used for serving up
+ <glossterm>Bugzilla</glossterm> pages. Contrary to
+ popular belief, the apache web server has nothing to do
+ with the ancient and noble Native American tribe, but
+ instead derived its name from the fact that it was
+ <quote>a patchy</quote> version of the original
+ <acronym>NCSA</acronym> world-wide-web server.</para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+
+ <glossdiv id="gloss_b">
+ <title>B</title>
+ <glossentry>
+ <glossterm>Bug</glossterm>
+ <glossdef>
+ <para>
+ A <quote>Bug</quote> in Bugzilla refers to an issue
+ entered into the database which has an associated number,
+ assignments, comments, etc. Some also refer to a
+ <quote>tickets</quote> or <quote>issues</quote>; in the
+ context of Bugzilla, they are synonymous.
+ </para>
+ </glossdef>
+ </glossentry>
+
+ <glossentry>
+ <glossterm>Bug Number</glossterm>
+ <glossdef>
+ <para>
+ Each Bugzilla Bug is assigned a number that uniquely
+ identifies that Bug. The Bug associated with a Bug Number
+ can be pulled up via a query, or easily from the very
+ front page by typing the number in the "Find" box.
+ </para>
+ </glossdef>
+ </glossentry>
+
+ <glossentry>
+ <glossterm>Bug Life Cycle</glossterm>
+ <glossdef>
+ <para>A Bug has stages through which it must pass before
+ becoming a <quote>closed bug</quote>, including
+ acceptance, resolution, and verification. The <quote>Bug
+ Life Cycle</quote> is moderately flexible according to
+ the needs of the organization using it, though.</para>
+ </glossdef>
+ </glossentry>
- <glossdiv id="gloss_a">
- <title>A</title>
- <glossentry>
- <glossterm>There are no entries for A</glossterm>
- <glossdef>
- <para></para>
- </glossdef>
- </glossentry>
- </glossdiv>
+ <glossentry>
+ <glossterm>Bugzilla</glossterm>
+ <glossdef>
+ <para>
+ Bugzilla is the industry-standard bug tracking system. It
+ is quite popular among Open Source enthusiasts.
+ </para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
- <glossdiv id="gloss_b">
- <title>B</title>
- <glossentry>
- <glossterm>Bug</glossterm>
- <glossdef>
- <para>A "Bug" in Bugzilla refers to an issue entered into the database which has an associated number, assignments, comments, etc. Many also refer to a "Ticket" or "Issue"; in this context, they are synonymous.</para>
- </glossdef>
- </glossentry>
+ <glossdiv id="gloss_c">
+ <title></title>
+ <glossentry id="gloss_component">
+ <glossterm>Component</glossterm>
+ <glossdef>
+ <para>
+ A Component is a subsection of a Product. It should be a
+ narrow category, tailored to your organization. All
+ Products must contain at least one Component (and, as a
+ matter of fact, creating a Product with no Components will
+ create an error in Bugzilla).
+ </para>
+ </glossdef>
+ </glossentry>
+ <glossentry id="gloss_cpan">
+ <glossterm><acronym>CPAN</acronym></glossterm>
+ <glossdef>
+ <para><acronym>CPAN</acronym> stands for the
+ <quote>Comprehensive Perl Archive Network</quote>. CPAN
+ maintains a large number of extremely useful
+ <glossterm>Perl</glossterm> modules. By themselves, Perl
+ modules generally do nothing, but when used as part of a
+ larger program, they provide much-needed algorithms and
+ functionality.</para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+
+ <glossdiv id="gloss_d">
+ <title>D</title>
+ <glossentry>
+ <glossterm>daemon</glossterm>
+ <glossdef>
+ <para>A daemon is a computer program which runs in the
+ background. In general, most daemons are started at boot
+ time via System V init scripts, or through RC scripts on
+ BSD-based systems. <glossterm>mysqld</glossterm>, the
+ MySQL server, and <glossterm>apache</glossterm>, a web
+ server, are generally run as daemons.</para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
- <glossentry>
- <glossterm>Bug Number</glossterm>
- <glossdef>
- <para>Each Bugzilla Bug is assigned a number that uniquely identifies that Bug. The Bug associated with a Bug Number can be pulled up via a query, or easily from the very front page by typing the number in the "Find" box.</para>
- </glossdef>
- </glossentry>
+ <glossdiv id="gloss_g">
+ <title></title>
+ <glossentry>
+ <glossterm>Groups</glossterm>
+ <glossdef>
+ <para>The word <quote>Groups</quote> has a very special
+ meaning to Bugzilla. Bugzilla's main security mechanism
+ comes by lumping users into groups, and assigning those
+ groups certain privileges to
+ <glossterm>Products</glossterm> and
+ <glossterm>Components</glossterm> in the
+ <glossterm>Bugzilla</glossterm> database.</para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
- <glossentry>
- <glossterm>Bug Life Cycle</glossterm>
- <glossdef>
- <para>A Bug has stages through which it must pass before becoming a "closed bug", including acceptance, resolution, and verification. The "Bug Life Cycle" is moderately flexible according to the needs of the organization using it, though.</para>
- </glossdef>
- </glossentry>
- </glossdiv>
+ <glossdiv id="gloss_i">
+ <title>I</title>
+ <glossentry id="gloss_infiniteloop">
+ <glossterm>Infinite Loop</glossterm>
+ <glossdef>
+ <para>A loop of information that never ends; see recursion.</para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
- <glossdiv id="gloss_i">
- <title>I</title>
- <glossentry id="gloss_infiniteloop">
- <glossterm>Infinite Loop</glossterm>
- <glosssee otherterm="gloss_recursion">
- </glossentry>
- </glossdiv>
+ <glossdiv id="gloss_m">
+ <title>M</title>
+ <glossentry>
+ <glossterm>mysqld</glossterm>
+ <glossdef>
+ <para>mysqld is the name of the
+ <glossterm>daemon</glossterm> 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>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
-<glossdiv id="gloss_p">
- <title>P</title>
- <glossentry>
- <glossterm id="gloss_product">Product</glossterm>
- <glossdef>
- <para>A Product is a broad category of types of bugs. In general, there are several Components to a Product. A Product also defines a default Group (used for Bug Security) for all bugs entered into components beneath it.</para>
- <example>
- <title>A Sample Product</title>
- <para>A company sells a software product called "X". They also maintain some older software called "Y", and have a secret project "Z". An effective use of Products might be to create Products "X", "Y", and "Z", each with Components "User Interface", "Database", and "Business Logic". They might also change group permissions so that only those people who are members of Group "Z" can see components and bugs under Product "Z".</para>
- </example>
- </glossdef>
- </glossentry>
- </glossdiv>
-
- <glossdiv id="gloss_q">
- <title>Q</title>
- <glossentry>
- <glossterm>Q/A</glossterm>
- <glossdef>
- <para>"Q/A" is short for "Quality Assurance". In most large software development organizations, there is a team devoted to ensuring the product meets minimum standards before shipping. This team will also generally want to track the progress of bugs over their life cycle, thus the need for the "Q/A Contact" field in a Bug.</para>
- </glossdef>
- </glossentry>
- </glossdiv>
-
-<glossdiv id="gloss_r">
- <title>R</title>
- <glossentry>
- <glossterm id="gloss_recursion">Recursion</glossterm>
- <glosssee otherterm="gloss_infiniteloop">
- </glossentry>
- </glossdiv>
-
-<glossdiv id="gloss_z">
- <title>Z</title>
- <glossentry>
- <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>
- </glossdef>
- </glossentry>
-</glossdiv>
-
-</glossary>
+ <glossdiv id="gloss_p">
+ <title>P</title>
+ <glossentry>
+ <glossterm id="gloss_product">Product</glossterm>
+ <glossdef>
+ <para>A Product is a broad category of types of bugs. In
+ general, there are several Components to a Product. A
+ Product also defines a default Group (used for Bug
+ Security) for all bugs entered into components beneath
+ it.</para>
+ <example>
+ <title>A Sample Product</title>
+ <para>A company sells a software product called
+ <quote>X</quote>. They also maintain some older
+ software called <quote>Y</quote>, and have a secret
+ project <quote>Z</quote>. An effective use of Products
+ might be to create Products <quote>X</quote>,
+ <quote>Y</quote>, <quote>Z</quote>, each with Components
+ of User Interface, Database, and Business Logic. They
+ might also change group permissions so that only those
+ people who are members of Group <quote>Z</quote> can see
+ components and bugs under Product
+ <quote>Z</quote>.</para>
+ </example>
+ </glossdef>
+ </glossentry>
+ <glossentry>
+ <glossterm>Perl</glossterm>
+ <glossdef>
+ <para>First written by Larry Wall, Perl is a remarkable
+ program language. It has the benefits of the flexibility
+ of an interpreted scripting language (such as shell
+ script), combined with the speed and power of a compiled
+ language, such as C. <glossterm>Bugzilla</glossterm> is
+ maintained in Perl.</para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+
+ <glossdiv id="gloss_q">
+ <title>Q</title>
+ <glossentry>
+ <glossterm>QA</glossterm>
+ <glossdef>
+ <para><quote>QA</quote>, <quote>Q/A</quote>, and
+ <quote>Q.A.</quote> are short for <quote>Quality
+ Assurance</quote>. In most large software development
+ organizations, there is a team devoted to ensuring the
+ product meets minimum standards before shipping. This
+ team will also generally want to track the progress of
+ bugs over their life cycle, thus the need for the
+ <quote>QA Contact</quote> field in a Bug.</para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+
+ <glossdiv id="gloss_r">
+ <title>R</title>
+ <glossentry id="gloss_recursion" xreflabel="Recursion">
+ <glossterm>Recursion</glossterm>
+ <glossdef>
+ <para>The property of a function looking back at itself for
+ something. <quote>GNU</quote>, for instance, stands for
+ <quote>GNU's Not UNIX</quote>, thus recursing upon itself
+ for definition. For further clarity, see Infinite
+ Loop.</para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+ <glossdiv id="gloss_s">
+ <title>S</title>
+ <glossentry>
+ <glossterm><acronym>SGML</acronym></glossterm>
+ <glossdef>
+ <para><acronym>SGML</acronym> stands for <quote>Standard
+ Generalized Markup Language</quote>. Created in the
+ 1980's to provide an extensible means to maintain
+ documentation based upon content instead of presentation,
+ <acronym>SGML</acronym> has withstood the test of time as
+ a robust, powerful language.
+ <glossterm><acronym>XML</acronym></glossterm> is the
+ <quote>baby brother</quote> of SGML; any valid
+ <acronym>XML</acronym> document it, by definition, a valid
+ <acronym>SGML</acronym> document. The document you are
+ reading is written and maintained in
+ <acronym>SGML</acronym>, and is also valid
+ <acronym>XML</acronym> if you modify the Document Type
+ Definition.</para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+ <glossdiv id="gloss_t">
+ <title>T</title>
+ <glossentry id="gloss_target_milestone" xreflabel="Target Milestone">
+ <glossterm>Target Milestone</glossterm>
+ <glossdef>
+ <para>
+ Target Milestones are Product goals. They are
+ configurable on a per-Product basis. Most software
+ development houses have a concept of
+ <quote>milestones</quote> where the people funding a
+ project expect certain functionality on certain dates.
+ Bugzilla facilitates meeting these milestones by giving
+ you the ability to declare by which milestone a bug will be
+ fixed, or an enhancement will be implemented.
+ </para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+
+ <glossdiv id="gloss_z">
+ <title>Z</title>
+ <glossentry id="zarro-boogs-found" xreflabel="Zarro Boogs Found">
+ <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>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+
+ </glossary>
+
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
-sgml-omittag:t
-sgml-shorttag:t
-sgml-namecase-general:t
-sgml-general-insert-case:lower
-sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
-sgml-indent-step:2
-sgml-indent-data:t
-sgml-parent-document:nil
+sgml-auto-insert-required-elements:t
+sgml-balanced-tag-edit:t
sgml-exposed-tags:nil
+sgml-general-insert-case:lower
+sgml-indent-data:t
+sgml-indent-step:2
sgml-local-catalogs:nil
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-shorttag:t
+sgml-tag-region-if-active:t
End:
-->
diff --git a/docs/sgml/index.sgml b/docs/sgml/index.sgml
index e69de29bb..7ca578cfc 100644
--- a/docs/sgml/index.sgml
+++ b/docs/sgml/index.sgml
@@ -0,0 +1,20 @@
+<!-- Keep this comment at the end of the file
+Local variables:
+mode: sgml
+sgml-always-quote-attributes:t
+sgml-auto-insert-required-elements:t
+sgml-balanced-tag-edit:t
+sgml-exposed-tags:nil
+sgml-general-insert-case:lower
+sgml-indent-data:t
+sgml-indent-step:2
+sgml-local-catalogs:nil
+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-shorttag:t
+sgml-tag-region-if-active:t
+End:
+-->
diff --git a/docs/sgml/installation.sgml b/docs/sgml/installation.sgml
index 03ff0bd8d..79b402c5c 100644
--- a/docs/sgml/installation.sgml
+++ b/docs/sgml/installation.sgml
@@ -1,1322 +1,1925 @@
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
+<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
-<CHAPTER id="installation">
- <TITLE>Installing Bugzilla</TITLE>
+ <chapter id="installation" xreflabel="Bugzilla Installation">
+ <title>Installation</title>
+ <para>
+ These installation instructions are presented assuming you are
+ installing on a UNIX or completely POSIX-compliant system. If
+ you are installing on Microsoft Windows or another oddball
+ operating system, please consult the appropriate sections in
+ this installation guide for notes on how to be successful.
+ </para>
+ <section id="errata">
+ <title>ERRATA</title>
+ <para>Here are some miscellaneous notes about possible issues you
+ main run into when you begin your Bugzilla installation.
+ Reference platforms for Bugzilla installation are Redhat Linux
+ 7.2, Linux-Mandrake 8.0, and Solaris 8.</para>
- <SECTION id="README.unix">
- <TITLE>UNIX Installation</TITLE>
- <SECTION>
- <TITLE>ERRATA</TITLE>
- <NOTE>
- <PARA>
- If you are installing Bugzilla on S.u.S.e. Linux, or some other
- distributions with "paranoid" security options, it is possible
- that the checksetup.pl script may fail with the error:
- <ERRORNAME>cannot chdir(/var/spool/mqueue): Permission denied</ERRORNAME>
- This is because your
- /var/spool/mqueue directory has a mode of "drwx------". Type
- <COMMAND>chmod 755 /var/spool/mqueue</COMMAND> as root to fix this problem.
- </PARA>
- </NOTE>
+ <simplelist>
+ <member>
+ If you are installing Bugzilla on S.u.S.e. Linux, or some
+ other distributions with <quote>paranoid</quote> security
+ options, it is possible that the checksetup.pl script may fail
+ with the error: <errorname>cannot chdir(/var/spool/mqueue):
+ Permission denied</errorname> This is because your
+ <filename>/var/spool/mqueue</filename> directory has a mode of
+ <quote>drwx------</quote>. Type <command>chmod 755
+ <filename>/var/spool/mqueue</filename></command> as root to
+ fix this problem.
+ </member>
- <NOTE>
- <PARA>
- Release Notes for Bugzilla 2.12 are available at docs/rel_notes.txt
- </PARA>
- </NOTE>
+ <member>
+ Bugzilla may be installed on Macintosh OS X (10), which is a
+ unix-based (BSD) operating system. Everything required for
+ Bugzilla on OS X will install cleanly, but the optional GD
+ perl module which is used for bug charting requires some
+ additional setup for installation. Please see the Mac OS X
+ installation section below for details
+ </member>
- <NOTE>
- <PARA>
- The preferred documentation for Bugzilla is available in docs/, with
- a variety of document types available. Please refer to these documents when
- installing, configuring, and maintaining your Bugzilla installation.
- </PARA>
- </NOTE>
+ <member>
+ Release Notes for Bugzilla &bz-ver; are available at
+ <filename>docs/rel_notes.txt</filename> in your Bugzilla
+ source distribution.
+ </member>
- <WARNING>
- <PARA>
- Bugzilla is not a package where you can just plop it in a directory,
- twiddle a few things, and you're off. Installing Bugzilla assumes you
- know your variant of UNIX or Microsoft Windows well, are familiar with the
- command line, and are comfortable compiling and installing a plethora
- of third-party utilities. To install Bugzilla on Win32 requires
- fair Perl proficiency, and if you use a webserver other than Apache you
- should be intimately familiar with the security mechanisms and CGI
- environment thereof.
- </PARA>
- </WARNING>
-
- <WARNING>
- <PARA>
- Bugzilla has not undergone a complete security review. Security holes
- may exist in the code. Great care should be taken both in the installation
- and usage of this software. Carefully consider the implications of
- installing other network services with Bugzilla.
- </PARA>
- </WARNING>
- </SECTION>
-
- <SECTION>
- <TITLE>Step-by-step Install</TITLE>
- <SECTION>
- <TITLE>Introduction</TITLE>
- <PARA>
- Installation of bugzilla is pretty straightforward, particularly if your
- machine already has MySQL and the MySQL-related perl packages installed.
- If those aren't installed yet, then that's the first order of business. The
- other necessary ingredient is a web server set up to run cgi scripts.
- While using Apache for your webserver is not required, it is recommended.
- </PARA>
-
- <PARA>
- Bugzilla has been successfully installed under Solaris, Linux, and
- Win32. The peculiarities of installing on Win32 (Win98+/NT/2K) are not
- included in this section of the Guide; please check out the "Win32 Installation Instructions"
- for further advice on getting Bugzilla to work on Microsoft Windows.
- </PARA>
-
- <PARA>
- The Bugzilla Guide is contained in the "docs/" folder. It is available
- in plain text (docs/txt), HTML (docs/html), or SGML source (docs/sgml).
- </PARA>
- </SECTION>
- <SECTION>
- <TITLE>Installing the Prerequisites</TITLE>
+ <member>
+ The preferred documentation for Bugzilla is available in
+ docs/, with a variety of document types available. Please
+ refer to these documents when installing, configuring, and
+ maintaining your Bugzilla installation.
+ </member>
- <PARA>
- The software packages necessary for the proper running of bugzilla are:
- <ORDEREDLIST>
- <LISTITEM>
- <PARA>
- MySQL database server and the mysql client (3.22.5 or greater)
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- Perl (5.004 or greater)
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- DBI Perl module
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- Data::Dumper Perl module
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- DBD::mySQL
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- TimeDate Perl module collection
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- GD perl module (1.8.3) (optional, for bug charting)
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- Chart::Base Perl module (0.99c) (optional, for bug charting)
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- DB_File Perl module (optional, for bug charting)
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- The web server of your choice. Apache is recommended.
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- MIME::Parser Perl module (optional, for contrib/bug_email.pl interface)
- </PARA>
- </LISTITEM>
- </ORDEREDLIST>
- <NOTE>
- <PARA>
- You must run Bugzilla on a filesystem that supports file locking via
- flock(). This is necessary for Bugzilla to operate safely with multiple
- instances.
- </PARA>
- </NOTE>
- <WARNING>
- <PARA>
- It is a good idea, while installing Bugzilla, to ensure it is not
- <EMPHASIS>accessible</EMPHASIS> by other machines on the Internet.
- Your machine may be vulnerable to attacks
- while you are installing. In other words, ensure there is some kind of firewall between you
- and the rest of the Internet. Many installation steps require an active Internet connection
- to complete, but you must take care to ensure that at no point is your machine vulnerable
- to an attack.
- </PARA>
- </WARNING>
-
- </PARA>
- </SECTION>
- <SECTION>
- <TITLE>Installing MySQL Database</TITLE>
- <PARA>
- Visit MySQL homepage at http://www.mysql.org/ and grab the latest stable
- release of the server. Both binaries and source are available and which
- you get shouldn't matter. Be aware that many of the binary versions
- of MySQL store their data files in /var which on many installations
- (particularly common with linux installations) is part of a smaller
- root partition. If you decide to build from sources you can easily set
- the dataDir as an option to configure.
- </PARA>
- <PARA>
- If you've installed from source or non-package (RPM, deb, etc.) binaries
- you'll want to make sure to add mysqld to your init scripts so the server
- daemon will come back up whenever your machine reboots.
- You also may want to edit those init scripts, to make sure that
- mysqld will accept large packets. By default, mysqld is set up to only
- accept packets up to 64K long. This limits the size of attachments you
- may put on bugs. If you add something like "-O max_allowed_packet=1M"
- to the command that starts mysqld (or safe_mysqld), then you will be
- able to have attachments up to about 1 megabyte.
- </PARA>
- <NOTE>
- <PARA>
- If you plan on running Bugzilla and MySQL on the same machine,
- consider using the "--skip-networking" option in the init script.
- This enhances security by preventing network access to MySQL.
- </PARA>
- </NOTE>
- </SECTION>
-
- <SECTION>
- <TITLE>Perl (5.004 or greater)</TITLE>
- <PARA>
- Any machine that doesn't have perl on it is a sad machine indeed. Perl
- for *nix systems can be gotten in source form from http://www.perl.com.
- </PARA>
- <PARA>
- Perl is now a far cry from the the single compiler/interpreter binary it
- once was. It now includes a great many required modules and quite a
- few other support files. If you're not up to or not inclined to build
- perl from source, you'll want to install it on your machine using some
- sort of packaging system (be it RPM, deb, or what have you) to ensure
- a sane install. In the subsequent sections you'll be installing quite
- a few perl modules; this can be quite ornery if your perl installation
- isn't up to snuff.
- </PARA>
- <TIP>
- <PARA>
- You can skip the following Perl module installation
- steps by installing "Bundle::Bugzilla" from CPAN, which includes them.
- All Perl module installation steps require you have an active Internet
- connection.
- </PARA>
- <PARA>
- <COMPUTEROUTPUT>
- <PROMPT>bash#</PROMPT>
- <COMMAND>perl -MCPAN -e 'install "Bundle::Bugzilla"'</COMMAND>
- </COMPUTEROUTPUT>
- </PARA>
- <PARA>
- Bundle::Bugzilla doesn't include GD, Chart::Base, or MIME::Parser,
- which are not essential to a basic Bugzilla install. If installing
- this bundle fails, you should install each module individually to
- isolate the problem.
- </PARA>
- </TIP>
- </SECTION>
+ </simplelist>
+
+ <warning>
+ <para>
+ Bugzilla is not a package where you can just plop it in a directory,
+ twiddle a few things, and you're off. Installing Bugzilla assumes you
+ know your variant of UNIX or Microsoft Windows well, are familiar with the
+ command line, and are comfortable compiling and installing a plethora
+ of third-party utilities. To install Bugzilla on Win32 requires
+ fair Perl proficiency, and if you use a webserver other than Apache you
+ should be intimately familiar with the security mechanisms and CGI
+ environment thereof.
+ </para>
+ </warning>
+
+ <warning>
+ <para>
+ Bugzilla has not undergone a complete security review. Security holes
+ may exist in the code. Great care should be taken both in the installation
+ and usage of this software. Carefully consider the implications of
+ installing other network services with Bugzilla.
+ </para>
+ </warning>
+ </section>
+
+ <section id="stepbystep" xreflabel="Bugzilla Installation Step-by-step">
+ <title>Step-by-step Install</title>
+ <section>
+ <title>Introduction</title>
+ <para>
+ Installation of bugzilla is pretty straightforward, particularly if your
+ machine already has MySQL and the MySQL-related perl packages installed.
+ If those aren't installed yet, then that's the first order of business. The
+ other necessary ingredient is a web server set up to run cgi scripts.
+ While using Apache for your webserver is not required, it is recommended.
+ </para>
+
+ <para>
+ Bugzilla has been successfully installed under Solaris, Linux,
+ and Win32. The peculiarities of installing on Win32 (Microsoft
+ Windows) are not included in this section of the Guide; please
+ check out the <xref linkend="win32"> for further advice
+ on getting Bugzilla to work on Microsoft Windows.
+ </para>
+
+ <para>
+ The Bugzilla Guide is contained in the "docs/" folder in your
+ Bugzilla distribution. It is available in plain text
+ (docs/txt), HTML (docs/html), or SGML source (docs/sgml).
+ </para>
+ </section>
+ <section>
+ <title>Installing the Prerequisites</title>
+ <note>
+ <para>If you want to skip these manual installation steps for
+ the CPAN dependencies listed below, and are running the very
+ most recent version of Perl and MySQL (both the executables
+ and development libraries) on your system, check out
+ Bundle::Bugzilla in <xref linkend="bundlebugzilla"></para>
+ </note>
+ <para>
+ The software packages necessary for the proper running of bugzilla are:
+ <orderedlist>
+ <listitem>
+ <para>
+ MySQL database server and the mysql client (3.22.5 or greater)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Perl (5.004 or greater, 5.6.1 is recommended if you wish
+ to use Bundle::Bugzilla)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ DBI Perl module
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Data::Dumper Perl module
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Bundle::Mysql Perl module collection
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ TimeDate Perl module collection
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ GD perl module (1.8.3) (optional, for bug charting)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Chart::Base Perl module (0.99c) (optional, for bug charting)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ DB_File Perl module (optional, for bug charting)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The web server of your choice. Apache is recommended.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ MIME::Parser Perl module (optional, for contrib/bug_email.pl interface)
+ </para>
+ </listitem>
+ </orderedlist>
- <SECTION>
- <TITLE>DBI Perl Module</TITLE>
- <PARA>
- The DBI module is a generic Perl module used by other database related
- Perl modules. For our purposes it's required by the MySQL-related
- modules. As long as your Perl installation was done correctly the
- DBI module should be a breeze. It's a mixed Perl/C module, but Perl's
- MakeMaker system simplifies the C compilation greatly.
- </PARA>
- <PARA>
- Like almost all Perl modules DBI can be found on the Comprehensive Perl
- Archive Network (CPAN) at http://www.cpan.org. The CPAN servers have a
- real tendency to bog down, so please use mirrors. The current location
- at the time of this writing (02/17/99) can be found in Appendix A.
- </PARA>
- <PARA>
- Quality, general Perl module installation instructions can be found on
- the CPAN website, but the easy thing to do is to just use the CPAN shell
- which does all the hard work for you.
- </PARA>
- <PARA>
- To use the CPAN shell to install DBI:
- <INFORMALEXAMPLE>
- <PARA>
- <COMPUTEROUTPUT>
- <PROMPT>bash#</PROMPT>
- <COMMAND>perl -MCPAN -e 'install "DBI"'</COMMAND>
- </COMPUTEROUTPUT>
- <NOTE>
- <PARA>Replace "DBI" with the name of whichever module you wish
- to install, such as Data::Dumper, TimeDate, GD, etc.</PARA>
- </NOTE>
- </PARA>
- </INFORMALEXAMPLE>
- To do it the hard way:
- <INFORMALEXAMPLE>
- <PARA>
- Untar the module tarball -- it should create its own directory
- </PARA>
- <PARA>
- CD to the directory just created, and enter the following commands:
- <ORDEREDLIST>
- <LISTITEM>
- <PARA>
- <COMPUTEROUTPUT>
- <PROMPT>bash#</PROMPT>
- <COMMAND>perl Makefile.PL</COMMAND>
- </COMPUTEROUTPUT>
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- <COMPUTEROUTPUT>
- <PROMPT>bash#</PROMPT>
- <COMMAND>make</COMMAND>
- </COMPUTEROUTPUT>
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- <COMPUTEROUTPUT>
- <PROMPT>bash#</PROMPT>
- <COMMAND>make test</COMMAND>
- </COMPUTEROUTPUT>
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- <COMPUTEROUTPUT>
- <PROMPT>bash#</PROMPT>
- <COMMAND>make install</COMMAND>
- </COMPUTEROUTPUT>
- </PARA>
- </LISTITEM>
- </ORDEREDLIST>
- If everything went ok that should be all it takes. For the vast
- majority of perl modules this is all that's required.
- </PARA>
- </INFORMALEXAMPLE>
- </PARA>
- </SECTION>
- <SECTION>
- <TITLE>Data::Dumper Perl Module</TITLE>
- <PARA>
- The Data::Dumper module provides data structure persistence for Perl
- (similar to Java's serialization). It comes with later sub-releases of
- Perl 5.004, but a re-installation just to be sure it's available won't
- hurt anything.
- </PARA>
- <PARA>
- Data::Dumper is used by the MySQL related Perl modules. It can be
- found on CPAN (link in Appendix A) and can be installed by following
- the same four step make sequence used for the DBI module.
- </PARA>
- </SECTION>
+ <warning>
+ <para>
+ It is a good idea, while installing Bugzilla, to ensure it
+ is not <emphasis>accessible</emphasis> by other machines
+ on the Internet. Your machine may be vulnerable to attacks
+ while you are installing. In other words, ensure there is
+ some kind of firewall between you and the rest of the
+ Internet. Many installation steps require an active
+ Internet connection to complete, but you must take care to
+ ensure that at no point is your machine vulnerable to an
+ attack.
+ </para>
+ </warning>
+ <note>
+ <para>Linux-Mandrake 8.0, the author's test system, includes
+ every required and optional library for Bugzilla. The
+ easiest way to install them is by using the
+ <filename>urpmi</filename> utility. If you follow these
+ commands, you should have everything you need for
+ Bugzilla, and <filename>checksetup.pl</filename> should
+ not complain about any missing libraries. You may already
+ have some of these installed.</para>
+ <simplelist>
+ <member><prompt>bash#</prompt><command> urpmi
+ perl-mysql</command></member>
+ <member><prompt>bash#</prompt><command> urpmi
+ perl-chart</command></member>
+ <member><prompt>bash#</prompt><command> urpmi
+ perl-gd</command></member>
+ <member><prompt>bash#</prompt><command> urpmi
+ perl-MailTools</command> (for Bugzilla email
+ integration)</member>
+ <member><prompt>bash#</prompt><command> urpmi
+ apache-modules</command></member>
+ </simplelist>
+ </note>
+
+ </para>
+ </section>
+ <section id="install-mysql">
+ <title>Installing MySQL Database</title>
+ <para>
+ Visit MySQL homepage at <ulink
+ url="http://www.mysql.com">www.mysql.com</ulink> and grab the latest stable release of the server. Many of the binary versions of MySQL store their data files in <filename>/var</filename> which is often part of a smaller root partition. If you decide to build from sources you can easily set the dataDir as an option to <filename>configure</filename>.
+ </para>
+ <para>
+ If you install from source or non-package (RPM, deb, etc.)
+ binaries you need to add
+ <firstterm>mysqld</firstterm> to your
+ init scripts so the server daemon will come back up whenever
+ your machine reboots. Further discussion of UNIX init
+ sequences are beyond the scope of this guide.
+ <note>
+ <para>You should have your init script start
+ <glossterm>mysqld</glossterm> with the ability to accept
+ large packets. By default, <filename>mysqld</filename>
+ only accepts packets up to 64K long. This limits the size
+ of attachments you may put on bugs. If you add <option>-O
+ max_allowed_packet=1M</option> to the command that starts
+ <filename>mysqld</filename> (or
+ <filename>safe_mysqld</filename>), then you will be able
+ to have attachments up to about 1 megabyte.</para>
+ </note>
- <SECTION>
- <TITLE>MySQL related Perl Module Collection</TITLE>
- <PARA>
- The Perl/MySQL interface requires a few mutually-dependent perl
- modules. These modules are grouped together into the the
- Msql-Mysql-modules package. This package can be found at CPAN.
- After the archive file has been downloaded it should
- be untarred.
- </PARA>
- <PARA>
- The MySQL modules are all built using one make file which is generated
- by running:
- <PROMPT>bash#</PROMPT>
- <COMMAND>perl Makefile.pl</COMMAND>
- </PARA>
- <PARA>
- The MakeMaker process will ask you a few questions about the desired
- compilation target and your MySQL installation. For many of the questions
- the provided default will be adequate.
- </PARA>
- <PARA>
- When asked if your desired target is the MySQL or mSQL packages
- selected the MySQL related ones. Later you will be asked if you wish
- to provide backwards compatibility with the older MySQL packages; you
- must answer YES to this question. The default will be no, and if you
- select it things won't work later.
- </PARA>
- <PARA>
+ </para>
+ <note>
+ <para>
+ If you plan on running Bugzilla and MySQL on the same
+ machine, consider using the <option>--skip-networking</option>
+ option in the init script. This enhances security by
+ preventing network access to MySQL.
+ </para>
+ </note>
+ </section>
+
+ <section id="install-perl">
+ <title>Perl (5.004 or greater)</title>
+ <para>
+ Any machine that doesn't have perl on it is a sad machine
+ indeed. Perl for *nix systems can be gotten in source form
+ from http://www.perl.com. Although Bugzilla runs with most
+ post-5.004 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 &perl-ver;.
+ </para>
+ <para>
+ Perl is now a far cry from the the single compiler/interpreter
+ binary it once was. It includes a great many required modules
+ and quite a few other support files. If you're not up to or
+ not inclined to build perl from source, you'll want to install
+ it on your machine using some sort of packaging system (be it
+ RPM, deb, or what have you) to ensure a sane install. In the
+ subsequent sections you'll be installing quite a few perl
+ modules; this can be quite ornery if your perl installation
+ isn't up to snuff.
+ </para>
+ <warning>
+ <para>Many people complain that Perl modules will not install
+ for them. Most times, the error messages complain that they
+ are missing a file in <quote>@INC</quote>. Virtually every
+ time, this is due to permissions being set too restrictively
+ for you to compile Perl modules or not having the necessary
+ Perl development libraries installed on your system..
+ Consult your local UNIX systems administrator for help
+ solving these permissions issues; if you
+ <emphasis>are</emphasis> the local UNIX sysadmin, please
+ consult the newsgroup/mailing list for further assistance or
+ hire someone to help you out.
+ </para>
+ </warning>
+ <tip id="bundlebugzilla" xreflabel="Using Bundle::Bugzilla instead of manually installing Perl modules">
+ <para>
+ You can skip the following Perl module installation steps by
+ installing <productname>Bundle::Bugzilla</productname> from
+ <glossterm linkend="gloss_cpan">CPAN</glossterm>, which
+ includes them. All Perl module installation steps require
+ you have an active Internet connection. If you wish to use
+ Bundle::Bugzilla, however, you must be using the latest
+ version of Perl (at this writing, version &perl-ver;)
+ </para>
+ <para>
+ <computeroutput> <prompt>bash#</prompt> <command>perl -MCPAN
+ -e 'install "Bundle::Bugzilla"'</command>
+ </computeroutput>
+ </para>
+ <para>
+ Bundle::Bugzilla doesn't include GD, Chart::Base, or
+ MIME::Parser, which are not essential to a basic Bugzilla
+ install. If installing this bundle fails, you should
+ install each module individually to isolate the problem.
+ </para>
+ </tip>
+ </section>
+
+ <section>
+ <title>DBI Perl Module</title>
+ <para>
+ The DBI module is a generic Perl module used by other database related
+ Perl modules. For our purposes it's required by the MySQL-related
+ modules. As long as your Perl installation was done correctly the
+ DBI module should be a breeze. It's a mixed Perl/C module, but Perl's
+ MakeMaker system simplifies the C compilation greatly.
+ </para>
+ <para>
+ Like almost all Perl modules DBI can be found on the Comprehensive Perl
+ Archive Network (CPAN) at http://www.cpan.org. The CPAN servers have a
+ real tendency to bog down, so please use mirrors. The current location
+ at the time of this writing can be found in <xref linkend="downloadlinks">.
+ </para>
+ <para>
+ Quality, general Perl module installation instructions can be found on
+ the CPAN website, but the easy thing to do is to just use the CPAN shell
+ which does all the hard work for you.
+ </para>
+ <para>
+ To use the CPAN shell to install DBI:
+ <informalexample>
+ <para>
+ <computeroutput>
+ <prompt>bash#</prompt>
+ <command>perl -MCPAN -e 'install "DBI"'</command>
+ </computeroutput>
+ <note>
+ <para>Replace "DBI" with the name of whichever module you wish
+ to install, such as Data::Dumper, TimeDate, GD, etc.</para>
+ </note>
+ </para>
+ </informalexample>
+ To do it the hard way:
+ <informalexample>
+ <para>
+ Untar the module tarball -- it should create its own directory
+ </para>
+ <para>
+ CD to the directory just created, and enter the following commands:
+ <orderedlist>
+ <listitem>
+ <para>
+ <computeroutput>
+ <prompt>bash#</prompt>
+ <command>perl Makefile.PL</command>
+ </computeroutput>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <computeroutput>
+ <prompt>bash#</prompt>
+ <command>make</command>
+ </computeroutput>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <computeroutput>
+ <prompt>bash#</prompt>
+ <command>make test</command>
+ </computeroutput>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <computeroutput>
+ <prompt>bash#</prompt>
+ <command>make install</command>
+ </computeroutput>
+ </para>
+ </listitem>
+ </orderedlist>
+ If everything went ok that should be all it takes. For the vast
+ majority of perl modules this is all that's required.
+ </para>
+ </informalexample>
+ </para>
+ </section>
+ <section>
+ <title>Data::Dumper Perl Module</title>
+ <para>
+ The Data::Dumper module provides data structure persistence for Perl
+ (similar to Java's serialization). It comes with later sub-releases of
+ Perl 5.004, but a re-installation just to be sure it's available won't
+ hurt anything.
+ </para>
+ <para>
+ Data::Dumper is used by the MySQL-related Perl modules. It
+ can be found on CPAN (see <xref linkend="downloadlinks">) and
+ can be
+ installed by following the same four step make sequence used
+ for the DBI module.
+ </para>
+ </section>
+
+ <section>
+ <title>MySQL related Perl Module Collection</title>
+ <para>
+ The Perl/MySQL interface requires a few mutually-dependent perl
+ modules. These modules are grouped together into the the
+ Msql-Mysql-modules package. This package can be found at CPAN.
+ After the archive file has been downloaded it should
+ be untarred.
+ </para>
+ <para>
+ The MySQL modules are all built using one make file which is generated
+ by running:
+ <prompt>bash#</prompt>
+ <command>perl Makefile.pl</command>
+ </para>
+ <para>
+ The MakeMaker process will ask you a few questions about the desired
+ compilation target and your MySQL installation. For many of the questions
+ the provided default will be adequate.
+ </para>
+ <para>
+ When asked if your desired target is the MySQL or mSQL packages,
+ 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.
+ </para>
+ <para>
A host of 'localhost' should be fine and a testing user of 'test' and
a null password should find itself with sufficient access to run tests
on the 'test' database which MySQL created upon installation. If 'make
test' and 'make install' go through without errors you should be ready
to go as far as database connectivity is concerned.
- </PARA>
- </SECTION>
+ </para>
+ </section>
- <SECTION>
- <TITLE>TimeDate Perl Module Collection</TITLE>
- <PARA>
- Many of the more common date/time/calendar related Perl modules have
- been grouped into a bundle similar to the MySQL modules bundle. This
- bundle is stored on the CPAN under the name TimeDate. A (hopefully
- current) link can be found in Appendix A. The component module we're
- most interested in is the Date::Format module, but installing all of them
- is probably a good idea anyway. The standard Perl module installation
- instructions should work perfectly for this simple package.
- </PARA>
- </SECTION>
- <SECTION>
- <TITLE>GD Perl Module (1.8.3)</TITLE>
- <PARA>
- The GD library was written by Thomas Boutell a long while ago to
- programatically generate images in C. Since then it's become almost a
- defacto standard for programatic image construction. The Perl bindings
- to it found in the GD library are used on a million web pages to generate
- graphs on the fly. That's what bugzilla will be using it for so you'd
- better install it if you want any of the graphing to work.
- </PARA>
- <PARA>
- Actually bugzilla uses the Graph module which relies on GD itself,
- but isn't that always the way with OOP. At any rate, you can find the
- GD library on CPAN (link in Appendix "Required Software").
- </PARA>
- <NOTE>
- <PARA>
- The Perl GD library requires some other libraries that may or may not be
- installed on your system, including "libpng" and "libgd". The full requirements
- are listed in the Perl GD library README. Just realize that if compiling GD fails,
- it's probably because you're missing a required library.
- </PARA>
- </NOTE>
- </SECTION>
+ <section>
+ <title>TimeDate Perl Module Collection</title>
+ <para>
+ Many of the more common date/time/calendar related Perl
+ modules have been grouped into a bundle similar to the MySQL
+ modules bundle. This bundle is stored on the CPAN under the
+ name TimeDate (see link: <xref linkend="downloadlinks">). The
+ component module we're most interested in is the Date::Format
+ module, but installing all of them is probably a good idea
+ anyway. The standard Perl module installation instructions
+ should work perfectly for this simple package.
+ </para>
+ </section>
+ <section>
+ <title>GD Perl Module (1.8.3)</title>
+ <para>
+ The GD library was written by Thomas Boutell a long while
+ ago to programatically generate images in C. Since then it's
+ become 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.
+ </para>
+ <para>
+ Actually bugzilla uses the Graph module which relies on GD
+ itself. Isn't that always the way with object-oriented
+ programming? At any rate, you can find the GD library on CPAN
+ in <xref linkend="downloadlinks">.
+ </para>
+ <note>
+ <para>
+ The Perl GD library requires some other libraries that may
+ or may not be installed on your system, including
+ <classname>libpng</classname> and
+ <classname>libgd</classname>. The full requirements are
+ listed in the Perl GD library README. Just realize that if
+ compiling GD fails, it's probably because you're missing a
+ required library.
+ </para>
+ </note>
+ </section>
- <SECTION>
- <TITLE>Chart::Base Perl Module (0.99c)</TITLE>
- <PARA>
+ <section>
+ <title>Chart::Base Perl Module (0.99c)</title>
+ <para>
The Chart module provides bugzilla with on-the-fly charting
- abilities. It can be installed in the usual fashion after it has been
- fetched from CPAN where it is found as the Chart-x.x... tarball in a
- directory to be listed in Appendix "Required Software". Note that as with the GD perl
- module, only the specific versions listed above (or newer) will work. Earlier
- versions used GIF's, which are no longer supported by the latest
- versions of GD.
- </PARA>
- </SECTION>
+ abilities. It can be installed in the usual fashion after it
+ has been fetched from CPAN where it is found as the
+ Chart-x.x... tarball, linked in <xref linkend="downloadlinks">. Note that
+ as with the GD perl module, only the version listed above, or
+ newer, will work. Earlier versions used GIF's, which are no
+ longer supported by the latest versions of GD.
+ </para>
+ </section>
- <SECTION>
- <TITLE>DB_File Perl Module</TITLE>
- <PARA>
- DB_File is a module which allows Perl programs to make use of the facilities provided by
- Berkeley DB version 1.x. This module is required by collectstats.pl which is used for
- bug charting. If you plan to make use of bug charting, you must install this module.
- </PARA>
- </SECTION>
+ <section>
+ <title>DB_File Perl Module</title>
+ <para>
+ DB_File is a module which allows Perl programs to make use
+ of the facilities provided by Berkeley DB version 1.x. This
+ module is required by collectstats.pl which is used for bug
+ charting. If you plan to make use of bug charting, you must
+ install this module.
+ </para>
+ </section>
- <SECTION>
- <TITLE>HTTP Server</TITLE>
- <PARA>
- You have a freedom of choice here - Apache, Netscape or any other
- server on UNIX would do. You can easily run the web server on a different
- machine than MySQL, but need to adjust the MySQL "bugs" user permissions
- accordingly.
- </PARA>
- <PARA>
- You'll want to make sure that your web server will run any file
- with the .cgi extension as a cgi and not just display it. If you're using
- apache that means uncommenting the following line in the srm.conf file:
- <COMPUTEROUTPUT>AddHandler cgi-script .cgi</COMPUTEROUTPUT>
- </PARA>
- <PARA>
- With apache you'll also want to make sure that within the access.conf
- file the line:
- <COMPUTEROUTPUT>
- Options ExecCGI
- </COMPUTEROUTPUT>
- is in the stanza that covers the directories you intend to put the bugzilla
- .html and .cgi files into.
- </PARA>
- <PARA>
- If you are using a newer version of Apache, both of the above lines will be
- (or will need to be) in the httpd.conf file, rather than srm.conf or
- access.conf.
- </PARA>
- <WARNING>
- <PARA>
- There are two critical directories and a file that should not be a served by
- the HTTP server. These are the 'data' and 'shadow' directories and the
- 'localconfig' file. You should configure your HTTP server to not serve
- content from these files. Failure to do so will expose critical passwords
- and other data. Please see your HTTP server configuration manual on how
- to do this. If you use quips (at the top of the buglist pages) you will want
- the 'data/comments' file to still be served. This file contains those quips.
- </PARA>
- </WARNING>
- </SECTION>
+ <section>
+ <title>HTTP Server</title>
+ <para>
+ You have a freedom of choice here - Apache, Netscape or any
+ other server on UNIX would do. You can easily run the web
+ server on a different machine than MySQL, but need to adjust
+ the MySQL <quote>bugs</quote> user permissions accordingly.
+ <note>
+ <para>I strongly recommend Apache as the web server to use.
+ The Bugzilla Guide installation instructions, in general,
+ assume you are using Apache. As more users use different
+ webservers and send me information on the peculiarities of
+ installing using their favorite webserver, I will provide
+ notes for them.</para>
+ </note>
+ </para>
+ <para>
+ You'll want to make sure that your web server will run any
+ file with the .cgi extension as a cgi and not just display it.
+ If you're using apache that means uncommenting the following
+ line in the srm.conf file:
+ <programlisting>
+AddHandler cgi-script .cgi
+ </programlisting>
+ </para>
+ <para>
+ With apache you'll also want to make sure that within the
+ access.conf file the line:
+ <programlisting>
+Options ExecCGI
+</programlisting>
+ is in the stanza that covers the directories into which
+ you intend to put the bugzilla .html and .cgi files.
+ </para>
+ <note>
+ <para>
+ Users of newer versions of Apache will generally find both
+ of the above lines will be in the httpd.conf file, rather
+ than srm.conf or access.conf.
+ </para>
+ </note>
+ <warning>
+ <para>
+ There are important files and directories that should not
+ be a served by the HTTP server. These are most files in the
+ <quote>data</quote> and <quote>shadow</quote> directories
+ and the <quote>localconfig</quote> file. You should
+ configure your HTTP server to not serve content from these
+ files. Failure to do so will expose critical passwords and
+ other data. Please see <xref linkend="htaccess"> for details
+ on how to do this for Apache. I appreciate notes on how to
+ get this same functionality using other webservers.
+ </para>
+ </warning>
+ </section>
- <SECTION>
- <TITLE>Installing the Bugzilla Files</TITLE>
- <PARA>
- You should untar the Bugzilla files into a directory that you're
- willing to make writable by the default web server user (probably
- 'nobody'). You may decide to put the files off of the main web space
- for your web server or perhaps off of /usr/local with a symbolic link
- in the web space that points to the bugzilla directory. At any rate,
- just dump all the files in the same place (optionally omitting the CVS
- directories if they were accidentally tarred up with the rest of Bugzilla)
- and make sure you can access the files in that directory through your
- web server.
- </PARA>
- <TIP>
- <PARA>
- HINT: If you symlink the bugzilla directory into your Apache's
- HTML heirarchy, you may receive "Forbidden" errors unless you
- add the "FollowSymLinks" directive to the <Directory> entry
- for the HTML root.
- </PARA>
- </TIP>
- <PARA>
- Once all the files are in a web accessible directory, make that
- directory writable by your webserver's user (which may require just
- making it world writable). This is a temporary step until you run
- the post-install "checksetup.pl" script, which locks down your
- installation.
- </PARA>
- <PARA>
- Lastly, you'll need to set up a symbolic link from /usr/bonsaitools/bin
- to the correct location of your perl executable (probably /usr/bin/perl).
- Otherwise you must hack all the .cgi files to change where they look
- for perl. To make future upgrades easier, you should use the symlink
- approach.
- <TIP>
- <PARA>
- If you don't have root access to set this symlink up, check out the
- "setperl.csh" utility, listed in the Patches section of this
- Guide. It will change the path to perl in all your Bugzilla files for
- you.
- </PARA>
- </TIP>
- </PARA>
- </SECTION>
+ <section>
+ <title>Installing the Bugzilla Files</title>
+ <para>
+ You should untar the Bugzilla files into a directory that
+ you're willing to make writable by the default web server user
+ (probably <quote>nobody</quote>). You may decide to put the
+ files off of the main web space for your web server or perhaps
+ off of <filename>/usr/local</filename> with a symbolic link in
+ the web space that points to the Bugzilla directory. At any
+ rate, just dump all the files in the same place, and make sure
+ you can access the files in that directory through your web
+ server.
+ </para>
+ <tip>
+ <para>
+ If you symlink the bugzilla directory into your Apache's
+ HTML heirarchy, you may receive
+ <errorname>Forbidden</errorname> errors unless you add the
+ <quote>FollowSymLinks</quote> directive to the
+ <Directory> entry for the HTML root.
+ </para>
+ </tip>
+ <para>
+ Once all the files are in a web accessible directory, make
+ that directory writable by your webserver's user. This is a
+ temporary step until you run the post-install
+ <filename>checksetup.pl</filename> script, which locks down your
+ installation.
+ </para>
+ <para>
+ Lastly, you'll need to set up a symbolic link to
+ <filename>/usr/bonsaitools/bin/perl</filename> for the correct
+ location of your perl executable (probably
+ <filename>/usr/bin/perl</filename>). Otherwise you must hack
+ all the .cgi files to change where they look for perl, or use
+ <xref linkend="setperl">, found in
+ <xref linkend="patches">. I suggest using the symlink
+ approach for future release compatability.
+ <example>
+ <title>Setting up bonsaitools symlink</title>
+ <para>
+ Here's how you set up the Perl symlink on Linux to make
+ Bugzilla work. Your mileage may vary. For some UNIX
+ operating systems, you probably need to subsitute
+ <quote>/usr/local/bin/perl</quote> for
+ <quote>/usr/bin/perl</quote> below; if on certain other
+ UNIX systems, Perl may live in weird places like
+ <quote>/opt/perl</quote>. As root, run these commands:
+ <programlisting>
+bash# mkdir /usr/bonsaitools
+bash# mkdir /usr/bonsaitools/bin
+bash# ln -s /usr/bin/perl /usr/bosaitools/bin/perl
+ </programlisting>
+ </para>
+ <para>
+ Alternately, you can simply run this perl one-liner to
+ change your path to perl in all the files in your Bugzilla
+ installation:
+ <programlisting>
+perl -pi -e 's@#!/usr/bonsaitools/bin/perl@#!/usr/bin/perl@' *cgi *pl Bug.pm
+ </programlisting>
+ Change the second path to perl to match your installation.
+ </para>
+ </example>
+ <tip>
+ <para>
+ If you don't have root access to set this symlink up,
+ check out the
+ <xref linkend="setperl">, listed in <xref
+ linkend="patches">. It will change the path to perl in all your Bugzilla files for you.
+ </para>
+ </tip>
+ </para>
+ </section>
- <SECTION>
- <TITLE>Setting Up the MySQL Database</TITLE>
- <PARA>
+ <section>
+ <title>Setting Up the MySQL Database</title>
+ <para>
After you've gotten all the software installed and working you're ready
to start preparing the database for its life as a the back end to a high
quality bug tracker.
- </PARA>
- <PARA>
- First, you'll want to fix MySQL permissions to allow access from
- Bugzilla. For the purpose of this Installation section, the Bugzilla username
- will be "bugs", and will have minimal permissions. Bugzilla has
- not undergone a thorough security audit. It may be possible for
- a system cracker to somehow trick Bugzilla into executing a command
- such as "; DROP DATABASE mysql".
- </PARA>
- <PARA>
- That would be bad.
- </PARA>
- <PARA>
- Give the MySQL root user a password. MySQL passwords are
- limited to 16 characters.
- <SIMPLELIST>
- <MEMBER>
- <COMPUTEROUTPUT>
- <PROMPT>bash#</PROMPT>
- <COMMAND>mysql -u root mysql</COMMAND>
- </COMPUTEROUTPUT>
- </MEMBER>
- <MEMBER>
- <COMPUTEROUTPUT>
- <PROMPT>mysql></PROMPT>
- <COMMAND>
- UPDATE user SET Password=PASSWORD ('new_password')
- WHERE user='root';
- </COMMAND>
- </COMPUTEROUTPUT>
- </MEMBER>
- <MEMBER>
- <COMPUTEROUTPUT>
- <PROMPT>mysql></PROMPT>
- <COMMAND>FLUSH PRIVILEGES;</COMMAND>
- </COMPUTEROUTPUT>
- </MEMBER>
- </SIMPLELIST>
- From this point on, if you need to access MySQL as the
- MySQL root user, you will need to use "mysql -u root -p" and
- enter your new_password. Remember that MySQL user names have
- nothing to do with Unix user names (login names).
- </PARA>
- <PARA>
- Next, we create the "bugs" user, and grant sufficient
- permissions for checksetup.pl, which we'll use later, to work
- its magic. This also restricts the "bugs" user to operations
- within a database called "bugs", and only allows the account
- to connect from "localhost". Modify it to reflect your setup
- if you will be connecting from another machine or as a different
- user.
- </PARA>
- <PARA>
- Remember to set bugs_password to some unique password.
- <SIMPLELIST>
- <MEMBER>
- <COMPUTEROUTPUT>
- <PROMPT>mysql></PROMPT>
- <COMMAND>GRANT SELECT,INSERT,UPDATE,DELETE,INDEX,
- ALTER,CREATE,DROP,REFERENCES
- ON bugs.* TO bugs@localhost
- IDENTIFIED BY 'bugs_password';</COMMAND>
- </COMPUTEROUTPUT>
- </MEMBER>
- <MEMBER>
- <COMPUTEROUTPUT>
- <PROMPT>
- mysql>
- </PROMPT>
- <COMMAND>
- FLUSH PRIVILEGES;
- </COMMAND>
- </COMPUTEROUTPUT>
- </MEMBER>
- </SIMPLELIST>
- </PARA>
- <PARA>
- Next, run the magic checksetup.pl script. (Many thanks to Holger
- Schurig <holgerschurig@nikocity.de> for writing this script!)
- It will make sure Bugzilla files and directories have reasonable
- permissions, set up the "data" directory, and create all the MySQL
- tables.
- <SIMPLELIST>
- <MEMBER>
- <COMPUTEROUTPUT>
- <PROMPT>bash#</PROMPT>
- <COMMAND>./checksetup.pl</COMMAND>
- </COMPUTEROUTPUT>
- </MEMBER>
- </SIMPLELIST>
- The first time you run it, it will create a file called "localconfig".
- </PARA>
- </SECTION>
-
- <SECTION>
- <TITLE>Tweaking "localconfig"</TITLE>
- <PARA>
- This file contains a variety of settings you may need to tweak including
- how Bugzilla should connect to the MySQL database.
- </PARA>
- <PARA>
- The connection settings include:
- <ORDEREDLIST>
- <LISTITEM>
- <PARA>
- server's host: just use "localhost" if the MySQL server is
- local
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- database name: "bugs" if you're following these directions
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- MySQL username: "bugs" if you're following these directions
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- Password for the "bugs" MySQL account above
- </PARA>
- </LISTITEM>
- </ORDEREDLIST>
- </PARA>
- <PARA>
- Once you are happy with the settings, re-run checksetup.pl. On this
- second run, it will create the database and an administrator account
- for which you will be prompted to provide information.
- </PARA>
- <PARA>
- When logged into an administrator account once Bugzilla is running,
- if you go to the query page (off of the bugzilla main menu), you'll
- find an 'edit parameters' option that is filled with editable treats.
- </PARA>
- <PARA>
- Should everything work, you should have a nearly empty copy of the bug
- tracking setup.
- </PARA>
- <PARA>
- The second time around, checksetup.pl will stall if it is on a
- filesystem that does not fully support file locking via flock(), such as
- NFS mounts. This support is required for Bugzilla to operate safely with
- multiple instances. If flock() is not fully supported, it will stall at:
- <ERRORCODE>Now regenerating the shadow database for all bugs.</ERRORCODE>
- <NOTE>
- <PARA>
- The second time you run checksetup.pl, it is recommended you be the same
- user as your web server runs under, and that you be sure you have set the
- "webservergroup" parameter in localconfig to match the web server's group
- name, if any. Under some systems, otherwise, checksetup.pl will goof up
- your file permissions and make them unreadable to your web server.
- </PARA>
- </NOTE>
- </PARA>
- <NOTE>
- <PARA>
- The checksetup.pl script is designed so that you can run it at any time
- without causing harm. You should run it after any upgrade to Bugzilla.
- </PARA>
- </NOTE>
- </SECTION>
-
- <SECTION>
- <TITLE>Setting Up Maintainers Manuall (Optional)</TITLE>
- <PARA>
- If you want to add someone else to every group by hand, you can do it
- by typing the appropriate MySQL commands. Run '<COMPUTEROUTPUT>
- mysql -u root -p bugs</COMPUTEROUTPUT>'
- (you may need different parameters, depending on your security settings
- according to section 3, above). Then:
- <SIMPLELIST>
- <MEMBER>
- <COMPUTEROUTPUT>
- <PROMPT>mysql></PROMPT>
- <COMMAND>update profiles set groupset=0x7fffffffffffffff
- where login_name = 'XXX';</COMMAND>
- </COMPUTEROUTPUT>
- </MEMBER>
- </SIMPLELIST>
- replacing XXX with the Bugzilla email address.
- </PARA>
- </SECTION>
+ </para>
+ <para>
+ First, you'll want to fix MySQL permissions to allow access
+ from Bugzilla. For the purpose of this Installation section,
+ the Bugzilla username will be <quote>bugs</quote>, and will
+ have minimal permissions.
+
+ <warning>
+ <para>
+ Bugzilla has not undergone a thorough security audit. It
+ may be possible for a system cracker to somehow trick
+ Bugzilla into executing a command such as <command>DROP
+ DATABASE mysql</command>.
+ </para>
+ <para>That would be bad.</para>
+ </warning>
+ </para>
+
+ <para>
+ Give the MySQL root user a password. MySQL passwords are
+ limited to 16 characters.
+ <simplelist>
+ <member>
+ <computeroutput> <prompt>bash#</prompt> <command>mysql
+ -u root mysql</command> </computeroutput>
+ </member>
+ <member>
+ <computeroutput> <prompt>mysql></prompt> <command>
+ UPDATE user SET Password=PASSWORD ('new_password')
+ WHERE user='root'; </command> </computeroutput>
+ </member>
+ <member>
+ <computeroutput> <prompt>mysql></prompt> <command>FLUSH
+ PRIVILEGES;</command> </computeroutput>
+ </member>
+ </simplelist> From this point on, if you need to access
+ MySQL as the MySQL root user, you will need to use
+ <command>mysql -u root -p</command> and enter your
+ new_password. Remember that MySQL user names have nothing to
+ do with Unix user names (login names).
+ </para>
+ <para>
+ Next, we create the <quote>bugs</quote> user, and grant
+ sufficient permissions for checksetup.pl, which we'll use
+ later, to work its magic. This also restricts the
+ <quote>bugs</quote> user to operations within a database
+ called <quote>bugs</quote>, and only allows the account to
+ connect from <quote>localhost</quote>. Modify it to reflect
+ your setup if you will be connecting from another machine or
+ as a different user.
+ </para>
+ <para>
+ Remember to set bugs_password to some unique password.
+ <simplelist>
+ <member>
+ <computeroutput>
+ <prompt>mysql></prompt>
+ <command>GRANT SELECT,INSERT,UPDATE,DELETE,INDEX,
+ ALTER,CREATE,DROP,REFERENCES
+ ON bugs.* TO bugs@localhost
+ IDENTIFIED BY 'bugs_password';</command>
+ </computeroutput>
+ </member>
+ <member>
+ <computeroutput>
+ <prompt>
+ mysql>
+ </prompt>
+ <command>
+ FLUSH PRIVILEGES;
+ </command>
+ </computeroutput>
+ </member>
+ </simplelist>
+ </para>
+ <para>
+ Next, run the magic checksetup.pl script. (Many thanks to
+ Holger Schurig <holgerschurig@nikocity.de> for writing
+ this script!) It will make sure Bugzilla files and directories
+ have reasonable permissions, set up the
+ <filename>data</filename> directory, and create all the MySQL
+ tables.
+ <simplelist>
+ <member>
+ <computeroutput> <prompt>bash#</prompt>
+ <command>./checksetup.pl</command> </computeroutput>
+ </member>
+ </simplelist> The first time you run it, it will create a
+ file called <filename>localconfig</filename>.
+ </para>
+ </section>
+
+ <section>
+ <title>Tweaking <filename>localconfig</filename></title>
+ <para>
+ This file contains a variety of settings you may need to tweak including
+ how Bugzilla should connect to the MySQL database.
+ </para>
+ <para>
+ The connection settings include:
+ <orderedlist>
+ <listitem>
+ <para>
+ server's host: just use <quote>localhost</quote> if the
+ MySQL server is local
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ database name: <quote>bugs</quote> if you're following
+ these directions
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ MySQL username: <quote>bugs</quote> if you're following
+ these directions
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Password for the <quote>bugs</quote> MySQL account above
+ </para>
+ </listitem>
+ </orderedlist>
+ </para>
+ <para>
+ You should also install .htaccess files that the Apache
+ webserver will use to restrict access to Bugzilla data files.
+ See <xref
+ linkend="htaccess">.
+ </para>
+ <para>
+ Once you are happy with the settings, re-run
+ <filename>checksetup.pl</filename>. On this second run, it will
+ create the database and an administrator account for which
+ you will be prompted to provide information.
+ </para>
+ <para>
+ When logged into an administrator account once Bugzilla is
+ running, if you go to the query page (off of the Bugzilla main
+ menu), you'll find an <quote>edit parameters</quote> option
+ that is filled with editable treats.
+ </para>
+ <para>
+ Should everything work, you will have a nearly empty Bugzilla
+ database and a newly-created <filename>localconfig</filename>
+ file in your Bugzilla root directory.
+ </para>
+ <para>
+ <note>
+ <para>
+ The second time you run checksetup.pl, you should become
+ the user your web server runs as, and that you ensure that
+ you set the <quote>webservergroup</quote> parameter in localconfig to
+ match the web server's group name, if any. I believe,
+ for the next release of Bugzilla, this will be fixed so
+ that Bugzilla supports a <quote>webserveruser</quote> parameter in
+ localconfig as well.
+ <example>
+ <title>Running checksetup.pl as the web user</title>
+ <para>
+ Assuming your web server runs as user "apache", and
+ Bugzilla is installed in "/usr/local/bugzilla", here's
+ one way to run checksetup.pl as the web server user.
+ As root, for the <emphasis>second run</emphasis> of
+ checksetup.pl, do this:
+ <programlisting>
+bash# chown -R apache:apache /usr/local/bugzilla
+bash# su - apache
+bash# cd /usr/local/bugzilla
+bash# ./checksetup.pl
+ </programlisting>
+ </para>
+ </example>
+ </para>
+ </note>
+ </para>
+ <note>
+ <para>
+ The checksetup.pl script is designed so that you can run
+ it at any time without causing harm. You should run it
+ after any upgrade to Bugzilla.
+ </para>
+ </note>
+ </section>
+
+ <section>
+ <title>Setting Up Maintainers Manually (Optional)</title>
+ <para>
+ If you want to add someone else to every group by hand, you
+ can do it by typing the appropriate MySQL commands. Run
+ <command> mysql -u root -p bugs</command> You
+ may need different parameters, depending on your security
+ settings. Then:
+ <simplelist>
+ <member>
+ <computeroutput> <prompt>mysql></prompt> <command>update
+ profiles set groupset=0x7fffffffffffffff where
+ login_name = 'XXX';</command> </computeroutput> (yes, that's <emphasis>fifteen</emphasis><quote>f</quote>'s.
+ </member>
+ </simplelist> replacing XXX with the Bugzilla email address.
+ </para>
+ </section>
- <SECTION>
- <TITLE>The Whining Cron (Optional)</TITLE>
- <PARA>
- By now you've got a fully functional bugzilla, but what good are bugs
- if they're not annoying? To help make those bugs more annoying you can
- set up bugzilla's automatic whining system. This can be done by adding
- the following command as a daily crontab entry (for help on that see that
- crontab man page):
- <SIMPLELIST>
- <MEMBER>
- <COMPUTEROUTPUT>
- <COMMAND>cd <your-bugzilla-directory> ; ./whineatnews.pl</COMMAND>
- </COMPUTEROUTPUT>
- </MEMBER>
- </SIMPLELIST>
- </PARA>
- </SECTION>
+ <section>
+ <title>The Whining Cron (Optional)</title>
+ <para>
+ 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. This can be done by adding the following command as a
+ daily crontab entry (for help on that see that crontab man
+ page):
+ <simplelist>
+ <member>
+ <computeroutput> <command>cd
+ <your-bugzilla-directory> ;
+ ./whineatnews.pl</command> </computeroutput>
+ </member>
+ </simplelist>
+ </para>
+ <tip>
+ <para>
+ Depending on your system, crontab may have several manpages.
+ The following command should lead you to the most useful
+ page for this purpose:
+ <programlisting>
+ man 5 crontab
+ </programlisting>
+ </para>
+ </tip>
+ </section>
+
+ <section>
+ <title>Bug Graphs (Optional)</title>
+ <para>
+ As long as you installed the GD and Graph::Base Perl modules
+ you might as well turn on the nifty bugzilla bug reporting
+ graphs.
+ </para>
+ <para>
+ Add a cron entry like this to run collectstats daily at 5
+ after midnight:
+ <simplelist>
+ <member>
+ <computeroutput> <prompt>bash#</prompt> <command>crontab
+ -e</command> </computeroutput>
+ </member>
+ <member>
+ <computeroutput> 5 0 * * * cd
+ <your-bugzilla-directory> ; ./collectstats.pl
+ </computeroutput>
+ </member>
+ </simplelist>
+ </para>
+ <para>
+ After two days have passed you'll be able to view bug graphs
+ from the Bug Reports page.
+ </para>
+ </section>
+
+ <section>
+ <title>Securing MySQL</title>
+ <para>
+ If you followed the 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>
+ Use .htaccess files with the Apache webserver to secure your
+ bugzilla install. See <xref linkend="htaccess">
+ </para>
+ <para>
+ Consider also:
+ <orderedlist>
+ <listitem>
+ <para>
+ Turning off external networking with "--skip-networking",
+ unless you have "mit-pthreads", in which case you can't.
+ Without networking, MySQL connects with a Unix domain socket.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ using the --user= option to mysqld to run it as an unprivileged
+ user.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ starting MySQL in a chroot jail
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ running the httpd in a "chrooted" jail
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ making sure the MySQL passwords are different from the OS
+ passwords (MySQL "root" has nothing to do with system "root").
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ running MySQL on a separate untrusted machine
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ making backups ;-)
+ </para>
+ </listitem>
+ </orderedlist>
+ </para>
+ </section>
+ </section>
+ <section id="osx">
+ <title>Mac OS X Installation Notes</title>
+ <para>
+ 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.
+ </para>
+ <para>
+ 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/>.
+ </para>
+ <para>
+ Follow the instructions for setting up Fink. Once it's
+ installed, you'll want to run the following as root:
+ <command>fink install gd</command>
+ </para>
+ <para>
+ It will prompt you for a number of dependencies, type 'y' and
+ hit enter to install all of the dependencies. Then watch it
+ work.
+ </para>
+ <para>
+ 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 (it looks for the specific paths instead of getting
+ them from your environment). But there's a way around that
+ :-)
+ </para>
+ <para>
+ Instead of typing <quote>install GD</quote> at the
+ <prompt>cpan></prompt> prompt, type <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 the
+ following patch to the Makefile.PL file (save the patch into a
+ file and use the command <command>patch <
+ patchfile</command>:
+ </para>
+ <para>
+ <programlisting>
+<![CDATA[
+
+--- GD-1.33/Makefile.PL Fri Aug 4 16:59:22 2000
++++ GD-1.33-darwin/Makefile.PL Tue Jun 26 01:29:32 2001
+@@ -3,8 +3,8 @@
+ warn "NOTICE: This module requires libgd 1.8.3 or higher (shared library version 4.X).\n";
+
+ # =====> PATHS: CHECK AND ADJUST <=====
+-my @INC = qw(-I/usr/local/include -I/usr/local/include/gd);
+-my @LIBPATH = qw(-L/usr/lib/X11 -L/usr/X11R6/lib -L/usr/X11/lib -L/usr/local/lib );
++my @INC = qw(-I/sw/include -I/sw/include/gd -I/usr/local/include -I/usr/local/include/gd);
++my @LIBPATH = qw(-L/usr/lib/X11 -L/usr/X11R6/lib -L/usr/X11/lib -L/sw/lib -L/usr/local/lib);
+ my @LIBS = qw(-lgd -lpng -lz);
+
+ # FEATURE FLAGS
+@@ -23,7 +23,7 @@
+
+ push @LIBS,'-lttf' if $TTF;
+ push @LIBS,'-ljpeg' if $JPEG;
+-push @LIBS, '-lm' unless $^O eq 'MSWin32';
++push @LIBS, '-lm' unless ($^O =~ /^MSWin32|darwin$/);
+
+ # FreeBSD 3.3 with libgd built from ports croaks if -lXpm is specified
+ if ($^O ne 'freebsd' && $^O ne 'MSWin32') {
- <SECTION>
- <TITLE>Bug Graphs (Optional)</TITLE>
- <PARA>
- As long as you installed the GD and Graph::Base Perl modules you might
- as well turn on the nifty bugzilla bug reporting graphs.
- </PARA>
- <PARA>
- Add a cron entry like this to run collectstats daily at 5 after midnight:
- <SIMPLELIST>
- <MEMBER>
- <COMPUTEROUTPUT>
- <PROMPT>bash#</PROMPT>
- <COMMAND>crontab -e</COMMAND>
- </COMPUTEROUTPUT>
- </MEMBER>
- <MEMBER>
- <COMPUTEROUTPUT>
- 5 0 * * * cd <your-bugzilla-directory> ; ./collectstats.pl
- </COMPUTEROUTPUT>
- </MEMBER>
- </SIMPLELIST>
- </PARA>
- <PARA>
- After two days have passed you'll be able to view bug graphs from the
- Bug Reports page.
- </PARA>
- </SECTION>
+]]>
+ </programlisting>
+ </para>
+ <para>
+ Then, run these commands to finish the installation of the perl module:
+ <simplelist>
+ <member><command>perl Makefile.PL</command></member>
+ <member><command>make</command></member>
+ <member><command>make test</command></member>
+ <member><command>make install</command></member>
+ <member>And don't forget to run <command>exit</command> to get back to cpan.</member>
+ </simplelist>
+ </para>
+ <para>
+ Happy Hacking!
+ </para>
+ </section>
+
+ <section id="bsdinstall" xreflabel="BSD Installation Notes">
+ <title>BSD Installation Notes</title>
+ <para>
+ For instructions on how to set up Bugzilla on FreeBSD, NetBSD, OpenBSD, BSDi, etc. please
+ consult <xref linkend="osx">.
+ </para>
+ </section>
+
+
+ <section id="geninstall" xreflabel="Installation General Notes">
+ <title>Installation General Notes</title>
+ <section>
+ <title>Modifying Your Running System</title>
+ <para>
+ Bugzilla optimizes database lookups by storing all relatively static
+ information in the versioncache file, located in the data/ subdirectory
+ under your installation directory.
+ </para>
+ <para>
+ If you make a change to the structural data in your database
+ (the versions table for example), or to the
+ <quote>constants</quote> encoded in defparams.pl, you will
+ need to remove the cached content from the data directory
+ (by doing a <quote>rm data/versioncache</quote>), or your
+ changes won't show up.
+ </para>
+ <para>
+ That file gets automatically regenerated whenever it's more than an
+ hour old, so Bugzilla will eventually notice your changes by itself, but
+ generally you want it to notice right away, so that you can test things.
+ </para>
+ </section>
+ <section>
+ <title>Upgrading From Previous Versions</title>
+ <para>
+ The developers of Bugzilla are constantly adding new tables, columns and
+ fields. You'll get SQL errors if you just update the code. The strategy
+ to update is to simply always run the checksetup.pl script whenever
+ you upgrade your installation of Bugzilla. If you want to see what has
+ changed, you can read the comments in that file, starting from the end.
+ </para>
+ <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>
+ </section>
- <SECTION>
- <TITLE>Securing MySQL</TITLE>
- <PARA>
- If you followed the README for setting up your "bugs" and "root" user in
- MySQL, much of this should not apply to you. If you are upgrading
- an existing installation of Bugzilla, you should pay close attention
- to this section.
- </PARA>
- <PARA>
- Most MySQL installs have "interesting" default security parameters:
- <SIMPLELIST>
- <MEMBER>mysqld defaults to running as root</MEMBER>
- <MEMBER>it defaults to allowing external network connections</MEMBER>
- <MEMBER>it has a known port number, and is easy to detect</MEMBER>
- <MEMBER>it defaults to no passwords whatsoever</MEMBER>
- <MEMBER>it defaults to allowing "File_Priv"</MEMBER>
- </SIMPLELIST>
- </PARA>
- <PARA>
- This means anyone from anywhere on the internet can not only drop the
- database with one SQL command, and they can write as root to the system.
- </PARA>
- <PARA>
- To see your permissions do:
- <SIMPLELIST>
- <MEMBER>
- <COMPUTEROUTPUT>
- <PROMPT>bash#</PROMPT>
- <COMMAND>mysql -u root -p</COMMAND>
- </COMPUTEROUTPUT>
- </MEMBER>
- <MEMBER>
- <COMPUTEROUTPUT>
- <PROMPT>mysql></PROMPT>
- <COMMAND>use mysql;</COMMAND>
- </COMPUTEROUTPUT>
- </MEMBER>
- <MEMBER>
- <COMPUTEROUTPUT>
- <PROMPT>mysql></PROMPT>
- <COMMAND>show tables;</COMMAND>
- </COMPUTEROUTPUT>
- </MEMBER>
- <MEMBER>
- <COMPUTEROUTPUT>
- <PROMPT>mysql></PROMPT>
- <COMMAND>select * from user;</COMMAND>
- </COMPUTEROUTPUT>
- </MEMBER>
- <MEMBER>
- <COMPUTEROUTPUT>
- <PROMPT>mysql></PROMPT>
- <COMMAND>select * from db;</COMMAND>
- </COMPUTEROUTPUT>
- </MEMBER>
- </SIMPLELIST>
- </PARA>
- <PARA>
- To fix the gaping holes:
- <SIMPLELIST>
- <MEMBER>DELETE FROM user WHERE User='';</MEMBER>
- <MEMBER>UPDATE user SET Password=PASSWORD('new_password') WHERE user='root';</MEMBER>
- <MEMBER> FLUSH PRIVILEGES;</MEMBER>
- </SIMPLELIST>
- </PARA>
- <PARA>
- If you're not running "mit-pthreads" you can use:
- <SIMPLELIST>
- <MEMBER>GRANT USAGE ON *.* TO bugs@localhost;</MEMBER>
- <MEMBER>GRANT ALL ON bugs.* TO bugs@localhost;</MEMBER>
- <MEMBER>REVOKE DROP ON bugs.* FROM bugs@localhost;</MEMBER>
- <MEMBER>FLUSH PRIVILEGES;</MEMBER>
- </SIMPLELIST>
- </PARA>
- <PARA>
- With "mit-pthreads" you'll need to modify the "globals.pl" Mysql->Connect
- line to specify a specific host name instead of "localhost", and accept
- external connections:
- <SIMPLELIST>
- <MEMBER>GRANT USAGE ON *.* TO bugs@bounce.hop.com;</MEMBER>
- <MEMBER>GRANT ALL ON bugs.* TO bugs@bounce.hop.com;</MEMBER>
- <MEMBER>REVOKE DROP ON bugs.* FROM bugs@bounce.hop.com;</MEMBER>
- <MEMBER>FLUSH PRIVILEGES;</MEMBER>
- </SIMPLELIST>
- </PARA>
- <PARA>
- Consider also:
- <ORDEREDLIST>
- <LISTITEM>
- <PARA>
- Turning off external networking with "--skip-networking",
- unless you have "mit-pthreads", in which case you can't.
- Without networking, MySQL connects with a Unix domain socket.
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- using the --user= option to mysqld to run it as an unprivileged
- user.
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- starting MySQL in a chroot jail
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- running the httpd in a "chrooted" jail
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- making sure the MySQL passwords are different from the OS
- passwords (MySQL "root" has nothing to do with system "root").
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- running MySQL on a separate untrusted machine
- </PARA>
- </LISTITEM>
- <LISTITEM>
- <PARA>
- making backups ;-)
- </PARA>
- </LISTITEM>
- </ORDEREDLIST>
- </PARA>
- </SECTION>
-
- <SECTION>
- <TITLE>Installation General Notes</TITLE>
- <SECTION>
- <TITLE>Modifying Your Running System</TITLE>
- <PARA>
- Bugzilla optimizes database lookups by storing all relatively static
- information in the versioncache file, located in the data/ subdirectory
- under your installation directory (we said before it needs to be writable,
- right?!)
- </PARA>
- <PARA>
- If you make a change to the structural data in your database (the
- versions table for example), or to the "constants" encoded in
- defparams.pl, you will need to remove the cached content from the data
- directory (by doing a "rm data/versioncache"), or your changes won't show
- up!
- </PARA>
- <PARA>
- That file gets automatically regenerated whenever it's more than an
- hour old, so Bugzilla will eventually notice your changes by itself, but
- generally you want it to notice right away, so that you can test things.
- </PARA>
- </SECTION>
- <SECTION>
- <TITLE>Upgrading From Previous Versions</TITLE>
- <PARA>
- The developers of Bugzilla are constantly adding new tables, columns and
- fields. You'll get SQL errors if you just update the code. The strategy
- to update is to simply always run the checksetup.pl script whenever
- you upgrade your installation of Bugzilla. If you want to see what has
- changed, you can read the comments in that file, starting from the end.
- </PARA>
- </SECTION>
- <SECTION>
- <TITLE>UNIX Installation Instructions History</TITLE>
- <PARA>
- This document was originally adapted from the Bonsai installation
- instructions by Terry Weissman <terry@mozilla.org>.
- </PARA>
- <PARA>
- The February 25, 1999 re-write of this page was done by Ry4an Brase
- <ry4an@ry4an.org>, with some edits by Terry Weissman, Bryce Nesbitt,
- Martin Pool, & Dan Mosedale (But don't send bug reports to them!
- Report them using bugzilla, at http://bugzilla.mozilla.org/enter_bug.cgi ,
- project Webtools, component Bugzilla).
- </PARA>
- <PARA>
- This document was heavily modified again Wednesday, March 07 2001 to
- reflect changes for Bugzilla 2.12 release by Matthew P. Barnson. The
- securing MySQL section should be changed to become standard procedure
- for Bugzilla installations.
- </PARA>
- <PARA>
- Finally, the README in its entirety was marked up in SGML and included into
- the Guide on April 24, 2001.
- </PARA>
- <PARA>
- Comments from people using this Guide for the first time are particularly welcome.
- </PARA>
- </SECTION>
- </SECTION>
+ <section id="htaccess" xreflabel=".htaccess files and security">
+ <title><filename>.htaccess</filename> files and security</title>
+ <para>
+ To enhance the security of your Bugzilla installation,
+ Bugzilla will generate
+ <glossterm><filename>.htaccess</filename></glossterm> files
+ which the Apache webserver can use to restrict access to
+ the bugzilla data files. The checksetup script will
+ generate the <filename>.htaccess</filename> files.
+
+ <note>
+ <para>
+ If you are using an alternate provider of
+ <productname>webdot</productname> services for graphing
+ (as described when viewing
+ <filename>editparams.cgi</filename> in your web
+ browser), you will need to change the ip address in
+ <filename>data/webdot/.htaccess</filename> to the ip
+ address of the webdot server that you are using.
+ </para>
+ </note>
+
+ </para>
+ <para>
+ If you are using Internet Information Server or other web
+ server which does not observe <filename>.htaccess</filename>
+ conventions, you can disable their creation by editing
+ <filename>localconfig</filename> and setting the
+ <varname>$create_htaccess</varname> variable to
+ <parameter>0</parameter>.
+ </para>
+ </section>
- </SECTION>
- </SECTION>
+ <section id="mod_throttle" xreflabel="Using mod_throttle to prevent Denial of Service attacks">
+ <title><filename>mod_throttle</filename> and Security</title>
+ <para>
+ 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 <filename>mod_throttle</filename> which can limit
+ connections by ip-address. You may download this module at
+ <ulink
+ url="http://www.snert.com/Software/Throttle/">http://www.snert.com/Software/Throttle/</ulink>. Follow the instructions to install into your Apache install. <emphasis>This module only functions with the Apache web server!</emphasis>. You may use the <command>ThrottleClientIP</command> command provided by this module to accomplish this goal. See the <ulink url="http://www.snert.com/Software/Throttle/">Module Instructions</ulink> for more information. </para>
+ </section>
+
+ <section id="content_type" xreflabel="Preventing untrusted Bugzilla contentfrom executing malicious Javascript code">
+ <title>Preventing untrusted Bugzilla content from executing malicious Javascript code</title>
+ <para>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 <ulink
+ url="http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3">http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3</ulink>. 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. </para>
+ <para><programlisting>
+bash# cd $BUGZILLA_HOME; for i in `ls *.cgi`; \
+ do cat $i | sed 's/Content-type\: text\/html/Content-Type: text\/html\; charset=ISO-8859-1/' >$i.tmp; \
+ mv $i.tmp $i; done
+ </programlisting></para>
+ <para>
+ All this one-liner command does is search for all instances of
+ <quote>Content-type: text/html</quote> and replaces it with
+ <quote>Content-Type: text/html; charset=ISO-8859-1</quote>.
+ 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
+ <quote>ISO-8859-1</quote>, above, to <quote>UTF-8</quote>.
+ </para>
+ </section>
- <SECTION id="README.windows">
- <TITLE>Win32 (Win98+/NT/2K) Installation</TITLE>
- <PARA>
- These directions have <EMPHASIS>not</EMPHASIS> been extensively tested.
- We need testers! Please try these out and post any changes to the
- newsgroup.
- </PARA>
- <SECTION id="ntverified">
- <TITLE>Win32 Installation: Step-by-step</TITLE>
- <NOTE>
- <PARA>
- You should be familiar with, and cross-reference, the UNIX README
- while performing your Win32 installation. Unfortunately, Win32
- directions are not yet as detailed as those for UNIX.
- </PARA>
- <PARA>
- The <EMPHASIS>most critical</EMPHASIS> difference for Win32 users is
- the lack of support for a crypt() function in MySQL for Windows. It does not
- have it! All ENCRYPT statements must be modified.
- </PARA>
- </NOTE>
+
+ <section id="unixhistory">
+ <title>UNIX Installation Instructions History</title>
+ <para>
+ This document was originally adapted from the Bonsai
+ installation instructions by Terry Weissman
+ <terry@mozilla.org>.
+ </para>
+ <para>
+ The February 25, 1999 re-write of this page was done by Ry4an
+ Brase <ry4an@ry4an.org>, with some edits by Terry
+ Weissman, Bryce Nesbitt, Martin Pool, & Dan Mosedale (But
+ don't send bug reports to them; report them using bugzilla, at <ulink
+ url="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla">http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla</ulink> ).
+ </para>
+ <para>
+ This document was heavily modified again Wednesday, March 07
+ 2001 to reflect changes for Bugzilla 2.12 release by Matthew
+ P. Barnson. The securing MySQL section should be changed to
+ become standard procedure for Bugzilla installations.
+ </para>
+ <para>
+ Finally, the README in its entirety was marked up in SGML and
+ included into the Guide on April 24, 2001 by Matt Barnson.
+ Since that time, it's undergone extensive modification as
+ Bugzilla grew.
+ </para>
+ <para>
+ Comments from people using this Guide for the first time are
+ particularly welcome.
+ </para>
+ </section>
+ </section>
+
+ <section id="win32" xreflabel="Win32 Installation Notes">
+ <title>Win32 Installation Notes</title>
+ <para>This section covers installation on Microsoft Windows 95,
+ 98, ME, NT, and 2000. Bugzilla works fine on Win32 platforms,
+ but please remember that the Bugzilla team and the author of the
+ Guide neither endorse nor support installation on Microsoft
+ Windows. Bugzilla installs and runs <emphasis>best</emphasis>
+ and <emphasis>easiest</emphasis> on UNIX-like operating systems,
+ and that is the way it will stay for the foreseeable future. The
+ Bugzilla team is considering supporting Win32 for the 2.16
+ release and later.</para>
+ <para>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.</para>
- <PROCEDURE>
- <STEP>
- <PARA>
- Install <ULINK URL="http://www.apache.org/">Apache Web Server</ULINK>
- for Windows.
- </PARA>
- <NOTE>
- <PARA>
- You may also use Internet Information Server or Personal Web
- Server for this purpose. However, setup is slightly more
- difficult. If ActivePerl doesn't seem to handle your file
- associations correctly (for .cgi and .pl files), please
- consult the FAQ, in the "Win32" section.
- </PARA>
- <PARA>
- If you are going to use IIS, if on Windows NT you must be updated
- to at least Service Pack 4.
- </PARA>
- </NOTE>
- </STEP>
- <STEP>
- <PARA>
- Install <ULINK URL="http://www.activestate.com/">ActivePerl</ULINK>
- </PARA>
- <PARA>
+ <section id="wininstall" xreflabel="Win32 Installation: Step-by-step">
+ <title>Win32 Installation: Step-by-step</title>
+ <note>
+ <para>
+ You should be familiar with, and cross-reference, the rest
+ of the
+ <xref linkend="installation"> section while performing your
+ Win32 installation.
+ </para>
+ <para> Making Bugzilla work on Microsoft Windows is no
+ picnic. Support for Win32 has improved dramatically in the
+ last few releases, but, if you choose to proceed, you should
+ be a <emphasis>very</emphasis> skilled Windows Systems
+ Administrator with strong troubleshooting abilities, a high
+ tolerance for pain, and moderate perl skills. Bugzilla on NT
+ requires hacking source code and implementing some advanced
+ utilities. What follows is the recommended installation
+ procedure for Win32; additional suggestions are provided in
+ <xref linkend="faq">.
+ </para>
+ </note>
+
+ <procedure>
+ <step>
+ <para>
+ Install <ulink url="http://www.apache.org/">Apache Web
+ Server</ulink> for Windows, and copy the Bugzilla files
+ somewhere Apache can serve them. Please follow all the
+ instructions referenced in <xref linkend="installation">
+ regarding your Apache configuration, particularly
+ instructions regarding the <quote>AddHandler</quote>
+ parameter and <quote>ExecCGI</quote>.
+ </para>
+ <note>
+ <para>
+ 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 <xref linkend="faq">.
+ </para>
+ <para>
+ 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.
+ </para>
+ </note>
+ </step>
+ <step>
+ <para>
+ Install <ulink url="http://www.activestate.com/">ActivePerl</ulink> for Windows. Check <ulink url="http://aspn.activestate.com/ASPN/Downloads/ActivePerl/">http://aspn.activestate.com/ASPN/Downloads/ActivePerl</ulink> for a current compiled binary.
+ </para>
+ <para>
Please also check the following links to fully understand the status
of ActivePerl on Win32:
- <ULINK URL="http://language.perl.com/newdocs/pod/perlport.html">
- Perl Porting</ULINK>, and
- <ULINK URL="http://ftp.univie.ac.at/packages/perl/ports/nt/FAQ/perlwin32faq5.html">
- Hixie Click Here</ULINK>
- </PARA>
- </STEP>
- <STEP>
- <PARA>
+ <ulink url="http://language.perl.com/newdocs/pod/perlport.html">
+ Perl Porting</ulink>, and
+ <ulink url="http://ftp.univie.ac.at/packages/perl/ports/nt/FAQ/perlwin32faq5.html">
+ Perl on Win32 FAQ</ulink>
+ </para>
+ </step>
+ <step>
+ <para>
Use ppm from your perl\bin directory to install the following packs: DBI,
DBD-Mysql, TimeDate, Chart, Date-Calc, Date-Manip, and GD. You may need
to extract them from .zip format using Winzip or other unzip program first.
These additional ppm modules can be downloaded from ActiveState.
- </PARA>
- <PARA>
+ </para>
+ <note>
+ <para>
+ You can find a list of modules at
+ <ulink url="http://www.activestate.com/PPMPackages/zips/5xx-builds-only">
+ http://www.activestate.com/PPMPackages/zips/5xx-builds-only/</ulink>
+ </para>
+ </note>
+ <para>
The syntax for ppm is:
- <COMPUTEROUTPUT>
- <PROMPT>C:> </PROMPT><COMMAND>ppm install <module>.ppd</COMMAND>
- </COMPUTEROUTPUT>
- </PARA>
- <PARA>
+ <computeroutput>
+ <prompt>C:> </prompt><command>ppm <modulename></command>
+ </computeroutput>
+ </para>
+
+ <example>
+ <title>Installing ActivePerl ppd Modules on Microsoft Windows</title>
+ <para><prompt>C:></prompt><command>ppm
+ <option>DBD-Mysql</option></command></para>
+ <para>Watch your capitalization!</para>
+ </example>
+
+ <para>
You can find ActiveState ppm modules at
- <ULINK URL="http://www.activestate.com/PPMPackages/5.6plus/">
- http://www.activestate.com/PPMPackages/5.6plus</ULINK>
- </PARA>
- </STEP>
- <STEP>
- <PARA>
- Download and install the Windows GNU tools from
- <ULINK URL="http://www.cygwin.com/">www.cygwin.com</ULINK>.
- Make sure the GNU utilities are in your $PATH.
- </PARA>
- </STEP>
- <STEP>
- <PARA>
+ <ulink url="http://www.activestate.com/PPMPackages/5.6plus/">
+ http://www.activestate.com/PPMPackages/5.6plus</ulink>
+ </para>
+ </step>
+
+ <step>
+ <para>
Install MySQL for NT.
- <NOTE>
- <PARA>
- Your configuration file for MySQL <EMPHASIS>must</EMPHASIS> be named C:\MY.CNF.
- </PARA>
- </NOTE>
- </PARA>
- </STEP>
- <STEP>
- <PARA>
+ <note>
+ <para>
+ You can download MySQL for Windows NT from <ulink url="http://www.mysql.com/">MySQL.com</ulink>. Some find it helpful to use the WinMySqlAdmin utility, included with the download, to set up the database.
+ </para>
+ </note>
+ </para>
+ </step>
+ <step>
+ <para>
Setup MySQL
- </PARA>
- <SUBSTEPS>
- <STEP>
- <PARA>
- <COMPUTEROUTPUT>
- <PROMPT>C:> </PROMPT>
- <COMMAND>C:\mysql\bin\mysql -u root mysql</COMMAND>
- </COMPUTEROUTPUT>
- </PARA>
- </STEP>
- <STEP>
- <PARA>
- <COMPUTEROUTPUT>
- <PROMPT>mysql></PROMPT>
- <COMMAND>DELETE FROM user WHERE Host='localhost' AND User='';</COMMAND>
- </COMPUTEROUTPUT>
- </PARA>
- </STEP>
- <STEP>
- <PARA>
- <COMPUTEROUTPUT>
- <PROMPT>mysql></PROMPT>
- <COMMAND>UPDATE user SET Password=PASSWORD ('new_password')
- WHERE user='root';</COMMAND>
- </COMPUTEROUTPUT>
- </PARA>
- </STEP>
- <STEP>
- <PARA>
- <COMPUTEROUTPUT>
- <PROMPT>mysql></PROMPT>
- <COMMAND>GRANT SELECT, INSERT, UPDATE, DELETE,
+ </para>
+ <substeps>
+ <step>
+ <para>
+ <computeroutput>
+ <prompt>C:> </prompt>
+ <command>C:\mysql\bin\mysql -u root mysql</command>
+ </computeroutput>
+ </para>
+ </step>
+ <step>
+ <para>
+ <computeroutput>
+ <prompt>mysql></prompt>
+ <command>DELETE FROM user WHERE Host='localhost' AND User='';</command>
+ </computeroutput>
+ </para>
+ </step>
+ <step>
+ <para>
+ <computeroutput>
+ <prompt>mysql></prompt>
+ <command>UPDATE user SET Password=PASSWORD ('new_password')
+ WHERE user='root';</command>
+ </computeroutput>
+ </para>
+ <para><quote>new_password</quote>, above, indicates
+ whatever password you wish to use for your
+ <quote>root</quote> user.</para>
+ </step>
+ <step id="ntbugs-password">
+ <para>
+ <computeroutput>
+ <prompt>mysql></prompt>
+ <command>GRANT SELECT, INSERT, UPDATE, DELETE,
INDEX, ALTER, CREATE, DROP, REFERENCES
ON bugs.* to bugs@localhost
- IDENTIFIED BY 'bugs_password';</COMMAND>
- </COMPUTEROUTPUT>
- </PARA>
- </STEP>
- <STEP>
- <PARA>
- <COMPUTEROUTPUT>
- <PROMPT>mysql></PROMPT>
- <COMMAND>FLUSH PRIVILEGES;</COMMAND>
- </COMPUTEROUTPUT>
- </PARA>
- </STEP>
- <STEP>
- <PARA>
- <COMPUTEROUTPUT>
- <PROMPT>mysql></PROMPT>
- <COMMAND>create database bugs;</COMMAND>
- </COMPUTEROUTPUT>
- </PARA>
- </STEP>
- <STEP>
- <PARA>
- <COMPUTEROUTPUT>
- <PROMPT>mysql></PROMPT>
- <COMMAND>exit</COMMAND>
- </COMPUTEROUTPUT>
- </PARA>
- </STEP>
- <STEP>
- <PARA>
- <COMPUTEROUTPUT>
- <PROMPT>C:></PROMPT>
- <COMMAND>C:\mysql\bin\mysqladmin -u root -p reload</COMMAND>
- </COMPUTEROUTPUT>
- </PARA>
- </STEP>
- </SUBSTEPS>
- </STEP>
+ IDENTIFIED BY 'bugs_password';</command>
+ </computeroutput>
+ </para>
+ <para><quote>bugs_password</quote>, above, indicates
+ whatever password you wish to use for your
+ <quote>bugs</quote> user.</para>
+ </step>
+ <step>
+ <para>
+ <computeroutput>
+ <prompt>mysql></prompt>
+ <command>FLUSH PRIVILEGES;</command>
+ </computeroutput>
+ </para>
+ </step>
+ <step>
+ <para>
+ <computeroutput>
+ <prompt>mysql></prompt>
+ <command>create database bugs;</command>
+ </computeroutput>
+ </para>
+ </step>
+ <step>
+ <para>
+ <computeroutput>
+ <prompt>mysql></prompt>
+ <command>exit;</command>
+ </computeroutput>
+ </para>
+ </step>
+ <step>
+ <para>
+ <computeroutput>
+ <prompt>C:></prompt>
+ <command>C:\mysql\bin\mysqladmin -u root -p reload</command>
+ </computeroutput>
+ </para>
+ </step>
+ </substeps>
+ </step>
- <STEP>
- <PARA>
- Configure Bugzilla. For Win32, this involves editing "defparams.pl"
- and "localconfig" to taste. Running "checksetup.pl" should create
- localconfig for you. Note that getgrnam() doesn't work, and should be
- deleted. Change this line:
- "my $webservergid = getgrnam($my_webservergroup); "
+ <step>
+ <para>
+ Edit <filename>checksetup.pl</filename> in your Bugzilla directory. Change
+ this line:
+ </para>
+ <para>
+ <programlisting>
+my $webservergid = getgrnam($my_webservergroup);
+ </programlisting>
+ </para>
+ <para>
to
- "my $webservergid = $my_webservergroup; "
- </PARA>
- </STEP>
+ </para>
+ <para>
+ <programlisting>
+my $webservergid = $my_webservergroup;
+ </programlisting>
+or the name of the group you wish to own the files explicitly:
+ <programlisting>
+my $webservergid = 'Administrators'
+ </programlisting>
+ </para>
+ </step>
+
+ <step>
+ <para>
+ Run <filename>checksetup.pl</filename> from the Bugzilla directory.
+ </para>
+ </step>
- <STEP>
- <NOTE>
- <PARA>
+ <step>
+ <para>Edit <filename>localconfig</filename> to suit your
+ requirements. Set <varname>$db_pass</varname> to your
+ <quote>bugs_password</quote> from <xref linkend="ntbugs-password">, and <varname>$webservergroup</varname> to <quote>8</quote>.</para>
+ <note>
+ <para>Not sure on the <quote>8</quote> for
+ <varname>$webservergroup</varname> above. If it's
+ wrong, please send corrections.</para>
+ </note>
+ </step>
+
+ <step>
+ <para>
+ Edit <filename>defparams.pl</filename> to suit your
+ requirements. Particularly, set
+ <varname>DefParam("maintainer")</varname> and
+ <varname>DefParam("urlbase") to match your
+ install.</varname>
+ </para>
+ <note>
+ <para>This is yet another step I'm not sure of, since the
+ maintainer of this documentation does not maintain
+ Bugzilla on NT. If you can confirm or deny that this
+ step is required, please let me know.</para>
+ </note>
+ </step>
+
+ <step>
+ <note>
+ <para>
There are several alternatives to Sendmail that will work on Win32.
- The one mentioned here is a <EMPHASIS>suggestion</EMPHASIS>, not
+ The one mentioned here is a <emphasis>suggestion</emphasis>, not
a requirement. Some other mail packages that can work include
- <ULINK URL="http://www.blat.net/">BLAT</ULINK>,
- <ULINK URL="http://www.geocel.com/windmail/">Windmail</ULINK>,
- <ULINK URL="http://www.dynamicstate.com/">Mercury Sendmail</ULINK>,
+ <ulink url="http://www.blat.net/">BLAT</ulink>,
+ <ulink url="http://www.geocel.com/windmail/">Windmail</ulink>,
+ <ulink url="http://www.dynamicstate.com/">Mercury Sendmail</ulink>,
and the CPAN Net::SMTP Perl module (available in .ppm).
Every option requires some hacking of the Perl scripts for Bugzilla
to make it work. The option here simply requires the least.
- </PARA>
- </NOTE>
- <PARA>
- Download NTsendmail, available from<ULINK URL="http://www.ntsendmail.com/">
- www.ntsendmail.com</ULINK>. In order for it to work, you must set up some
- new environment variables (detailed on the ntsendmail home page). Figuring
- out where to put those variables is left as an exercise for the reader.
- 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)
- </PARA>
- <PARA>
- Once downloaded and installed, modify all open(SENDMAIL) calls to open
- "| c:\ntsendmail\ntsendmail -t" instead of "|/usr/lib/sendmail -t".
- </PARA>
- <NOTE>
- <PARA>
- We need someone to test this and make sure this works as advertised.
- </PARA>
- </NOTE>
- </STEP>
- <STEP>
- <PARA>
- Modify globals.pl and CGI.pl to remove the word "encrypt".
- </PARA>
- <NOTE>
- <PARA>
- I'm not sure this is all that is involved to remove crypt. Any
- NT Bugzilla hackers want to pipe up?
- </PARA>
- </NOTE>
- </STEP>
- <STEP>
- <PARA>
- Change all references to "processmail" to "processmail.pl" in
- all files, and rename "processmail" to "processmail.pl"
- </PARA>
- <NOTE>
- <PARA>
- I really think this may be a change we want to make for
+ </para>
+ </note>
+
+ <procedure>
+ <step>
+ <para>
+ Download NTsendmail, available from<ulink url="http://www.ntsendmail.com/"> www.ntsendmail.com</ulink>. 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)
+ </para>
+ </step>
+
+ <step>
+ <para>Put ntsendmail.pm into your .\perl\lib directory.</para>
+ </step>
+
+ <step>
+ <para>Add to globals.pl:</para>
+ <programlisting>
+# these settings configure the NTsendmail process
+use NTsendmail;
+$ENV{"NTsendmail"}="your.smtpserver.box";
+$ENV{"NTsendmail_debug"}=1;
+$ENV{"NTsendmail_max_tries"}=5;
+ </programlisting>
+ <note>
+ <para>
+ Some mention to also edit
+ <varname>$db_pass</varname> in
+ <filename>globals.pl</filename> to be your
+ <quote>bugs_password</quote>. Although this may get
+ you around some problem authenticating to your
+ database, since globals.pl is not normally
+ restricted by <filename>.htaccess</filename>, your
+ database password is exposed to whoever uses your
+ web server.
+ </para>
+ </note>
+ </step>
+
+ <step>
+ <para>
+ Find and comment out all occurences of
+ <quote><command>open(SENDMAIL</command></quote> in
+ your Bugzilla directory. Then replace them with:
+ <programlisting>
+# new sendmail functionality
+my $mail=new NTsendmail;
+my $from="bugzilla\@your.machine.name.tld";
+my $to=$login;
+my $subject=$urlbase;
+$mail->send($from,$to,$subject,$msg);
+ </programlisting>
+ </para>
+ <note>
+ <para>
+ Some have found success using the commercial product,
+ <productname>Windmail</productname>.
+ You could try replacing your sendmail calls with:
+ <programlisting>
+open SENDMAIL, "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t > mail.log";
+ </programlisting>
+ or something to that effect.
+ </para>
+ </note>
+ </step>
+ </procedure>
+ </step>
+
+ <step>
+ <para>
+ Change all references in all files from
+ <filename>processmail</filename> to
+ <filename>processmail.pl</filename>, and
+ rename <filename>processmail</filename> to
+ <filename>processmail.pl</filename>.
+ </para>
+ <note>
+ <para>
+ 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.
- </PARA>
- </NOTE>
- </STEP>
- <STEP>
- <PARA>
- 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.pl" utility to speed part of this procedure,
- available in the "Patches and Utilities" section of The Bugzilla Guide.
- </PARA>
- </STEP>
- <STEP>
- <PARA>
- In processmail.pl, add "binmode(HANDLE)" before all read() calls.
- This may not be necessary, but in some cases the read() under
- Win32 doesn't count the EOL's without using a binary read().
- </PARA>
- </STEP>
- </PROCEDURE>
+ </para>
+ </note>
+ <note>
+ <para>
+ 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.
+ <programlisting>
+<![CDATA[
+
+my $smtp = Net::SMTP->new('<Name of your SMTP server>'); #connect to SMTP server
+$smtp->mail('<your name>@<you smpt server>');# use the sender's adress here
+$smtp->to($tolist); # recipient's address
+$smtp->data(); # Start the mail
+$smtp->datasend($msg);
+$smtp->dataend(); # Finish sending the mail
+$smtp->quit; # Close the SMTP connection
+$logstr = "$logstr; mail sent to $tolist $cclist";
+}
+
+]]>
+</programlisting>
+here is a test mail program for Net::SMTP:
+<programlisting>
+<![CDATA[
+
+use Net::SMTP;
+ my $smtp = Net::SMTP->new('<Name of your SMTP server', Timeout => 30, Debug
+=> 1, ); # connect to SMTP server
+ $smtp->auth;
+ $smtp->mail('you@yourcompany.com');# use the sender's adress
+here
+ $smtp->to('someotherAddress@someotherdomain.com'); #
+recipient's address
+ $smtp->data(); # Start the mail
+ $smtp->datasend('test');
+ $smtp->dataend(); # Finish sending the mail
+ $smtp->quit; # Close the SMTP connection
+exit;
- </SECTION>
+]]>
+</programlisting>
+ </para>
+ </note>
+ </step>
+ <step>
+ <note>
+ <para>
+ This step is optional if you are using IIS or another
+ web server which only decides on an interpreter based
+ upon the file extension (.pl), rather than the
+ <quote>shebang</quote> line (#/usr/bonsaitools/bin/perl)
+ </para>
+ </note>
+ <para>
+ Modify the path to perl on the first line (#!) of all
+ files to point to your Perl installation, and add
+ <quote>perl</quote> 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 <quote>setperl.csh</quote>
+ utility to speed part of this procedure, available in the
+ <xref linkend="patches"> section of The Bugzilla Guide.
+ However, it requires the Cygwin GNU-compatible environment
+ for Win32 be set up in order to work. See <ulink url="http://www.cygwin.com/">http://www.cygwin.com/</ulink> for details on obtaining Cygwin.
+ </para>
+ </step>
- <SECTION id="addlwintips">
- <TITLE>Additional Windows Tips</TITLE>
- <TIP>
- <PARA>
+ <step>
+ <para>
+ Modify the invocation of all system() calls in all perl
+ scripts in your Bugzilla directory. For instance, change
+ this line in processmail:
+ <programlisting>
+system ("./processmail.pl",@ARGLIST);
+ </programlisting> to
+ <programlisting>
+system ("perl processmail.pl",@ARGLIST);
+ </programlisting>
+ </para>
+ </step>
+ <step>
+ <para>
+ Add <function>binmode()</function> calls so attachments
+ will work (<ulink
+ url="http://bugzilla.mozilla.org/show_bug.cgi?id=62000">bug 62000</ulink>).
+ </para>
+ <para>
+ Because Microsoft Windows based systems handle binary
+ files different than Unix based systems, you need to add
+ the following lines to
+ <filename>createattachment.cgi</filename> and
+ <filename>showattachment.cgi</filename> before the
+ <function>require 'CGI.pl';</function> line.
+</para>
+<para>
+<programlisting>
+<![CDATA[
+binmode(STDIN);
+binmode(STDOUT);
+]]>
+</programlisting>
+ </para>
+ <note>
+ <para>
+ According to <ulink
+ url="http://bugzilla.mozilla.org/show_bug.cgi?id=62000">bug 62000</ulink>, the perl documentation says that you should always use <function>binmode()</function> when dealing with binary files, but never when dealing with text files. That seems to suggest that rather than aribtrarily putting <function>binmode()</function> at the begining of the attachment files, there should be logic to determine if <function>binmode()</function> is needed or not.
+ </para>
+ </note>
+ </step>
+ </procedure>
+
+ <tip>
+ <para>
+ 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:
+ </para>
+ <para>
+ <programlisting>
+.cgi to: <perl install directory>\perl.exe %s %s
+.pl to: <perl install directory>\perl.exe %s %s
+GET,HEAD,POST
+ </programlisting>
+ Change the path to Perl to match your
+ install, of course.
+ </para>
+ </tip>
+ </section>
+
+ <section id="addlwintips">
+ <title>Additional Windows Tips</title>
+ <tip>
+ <para>
From Andrew Pearson:
- <BLOCKQUOTE>
- <PARA>
- "You can make Bugzilla work with Personal Web Server for
- Windows 98 and higher, as well as for IIS 4.0. Microsoft has
- information available at
- <ULINK URL=" http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP">
- http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP</ULINK>
- </PARA>
- <PARA>
+ <blockquote>
+ <para>
+ You can make Bugzilla work with Personal Web Server for
+ Windows 98 and higher, as well as for IIS 4.0.
+ Microsoft has information available at <ulink url="
+ http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP"> http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP</ulink>
+ </para>
+ <para>
Basically you need to add two String Keys in the
registry at the following location:
- </PARA>
- <PARA>
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\ScriptMap
- </PARA>
- <PARA>
+ </para>
+ <para>
+ <programlisting>
+HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\ScriptMap
+ </programlisting>
+ </para>
+ <para>
The keys should be called ".pl" and ".cgi", and both
should have a value something like:
- <COMMAND>c:/perl/bin/perl.exe "%s" "%s"</COMMAND>
- </PARA>
- <PARA>
+ <command>c:/perl/bin/perl.exe "%s" "%s"</command>
+ </para>
+ <para>
The KB article only talks about .pl, but it goes into
more detail and provides a perl test script.
- </PARA>
- </BLOCKQUOTE>
- </PARA>
- </TIP>
- <TIP>
- <PARA>"Brian" had this to add, about upgrading to Bugzilla 2.12 from previous versions:</PARA>
- <BLOCKQUOTE>
- <PARA>
- Hi - I am updating bugzilla to 2.12 so I can tell you what I did (after I
- deleted the current dir and copied the files in).
- </PARA>
- <PARA>
- In checksetup.pl, I did the following...
- </PARA>
- <PROCEDURE>
- <STEP>
- <PROGRAMLISTING>
-my $webservergid = getgrnam($my_webservergroup);
- </PROGRAMLISTING>
- <PARA>to</PARA>
- <PROGRAMLISTING>
-my $webservergid = 'Administrators'
- </PROGRAMLISTING>
- </STEP>
- <STEP>
- <PARA>
- I then ran checksetup.pl
- </PARA>
- </STEP>
- <STEP>
- <PARA>
- I removed all the encrypt()
- <EXAMPLE>
- <TITLE>Removing encrypt() for Windows NT installations</TITLE>
- <PARA>
- Replace this:
- <PROGRAMLISTING>
-SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " .
- SqlQuote(substr($realcryptpwd, 0, 2)) . ")");
+ </para>
+ </blockquote>
+ </para>
+ </tip>
+ <tip>
+ <para>
+ If attempting to run Bugzilla 2.12 or older, you will need
+ to remove encrypt() calls from the Perl source. This is
+ <emphasis>not necessary</emphasis> for Bugzilla 2.13 and
+ later, which includes the current release, Bugzilla
+ &bz-ver;.
+ <example>
+ <title>Removing encrypt() for Windows NT Bugzilla version
+ 2.12 or earlier</title>
+ <para>
+ Replace this:
+ <programlisting>
+SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " . SQLQuote(substr($realcryptpwd, 0, 2)) . ")");
my $enteredcryptpwd = FetchOneColumn();
- </PROGRAMLISTING>
- with this:
- <PROGRAMLISTING>
-my $enteredcryptpwd = $enteredpwd
- </PROGRAMLISTING>
- in cgi.pl.
- </PARA>
- </EXAMPLE>
- </PARA>
- </STEP>
- <STEP>
- <PARA>
- I renamed processmail to processmail.pl
- </PARA>
- </STEP>
- <STEP>
- <PARA>
- I altered the sendmail statements to windmail:
- <PROGRAMLISTING>
-open SENDMAIL, "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t > mail.log";
- </PROGRAMLISTING>
- </PARA>
- <PARA>
- The quotes around the dir is for the spaces. mail.log is for the output
- </PARA>
- </STEP>
- </PROCEDURE>
- </BLOCKQUOTE>
- </TIP>
- </SECTION>
- </SECTION>
-</CHAPTER>
+ </programlisting>
+with this:
+ <programlisting>
+my $enteredcryptpwd = $enteredpwd
+ </programlisting>
+ in cgi.pl.
+ </para>
+ </example>
+ </para>
+ </tip>
+ </section>
+
+ <section id="bzldap">
+ <title>Bugzilla LDAP Integration</title>
+ <para>
+ What follows is some late-breaking information on using the
+ LDAP authentication options with Bugzilla. The author has not
+ tested these (nor even formatted this section!) so please
+ contribute feedback to the newsgroup.
+ </para>
+ <literallayout>
+Mozilla::LDAP module
+
+The Mozilla::LDAP module allows you to use LDAP for authentication to
+the Bugzilla system. This module is not required if you are not using
+LDAP.
+
+Mozilla::LDAP (aka PerLDAP) is available for download from
+http://www.mozilla.org/directory.
+
+NOTE: The Mozilla::LDAP module requires Netscape's Directory SDK.
+Follow the link for "Directory SDK for C" on that same page to
+download the SDK first. After you have installed this SDK, then
+install the PerLDAP module.
+----------------------------------------------------------------------
+
+Post-Installation Checklist
+----------------------------------------------------------------------
+Set 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 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
+servers available, this is "mail", but you may need to change this.
+----------------------------------------------------------------------
+(Not sure where this bit should go, but it's important that it be in
+there somewhere...)
+----------------------------------------------------------------------
+Using LDAP authentication for Bugzilla:
+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. 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 tasks are still handled
+by email address, not LDAP username. You still assign bugs by email
+address, query on users by email address, etc.
+----------------------------------------------------------------------
+ </literallayout>
+ </section>
+ </section>
+</chapter>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
-sgml-omittag:t
-sgml-shorttag:t
-sgml-namecase-general:t
-sgml-general-insert-case:upper
-sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
-sgml-indent-step:2
-sgml-indent-data:t
-sgml-parent-document:nil
+sgml-auto-insert-required-elements:t
+sgml-balanced-tag-edit:t
sgml-exposed-tags:nil
+sgml-general-insert-case:lower
+sgml-indent-data:t
+sgml-indent-step:2
sgml-local-catalogs:nil
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-shorttag:t
+sgml-tag-region-if-active:t
End:
-->
diff --git a/docs/sgml/integration.sgml b/docs/sgml/integration.sgml
index 74ec817f5..36cc617e2 100644
--- a/docs/sgml/integration.sgml
+++ b/docs/sgml/integration.sgml
@@ -1,75 +1,95 @@
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" >
+<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" > -->
<!-- Keep these tools listings in alphabetical order please. -MPB -->
<chapter id="integration">
<title>Integrating Bugzilla with Third-Party Tools</title>
- <section id="bonsai">
+ <section id="bonsai" xreflabel="Bonsai, the Mozilla automated CVS management system">
<title>Bonsai</title>
- <para>We need Bonsai integration information.</para>
+ <para>Bonsai is a web-based tool for managing <xref
+ linkend="cvs">
+ . 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. These kinds of changes cause the
+ engineer responsible to be <quote>on the hook</quote> (include
+ cool URL link here for Hook policies at mozilla.org). Bonsai
+ also includes gateways to <xref
+ linkend="tinderbox"> and Bugzilla </para>
</section>
- <section id="cvs">
+ <section id="cvs" xreflabel="CVS, the Concurrent Versioning System">
<title>CVS</title>
- <para>We need CVS integration information</para>
+ <para>CVS integration is best accomplished, at this point, using
+ the Bugzilla Email Gateway. There have been some files
+ submitted to allow greater CVS integration, but we need to make
+ certain that Bugzilla is not tied into one particular software
+ management package.</para>
+ <para>
+ Follow the instructions in the FAQ 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 <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>
+ <para>
+ There is also a project, based upon somewhat dated Bugzilla
+ code, to integrate CVS and Bugzilla through CVS' ability to
+ email. Check it out at:
+ <ulink url="http://homepages.kcbbs.gen.nz/~tonyg/">
+ http://homepages.kcbbs.gen.nz/~tonyg/</ulink>, under the
+ <quote>cvszilla</quote> link.
+ </para>
</section>
- <section id="scm">
+ <section id="scm" xreflabel="Perforce SCM (Fast Software Configuration Management System, a powerful commercial alternative to CVS">
<title>Perforce SCM</title>
<para>
- Richard Brooksby created a Perforce integration tool for Bugzilla and TeamTrack.
- You can find the main project page at
- <ulink url="http://www.ravenbrook.com/project/p4dti/">
- http://www.ravenbrook.com/project/p4dti</ulink>. "p4dti" is now an officially
- supported product from Perforce, and you can find the "Perforce Public Depot"
- p4dti page at <ulink url="http://public.perforce.com/public/perforce/p4dti/index.html">
- http://public.perforce.com/public/perforce/p4dti/index.html</ulink>.
- </para>
- <para>
- Integration of Perforce with Bugzilla, once patches are applied, is fairly seamless. However,
- p4dti is a patch against the Bugzilla 2.10 release, not the current 2.12 release. I anticipate
- patches for 2.12 will be out shortly. Check the project page regularly for updates, or
- take the given patches and patch it manually. p4dti is designed to support multiple defect
- trackers, and maintains its own documentation for it. Please consult the pages linked
- above for further information.
+ You can find the project page for Bugzilla and Teamtrack
+ Perforce integration (p4dti) at: <ulink
+ url="http://www.ravenbrook.com/project/p4dti/"> http://www.ravenbrook.com/project/p4dti</ulink> . <quote>p4dti</quote> is now an officially supported product from Perforce, and you can find the "Perforce Public Depot" p4dti page at <ulink url="http://public.perforce.com/public/perforce/p4dti/index.html"> http://public.perforce.com/public/perforce/p4dti/index.html</ulink>.
</para>
<para>
- Right now, there is no way to synchronize the Bug ID and the Perforce Transaction Number, or
- to change the Bug ID to read (PRODUCT).bugID unless you hack it in. Additionally, if you
- have synchronization problems, the easiest way to avoid them is to only put the bug
- information, comments, etc. into Bugzilla, and not into the Perforce change records.
- They will link anyway; merely reference the bug ID fixed in your change description,
- and put a comment into Bugzilla
- giving the change ID that fixed the Bugzilla bug. It's a process issue, not a technology
- question.
+ 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.
</para>
</section>
- <section id="tinderbox">
- <title>Tinderbox</title>
- <para>We need Tinderbox integration information</para>
+ <section id="tinderbox" xreflabel="Tinderbox, the Mozilla automated build management system">
+ <title>Tinderbox/Tinderbox2</title>
+ <para>We need Tinderbox integration information.</para>
</section>
</chapter>
+
+
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
-sgml-omittag:t
-sgml-shorttag:t
-sgml-namecase-general:t
-sgml-general-insert-case:lower
-sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
-sgml-indent-step:2
-sgml-indent-data:t
-sgml-parent-document:nil
+sgml-auto-insert-required-elements:t
+sgml-balanced-tag-edit:t
sgml-exposed-tags:nil
+sgml-general-insert-case:lower
+sgml-indent-data:t
+sgml-indent-step:2
sgml-local-catalogs:nil
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-shorttag:t
+sgml-tag-region-if-active:t
End:
-->
-
-
diff --git a/docs/sgml/patches.sgml b/docs/sgml/patches.sgml
index 8d7a72682..3f49255f2 100644
--- a/docs/sgml/patches.sgml
+++ b/docs/sgml/patches.sgml
@@ -1,15 +1,48 @@
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
+<!-- <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
-<appendix id="patches">
+<appendix id="patches" xreflabel="Useful Patches and Utilities for Bugzilla">
<title>Useful Patches and Utilities for Bugzilla</title>
-<section id="setperl">
+ <para>Are you looking for a way to put your Bugzilla into overdrive? Catch some of the niftiest tricks here in this section.</para>
+
+ <section id="rewrite" xreflabel="Apache mod_rewrite magic">
+ <title>Apache <filename>mod_rewrite</filename> magic</title>
+ <para>Apache's <filename>mod_rewrite</filename> module lets you do some truly amazing things with URL rewriting. Here are a couple of examples of what you can do.</para>
+ <orderedlist>
+ <listitem>
+ <para>
+ Make it so if someone types
+ <computeroutput>http://www.foo.com/12345</computeroutput>,
+ 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:</para>
+ <programlisting>
+<![CDATA[
+<VirtualHost 12.34.56.78>
+RewriteEngine On
+RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R]
+</VirtualHost>
+]]>
+ </programlisting>
+
+ </listitem>
+ <listitem>
+ <para>There are many, many more things you can do with
+ mod_rewrite. As time goes on, I will include many more in
+ the Guide. For now, though, please refer to the mod_rewrite
+ documentation at <ulink
+ url="http://www.apache.org">http://www.apache.org</ulink></para>
+ </listitem>
+ </orderedlist>
+ </section>
+
+<section id="setperl" xreflabel="The setperl.csh Utility">
<title>The setperl.csh Utility</title>
- <para>
- You can use the "setperl.csh" utility to quickly and easily
- change the path to perl on all your Bugzilla files.
- This is a C-shell script; if you do not have "csh" or "tcsh" in the search
- path on your system, it will not work!
+ <para> You can use the "setperl.csh" utility to quickly and
+ easily change the path to perl on all your Bugzilla files. This
+ is a C-shell script; if you do not have "csh" or "tcsh" in the
+ search path on your system, it will not work!
</para>
<procedure>
<step>
@@ -28,18 +61,15 @@
</step>
<step>
<para>
- <computeroutput>
- <prompt>bash#</prompt>
- <command>wget -O setperl.csh 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'</command>
- </computeroutput>
+ <computeroutput> <prompt>bash#</prompt> <command>wget -O
+ setperl.csh
+ 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'</command> </computeroutput>
</para>
</step>
<step>
<para>
- <computeroutput>
- <prompt>bash#</prompt>
- <command>chmod u+x setperl.csh</command>
- </computeroutput>
+ <computeroutput> <prompt>bash#</prompt> <command>chmod
+ u+x setperl.csh</command> </computeroutput>
</para>
</step>
</substeps>
@@ -59,10 +89,8 @@
</step>
<step>
<para>
- <computeroutput>
- <prompt>bash#</prompt>
- <command>chmod u+x duplicates.cgi</command>
- </computeroutput>
+ <computeroutput> <prompt>bash#</prompt> <command>chmod
+ u+x duplicates.cgi</command> </computeroutput>
</para>
</step>
<step>
@@ -80,16 +108,14 @@
Run the script:
</para>
<para>
- <computeroutput>
- <prompt>bash#</prompt>
+ <computeroutput> <prompt>bash#</prompt>
<command>./setperl.csh /your/path/to/perl</command>
</computeroutput>
<example>
<title>Using Setperl to set your perl path</title>
<para>
- <computeroutput>
- <prompt>bash#</prompt>
- <command>./setperl.csh /usr/bin/perl</command>
+ <computeroutput> <prompt>bash#</prompt>
+ <command>./setperl.csh /usr/bin/perl</command>
</computeroutput>
</para>
</example>
@@ -101,22 +127,23 @@
<section id="cmdline">
<title>Command-line Bugzilla Queries</title>
<para>
- Users can query Bugzilla from the command line using
- this suite of utilities.
+ Users can query Bugzilla from the command line using this suite
+ of utilities.
</para>
<para>
The query.conf file 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"
+ 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"
</para>
<para>
- 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=".
+ 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=".
</para>
<para>
The columlist is taken from the COLUMNLIST environment variable.
@@ -128,10 +155,10 @@
<para>
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
- <command>sed -e 's/,/ /g' | wc | awk '{printf $2 "\n"}'</command>
+ "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 <command>sed -e 's/,/ /g' | wc |
+ awk '{printf $2 "\n"}'</command>
</para>
<para>
Akkana says she has good results piping buglist output through
@@ -145,26 +172,23 @@
<substeps>
<step>
<para>
- <computeroutput>
- <prompt>bash$</prompt>
- <command>wget -O query.conf 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26157'</command>
- </computeroutput>
+ <computeroutput> <prompt>bash$</prompt> <command>wget -O
+ query.conf
+ 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26157'</command> </computeroutput>
</para>
</step>
<step>
<para>
- <computeroutput>
- <prompt>bash$</prompt>
- <command>wget -O buglist 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26944'</command>
- </computeroutput>
+ <computeroutput> <prompt>bash$</prompt> <command>wget -O
+ buglist
+ 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26944'</command> </computeroutput>
</para>
</step>
<step>
<para>
- <computeroutput>
- <prompt>bash#</prompt>
- <command>wget -O bugs 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26215'</command>
- </computeroutput>
+ <computeroutput> <prompt>bash#</prompt> <command>wget -O
+ bugs
+ 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26215'</command> </computeroutput>
</para>
</step>
</substeps>
@@ -185,53 +209,162 @@
<title>The Quicksearch Utility</title>
<para>
Quicksearch is a new, experimental feature of the 2.12 release.
- It consist of two Javascript files, "quicksearch.js" and "localconfig.js",
- and two documentation files, "quicksearch.html" and "quicksearchhack.html"
+ It consist of two Javascript files, "quicksearch.js" and
+ "localconfig.js", and two documentation files,
+ "quicksearch.html" and "quicksearchhack.html"
</para>
<para>
- The index.html page has been updated to include the QuickSearch text box.
+ The index.html page has been updated to include the QuickSearch
+ text box.
</para>
<para>
- To take full advantage of the query power, the Bugzilla maintainer must
- edit "localconfig.js" according to the value sets used in the local installation.
+ To take full advantage of the query power, the Bugzilla
+ maintainer must edit "localconfig.js" according to the value
+ sets used in the local installation.
</para>
<para>
- Currently, keywords must be hard-coded in localconfig.js. If they are not,
- keywords are not automatically recognized. This means, if localconfig.js
- is left unconfigured, that searching for a bug with the "foo" keyword
- will only find bugs with "foo" in the summary, status whiteboard, product or
- component name, but not those with the keyword "foo".
+ Currently, keywords must be hard-coded in localconfig.js. If
+ they are not, keywords are not automatically recognized. This
+ means, if localconfig.js is left unconfigured, that searching
+ for a bug with the "foo" keyword will only find bugs with "foo"
+ in the summary, status whiteboard, product or component name,
+ but not those with the keyword "foo".
</para>
<para>
Workarounds for Bugzilla users:
<simplelist>
- <member>search for '!foo' (this will find only bugs with the keyword "foo"</member>
- <member>search 'foo,!foo' (equivalent to 'foo OR keyword:foo')</member>
+ <member>search for '!foo' (this will find only bugs with the
+ keyword "foo"</member>
+ <member>search 'foo,!foo' (equivalent to 'foo OR
+ keyword:foo')</member>
</simplelist>
</para>
<para>
- When this tool is ported from client-side JavaScript to server-side Perl,
- the requirement for hard-coding keywords can be fixed.
- <ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=70907">This bug</ulink>
- has details.
+ When this tool is ported from client-side JavaScript to
+ server-side Perl, the requirement for hard-coding keywords can
+ be fixed. <ulink
+ url="http://bugzilla.mozilla.org/show_bug.cgi?id=70907">This bug</ulink> has details.
</para>
</section>
+ <section id="bzhacking">
+ <title>Hacking Bugzilla</title>
+ <para>
+ What follows are some general guidelines for changing Bugzilla, and adhering to good coding practice while doing so. We've had some checkins in the past which ruined Bugzilla installations because of disregard for these conventions. Sorry for the lack of formatting; I got this info into the Guide on the day of 2.14 release and haven't formatted it yet.
+ </para>
+ <literallayout>
+
+The following is a guide for reviewers when checking code into Bugzilla's
+CVS repostory at mozilla.org. If you wish to submit patches to Bugzilla,
+you should follow the rules and style conventions below. Any code that
+does not adhere to these basic rules will not be added to Bugzilla's
+codebase.
+
+ 1. Usage of variables in Regular Expressions
+
+ It is very important that you don't use a variable in a regular
+ expression unless that variable is supposed to contain an expression.
+ This especially applies when using grep. You should use:
+
+ grep ($_ eq $value, @array);
+
+ - NOT -
+
+ grep (/$value/, @array);
+
+ If you need to use a non-expression variable inside of an expression, be
+ sure to quote it properly (using \Q..\E).
+
+Coding Style for Bugzilla
+-------------------------
+
+While it's true that not all of the code currently in Bugzilla adheres to
+this styleguide, it is something that is being worked toward. Therefore,
+we ask that all new code (submitted patches and new files) follow this guide
+as closely as possible (if you're only changing 1 or 2 lines, you don't have
+to reformat the entire file :).
+
+ 1. Whitespace
+
+ Bugzilla's prefered indentation is 4 spaces (no tabs, please).
+
+ 2. Curly braces.
+
+ The opening brace of a block should be on the same line as the statement
+ that is causing the block and the closing brace should be at the same
+ indentation level as that statement, for example:
+
+ if ($var) {
+ print "The variable is true";
+ } else {
+ print "Try again";
+ }
+
+ - NOT -
+
+ if ($var)
+ {
+ print "The variable is true";
+ }
+ else
+ {
+ print "Try again";
+ }
+
+ 3. File Names
+
+ File names for bugzilla code and support documention should be legal across
+ multiple platforms. \ / : * ? " < > and | are all illegal characters for
+ filenames on various platforms. Also, file names should not have spaces in
+ them as they can cause confusion in CVS and other mozilla.org utilities.
+
+ 4. Variable Names
+
+ If a variable is scoped globally ($::variable) its name should be descriptive
+ of what it contains. Local variables can be named a bit looser, provided the
+ context makes their content obvious. For example, $ret could be used as a
+ staging variable for a routine's return value as the line |return $ret;| will
+ make it blatently obvious what the variable holds and most likely be shown
+ on the same screen as |my $ret = "";|.
+
+ 5. Cross Database Compatability
+
+ Bugzilla was originally written to work with MySQL and therefore took advantage
+ of some of its features that aren't contained in other RDBMS software. These
+ should be avoided in all new code. Examples of these features are enums and
+ encrypt().
+
+ 6. Cross Platform Compatability
+
+ While Bugzilla was written to be used on Unix based systems (and Unix/Linux is
+ still the only officially supported platform) there are many who desire/need to
+ run Bugzilla on Microsoft Windows boxes. Whenever possible, we should strive
+ not to make the lives of these people any more complicated and avoid doing things
+ that break Bugzilla's ability to run on multiple operating systems.
+
+ </literallayout>
+ </section>
+
</appendix>
+
+
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
-sgml-omittag:t
-sgml-shorttag:t
-sgml-namecase-general:t
-sgml-general-insert-case:lower
-sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
-sgml-indent-step:2
-sgml-indent-data:t
-sgml-parent-document:nil
+sgml-auto-insert-required-elements:t
+sgml-balanced-tag-edit:t
sgml-exposed-tags:nil
+sgml-general-insert-case:lower
+sgml-indent-data:t
+sgml-indent-step:2
sgml-local-catalogs:nil
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-shorttag:t
+sgml-tag-region-if-active:t
End:
-->
diff --git a/docs/sgml/requiredsoftware.sgml b/docs/sgml/requiredsoftware.sgml
index 2d819ab62..e36b6184a 100644
--- a/docs/sgml/requiredsoftware.sgml
+++ b/docs/sgml/requiredsoftware.sgml
@@ -1,4 +1,4 @@
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
+<!-- <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
<appendix id="downloadlinks">
<title>Software Download Links</title>
@@ -15,7 +15,7 @@
http://www.mozilla.org/projects/bugzilla/</ulink>
</para>
<para>
- MySQL: <ulink url="http://www.mysql.org/">http://www.mysql.org/</ulink>
+ MySQL: <ulink url="http://www.mysql.com/">http://www.mysql.com/</ulink>
</para>
<para>
Perl: <ulink url="http://www.perl.org">http://www.perl.org/</ulink>
@@ -63,20 +63,24 @@
</appendix>
+
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
-sgml-omittag:t
-sgml-shorttag:t
-sgml-namecase-general:t
-sgml-general-insert-case:lower
-sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
-sgml-indent-step:2
-sgml-indent-data:t
-sgml-parent-document:nil
+sgml-auto-insert-required-elements:t
+sgml-balanced-tag-edit:t
sgml-exposed-tags:nil
+sgml-general-insert-case:lower
+sgml-indent-data:t
+sgml-indent-step:2
sgml-local-catalogs:nil
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-shorttag:t
+sgml-tag-region-if-active:t
End:
-->
diff --git a/docs/sgml/using.sgml b/docs/sgml/using.sgml
index bc8159835..934817081 100644
--- a/docs/sgml/using.sgml
+++ b/docs/sgml/using.sgml
@@ -1,4 +1,4 @@
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
+<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
<!-- TOC
Chapter: Using Bugzilla
@@ -31,26 +31,26 @@ Chapter: Using Bugzilla
<title>Using Bugzilla</title>
<epigraph>
<para>
- What, Why, How, & What's in it for me?
+ What, Why, How, & Where?
</para>
</epigraph>
<section id="whatis">
<title>What is Bugzilla?</title>
<para>
- Bugzilla is one example of a class of programs called "Defect Tracking Systems",
- or, more commonly, "Bug-Tracking Systems". Defect Tracking Systems allow individual or
- groups of developers to keep track of outstanding bugs in their product effectively.
- Bugzilla was originally written by Terry Weissman in a programming language called
- "TCL", to replace a crappy
- bug-tracking database used internally for Netscape Communications. Terry later ported
- Bugzilla to
- Perl from TCL, and in Perl it remains to this day.
- Most commercial defect-tracking software vendors at the
- time charged enormous licensing fees, and Bugzilla quickly became a favorite of the
- open-source crowd (with its genesis in the open-source browser project, Mozilla). It
- is now the de-facto standard defect-tracking system against which all others are
- measured.
+ Bugzilla is one example of a class of programs called "Defect
+Tracking Systems", or, more commonly, "Bug-Tracking Systems". Defect
+Tracking Systems allow individual or groups of developers to keep
+track of outstanding bugs in their product effectively. Bugzilla was
+originally written by Terry Weissman in a programming language called
+"TCL", to replace a crappy bug-tracking database used internally for
+Netscape Communications. Terry later ported Bugzilla to Perl from
+TCL, and in Perl it remains to this day. Most commercial
+defect-tracking software vendors at the time charged enormous
+licensing fees, and Bugzilla quickly became a favorite of the
+open-source crowd (with its genesis in the open-source browser
+project, Mozilla). It is now the de-facto standard defect-tracking
+system against which all others are measured.
</para>
<para>
Bugzilla has matured immensely, and now boasts many advanced features. These include:
@@ -87,13 +87,15 @@ Chapter: Using Bugzilla
</listitem>
<listitem>
<para>
- email, XML, and HTTP APIs
+ email, XML, console, and HTTP APIs
</para>
</listitem>
<listitem>
<para>
- available integration with automated software configuration management systems, including
- Perforce and CVS.
+ available integration with automated software
+ configuration management systems, including Perforce and
+ CVS (through the Bugzilla email interface and
+ checkin/checkout scripts)
</para>
</listitem>
<listitem>
@@ -104,23 +106,28 @@ Chapter: Using Bugzilla
</itemizedlist>
</para>
<para>
- Despite its current robustness and popularity, however, Bugzilla
- faces some near-term challenges, such as reliance on a single database, a lack of
- abstraction of the user interface and program logic, verbose email bug
- notifications, a powerful but daunting query interface, little reporting configurability,
- problems with extremely large queries, some unsupportable bug resolution options,
- no internationalization, and dependence on some nonstandard libraries.
+ Despite its current robustness and popularity, Bugzilla faces
+ some near-term challenges, such as reliance on a single
+ database, a lack of abstraction of the user interface and
+ program logic, verbose email bug notifications, a powerful but
+ daunting query interface, little reporting configurability,
+ problems with extremely large queries, some unsupportable bug
+ resolution options, little internationalization (although non-US
+ character sets are accepted for comments), and dependence on
+ some nonstandard libraries.
</para>
<para>
- Some recent headway has been made on the query front, however. If you are using the latest
- version of Bugzilla, you should see a "simple search" form on the default front page of
- your Bugzilla install. Type in two or three search terms and you should pull up some
- relevant information. This is also available as "queryhelp.cgi".
+ Some recent headway has been made on the query front, however.
+ If you are using the latest version of Bugzilla, you should see
+ a <quote>simple search</quote> form on the default front page of
+ your Bugzilla install. Type in two or three search terms and
+ you should pull up some relevant information. This is also
+ available as "queryhelp.cgi".
</para>
<para>
- Despite these small problems, Bugzilla is very hard to beat. It is under <emphasis>very</emphasis>
- active development to address the current issues, and a long-awaited overhaul in the form
- of Bugzilla 3.0 is expected sometime later this year.
+ Despite these small problems, Bugzilla is very hard to beat. It
+ is under <emphasis>very</emphasis> active development to address
+ the current issues, and continually gains new features.
</para>
</section>
@@ -132,50 +139,57 @@ Chapter: Using Bugzilla
</para>
</epigraph>
<para>
- 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
+ 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.
</para>
<para>
- 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.
+ 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.
</para>
<para>
But why should <emphasis>you</emphasis> use Bugzilla?
</para>
<para>
- 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, Loki software,
- Linux-Mandrake, and VA Systems. Combined with systems such as CVS, Bonsai,
- or Perforce SCM, Bugzilla provides a powerful, easy-to-use solution to
- configuration management and replication problems
+ Bugzilla 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, Loki
+ software, Linux-Mandrake, and VA Systems. Combined with systems
+ such as CVS, Bonsai, or Perforce SCM, Bugzilla provides a
+ powerful, easy-to-use solution to configuration management and
+ replication problems
</para>
<para>
- 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 by using Bugzilla's e-mail integration features
- be able to follow the discussion trail that led to critical decisions.
+ 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 <emphasis>something</emphasis> 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 by using Bugzilla's e-mail
+ integration features be able to follow the discussion trail that
+ led to critical decisions.
</para>
<para>
- 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.
+ 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.
</para>
</section>
@@ -189,46 +203,45 @@ Chapter: Using Bugzilla
<para>
Bugzilla is a large, complex system. Describing how to use it
- requires some time. If you are only interested in installing or administering
- a Bugzilla installation, please consult the Installing and Administering
- Bugzilla portions of this Guide. This section is principally aimed towards
- developing end-user mastery of Bugzilla, so you may fully enjoy the benefits
- afforded by using this reliable open-source bug-tracking software.
+ requires some time. If you are only interested in installing or
+ administering a Bugzilla installation, please consult the
+ Installing and Administering Bugzilla portions of this Guide.
+ This section is principally aimed towards developing end-user
+ mastery of Bugzilla, so you may fully enjoy the benefits
+ afforded by using this reliable open-source bug-tracking
+ software.
</para>
<para>
- Throughout this portion of the Guide, we will refer to user account
- options available at the Bugzilla test installation,
+ Throughout this portion of the Guide, we will refer to user
+ account options available at the Bugzilla test installation,
<ulink url="http://landfill.tequilarista.org/">
- landfill.tequilarista.org</ulink>.
+ landfill.tequilarista.org</ulink>.
<note>
<para>
- Some people have run into difficulties completing this tutorial. If
- you run into problems, please check the updated, online documentation available
- at <ulink url="http://www.trilobyte.net/barnsons/">http://www.trilobyte.net/barnsons</ulink>.
- If you're still stumped, please subscribe to the newsgroup and provide details of exactly
- what's stumping you! If enough people complain, I'll have to fix it in the next
- version of this Guide. You can subscribe to the newsgroup at
- <ulink url="news://news.mozilla.org/netscape.public.mozilla.webtools">
- news://news.mozilla.org/netscape.public.mozilla.webtools</ulink>
+ Some people have run into difficulties completing this
+ tutorial. If you run into problems, please check the
+ updated online documentation available at <ulink
+ url="http://www.trilobyte.net/barnsons/">http://www.trilobyte.net/barnsons</ulink>. If you're still stumped, please subscribe to the newsgroup and provide details of exactly what's stumping you! If enough people complain, I'll have to fix it in the next version of this Guide. You can subscribe to the newsgroup at <ulink url="news://news.mozilla.org/netscape.public.mozilla.webtools"> news://news.mozilla.org/netscape.public.mozilla.webtools</ulink>
</para>
- </note>
- Although Landfill serves as a great introduction to Bugzilla, it does not offer
- all the options you would have as a user on your own installation of Bugzilla,
- nor can it do more than serve as a general introduction to Bugzilla. Additionally,
- Landfill often runs cutting-edge versions of Bugzilla for testing, so some things
- may work slightly differently than mentioned here.
+ </note> Although Landfill serves as a great introduction to
+ Bugzilla, it does not offer all the options you would have as a
+ user on your own installation of Bugzilla, nor can it do more
+ than serve as a general introduction to Bugzilla. Additionally,
+ Landfill often runs cutting-edge versions of Bugzilla for
+ testing, so some things may work slightly differently than
+ mentioned here.
</para>
<section id="myaccount">
<title>Create a Bugzilla Account</title>
<para>
- First thing's first! 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 the end-user Bugzilla experience, use this URL:
- <ulink url="http://landfill.tequilarista.org/mozilla/bugzilla/">
- http://landfill.tequilarista.org/mozilla/bugzilla/</ulink>
+ First things first! 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 the end-user
+ Bugzilla experience, use this URL: <ulink
+ url="http://landfill.tequilarista.org/bugzilla-tip/"> http://landfill.tequilarista.org/bugzilla-tip/</ulink>
</para>
<orderedlist>
<listitem>
@@ -238,64 +251,81 @@ Chapter: Using Bugzilla
</listitem>
<listitem>
<para>
- Enter your "E-mail address" and "Real Name" (or whatever name you want to call yourself)
- in the spaces provided, then select the "Create Account" button.
+ Enter your "E-mail address" and "Real Name" (or whatever
+ name you want to call yourself) in the spaces provided,
+ then select the "Create Account" button.
</para>
</listitem>
<listitem>
<para>
- Within 5-10 minutes, you should receive an email to the address you provided above,
- which contains your login name (generally the same as the email address), and
- a password you can use to access your account. This password is randomly generated,
- and should be changed at your nearest opportunity (we'll go into how to do it later).
+ Within moments, you should receive an email to the address
+ you provided above, which contains your login name
+ (generally the same as the email address), and a password
+ you can use to access your account. This password is
+ randomly generated, and should be changed at your nearest
+ opportunity (we'll go into how to do it later).
</para>
</listitem>
<listitem>
<para>
- Click the "Log In" link in the yellow area at the bottom of the page in your browser,
- then enter your "E-mail address" and "Password" you just received into the spaces provided,
- and select "Login".
+ Click the <quote>Log In</quote> link in the yellow area at
+ the bottom of the page in your browser, then enter your
+ <quote>E-mail address</quote> and <quote>Password</quote>
+ you just received into the spaces provided, and select
+ <quote>Login</quote>.
<note>
<para>
- If you ever forget your password, you can come back to this page, enter your
- "E-mail address", then select the "E-mail me a password" button to have your password
- mailed to you again so that you can login.
+ If you ever forget your password, you can come back to
+ this page, enter your <quote>E-mail address</quote>,
+ then select the <quote>E-mail me a password</quote>
+ button to have your password mailed to you again so
+ that you can login.
</para>
</note>
<caution>
<para>
- Many modern browsers include an "Auto-Complete" or "Form Fill" feature to
- remember the user names and passwords you type in at many sites. Unfortunately,
- sometimes they attempt to "guess" what you will put in as your password, and guess
- wrong. If you notice a text box is already filled out, please overwrite the contents
- of the text box so you can be sure to input the correct information.
+ Many modern browsers include an
+ <quote>Auto-Complete</quote> or <quote>Form
+ Fill</quote> feature to remember the user names and
+ passwords you type in at many sites. Unfortunately,
+ sometimes they attempt to guess what you will put in
+ as your password, and guess wrong. If you notice a
+ text box is already filled out, please overwrite the
+ contents of the text box so you can be sure to input
+ the correct information.
</para>
</caution>
</para>
</listitem>
</orderedlist>
<para>
- Congratulations! If you followed these directions, you now are the
- proud owner of a user account on landfill.tequilarista.org (Landfill) or
- your local Bugzilla install. You should now see in your browser a
- page called the "Bugzilla Query Page". It may look daunting, but
- with this Guide to walk you through it, you will master it in no time.
+ Congratulations! If you followed these directions, you now
+ are the proud owner of a user account on
+ landfill.tequilarista.org (Landfill) or your local Bugzilla
+ install. You should now see in your browser a page called the
+ <quote>Bugzilla Query Page</quote>. It may look daunting, but with this
+ Guide to walk you through it, you will master it in no time.
</para>
</section>
<section id="query">
<title>The Bugzilla Query Page</title>
<para>
- The Bugzilla Query Page is the heart and soul of Bugzilla. It is the master
- interface where you can find any bug report, comment, or patch currently in the Bugzilla
- system. We'll go into how to create your own bug report later on.
+ The Bugzilla Query Page is the heart and soul of the Bugzilla
+ user experience. It is the master interface where you can
+ find any bug report, comment, or patch currently in the
+ Bugzilla system. We'll go into how to create your own bug
+ report later on.
</para>
<para>
- There are efforts underway to simplify query usage. If you have a local installation
- of Bugzilla 2.12 or higher, you should have "quicksearch.html" available
- to use and simplify your searches. There is also, or shortly will be, a helper
- for the query interface, called "queryhelp.cgi". Landfill tends to run the latest code,
- so these two utilities should be available there for your perusal.
+ There are efforts underway to simplify query usage. If you
+ have a local installation of Bugzilla 2.12 or higher, you
+ should have <filename>quicksearch.html</filename> available to
+ use and simplify your searches. There is also a helper for
+ the query interface, called
+ <filename>queryhelp.cgi</filename>. Landfill tends to run the
+ latest code, so these two utilities should be available there
+ for your perusal.
</para>
<para>
At this point, please visit the main Bugzilla site,
@@ -303,47 +333,57 @@ Chapter: Using Bugzilla
bugzilla.mozilla.org</ulink>, to see a more fleshed-out query page.
</para>
<para>
- The first thing you need to notice about the Bugzilla Query Page is that
- nearly every box you see on your screen has a hyperlink nearby, explaining what
- it is or what it does. Near the upper-left-hand corner of your browser window
- you should see the word "Status" underlined. Select it.
+ The first thing you need to notice about the Bugzilla Query
+ Page is that nearly every box you see on your screen has a
+ hyperlink nearby, explaining what it is or what it does. Near
+ the upper-left-hand corner of your browser window you should
+ see the word <quote>Status</quote> underlined. Select it.
</para>
<para>
- Notice the page that popped up? Every underlined word you see on your screen
- is a hyperlink that will take you to context-sensitive help.
- Click around for a while, and learn what everything here does. To return
- to the query interface after pulling up a help page, use the "Back" button in
- your browser.
+ Notice the page that popped up? Every underlined word you see
+ on your screen is a hyperlink that will take you to
+ context-sensitive help. Click around for a while, and learn
+ what everything here does. To return to the query interface
+ after pulling up a help page, use the <quote>Back</quote>
+ button in your browser.
</para>
<para>
- I'm sure that after checking out the online help, you are now an Expert
- on the Bugzilla Query Page. If, however, you feel you haven't mastered it yet,
- let me walk you through making a few successful queries to find out what there
- are in the Bugzilla bug-tracking system itself.
+ I'm sure that after checking out the online help, you are now
+ an expert on the Bugzilla Query Page. If, however, you feel
+ you haven't mastered it yet, let me walk you through making a
+ few successful queries to find out what there are in the
+ Bugzilla bug-tracking system itself.
</para>
<orderedlist>
<listitem>
<para>
- Ensure you are back on the "Bugzilla Query Page"
- Do nothing in the boxes marked "Status", "Resolution", "Platform", "OpSys",
- "Priority", or "Severity". The default query for "Status" is to find all bugs that
- are NEW, ASSIGNED, or REOPENED, which is what we want. If you don't select anything
- in the other 5 scrollboxes there, then you are saying that "any of these are OK";
- we're not locking ourselves into only finding bugs on the "DEC" Platform, or "Windows 95"
- OpSys (Operating System). You're smart, I think you have it figured out.
+ Ensure you are back on the <quote>Bugzilla Query
+ Page</quote>. Do nothing in the boxes marked "Status",
+ "Resolution", "Platform", "OpSys", "Priority", or
+ "Severity". The default query for "Status" is to find all
+ bugs that are NEW, ASSIGNED, or REOPENED, which is what we
+ want. If you don't select anything in the other 5
+ scrollboxes there, then you are saying that "any of these
+ are OK"; we're not locking ourselves into only finding
+ bugs on the "DEC" Platform, or "Windows 95" OpSys
+ (Operating System). You're smart, I think you have it
+ figured out.
</para>
<para>
- Basically, selecting <emphasis>anything</emphasis> on the query page narrows your search
- down. Leaving stuff unselected, or text boxes unfilled, broadens your search!
+ Basically, selecting <emphasis>anything</emphasis> on the
+ query page narrows your search down. Leaving stuff
+ unselected, or text boxes unfilled, broadens your search.
</para>
</listitem>
<listitem>
<para>
- You see the box immediately below the top six boxes that contains an "Email" text box,
- with the words "matching as", a drop-down selection box, then some checkboxes with
- "Assigned To" checked by default? This allows you to filter your search down based upon
- email address. Let's put my email address in there, and see what happens.
+ You see the box immediately below the top six boxes that
+ contains an "Email" text box, with the words "matching
+ as", a drop-down selection box, then some checkboxes with
+ "Assigned To" checked by default? This allows you to
+ filter your search down based upon email address. Let's
+ put my email address in there, and see what happens.
</para>
<para>
Type "barnboy@trilobyte.net" in the top Email text box.
@@ -352,47 +392,55 @@ Chapter: Using Bugzilla
<listitem>
<para>
- Let's narrow the search some more. Scroll down until you find the box with the word
- "Program" over the top of it. This is where we can narrow our search down to only
- specific products (software programs or product lines) in our Bugzilla database.
- Please notice the box is a <emphasis>scrollbox</emphasis>. Using the down arrow on the
- scrollbox, scroll down until you can see an entry called "Webtools". Select this entry.
+ Let's narrow the search some more. Scroll down until you
+ find the box with the word "Program" over the top of it.
+ This is where we can narrow our search down to only
+ specific products (software programs or product lines) in
+ our Bugzilla database. Please notice the box is a
+ <emphasis>scrollbox</emphasis>. Using the down arrow on
+ the scrollbox, scroll down until you can see an entry
+ called "Bugzilla". Select this entry.
</para>
</listitem>
<listitem>
<para>
- Did you notice that some of the boxes to the right changed when you selected "Webtools"?
- Every Program (or Product) has different Versions, Components, and Target Milestones associated
- with it. A "Version" is the number of a software program.
+ Did you notice that some of the boxes to the right changed
+ when you selected "Bugzilla"? Every Program (or Product)
+ has different Versions, Components, and Target Milestones
+ associated with it. A "Version" is the number of a
+ software program.
<example>
<title>Some Famous Software Versions</title>
<informalexample>
<para>
- Do you remember the hype in 1995 when Microsoft Windows 95(r) was released?
- It may have been several years
- ago, but Microsoft(tm) spent over $300 Million advertising this new Version of their
- software. Three years later, they released Microsoft Windows 98(r),
- another new version, to great fanfare, and then in 2000 quietly
- released Microsoft Windows ME(Millenium Edition)(r).
+ Do you remember the hype in 1995 when Microsoft
+ Windows 95(r) was released? It may have been several
+ years ago, but Microsoft(tm) spent over $300 Million
+ advertising this new Version of their software.
+ Three years later, they released Microsoft Windows
+ 98(r), another new version, to great fanfare, and
+ then in 2000 quietly released Microsoft Windows
+ ME(Millenium Edition)(r).
</para>
<para>
- Software "Versions" help a manufacturer differentiate
- their current product from their
- previous products. Most do not identify their products
- by the year they were released.
- Instead, the "original" version of their software will
- often be numbered "1.0", with
- small bug-fix releases on subsequent tenths of a digit. In most cases, it's not
- a decimal number; for instance, often 1.9 is an <emphasis>older</emphasis> version
- of the software than 1.11,
- but is a <emphasis>newer</emphasis> version than 1.1.1.
+ Software "Versions" help a manufacturer
+ differentiate their current product from their
+ previous products. Most do not identify their
+ products by the year they were released. Instead,
+ the "original" version of their software will often
+ be numbered "1.0", with small bug-fix releases on
+ subsequent tenths of a digit. In most cases, it's
+ not a decimal number; for instance, often 1.9 is an
+ <emphasis>older</emphasis> version of the software
+ than 1.11, but is a <emphasis>newer</emphasis>
+ version than 1.1.1.
</para>
<para>
- In general, a "Version" in Bugzilla should refer to
- <emphasis>released</emphasis>
- products, not products that have not yet been released
- to the public. Forthcoming products
- are what the Target Milestone field is for.
+ In general, a "Version" in Bugzilla should refer to
+ <emphasis>released</emphasis> products, not products
+ that have not yet been released to the public.
+ Forthcoming products are what the Target Milestone
+ field is for.
</para>
</informalexample>
</example>
@@ -404,60 +452,90 @@ Chapter: Using Bugzilla
Normally, a Component has a single Owner, who is responsible
for overseeing efforts to improve that Component.
<example>
- <title>Mozilla Webtools Components</title>
+ <title>Mozilla's Bugzilla Components</title>
<informalexample>
<para>
- Mozilla's "Webtools" Product is composed of several pieces (Components):
+ Mozilla's "Bugzilla" Product is composed of several pieces (Components):
<simplelist>
- <member><emphasis>Bonsai</emphasis>,
- a tool to show recent changes to Mozilla</member>
- <member><emphasis>Bugzilla</emphasis>,
- a defect-tracking tool</member>
- <member><emphasis>Build</emphasis>,
- a tool to automatically compile source code
- into machine-readable form</member>
- <member><emphasis>Despot</emphasis>,
- a program that controls access to the other Webtools</member>
- <member><emphasis>LXR</emphasis>,
- a utility that automatically marks up text files
- to make them more readable</member>
- <member><emphasis>MozBot</emphasis>,
- a "robot" that announces changes to Mozilla in Chat</member>
- <member><emphasis>TestManager</emphasis>,
- a tool to help find bugs in Mozilla</member>
- <member><emphasis>Tinderbox</emphasis>,
- which displays reports from Build</member>
+ <member><emphasis>Administration</emphasis>,
+ Administration of a bugzilla installation, including
+ <filename>editcomponents.cgi</filename>,
+ <filename>editgroups.cgi</filename>,
+ <filename>editkeywords.cgi</filename>,
+ <filename>editparams.cgi</filename>,
+ <filename>editproducts.cgi</filename>,
+ <filename>editusers.cgi</filename>,
+ <filename>editversions.cgi,</filename> and
+ <filename>sanitycheck.cgi</filename>.
+ </member>
+ <member><emphasis>Bugzilla-General</emphasis>,
+ Anything that doesn't fit in the other components, or spans
+ multiple components.
+ </member>
+ <member><emphasis>Creating/Changing Bugs</emphasis>,
+ Creating, changing, and viewing bugs.
+ <filename>enter_bug.cgi</filename>,
+ <filename>post_bug.cgi</filename>,
+ <filename>show_bug.cgi</filename> and
+ <filename>process_bug.cgi</filename>.
+ </member>
+ <member><emphasis>Documentation</emphasis>,
+ The bugzilla documentation, including anything in the
+ <filename>docs/</filename> directory and The Bugzilla Guide
+ (This document :)
+ </member>
+ <member><emphasis>Email</emphasis>,
+ Anything to do with email sent by Bugzilla.
+ <filename>processmail</filename>
+ </member>
+ <member><emphasis>Installation</emphasis>,
+ The installation process of Bugzilla. This includes
+ <filename>checksetup.pl</filename> and whatever else it evolves into.
+ </member>
+ <member><emphasis>Query/Buglist</emphasis>,
+ Anything to do with searching for bugs and viewing the buglists.
+ <filename>query.cgi</filename> and
+ <filename>buglist.cgi</filename>
+ </member>
+ <member><emphasis>Reporting/Charting</emphasis>,
+ Getting reports from Bugzilla.
+ <filename>reports.cgi</filename> and
+ <filename>duplicates.cgi</filename>
+ </member>
+ <member><emphasis>User Accounts</emphasis>,
+ Anything about managing a user account from the user's perspective.
+ <filename>userprefs.cgi</filename>, saved queries, creating accounts,
+ changing passwords, logging in, etc.
+ </member>
+ <member><emphasis>User Interface</emphasis>,
+ General issues having to do with the user interface cosmetics (not
+ functionality) including cosmetic issues, HTML templates, etc.
+ </member>
</simplelist>
</para>
- <para>
- A different person is responsible for each of these Components.
- Tara Hernandez keeps
- the "Bugzilla" component up-to-date.
- </para>
</informalexample>
</example>
</para>
<para>
- A "Milestone", or "Target Milestone" is a often a planned future "Version" of a
- product. In many cases, though, Milestones simply represent significant dates for
- a developer. Having certain features in your Product is frequently
- tied to revenue (money)
- the developer will receive if the features work by the time she
- reaches the Target Milestone.
- Target Milestones are a great tool to organize your time.
- If someone will pay you $100,000 for
- incorporating certain features by a certain date,
- those features by that Milestone date become
- a very high priority. Milestones tend to be highly malleable creatures,
- though, that appear
- to be in reach but are out of reach by the time the important day arrives.
+ A "Milestone", or "Target Milestone" is a often a planned
+ future "Version" of a product. In many cases, though,
+ Milestones simply represent significant dates for a
+ developer. Having certain features in your Product is
+ frequently tied to revenue (money) the developer will
+ receive if the features work by the time she reaches the
+ Target Milestone. Target Milestones are a great tool to
+ organize your time. If someone will pay you $100,000 for
+ incorporating certain features by a certain date, those
+ features by that Milestone date become a very high
+ priority. Milestones tend to be highly malleable
+ creatures, though, that appear to be in reach but are out
+ of reach by the time the important day arrives.
</para>
<para>
- The Bugzilla Project has set up Milestones for future
- Bugzilla versions 2.14, 2.16, 2.18, 3.0, etc. However,
- a Target Milestone can just as easily be a specific date,
- code name, or weird alphanumeric
- combination, like "M19".
+ The Bugzilla Project has set up Milestones for future
+ Bugzilla versions 2.14, 2.16, 2.18, 3.0, etc. However, a
+ Target Milestone can just as easily be a specific date,
+ code name, or weird alphanumeric combination, like "M19".
</para>
</listitem>
@@ -475,56 +553,54 @@ Chapter: Using Bugzilla
</listitem>
<listitem>
<para>
- Congratulations! You've completed your first Query, and have before you the Bug List
- of the author of this Guide, Matthew P. Barnson (barnboy@trilobyte.net). If I'm
- doing well,
- you'll have a cryptic "Zarro Boogs Found" message on your screen. It is just
- a happy hacker's way of saying "Zero Bugs Found". However, I am fairly certain I will
+ Congratulations! You've completed your first Query, and
+ have before you the Bug List of the author of this Guide,
+ Matthew P. Barnson (barnboy@trilobyte.net). If I'm doing
+ well, you'll have a cryptic "Zarro Boogs Found" message on
+ your screen. It is just a happy hacker's way of saying
+ "Zero Bugs Found". However, I am fairly certain I will
always have some bugs assigned to me that aren't done yet,
so you won't often see that message!
</para>
</listitem>
</orderedlist>
<para>
- I encourage you to click the bug numbers in the left-hand column and examine
- my bugs. Also notice that if you click the underlined
- links near the top of this page, they do
- not take you to context-sensitive help here,
- but instead sort the columns of bugs on the screen!
- When you need to sort your bugs by priority, severity,
- or the people they are assigned to, this
- is a tremendous timesaver.
+ I encourage you to click the bug numbers in the left-hand
+ column and examine my bugs. Also notice that if you click the
+ underlined links near the top of this page, they do not take
+ you to context-sensitive help here, but instead sort the
+ columns of bugs on the screen! When you need to sort your bugs
+ by priority, severity, or the people they are assigned to,
+ this is a tremendous timesaver.
</para>
<para>
A couple more interesting things about the Bug List page:
<simplelist>
- <member><emphasis>Change Columns</emphasis>:
- by selecting this link, you can show all kinds
- of information in the Bug List</member>
- <member><emphasis>Change several bugs at once</emphasis>:
- If you have sufficient rights to change all
- the bugs shown in the Bug List, you can mass-modify them.
- This is a big time-saver.</member>
- <member><emphasis>Send mail to bug owners</emphasis>:
- If you have many related bugs, you can request
- an update from every person who owns the bugs in
- the Bug List asking them the status.</member>
- <member><emphasis>Edit this query</emphasis>:
- If you didn't get exactly the results you were looking for,
- you can return to the Query page through this link and make
- small revisions to the query you just made so
- you get more accurate results.</member>
+ <member><emphasis>Change Columns</emphasis>: by selecting
+ this link, you can show all kinds of information in the
+ Bug List</member>
+ <member><emphasis>Change several bugs at once</emphasis>: If
+ you have sufficient rights to change all the bugs shown in
+ the Bug List, you can mass-modify them. This is a big
+ time-saver.</member>
+ <member><emphasis>Send mail to bug owners</emphasis>: If you
+ have many related bugs, you can request an update from
+ every person who owns the bugs in the Bug List asking them
+ the status.</member>
+ <member><emphasis>Edit this query</emphasis>: If you didn't
+ get exactly the results you were looking for, you can
+ return to the Query page through this link and make small
+ revisions to the query you just made so you get more
+ accurate results.</member>
</simplelist>
</para>
<note>
<para>
- There are many more options to the Bugzilla Query Page
- and the Bug List than I have shown you.
- But this should be enough for you to learn to get around.
- I encourage you to check out the
- <ulink url="http://www.mozilla.org/bugs/">Bugzilla Home Page</ulink>
- to learn about the Anatomy
- and Life Cycle of a Bug before continuing.
+ There are many more options to the Bugzilla Query Page and
+ the Bug List than I have shown you. But this should be
+ enough for you to learn to get around. I encourage you to
+ check out the <ulink
+ url="http://www.mozilla.org/bugs/">Bugzilla Home Page</ulink> to learn about the Anatomy and Life Cycle of a Bug before continuing.
</para>
</note>
</section>
@@ -539,37 +615,35 @@ Chapter: Using Bugzilla
<section id="bug_writing">
<title>Writing a Great Bug Report</title>
<para>
- Before we plunge into writing your first bug report, I encourage you to read
- <ulink url="http://www.mozilla.org/quality/bug-writing-guidelines.html">Mozilla.org's Bug
- Writing Guidelines</ulink>. 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.
+ Before we plunge into writing your first bug report, I
+ encourage you to read some bug-writing guidelines. If you
+ are reading this document as part of a Bugzilla CVS checkout
+ or un-tarred Bugzilla distribution, you should be able to
+ read them by clicking <ulink
+ url="../../bugwritinghelp.html">here</ulink>. If you are reading this online, check out the Mozilla.org bug-writing guidelines at <ulink url="http://www.mozilla.org/quality/bug-writing-guidelines.html">http://www.mozilla.org/quality/bug-writing-guidelines.html</ulink>. 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.
</para>
<para>
- While you are at it, why not learn how to find previously reported bugs? Mozilla.org
- has published a great tutorial on finding duplicate bugs, available at
- <ulink url="http://www.mozilla.org/quality/help/beginning-duplicate-finding.html">
- http://www.mozilla.org/quality/help/beginning-duplicate-finding.html</ulink>.
+ While you are at it, why not learn how to find previously
+ reported bugs? Mozilla.org has published a great tutorial
+ on finding duplicate bugs, available at <ulink
+ url="http://www.mozilla.org/quality/help/beginning-duplicate-finding.html"> http://www.mozilla.org/quality/help/beginning-duplicate-finding.html</ulink>.
</para>
<para>
- I realize this was a lot to read. However, understanding the mentality of writing
- great bug reports will help us on the next part!
+ I realize this was a lot to read. However, understanding
+ the mentality of writing great bug reports will help us on
+ the next part!
</para>
<orderedlist>
<listitem>
<para>
- Go back to <ulink url="http://landfill.tequilarista.org/mozilla/bugzilla/">
- http://landfill.tequilarista.org/mozilla/bugzilla/</ulink>
- in your browser.
+ Go back to <ulink
+ url="http://landfill.tequilarista.org/bugzilla-tip/"> http://landfill.tequilarista.org/bugzilla-tip/</ulink> in your browser.
</para>
</listitem>
<listitem>
<para>
- Select the
- <ulink url="http://landfill.tequilarista.org/mozilla/bugzilla/enter_bug.cgi">
- Enter a new bug report</ulink> link.
+ Select the <ulink
+ url="http://landfill.tequilarista.org/bugzilla-tip/enter_bug.cgi"> Enter a new bug report</ulink> link.
</para>
</listitem>
<listitem>
@@ -579,11 +653,11 @@ Chapter: Using Bugzilla
</listitem>
<listitem>
<para>
- Now you should be at the "Enter Bug" form.
- The "reporter" should have been automatically filled out
- for you (or else Bugzilla prompted you to Log In again
- -- you did keep the email with your username
- and password, didn't you?).
+ Now you should be at the "Enter Bug" form. The
+ "reporter" should have been automatically filled out for
+ you (or else Bugzilla prompted you to Log In again --
+ you did keep the email with your username and password,
+ didn't you?).
</para>
</listitem>
<listitem>
@@ -593,107 +667,97 @@ Chapter: Using Bugzilla
</listitem>
<listitem>
<para>
- Bugzilla should have made reasonable guesses, based upon your browser,
- for the "Platform" and "OS" drop-down
- boxes. If those are wrong, change them -- if you're on an SGI box
- running IRIX, we want to know!
+ Bugzilla should have made reasonable guesses, based upon
+ your browser, for the "Platform" and "OS" drop-down
+ boxes. If those are wrong, change them -- if you're on
+ an SGI box running IRIX, we want to know!
</para>
</listitem>
<listitem>
<para>
- Fill in the "Assigned To" box with the email address you provided earlier.
- This way you don't end up sending copies of your bug to lots of other people,
- since it's just a test bug.
+ Fill in the "Assigned To" box with the email address you
+ provided earlier. This way you don't end up sending
+ copies of your bug to lots of other people, since it's
+ just a test bug.
</para>
</listitem>
<listitem>
<para>
- Leave the "CC" text box blank.
- Fill in the "URL" box with "http://www.mozilla.org".
+ Leave the "CC" text box blank. Fill in the "URL" box
+ with "http://www.mozilla.org".
</para>
</listitem>
<listitem>
<para>
- Enter "The Bugzilla Guide" in the Summary text box,
- and place any comments you have on this
- tutorial, or the Guide in general, into the Description box.
+ Enter "The Bugzilla Guide" in the Summary text box, and
+ place any comments you have on this tutorial, or the
+ Guide in general, into the Description box.
</para>
</listitem>
</orderedlist>
<para>
- Voila! Select "Commit" and send in your bug report!
- Next we'll look at resolving bugs.
+ Voila! Select "Commit" and send in your bug report! Next
+ we'll look at resolving bugs.
</para>
</section>
<section id="bug_manage">
<title>Managing your Bug Reports</title>
<para>
- OK, you should have a link to the bug you just created near the top of your page.
- It should say
- "Bug XXXX posted", with a link to the right saying "Back to BUG# XXXX".
- Select this link.
+ OK, you should have a link to the bug you just created near
+ the top of your page. It should say "Bug XXXX posted", with
+ a link to the right saying "Back to BUG# XXXX". Select this
+ link.
</para>
<orderedlist>
<listitem>
<para>
- Scroll down a bit on the subsequent page,
- until you see the "Resolve bug, changing resolution to (dropdown box).
- Normally, you would
- "Accept bug (change status to ASSIGNED)", fix it, and then resolve.
- But in this case, we're
- going to short-circuit the process because this wasn't a real bug.
- Change the dropdown next to
- "Resolve Bug" to "INVALID", make sure the radio button is
- marked next to "Resolve Bug", then
- click "Commit".
+ Scroll down a bit on the subsequent page, until you see
+ the "Resolve bug, changing resolution to (dropdown box).
+ Normally, you would "Accept bug (change status to
+ ASSIGNED)", fix it, and then resolve. But in this case,
+ we're going to short-circuit the process because this
+ wasn't a real bug. Change the dropdown next to "Resolve
+ Bug" to "INVALID", make sure the radio button is marked
+ next to "Resolve Bug", then click "Commit".
</para>
</listitem>
<listitem>
<para>
- Hey! It said it couldn't take the change in a big red box!
- That's right, you must specify
- a Comment in order to make this change. Select the "Back"
- button in your browser, add a
- Comment, then try Resolving the bug with INVALID status again.
- This time it should work.
+ Hey! It said it couldn't take the change in a big red
+ box! That's right, you must specify a Comment in order
+ to make this change. Select the "Back" button in your
+ browser, add a Comment, then try Resolving the bug with
+ INVALID status again. This time it should work.
</para>
</listitem>
</orderedlist>
<para>
You have now learned the basics of Bugzilla navigation,
- entering a bug, and bug maintenance.
- I encourage you to explore these features, and see what you can do with them!
- We'll spend no more time on individual Bugs or Queries from this point on, so you are
- on your own there.
+ entering a bug, and bug maintenance. I encourage you to
+ explore these features, and see what you can do with them!
+ We'll spend no more time on individual Bugs or Queries from
+ this point on, so you are on your own there.
</para>
<para>
But I'll give a few last hints!
</para>
<para>
- There is a <ulink url="http://bugzilla.mozilla.org/help.html">CLUE</ulink>
- on the Query page
- that will teach you more how to use the form.
+ There is a <ulink
+ url="http://bugzilla.mozilla.org/help.html">CLUE</ulink> on the Query page that will teach you more how to use the form.
</para>
<para>
- If you click the hyperlink on the
- <ulink url="http://bugzilla.mozilla.org/describecomponents.cgi">Component</ulink>
- box of the Query page, you will be presented a form that will describe what all
- the components are.
+ If you click the hyperlink on the <ulink
+ url="http://bugzilla.mozilla.org/describecomponents.cgi">Component</ulink> box of the Query page, you will be presented a form that will describe what all the components are.
</para>
<para>
- Possibly the most powerful feature of the Query page is the
- <ulink url="http://bugzilla.mozilla.org/booleanchart.html">Boolean Chart</ulink> section.
- It's a bit confusing to use the first time, but can provide unparalleled
- flexibility in your queries,
- allowing you to build extremely powerful requests.
+ Possibly the most powerful feature of the Query page is the
+ <ulink
+ url="http://bugzilla.mozilla.org/booleanchart.html">Boolean Chart</ulink> section. It's a bit confusing to use the first time, but can provide unparalleled flexibility in your queries, allowing you to build extremely powerful requests.
</para>
<para>
- Finally, you can build some nifty
- <ulink url="http://bugzilla.mozilla.org/reports.cgi">Reports</ulink>
- using the "Bug Reports" link near the bottom of the query page, and also
- available via the "Reports" link
- at the footer of each page.
+ Finally, you can build some nifty <ulink
+ url="http://bugzilla.mozilla.org/reports.cgi">Reports</ulink> using the "Bug Reports" link near the bottom of the query page, and also available via the "Reports" link at the footer of each page.
</para>
</section>
</section>
@@ -701,7 +765,7 @@ Chapter: Using Bugzilla
</section>
<section id="init4me">
- <title>What's in it for me?</title>
+ <title>Where can I find my user preferences?</title>
<epigraph>
<para>
Indiana, it feels like we walking on fortune cookies!
@@ -711,98 +775,95 @@ Chapter: Using Bugzilla
</para>
</epigraph>
<para>
- Customized User Preferences offer tremendous versatility to
- your individual Bugzilla experience.
- Let's plunge into what you can do! The first step is to click
- the "Edit prefs" link at the footer of each page once you
- have logged in to
- <ulink url="http://landfill.tequilarista.org/mozilla/bugzilla/query.cgi?GoAheadAndLogIn=1">
- Landfill</ulink>.
+ Customized User Preferences offer tremendous versatility to your
+ individual Bugzilla experience. Let's plunge into what you can
+ do! The first step is to click the "Edit prefs" link at the
+ footer of each page once you have logged in to <ulink
+ url="http://landfill.tequilarista.org/bugzilla-tip/query.cgi?GoAheadAndLogIn=1"> Landfill</ulink>.
</para>
- <section id="accountsettings">
+ <section id="accountsettings" xreflabel="Account Settings">
<title>Account Settings</title>
<para>
On this page, you can change your basic Account Settings,
- including your password and full name.
- For security reasons, in order to change anything on this page you
- must type your <emphasis>current</emphasis>
- password into the "Old Password" field.
- If you wish to change your password, type the new password you
- want into the "New Password" field and again into the "Re-enter
- new password" field to ensure
- you typed your new password correctly. Select the "Submit" button and you're done!
+ including your password and full name. For security reasons,
+ in order to change anything on this page you must type your
+ <emphasis>current</emphasis> password into the <quote>Old
+ Password</quote> field. If you wish to change your
+ password, type the new password you want into the <quote>New
+ Password</quote> field and again into the <quote>Re-enter
+ new password</quote> field to ensure you typed your new
+ password correctly. Select the <quote>Submit</quote> button
+ and you are done.
</para>
</section>
- <section id="emailsettings">
+ <section id="emailsettings" >
<title>Email Settings</title>
- <section id="notification">
+ <section id="notification" xreflabel="">
<title>Email Notification</title>
- <note>
- <para>
- The email notification settings described below have been obsoleted in Bugzilla 2.12, and
- this section will be replaced with a comprehensive description of the amazing array of
- new options at your disposal. However, in the meantime, throw this chunk out the window
- and go crazy with goofing around with different notification options.
- </para>
- </note>
<para>
- Ahh, here you can reduce or increase the amount of email sent you from Bugzilla!
- In the drop-down "Notify me of changes to", select one of
- <simplelist>
- <member><emphasis>All qualifying bugs</emphasis>: sends you every change to every bug
- where your name is somewhere on it, regardless of who changed it.</member>
- <member><emphasis>Only those bugs which I am listed in the CC line</emphasis>: prevents
- you from receiving mail for which you are the reporter,'
- owner, or QA contact. If you are on the CC
- list, presumably someone had a <emphasis>good</emphasis>
- reason for you to get the email.</member>
- <member><emphasis>All qulifying bugs except those which I change</emphasis>:
- This is the default, and
- a sensible setting. If someone else changes your bugs, you will get emailed,
- but if you change bugs
- yourself you will receive no notification of the change.</member>
- </simplelist>
+ Here you can reduce or increase the amount of email sent you
+ from Bugzilla. Although this is referred to as
+ <quote>Advanced Email Filtering Options</quote>, they are,
+ in fact, the standard email filter set. All of them are
+ self-explanatory, but you can use the filters in interesting
+ ways. For instance, some people (notably Quality Assurance
+ personnel) often only care to receive updates regarding a
+ bug when the bug changes state, so they can track bugs on
+ their flow charts and know when it is time to pull the bug
+ onto a quality assurance platform for inspection. Other
+ people set up email gateways to
+ <xref linkend="bonsai"> or <xref linkend="tinderbox">, and
+ restrict which types of Bugzilla information are fed to
+ these systems..
</para>
</section>
<section id="newemailtech">
<title>New Email Technology</title>
<note>
<para>
- This option may not be available in all Bugzilla installations, depending upon
- the preferences of the systems administrator responsible for the setup of your Bugzilla.
- However, if you really want this functionality, ask her to "enable newemailtech
- in Params"
- and "make it the default for all new users", referring her to the Administration section
- of this Guide.
+ This option may not be available in all Bugzilla
+ installations, depending upon the preferences of the
+ systems administrator responsible for the setup of your
+ Bugzilla. However, if you really want this functionality,
+ ask her to "enable newemailtech in Params" and "make it
+ the default for all new users", referring her to the
+ Administration section of this Guide.
</para>
</note>
<para>
- Disregard the warnings about "experimental and bleeding edge"; the code to handle email
- in a cleaner manner than that historically used for Bugzilla is
- quite robust and well-tested now.
+ Disregard the warnings about "experimental and bleeding
+ edge"; the code to handle email in a cleaner manner than
+ that historically used for Bugzilla is quite robust and
+ well-tested now.
</para>
<para>
- I recommend you enable the option, "Click here to sign up (and risk any bugs)".
- Your email-box
- will thank you for it. The fundamental shift in "newemailtech" is away from standard UNIX
- "diff" output, which is quite ugly, to a prettier, better laid-out email.
+ I recommend you enable the option, "Click here to sign up
+ (and risk any bugs)". Your email-box will thank you for it.
+ The fundamental shift in "newemailtech" is away from
+ standard UNIX "diff" output, which is quite ugly, to a
+ prettier, better laid-out email.
</para>
</section>
<section id="watchsettings">
<title>"Watching" Users</title>
<note>
<para>
- This option may not be available in all Bugzilla installations, depending upon
- the preferences of the systems administrator responsible for the setup of your Bugzilla.
- However, if you really want this functionality, ask her to "enable watchers in Params".
+ This option may not be available in all Bugzilla
+ installations, depending upon the preferences of the
+ systems administrator responsible for the setup of your
+ Bugzilla. However, if you really want this functionality,
+ ask her to "enable watchers in Params".
</para>
</note>
<para>
- By entering user email names into the "Users to watch" text entry box, delineated by commas,
- you can watch bugs of other users. This powerful functionality enables seamless transitions
- as developers change projects, managers wish to get in touch with the issues faced by their
- direct reports, or users go on vacation. If any of these three situations apply
- to you, you will undoubtedly find this feature quite convenient.
+ By entering user email names into the "Users to watch" text
+ entry box, delineated by commas, you can watch bugs of other
+ users. This powerful functionality enables seamless
+ transitions as developers change projects, managers wish to
+ get in touch with the issues faced by their direct reports,
+ or users go on vacation. If any of these three situations
+ apply to you, you will undoubtedly find this feature quite
+ convenient.
</para>
</section>
</section>
@@ -810,36 +871,46 @@ Chapter: Using Bugzilla
<title>Page Footer</title>
<note>
<para>
- By default, this page is quite barren. However, go explore the Query Page some more; you will
- find that you can store numerous queries on the server, so if you regularly run a particular query
- it is just a drop-down menu away. On this page of Preferences, if you have many stored
- queries you can elect to have them always one-click away!
+ By default, this page is quite barren. However, go explore
+ the Query Page some more; you will find that you can store
+ numerous queries on the server, so if you regularly run a
+ particular query it is just a drop-down menu away. On this
+ page of Preferences, if you have many stored queries you can
+ elect to have them always one-click away!
</para>
</note>
<para>
- If you have many stored queries on the server, here you will find individual drop-downs for each
- stored query. Each drop-down gives you the option of that query appearing on the footer of every
- page in Bugzilla! This gives you powerful one-click access to any complex searches you may set up,
- and is an excellent way to impress your boss...
+ If you have many stored queries on the server, here you will
+ find individual drop-downs for each stored query. Each
+ drop-down gives you the option of that query appearing on the
+ footer of every page in Bugzilla! This gives you powerful
+ one-click access to any complex searches you may set up, and
+ is an excellent way to impress your boss...
</para>
<tip>
- <para>By default, the "My Bugs" link appears at the bottom of each page. However, this query
- gives you both the bugs you have reported, as well as those you are assigned. One of the most
- common uses for this page is to remove the "My Bugs" link, replacing it with two other queries,
- commonly called "My Bug Reports" and "My Bugs" (but only referencing bugs assigned to you). This
- allows you to distinguish those bugs you have reported from those you are assigned. I commonly
- set up complex Boolean queries in the Query page and link them to my footer in this page. When
- they are significantly complex, a one-click reference can save hours of work.</para>
+ <para>By default, the "My Bugs" link appears at the bottom of
+ each page. However, this query gives you both the bugs you
+ have reported, as well as those you are assigned. One of
+ the most common uses for this page is to remove the "My
+ Bugs" link, replacing it with two other queries, commonly
+ called "My Bug Reports" and "My Bugs" (but only referencing
+ bugs assigned to you). This allows you to distinguish those
+ bugs you have reported from those you are assigned. I
+ commonly set up complex Boolean queries in the Query page
+ and link them to my footer in this page. When they are
+ significantly complex, a one-click reference can save hours
+ of work.</para>
</tip>
</section>
<section id="permissionsettings">
<title>Permissions</title>
<para>
- This is a purely informative page which outlines your current permissions on
- this installation of Bugzilla. If you have permissions to grant certain permissions to
- other users, the "other users" link appears on this page as well as the footer.
- For more information regarding user administration, please consult the Administration
- section of this Guide.
+ This is a purely informative page which outlines your current
+ permissions on this installation of Bugzilla. If you have
+ permissions to grant certain permissions to other users, the
+ "other users" link appears on this page as well as the footer.
+ For more information regarding user administration, please
+ consult the Administration section of this Guide.
</para>
</section>
</section>
@@ -847,12 +918,11 @@ Chapter: Using Bugzilla
<section id="usingbz-conc">
<title>Using Bugzilla-Conclusion</title>
<para>
- Thank you for reading through this portion of the Bugzilla Guide. I anticipate
- it may not yet meet the needs of all readers. If you have additional comments or
- corrections to make, please submit your contributions to the
- <ulink url="mailto://mozilla-webtools@mozilla.org">mozilla-webtools</ulink>
- mailing list/newsgroup. The mailing list is mirrored to the netscape.public.mozilla.webtools
- newsgroup, and the newsgroup is mirrored to mozilla-webtools@mozilla.org
+ Thank you for reading through this portion of the Bugzilla
+ Guide. I anticipate it may not yet meet the needs of all
+ readers. If you have additional comments or corrections to
+ make, please submit your contributions to the <ulink
+ url="mailto://mozilla-webtools@mozilla.org">mozilla-webtools</ulink> mailing list/newsgroup. The mailing list is mirrored to the netscape.public.mozilla.webtools newsgroup, and the newsgroup is mirrored to mozilla-webtools@mozilla.org
</para>
</section>
</chapter>
@@ -861,17 +931,20 @@ Chapter: Using Bugzilla
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
-sgml-omittag:t
-sgml-shorttag:t
-sgml-namecase-general:t
-sgml-general-insert-case:lower
-sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
-sgml-indent-step:2
-sgml-indent-data:t
-sgml-parent-document:Bugzilla-Guide\.sgml
+sgml-auto-insert-required-elements:t
+sgml-balanced-tag-edit:t
sgml-exposed-tags:nil
+sgml-general-insert-case:lower
+sgml-indent-data:t
+sgml-indent-step:2
sgml-local-catalogs:nil
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-shorttag:t
+sgml-tag-region-if-active:t
End:
-->
diff --git a/docs/sgml/variants.sgml b/docs/sgml/variants.sgml
index d13b9ee8d..a5b346023 100644
--- a/docs/sgml/variants.sgml
+++ b/docs/sgml/variants.sgml
@@ -1,87 +1,96 @@
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
+<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN">-->
-<chapter id="variants">
- <title>Bugzilla Variants</title>
- <note>
- <para>
- I <emphasis>know</emphasis> there are more variants than just RedHat Bugzilla out there.
- Please help me get information about them, their project status, and benefits there
- might be in using them or in using their code in main-tree Bugzilla.
- </para>
- </note>
+<chapter id="variants" xreflabel="Bugzilla Variants and Competitors">
+ <title>Bugzilla Variants and Competitors</title>
+ <para>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: <ulink
+ url="http://linas.org/linux/pm.html">http://linas.org/linux/pm.html</ulink></para>
- <section id="rhbugzilla">
+ <section id="rhbugzilla" xreflabel="Red Hat Bugzilla">
<title>Red Hat Bugzilla</title>
<para>
- Red Hat Bugzilla is probably the most popular Bugzilla variant, aside from Mozilla Bugzilla,
- on the planet.
- One of the major benefits of Red Hat Bugzilla is the ability to work with Oracle as a
- database, as well as MySQL.
- Here's what Dave Lawrence had to say about the status of Red Hat Bugzilla,
- <blockquote>
- <literallayout>
- Hello. I apologize that I am getting back to you so late. It has been difficult to keep
-up with email this past week. I have checked out your updated documentation and I will
-have to say very good work. A few notes and additions as follows.
-
-(ed: from the FAQ)
->For the record, we are not using any template type implementation for the cosmetic changes
->maded to Bugzilla. It is just alot of html changes in the code itself. I admit I may have
->gotten a little carried away with it but the corporate types asked for a more standardized
->interface to match up with other projects relating to Red Hat web sites. A lot of other web
->based internal tools I am working on also look like Bugzilla.
-
+ Red Hat Bugzilla is probably the most popular Bugzilla variant
+ on the planet. One of the major benefits of Red Hat Bugzilla is
+ the ability to work with Oracle, MySQL, and PostGreSQL databases
+ serving as the back-end, instead of just MySQL. Dave Lawrence
+ has worked very hard to keep Red Hat Bugzilla up-to-date, and
+ many people prefer the snappier-looking page layout of Red Hat
+ Bugzilla to the default Mozilla-standard formatting.
+ </para>
+ <para>URL: <ulink
+ url="http://bugzilla.redhat.com/bugzilla/">http://bugzilla.redhat.com/bugzilla/</ulink></para>
+ </section>
-This should probably be changed since we are now in fact using Text::Template for most
-of the html rendering. You actually state this later in your numbered list.
+ <section id="variant_fenris" xreflabel="Loki Bugzilla, a.k.a. Fenris">
+ <title>Loki Bugzilla (Fenris)</title>
+ <para>Fenris can be found at <ulink
+ url="http://fenris.lokigames.com/">http://fenris.lokigames.com</ulink>. It is a fork from Bugzilla.</para>
+ </section>
-Also number 6 contradicts number 8 where number 6 would be the most up to date status
-on the Oracle port.
+ <section id="variant_issuezilla" xreflabel="Issuezilla">
+ <title>Issuezilla</title>
+ <para>Issuezilla is another fork from Bugzilla, and seems nearly
+ as popular as the Red Hat Bugzilla fork. Some Issuezilla team
+ members are regular contributors to the Bugzilla mailing
+ list/newsgroup. Issuezilla is not the primary focus of
+ bug-tracking at tigris.org, however. Their Java-based
+ bug-tracker, <xref linkend="variant_scarab">, is under heavy development
+ and looks promising!</para>
+ <para>URL: <ulink url="http://issuezilla.tigris.org/servlets/ProjectHome">http://issuezilla.tigris.org/servlets/ProjectHome</ulink></para>
+ </section>
-Additional Information:
------------------------------
-1. Comments are now stored in varchar fields of 4k in size each. If the comment is more
-than 4k it is broken up into chunks and given a sort number so each comment can be re
-assembled in the correct order. This was done because originally I was storing the comments
-in a long datatype which unfortunately cannot be indexed or joined with another table. This
-cause the search of text within the long description to be disabled for a long time. That
-is now working and is nto showing any noticeble performance hit that I can tell.
+ <section id="variant_scarab" xreflabel="Scarab, a newfangled Java-based issue tracker">
+ <title>Scarab</title>
+ <para>Scarab is a promising new bug-tracking system built using
+ Java Serlet technology. As of this writing, no source code has
+ been released as a package, but you can obtain the code from
+ CVS.
+ </para>
+ <para>URL: <ulink url="http://scarab.tigris.org/">http://scarab.tigris.org</ulink></para>
+ </section>
-2. Work is being started on internationalizing the Bugzilla source we have to allow our
-Japanese customers to enter bug reports into a single bugzilla system. This will probably
-be done by using the nvarchar data types supported by Oracle which allows storage of
-double byte characters and also the use of the Accept-Language in the http header for
-detection by Bugilla of which language to render.
+ <section id="variant_perforce" xreflabel="Using Perforce to track bugs">
+ <title>Perforce SCM</title>
+ <para>Although Perforce isn't really a bug tracker, it can be used
+ as such through the <quote>jobs</quote> functionality.</para>
+ <para><ulink
+ url="http://www.perforce.com/perforce/technotes/note052.html"></ulink>http://www.perforce.com/perforce/technotes/note052.html</para>
+ </section>
-3. Of course even more cosmetic changes. It is difficult to keep up with the ever
-changing faces of www.redhat.com.
+ <section id="variant_sourceforge" xreflabel="SourceForge">
+ <title>SourceForge</title>
+ <para>SourceForge is more of a way of coordinating geographically
+ distributed free software and open source projects over the
+ Internet than strictly a bug tracker, but if you're hunting for
+ bug-tracking for your open project, it may be just what the
+ software engineer ordered!</para>
+ <para>URL: <ulink
+ url="http://www.sourceforge.net">http://www.sourceforge.net</ulink></para>
+ </section>
-4. Some convenience enhancements in the administration utilities. And more integration
-with other internal/external Red Hat web sites.
-I hope this information may prove helpful for your documentation. Please contact
-me if you have any more question or I can do anything else.
-Regards
- </literallayout>
- </blockquote>
- </para>
- </section>
</chapter>
+
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
-sgml-omittag:t
-sgml-shorttag:t
-sgml-namecase-general:t
-sgml-general-insert-case:lower
-sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
-sgml-indent-step:2
-sgml-indent-data:t
-sgml-parent-document:nil
+sgml-auto-insert-required-elements:t
+sgml-balanced-tag-edit:t
sgml-exposed-tags:nil
+sgml-general-insert-case:lower
+sgml-indent-data:t
+sgml-indent-step:2
sgml-local-catalogs:nil
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-shorttag:t
+sgml-tag-region-if-active:t
End:
-->
diff --git a/docs/txt/Bugzilla-Guide.txt b/docs/txt/Bugzilla-Guide.txt
index b31a112e6..17caf5ddd 100644
--- a/docs/txt/Bugzilla-Guide.txt
+++ b/docs/txt/Bugzilla-Guide.txt
@@ -4,6 +4,9 @@ The Bugzilla Guide
Matthew P. Barnson
barnboy@trilobyte.net
+ Zach Lipton
+
+ zach AT zachlipton DOT com
Revision History
Revision v2.11 20 December 2000 Revised by: MPB
Converted the README, FAQ, and DATABASE information into SGML docbook
@@ -24,9 +27,31 @@ Matthew P. Barnson
deprecated status. Things I know need work: Used "simplelist" a lot,
where I should have used "procedure" to tag things. Need to lowercase
all tags to be XML compliant.
+ Revision 2.14.0 07 August 2001 Revised by: MPB
+ Attempted to integrate relevant portions of the UNIX and Windows
+ installation instructions, moved some data from FAQ to Install,
+ removed references to README from text, added Mac OS X install
+ instructions, fixed a bunch of tpyos (Mark Harig), linked text that
+ referenced other parts of the Guide, and nuked the old MySQL
+ permissions section.
This is the documentation for Bugzilla, the Mozilla bug-tracking
system.
+
+ Bugzilla is an enterprise-class set of software utilities that, when
+ used together, power issue-tracking for hundreds of organizations
+ around the world, tracking millions of bugs. While it is easy to use
+ and quite flexible, it is very difficult for a novice to install and
+ maintain. Although we have provided step-by-step directions, Bugzilla
+ is not always easy to get working. Please be sure the person
+ responsible for installing and maintaining this software is a
+ qualified professional on operating system upon which you install
+ Bugzilla.
+
+ THIS DOCUMENTATION IS MAINTAINED IN DOCBOOK 4.1 SGML FORMAT. IF YOU
+ WISH TO MAKE CORRECTIONS, PLEASE MAKE THEM IN PLAIN TEXT OR SGML DIFFS
+ AGAINST THE SOURCE. I CANNOT ACCEPT ADDITIONS TO THE GUIDE WRITTEN IN
+ HTML!
_________________________________________________________________
Table of Contents
@@ -42,105 +67,117 @@ Matthew P. Barnson
1.8. Translations
1.9. Document Conventions
- 2. Installing Bugzilla
+ 2. Using Bugzilla
- 2.1. UNIX Installation
+ 2.1. What is Bugzilla?
+ 2.2. Why Should We Use Bugzilla?
+ 2.3. How do I use Bugzilla?
- 2.1.1. ERRATA
- 2.1.2. Step-by-step Install
+ 2.3.1. Create a Bugzilla Account
+ 2.3.2. The Bugzilla Query Page
+ 2.3.3. Creating and Managing Bug Reports
- 2.1.2.1. Introduction
- 2.1.2.2. Installing the Prerequisites
- 2.1.2.3. Installing MySQL Database
- 2.1.2.4. Perl (5.004 or greater)
- 2.1.2.5. DBI Perl Module
- 2.1.2.6. Data::Dumper Perl Module
- 2.1.2.7. MySQL related Perl Module Collection
- 2.1.2.8. TimeDate Perl Module Collection
- 2.1.2.9. GD Perl Module (1.8.3)
- 2.1.2.10. Chart::Base Perl Module (0.99c)
- 2.1.2.11. DB_File Perl Module
- 2.1.2.12. HTTP Server
- 2.1.2.13. Installing the Bugzilla Files
- 2.1.2.14. Setting Up the MySQL Database
- 2.1.2.15. Tweaking "localconfig"
- 2.1.2.16. Setting Up Maintainers Manuall (Optional)
- 2.1.2.17. The Whining Cron (Optional)
- 2.1.2.18. Bug Graphs (Optional)
- 2.1.2.19. Securing MySQL
- 2.1.2.20. Installation General Notes
+ 2.3.3.1. Writing a Great Bug Report
+ 2.3.3.2. Managing your Bug Reports
- 2.2. Win32 (Win98+/NT/2K) Installation
+ 2.4. Where can I find my user preferences?
- 2.2.1. Win32 Installation: Step-by-step
- 2.2.2. Additional Windows Tips
+ 2.4.1. Account Settings
+ 2.4.2. Email Settings
- 3. Administering Bugzilla
+ 2.4.2.1. Email Notification
+ 2.4.2.2. New Email Technology
+ 2.4.2.3. "Watching" Users
- 3.1. Post-Installation Checklist
- 3.2. User Administration
+ 2.4.3. Page Footer
+ 2.4.4. Permissions
- 3.2.1. Creating the Default User
- 3.2.2. Managing Other Users
+ 2.5. Using Bugzilla-Conclusion
- 3.2.2.1. Logging In
- 3.2.2.2. Creating new users
- 3.2.2.3. Disabling Users
- 3.2.2.4. Modifying Users
+ 3. Installation
- 3.3. Product, Component, Milestone, and Version Administration
+ 3.1. ERRATA
+ 3.2. Step-by-step Install
- 3.3.1. Products
- 3.3.2. Components
- 3.3.3. Versions
- 3.3.4. Milestones
- 3.3.5. Voting
- 3.3.6. Groups and Group Security
+ 3.2.1. Introduction
+ 3.2.2. Installing the Prerequisites
+ 3.2.3. Installing MySQL Database
+ 3.2.4. Perl (5.004 or greater)
+ 3.2.5. DBI Perl Module
+ 3.2.6. Data::Dumper Perl Module
+ 3.2.7. MySQL related Perl Module Collection
+ 3.2.8. TimeDate Perl Module Collection
+ 3.2.9. GD Perl Module (1.8.3)
+ 3.2.10. Chart::Base Perl Module (0.99c)
+ 3.2.11. DB_File Perl Module
+ 3.2.12. HTTP Server
+ 3.2.13. Installing the Bugzilla Files
+ 3.2.14. Setting Up the MySQL Database
+ 3.2.15. Tweaking localconfig
+ 3.2.16. Setting Up Maintainers Manually (Optional)
+ 3.2.17. The Whining Cron (Optional)
+ 3.2.18. Bug Graphs (Optional)
+ 3.2.19. Securing MySQL
- 3.4. Bugzilla Security
+ 3.3. Mac OS X Installation Notes
+ 3.4. BSD Installation Notes
+ 3.5. Installation General Notes
- 4. Using Bugzilla
+ 3.5.1. Modifying Your Running System
+ 3.5.2. Upgrading From Previous Versions
+ 3.5.3. .htaccess files and security
+ 3.5.4. mod_throttle and Security
+ 3.5.5. Preventing untrusted Bugzilla content from executing
+ malicious Javascript code
- 4.1. What is Bugzilla?
- 4.2. Why Should We Use Bugzilla?
- 4.3. How do I use Bugzilla?
+ 3.5.6. UNIX Installation Instructions History
- 4.3.1. Create a Bugzilla Account
- 4.3.2. The Bugzilla Query Page
- 4.3.3. Creating and Managing Bug Reports
+ 3.6. Win32 Installation Notes
- 4.3.3.1. Writing a Great Bug Report
- 4.3.3.2. Managing your Bug Reports
+ 3.6.1. Win32 Installation: Step-by-step
+ 3.6.2. Additional Windows Tips
+ 3.6.3. Bugzilla LDAP Integration
- 4.4. What's in it for me?
+ 4. Administering Bugzilla
- 4.4.1. Account Settings
- 4.4.2. Email Settings
+ 4.1. Post-Installation Checklist
+ 4.2. User Administration
- 4.4.2.1. Email Notification
- 4.4.2.2. New Email Technology
- 4.4.2.3. "Watching" Users
+ 4.2.1. Creating the Default User
+ 4.2.2. Managing Other Users
- 4.4.3. Page Footer
- 4.4.4. Permissions
+ 4.2.2.1. Logging In
+ 4.2.2.2. Creating new users
+ 4.2.2.3. Disabling Users
+ 4.2.2.4. Modifying Users
- 4.5. Using Bugzilla-Conclusion
+ 4.3. Product, Component, Milestone, and Version Administration
+
+ 4.3.1. Products
+ 4.3.2. Components
+ 4.3.3. Versions
+ 4.3.4. Milestones
+ 4.3.5. Voting
+ 4.3.6. Groups and Group Security
+
+ 4.4. Bugzilla Security
5. Integrating Bugzilla with Third-Party Tools
5.1. Bonsai
5.2. CVS
5.3. Perforce SCM
- 5.4. Tinderbox
+ 5.4. Tinderbox/Tinderbox2
6. The Future of Bugzilla
+ 7. Bugzilla Variants and Competitors
- 6.1. Reducing Spam
- 6.2. Better Searching
- 6.3. Description Flags and Tracking Bugs
- 6.4. Bug Issues
- 6.5. Database Integrity
- 6.6. Bugzilla 3.0
+ 7.1. Red Hat Bugzilla
+ 7.2. Loki Bugzilla (Fenris)
+ 7.3. Issuezilla
+ 7.4. Scarab
+ 7.5. Perforce SCM
+ 7.6. SourceForge
A. The Bugzilla FAQ
B. Software Download Links
@@ -148,18 +185,20 @@ Matthew P. Barnson
C.1. Database Schema Chart
C.2. MySQL Bugzilla Database Introduction
- C.3. MySQL Permissions & Grant Tables
- C.4. Cleaning up after mucking with Bugzilla
- 7. Bugzilla Variants
+ C.2.1. Bugzilla Database Basics
- 7.1. Red Hat Bugzilla
+ C.2.1.1. Bugzilla Database Tables
+
+ C.3. MySQL Permissions & Grant Tables
D. Useful Patches and Utilities for Bugzilla
- D.1. The setperl.csh Utility
- D.2. Command-line Bugzilla Queries
- D.3. The Quicksearch Utility
+ D.1. Apache mod_rewrite magic
+ D.2. The setperl.csh Utility
+ D.3. Command-line Bugzilla Queries
+ D.4. The Quicksearch Utility
+ D.5. Hacking Bugzilla
E. GNU Free Documentation License
@@ -179,19 +218,23 @@ Matthew P. Barnson
Glossary
List of Examples
- 2-1. Removing encrypt() for Windows NT installations
- 3-1. Creating some Components
- 3-2. Common Use of Versions
- 3-3. A Different Use of Versions
- 3-4. Using SortKey with Target Milestone
- 3-5. When to Use Group Security
- 3-6. Creating a New Group
- 4-1. Some Famous Software Versions
- 4-2. Mozilla Webtools Components
+ 2-1. Some Famous Software Versions
+ 2-2. Mozilla's Bugzilla Components
+ 3-1. Setting up bonsaitools symlink
+ 3-2. Running checksetup.pl as the web user
+ 3-3. Installing ActivePerl ppd Modules on Microsoft Windows
+ 3-4. Removing encrypt() for Windows NT Bugzilla version 2.12 or
+ earlier
+
+ 4-1. Creating some Components
+ 4-2. Common Use of Versions
+ 4-3. A Different Use of Versions
+ 4-4. Using SortKey with Target Milestone
+ 4-5. When to Use Group Security
+ 4-6. Creating a New Group
+ 4-7. Bugzilla Groups
D-1. Using Setperl to set your perl path
1. A Sample Product
-
- ] >
_________________________________________________________________
Chapter 1. About This Guide
@@ -203,13 +246,12 @@ Chapter 1. About This Guide
I left untouched for nearly half a year. After numerous complete
rewrites and reformatting, it is the document you see today.
- Despite the lack of updates, Bugzilla is simply the best piece of
- bug-tracking software the world has ever seen. This document is
- intended to be the comprehensive guide to the installation,
- administration, maintenance, and use of the Bugzilla bug-tracking
- system.
+ Bugzilla is simply the best piece of bug-tracking software the world
+ has ever seen. This document is intended to be the comprehensive guide
+ to the installation, administration, maintenance, and use of the
+ Bugzilla bug-tracking system.
- This release of the Bugzilla Guide is the 2.11 release. It is so named
+ This release of the Bugzilla Guide is the 2.14 release. It is so named
that it may match the current version of Bugzilla. The numbering
tradition stems from that used for many free software projects, in
which even-numbered point releases (1.2, 1.14, etc.) are considered
@@ -218,13 +260,14 @@ Chapter 1. About This Guide
development releases intended for advanced users, systems
administrators, developers, and those who enjoy a lot of pain.
- Newer revisions of the Bugzilla Guide will follow the numbering
- conventions of the main-tree Bugzilla releases, available at
- Mozilla.org, with the exception that intermediate releases will have a
- minor revision number following a period. For instance, if the current
- version of Bugzilla is 4.2, the current "stable" version of the
- Bugzilla guide, in, say, it's fifth revision, would be numbered
- "4.2.5". Got it? Good.
+ Newer revisions of the Bugzilla Guide follow the numbering conventions
+ of the main-tree Bugzilla releases, available at
+ http://www.mozilla.org/projects/bugzilla. Intermediate releases will
+ have a minor revision number following a period. The current version
+ of Bugzilla, as of this writing (August 10, 2001) is 2.14; if
+ something were seriously wrong with that edition of the Guide,
+ subsequent releases would receive an additional dotted-decimal digit
+ to indicate the update (2.14.1, 2.14.2, etc.). Got it? Good.
I wrote this in response to the enormous demand for decent Bugzilla
documentation. I have incorporated instructions from the Bugzilla
@@ -239,7 +282,7 @@ Chapter 1. About This Guide
Permission is granted to copy, distribute and/or modify this document
- under thei terms of the GNU Free Documentation License, Version 1.1 or
+ under the terms of the GNU Free Documentation License, Version 1.1 or
any later version published by the Free Software Foundation; with no
Invariant Sections, no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled "GNU
@@ -247,9 +290,9 @@ Chapter 1. About This Guide
--Copyright (c) 2000-2001 Matthew P. Barnson
- If you have any questions regarding this document, its' copyright, or
+ If you have any questions regarding this document, its copyright, or
publishing this document in non-electronic form, please contact
- <barnboy@trilobyte.net>
+ Matthew P. Barnson.
_________________________________________________________________
1.3. Disclaimer
@@ -265,27 +308,38 @@ Chapter 1. About This Guide
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. In particular, I like to put down Microsoft(tm). Live with it.
+ mark.
Naming of particular products or brands should not be seen as
- endorsements, with the exception of the term "GNU/Linux". Use
- GNU/Linux. Love it. Bathe with it. It is life and happiness. I endorse
- it wholeheartedly and encourage you to do the same.
+ endorsements, with the exception of the term "GNU/Linux". I
+ 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. Heaven knows
it's saved my bacon time after time; if you implement any suggestion
in this Guide, implement this one!
- Bugzilla has not undergone a complete security review. Security holes
- probably exist in the code. Great care should be taken both in the
- installation and usage of this software. Carefully consider the
- implications of installing other network services with Bugzilla.
+ 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 insure
+ your security needs are met.
_________________________________________________________________
1.4. New Versions
- This is the initial release of the Bugzilla Guide.
+ This is the 2.14 version of The Bugzilla Guide. 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:
@@ -305,8 +359,8 @@ Chapter 1. About This Guide
numerous e-mail and IRC support sessions, and overall excellent
contribution to the Bugzilla community:
- Terry Weissman for initially converting Bugzilla from BugSplat! and
- writing the README upon which this documentation is largely based.
+ 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
@@ -328,8 +382,8 @@ Chapter 1. About This Guide
Thanks go to these people for significant contributions to this
documentation (in no particular order):
- Zach Lipton (significant textual contributions), Andrew Pearson,
- Spencer Smith, Eric Hanson, Kevin Brannen,
+ Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen, Ron
+ Teitelbaum, Jacob Steenhagen, Joe Robins
_________________________________________________________________
1.7. Feedback
@@ -345,9 +399,8 @@ Chapter 1. About This Guide
The Bugzilla Guide needs translators! Please volunteer your
translation into the language of your choice. If you will translate
this Guide, please notify the members of the mozilla-webtools mailing
- list at <mozilla-webtools@mozilla.org>. Since The Bugzilla Guide is
- also hosted on the Linux Documentation Project, you would also do well
- to notify
+ list at <mozilla-webtools@mozilla.org>, and arrange with Matt Barnson
+ to check it into CVS.
_________________________________________________________________
1.9. Document Conventions
@@ -362,12 +415,14 @@ Chapter 1. About This Guide
Warnings.
Hint
- Tip: Hint.
+ Tip
+ Hint.
Notes
- Note: Note.
+ Note
+ Note.
Information requiring special attention
Warning
@@ -386,2351 +441,3444 @@ Chapter 1. About This Guide
<para>Beginning and end of paragraph</para>
_________________________________________________________________
-Chapter 2. Installing Bugzilla
-
-2.1. UNIX Installation
-
-2.1.1. ERRATA
-
- Note: If you are installing Bugzilla on S.u.S.e. Linux, or some
- other distributions with "paranoid" security options, it is
- possible that the checksetup.pl script may fail with the error:
- 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 problem.
-
- Note: Release Notes for Bugzilla 2.12 are available at
- docs/rel_notes.txt
-
- Note: The preferred documentation for Bugzilla is available in
- docs/, with a variety of document types available. Please refer to
- these documents when installing, configuring, and maintaining your
- Bugzilla installation.
-
- Warning
-
- Bugzilla is not a package where you can just plop it in a directory,
- twiddle a few things, and you're off. Installing Bugzilla assumes you
- know your variant of UNIX or Microsoft Windows well, are familiar with
- the command line, and are comfortable compiling and installing a
- plethora of third-party utilities. To install Bugzilla on Win32
- requires fair Perl proficiency, and if you use a webserver other than
- Apache you should be intimately familiar with the security mechanisms
- and CGI environment thereof.
-
- Warning
-
- Bugzilla has not undergone a complete security review. Security holes
- may exist in the code. Great care should be taken both in the
- installation and usage of this software. Carefully consider the
- implications of installing other network services with Bugzilla.
- _________________________________________________________________
-
-2.1.2. Step-by-step Install
+Chapter 2. Using Bugzilla
-2.1.2.1. Introduction
-
- Installation of bugzilla is pretty straightforward, particularly if
- your machine already has MySQL and the MySQL-related perl packages
- installed. If those aren't installed yet, then that's the first order
- of business. The other necessary ingredient is a web server set up to
- run cgi scripts. While using Apache for your webserver is not
- required, it is recommended.
- Bugzilla has been successfully installed under Solaris, Linux, and
- Win32. The peculiarities of installing on Win32 (Win98+/NT/2K) are not
- included in this section of the Guide; please check out the "Win32
- Installation Instructions" for further advice on getting Bugzilla to
- work on Microsoft Windows.
- The Bugzilla Guide is contained in the "docs/" folder. It is available
- in plain text (docs/txt), HTML (docs/html), or SGML source
- (docs/sgml).
+ What, Why, How, & Where?
_________________________________________________________________
-2.1.2.2. Installing the Prerequisites
+2.1. What is Bugzilla?
- The software packages necessary for the proper running of bugzilla
- are:
+ Bugzilla is one example of a class of programs called "Defect Tracking
+ Systems", or, more commonly, "Bug-Tracking Systems". Defect Tracking
+ Systems allow individual or groups of developers to keep track of
+ outstanding bugs in their product effectively. Bugzilla was originally
+ written by Terry Weissman in a programming language called "TCL", to
+ replace a crappy bug-tracking database used internally for Netscape
+ Communications. Terry later ported Bugzilla to Perl from TCL, and in
+ Perl it remains to this day. Most commercial defect-tracking software
+ vendors at the time charged enormous licensing fees, and Bugzilla
+ quickly became a favorite of the open-source crowd (with its genesis
+ in the open-source browser project, Mozilla). It is now the de-facto
+ standard defect-tracking system against which all others are measured.
- 1. MySQL database server and the mysql client (3.22.5 or greater)
- 2. Perl (5.004 or greater)
- 3. DBI Perl module
- 4. Data::Dumper Perl module
- 5. DBD::mySQL
- 6. TimeDate Perl module collection
- 7. GD perl module (1.8.3) (optional, for bug charting)
- 8. Chart::Base Perl module (0.99c) (optional, for bug charting)
- 9. DB_File Perl module (optional, for bug charting)
- 10. The web server of your choice. Apache is recommended.
- 11. MIME::Parser Perl module (optional, for contrib/bug_email.pl
- interface)
+ Bugzilla has matured immensely, and now boasts many advanced features.
+ These include:
- Note: You must run Bugzilla on a filesystem that supports file
- locking via flock(). This is necessary for Bugzilla to operate
- safely with multiple instances.
+ * integrated, product-based granular security schema
+ * inter-bug dependencies and dependency graphing
+ * advanced reporting capabilities
+ * a robust, stable RDBMS back-end
+ * extensive configurability
+ * a very well-understood and well-thought-out natural bug resolution
+ protocol
+ * email, XML, console, and HTTP APIs
+ * available integration with automated software configuration
+ management systems, including Perforce and CVS (through the
+ Bugzilla email interface and checkin/checkout scripts)
+ * too many more features to list
- Warning
+ Despite its current robustness and popularity, Bugzilla faces some
+ near-term challenges, such as reliance on a single database, a lack of
+ abstraction of the user interface and program logic, verbose email bug
+ notifications, a powerful but daunting query interface, little
+ reporting configurability, problems with extremely large queries, some
+ unsupportable bug resolution options, little internationalization
+ (although non-US character sets are accepted for comments), and
+ dependence on some nonstandard libraries.
- It is a good idea, while installing Bugzilla, to ensure it is not
- accessible by other machines on the Internet. Your machine may be
- vulnerable to attacks while you are installing. In other words, ensure
- there is some kind of firewall between you and the rest of the
- Internet. Many installation steps require an active Internet
- connection to complete, but you must take care to ensure that at no
- point is your machine vulnerable to an attack.
- _________________________________________________________________
+ Some recent headway has been made on the query front, however. If you
+ are using the latest version of Bugzilla, you should see a "simple
+ search" form on the default front page of your Bugzilla install. Type
+ in two or three search terms and you should pull up some relevant
+ information. This is also available as "queryhelp.cgi".
-2.1.2.3. Installing MySQL Database
-
- Visit MySQL homepage at http://www.mysql.org/ and grab the latest
- stable release of the server. Both binaries and source are available
- and which you get shouldn't matter. Be aware that many of the binary
- versions of MySQL store their data files in /var which on many
- installations (particularly common with linux installations) is part
- of a smaller root partition. If you decide to build from sources you
- can easily set the dataDir as an option to configure.
-
- If you've installed from source or non-package (RPM, deb, etc.)
- binaries you'll want to make sure to add mysqld to your init scripts
- so the server daemon will come back up whenever your machine reboots.
- You also may want to edit those init scripts, to make sure that mysqld
- will accept large packets. By default, mysqld is set up to only accept
- packets up to 64K long. This limits the size of attachments you may
- put on bugs. If you add something like "-O max_allowed_packet=1M" to
- the command that starts mysqld (or safe_mysqld), then you will be able
- to have attachments up to about 1 megabyte.
-
- Note: If you plan on running Bugzilla and MySQL on the same
- machine, consider using the "--skip-networking" option in the init
- script. This enhances security by preventing network access to
- MySQL.
+ Despite these small problems, Bugzilla is very hard to beat. It is
+ under very active development to address the current issues, and
+ continually gains new features.
_________________________________________________________________
-2.1.2.4. Perl (5.004 or greater)
-
- Any machine that doesn't have perl on it is a sad machine indeed. Perl
- for *nix systems can be gotten in source form from
- http://www.perl.com.
-
- Perl is now a far cry from the the single compiler/interpreter binary
- it once was. It now includes a great many required modules and quite a
- few other support files. If you're not up to or not inclined to build
- perl from source, you'll want to install it on your machine using some
- sort of packaging system (be it RPM, deb, or what have you) to ensure
- a sane install. In the subsequent sections you'll be installing quite
- a few perl modules; this can be quite ornery if your perl installation
- isn't up to snuff.
-
- Tip: You can skip the following Perl module installation steps by
- installing "Bundle::Bugzilla" from CPAN, which includes them. All
- Perl module installation steps require you have an active Internet
- connection.
+2.2. Why Should We Use Bugzilla?
- bash# perl -MCPAN -e 'install "Bundle::Bugzilla"'
- Bundle::Bugzilla doesn't include GD, Chart::Base, or MIME::Parser,
- which are not essential to a basic Bugzilla install. If installing
- this bundle fails, you should install each module individually to
- isolate the problem.
- _________________________________________________________________
-2.1.2.5. DBI Perl Module
+ No, Who's on first...
- The DBI module is a generic Perl module used by other database related
- Perl modules. For our purposes it's required by the MySQL-related
- modules. As long as your Perl installation was done correctly the DBI
- module should be a breeze. It's a mixed Perl/C module, but Perl's
- MakeMaker system simplifies the C compilation greatly.
+ 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.
- Like almost all Perl modules DBI can be found on the Comprehensive
- Perl Archive Network (CPAN) at http://www.cpan.org. The CPAN servers
- have a real tendency to bog down, so please use mirrors. The current
- location at the time of this writing (02/17/99) can be found in
- Appendix A.
+ 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.
- 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.
+ But why should you use Bugzilla?
- To use the CPAN shell to install DBI:
+ 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, Loki software, Linux-Mandrake, and VA
+ Systems. Combined with systems such as CVS, Bonsai, or Perforce SCM,
+ Bugzilla provides a powerful, easy-to-use solution to configuration
+ management and replication problems
- bash# perl -MCPAN -e 'install "DBI"'
+ 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 by using Bugzilla's e-mail
+ integration features be able to follow the discussion trail that led
+ to critical decisions.
- Note: Replace "DBI" with the name of whichever module you wish to
- install, such as Data::Dumper, TimeDate, GD, etc.
+ 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.
+ _________________________________________________________________
- To do it the hard way:
+2.3. How do I use Bugzilla?
- Untar the module tarball -- it should create its own directory
- CD to the directory just created, and enter the following commands:
- 1. bash# perl Makefile.PL
- 2. bash# make
- 3. bash# make test
- 4. bash# make install
+ Hey! I'm Woody! Howdy, Howdy, Howdy!
- If everything went ok that should be all it takes. For the vast
- majority of perl modules this is all that's required.
- _________________________________________________________________
+ Bugzilla is a large, complex system. Describing how to use it requires
+ some time. If you are only interested in installing or administering a
+ Bugzilla installation, please consult the Installing and Administering
+ Bugzilla portions of this Guide. This section is principally aimed
+ towards developing end-user mastery of Bugzilla, so you may fully
+ enjoy the benefits afforded by using this reliable open-source
+ bug-tracking software.
-2.1.2.6. Data::Dumper Perl Module
+ Throughout this portion of the Guide, we will refer to user account
+ options available at the Bugzilla test installation,
+ landfill.tequilarista.org.
- 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.
+ Note
- Data::Dumper is used by the MySQL related Perl modules. It can be
- found on CPAN (link in Appendix A) and can be installed by following
- the same four step make sequence used for the DBI module.
+ Some people have run into difficulties completing this tutorial. If
+ you run into problems, please check the updated online documentation
+ available at http://www.trilobyte.net/barnsons. If you're still
+ stumped, please subscribe to the newsgroup and provide details of
+ exactly what's stumping you! If enough people complain, I'll have to
+ fix it in the next version of this Guide. You can subscribe to the
+ newsgroup at news://news.mozilla.org/netscape.public.mozilla.webtools
+ Although Landfill serves as a great introduction to Bugzilla, it does
+ not offer all the options you would have as a user on your own
+ installation of Bugzilla, nor can it do more than serve as a general
+ introduction to Bugzilla. Additionally, Landfill often runs
+ cutting-edge versions of Bugzilla for testing, so some things may work
+ slightly differently than mentioned here.
_________________________________________________________________
-2.1.2.7. MySQL related Perl Module Collection
+2.3.1. Create a Bugzilla Account
- The Perl/MySQL interface requires a few mutually-dependent perl
- modules. These modules are grouped together into the the
- Msql-Mysql-modules package. This package can be found at CPAN. After
- the archive file has been downloaded it should be untarred.
+ First things first! 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 the end-user Bugzilla experience, use this URL:
+ http://landfill.tequilarista.org/bugzilla-tip/
- The MySQL modules are all built using one make file which is generated
- by running: bash# perl Makefile.pl
+ 1. Click the "Open a new Bugzilla account" link.
+ 2. Enter your "E-mail address" and "Real Name" (or whatever name you
+ want to call yourself) in the spaces provided, then select the
+ "Create Account" button.
+ 3. Within moments, you should receive an email to the address you
+ provided above, which contains your login name (generally the same
+ as the email address), and a password you can use to access your
+ account. This password is randomly generated, and should be
+ changed at your nearest opportunity (we'll go into how to do it
+ later).
+ 4. Click the "Log In" link in the yellow area at the bottom of the
+ page in your browser, then enter your "E-mail address" and
+ "Password" you just received into the spaces provided, and select
+ "Login".
- The MakeMaker process will ask you a few questions about the desired
- compilation target and your MySQL installation. For many of the
- questions the provided default will be adequate.
+ Note
- When asked if your desired target is the MySQL or mSQL packages
- selected the MySQL related ones. Later you will be asked if you wish
- to provide backwards compatibility with the older MySQL packages; you
- must answer YES to this question. The default will be no, and if you
- select it things won't work later.
+ If you ever forget your password, you can come back to this page,
+ enter your "E-mail address", then select the "E-mail me a password"
+ button to have your password mailed to you again so that you can
+ login.
- A host of 'localhost' should be fine and a testing user of 'test' and
- a null password should find itself with sufficient access to run tests
- on the 'test' database which MySQL created upon installation. If 'make
- test' and 'make install' go through without errors you should be ready
- to go as far as database connectivity is concerned.
- _________________________________________________________________
+ Caution
-2.1.2.8. TimeDate Perl Module Collection
+ Many modern browsers include an "Auto-Complete" or "Form Fill" feature
+ to remember the user names and passwords you type in at many sites.
+ Unfortunately, sometimes they attempt to guess what you will put in as
+ your password, and guess wrong. If you notice a text box is already
+ filled out, please overwrite the contents of the text box so you can
+ be sure to input the correct information.
- Many of the more common date/time/calendar related Perl modules have
- been grouped into a bundle similar to the MySQL modules bundle. This
- bundle is stored on the CPAN under the name TimeDate. A (hopefully
- current) link can be found in Appendix A. The component module we're
- most interested in is the Date::Format module, but installing all of
- them is probably a good idea anyway. The standard Perl module
- installation instructions should work perfectly for this simple
- package.
+ Congratulations! If you followed these directions, you now are the
+ proud owner of a user account on landfill.tequilarista.org (Landfill)
+ or your local Bugzilla install. You should now see in your browser a
+ page called the "Bugzilla Query Page". It may look daunting, but with
+ this Guide to walk you through it, you will master it in no time.
_________________________________________________________________
-2.1.2.9. GD Perl Module (1.8.3)
+2.3.2. The Bugzilla Query Page
- The GD library was written by Thomas Boutell a long while ago to
- programatically generate images in C. Since then it's become almost a
- defacto standard for programatic image construction. The Perl bindings
- to it found in the GD library are used on a million web pages to
- generate graphs on the fly. That's what bugzilla will be using it for
- so you'd better install it if you want any of the graphing to work.
+ The Bugzilla Query Page is the heart and soul of the Bugzilla user
+ experience. It is the master interface where you can find any bug
+ report, comment, or patch currently in the Bugzilla system. We'll go
+ into how to create your own bug report later on.
- Actually bugzilla uses the Graph module which relies on GD itself, but
- isn't that always the way with OOP. At any rate, you can find the GD
- library on CPAN (link in Appendix "Required Software").
+ There are efforts underway to simplify query usage. If you have a
+ local installation of Bugzilla 2.12 or higher, you should have
+ quicksearch.html available to use and simplify your searches. There is
+ also a helper for the query interface, called queryhelp.cgi. Landfill
+ tends to run the latest code, so these two utilities should be
+ available there for your perusal.
- Note: The Perl GD library requires some other libraries that may or
- may not be installed on your system, including "libpng" and
- "libgd". The full requirements are listed in the Perl GD library
- README. Just realize that if compiling GD fails, it's probably
- because you're missing a required library.
- _________________________________________________________________
+ At this point, please visit the main Bugzilla site,
+ bugzilla.mozilla.org, to see a more fleshed-out query page.
-2.1.2.10. Chart::Base Perl Module (0.99c)
+ The first thing you need to notice about the Bugzilla Query Page is
+ that nearly every box you see on your screen has a hyperlink nearby,
+ explaining what it is or what it does. Near the upper-left-hand corner
+ of your browser window you should see the word "Status" underlined.
+ Select it.
- The Chart module provides bugzilla with on-the-fly charting abilities.
- It can be installed in the usual fashion after it has been fetched
- from CPAN where it is found as the Chart-x.x... tarball in a directory
- to be listed in Appendix "Required Software". Note that as with the GD
- perl module, only the specific versions listed above (or newer) will
- work. Earlier versions used GIF's, which are no longer supported by
- the latest versions of GD.
- _________________________________________________________________
+ Notice the page that popped up? Every underlined word you see on your
+ screen is a hyperlink that will take you to context-sensitive help.
+ Click around for a while, and learn what everything here does. To
+ return to the query interface after pulling up a help page, use the
+ "Back" button in your browser.
-2.1.2.11. DB_File Perl Module
+ I'm sure that after checking out the online help, you are now an
+ expert on the Bugzilla Query Page. If, however, you feel you haven't
+ mastered it yet, let me walk you through making a few successful
+ queries to find out what there are in the Bugzilla bug-tracking system
+ itself.
- DB_File is a module which allows Perl programs to make use of the
- facilities provided by Berkeley DB version 1.x. This module is
- required by collectstats.pl which is used for bug charting. If you
- plan to make use of bug charting, you must install this module.
- _________________________________________________________________
-
-2.1.2.12. HTTP Server
+ 1. Ensure you are back on the "Bugzilla Query Page". Do nothing in
+ the boxes marked "Status", "Resolution", "Platform", "OpSys",
+ "Priority", or "Severity". The default query for "Status" is to
+ find all bugs that are NEW, ASSIGNED, or REOPENED, which is what
+ we want. If you don't select anything in the other 5 scrollboxes
+ there, then you are saying that "any of these are OK"; we're not
+ locking ourselves into only finding bugs on the "DEC" Platform, or
+ "Windows 95" OpSys (Operating System). You're smart, I think you
+ have it figured out.
+ Basically, selecting anything on the query page narrows your
+ search down. Leaving stuff unselected, or text boxes unfilled,
+ broadens your search.
+ 2. You see the box immediately below the top six boxes that contains
+ an "Email" text box, with the words "matching as", a drop-down
+ selection box, then some checkboxes with "Assigned To" checked by
+ default? This allows you to filter your search down based upon
+ email address. Let's put my email address in there, and see what
+ happens.
+ Type "barnboy@trilobyte.net" in the top Email text box.
+ 3. Let's narrow the search some more. Scroll down until you find the
+ box with the word "Program" over the top of it. This is where we
+ can narrow our search down to only specific products (software
+ programs or product lines) in our Bugzilla database. Please notice
+ the box is a scrollbox. Using the down arrow on the scrollbox,
+ scroll down until you can see an entry called "Bugzilla". Select
+ this entry.
+ 4. Did you notice that some of the boxes to the right changed when
+ you selected "Bugzilla"? Every Program (or Product) has different
+ Versions, Components, and Target Milestones associated with it. A
+ "Version" is the number of a software program.
+ Example 2-1. Some Famous Software Versions
+ Do you remember the hype in 1995 when Microsoft Windows 95(r) was
+ released? It may have been several years ago, but Microsoft(tm)
+ spent over $300 Million advertising this new Version of their
+ software. Three years later, they released Microsoft Windows
+ 98(r), another new version, to great fanfare, and then in 2000
+ quietly released Microsoft Windows ME(Millenium Edition)(r).
+ Software "Versions" help a manufacturer differentiate their
+ current product from their previous products. Most do not identify
+ their products by the year they were released. Instead, the
+ "original" version of their software will often be numbered "1.0",
+ with small bug-fix releases on subsequent tenths of a digit. In
+ most cases, it's not a decimal number; for instance, often 1.9 is
+ an older version of the software than 1.11, but is a newer version
+ than 1.1.1.
+ In general, a "Version" in Bugzilla should refer to released
+ products, not products that have not yet been released to the
+ public. Forthcoming products are what the Target Milestone field
+ is for.
+ A "Component" is a piece of a Product. It may be a standalone
+ program, or some other logical division of a Product or Program.
+ Normally, a Component has a single Owner, who is responsible for
+ overseeing efforts to improve that Component.
+ Example 2-2. Mozilla's Bugzilla Components
+ Mozilla's "Bugzilla" Product is composed of several pieces
+ (Components):
- You have a freedom of choice here - Apache, Netscape or any other
- server on UNIX would do. You can easily run the web server on a
- different machine than MySQL, but need to adjust the MySQL "bugs" user
- permissions accordingly.
+ Administration, Administration of a bugzilla installation, including
+ editcomponents.cgi, editgroups.cgi, editkeywords.cgi, editparams.cgi,
+ editproducts.cgi, editusers.cgi, editversions.cgi, and
+ sanitycheck.cgi.
+ Bugzilla-General, Anything that doesn't fit in the other components,
+ or spans multiple components.
+ Creating/Changing Bugs, Creating, changing, and viewing bugs.
+ enter_bug.cgi, post_bug.cgi, show_bug.cgi and process_bug.cgi.
+ Documentation, The bugzilla documentation, including anything in the
+ docs/ directory and The Bugzilla Guide (This document :)
+ Email, Anything to do with email sent by Bugzilla. processmail
+ Installation, The installation process of Bugzilla. This includes
+ checksetup.pl and whatever else it evolves into.
+ Query/Buglist, Anything to do with searching for bugs and viewing the
+ buglists. query.cgi and buglist.cgi
+ Reporting/Charting, Getting reports from Bugzilla. reports.cgi and
+ duplicates.cgi
+ User Accounts, Anything about managing a user account from the user's
+ perspective. userprefs.cgi, saved queries, creating accounts, changing
+ passwords, logging in, etc.
+ User Interface, General issues having to do with the user interface
+ cosmetics (not functionality) including cosmetic issues, HTML
+ templates, etc.
+ A "Milestone", or "Target Milestone" is a often a planned future
+ "Version" of a product. In many cases, though, Milestones simply
+ represent significant dates for a developer. Having certain
+ features in your Product is frequently tied to revenue (money) the
+ developer will receive if the features work by the time she
+ reaches the Target Milestone. Target Milestones are a great tool
+ to organize your time. If someone will pay you $100,000 for
+ incorporating certain features by a certain date, those features
+ by that Milestone date become a very high priority. Milestones
+ tend to be highly malleable creatures, though, that appear to be
+ in reach but are out of reach by the time the important day
+ arrives.
+ The Bugzilla Project has set up Milestones for future Bugzilla
+ versions 2.14, 2.16, 2.18, 3.0, etc. However, a Target Milestone
+ can just as easily be a specific date, code name, or weird
+ alphanumeric combination, like "M19".
+ 5. OK, now let's select the "Bugzilla" component from its scrollbox.
+ 6. Skip down the page a bit -- do you see the "submit query" button?
+ Select it, and let's run this query!
+ 7. Congratulations! You've completed your first Query, and have
+ before you the Bug List of the author of this Guide, Matthew P.
+ Barnson (barnboy@trilobyte.net). If I'm doing well, you'll have a
+ cryptic "Zarro Boogs Found" message on your screen. It is just a
+ happy hacker's way of saying "Zero Bugs Found". However, I am
+ fairly certain I will always have some bugs assigned to me that
+ aren't done yet, so you won't often see that message!
- You'll want to make sure that your web server will run any file with
- the .cgi extension as a cgi and not just display it. If you're using
- apache that means uncommenting the following line in the srm.conf
- file: AddHandler cgi-script .cgi
+ I encourage you to click the bug numbers in the left-hand column and
+ examine my bugs. Also notice that if you click the underlined links
+ near the top of this page, they do not take you to context-sensitive
+ help here, but instead sort the columns of bugs on the screen! When
+ you need to sort your bugs by priority, severity, or the people they
+ are assigned to, this is a tremendous timesaver.
- With apache you'll also want to make sure that within the access.conf
- file the line: Options ExecCGI is in the stanza that covers the
- directories you intend to put the bugzilla .html and .cgi files into.
+ A couple more interesting things about the Bug List page:
- If you are using a newer version of Apache, both of the above lines
- will be (or will need to be) in the httpd.conf file, rather than
- srm.conf or access.conf.
+ Change Columns: by selecting this link, you can show all kinds of
+ information in the Bug List
+ Change several bugs at once: If you have sufficient rights to change
+ all the bugs shown in the Bug List, you can mass-modify them. This is
+ a big time-saver.
+ Send mail to bug owners: If you have many related bugs, you can
+ request an update from every person who owns the bugs in the Bug List
+ asking them the status.
+ Edit this query: If you didn't get exactly the results you were
+ looking for, you can return to the Query page through this link and
+ make small revisions to the query you just made so you get more
+ accurate results.
- Warning
+ Note
- There are two critical directories and a file that should not be a
- served by the HTTP server. These are the 'data' and 'shadow'
- directories and the 'localconfig' file. You should configure your HTTP
- server to not serve content from these files. Failure to do so will
- expose critical passwords and other data. Please see your HTTP server
- configuration manual on how to do this. If you use quips (at the top
- of the buglist pages) you will want the 'data/comments' file to still
- be served. This file contains those quips.
+ There are many more options to the Bugzilla Query Page and the Bug
+ List than I have shown you. But this should be enough for you to learn
+ to get around. I encourage you to check out the Bugzilla Home Page to
+ learn about the Anatomy and Life Cycle of a Bug before continuing.
_________________________________________________________________
-2.1.2.13. Installing the Bugzilla Files
+2.3.3. Creating and Managing Bug Reports
- You should untar the Bugzilla files into a directory that you're
- willing to make writable by the default web server user (probably
- 'nobody'). You may decide to put the files off of the main web space
- for your web server or perhaps off of /usr/local with a symbolic link
- in the web space that points to the bugzilla directory. At any rate,
- just dump all the files in the same place (optionally omitting the CVS
- directories if they were accidentally tarred up with the rest of
- Bugzilla) and make sure you can access the files in that directory
- through your web server.
- Tip: HINT: If you symlink the bugzilla directory into your Apache's
- HTML heirarchy, you may receive "Forbidden" errors unless you add
- the "FollowSymLinks" directive to the <Directory> entry for the
- HTML root.
- Once all the files are in a web accessible directory, make that
- directory writable by your webserver's user (which may require just
- making it world writable). This is a temporary step until you run the
- post-install "checksetup.pl" script, which locks down your
- installation.
+ And all this time, I thought we were taking bugs out...
+ _________________________________________________________________
- Lastly, you'll need to set up a symbolic link from
- /usr/bonsaitools/bin to the correct location of your perl executable
- (probably /usr/bin/perl). Otherwise you must hack all the .cgi files
- to change where they look for perl. To make future upgrades easier,
- you should use the symlink approach.
+2.3.3.1. Writing a Great Bug Report
- Tip: If you don't have root access to set this symlink up, check
- out the "setperl.csh" utility, listed in the Patches section of
- this Guide. It will change the path to perl in all your Bugzilla
- files for you.
- _________________________________________________________________
+ Before we plunge into writing your first bug report, I encourage you
+ to read some bug-writing guidelines. If you are reading this document
+ as part of a Bugzilla CVS checkout or un-tarred Bugzilla distribution,
+ you should be able to read them by clicking here. If you are reading
+ this online, check out the Mozilla.org bug-writing guidelines at
+ http://www.mozilla.org/quality/bug-writing-guidelines.html. 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.
-2.1.2.14. Setting Up the MySQL Database
+ While you are at it, why not learn how to find previously reported
+ bugs? Mozilla.org has published a great tutorial on finding duplicate
+ bugs, available at
+ http://www.mozilla.org/quality/help/beginning-duplicate-finding.html.
- After you've gotten all the software installed and working you're
- ready to start preparing the database for its life as a the back end
- to a high quality bug tracker.
+ I realize this was a lot to read. However, understanding the mentality
+ of writing great bug reports will help us on the next part!
- First, you'll want to fix MySQL permissions to allow access from
- Bugzilla. For the purpose of this Installation section, the Bugzilla
- username will be "bugs", and will have minimal permissions. Bugzilla
- has not undergone a thorough security audit. It may be possible for a
- system cracker to somehow trick Bugzilla into executing a command such
- as "; DROP DATABASE mysql".
+ 1. Go back to http://landfill.tequilarista.org/bugzilla-tip/ in your
+ browser.
+ 2. Select the Enter a new bug report link.
+ 3. Select a product.
+ 4. Now you should be at the "Enter Bug" form. The "reporter" should
+ have been automatically filled out for you (or else Bugzilla
+ prompted you to Log In again -- you did keep the email with your
+ username and password, didn't you?).
+ 5. Select a Component in the scrollbox.
+ 6. Bugzilla should have made reasonable guesses, based upon your
+ browser, for the "Platform" and "OS" drop-down boxes. If those are
+ wrong, change them -- if you're on an SGI box running IRIX, we
+ want to know!
+ 7. Fill in the "Assigned To" box with the email address you provided
+ earlier. This way you don't end up sending copies of your bug to
+ lots of other people, since it's just a test bug.
+ 8. Leave the "CC" text box blank. Fill in the "URL" box with
+ "http://www.mozilla.org".
+ 9. Enter "The Bugzilla Guide" in the Summary text box, and place any
+ comments you have on this tutorial, or the Guide in general, into
+ the Description box.
- That would be bad.
+ Voila! Select "Commit" and send in your bug report! Next we'll look at
+ resolving bugs.
+ _________________________________________________________________
- Give the MySQL root user a password. MySQL passwords are limited to 16
- characters.
+2.3.3.2. Managing your Bug Reports
- bash# mysql -u root mysql
- mysql> UPDATE user SET Password=PASSWORD ('new_password') WHERE
- user='root';
- mysql> FLUSH PRIVILEGES;
+ OK, you should have a link to the bug you just created near the top of
+ your page. It should say "Bug XXXX posted", with a link to the right
+ saying "Back to BUG# XXXX". Select this link.
- From this point on, if you need to access MySQL as the MySQL root
- user, you will need to use "mysql -u root -p" and enter your
- new_password. Remember that MySQL user names have nothing to do with
- Unix user names (login names).
+ 1. Scroll down a bit on the subsequent page, until you see the
+ "Resolve bug, changing resolution to (dropdown box). Normally, you
+ would "Accept bug (change status to ASSIGNED)", fix it, and then
+ resolve. But in this case, we're going to short-circuit the
+ process because this wasn't a real bug. Change the dropdown next
+ to "Resolve Bug" to "INVALID", make sure the radio button is
+ marked next to "Resolve Bug", then click "Commit".
+ 2. Hey! It said it couldn't take the change in a big red box! That's
+ right, you must specify a Comment in order to make this change.
+ Select the "Back" button in your browser, add a Comment, then try
+ Resolving the bug with INVALID status again. This time it should
+ work.
- Next, we create the "bugs" user, and grant sufficient permissions for
- checksetup.pl, which we'll use later, to work its magic. This also
- restricts the "bugs" user to operations within a database called
- "bugs", and only allows the account to connect from "localhost".
- Modify it to reflect your setup if you will be connecting from another
- machine or as a different user.
+ You have now learned the basics of Bugzilla navigation, entering a
+ bug, and bug maintenance. I encourage you to explore these features,
+ and see what you can do with them! We'll spend no more time on
+ individual Bugs or Queries from this point on, so you are on your own
+ there.
- Remember to set bugs_password to some unique password.
+ But I'll give a few last hints!
- mysql> GRANT SELECT,INSERT,UPDATE,DELETE,INDEX,
- ALTER,CREATE,DROP,REFERENCES ON bugs.* TO bugs@localhost IDENTIFIED BY
- 'bugs_password';
- mysql> FLUSH PRIVILEGES;
+ There is a CLUE on the Query page that will teach you more how to use
+ the form.
- Next, run the magic checksetup.pl script. (Many thanks to Holger
- Schurig <holgerschurig@nikocity.de> for writing this script!) It will
- make sure Bugzilla files and directories have reasonable permissions,
- set up the "data" directory, and create all the MySQL tables.
+ If you click the hyperlink on the Component box of the Query page, you
+ will be presented a form that will describe what all the components
+ are.
- bash# ./checksetup.pl
+ Possibly the most powerful feature of the Query page is the Boolean
+ Chart section. It's a bit confusing to use the first time, but can
+ provide unparalleled flexibility in your queries, allowing you to
+ build extremely powerful requests.
- The first time you run it, it will create a file called "localconfig".
+ Finally, you can build some nifty Reports using the "Bug Reports" link
+ near the bottom of the query page, and also available via the
+ "Reports" link at the footer of each page.
_________________________________________________________________
-2.1.2.15. Tweaking "localconfig"
+2.4. Where can I find my user preferences?
- This file contains a variety of settings you may need to tweak
- including how Bugzilla should connect to the MySQL database.
- The connection settings include:
- 1. server's host: just use "localhost" if the MySQL server is local
- 2. database name: "bugs" if you're following these directions
- 3. MySQL username: "bugs" if you're following these directions
- 4. Password for the "bugs" MySQL account above
+ Indiana, it feels like we walking on fortune cookies!
- Once you are happy with the settings, re-run checksetup.pl. On this
- second run, it will create the database and an administrator account
- for which you will be prompted to provide information.
+ These ain't fortune cookies, kid...
- When logged into an administrator account once Bugzilla is running, if
- you go to the query page (off of the bugzilla main menu), you'll find
- an 'edit parameters' option that is filled with editable treats.
-
- Should everything work, you should have a nearly empty copy of the bug
- tracking setup.
-
- The second time around, checksetup.pl will stall if it is on a
- filesystem that does not fully support file locking via flock(), such
- as NFS mounts. This support is required for Bugzilla to operate safely
- with multiple instances. If flock() is not fully supported, it will
- stall at: Now regenerating the shadow database for all bugs.
-
- Note: The second time you run checksetup.pl, it is recommended you
- be the same user as your web server runs under, and that you be
- sure you have set the "webservergroup" parameter in localconfig to
- match the web server's group name, if any. Under some systems,
- otherwise, checksetup.pl will goof up your file permissions and
- make them unreadable to your web server.
-
- Note: The checksetup.pl script is designed so that you can run it
- at any time without causing harm. You should run it after any
- upgrade to Bugzilla.
+ Customized User Preferences offer tremendous versatility to your
+ individual Bugzilla experience. Let's plunge into what you can do! The
+ first step is to click the "Edit prefs" link at the footer of each
+ page once you have logged in to Landfill.
_________________________________________________________________
-2.1.2.16. Setting Up Maintainers Manuall (Optional)
-
- If you want to add someone else to every group by hand, you can do it
- by typing the appropriate MySQL commands. Run ' mysql -u root -p bugs'
- (you may need different parameters, depending on your security
- settings according to section 3, above). Then:
+2.4.1. Account Settings
- mysql> update profiles set groupset=0x7fffffffffffffff where
- login_name = 'XXX';
+ On this page, you can change your basic Account Settings, including
+ your password and full name. For security reasons, in order to change
+ anything on this page you must type your current password into the
+ "Old Password" field. If you wish to change your password, type the
+ new password you want into the "New Password" field and again into the
+ "Re-enter new password" field to ensure you typed your new password
+ correctly. Select the "Submit" button and you are done.
+ _________________________________________________________________
- replacing XXX with the Bugzilla email address.
+2.4.2. Email Settings
+
+2.4.2.1. Email Notification
+
+ Here you can reduce or increase the amount of email sent you from
+ Bugzilla. Although this is referred to as "Advanced Email Filtering
+ Options", they are, in fact, the standard email filter set. All of
+ them are self-explanatory, but you can use the filters in interesting
+ ways. For instance, some people (notably Quality Assurance personnel)
+ often only care to receive updates regarding a bug when the bug
+ changes state, so they can track bugs on their flow charts and know
+ when it is time to pull the bug onto a quality assurance platform for
+ inspection. Other people set up email gateways to Bonsai, the Mozilla
+ automated CVS management system or Tinderbox, the Mozilla automated
+ build management system, and restrict which types of Bugzilla
+ information are fed to these systems..
_________________________________________________________________
-2.1.2.17. The Whining Cron (Optional)
+2.4.2.2. New Email Technology
- By now you've got a fully functional bugzilla, but what good are bugs
- if they're not annoying? To help make those bugs more annoying you can
- set up bugzilla's automatic whining system. This can be done by adding
- the following command as a daily crontab entry (for help on that see
- that crontab man page):
+ Note
- cd <your-bugzilla-directory> ; ./whineatnews.pl
- _________________________________________________________________
+ This option may not be available in all Bugzilla installations,
+ depending upon the preferences of the systems administrator
+ responsible for the setup of your Bugzilla. However, if you really
+ want this functionality, ask her to "enable newemailtech in Params"
+ and "make it the default for all new users", referring her to the
+ Administration section of this Guide.
-2.1.2.18. Bug Graphs (Optional)
+ Disregard the warnings about "experimental and bleeding edge"; the
+ code to handle email in a cleaner manner than that historically used
+ for Bugzilla is quite robust and well-tested now.
- As long as you installed the GD and Graph::Base Perl modules you might
- as well turn on the nifty bugzilla bug reporting graphs.
+ I recommend you enable the option, "Click here to sign up (and risk
+ any bugs)". Your email-box will thank you for it. The fundamental
+ shift in "newemailtech" is away from standard UNIX "diff" output,
+ which is quite ugly, to a prettier, better laid-out email.
+ _________________________________________________________________
- Add a cron entry like this to run collectstats daily at 5 after
- midnight:
+2.4.2.3. "Watching" Users
- bash# crontab -e
- 5 0 * * * cd <your-bugzilla-directory> ; ./collectstats.pl
+ Note
- After two days have passed you'll be able to view bug graphs from the
- Bug Reports page.
+ This option may not be available in all Bugzilla installations,
+ depending upon the preferences of the systems administrator
+ responsible for the setup of your Bugzilla. However, if you really
+ want this functionality, ask her to "enable watchers in Params".
+
+ By entering user email names into the "Users to watch" text entry box,
+ delineated by commas, you can watch bugs of other users. This powerful
+ functionality enables seamless transitions as developers change
+ projects, managers wish to get in touch with the issues faced by their
+ direct reports, or users go on vacation. If any of these three
+ situations apply to you, you will undoubtedly find this feature quite
+ convenient.
_________________________________________________________________
-2.1.2.19. Securing MySQL
+2.4.3. Page Footer
- If you followed the README for setting up your "bugs" and "root" user
- in MySQL, much of this should not apply to you. If you are upgrading
- an existing installation of Bugzilla, you should pay close attention
- to this section.
+ Note
- Most MySQL installs have "interesting" default security parameters:
+ By default, this page is quite barren. However, go explore the Query
+ Page some more; you will find that you can store numerous queries on
+ the server, so if you regularly run a particular query it is just a
+ drop-down menu away. On this page of Preferences, if you have many
+ stored queries you can elect to have them always one-click away!
- 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"
+ If you have many stored queries on the server, here you will find
+ individual drop-downs for each stored query. Each drop-down gives you
+ the option of that query appearing on the footer of every page in
+ Bugzilla! This gives you powerful one-click access to any complex
+ searches you may set up, and is an excellent way to impress your
+ boss...
- 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.
+ Tip
+
+ By default, the "My Bugs" link appears at the bottom of each page.
+ However, this query gives you both the bugs you have reported, as well
+ as those you are assigned. One of the most common uses for this page
+ is to remove the "My Bugs" link, replacing it with two other queries,
+ commonly called "My Bug Reports" and "My Bugs" (but only referencing
+ bugs assigned to you). This allows you to distinguish those bugs you
+ have reported from those you are assigned. I commonly set up complex
+ Boolean queries in the Query page and link them to my footer in this
+ page. When they are significantly complex, a one-click reference can
+ save hours of work.
+ _________________________________________________________________
- To see your permissions do:
+2.4.4. Permissions
- bash# mysql -u root -p
- mysql> use mysql;
- mysql> show tables;
- mysql> select * from user;
- mysql> select * from db;
+ This is a purely informative page which outlines your current
+ permissions on this installation of Bugzilla. If you have permissions
+ to grant certain permissions to other users, the "other users" link
+ appears on this page as well as the footer. For more information
+ regarding user administration, please consult the Administration
+ section of this Guide.
+ _________________________________________________________________
- To fix the gaping holes:
+2.5. Using Bugzilla-Conclusion
- DELETE FROM user WHERE User='';
- UPDATE user SET Password=PASSWORD('new_password') WHERE user='root';
- FLUSH PRIVILEGES;
+ Thank you for reading through this portion of the Bugzilla Guide. I
+ anticipate it may not yet meet the needs of all readers. If you have
+ additional comments or corrections to make, please submit your
+ contributions to the mozilla-webtools mailing list/newsgroup. The
+ mailing list is mirrored to the netscape.public.mozilla.webtools
+ newsgroup, and the newsgroup is mirrored to
+ mozilla-webtools@mozilla.org
+ _________________________________________________________________
- If you're not running "mit-pthreads" you can use:
+Chapter 3. Installation
- GRANT USAGE ON *.* TO bugs@localhost;
- GRANT ALL ON bugs.* TO bugs@localhost;
- REVOKE DROP ON bugs.* FROM bugs@localhost;
- FLUSH PRIVILEGES;
+ These installation instructions are presented assuming you are
+ installing on a UNIX or completely POSIX-compliant system. If you are
+ installing on Microsoft Windows or another oddball operating system,
+ please consult the appropriate sections in this installation guide for
+ notes on how to be successful.
+ _________________________________________________________________
- 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:
+3.1. ERRATA
+
+ Here are some miscellaneous notes about possible issues you main run
+ into when you begin your Bugzilla installation. Reference platforms
+ for Bugzilla installation are Redhat Linux 7.2, Linux-Mandrake 8.0,
+ and Solaris 8.
+
+ If you are installing Bugzilla on S.u.S.e. Linux, or some other
+ distributions with "paranoid" security options, it is possible that
+ the checksetup.pl script may fail with the error: 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 problem.
+ Bugzilla may be installed on Macintosh OS X (10), which is a
+ unix-based (BSD) operating system. Everything required for Bugzilla on
+ OS X will install cleanly, but the optional GD perl module which is
+ used for bug charting requires some additional setup for installation.
+ Please see the Mac OS X installation section below for details
+ Release Notes for Bugzilla 2.14 are available at docs/rel_notes.txt in
+ your Bugzilla source distribution.
+ The preferred documentation for Bugzilla is available in docs/, with a
+ variety of document types available. Please refer to these documents
+ when installing, configuring, and maintaining your Bugzilla
+ installation.
- 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;
+ Warning
- Consider also:
+ Bugzilla is not a package where you can just plop it in a directory,
+ twiddle a few things, and you're off. Installing Bugzilla assumes you
+ know your variant of UNIX or Microsoft Windows well, are familiar with
+ the command line, and are comfortable compiling and installing a
+ plethora of third-party utilities. To install Bugzilla on Win32
+ requires fair Perl proficiency, and if you use a webserver other than
+ Apache you should be intimately familiar with the security mechanisms
+ and CGI environment thereof.
- 1. Turning off external networking with "--skip-networking", unless
- you have "mit-pthreads", in which case you can't. Without
- networking, MySQL connects with a Unix domain socket.
- 2. using the --user= option to mysqld to run it as an unprivileged
- user.
- 3. starting MySQL in a chroot jail
- 4. running the httpd in a "chrooted" jail
- 5. making sure the MySQL passwords are different from the OS
- passwords (MySQL "root" has nothing to do with system "root").
- 6. running MySQL on a separate untrusted machine
- 7. making backups ;-)
+ Warning
+
+ Bugzilla has not undergone a complete security review. Security holes
+ may exist in the code. Great care should be taken both in the
+ installation and usage of this software. Carefully consider the
+ implications of installing other network services with Bugzilla.
_________________________________________________________________
-2.1.2.20. Installation General Notes
+3.2. Step-by-step Install
-2.1.2.20.1. Modifying Your Running System
+3.2.1. Introduction
- Bugzilla optimizes database lookups by storing all relatively static
- information in the versioncache file, located in the data/
- subdirectory under your installation directory (we said before it
- needs to be writable, right?!)
+ Installation of bugzilla is pretty straightforward, particularly if
+ your machine already has MySQL and the MySQL-related perl packages
+ installed. If those aren't installed yet, then that's the first order
+ of business. The other necessary ingredient is a web server set up to
+ run cgi scripts. While using Apache for your webserver is not
+ required, it is recommended.
- If you make a change to the structural data in your database (the
- versions table for example), or to the "constants" encoded in
- defparams.pl, you will need to remove the cached content from the data
- directory (by doing a "rm data/versioncache"), or your changes won't
- show up!
+ Bugzilla has been successfully installed under Solaris, Linux, and
+ Win32. The peculiarities of installing on Win32 (Microsoft Windows)
+ are not included in this section of the Guide; please check out the
+ Win32 Installation Notes for further advice on getting Bugzilla to
+ work on Microsoft Windows.
- That file gets automatically regenerated whenever it's more than an
- hour old, so Bugzilla will eventually notice your changes by itself,
- but generally you want it to notice right away, so that you can test
- things.
+ The Bugzilla Guide is contained in the "docs/" folder in your Bugzilla
+ distribution. It is available in plain text (docs/txt), HTML
+ (docs/html), or SGML source (docs/sgml).
_________________________________________________________________
-2.1.2.20.2. Upgrading From Previous Versions
+3.2.2. Installing the Prerequisites
- The developers of Bugzilla are constantly adding new tables, columns
- and fields. You'll get SQL errors if you just update the code. The
- strategy to update is to simply always run the checksetup.pl script
- whenever you upgrade your installation of Bugzilla. If you want to see
- what has changed, you can read the comments in that file, starting
- from the end.
- _________________________________________________________________
+ Note
-2.1.2.20.3. UNIX Installation Instructions History
+ If you want to skip these manual installation steps for the CPAN
+ dependencies listed below, and are running the very most recent
+ version of Perl and MySQL (both the executables and development
+ libraries) on your system, check out Bundle::Bugzilla in Using
+ Bundle::Bugzilla instead of manually installing Perl modules
- This document was originally adapted from the Bonsai installation
- instructions by Terry Weissman <terry@mozilla.org>.
+ The software packages necessary for the proper running of bugzilla
+ are:
- The February 25, 1999 re-write of this page was done by Ry4an Brase
- <ry4an@ry4an.org>, with some edits by Terry Weissman, Bryce Nesbitt,
- Martin Pool, & Dan Mosedale (But don't send bug reports to them!
- Report them using bugzilla, at
- http://bugzilla.mozilla.org/enter_bug.cgi , project Webtools,
- component Bugzilla).
+ 1. MySQL database server and the mysql client (3.22.5 or greater)
+ 2. Perl (5.004 or greater, 5.6.1 is recommended if you wish to use
+ Bundle::Bugzilla)
+ 3. DBI Perl module
+ 4. Data::Dumper Perl module
+ 5. Bundle::Mysql Perl module collection
+ 6. TimeDate Perl module collection
+ 7. GD perl module (1.8.3) (optional, for bug charting)
+ 8. Chart::Base Perl module (0.99c) (optional, for bug charting)
+ 9. DB_File Perl module (optional, for bug charting)
+ 10. The web server of your choice. Apache is recommended.
+ 11. MIME::Parser Perl module (optional, for contrib/bug_email.pl
+ interface)
- This document was heavily modified again Wednesday, March 07 2001 to
- reflect changes for Bugzilla 2.12 release by Matthew P. Barnson. The
- securing MySQL section should be changed to become standard procedure
- for Bugzilla installations.
+ Warning
- Finally, the README in its entirety was marked up in SGML and included
- into the Guide on April 24, 2001.
+ It is a good idea, while installing Bugzilla, to ensure it is not
+ accessible by other machines on the Internet. Your machine may be
+ vulnerable to attacks while you are installing. In other words, ensure
+ there is some kind of firewall between you and the rest of the
+ Internet. Many installation steps require an active Internet
+ connection to complete, but you must take care to ensure that at no
+ point is your machine vulnerable to an attack.
- Comments from people using this Guide for the first time are
- particularly welcome.
- _________________________________________________________________
+ Note
-2.2. Win32 (Win98+/NT/2K) Installation
+ Linux-Mandrake 8.0, the author's test system, includes every required
+ and optional library for Bugzilla. The easiest way to install them is
+ by using the urpmi utility. If you follow these commands, you should
+ have everything you need for Bugzilla, and checksetup.pl should not
+ complain about any missing libraries. You may already have some of
+ these installed.
- These directions have not been extensively tested. We need testers!
- Please try these out and post any changes to the newsgroup.
+ bash# urpmi perl-mysql
+ bash# urpmi perl-chart
+ bash# urpmi perl-gd
+ bash# urpmi perl-MailTools (for Bugzilla email integration)
+ bash# urpmi apache-modules
_________________________________________________________________
-2.2.1. Win32 Installation: Step-by-step
+3.2.3. Installing MySQL Database
- Note: You should be familiar with, and cross-reference, the UNIX
- README while performing your Win32 installation. Unfortunately,
- Win32 directions are not yet as detailed as those for UNIX.
+ Visit MySQL homepage at www.mysql.com and grab the latest stable
+ release of the server. Many of the binary versions of MySQL store
+ their data files in /var which is often part of a smaller root
+ partition. If you decide to build from sources you can easily set the
+ dataDir as an option to configure.
- The most critical difference for Win32 users is the lack of support
- for a crypt() function in MySQL for Windows. It does not have it!
- All ENCRYPT statements must be modified.
+ If you install from source or non-package (RPM, deb, etc.) binaries
+ you need to add mysqld to your init scripts so the server daemon will
+ come back up whenever your machine reboots. Further discussion of UNIX
+ init sequences are beyond the scope of this guide.
- 1. Install Apache Web Server for Windows.
+ Note
- Note: You may also use Internet Information Server or Personal Web
- Server for this purpose. However, setup is slightly more difficult.
- If ActivePerl doesn't seem to handle your file associations
- correctly (for .cgi and .pl files), please consult the FAQ, in the
- "Win32" section.
- If you are going to use IIS, if on Windows NT you must be updated
- to at least Service Pack 4.
- 2. Install ActivePerl
- Please also check the following links to fully understand the
- status of ActivePerl on Win32: Perl Porting, and Hixie Click Here
- 3. Use ppm from your perl\bin directory to install the following
- packs: DBI, DBD-Mysql, TimeDate, Chart, Date-Calc, Date-Manip, and
- GD. You may need to extract them from .zip format using Winzip or
- other unzip program first. These additional ppm modules can be
- downloaded from ActiveState.
- The syntax for ppm is: C:> ppm install <module>.ppd
- You can find ActiveState ppm modules at
- http://www.activestate.com/PPMPackages/5.6plus
- 4. Download and install the Windows GNU tools from www.cygwin.com.
- Make sure the GNU utilities are in your $PATH.
- 5. Install MySQL for NT.
+ You should have your init script start mysqld with the ability to
+ accept large packets. By default, mysqld only accepts packets up to
+ 64K long. This limits the size of attachments you may put on bugs. If
+ you add -O max_allowed_packet=1M to the command that starts mysqld (or
+ safe_mysqld), then you will be able to have attachments up to about 1
+ megabyte.
- Note: Your configuration file for MySQL must be named C:\MY.CNF.
- 6. Setup MySQL
- a. C:> C:\mysql\bin\mysql -u root mysql
- b. mysql> DELETE FROM user WHERE Host='localhost' AND User='';
- c. mysql> UPDATE user SET Password=PASSWORD ('new_password')
- WHERE user='root';
- d. mysql> GRANT SELECT, INSERT, UPDATE, DELETE, INDEX, ALTER,
- CREATE, DROP, REFERENCES ON bugs.* to bugs@localhost
- IDENTIFIED BY 'bugs_password';
- e. mysql> FLUSH PRIVILEGES;
- f. mysql> create database bugs;
- g. mysql> exit
- h. C:> C:\mysql\bin\mysqladmin -u root -p reload
- 7. Configure Bugzilla. For Win32, this involves editing
- "defparams.pl" and "localconfig" to taste. Running "checksetup.pl"
- should create localconfig for you. Note that getgrnam() doesn't
- work, and should be deleted. Change this line: "my $webservergid =
- getgrnam($my_webservergroup); " to "my $webservergid =
- $my_webservergroup; "
- 8.
-
- Note: There are several alternatives to Sendmail that will work on
- Win32. The one mentioned here is a suggestion, not a requirement.
- Some other mail packages that can work include BLAT, Windmail,
- Mercury Sendmail, and the CPAN Net::SMTP Perl module (available in
- .ppm). Every option requires some hacking of the Perl scripts for
- Bugzilla to make it work. The option here simply requires the
- least.
- Download NTsendmail, available from www.ntsendmail.com. In order
- for it to work, you must set up some new environment variables
- (detailed on the ntsendmail home page). Figuring out where to put
- those variables is left as an exercise for the reader. 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)
- Once downloaded and installed, modify all open(SENDMAIL) calls to
- open "| c:\ntsendmail\ntsendmail -t" instead of
- "|/usr/lib/sendmail -t".
-
- Note: We need someone to test this and make sure this works as
- advertised.
- 9. Modify globals.pl and CGI.pl to remove the word "encrypt".
-
- Note: I'm not sure this is all that is involved to remove crypt.
- Any NT Bugzilla hackers want to pipe up?
- 10. Change all references to "processmail" to "processmail.pl" in all
- files, and rename "processmail" to "processmail.pl"
-
- Note: I really 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.
- 11. 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.pl" utility to
- speed part of this procedure, available in the "Patches and
- Utilities" section of The Bugzilla Guide.
- 12. In processmail.pl, add "binmode(HANDLE)" before all read() calls.
- This may not be necessary, but in some cases the read() under
- Win32 doesn't count the EOL's without using a binary read().
+ Note
+
+ If you plan on running Bugzilla and MySQL on the same machine,
+ consider using the --skip-networking option in the init script. This
+ enhances security by preventing network access to MySQL.
_________________________________________________________________
-2.2.2. Additional Windows Tips
+3.2.4. Perl (5.004 or greater)
- Tip: From Andrew Pearson:
+ Any machine that doesn't have perl on it is a sad machine indeed. Perl
+ for *nix systems can be gotten in source form from
+ http://www.perl.com. Although Bugzilla runs with most post-5.004
+ 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.
- "You can make Bugzilla work with Personal Web Server for Windows 98
- and higher, as well as for IIS 4.0. Microsoft has information
- available at
- http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP
+ Perl is now a far cry from the the single compiler/interpreter binary
+ it once was. It includes a great many required modules and quite a few
+ other support files. If you're not up to or not inclined to build perl
+ from source, you'll want to install it on your machine using some sort
+ of packaging system (be it RPM, deb, or what have you) to ensure a
+ sane install. In the subsequent sections you'll be installing quite a
+ few perl modules; this can be quite ornery if your perl installation
+ isn't up to snuff.
- Basically you need to add two String Keys in the registry at the
- following location:
+ Warning
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Paramete
- rs\ScriptMap
+ Many people complain that Perl modules will not install for them. Most
+ times, the error messages complain that they are missing a file in
+ "@INC". Virtually every time, this is due to permissions being set too
+ restrictively for you to compile Perl modules or not having the
+ necessary Perl development libraries installed on your system..
+ Consult your local UNIX systems administrator for help solving these
+ permissions issues; if you are the local UNIX sysadmin, please consult
+ the newsgroup/mailing list for further assistance or hire someone to
+ help you out.
+
+ Tip
+
+ You can skip the following Perl module installation steps by
+ installing Bundle::Bugzilla from CPAN, which includes them. All Perl
+ module installation steps require you have an active Internet
+ connection. If you wish to use Bundle::Bugzilla, however, you must be
+ using the latest version of Perl (at this writing, version 5.6.1)
+
+ bash# perl -MCPAN -e 'install "Bundle::Bugzilla"'
+
+ Bundle::Bugzilla doesn't include GD, Chart::Base, or MIME::Parser,
+ which are not essential to a basic Bugzilla install. If installing
+ this bundle fails, you should install each module individually to
+ isolate the problem.
+ _________________________________________________________________
- The keys should be called ".pl" and ".cgi", and both should have a
- value something like: c:/perl/bin/perl.exe "%s" "%s"
+3.2.5. DBI Perl Module
- The KB article only talks about .pl, but it goes into more detail
- and provides a perl test script.
+ The DBI module is a generic Perl module used by other database related
+ Perl modules. For our purposes it's required by the MySQL-related
+ modules. As long as your Perl installation was done correctly the DBI
+ module should be a breeze. It's a mixed Perl/C module, but Perl's
+ MakeMaker system simplifies the C compilation greatly.
+
+ Like almost all Perl modules DBI can be found on the Comprehensive
+ Perl Archive Network (CPAN) at http://www.cpan.org. The CPAN servers
+ have a real tendency to bog down, so please use mirrors. The current
+ location at the time of this writing can be found in Appendix B.
+
+ 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.
- Tip: "Brian" had this to add, about upgrading to Bugzilla 2.12 from
- previous versions:
+ To use the CPAN shell to install DBI:
- Hi - I am updating bugzilla to 2.12 so I can tell you what I did
- (after I deleted the current dir and copied the files in).
+ bash# perl -MCPAN -e 'install "DBI"'
- In checksetup.pl, I did the following...
+ Note
- 1.
+ Replace "DBI" with the name of whichever module you wish to install,
+ such as Data::Dumper, TimeDate, GD, etc.
-my $webservergid = getgrnam($my_webservergroup);
+ To do it the hard way:
+ Untar the module tarball -- it should create its own directory
- to
+ CD to the directory just created, and enter the following commands:
-my $webservergid = 'Administrators'
+ 1. bash# perl Makefile.PL
+ 2. bash# make
+ 3. bash# make test
+ 4. bash# make install
+ If everything went ok that should be all it takes. For the vast
+ majority of perl modules this is all that's required.
+ _________________________________________________________________
- 2. I then ran checksetup.pl
- 3. I removed all the encrypt()
- Example 2-1. Removing encrypt() for Windows NT installations
- Replace this:
+3.2.6. Data::Dumper Perl Module
-SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " .
- SqlQuote(substr($realcryptpwd, 0, 2)) . ")");
-my $enteredcryptpwd = FetchOneColumn();
+ The Data::Dumper module provides data structure persistence for Perl
+ (similar to Java's serialization). It comes with later sub-releases of
+ Perl 5.004, but a re-installation just to be sure it's available won't
+ hurt anything.
+ Data::Dumper is used by the MySQL-related Perl modules. It can be
+ found on CPAN (see Appendix B) and can be installed by following the
+ same four step make sequence used for the DBI module.
+ _________________________________________________________________
- with this:
+3.2.7. MySQL related Perl Module Collection
-my $enteredcryptpwd = $enteredpwd
+ The Perl/MySQL interface requires a few mutually-dependent perl
+ modules. These modules are grouped together into the the
+ Msql-Mysql-modules package. This package can be found at CPAN. After
+ the archive file has been downloaded it should be untarred.
+
+ The MySQL modules are all built using one make file which is generated
+ by running: bash# perl Makefile.pl
+ The MakeMaker process will ask you a few questions about the desired
+ compilation target and your MySQL installation. For many of the
+ questions the provided default will be adequate.
- in cgi.pl.
- 4. I renamed processmail to processmail.pl
- 5. I altered the sendmail statements to windmail:
+ When asked if your desired target is the MySQL or mSQL packages,
+ select the MySQL related ones. Later you will be asked if you wish 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' and
+ a null password should find itself with sufficient access to run tests
+ on the 'test' database which MySQL created upon installation. If 'make
+ test' and 'make install' go through without errors you should be ready
+ to go as far as database connectivity is concerned.
+ _________________________________________________________________
-open SENDMAIL, "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t > mail.
-log";
+3.2.8. TimeDate Perl Module Collection
- The quotes around the dir is for the spaces. mail.log is for the
- output
+ 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 (see link:
+ Appendix B). The component module we're most interested in is the
+ Date::Format module, but installing all of them is probably a good
+ idea anyway. The standard Perl module installation instructions should
+ work perfectly for this simple package.
_________________________________________________________________
-Chapter 3. Administering Bugzilla
+3.2.9. GD Perl Module (1.8.3)
- Or, I just got this cool thing installed. Now what the heck do I do
- with it?
+ 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.
- So you followed the README isntructions to the letter, and just logged
- into bugzilla with your super-duper god account and you are sitting at
- the query screen. Yet, you have nothing to query. Your first act of
- business needs to be to setup the operating parameters for bugzilla.
+ Actually bugzilla uses the Graph module which relies on GD itself.
+ Isn't that always the way with object-oriented programming? At any
+ rate, you can find the GD library on CPAN in Appendix B.
+
+ Note
+
+ The Perl GD library requires some other libraries that may or may not
+ be installed on your system, including libpng and libgd. The full
+ requirements are listed in the Perl GD library README. Just realize
+ that if compiling GD fails, it's probably because you're missing a
+ required library.
_________________________________________________________________
-3.1. Post-Installation Checklist
-
- After installation, follow the checklist below to ensure that you have
- a successful installation. If you do not see a recommended setting for
- a parameter, consider leaving it at the default while you perform your
- initial tests on your Bugzilla setup.
- 1. Bring up "editparams.cgi" in your web browser. For instance, to
- edit parameters at mozilla.org, the URL would be
- http://bugzilla.mozilla.org/editparams.cgi, also available under
- the "edit parameters" link on your query page.
- 2. Set "maintainer" to your email address. This allows Bugzilla's
- error messages to display your email address and allow people to
- contact you for help.
- 3. Set "urlbase" to the URL reference for your Bugzilla installation.
- If your bugzilla query page is at
- http://www.foo.com/bugzilla/query.cgi, your url base is
- http://www.foo.com/bugzilla/
- 4. Set "usebuggroups" to "1" only if you need to restrict access to
- products. I suggest leaving this parameter off while initially
- testing your Bugzilla.
- 5. Set "usebuggroupsentry" to "1" if you want to restrict access to
- products. Once again, if you are simply testing your installation,
- I suggest against turning this parameter on; the strict security
- checking may stop you from being able to modify your new entries.
- 6. Set "shadowdb" to "bug_shadowdb" if you will be running a *very*
- large installation of Bugzilla. The shadow database enables many
- simultaneous users to read and write to the database without
- interfering with one another.
+3.2.10. Chart::Base Perl Module (0.99c)
- Note: Enabling "shadowdb" can adversely affect the stability of
- your installation of Bugzilla. You may frequently need to manually
- synchronize your databases, or schedule nightly syncs via "cron"
- Once again, in testing you should avoid this option -- use it if
- or when you need to use it, and have repeatedly run into the
- problem it was designed to solve -- very long wait times while
- attempting to commit a change to the database.
- If you use the "shadowdb" option, it is only natural that you
- should turn the "queryagainstshadowdb" option "On" as well.
- Otherwise you are replicating data into a shadow database for no
- reason!
- 7. If you have custom logos or HTML you must put in place to fit
- within your site design guidelines, place the code in the
- "headerhtml", "footerhtml", "errorhtml", "bannerhtml", or
- "blurbhtml" text boxes.
-
- Note: The "headerhtml" text box is the HTML printed out before any
- other code on the page. If you have a special banner, put the code
- for it in "bannerhtml". You may want to leave these settings at the
- defaults initially.
- 8. Add any text you wish to the "passwordmail" parameter box. For
- instance, many people choose to use this box to give a quick
- training blurb about how to use Bugzilla at your site.
- 9. Ensure "newemailtech" is "on". Your users will thank you. This is
- the default in the post-2.12 world, and is only an issue if you
- are upgrading.
- 10. Do you want to use the qa contact ("useqacontact") and status
- whiteboard ("usestatuswhiteboard") fields? These fields are useful
- because they allow for more flexibility, particularly when you
- have an existing Quality Assurance and/or Release Engineering
- team, but they may not be needed for smaller installations.
- 11. Set "whinedays" to the amount of days you want to let bugs go in
- the "New" or "Reopened" state before notifying people they have
- untouched new bugs. If you do not plan to use this feature, simply
- do not set up the whining cron job described in the README, or set
- this value to "0".
- 12. Set the "commenton" options according to your site policy. It is a
- wise idea to require comments when users resolve, reassign, or
- reopen bugs.
-
- Note: It is generally far better to require a developer comment
- when resolving bugs than not. Few things are more annoying to bug
- database users than having a developer mark a bug "fixed" without
- any comment as to what the fix was (or even that it was truly
- fixed!)
- 13. Set "supportwatchers" to "On". This feature is helpful for team
- leads to monitor progress in their respective areas, and can offer
- many other benefits, such as allowing a developer to pick up a
- former engineer's bugs without requiring her to change all the
- information in the bug.
+ The Chart module provides bugzilla with on-the-fly charting abilities.
+ It can be installed in the usual fashion after it has been fetched
+ from CPAN where it is found as the Chart-x.x... tarball, linked in
+ Appendix B. Note that as with the GD perl module, only the version
+ listed above, or newer, will work. Earlier versions used GIF's, which
+ are no longer supported by the latest versions of GD.
_________________________________________________________________
-3.2. User Administration
+3.2.11. DB_File Perl Module
- User administration is one of the easiest parts of Bugzilla. Keeping
- it from getting out of hand, however, can become a challenge.
+ DB_File is a module which allows Perl programs to make use of the
+ facilities provided by Berkeley DB version 1.x. This module is
+ required by collectstats.pl which is used for bug charting. If you
+ plan to make use of bug charting, you must install this module.
_________________________________________________________________
-3.2.1. Creating the Default User
+3.2.12. HTTP Server
- 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 were to delete
- the "super user" account, re-running checksetup.pl will again prompt
- you for this username and password.
+ You have a freedom of choice here - Apache, Netscape or any other
+ server on UNIX would do. You can easily run the web server on a
+ different machine than MySQL, but need to adjust the MySQL "bugs" user
+ permissions accordingly.
- Tip: If you wish to add more administrative users, you must use the
- MySQL interface. Run "mysql" from the command line, and use these
- commands ("mysql>" denotes the mysql prompt, not something you
- should type in): mysql> use bugs; mysql> update profiles set
- groupset=0x7ffffffffffffff where login_name = "(user's login
- name)";
- _________________________________________________________________
+ Note
-3.2.2. Managing Other Users
+ I strongly recommend Apache as the web server to use. The Bugzilla
+ Guide installation instructions, in general, assume you are using
+ Apache. As more users use different webservers and send me information
+ on the peculiarities of installing using their favorite webserver, I
+ will provide notes for them.
-3.2.2.1. Logging In
+ You'll want to make sure that your web server will run any file with
+ the .cgi extension as a cgi and not just display it. If you're using
+ apache that means uncommenting the following line in the srm.conf
+ file:
+ AddHandler cgi-script .cgi
- 1. Open the index.html page for your Bugzilla installation in your
- browser window.
- 2. Click the "Query Existing Bug Reports" link.
- 3. Click the "Log In" link at the foot of the page.
- 4. Type your email address, and the password which was emailed to you
- when you created your Bugzilla account, into the spaces provided.
+ With apache you'll also want to make sure that within the access.conf
+ file the line:
+ Options ExecCGI
- Congratulations, you are logged in!
+ is in the stanza that covers the directories into which you intend to
+ put the bugzilla .html and .cgi files.
+
+ Note
+
+ Users of newer versions of Apache will generally find both of the
+ above lines will be in the httpd.conf file, rather than srm.conf or
+ access.conf.
+
+ Warning
+
+ There are important files and directories that should not be a served
+ by the HTTP server. These are most files in the "data" and "shadow"
+ directories and the "localconfig" file. You should configure your HTTP
+ server to not serve content from these files. Failure to do so will
+ expose critical passwords and other data. Please see .htaccess files
+ and security for details on how to do this for Apache. I appreciate
+ notes on how to get this same functionality using other webservers.
_________________________________________________________________
-3.2.2.2. Creating new users
+3.2.13. Installing the Bugzilla Files
- Your users can create their own user accounts by clicking the "New
- Account" link at the bottom of each page. However, should you desire
- to create user accounts ahead of time, here is how you do it.
+ You should untar the Bugzilla files into a directory that you're
+ willing to make writable by the default web server user (probably
+ "nobody"). You may decide to put the files off of the main web space
+ for your web server or perhaps off of /usr/local with a symbolic link
+ in the web space that points to the Bugzilla directory. At any rate,
+ just dump all the files in the same place, and make sure you can
+ access the files in that directory through your web server.
- 1. After logging in, click the "Users" link at the footer of the
- query page.
- 2. To see a specific user, type a portion of their login name in the
- box provided and click "submit". To see all users, simply click
- the "submit" button. You must click "submit" here to be able to
- add a new user.
+ Tip
- Tip: More functionality is available via the list on the right-hand
- side of the text entry box. You can match what you type as a
- case-insensitive substring (the default) of all users on your
- system, a case-sensitive regular expression (please see the "man
- regexp" manual page for details on regular expression syntax), or a
- reverse regular expression match, where every user name which does
- NOT match the regular expression is selected.
- 3. Click the "Add New User" link at the bottom of the user list
- 4. Fill out the form presented. This page is self-explanatory. When
- done, click "submit".
+ If you symlink the bugzilla directory into your Apache's HTML
+ heirarchy, you may receive Forbidden errors unless you add the
+ "FollowSymLinks" directive to the <Directory> entry for the HTML root.
- Note: Adding a user this way will not send an email informing them
- of their username and password. In general, it is preferable to log
- out and use the "New Account" button to create users, as it will
- pre-populate all the required fields and also notify the user of
- her account name and password.
+ Once all the files are in a web accessible directory, make that
+ directory writable by your webserver's user. This is a temporary step
+ until you run the post-install checksetup.pl script, which locks down
+ your installation.
+
+ Lastly, you'll need to set up a symbolic link to
+ /usr/bonsaitools/bin/perl for the correct location of your perl
+ executable (probably /usr/bin/perl). Otherwise you must hack all the
+ .cgi files to change where they look for perl, or use The setperl.csh
+ Utility, found in Useful Patches and Utilities for Bugzilla. I suggest
+ using the symlink approach for future release compatability.
+
+ Example 3-1. Setting up bonsaitools symlink
+
+ Here's how you set up the Perl symlink on Linux to make Bugzilla work.
+ Your mileage may vary. For some UNIX operating systems, you probably
+ need to subsitute "/usr/local/bin/perl" for "/usr/bin/perl" below; if
+ on certain other UNIX systems, Perl may live in weird places like
+ "/opt/perl". As root, run these commands:
+bash# mkdir /usr/bonsaitools
+bash# mkdir /usr/bonsaitools/bin
+bash# ln -s /usr/bin/perl /usr/bosaitools/bin/perl
+
+ Alternately, you can simply run this perl one-liner to change your
+ path to perl in all the files in your Bugzilla installation:
+perl -pi -e 's@#!/usr/bonsaitools/bin/perl@#!/usr/bin/perl@' *cgi *pl Bug.pm
+
+ Change the second path to perl to match your installation.
+
+ Tip
+
+ If you don't have root access to set this symlink up, check out the
+ The setperl.csh Utility, listed in Useful Patches and Utilities for
+ Bugzilla. It will change the path to perl in all your Bugzilla files
+ for you.
_________________________________________________________________
-3.2.2.3. Disabling Users
+3.2.14. Setting Up the MySQL Database
- I bet you noticed that big "Disabled Text" entry box available from
- the "Add New User" screen, when you edit an account? By entering any
- text in this box and selecting "submit", you have prevented the user
- from using Bugzilla via the web interface. Your explanation, written
- in this text box, will be presented to the user the next time she
- attempts to use the system.
+ After you've gotten all the software installed and working you're
+ ready to start preparing the database for its life as a the back end
+ to a high quality bug tracker.
+
+ First, you'll want to fix MySQL permissions to allow access from
+ Bugzilla. For the purpose of this Installation section, the Bugzilla
+ username will be "bugs", and will have minimal permissions.
Warning
- Don't disable your own administrative account, or you will hate life!
- _________________________________________________________________
+ Bugzilla has not undergone a thorough security audit. It may be
+ possible for a system cracker to somehow trick Bugzilla into executing
+ a command such as DROP DATABASE mysql.
-3.2.2.4. Modifying Users
+ That would be bad.
- Here I will attempt to describe the function of each option on the
- user edit screen.
+ Give the MySQL root user a password. MySQL passwords are limited to 16
+ characters.
- * Login Name: This is generally the user's email address. However,
- if you have edited your system parameters, this may just be the
- user's login name or some other identifier.
+ bash# mysql -u root mysql
+ mysql> UPDATE user SET Password=PASSWORD ('new_password') WHERE
+ user='root';
+ mysql> FLUSH PRIVILEGES;
- Tip: For compatability reasons, you should probably stick with
- email addresses as user login names. It will make your life easier.
- * Real Name: Duh!
- * Password: You will only see asterisks in versions of Bugzilla
- newer than 2.10 or early 2.11. You can change the user password
- here.
- * Email Notification: You may choose from one of three options:
- 1. All qualifying bugs except those which I change: The user
- will be notified of any change to any bug for which she is
- the reporter, assignee, Q/A contact, CC recipient, or
- "watcher".
- 2. Only those bugs which I am listed on the CC line: The user
- will not be notified of changes to bugs where she is the
- assignee, reporter, or Q/A contact, but will receive them if
- she is on the CC list.
+ From this point on, if you need to access MySQL as the MySQL root
+ user, you will need to use mysql -u root -p and enter your
+ new_password. Remember that MySQL user names have nothing to do with
+ Unix user names (login names).
- Note: She will still receive whining cron emails if you set up the
- "whinemail" feature.
- 3. All Qualifying Bugs: This user is a glutton for punishment.
- If her name is in the reporter, Q/A contact, CC, assignee, or
- is a "watcher", she will get email updates regarding the bug.
- Disable Text: If you type anything in this box, including just a
- space, the user account is disabled from making any changes to
- bugs via the web interface, and what you type in this box is
- presented as the reason.
+ Next, we create the "bugs" user, and grant sufficient permissions for
+ checksetup.pl, which we'll use later, to work its magic. This also
+ restricts the "bugs" user to operations within a database called
+ "bugs", and only allows the account to connect from "localhost".
+ Modify it to reflect your setup if you will be connecting from another
+ machine or as a different user.
- Warning
- Don't disable the administrator account!
+ Remember to set bugs_password to some unique password.
- Note: As of this writing, the user can still submit bugs via the
- e-mail gateway, if you set it up, despite the disabled text field.
- The e-mail gateway should not be enabled for secure installations
- of Bugzilla.
- * CanConfirm: This field is only used if you have enabled
- "unconfirmed" status in your parameters screen. If you enable this
- for a user, that user can then move bugs from "Unconfirmed" to
- "Confirmed" status (ergo: "New" status). Be judicious about
- allowing users to turn this bit on for other users.
- * Creategroups: This option will allow a user to create and destroy
- groups in Bugzilla. Unless you are using the Bugzilla GroupSentry
- security option "usebuggroupsentry" in your parameters, this
- setting has no effect.
- * Editbugs: Unless a user has this bit set, they can only edit those
- bugs for which they are the assignee or the reporter.
+ mysql> GRANT SELECT,INSERT,UPDATE,DELETE,INDEX,
+ ALTER,CREATE,DROP,REFERENCES ON bugs.* TO bugs@localhost IDENTIFIED BY
+ 'bugs_password';
+ mysql> FLUSH PRIVILEGES;
- Note: Leaving this option unchecked does not prevent users from
- adding comments to a bug! They simply cannot change a bug priority,
- severity, etc. unless they are the assignee or reporter.
- * Editcomponents: This flag allows a user to create new products and
- components, as well as modify and destroy those that have no bugs
- associated with them. If a product or component has bugs
- associated with it, those bugs must be moved to a different
- product or component before Bugzilla will allow them to be
- destroyed. The name of a product or component can be changed
- without affecting the associated bugs, but it tends to annoy the
- hell out of your users when these change a lot.
- * Editkeywords: If you use Bugzilla's keyword functionality,
- enabling this feature allows a user can create and destroy
- keywords. As always, the keywords for existing bugs containing the
- keyword the user wishes to destroy must be changed before Bugzilla
- will allow it to die. You must be very careful about creating too
- many new keywords if you run a very large Bugzilla installation;
- keywords are global variables across products, and you can often
- run into a phenomenon called "keyword bloat". This confuses users,
- and then the feature goes unused.
- * Editusers: This flag allows a user do what you're doing right now:
- edit other users. This will allow those with the right to do so to
- remove administrator priveleges from other users or grant them to
- themselves. Enable with care.
- * PRODUCT: PRODUCT bugs access. This allows an administrator, with
- product-level granularity, to specify in which products a user can
- edit bugs. The user must still have the "editbugs" privelege to
- edit bugs in this area; this simply restricts them from even
- seeing bugs outside these boundaries if the administrator has
- enabled the group sentry parameter "usebuggroupsentry". Unless you
- are using bug groups, this option has no effect.
+ Next, run the magic checksetup.pl script. (Many thanks to Holger
+ Schurig <holgerschurig@nikocity.de> for writing this script!) It will
+ make sure Bugzilla files and directories have reasonable permissions,
+ set up the data directory, and create all the MySQL tables.
+
+ bash# ./checksetup.pl
+
+ The first time you run it, it will create a file called localconfig.
_________________________________________________________________
-3.3. Product, Component, Milestone, and Version Administration
+3.2.15. Tweaking localconfig
+ This file contains a variety of settings you may need to tweak
+ including how Bugzilla should connect to the MySQL database.
+ The connection settings include:
- Dear Lord, we have to get our users to do WHAT?
- _________________________________________________________________
+ 1. server's host: just use "localhost" if the MySQL server is local
+ 2. database name: "bugs" if you're following these directions
+ 3. MySQL username: "bugs" if you're following these directions
+ 4. Password for the "bugs" MySQL account above
-3.3.1. Products
+ You should also install .htaccess files that the Apache webserver will
+ use to restrict access to Bugzilla data files. See .htaccess files and
+ security.
- Formerly, and in some spots still, called "Programs"
+ Once you are happy with the settings, re-run checksetup.pl. On this
+ second run, it will create the database and an administrator account
+ for which you will be prompted to provide information.
- Products are the broadest category in Bugzilla, and you should have
- the least of these. If your company makes computer games, you should
- have one product per game, and possibly a few special products
- (website, meetings...)
+ When logged into an administrator account once Bugzilla is running, if
+ you go to the query page (off of the Bugzilla main menu), you'll find
+ an "edit parameters" option that is filled with editable treats.
- A Product (formerly called "Program", and still referred to that way
- in some portions of the source code) controls some very important
- functions. The number of "votes" available for users to vote for the
- most important bugs is set per-product, as is the number of votes
- required to move a bug automatically from the UNCONFIRMED status to
- the NEW status. One can close a Product for further bug entry and
- define various Versions available from the Edit Product screen.
+ Should everything work, you will have a nearly empty Bugzilla database
+ and a newly-created localconfig file in your Bugzilla root directory.
- To create a new product:
+ Note
- 1. Select "components" from the yellow footer
+ The second time you run checksetup.pl, you should become the user your
+ web server runs as, and that you ensure that you set the
+ "webservergroup" parameter in localconfig to match the web server's
+ group name, if any. I believe, for the next release of Bugzilla, this
+ will be fixed so that Bugzilla supports a "webserveruser" parameter in
+ localconfig as well.
- Tip: It may seem counterintuitive to click "components" when you
- want to edit the properties associated with Products. This is one
- of a long list of things we want in Bugzilla 3.0...
- 2. Select the "Add" link to the right of "Add a new product".
- 3. Enter the name of the product and a description. The Description
- field is free-form.
+ Example 3-2. Running checksetup.pl as the web user
- Tip: Don't worry about the "Closed for bug entry", "Maximum Votes
- per person", "Maximum votes a person can put on a single bug",
- "Number of votes a bug in this Product needs to automatically get
- out of the UNCOMFIRMED state", and "Version" options yet. We'll
- cover those in a few moments.
+ Assuming your web server runs as user "apache", and Bugzilla is
+ installed in "/usr/local/bugzilla", here's one way to run
+ checksetup.pl as the web server user. As root, for the second run of
+ checksetup.pl, do this:
+
+bash# chown -R apache:apache /usr/local/bugzilla
+bash# su - apache
+bash# cd /usr/local/bugzilla
+bash# ./checksetup.pl
+
+ Note
+
+ The checksetup.pl script is designed so that you can run it at any
+ time without causing harm. You should run it after any upgrade to
+ Bugzilla.
_________________________________________________________________
-3.3.2. Components
+3.2.16. Setting Up Maintainers Manually (Optional)
- Components are subsections of a Product.
+ If you want to add someone else to every group by hand, you can do it
+ by typing the appropriate MySQL commands. Run mysql -u root -p bugs
+ You may need different parameters, depending on your security
+ settings. Then:
- Example 3-1. Creating some Components
+ mysql> update profiles set groupset=0x7fffffffffffffff where
+ login_name = 'XXX'; (yes, that's fifteen"f"'s.
- The computer game you are designing may 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.
+ replacing XXX with the Bugzilla email address.
+ _________________________________________________________________
- 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; the Owner and Q/A
- Contact fields in a bug are otherwise unrelated to the Component.
+3.2.17. The Whining Cron (Optional)
- To create a new Component:
+ 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. This can be done by adding
+ the following command as a daily crontab entry (for help on that see
+ that crontab man page):
- 1. Select the "Edit components" link from the "Edit Product" page
- 2. Select the "Add" link to the right of the "Add a new component"
- text on the "Select Component" page.
- 3. Fill out the "Component" field, a short "Description", and the
- "Initial Owner". The "Component" field should not contain a space.
- The "Description" field is free-form. The "Initial Owner" field
- must be that of a valid user already existing in the database. If
- the initial owner does not exist, Bugzilla will refuse to create
- the component.
-
- Tip: Is your "Default Owner" a user who is not yet in the database?
- No problem.
- a. Select the "Log out" link on the footer of the page.
- b. Select the "New Account" link on the footer of the "Relogin"
- page
- c. Type in the email address of the default owner you want to
- create in the "E-mail address" field, and her full name in
- the "Real name" field, then select the "Submit Query" button.
- d. Now select "Log in" again, type in your login information,
- and you can modify the product to use the Default Owner
- information you require.
+ cd <your-bugzilla-directory> ; ./whineatnews.pl
- 4. Either "edit" more components or return to the "query" page on the
- ensuing "Addming new component" page. To return to the Product you
- were editing, you must select the "components" link as before.
+ Tip
+
+ 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
_________________________________________________________________
-3.3.3. Versions
+3.2.18. Bug Graphs (Optional)
- Versions are the revisions of the product, such as "Flinders 3.1",
- "Flinders 95", and "Flinders 2000". Using Versions helps you isolate
- code changes and are an aid in reporting.
+ As long as you installed the GD and Graph::Base Perl modules you might
+ as well turn on the nifty bugzilla bug reporting graphs.
- Example 3-2. Common Use of Versions
+ Add a cron entry like this to run collectstats daily at 5 after
+ midnight:
- A user reports a bug against Version "Beta 2.0" of your product. The
- current Version of your software is "Release Candidate 1", and no
- longer has the bug. This will help you triage and classify bugs
- according to their relevance. It is also possible people may report
- bugs against bleeding-edge beta versions that are not evident in older
- versions of the software. This can help isolate code changes that
- caused the bug
+ bash# crontab -e
+ 5 0 * * * cd <your-bugzilla-directory> ; ./collectstats.pl
- Example 3-3. A Different Use of Versions
+ After two days have passed you'll be able to view bug graphs from the
+ Bug Reports page.
+ _________________________________________________________________
- This field has been used to good effect by an online service provider
- in a slightly different way. They had three versions of the product:
- "Production", "QA", and "Dev". Although it may be the same product, a
- bug in the development environment is not normally as critical as a
- Production bug, nor does it need to be reported publicly. When used in
- conjunction with Target Milestones, one can easily specify the
- environment where a bug can be reproduced, and the Milestone by which
- it will be fixed.
+3.2.19. Securing MySQL
- To create and edit Versions:
+ 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.
- 1. From the "Edit Product" screen, select "Edit Versions"
- 2. You will notice that the product already has the default version
- "undefined". If your product doesn't use version numbers, you may
- want to leave this as it is or edit it so that it is "---". You
- can then go back to the edit versions page and add new versions to
- your product.
- Otherwise, click the "Add" button to the right of the "Add a new
- version" text.
- 3. Enter the name of the Version. This can be free-form characters up
- to the limit of the text box. Then select the "Add" button.
- 4. At this point you can select "Edit" to edit more Versions, or
- return to the "Query" page, from which you can navigate back to
- the product through the "components" link at the foot of the Query
- page.
- _________________________________________________________________
+ Most MySQL installs have "interesting" default security parameters:
-3.3.4. Milestones
+ 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"
- 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. Or, you have a bug that you
- plan to fix for 2.8, this would have a milestone of 2.8.
+ 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.
- Note: Milestone options will only appear for a Product if you
- turned the "usetargetmilestone" field in the "Edit Parameters"
- screen "On".
+ To see your permissions do:
- To create new Milestones, set Default Milestones, and set Milestone
- URL:
+ bash# mysql -u root -p
+ mysql> use mysql;
+ mysql> show tables;
+ mysql> select * from user;
+ mysql> select * from db;
- 1. Select "edit milestones"
- 2. Select "Add" to the right of the "Add a new milestone" 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. Select "Add".
- Example 3-4. Using SortKey with Target Milestone
- Let's say you create a target milestone called "Release 1.0", with
- Sortkey set to "0". Later, you realize that you will have a public
- beta, called "Beta1". You can create a Milestone called "Beta1",
- with a Sortkey of "-1" in order to ensure people will see the
- Target Milestone of "Beta1" earlier on the list than "Release 1.0"
- 4. If you want to add more milestones, select the "Edit" link. If you
- don't, well shoot, you have to go back to the "query" page and
- select "components" again, and make your way back to the Product
- you were editing.
+ To fix the gaping holes:
- Note: This is another in the list of unusual user interface
- decisions that we'd like to get cleaned up. Shouldn't there be a
- link to the effect of "edit the Product I was editing when I ended
- up here"? In any case, clicking "components" in the footer takes
- you back to the "Select product" screen, from which you can begin
- editing your product again.
- 5. From the Edit Product screen again (once you've made your way
- back), enter the URL for a description of what your milestones are
- for this product in the "Milestone URL" field. It should be of the
- format "http://www.foo.com/bugzilla/product_milestones.html"
- Some common uses of this field include product descriptions,
- product roadmaps, and of course a simple description of the
- meaning of each milestone.
- 6. If you're using Target Milestones, the "Default Milestone" field
- must have some kind of entry. If you really don't care if people
- set coherent Target Milestones, simply leave this at the default,
- "---". However, controlling and regularly updating the Default
- Milestone field is a powerful tool when reporting the status of
- projects.
- Select the "Update" button when you are done.
- 7.
- _________________________________________________________________
+ DELETE FROM user WHERE User='';
+ UPDATE user SET Password=PASSWORD('new_password') WHERE user='root';
+ FLUSH PRIVILEGES;
-3.3.5. Voting
+ If you're not running "mit-pthreads" you can use:
- The concept of "voting" is a poorly understood, yet powerful feature
- for the management of open-source projects. Each user is assigned so
- many Votes per product, which they can freely reassign (or assign
- multiple votes to a single bug). 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.
+ GRANT USAGE ON *.* TO bugs@localhost;
+ GRANT ALL ON bugs.* TO bugs@localhost;
+ REVOKE DROP ON bugs.* FROM bugs@localhost;
+ FLUSH PRIVILEGES;
- The daunting challenge of Votes is deciding where you draw the line
- for a "vocal majority". If you only have a user base of 100 users,
- setting a low threshold for bugs to move from UNCONFIRMED to NEW makes
- sense. As the Bugzilla user base expands, however, these thresholds
- must be re-evaluated. You should gauge whether this feature is worth
- the time and close monitoring involved, and perhaps forego
- implementation until you have a critical mass of users who demand it.
+ 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:
- To modify Voting settings:
+ 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;
- 1. Navigate to the "Edit Product" screen for the Product you wish to
- modify
- 2. Set "Maximum Votes per person" to your calculated value. Setting
- this field to "0" disables voting.
- 3. Set "Maximum Votes a person can put on a single bug" to your
- calculated value. It should probably be some number lower than the
- "Maximum votes per person". Setting this field to "0" disables
- voting, but leaves the voting options open to the user. This is
- confusing.
- 4. Set "Number of votes a bug in this product needs to automatically
- get out of the UNCONFIRMED state" to your calculated number.
- Setting this field to "0" disables the automatic move of bugs from
- UNCONFIRMED to NEW. Some people advocate leaving this at "0", but
- of what use are Votes if your Bugzilla user base is unable to
- affect which bugs appear on Development radar?
+ Use .htaccess files with the Apache webserver to secure your bugzilla
+ install. See .htaccess files and security
- Tip: You should probably set this number to higher than a small
- coalition of Bugzilla users can influence it. Most sites use this
- as a "referendum" mechanism -- if users are able to vote a bug out
- of UNCONFIRMED, it is a really bad bug!
- 5. Once you have adjusted the values to your preference, select the
- "Update" button.
+ Consider also:
+
+ 1. Turning off external networking with "--skip-networking", unless
+ you have "mit-pthreads", in which case you can't. Without
+ networking, MySQL connects with a Unix domain socket.
+ 2. using the --user= option to mysqld to run it as an unprivileged
+ user.
+ 3. starting MySQL in a chroot jail
+ 4. running the httpd in a "chrooted" jail
+ 5. making sure the MySQL passwords are different from the OS
+ passwords (MySQL "root" has nothing to do with system "root").
+ 6. running MySQL on a separate untrusted machine
+ 7. making backups ;-)
_________________________________________________________________
-3.3.6. Groups and Group Security
+3.3. Mac OS X Installation Notes
- Groups can be very useful in bugzilla, because they allow users to
- isolate bugs or products that should only be seen by certain people.
- Groups can also be a complicated minefield of interdependencies and
- weirdness if mismanaged.
+ 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.
- Example 3-5. When to Use Group Security
+ 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/>.
- Many Bugzilla sites isolate "Security-related" bugs from all other
- bugs. This way, they can have a fix ready before the security
- vulnerability is announced to the world. You can create a "Security"
- product which, by default, has no members, and only add members to the
- group (in their individual User page, as described under User
- Administration) who should have priveleged access to "Security" bugs.
- Alternately, you may create a Group independently of any Product, and
- change the Group mask on individual bugs to restrict access to members
- only of certain Groups.
+ Follow the instructions for setting up Fink. Once it's installed,
+ you'll want to run the following as root: fink install gd
- Groups only work if you enable the "usebuggroups" paramater. In
- addition, if the "usebuggroupsentry" parameter is "On", one can
- restrict access to products by groups, so that only members of a
- product group are able to view bugs within that product. Group
- security in Bugzilla can be divided into two categories: Generic and
- Product-Based.
+ It will prompt you for a number of dependencies, type 'y' and hit
+ enter to install all of the dependencies. Then watch it work.
- Note: Groups in Bugzilla are a complicated beast that evolved out
- of very simple user permission bitmasks, apparently itself derived
- from common concepts in UNIX access controls. A "bitmask" is a
- fixed-length number whose value can describe one, and only one, set
- of states. For instance, UNIX file permissions are assigned bitmask
- values: "execute" has a value of 1, "write" has a value of 2, and
- "read" has a value of 4. Add them together, and a file can be read,
- written to, and executed if it has a bitmask of "7". (This is a
- simplified example -- anybody who knows UNIX security knows there
- is much more to it than this. Please bear with me for the purpose
- of this note.) The only way a bitmask scheme can work is by
- doubling the bit count for each value. Thus if UNIX wanted to offer
- another file permission, the next would have to be a value of 8,
- then the next 16, the next 32, etc.
-
- Similarly, Bugzilla offers a bitmask to define group permissions,
- with an internal limit of 64. Several are already occupied by
- built-in permissions. The way around this limitation is to avoid
- assigning groups to products if you have many products, avoid
- bloating of group lists, and religiously prune irrelevant groups.
- In reality, most installations of Bugzilla support far fewer than
- 64 groups, so this limitation has not hit for most sites, but it is
- on the table to be revised for Bugzilla 3.0 because it interferes
- with the security schemes of some administrators.
+ 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 (it looks for the specific paths instead of getting them from
+ your environment). But there's a way around that :-)
- To enable Generic Group Security ("usebuggroups"):
+ 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 the following patch to the Makefile.PL file (save the
+ patch into a file and use the command patch < patchfile:
- 1. Turn "On" "usebuggroups" in the "Edit Parameters" screen.
- 2. You will generally have no groups set up. Select the "groups" link
- in the footer.
- 3. Take a moment to understand the instructions on the "Edit Groups"
- screen. Once you feel confident you understand what is expected of
- you, select the "Add Group" link.
- 4. Fill out the "New Name" (remember, no spaces!), "New Description",
- and "New User RegExp" fields. "New User RegExp" allows you to
- automatically place all users who fulfill the Regular Expression
- into the new group.
- Example 3-6. Creating a New Group
- I created a group called "DefaultGroup" with a description of
- "This is simply a group to play with", and a "New User RegExp" of
- "*@velio.com". This new group automatically includes all Bugzilla
- users with "@velio.com" at the end of their user id. When I
- finished, my new group was assigned bit #128.
- When you have finished, select the "Add" button.
- To enable Product-Based Group Security ("usebuggroupsentry"):
+--- GD-1.33/Makefile.PL Fri Aug 4 16:59:22 2000
++++ GD-1.33-darwin/Makefile.PL Tue Jun 26 01:29:32 2001
+@@ -3,8 +3,8 @@
+ warn "NOTICE: This module requires libgd 1.8.3 or higher (shared library versi
+on 4.X).\n";
- Warning
+ # =====> PATHS: CHECK AND ADJUST <=====
+-my @INC = qw(-I/usr/local/include -I/usr/local/include/gd);
+-my @LIBPATH = qw(-L/usr/lib/X11 -L/usr/X11R6/lib -L/usr/X11/lib -L/usr/local/l
+ib );
++my @INC = qw(-I/sw/include -I/sw/include/gd -I/usr/local/include -I/usr/lo
+cal/include/gd);
++my @LIBPATH = qw(-L/usr/lib/X11 -L/usr/X11R6/lib -L/usr/X11/lib -L/sw/lib -L/u
+sr/local/lib);
+ my @LIBS = qw(-lgd -lpng -lz);
- Don't forget that you only have 64 groups masks available, total, for
- your installation of Bugzilla! If you plan on having more than 50
- products in your individual Bugzilla installation, and require group
- security for your products, you should consider either running
- multiple Bugzillas or using Generic Group Security instead of
- Product-Based ("usebuggroupsentry") Group Security.
+ # FEATURE FLAGS
+@@ -23,7 +23,7 @@
- 1. Turn "On" "usebuggroups" and "usebuggroupsentry" in the "Edit
- Parameters" screen.
+ push @LIBS,'-lttf' if $TTF;
+ push @LIBS,'-ljpeg' if $JPEG;
+-push @LIBS, '-lm' unless $^O eq 'MSWin32';
++push @LIBS, '-lm' unless ($^O =~ /^MSWin32|darwin$/);
- Warning
- "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, Products, etc. with the administrative
- account.
- 2. You will generally have no Groups set up, unless you enabled
- "usebuggroupsentry" prior to creating any Products. To create
- "Generic Group Security" groups, follow the instructions given
- above. To create Product-Based Group security, simply follow the
- instructions for creating a new Product. If you need to add users
- to these new groups as you create them, you will find the option
- to add them to the group available under the "Edit User" screens.
+ # FreeBSD 3.3 with libgd built from ports croaks if -lXpm is specified
+ if ($^O ne 'freebsd' && $^O ne 'MSWin32') {
+
+
+
+ Then, run these commands to finish the installation of the perl
+ module:
+
+ perl Makefile.PL
+ make
+ make test
+ make install
+ And don't forget to run exit to get back to cpan.
+
+ Happy Hacking!
_________________________________________________________________
-3.4. Bugzilla Security
+3.4. BSD Installation Notes
+ For instructions on how to set up Bugzilla on FreeBSD, NetBSD,
+ OpenBSD, BSDi, etc. please consult Section 3.3.
+ _________________________________________________________________
+3.5. Installation General Notes
- Putting your money in a wall safe is better protection than depending
- on the fact that no one knows that you hide your money in a mayonnaise
- jar in your fridge.
+3.5.1. Modifying Your Running System
- Note: Poorly-configured MySQL, Bugzilla, and FTP installations have
- given attackers full access to systems in the past. Please take
- these guidelines seriously, even for Bugzilla machines hidden away
- behind your firewall. 80% of all computer trespassers are insiders,
- not anonymous crackers.
+ Bugzilla optimizes database lookups by storing all relatively static
+ information in the versioncache file, located in the data/
+ subdirectory under your installation directory.
- First thing's first: Secure your installation.
+ If you make a change to the structural data in your database (the
+ versions table for example), or to the "constants" encoded in
+ defparams.pl, you will need to remove the cached content from the data
+ directory (by doing a "rm data/versioncache"), or your changes won't
+ show up.
- 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
+ That file gets automatically regenerated whenever it's more than an
+ hour old, so Bugzilla will eventually notice your changes by itself,
+ but generally you want it to notice right away, so that you can test
+ things.
+ _________________________________________________________________
- 1. Ensure you are running at least MysQL version 3.22.32 or newer.
- Earlier versions had notable security holes and poorly secured
- default configuration choices.
- 2. There is no substitute for understanding the tools on your system!
- Read The MySQL Privelege System until you can recite it from
- memory!
- At the very least, ensure you password the "mysql -u root" account
- and the "bugs" account, establish grant table rights (consult the
- Keystone guide in Appendix C: The Bugzilla Database for some
- easy-to-use details) that do not allow CREATE, DROP, RELOAD,
- SHUTDOWN, and PROCESS for user "bugs". I wrote up the Keystone
- advice back when I knew far less about security than I do now : )
- 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.
- 5. Ensure you have adequate access controls for the
- $BUGZILLA_HOME/data/ and $BUGZILLA_HOME/shadow/ directories, as
- well as the $BUGZILLA_HOME/localconfig file. The localconfig file
- stores your "bugs" user password, which would be terrible to have
- in the hands of a criminal. Also some files under
- $BUGZILLA_HOME/data/ store sensitive information, and
- $BUGZILLA_HOME/shadow/ stores bug information for faster
- retrieval. If you fail to secure these directories and this file,
- you will expose bug information to those who may not be allowed to
- see it.
- On Apache, you can use .htaccess files to protect access to these
- directories, as outlined in Bug 57161 for the localconfig file,
- and Bug 65572 for adequate protection in your data/ and shadow/
- directories.
- 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
+3.5.2. Upgrading From Previous Versions
- 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
+ The developers of Bugzilla are constantly adding new tables, columns
+ and fields. You'll get SQL errors if you just update the code. The
+ strategy to update is to simply always run the checksetup.pl script
+ whenever you upgrade your installation of Bugzilla. If you want to see
+ what has changed, you can read the comments in that file, starting
+ from the end.
- Place the following text into a file named ".htaccess", readable
- by your web server, in your $BUGZILLA_HOME/shadow directory.
- deny from all
+ 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.
_________________________________________________________________
-Chapter 4. Using Bugzilla
+3.5.3. .htaccess files and security
+
+ To enhance the security of your Bugzilla installation, Bugzilla will
+ generate .htaccess files which the Apache webserver can use to
+ restrict access to the bugzilla data files. The checksetup script will
+ generate the .htaccess files.
+ Note
+ If you are using an alternate provider of webdot services for graphing
+ (as described when viewing editparams.cgi in your web browser), you
+ will need to change the ip address in data/webdot/.htaccess to the ip
+ address of the webdot server that you are using.
- What, Why, How, & What's in it for me?
+ If you are using Internet Information Server or other 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.1. What is Bugzilla?
+3.5.4. 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.
+ _________________________________________________________________
- Bugzilla is one example of a class of programs called "Defect Tracking
- Systems", or, more commonly, "Bug-Tracking Systems". Defect Tracking
- Systems allow individual or groups of developers to keep track of
- outstanding bugs in their product effectively. Bugzilla was originally
- written by Terry Weissman in a programming language called "TCL", to
- replace a crappy bug-tracking database used internally for Netscape
- Communications. Terry later ported Bugzilla to Perl from TCL, and in
- Perl it remains to this day. Most commercial defect-tracking software
- vendors at the time charged enormous licensing fees, and Bugzilla
- quickly became a favorite of the open-source crowd (with its genesis
- in the open-source browser project, Mozilla). It is now the de-facto
- standard defect-tracking system against which all others are measured.
+3.5.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.
+
+bash# cd $BUGZILLA_HOME; for i in `ls *.cgi`; \
+ do cat $i | sed 's/Content-type\: text\/html/Content-Type: text\/html
+\; charset=ISO-8859-1/' >$i.tmp; \
+ mv $i.tmp $i; done
+
+ 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".
+ _________________________________________________________________
- Bugzilla has matured immensely, and now boasts many advanced features.
- These include:
+3.5.6. UNIX Installation Instructions History
- * integrated, product-based granular security schema
- * inter-bug dependencies and dependency graphing
- * advanced reporting capabilities
- * a robust, stable RDBMS back-end
- * extensive configurability
- * a very well-understood and well-thought-out natural bug resolution
- protocol
- * email, XML, and HTTP APIs
- * available integration with automated software configuration
- management systems, including Perforce and CVS.
- * too many more features to list
+ This document was originally adapted from the Bonsai installation
+ instructions by Terry Weissman <terry@mozilla.org>.
- Despite its current robustness and popularity, however, Bugzilla faces
- some near-term challenges, such as reliance on a single database, a
- lack of abstraction of the user interface and program logic, verbose
- email bug notifications, a powerful but daunting query interface,
- little reporting configurability, problems with extremely large
- queries, some unsupportable bug resolution options, no
- internationalization, and dependence on some nonstandard libraries.
+ The February 25, 1999 re-write of this page was done by Ry4an Brase
+ <ry4an@ry4an.org>, with some edits by Terry Weissman, Bryce Nesbitt,
+ Martin Pool, & Dan Mosedale (But don't send bug reports to them;
+ report them using bugzilla, at
+ http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla ).
- Some recent headway has been made on the query front, however. If you
- are using the latest version of Bugzilla, you should see a "simple
- search" form on the default front page of your Bugzilla install. Type
- in two or three search terms and you should pull up some relevant
- information. This is also available as "queryhelp.cgi".
+ This document was heavily modified again Wednesday, March 07 2001 to
+ reflect changes for Bugzilla 2.12 release by Matthew P. Barnson. The
+ securing MySQL section should be changed to become standard procedure
+ for Bugzilla installations.
- Despite these small problems, Bugzilla is very hard to beat. It is
- under very active development to address the current issues, and a
- long-awaited overhaul in the form of Bugzilla 3.0 is expected sometime
- later this year.
- _________________________________________________________________
+ Finally, the README in its entirety was marked up in SGML and included
+ into the Guide on April 24, 2001 by Matt Barnson. Since that time,
+ it's undergone extensive modification as Bugzilla grew.
-4.2. Why Should We Use Bugzilla?
+ Comments from people using this Guide for the first time are
+ particularly welcome.
+ _________________________________________________________________
+3.6. Win32 Installation Notes
+
+ This section covers installation on Microsoft Windows 95, 98, ME, NT,
+ and 2000. Bugzilla works fine on Win32 platforms, but please remember
+ that the Bugzilla team and the author of the Guide neither endorse nor
+ support installation on Microsoft Windows. Bugzilla installs and runs
+ best and easiest on UNIX-like operating systems, and that is the way
+ it will stay for the foreseeable future. The Bugzilla team is
+ considering supporting Win32 for the 2.16 release and later.
+
+ 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.
+ _________________________________________________________________
+3.6.1. Win32 Installation: Step-by-step
- No, Who's on first...
+ Note
- 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
+ You should be familiar with, and cross-reference, the rest of the
+ Bugzilla Installation section while performing your Win32
+ installation.
- 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.
+ Making Bugzilla work on Microsoft Windows is no picnic. Support for
+ Win32 has improved dramatically in the last few releases, but, if you
+ choose to proceed, you should be a very skilled Windows Systems
+ Administrator with strong troubleshooting abilities, a high tolerance
+ for pain, and moderate perl skills. Bugzilla on NT requires hacking
+ source code and implementing some advanced utilities. What follows is
+ the recommended installation procedure for Win32; additional
+ suggestions are provided in Appendix A.
+ 1. Install Apache Web Server for Windows, and copy the Bugzilla files
+ somewhere Apache can serve them. Please follow all the
+ instructions referenced in Bugzilla Installation regarding your
+ Apache configuration, particularly instructions regarding the
+ "AddHandler" parameter and "ExecCGI".
+
+ Note
+
+ You may also use Internet Information Server or Personal Web Server
+ for this purpose. However, setup is quite different. If ActivePerl
+ doesn't seem to handle your file associations correctly (for .cgi and
+ .pl files), please consult Appendix A.
+ If you are going to use IIS, if on Windows NT you must be updated to
+ at least Service Pack 4. Windows 2000 ships with a sufficient version
+ of IIS.
+ 2. Install ActivePerl for Windows. Check
+ http://aspn.activestate.com/ASPN/Downloads/ActivePerl for a
+ current compiled binary.
+ Please also check the following links to fully understand the
+ status of ActivePerl on Win32: Perl Porting, and Perl on Win32 FAQ
+ 3. Use ppm from your perl\bin directory to install the following
+ packs: DBI, DBD-Mysql, TimeDate, Chart, Date-Calc, Date-Manip, and
+ GD. You may need to extract them from .zip format using Winzip or
+ other unzip program first. These additional ppm modules can be
+ downloaded from ActiveState.
- But why should you use Bugzilla?
+ Note
- 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, Loki software, Linux-Mandrake, and VA
- Systems. Combined with systems such as CVS, Bonsai, or Perforce SCM,
- Bugzilla provides a powerful, easy-to-use solution to configuration
- management and replication problems
+ You can find a list of modules at
+ http://www.activestate.com/PPMPackages/zips/5xx-builds-only/
+ The syntax for ppm is: C:> ppm <modulename>
+ Example 3-3. Installing ActivePerl ppd Modules on Microsoft
+ Windows
+ C:>ppm DBD-Mysql
+ Watch your capitalization!
+ You can find ActiveState ppm modules at
+ http://www.activestate.com/PPMPackages/5.6plus
+ 4. Install MySQL for NT.
- 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 by using Bugzilla's e-mail
- integration features be able to follow the discussion trail that led
- to critical decisions.
+ Note
- 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.
- _________________________________________________________________
+ You can download MySQL for Windows NT from MySQL.com. Some find it
+ helpful to use the WinMySqlAdmin utility, included with the download,
+ to set up the database.
+ 5. Setup MySQL
+ a. C:> C:\mysql\bin\mysql -u root mysql
+ b. mysql> DELETE FROM user WHERE Host='localhost' AND User='';
+ c. mysql> UPDATE user SET Password=PASSWORD ('new_password')
+ WHERE user='root';
+ "new_password", above, indicates whatever password you wish
+ to use for your "root" user.
+ d. mysql> GRANT SELECT, INSERT, UPDATE, DELETE, INDEX, ALTER,
+ CREATE, DROP, REFERENCES ON bugs.* to bugs@localhost
+ IDENTIFIED BY 'bugs_password';
+ "bugs_password", above, indicates whatever password you wish
+ to use for your "bugs" user.
+ e. mysql> FLUSH PRIVILEGES;
+ f. mysql> create database bugs;
+ g. mysql> exit;
+ h. C:> C:\mysql\bin\mysqladmin -u root -p reload
+ 6. Edit checksetup.pl in your Bugzilla directory. Change this line:
-4.3. How do I use Bugzilla?
+my $webservergid = getgrnam($my_webservergroup);
+ to
- Hey! I'm Woody! Howdy, Howdy, Howdy!
+my $webservergid = $my_webservergroup;
- Bugzilla is a large, complex system. Describing how to use it requires
- some time. If you are only interested in installing or administering a
- Bugzilla installation, please consult the Installing and Administering
- Bugzilla portions of this Guide. This section is principally aimed
- towards developing end-user mastery of Bugzilla, so you may fully
- enjoy the benefits afforded by using this reliable open-source
- bug-tracking software.
- Throughout this portion of the Guide, we will refer to user account
- options available at the Bugzilla test installation,
- landfill.tequilarista.org.
+ or the name of the group you wish to own the files explicitly:
- Note: Some people have run into difficulties completing this
- tutorial. If you run into problems, please check the updated,
- online documentation available at
- http://www.trilobyte.net/barnsons. If you're still stumped, please
- subscribe to the newsgroup and provide details of exactly what's
- stumping you! If enough people complain, I'll have to fix it in the
- next version of this Guide. You can subscribe to the newsgroup at
- news://news.mozilla.org/netscape.public.mozilla.webtools
+my $webservergid = 'Administrators'
- Although Landfill serves as a great introduction to Bugzilla, it does
- not offer all the options you would have as a user on your own
- installation of Bugzilla, nor can it do more than serve as a general
- introduction to Bugzilla. Additionally, Landfill often runs
- cutting-edge versions of Bugzilla for testing, so some things may work
- slightly differently than mentioned here.
- _________________________________________________________________
-4.3.1. Create a Bugzilla Account
+ 7. Run checksetup.pl from the Bugzilla directory.
+ 8. Edit localconfig to suit your requirements. Set $db_pass to your
+ "bugs_password" from step 5.d, and $webservergroup to "8".
+
+ Note
+
+ Not sure on the "8" for $webservergroup above. If it's wrong, please
+ send corrections.
+ 9. Edit defparams.pl to suit your requirements. Particularly, set
+ DefParam("maintainer") and DefParam("urlbase") to match your
+ install.
+
+ Note
+
+ This is yet another step I'm not sure of, since the maintainer of this
+ documentation does not maintain Bugzilla on NT. If you can confirm or
+ deny that this step is required, please let me know.
+ 10.
+
+ Note
+
+ There are several alternatives to Sendmail that will work on Win32.
+ The one mentioned here is a suggestion, not a requirement. Some other
+ mail packages that can work include BLAT, Windmail, Mercury Sendmail,
+ and the CPAN Net::SMTP Perl module (available in .ppm). Every option
+ requires some hacking of the Perl scripts for Bugzilla to make it
+ work. The option here simply requires the least.
+ 1. Download NTsendmail, available from www.ntsendmail.com. You
+ must have a "real" mail server which allows you to relay off
+ it in your $ENV{"NTsendmail"} (which you should probably
+ place in globals.pl)
+ 2. Put ntsendmail.pm into your .\perl\lib directory.
+ 3. Add to globals.pl:
+
+# these settings configure the NTsendmail process
+use NTsendmail;
+$ENV{"NTsendmail"}="your.smtpserver.box";
+$ENV{"NTsendmail_debug"}=1;
+$ENV{"NTsendmail_max_tries"}=5;
+
+
+ Note
+
+ Some mention to also edit $db_pass in globals.pl to be your
+ "bugs_password". Although this may get you around some problem
+ authenticating to your database, since globals.pl is not normally
+ restricted by .htaccess, your database password is exposed to whoever
+ uses your web server.
+ 4. Find and comment out all occurences of "open(SENDMAIL" in
+ your Bugzilla directory. Then replace them with:
+
+# new sendmail functionality
+my $mail=new NTsendmail;
+my $from="bugzilla\@your.machine.name.tld";
+my $to=$login;
+my $subject=$urlbase;
+$mail->send($from,$to,$subject,$msg);
+
+ Note
+
+ 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";
- First thing's first! 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 the end-user Bugzilla experience, use this URL:
- http://landfill.tequilarista.org/mozilla/bugzilla/
- 1. Click the "Open a new Bugzilla account" link.
- 2. Enter your "E-mail address" and "Real Name" (or whatever name you
- want to call yourself) in the spaces provided, then select the
- "Create Account" button.
- 3. Within 5-10 minutes, you should receive an email to the address
- you provided above, which contains your login name (generally the
- same as the email address), and a password you can use to access
- your account. This password is randomly generated, and should be
- changed at your nearest opportunity (we'll go into how to do it
- later).
- 4. Click the "Log In" link in the yellow area at the bottom of the
- page in your browser, then enter your "E-mail address" and
- "Password" you just received into the spaces provided, and select
- "Login".
+ or something to that effect.
+ 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
+ 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
+ processmail.pl to make this work.
+my $smtp = Net::SMTP->new('<Name of your SMTP server>'); #connect to SMTP ser
+ver
+$smtp->mail('<your name>@<you smpt server>');# use the sender's adress here
+$smtp->to($tolist); # recipient's address
+$smtp->data(); # Start the mail
+$smtp->datasend($msg);
+$smtp->dataend(); # Finish sending the mail
+$smtp->quit; # Close the SMTP connection
+$logstr = "$logstr; mail sent to $tolist $cclist";
+}
+
+ here is a test mail program for Net::SMTP:
+use Net::SMTP;
+ my $smtp = Net::SMTP->new('<Name of your SMTP server', Timeout => 30, Debug
+=> 1, ); # connect to SMTP server
+ $smtp->auth;
+ $smtp->mail('you@yourcompany.com');# use the sender's adress
+here
+ $smtp->to('someotherAddress@someotherdomain.com'); #
+recipient's address
+ $smtp->data(); # Start the mail
+ $smtp->datasend('test');
+ $smtp->dataend(); # Finish sending the mail
+ $smtp->quit; # Close the SMTP connection
+exit;
+
+ 12.
+
+ Note
+
+ This step is optional if you are using IIS or another web server which
+ only decides on an interpreter based upon the file extension (.pl),
+ rather than the "shebang" line (#/usr/bonsaitools/bin/perl)
+ Modify the path to perl on the first line (#!) of all files to
+ point to your Perl installation, and add "perl" to the beginning
+ of all Perl system calls that use a perl script as an argument.
+ This may take you a while. There is a "setperl.csh" utility to
+ speed part of this procedure, available in the Useful Patches and
+ Utilities for Bugzilla section of The Bugzilla Guide. However, it
+ requires the Cygwin GNU-compatible environment for Win32 be set up
+ in order to work. See http://www.cygwin.com/ for details on
+ obtaining Cygwin.
+ 13. Modify the invocation of all system() calls in all perl scripts in
+ your Bugzilla directory. For instance, change this line in
+ processmail:
- Note: If you ever forget your password, you can come back to this
- page, enter your "E-mail address", then select the "E-mail me a
- password" button to have your password mailed to you again so that
- you can login.
- Caution
- Many modern browsers include an "Auto-Complete" or "Form Fill" feature
- to remember the user names and passwords you type in at many sites.
- Unfortunately, sometimes they attempt to "guess" what you will put in
- as your password, and guess wrong. If you notice a text box is already
- filled out, please overwrite the contents of the text box so you can
- be sure to input the correct information.
+system ("./processmail.pl",@ARGLIST);
- Congratulations! If you followed these directions, you now are the
- proud owner of a user account on landfill.tequilarista.org (Landfill)
- or your local Bugzilla install. You should now see in your browser a
- page called the "Bugzilla Query Page". It may look daunting, but with
- this Guide to walk you through it, you will master it in no time.
- _________________________________________________________________
-4.3.2. The Bugzilla Query Page
+ to
- The Bugzilla Query Page is the heart and soul of Bugzilla. It is the
- master interface where you can find any bug report, comment, or patch
- currently in the Bugzilla system. We'll go into how to create your own
- bug report later on.
- There are efforts underway to simplify query usage. If you have a
- local installation of Bugzilla 2.12 or higher, you should have
- "quicksearch.html" available to use and simplify your searches. There
- is also, or shortly will be, a helper for the query interface, called
- "queryhelp.cgi". Landfill tends to run the latest code, so these two
- utilities should be available there for your perusal.
+system ("perl processmail.pl",@ARGLIST);
- At this point, please visit the main Bugzilla site,
- bugzilla.mozilla.org, to see a more fleshed-out query page.
- The first thing you need to notice about the Bugzilla Query Page is
- that nearly every box you see on your screen has a hyperlink nearby,
- explaining what it is or what it does. Near the upper-left-hand corner
- of your browser window you should see the word "Status" underlined.
- Select it.
+ 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
+ require 'CGI.pl'; line.
- Notice the page that popped up? Every underlined word you see on your
- screen is a hyperlink that will take you to context-sensitive help.
- Click around for a while, and learn what everything here does. To
- return to the query interface after pulling up a help page, use the
- "Back" button in your browser.
+binmode(STDIN);
+binmode(STDOUT);
- I'm sure that after checking out the online help, you are now an
- Expert on the Bugzilla Query Page. If, however, you feel you haven't
- mastered it yet, let me walk you through making a few successful
- queries to find out what there are in the Bugzilla bug-tracking system
- itself.
+ Note
- 1. Ensure you are back on the "Bugzilla Query Page" Do nothing in the
- boxes marked "Status", "Resolution", "Platform", "OpSys",
- "Priority", or "Severity". The default query for "Status" is to
- find all bugs that are NEW, ASSIGNED, or REOPENED, which is what
- we want. If you don't select anything in the other 5 scrollboxes
- there, then you are saying that "any of these are OK"; we're not
- locking ourselves into only finding bugs on the "DEC" Platform, or
- "Windows 95" OpSys (Operating System). You're smart, I think you
- have it figured out.
- Basically, selecting anything on the query page narrows your
- search down. Leaving stuff unselected, or text boxes unfilled,
- broadens your search!
- 2. You see the box immediately below the top six boxes that contains
- an "Email" text box, with the words "matching as", a drop-down
- selection box, then some checkboxes with "Assigned To" checked by
- default? This allows you to filter your search down based upon
- email address. Let's put my email address in there, and see what
- happens.
- Type "barnboy@trilobyte.net" in the top Email text box.
- 3. Let's narrow the search some more. Scroll down until you find the
- box with the word "Program" over the top of it. This is where we
- can narrow our search down to only specific products (software
- programs or product lines) in our Bugzilla database. Please notice
- the box is a scrollbox. Using the down arrow on the scrollbox,
- scroll down until you can see an entry called "Webtools". Select
- this entry.
- 4. Did you notice that some of the boxes to the right changed when
- you selected "Webtools"? Every Program (or Product) has different
- Versions, Components, and Target Milestones associated with it. A
- "Version" is the number of a software program.
- Example 4-1. Some Famous Software Versions
- Do you remember the hype in 1995 when Microsoft Windows 95(r) was
- released? It may have been several years ago, but Microsoft(tm)
- spent over $300 Million advertising this new Version of their
- software. Three years later, they released Microsoft Windows
- 98(r), another new version, to great fanfare, and then in 2000
- quietly released Microsoft Windows ME(Millenium Edition)(r).
- Software "Versions" help a manufacturer differentiate their
- current product from their previous products. Most do not identify
- their products by the year they were released. Instead, the
- "original" version of their software will often be numbered "1.0",
- with small bug-fix releases on subsequent tenths of a digit. In
- most cases, it's not a decimal number; for instance, often 1.9 is
- an older version of the software than 1.11, but is a newer version
- than 1.1.1.
- In general, a "Version" in Bugzilla should refer to released
- products, not products that have not yet been released to the
- public. Forthcoming products are what the Target Milestone field
- is for.
- A "Component" is a piece of a Product. It may be a standalone
- program, or some other logical division of a Product or Program.
- Normally, a Component has a single Owner, who is responsible for
- overseeing efforts to improve that Component.
- Example 4-2. Mozilla Webtools Components
- Mozilla's "Webtools" Product is composed of several pieces
- (Components):
+ 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
+ aribtrarily putting binmode() at the begining of the attachment files,
+ there should be logic to determine if binmode() is needed or not.
- Bonsai, a tool to show recent changes to Mozilla
- Bugzilla, a defect-tracking tool
- Build, a tool to automatically compile source code into
- machine-readable form
- Despot, a program that controls access to the other Webtools
- LXR, a utility that automatically marks up text files to make them
- more readable
- MozBot, a "robot" that announces changes to Mozilla in Chat
- TestManager, a tool to help find bugs in Mozilla
- Tinderbox, which displays reports from Build
- A different person is responsible for each of these Components.
- Tara Hernandez keeps the "Bugzilla" component up-to-date.
- A "Milestone", or "Target Milestone" is a often a planned future
- "Version" of a product. In many cases, though, Milestones simply
- represent significant dates for a developer. Having certain
- features in your Product is frequently tied to revenue (money) the
- developer will receive if the features work by the time she
- reaches the Target Milestone. Target Milestones are a great tool
- to organize your time. If someone will pay you $100,000 for
- incorporating certain features by a certain date, those features
- by that Milestone date become a very high priority. Milestones
- tend to be highly malleable creatures, though, that appear to be
- in reach but are out of reach by the time the important day
- arrives.
- The Bugzilla Project has set up Milestones for future Bugzilla
- versions 2.14, 2.16, 2.18, 3.0, etc. However, a Target Milestone
- can just as easily be a specific date, code name, or weird
- alphanumeric combination, like "M19".
- 5. OK, now let's select the "Bugzilla" component from its scrollbox.
- 6. Skip down the page a bit -- do you see the "submit query" button?
- Select it, and let's run this query!
- 7. Congratulations! You've completed your first Query, and have
- before you the Bug List of the author of this Guide, Matthew P.
- Barnson (barnboy@trilobyte.net). If I'm doing well, you'll have a
- cryptic "Zarro Boogs Found" message on your screen. It is just a
- happy hacker's way of saying "Zero Bugs Found". However, I am
- fairly certain I will always have some bugs assigned to me that
- aren't done yet, so you won't often see that message!
+ Tip
- I encourage you to click the bug numbers in the left-hand column and
- examine my bugs. Also notice that if you click the underlined links
- near the top of this page, they do not take you to context-sensitive
- help here, but instead sort the columns of bugs on the screen! When
- you need to sort your bugs by priority, severity, or the people they
- are assigned to, this is a tremendous timesaver.
+ 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:
- A couple more interesting things about the Bug List page:
- Change Columns: by selecting this link, you can show all kinds of
- information in the Bug List
- Change several bugs at once: If you have sufficient rights to change
- all the bugs shown in the Bug List, you can mass-modify them. This is
- a big time-saver.
- Send mail to bug owners: If you have many related bugs, you can
- request an update from every person who owns the bugs in the Bug List
- asking them the status.
- Edit this query: If you didn't get exactly the results you were
- looking for, you can return to the Query page through this link and
- make small revisions to the query you just made so you get more
- accurate results.
+.cgi to: <perl install directory>\perl.exe %s %s
+.pl to: <perl install directory>\perl.exe %s %s
+GET,HEAD,POST
- Note: There are many more options to the Bugzilla Query Page and
- the Bug List than I have shown you. But this should be enough for
- you to learn to get around. I encourage you to check out the
- Bugzilla Home Page to learn about the Anatomy and Life Cycle of a
- Bug before continuing.
+ Change the path to Perl to match your install, of course.
_________________________________________________________________
-4.3.3. Creating and Managing Bug Reports
+3.6.2. Additional Windows Tips
+ Tip
+ From Andrew Pearson:
- And all this time, I thought we were taking bugs out...
- _________________________________________________________________
+ You can make Bugzilla work with Personal Web Server for Windows 98
+ and higher, as well as for IIS 4.0. Microsoft has information
+ available at
+ http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP
-4.3.3.1. Writing a Great Bug Report
+ Basically you need to add two String Keys in the registry at the
+ following location:
- Before we plunge into writing your first bug report, I encourage you
- to read Mozilla.org's 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.
+HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\ScriptMap
- While you are at it, why not learn how to find previously reported
- bugs? Mozilla.org has published a great tutorial on finding duplicate
- bugs, available at
- http://www.mozilla.org/quality/help/beginning-duplicate-finding.html.
+ The keys should be called ".pl" and ".cgi", and both should have a
+ value something like: c:/perl/bin/perl.exe "%s" "%s"
- I realize this was a lot to read. However, understanding the mentality
- of writing great bug reports will help us on the next part!
+ The KB article only talks about .pl, but it goes into more detail
+ and provides a perl test script.
- 1. Go back to http://landfill.tequilarista.org/mozilla/bugzilla/ in
- your browser.
- 2. Select the Enter a new bug report link.
- 3. Select a product.
- 4. Now you should be at the "Enter Bug" form. The "reporter" should
- have been automatically filled out for you (or else Bugzilla
- prompted you to Log In again -- you did keep the email with your
- username and password, didn't you?).
- 5. Select a Component in the scrollbox.
- 6. Bugzilla should have made reasonable guesses, based upon your
- browser, for the "Platform" and "OS" drop-down boxes. If those are
- wrong, change them -- if you're on an SGI box running IRIX, we
- want to know!
- 7. Fill in the "Assigned To" box with the email address you provided
- earlier. This way you don't end up sending copies of your bug to
- lots of other people, since it's just a test bug.
- 8. Leave the "CC" text box blank. Fill in the "URL" box with
- "http://www.mozilla.org".
- 9. Enter "The Bugzilla Guide" in the Summary text box, and place any
- comments you have on this tutorial, or the Guide in general, into
- the Description box.
+ Tip
- Voila! Select "Commit" and send in your bug report! Next we'll look at
- resolving bugs.
+ 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.14.
+
+ Example 3-4. Removing encrypt() for Windows NT Bugzilla version 2.12
+ or earlier
+
+ Replace this:
+
+SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " . SQLQuote(substr($rea
+lcryptpwd, 0, 2)) . ")");
+my $enteredcryptpwd = FetchOneColumn();
+
+ with this:
+
+my $enteredcryptpwd = $enteredpwd
+
+ in cgi.pl.
_________________________________________________________________
-4.3.3.2. Managing your Bug Reports
+3.6.3. Bugzilla LDAP Integration
+
+ What follows is some late-breaking information on using the LDAP
+ authentication options with Bugzilla. The author has not tested these
+ (nor even formatted this section!) so please contribute feedback to
+ the newsgroup.
+
+ Mozilla::LDAP module
+ The Mozilla::LDAP module allows you to use LDAP for authentication to
+ the Bugzilla system. This module is not required if you are not using
+ LDAP.
+ Mozilla::LDAP (aka PerLDAP) is available for download from
+ http://www.mozilla.org/directory.
+ NOTE: The Mozilla::LDAP module requires Netscape's Directory SDK.
+ Follow the link for "Directory SDK for C" on that same page to
+ download the SDK first. After you have installed this SDK, then
+ install the PerLDAP module.
+ ----------------------------------------------------------------------
+ Post-Installation Checklist
+ ----------------------------------------------------------------------
+ Set 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 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
+ servers available, this is "mail", but you may need to change this.
+ ----------------------------------------------------------------------
+ (Not sure where this bit should go, but it's important that it be in
+ there somewhere...)
+ ----------------------------------------------------------------------
+ Using LDAP authentication for Bugzilla:
+ 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. 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 tasks are still handled
+ by email address, not LDAP username. You still assign bugs by email
+ address, query on users by email address, etc.
+ ----------------------------------------------------------------------
+ _________________________________________________________________
- OK, you should have a link to the bug you just created near the top of
- your page. It should say "Bug XXXX posted", with a link to the right
- saying "Back to BUG# XXXX". Select this link.
+Chapter 4. Administering Bugzilla
- 1. Scroll down a bit on the subsequent page, until you see the
- "Resolve bug, changing resolution to (dropdown box). Normally, you
- would "Accept bug (change status to ASSIGNED)", fix it, and then
- resolve. But in this case, we're going to short-circuit the
- process because this wasn't a real bug. Change the dropdown next
- to "Resolve Bug" to "INVALID", make sure the radio button is
- marked next to "Resolve Bug", then click "Commit".
- 2. Hey! It said it couldn't take the change in a big red box! That's
- right, you must specify a Comment in order to make this change.
- Select the "Back" button in your browser, add a Comment, then try
- Resolving the bug with INVALID status again. This time it should
- work.
+ Or, I just got this cool thing installed. Now what the heck do I do
+ with it?
- You have now learned the basics of Bugzilla navigation, entering a
- bug, and bug maintenance. I encourage you to explore these features,
- and see what you can do with them! We'll spend no more time on
- individual Bugs or Queries from this point on, so you are on your own
- there.
+ So you followed "Bugzilla Installation" to the letter, and logged into
+ Bugzilla for the very first time with your super-duper god account.
+ You sit, contentedly staring at the Bugzilla Query Screen, the worst
+ of the whole mad business of installing this terrific program behind
+ you. It seems, though, you have nothing yet to query! Your first act
+ of business should be to setup the operating parameters for Bugzilla
+ so you can get busy getting data into your bug tracker.
+ _________________________________________________________________
- But I'll give a few last hints!
+4.1. Post-Installation Checklist
+
+ After installation, follow the checklist below to help ensure that you
+ have a successful installation. If you do not see a recommended
+ setting for a parameter, consider leaving it at the default while you
+ perform your initial tests on your Bugzilla setup.
+ 1. Bring up editparams.cgi in your web browser. This should be
+ available as the "edit parameters" link from any Bugzilla screen
+ once you have logged in.
+ 2. The "maintainer" is the email address of the person responsible
+ for maintaining this Bugzilla installation. The maintainer need
+ not be a valid Bugzilla user. Error pages, error emails, and
+ administrative mail will be sent with the maintainer as the return
+ email address.
+ Set "maintainer" to your email address. This allows Bugzilla's
+ error messages to display your email address and allow people to
+ contact you for help.
+ 3. The "urlbase" parameter defines the fully qualified domain name
+ and web server path to your Bugzilla installation.
+ For example, if your bugzilla query page is
+ http://www.foo.com/bugzilla/query.cgi, set your "urlbase" is
+ http://www.foo.com/bugzilla/.
+ 4. "usebuggroups" dictates whether or not to implement group-based
+ security for Bugzilla. If set, Bugzilla bugs can have an
+ associated groupmask defining which groups of users are allowed to
+ see and edit the bug.
+ Set "usebuggroups" to "on" only if you may wish to restrict access
+ to products. I suggest leaving this parameter off while initially
+ testing your Bugzilla.
+ 5. "usebuggroupsentry", when set to "on", requires that all bugs have
+ an associated groupmask when submitted. This parameter is made for
+ those installations where product isolation is a necessity.
+ Set "usebuggroupsentry" to "on" if you absolutely need to restrict
+ access to bugs from the moment they are submitted through
+ resolution. Once again, if you are simply testing your
+ installation, I suggest against turning this parameter on; the
+ strict security checking may stop you from being able to modify
+ your new entries.
+ 6. You run into an interesting problem when Bugzilla reaches a high
+ level of continuous activity. MySQL supports only table-level
+ write locking. What this means is that if someone needs to make a
+ change to a bug, they will lock the entire table until the
+ operation is complete. Locking for write also blocks reads until
+ the write is complete. The "shadowdb" parameter was designed to
+ get around this limitation. While only a single user is allowed to
+ write to a table at a time, reads can continue unimpeded on a
+ read-only shadow copy of the database. Although your database size
+ will double, a shadow database can cause an enormous performance
+ improvement when implemented on extremely high-traffic Bugzilla
+ databases.
+ Set "shadowdb" to "bug_shadowdb" if you will be running a *very*
+ large installation of Bugzilla. The shadow database enables many
+ simultaneous users to read and write to the database without
+ interfering with one another.
- There is a CLUE on the Query page that will teach you more how to use
- the form.
+ Note
- If you click the hyperlink on the Component box of the Query page, you
- will be presented a form that will describe what all the components
- are.
+ Enabling "shadowdb" can adversely affect the stability of your
+ installation of Bugzilla. You should regularly check that your
+ database is in sync. It is often advisable to force a shadow database
+ sync nightly via "cron".
+ Once again, in testing you should avoid this option -- use it if
+ or when you need to use it, and have repeatedly run into the
+ problem it was designed to solve -- very long wait times while
+ attempting to commit a change to the database. Mozilla.org began
+ needing "shadowdb" when they reached around 40,000 Bugzilla users
+ with several hundred Bugzilla bug changes and comments per day.
+ If you use the "shadowdb" option, it is only natural that you
+ should turn the "queryagainstshadowdb" option "On" as well.
+ Otherwise you are replicating data into a shadow database for no
+ reason!
+ 7. "headerhtml", "footerhtml", "errorhtml", "bannerhtml", and
+ "blurbhtml" are all templates which control display of headers,
+ footers, errors, banners, and additional data. We could go into
+ some detail regarding the usage of these, but it is really best
+ just to monkey around with them a bit to see what they do. I
+ strongly recommend you copy your data/params file somewhere safe
+ before playing with these values, though. If they are changed
+ dramatically, it may make it impossible for you to display
+ Bugzilla pages to fix the problem until you have restored your
+ data/params file.
+ If you have custom logos or HTML you must put in place to fit
+ within your site design guidelines, place the code in the
+ "headerhtml", "footerhtml", "errorhtml", "bannerhtml", or
+ "blurbhtml" text boxes.
- Possibly the most powerful feature of the Query page is the Boolean
- Chart section. It's a bit confusing to use the first time, but can
- provide unparalleled flexibility in your queries, allowing you to
- build extremely powerful requests.
+ Note
+
+ The "headerhtml" text box is the HTML printed out before any other
+ code on the page, except the CONTENT-TYPE header sent by the Bugzilla
+ engine. If you have a special banner, put the code for it in
+ "bannerhtml". You may want to leave these settings at the defaults
+ initially.
+ 8. "passwordmail" is rather simple. Every time a user creates an
+ account, the text of this parameter is read as the text to send to
+ the new user along with their password message.
+ Add any text you wish to the "passwordmail" parameter box. For
+ instance, many people choose to use this box to give a quick
+ training blurb about how to use Bugzilla at your site.
+ 9. "useqacontact" allows you to define an email address for each
+ component, in addition to that of the default owner, who will be
+ sent carbon copies of incoming bugs. The critical difference
+ between a QA Contact and an Owner is that the QA Contact follows
+ the component. If you reassign a bug from component A to component
+ B, the QA Contact for that bug will change with the reassignment,
+ regardless of owner.
+ "usestatuswhiteboard" defines whether you wish to have a
+ free-form, overwritable field associated with each bug. The
+ advantage of the Status Whiteboard is that it can be deleted or
+ modified with ease, and provides an easily-searchable field for
+ indexing some bugs that have some trait in common. Many people
+ will put "help wanted", "stalled", or "waiting on reply from
+ somebody" messages into the Status Whiteboard field so those who
+ peruse the bugs are aware of their status even more than that
+ which can be indicated by the Resolution fields.
+ Do you want to use the QA Contact ("useqacontact") and status
+ whiteboard ("usestatuswhiteboard") fields? These fields are useful
+ because they allow for more flexibility, particularly when you
+ have an existing Quality Assurance and/or Release Engineering
+ team, but they may not be needed for many smaller installations.
+ 10. Set "whinedays" to the amount of days you want to let bugs go in
+ the "New" or "Reopened" state before notifying people they have
+ untouched new bugs. If you do not plan to use this feature, simply
+ do not set up the whining cron job described in the installation
+ instructions, or set this value to "0" (never whine).
+ 11. "commenton" fields allow you to dictate what changes can pass
+ without comment, and which must have a comment from the person who
+ changed them. Often, administrators will allow users to add
+ themselves to the CC list, accept bugs, or change the Status
+ Whiteboard without adding a comment as to their reasons for the
+ change, yet require that most other changes come with an
+ explanation.
+ Set the "commenton" options according to your site policy. It is a
+ wise idea to require comments when users resolve, reassign, or
+ reopen bugs at the very least.
+
+ Note
+
+ It is generally far better to require a developer comment when
+ resolving bugs than not. Few things are more annoying to bug database
+ users than having a developer mark a bug "fixed" without any comment
+ as to what the fix was (or even that it was truly fixed!)
+ 12. The "supportwatchers" option can be an exceptionally powerful tool
+ in the hands of a power Bugzilla user. By enabling this option,
+ you allow users to receive email updates whenever other users
+ receive email updates. This is, of course, subject to the groupset
+ restrictions on the bug; if the "watcher" would not normally be
+ allowed to view a bug, the watcher cannot get around the system by
+ setting herself up to watch the bugs of someone with bugs outside
+ her priveleges. She would still only receive email updates for
+ those bugs she could normally view.
+ For Bugzilla sites which require strong inter-Product security to
+ prevent snooping, watchers are not a good idea.
+ However, for most sites you should set "supportwatchers" to "On".
+ This feature is helpful for team leads to monitor progress in
+ their respective areas, and can offer many other benefits, such as
+ allowing a developer to pick up a former engineer's bugs without
+ requiring her to change all the information in the bug.
+ _________________________________________________________________
- Finally, you can build some nifty Reports using the "Bug Reports" link
- near the bottom of the query page, and also available via the
- "Reports" link at the footer of each page.
+4.2. User Administration
+
+ User administration is one of the easiest parts of Bugzilla. Keeping
+ it from getting out of hand, however, can become a challenge.
_________________________________________________________________
-4.4. What's in it for me?
+4.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 were to delete
+ the "super user" account, re-running checksetup.pl will again prompt
+ you for this username and password.
+
+ Tip
+ If you wish to add more administrative users, you must use the MySQL
+ interface. Run "mysql" from the command line, and use these commands
+ ("mysql>" denotes the mysql prompt, not something you should type in):
+ mysql> use bugs; mysql> update profiles set groupset=0x7ffffffffffffff
+ where login_name = "(user's login name)";
+ Yes, that is fourteen "f"'s. A whole lot of f-ing going on if you want
+ to create a new administator.
+ _________________________________________________________________
- Indiana, it feels like we walking on fortune cookies!
+4.2.2. Managing Other Users
- These ain't fortune cookies, kid...
+4.2.2.1. Logging In
- Customized User Preferences offer tremendous versatility to your
- individual Bugzilla experience. Let's plunge into what you can do! The
- first step is to click the "Edit prefs" link at the footer of each
- page once you have logged in to Landfill.
+ 1. Open the index.html page for your Bugzilla installation in your
+ browser window.
+ 2. Click the "Query Existing Bug Reports" link.
+ 3. Click the "Log In" link at the foot of the page.
+ 4. Type your email address, and the password which was emailed to you
+ when you created your Bugzilla account, into the spaces provided.
+
+ Congratulations, you are logged in!
_________________________________________________________________
-4.4.1. Account Settings
+4.2.2.2. Creating new users
- On this page, you can change your basic Account Settings, including
- your password and full name. For security reasons, in order to change
- anything on this page you must type your current password into the
- "Old Password" field. If you wish to change your password, type the
- new password you want into the "New Password" field and again into the
- "Re-enter new password" field to ensure you typed your new password
- correctly. Select the "Submit" button and you're done!
+ Your users can create their own user accounts by clicking the "New
+ Account" link at the bottom of each page. 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.
+ 2. To see a specific user, type a portion of their login name in the
+ box provided and click "submit". To see all users, simply click
+ the "submit" button. You must click "submit" here to be able to
+ add a new user.
+
+ Tip
+
+ More functionality is available via the list on the right-hand side of
+ the text entry box. You can match what you type as a case-insensitive
+ substring (the default) of all users on your system, a case-sensitive
+ regular expression (please see the man regexp manual page for details
+ on regular expression syntax), or a reverse regular expression match,
+ where every user name which does NOT match the regular expression is
+ selected.
+ 3. Click the "Add New User" link at the bottom of the user list
+ 4. Fill out the form presented. This page is self-explanatory. When
+ done, click "submit".
+
+ Note
+
+ Adding a user this way will not send an email informing them of their
+ username and password. While useful for creating dummy accounts
+ (watchers which shuttle mail to another system, for instance, or email
+ addresses which are a mailing list), in general it is preferable to
+ log out and use the "New Account" button to create users, as it will
+ pre-populate all the required fields and also notify the user of her
+ account name and password.
_________________________________________________________________
-4.4.2. Email Settings
-
-4.4.2.1. Email Notification
-
- Note: The email notification settings described below have been
- obsoleted in Bugzilla 2.12, and this section will be replaced with
- a comprehensive description of the amazing array of new options at
- your disposal. However, in the meantime, throw this chunk out the
- window and go crazy with goofing around with different notification
- options.
-
- Ahh, here you can reduce or increase the amount of email sent you from
- Bugzilla! In the drop-down "Notify me of changes to", select one of
-
- All qualifying bugs: sends you every change to every bug where your
- name is somewhere on it, regardless of who changed it.
- Only those bugs which I am listed in the CC line: prevents you from
- receiving mail for which you are the reporter,' owner, or QA contact.
- If you are on the CC list, presumably someone had a good reason for
- you to get the email.
- All qulifying bugs except those which I change: This is the default,
- and a sensible setting. If someone else changes your bugs, you will
- get emailed, but if you change bugs yourself you will receive no
- notification of the change.
+4.2.2.3. Disabling Users
+
+ I bet you noticed that big "Disabled Text" entry box available from
+ the "Add New User" screen, when you edit an account? By entering any
+ text in this box and selecting "submit", you have prevented the user
+ from using Bugzilla via the web interface. Your explanation, written
+ in this text box, will be presented to the user the next time she
+ attempts to use the system.
+
+ Warning
+
+ Don't disable your own administrative account, or you will hate life!
+
+ At this time, "Disabled Text" does not prevent a user from using the
+ email interface. If you have the email interface enabled, they can
+ still continue to submit bugs and comments that way. We need a patch
+ to fix this.
_________________________________________________________________
-4.4.2.2. New Email Technology
+4.2.2.4. Modifying Users
- Note: This option may not be available in all Bugzilla
- installations, depending upon the preferences of the systems
- administrator responsible for the setup of your Bugzilla. However,
- if you really want this functionality, ask her to "enable
- newemailtech in Params" and "make it the default for all new
- users", referring her to the Administration section of this Guide.
+ Here I will attempt to describe the function of each option on the
+ Edit User screen.
- Disregard the warnings about "experimental and bleeding edge"; the
- code to handle email in a cleaner manner than that historically used
- for Bugzilla is quite robust and well-tested now.
+ * Login Name: This is generally the user's email address. However,
+ if you have edited your system parameters, this may just be the
+ user's login name or some other identifier.
+
+ Tip
+
+ For compatability reasons, you should probably stick with email
+ addresses as user login names. It will make your life easier.
+ * Real Name: Duh!
+ * Password: You can change the user password here. It is normal to
+ only see asterisks.
+ * Email Notification: You may choose from one of three options:
+ 1. All qualifying bugs except those which I change: The user
+ will be notified of any change to any bug for which she is
+ the reporter, assignee, QA Contact, CC recipient, or
+ "watcher".
+ 2. Only those bugs which I am listed on the CC line: The user
+ will not be notified of changes to bugs where she is the
+ assignee, reporter, or QA Contact, but will receive them if
+ she is on the CC list.
+
+ Note
+
+ She will still receive whining cron emails if you set up the
+ "whinemail" feature.
+ 3. All Qualifying Bugs: This user is a glutton for punishment.
+ If her name is in the reporter, QA Contact, CC, assignee, or
+ is a "watcher", she will get email updates regarding the bug.
+ Disable Text: If you type anything in this box, including just a
+ space, the user account is disabled from making any changes to
+ bugs via the web interface, and what you type in this box is
+ presented as the reason.
+
+ Warning
+
+ Don't disable the administrator account!
+
+ Note
+
+ As of this writing, the user can still submit bugs via the e-mail
+ gateway, if you set it up, despite the disabled text field. The e-mail
+ gateway should not be enabled for secure installations of Bugzilla.
+ * CanConfirm: This field is only used if you have enabled
+ "unconfirmed" status in your parameters screen. If you enable this
+ for a user, that user can then move bugs from "Unconfirmed" to
+ "Confirmed" status (e.g.: "New" status). Be judicious about
+ allowing users to turn this bit on for other users.
+ * Creategroups: This option will allow a user to create and destroy
+ groups in Bugzilla. Unless you are using the Bugzilla GroupSentry
+ security option "usebuggroupsentry" in your parameters, this
+ setting has no effect.
+ * Editbugs: Unless a user has this bit set, they can only edit those
+ bugs for which they are the assignee or the reporter.
+
+ Note
+
+ Leaving this option unchecked does not prevent users from adding
+ comments to a bug! They simply cannot change a bug priority, severity,
+ etc. unless they are the assignee or reporter.
+ * Editcomponents: This flag allows a user to create new products and
+ components, as well as modify and destroy those that have no bugs
+ associated with them. If a product or component has bugs
+ associated with it, those bugs must be moved to a different
+ product or component before Bugzilla will allow them to be
+ destroyed. The name of a product or component can be changed
+ without affecting the associated bugs, but it tends to annoy the
+ hell out of your users when these change a lot.
+ * Editkeywords: If you use Bugzilla's keyword functionality,
+ enabling this feature allows a user can create and destroy
+ keywords. As always, the keywords for existing bugs containing the
+ keyword the user wishes to destroy must be changed before Bugzilla
+ will allow it to die. You must be very careful about creating too
+ many new keywords if you run a very large Bugzilla installation;
+ keywords are global variables across products, and you can often
+ run into a phenomenon called "keyword bloat". This confuses users,
+ and then the feature goes unused.
+ * Editusers: This flag allows a user do what you're doing right now:
+ edit other users. This will allow those with the right to do so to
+ remove administrator priveleges from other users or grant them to
+ themselves. Enable with care.
+ * PRODUCT: PRODUCT bugs access. This allows an administrator, with
+ product-level granularity, to specify in which products a user can
+ edit bugs. The user must still have the "editbugs" privelege to
+ edit bugs in this area; this simply restricts them from even
+ seeing bugs outside these boundaries if the administrator has
+ enabled the group sentry parameter "usebuggroupsentry". Unless you
+ are using bug groups, this option has no effect.
+ _________________________________________________________________
+
+4.3. Product, Component, Milestone, and Version Administration
+
+
+
+ Dear Lord, we have to get our users to do WHAT?
+ _________________________________________________________________
+
+4.3.1. Products
+
+ Formerly, and in some spots still, called "Programs"
+
+ Products are the broadest category in Bugzilla, and you should have
+ the least of these. If your company makes computer games, you should
+ have one product per game, and possibly a few special products
+ (website, meetings...)
+
+ A Product (formerly called "Program", and still referred to that way
+ in some portions of the source code) controls some very important
+ functions. The number of "votes" available for users to vote for the
+ most important bugs is set per-product, as is the number of votes
+ required to move a bug automatically from the UNCONFIRMED status to
+ the NEW status. One can close a Product for further bug entry and
+ define various Versions available from the Edit product screen.
+
+ To create a new product:
+
+ 1. Select "components" from the yellow footer
+
+ Tip
+
+ It may seem counterintuitive to click "components" when you want to
+ edit the properties associated with Products. This is one of a long
+ list of things we want in Bugzilla 3.0...
+ 2. Select the "Add" link to the right of "Add a new product".
+ 3. Enter the name of the product and a description. The Description
+ field is free-form.
+
+ Tip
+
+ Don't worry about the "Closed for bug entry", "Maximum Votes per
+ person", "Maximum votes a person can put on a single bug", "Number of
+ votes a bug in this Product needs to automatically get out of the
+ UNCOMFIRMED state", and "Version" options yet. We'll cover those in a
+ few moments.
+ _________________________________________________________________
+
+4.3.2. Components
+
+ Components are subsections of a Product.
+
+ Example 4-1. Creating some Components
+
+ 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; the Owner and QA
+ Contact fields in a bug are otherwise unrelated to the Component.
+
+ To create a new Component:
+
+ 1. Select the "Edit components" link from the "Edit product" page
+ 2. Select the "Add" link to the right of the "Add a new component"
+ text on the "Select Component" page.
+ 3. Fill out the "Component" field, a short "Description", and the
+ "Initial Owner". The Component and Description fields are
+ free-form; the "Initial Owner" field must be that of a user ID
+ already existing in the database. If the initial owner does not
+ exist, Bugzilla will refuse to create the component.
+
+ Tip
+
+ Is your "Default Owner" a user who is not yet in the database? No
+ problem.
+ a. Select the "Log out" link on the footer of the page.
+ b. Select the "New Account" link on the footer of the "Relogin"
+ page
+ c. Type in the email address of the default owner you want to
+ create in the "E-mail address" field, and her full name in
+ the "Real name" field, then select the "Submit Query" button.
+ d. Now select "Log in" again, type in your login information,
+ and you can modify the product to use the Default Owner
+ information you require.
+
+ 4. Either Edit more components or return to the Bugzilla Query Page.
+ To return to the Product you were editing, you must select the
+ Components link as before.
+ _________________________________________________________________
+
+4.3.3. Versions
+
+ Versions are the revisions of the product, such as "Flinders 3.1",
+ "Flinders 95", and "Flinders 2000". Using Versions helps you isolate
+ code changes and are an aid in reporting.
+
+ Example 4-2. Common Use of Versions
+
+ A user reports a bug against Version "Beta 2.0" of your product. The
+ current Version of your software is "Release Candidate 1", and no
+ longer has the bug. This will help you triage and classify bugs
+ according to their relevance. It is also possible people may report
+ bugs against bleeding-edge beta versions that are not evident in older
+ versions of the software. This can help isolate code changes that
+ caused the bug
+
+ Example 4-3. A Different Use of Versions
+
+ This field has been used to good effect by an online service provider
+ in a slightly different way. They had three versions of the product:
+ "Production", "QA", and "Dev". Although it may be the same product, a
+ bug in the development environment is not normally as critical as a
+ Production bug, nor does it need to be reported publicly. When used in
+ conjunction with Target Milestones, one can easily specify the
+ environment where a bug can be reproduced, and the Milestone by which
+ it will be fixed.
+
+ 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
+ "undefined". If your product doesn't use version numbers, you may
+ want to leave this as it is or edit it so that it is "---". You
+ can then go back to the edit versions page and add new versions to
+ your product.
+ Otherwise, click the "Add" button to the right of the "Add a new
+ version" text.
+ 3. Enter the name of the Version. This can be free-form characters up
+ to the limit of the text box. Then select the "Add" button.
+ 4. At this point you can select "Edit" to edit more Versions, or
+ return to the "Query" page, from which you can navigate back to
+ the product through the "components" link at the foot of the Query
+ page.
+ _________________________________________________________________
+
+4.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. Or, you have a bug that you
+ plan to fix for 2.8, this would have a milestone of 2.8.
+
+ Note
+
+ Milestone options will only appear for a Product if you turned the
+ "usetargetmilestone" field in the "Edit Parameters" screen "On".
+
+ To create new Milestones, set Default Milestones, and set Milestone
+ URL:
+
+ 1. Select "edit milestones"
+ 2. Select "Add" to the right of the "Add a new milestone" 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. Select "Add".
+ Example 4-4. Using SortKey with Target Milestone
+ Let's say you create a target milestone called "Release 1.0", with
+ Sortkey set to "0". Later, you realize that you will have a public
+ beta, called "Beta1". You can create a Milestone called "Beta1",
+ with a Sortkey of "-1" in order to ensure people will see the
+ Target Milestone of "Beta1" earlier on the list than "Release 1.0"
+ 4. If you want to add more milestones, select the "Edit" link. If you
+ don't, well shoot, you have to go back to the "query" page and
+ select "components" again, and make your way back to the Product
+ you were editing.
+
+ Note
+
+ This is another in the list of unusual user interface decisions that
+ we'd like to get cleaned up. Shouldn't there be a link to the effect
+ of "edit the Product I was editing when I ended up here"? In any case,
+ clicking "components" in the footer takes you back to the "Select
+ product" screen, from which you can begin editing your product again.
+ 5. From the Edit product screen again (once you've made your way
+ back), enter the URL for a description of what your milestones are
+ for this product in the "Milestone URL" field. It should be of the
+ format "http://www.foo.com/bugzilla/product_milestones.html"
+ Some common uses of this field include product descriptions,
+ product roadmaps, and of course a simple description of the
+ meaning of each milestone.
+ 6. If you're using Target Milestones, the "Default Milestone" field
+ must have some kind of entry. If you really don't care if people
+ set coherent Target Milestones, simply leave this at the default,
+ "---". However, controlling and regularly updating the Default
+ Milestone field is a powerful tool when reporting the status of
+ projects.
+ Select the "Update" button when you are done.
+ _________________________________________________________________
+
+4.3.5. Voting
+
+ The concept of "voting" is a poorly understood, yet powerful feature
+ for the management of open-source projects. Each user is assigned so
+ many Votes per product, which they can freely reassign (or assign
+ multiple votes to a single bug). 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.
+
+ The daunting challenge of Votes is deciding where you draw the line
+ for a "vocal majority". If you only have a user base of 100 users,
+ setting a low threshold for bugs to move from UNCONFIRMED to NEW makes
+ sense. As the Bugzilla user base expands, however, these thresholds
+ must be re-evaluated. You should gauge whether this feature is worth
+ the time and close monitoring involved, and perhaps forego
+ implementation until you have a critical mass of users who demand it.
+
+ To modify Voting settings:
+
+ 1. Navigate to the "Edit product" screen for the Product you wish to
+ modify
+ 2. Set "Maximum Votes per person" to your calculated value. Setting
+ this field to "0" disables voting.
+ 3. Set "Maximum Votes a person can put on a single bug" to your
+ calculated value. It should probably be some number lower than the
+ "Maximum votes per person". Setting this field to "0" disables
+ voting, but leaves the voting options open to the user. This is
+ confusing.
+ 4. Set "Number of votes a bug in this product needs to automatically
+ get out of the UNCONFIRMED state" to your calculated number.
+ Setting this field to "0" disables the automatic move of bugs from
+ UNCONFIRMED to NEW. Some people advocate leaving this at "0", but
+ of what use are Votes if your Bugzilla user base is unable to
+ affect which bugs appear on Development radar?
+
+ Tip
+
+ You should probably set this number to higher than a small coalition
+ of Bugzilla users can influence it. Most sites use this as a
+ "referendum" mechanism -- if users are able to vote a bug out of
+ UNCONFIRMED, it is a really bad bug!
+ 5. Once you have adjusted the values to your preference, select the
+ "Update" button.
+ _________________________________________________________________
+
+4.3.6. Groups and Group Security
+
+ Groups can be very useful in bugzilla, because they allow users to
+ isolate bugs or products that should only be seen by certain people.
+ Groups can also be a complicated minefield of interdependencies and
+ weirdness if mismanaged.
+
+ Example 4-5. When to Use Group Security
+
+ Many Bugzilla sites isolate "Security-related" bugs from all other
+ bugs. This way, they can have a fix ready before the security
+ vulnerability is announced to the world. You can create a "Security"
+ product which, by default, has no members, and only add members to the
+ group (in their individual User page, as described under User
+ Administration) who should have priveleged access to "Security" bugs.
+ Alternately, you may create a Group independently of any Product, and
+ change the Group mask on individual bugs to restrict access to members
+ only of certain Groups.
+
+ Groups only work if you enable the "usebuggroups" paramater. In
+ addition, if the "usebuggroupsentry" parameter is "On", one can
+ restrict access to products by groups, so that only members of a
+ product group are able to view bugs within that product. Group
+ security in Bugzilla can be divided into two categories: Generic and
+ Product-Based.
+
+ Note
+
+ Groups in Bugzilla are a complicated beast that evolved out of very
+ simple user permission bitmasks, apparently itself derived from common
+ concepts in UNIX access controls. A "bitmask" is a fixed-length number
+ whose value can describe one, and only one, set of states. For
+ instance, UNIX file permissions are assigned bitmask values: "execute"
+ has a value of 1, "write" has a value of 2, and "read" has a value of
+ 4. Add them together, and a file can be read, written to, and executed
+ if it has a bitmask of "7". (This is a simplified example -- anybody
+ who knows UNIX security knows there is much more to it than this.
+ Please bear with me for the purpose of this note.) The only way a
+ bitmask scheme can work is by doubling the bit count for each value.
+ Thus if UNIX wanted to offer another file permission, the next would
+ have to be a value of 8, then the next 16, the next 32, etc.
+
+ Similarly, Bugzilla offers a bitmask to define group permissions, with
+ an internal limit of 64. Several are already occupied by built-in
+ permissions. The way around this limitation is to avoid assigning
+ groups to products if you have many products, avoid bloating of group
+ lists, and religiously prune irrelevant groups. In reality, most
+ installations of Bugzilla support far fewer than 64 groups, so this
+ limitation has not hit for most sites, but it is on the table to be
+ revised for Bugzilla 3.0 because it interferes with the security
+ schemes of some administrators.
+
+ To enable Generic Group Security ("usebuggroups"):
+
+ 1. Turn "On" "usebuggroups" in the "Edit Parameters" screen.
+ 2. You will generally have no groups set up. Select the "groups" link
+ in the footer.
+ 3. Take a moment to understand the instructions on the "Edit Groups"
+ screen. Once you feel confident you understand what is expected of
+ you, select the "Add Group" link.
+ 4. Fill out the "New Name" (remember, no spaces!), "New Description",
+ and "New User RegExp" fields. "New User RegExp" allows you to
+ automatically place all users who fulfill the Regular Expression
+ into the new group.
+ Example 4-6. Creating a New Group
+ I created a group called DefaultGroup with a description of "This
+ is simply a group to play with", and a New User RegExp of
+ ".*@mydomain.tld". This new group automatically includes all
+ Bugzilla users with "@mydomain.tld" at the end of their user id.
+ When I finished, my new group was assigned bit #128.
+ When you have finished, select the Add button.
+
+ To enable Product-Based Group Security (usebuggroupsentry):
+
+ Warning
+
+ Don't forget that you only have 64 groups masks available, total, for
+ your installation of Bugzilla! If you plan on having more than 50
+ products in your individual Bugzilla installation, and require group
+ security for your products, you should consider either running
+ multiple Bugzillas or using Generic Group Security instead of
+ Product-Based ("usebuggroupsentry") Group Security.
+
+ 1. Turn "On" "usebuggroups" and "usebuggroupsentry" in the "Edit
+ Parameters" screen.
+
+ Warning
+
+ "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, Products, etc. with the administrative
+ account.
+ 2. You will generally have no Groups set up, unless you enabled
+ "usebuggroupsentry" prior to creating any Products. To create
+ "Generic Group Security" groups, follow the instructions given
+ above. To create Product-Based Group security, simply follow the
+ instructions for creating a new Product. If you need to add users
+ to these new groups as you create them, you will find the option
+ to add them to the group available under the "Edit User" screens.
- I recommend you enable the option, "Click here to sign up (and risk
- any bugs)". Your email-box will thank you for it. The fundamental
- shift in "newemailtech" is away from standard UNIX "diff" output,
- which is quite ugly, to a prettier, better laid-out email.
+ You may find this example illustrative for how bug groups work.
+
+ Example 4-7. Bugzilla Groups
+
+ Bugzilla Groups example
+ -----------------------
+ For this example, let us suppose we have four groups, call them
+ Group1, Group2, Group3, and Group4.
+ We have 5 users, User1, User2, User3, User4, User5.
+ We have 8 bugs, Bug1, ..., Bug8.
+ Group membership is defined by this chart:
+ (X denotes that user is in that group.)
+ (I apologize for the nasty formatting of this table. Try viewing
+ it in a text-based browser or something for now. -MPB)
+ G G G G
+ r r r r
+ o o o o
+ u u u u
+ p p p p
+ 1 2 3 4
+ +-+-+-+-+
+ User1|X| | | |
+ +-+-+-+-+
+ User2| |X| | |
+ +-+-+-+-+
+ User3|X| |X| |
+ +-+-+-+-+
+ User4|X|X|X| |
+ +-+-+-+-+
+ User5| | | | |
+ +-+-+-+-+
+ Bug restrictions are defined by this chart:
+ (X denotes that bug is restricted to that group.)
+ G G G G
+ r r r r
+ o o o o
+ u u u u
+ p p p p
+ 1 2 3 4
+ +-+-+-+-+
+ Bug1| | | | |
+ +-+-+-+-+
+ Bug2| |X| | |
+ +-+-+-+-+
+ Bug3| | |X| |
+ +-+-+-+-+
+ Bug4| | | |X|
+ +-+-+-+-+
+ Bug5|X|X| | |
+ +-+-+-+-+
+ Bug6|X| |X| |
+ +-+-+-+-+
+ Bug7|X|X|X| |
+ +-+-+-+-+
+ Bug8|X|X|X|X|
+ +-+-+-+-+
+ Who can see each bug?
+ Bug1 has no group restrictions. Therefore, Bug1 can be seen by any
+ user, whatever their group membership. This is going to be the only
+ bug that User5 can see, because User5 isn't in any groups.
+ Bug2 can be seen by anyone in Group2, that is User2 and User4.
+ Bug3 can be seen by anyone in Group3, that is User3 and User4.
+ Bug4 can be seen by anyone in Group4. Nobody is in Group4, so none of
+ these users can see Bug4.
+ Bug5 can be seen by anyone who is in _both_ Group1 and Group2. This
+ is only User4. User1 cannot see it because he is not in Group2, and
+ User2 cannot see it because she is not in Group1.
+ Bug6 can be seen by anyone who is in both Group1 and Group3. This
+ would include User3 and User4. Similar to Bug5, User1 cannot see Bug6
+ because he is not in Group3.
+ Bug7 can be seen by anyone who is in Group1, Group2, and Group3. This
+ is only User4. All of the others are missing at least one of those
+ group priveleges, and thus cannot see the bug.
+ Bug8 can be seen by anyone who is in Group1, Group2, Group3, and
+ Group4. There is nobody in all four of these groups, so nobody can
+ see Bug8. It doesn't matter that User4 is in Group1, Group2, and
+ Group3, since he isn't in Group4.
_________________________________________________________________
-4.4.2.3. "Watching" Users
+4.4. Bugzilla Security
- Note: This option may not be available in all Bugzilla
- installations, depending upon the preferences of the systems
- administrator responsible for the setup of your Bugzilla. However,
- if you really want this functionality, ask her to "enable watchers
- in Params".
- By entering user email names into the "Users to watch" text entry box,
- delineated by commas, you can watch bugs of other users. This powerful
- functionality enables seamless transitions as developers change
- projects, managers wish to get in touch with the issues faced by their
- direct reports, or users go on vacation. If any of these three
- situations apply to you, you will undoubtedly find this feature quite
- convenient.
- _________________________________________________________________
-4.4.3. Page Footer
+ Putting your money in a wall safe is better protection than depending
+ on the fact that no one knows that you hide your money in a mayonnaise
+ jar in your fridge.
- Note: By default, this page is quite barren. However, go explore
- the Query Page some more; you will find that you can store numerous
- queries on the server, so if you regularly run a particular query
- it is just a drop-down menu away. On this page of Preferences, if
- you have many stored queries you can elect to have them always
- one-click away!
+ Note
- If you have many stored queries on the server, here you will find
- individual drop-downs for each stored query. Each drop-down gives you
- the option of that query appearing on the footer of every page in
- Bugzilla! This gives you powerful one-click access to any complex
- searches you may set up, and is an excellent way to impress your
- boss...
+ Poorly-configured MySQL, Bugzilla, and FTP installations have given
+ attackers full access to systems in the past. Please take these
+ guidelines seriously, even for Bugzilla machines hidden away behind
+ your firewall. 80% of all computer trespassers are insiders, not
+ anonymous crackers.
- Tip: By default, the "My Bugs" link appears at the bottom of each
- page. However, this query gives you both the bugs you have
- reported, as well as those you are assigned. One of the most common
- uses for this page is to remove the "My Bugs" link, replacing it
- with two other queries, commonly called "My Bug Reports" and "My
- Bugs" (but only referencing bugs assigned to you). This allows you
- to distinguish those bugs you have reported from those you are
- assigned. I commonly set up complex Boolean queries in the Query
- page and link them to my footer in this page. When they are
- significantly complex, a one-click reference can save hours of
- work.
- _________________________________________________________________
+ Secure your installation.
-4.4.4. Permissions
+ Note
- This is a purely informative page which outlines your current
- permissions on this installation of Bugzilla. If you have permissions
- to grant certain permissions to other users, the "other users" link
- appears on this page as well as the footer. For more information
- regarding user administration, please consult the Administration
- section of this Guide.
- _________________________________________________________________
+ 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
+
+ 1. Ensure you are running at least MysQL version 3.22.32 or newer.
+ Earlier versions had notable security holes and poorly secured
+ 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!
+ At the very least, ensure you password the "mysql -u root" account
+ and the "bugs" account, establish grant table rights (consult the
+ Keystone guide in Appendix C: The Bugzilla Database for some
+ easy-to-use details) that do not allow CREATE, DROP, RELOAD,
+ SHUTDOWN, and PROCESS for user "bugs". I wrote up the Keystone
+ advice back when I knew far less about security than I do now : )
+ 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.
-4.5. Using Bugzilla-Conclusion
+ Note
- Thank you for reading through this portion of the Bugzilla Guide. I
- anticipate it may not yet meet the needs of all readers. If you have
- additional comments or corrections to make, please submit your
- contributions to the mozilla-webtools mailing list/newsgroup. The
- mailing list is mirrored to the netscape.public.mozilla.webtools
- newsgroup, and the newsgroup is mirrored to
- mozilla-webtools@mozilla.org
+ "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/ and $BUGZILLA_HOME/shadow/ directories, as
+ well as the $BUGZILLA_HOME/localconfig and
+ $BUGZILLA_HOME/globals.pl files. The localconfig file stores your
+ "bugs" user password, which would be terrible to have in the hands
+ of a criminal, while the "globals.pl" stores some default
+ information regarding your installation which could aid a system
+ cracker. In addition, some files under $BUGZILLA_HOME/data/ store
+ sensitive information, and $BUGZILLA_HOME/shadow/ stores bug
+ information for faster retrieval. If you fail to secure these
+ directories and this file, you will expose bug information to
+ those who may not be allowed to see it.
+
+ Note
+
+ 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.
+ On Apache, you can use .htaccess files to protect access to these
+ directories, as outlined in Bug 57161 for the localconfig file,
+ and Bug 65572 for adequate protection in your data/ and shadow/
+ directories.
+ 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
+ Place the following text into a file named ".htaccess", readable
+ by your web server, in your $BUGZILLA_HOME/shadow directory.
+ deny from all
_________________________________________________________________
Chapter 5. Integrating Bugzilla with Third-Party Tools
5.1. Bonsai
- We need Bonsai integration information.
+ 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. These kinds of changes cause the engineer
+ responsible to be "on the hook" (include cool URL link here for Hook
+ policies at mozilla.org). Bonsai also includes gateways to Tinderbox,
+ the Mozilla automated build management system and Bugzilla
_________________________________________________________________
5.2. CVS
- We need CVS integration information
+ CVS integration is best accomplished, at this point, using the
+ Bugzilla Email Gateway. There have been some files submitted to allow
+ greater CVS integration, but we need to make certain that Bugzilla is
+ not tied into one particular software management package.
+
+ Follow the instructions in the FAQ 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.
+
+ There is also a 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/, under the "cvszilla" link.
_________________________________________________________________
5.3. Perforce SCM
- Richard Brooksby created a Perforce integration tool for Bugzilla and
- TeamTrack. You can find the main project page at
- http://www.ravenbrook.com/project/p4dti. "p4dti" is now an officially
- supported product from Perforce, and you can find the "Perforce Public
- Depot" p4dti page at
+ 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
- fairly seamless. However, p4dti is a patch against the Bugzilla 2.10
- release, not the current 2.12 release. I anticipate patches for 2.12
- will be out shortly. Check the project page regularly for updates, or
- take the given patches and patch it manually. p4dti is designed to
+ 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.
-
- Right now, there is no way to synchronize the Bug ID and the Perforce
- Transaction Number, or to change the Bug ID to read (PRODUCT).bugID
- unless you hack it in. Additionally, if you have synchronization
- problems, the easiest way to avoid them is to only put the bug
- information, comments, etc. into Bugzilla, and not into the Perforce
- change records. They will link anyway; merely reference the bug ID
- fixed in your change description, and put a comment into Bugzilla
- giving the change ID that fixed the Bugzilla bug. It's a process
- issue, not a technology question.
_________________________________________________________________
-5.4. Tinderbox
+5.4. Tinderbox/Tinderbox2
- We need Tinderbox integration information
+ We need Tinderbox integration information.
_________________________________________________________________
Chapter 6. The Future of Bugzilla
Bugzilla's Future. Much of this is the present, now.
- _________________________________________________________________
-6.1. Reducing Spam
-
- Those who use Bugzilla frequently are probably used to notification sp
- am
- - unwanted or unnecessary notifications. A number of proposals have
- been put forward to attempt to reduce this.
- 1. Reduce CC Spam
- Some of you probably know me as that guy who CCs on heaps and heaps of
- bugs. Just as you get a lot of CC changes from me, so do I get a lot
- from others. Why should CC changes send out email notifications?
- It's not necessarily the best idea to just remove the CC spam, there a
- re
- other issues too, like the difficulty of adding to large CC fields.
- For these reasons and more, an RFE for a per user "BCC" facility exist
+ Bugzilla's future is a constantly-changing thing, as various
+ developers "scratch an itch" when it comes to functionality. Thus this
+ section is very malleable, subject to change without notice, etc.
+ You'll probably also notice the lack of formatting. I apologize that
+ it's not quite as readable as the rest of the Guide.
+
+ Bugzilla Blue Sky
+ Customisability
+ One of the major stumbling blocks of Bugzilla has been that it is t
+ oo
+ rigid and does not adapt itself well enough to the needs of an
+ organisation. This has led to organisations making changes to the
+ Bugzilla code that need to be redone each new version of Bugzilla.
+ Bugzilla should attempt to move away from this to a world where thi
s
- that people could use to silently and privately track bugs, in a simil
- ar
- way to voting today, but applying to an unlimited number of bugs. See
- "http://bugzilla.mozilla.org/show_bug.cgi?id=7345".
- 2. Bulk Changes
- You know the drill - a large milestone change, a component movement,
- whatever, and lots of notifications are generated. If there's enough
- maybe you'll just go delete, delete, delete, whoops, there goes anothe
- r
- notification that wasn't from the bulk change you missed.
- Shouldn't bulk changes send out one notification? A proposal for this
- is at "http://bugzilla.mozilla.org/show_bug.cgi?id=26943".
- 3. Configurable Notification Criteria
- It would be good if you could choose what you want to receive. There
- are two parts to this.
- (a) Choose a selection of bugs you're interested in. This would be
- similar to CC except you let the set be computed from selection criter
- ia
- rather than limited to the bugs your name is on. There is currently a
- limited version of this in the bugzilla preferences, ie "all qualifyin
- g
- bugs"/"all qualifying bugs except the ones I change"/"only those bugs
- which I am listed on the cc line".
- (b) Choose what changes will trigger a notification for the bugs you a
- re
- watching. With this, you could choose whether you want to receive cc,
- dependency and keyword changes, for example.
- Both of these proposals live at
- "http://bugzilla.mozilla.org/show_bug.cgi?id=14137".
- Note that they also live at
- "http://bugzilla.mozilla.org/show_bug.cgi?id=17464", and the change
- has been checked in. This is fixed with Bugzilla 2.12 and is no longe
+ doesn't need to occur.
+ Most of the subsections in this section are currently explicit desi
+ gn
+ goals for the "Bugzilla 3" rewrite. This does not necessarily mean
+ that they will not occur before them in Bugzilla 2, but most are
+ significant undertakings.
+ Field Customisation
+ Many installations wish to customise the fields that appear on bug
+ reports. Current versions of Bugzilla offer limited
+ customisability. In particular, some fields can be turned off.
+ However, many administrators wish to add their own fields, and rena
+ me
+ or otherwise modify existing fields. An architecture that supports
+ this would be extraordinarily useful.
+ Indeed, many fields work similarly and could be abstracted into "fi
+ eld
+ types", so that an administrator need write little or no code to
+ support the new fields they desire.
+ Possible field types include text (eg status whiteboard), numbers,
+ dates (eg report time), accounts (eg reporter, qa, cc), inter-bug
+ relationships (dependencies, duplicates), option groups (platform,
+ os,
+ severity, priority, target milestone, version) etc.
+ Ideally an administrator could configure their fields through a
+ Bugzilla interface that requires no code to be added. However, it
+ is
+ highly unlikely this ideal will never be met, and in a similar way
+ that office applications have scripting languages, Bugzilla should
+ allow new field types to be written.
+ Similarly, a common desire is for resolutions to be added or remove
+ d.
+ Allocations
+ ?
+ Option Groups
+ ?
+ Relations
+ ?
+ Database Integrity
+ Furthermore, it is desirable for administrators to be able to speci
+ fy
+ rules that must or should apply between the fields on a bug report.
+ For example, you might wish to specify that a bug with status ASSIG
+ NED
+ must have a target milestone field that that is not untargetted. O
r
- an issue. Woo-Hoo!
- _________________________________________________________________
-
-6.2. Better Searching
-
- Current searching tools in Bugzilla include the querying mechanism,
- special summary reports and dependency trees. This message is about n
- ew
- facilities.
- 1. General Summary Reports
- For some time now it has been apparent to me that the query bug list
- leaves a little to be desired in its linear nature. There is a need t
- o
- have categorised subsets, and counts of each category. If you don't
- believe me, how about these facilities already in place or which peopl
- e
- have asked for:
- Most Doomed Reports - Categorised On Assignee, Shows and Counts Number
- of Bugs For Each Assignee
- Bug #15806 (Most Voted For Bugs) - Categorised On Product, Shows Bugs
- Voters Most Want Fixed
- Bug #9789 (BugAThon Tracking Page) - Categorised On Developer (Subset)
+ that a bug with a certain number of votes should get ASSIGNED. Or
+ that the QA contact must be different from the assignee.
+ "Must" relationships could be implemented by refusing to make chang
+ es
+ that violate the relationships, or alternatively, automatically
+ updating certain fields in order to satisfy the criteria. Which
+ occurs should be up to the administrator.
+ "Should" relationships could be implemented by a combination of
+ emitting warnings on the process bug page, the same on notification
+ mails, or emitting periodic whine mails about the situation. Again
,
- Counts Number of Bugs
- Bug #9409 and #9411 - The desire to be able to report on more subsets.
- Hopefully you can see the gist of what is desired here. It's a genera
- l
- reporting mechanism.
- This mechanism lets you choose the subset of bugs to operate on (like
- query), let's you categorise them, possibly along with subcategories a
- nd
- counts the number of bugs within each category. It might or might not
- show the actual bugs themselves, and it might limit the number of bugs
- within a category, or categories to report on.
- I'm further sure that many applications of this mechanism would only b
+ which occurs should be up to the administrator.
+ It should also be possible for whine mails to be emitted for "must"
+ relationships, as they might become violated through direct databas
e
- recognised once it was implemented.
- The general summary reports bug is at
- "http://bugzilla.mozilla.org/show_bug.cgi?id=12282".
- 2. Related Bugs
- It would be nice to have a field where you could enter other bugs
- related to the current bug - it would be handy for navigation and
- possibly even finding duplicates. See
- "http://bugzilla.mozilla.org/show_bug.cgi?id=12286".
- 3. Column Specification Support
- Currently query seems to get what columns to report on from whatever t
- he
- user last used. This doesn't work well for "prepackaged queries", whe
- re
- you followed a link. You can probably add a column by specifying a so
- rt
- column, but this is difficult and suboptimal.
- Furthermore, I find that when I want to add a column to a query, it's
- usually a one off and I would prefer it to go away for the next query.
-
- Hence, it would be nice to specify the columns that appear on the quer
+ access, Bugzilla bugs, or because they were there before the
+ relationship was enforced.
+ As well as implementing intra-bug constraints, it would be useful t
+ o
+ create inter-bug constraints. For example, a bug that is dependent
+ on
+ another bug should not have an earlier milestone or greater priorit
y
- (and general summary report) pages. The default query mechanism shoul
- d
- be able to let you specify your default columns.
- This proposal lives at
- "http://bugzilla.mozilla.org/show_bug.cgi?id=12284".
- _________________________________________________________________
-
-6.3. Description Flags and Tracking Bugs
-
- Since I last posted on this issue, we now have "keywords" that solve
- many of the issues of description and status whiteboard keywords. We
- have seen a migration towards keywords, but there is still further to
- go.
- Description ( + Status Whiteboard ) Keywords
- --------------------------------------------
- Some description keywords remain. I'd like to hear what reasons, othe
+ than that bug.
+ Database Adaptability
+ Often an administrator desires that fields adapt to the values of
+ other fields. For example, the value of a field might determine th
+ e
+ possible values of another field or even whether it appears (whethe
r
- than time, there are for these staying as they are. I'm suspecting ma
- ny
- are not really being used. Hopefully we can totally remove these
- eventually.
- Tracking Bugs
- -------------
- When I suggested keywords, I did so to get rid of tracking bugs too,
- though we've had less success on that front.
- There are many disadvantages to tracking bugs.
- - They can pollute bugs counts, and you must make sure you exclude
- them. I believe the meta keyword might be used for this purpose.
- - They have an assignee but there is nothing to fix, and that person c
- an
- get whined at by Bugzilla.
- - It would be better to craft your own "dependency tree" rather than
- rely on a fixed hierachy in the bug system.
- - In creating a nice little hierachy, many bugs duplicate information
- that should be available in other ways, eg
- "http://bugzilla.mozilla.org/show_bug.cgi?id=12833" which is
- about beta 1 networking issues. These could fall behind the actual
- data. What tracking bugs are good for, ad hoc lists, is what keywords
- are better for.
- - An automatically generated dependency structure between one "trackin
- g
- bug" and another would be better than a manual one, since it gives exa
- ct
- rather than manually set up classifications.
- Probably the only feature preventing tracking bugs being replaced is t
- he
- dependency tree. The quintessential tracking bug seems to be bug #722
- 9
- "chofmann's watch list", which probably has about a couple of hundred
- bugs at various levels, which allows a nice visualisation.
- Before keywords can replace tracking bugs better visualisation is goin
- g
- to be required. General summary reports and dependency forests of a b
- ug
- list ("http://bugzilla.mozilla.org/show_bug.cgi?id=12992") could both
- help, but neither solves the problem totally. Perhaps keywords within
- keywords would help here. In any case, I'm still thinking about this
- one.
- Some tracking bugs could definitely be turned into keywords immediatel
+ it is "applicable").
+ Limited adaptability is present in Bugzilla 2, and only on the
+ "Product" field:
+ * The possible values of the target milestone, version and compon
+ ent
+ fields depend on the product.
+ * UNCONFIRMED can be turned off for specific products.
+ * Voting can be configured differently or turned off for differen
+ t
+ products, and there is a separate user vote limits for each
+ product.
+ It would be good if more adaptability was present, both in terms of
+ all fields relying on the product, as well as the ability to adapt
+ based on the value of all fields.
+ Example ???
+ General adaptability raises the issue of circular references betwee
+ n
+ fields causing problems. One possible solution to this is to place
+ the fields in a total ordering and require a field refer only to th
+ e
+ previous fields.
+ In Bugzilla 2, changing the product of a bug meant a second page wo
+ uld
+ appear that allowed you to choose a new milestone, component and
+ version, as those fields adapted themselves to the new product. Th
+ is
+ page could be generalised to support all instances where:
+ * a field value must or might be changed because the possible val
+ ues
+ have changed
+ * is going to drop off because it it is no longer applicable, and
+ this should be confirmed
+ * must be specified because it is suddenly applicable, and the
+ default value, if one exists, might not be acceptable
+ Database Independence
+ Currently Bugzilla only runs on the MySQL database. It would be
+ desirable for Bugzilla to run on other databases, because:
+ * Organisations may have existing database products they use and
+ would prefer to run a homogenous environment.
+ * Databases each have their own shortcomings, including MySQL. A
+ n
+ administrator might choose a database that would work better wi
+ th
+ their Bugzilla.
+ This raises the possibility that we could use features that are onl
y
- though, and I'll point the finger at
- "http://bugzilla.mozilla.org/show_bug.cgi?id=7954" here since that's
- what came to mind first.
- _________________________________________________________________
-
-6.4. Bug Issues
-
- 1. Inline Bug Changes
- Why do I see so many "moving to M5" and "reassigning to blahblah"
- messages, and in other circumstances none are entered? Why aren't the
- se
- automatically generated? A comment should be only necessary when ther
+ present in some databases, by appropriately falling back. For
+ example, in the MySQL world, we live without:
+ * record-level locking, instead we use table-level locking
+ * referential and record constraints, instead we checking code
+ * subselects, instead we use multiple queries and redundant "cach
+ es"
+ Multiple Front Ends
+ Currently Bugzilla is manipulated via the Web, and notifies via
+ E-Mail. It would be desirable for Bugzilla to easily support vario
+ us
+ front ends.
+ There is no reason that Bugzilla could not be controlled via a whol
+ e
+ range of front ends, including Web, E-Mail, IRC, ICQ, etc, and
+ similarly for how it notifies. It's also possible that we could
+ introduce a special Bugzilla client that uses its own protocol, for
+ maximum user productivity.
+ Indeed a request reply might be returned via a totally different
+ transport method than was use to submit the request.
+ Internationalisation
+ Bugzilla currently supports only English. All of the field names,
+ user instructions, etc are written in English. It would be desirab
+ le
+ to allow "language packs" so Bugzilla can be easily used in
+ non-English speaking locales.
+ To a degree field customisation supports this, because administrato
+ rs
+ could specify their own fields names anyway. However, there will
+ always be some basic facilities not covered by this, and it is
+ desirable that the administrator's interface also is
+ internationalisable.
+ Better Searching
+ General Summary Reports
+ Sometimes, the normal querying page leaves a lot to be desired. Th
+ ere
+ are other facilities already in place or which people have asked fo
+ r:
+ Most Doomed Reports - All Bugs or All Bugs In A Product, Categorise
+ d
+ On Assignee, Shows and Counts Number of Bugs For Each Assignee
+ Most Voted For Bugs - All Bugs, Categorised On Product, Shows Top T
+ en
+ Bugs Voters Most Want Fixed
+ Number of Open Bugs For An Assignee - Bug List, Categorised On
+ Developers, Counts Number of Bugs In Category
+ The important thing to realise is that people want categorised repo
+ rts
+ on all sorts of things - a general summary report.
+ In a categorised report, you choose the subset of bugs you wish to
+ operate on (similar to how you would specify a query), and then
+ categorise them on one or more fields.
+ For each category you display the count of the number of things in
+ that category. You can optionally display the bugs themselves, or
+ leave them out, just showing the counts. And you can optionally li
+ mit
+ the number of things (bugs or subcategories) that display in each
+ category.
+ Such a mechanism would let you do all of the above and more.
+ Applications of this mechanism would only be recognised once it was
+ implemented.
+ Related Bugs
+ It would be nice to have a field where you could enter other bugs
+ related to the current bug. It would be handy for navigation and
+ possibly even finding duplicates.
+ Column Specification Support
+ Currently bug lists use the columns that you last used. This doesn
+ 't
+ work well for "prepackaged queries", where you followed a link. Yo
+ u
+ can probably add a column by specifying a sort column, but this is
+ difficult and suboptimal.
+ Furthermore, I find that when I want to add a column to a bug list,
+ it's usually a one off and I would prefer it to go away for the nex
+ t
+ query. Hence, it would be nice to specify the columns that appear
+ on
+ the bug list (and general summary report) pages. The default query
+ mechanism should be able to let you specify your default columns.
+ Advanced Querying Redesign
+ ?
+ Keywords
+ People have a need to apply tags to bugs. In the beginning, people
+ placed designators in the summary and status whiteboard. However,
+ these fields were not designed for that, and so there were many fla
+ ws
+ with this system:
+ * They pollute the field with information that was never intended
+ to
+ be present.
+ * Removing them with a bulk change is a difficult problem that ha
+ s
+ too many pitfalls to implement.
+ * You can easily get the capitalisation wrong.
+ Then dependencies were introduced (when?), and people realised that
+ they could use them for "tracking bugs". Again, dependencies were
+ not
+ designed for that, and so there were more flaws, albeit different
+ ones, including:
+ * They aren't really bugs, so it's difficult to distinguish issue
+ s
+ from bugs.
+ * They can pollute bugs counts, and you must somehow exclude them
+ from queries.
+ * There is a whole lot of useless information on them. They have
+ an
+ assignee but there is nothing to fix, and that person can get
+ whined at by Bugzilla. They have target milestones which must
+ be
+ manually maintained. And so on.
+ Finally, keywords were introduced (when?) for this purpose to remov
e
- is something to add, and if I'm not interested in this sort of
- information, I should be able to hide it.
- At the moment we're in a hybrid world where we don't get everything, b
- ut
- we can't get rid of the bug change "messages" either. Furthermore,
- "View Bug Activity" requires me to manually cross reference events on
- another page, rather than being able to visually see the chronological
- order. Shouldn't I be able to see all the information on one page?
- A proposal to allow bugs to be shown either way is at
- "http://bugzilla.mozilla.org/show_bug.cgi?id=11368".
- 2. Hard Wrapping Comments
- One thing that annoys me is the fact that comments are "hard wrapped"
+ the need for these two systems. Unfortunately, the simple keywords
+ implementation was itself lacking in certain features provided by t
+ he
+ two previous systems, and has remained almost unchanged since its
+ inception. Furthermore, it could not be forseen that in large
+ installations, the sheer number of keywords could become unwieldly
+ and
+ could lead to a movement back to the other systems.
+ The keywords system was the right idea, however, and it remains so.
+ Fixing the keywords system is one of the most important Bugzilla
+ issues.
+ Bringing Keywords Up To Par
+ For the most part, keywords are very good at what they do. It is e
+ asy
+ to add and remove them (unlike summary/whiteboard designators), we
+ can
+ simply see what issues are present on a bug (unlike tracking bugs),
+ and we do not confuse bugs with issues (unlike tracking bugs).
+ However, there are still some "regressions" in the keyword system o
+ ver
+ previous systems:
+ * Users wish to view the "dependency forest" of a keyword. While
+ a
+ dependency tree is of one bug, a dependency forest is of a bug
+ list, and consists of a dependency tree for each member of the
+ bug
+ list. Users can work around this with tracking bugs by creatin
+ g a
+ tracking bug and viewing the dependency tree of that tracking b
+ ug.
+ * Users wish to specify the keywords that initially apply to a bu
+ g,
+ but instead they must edit the bug once it has already been
+ submitted. They can work around this with summary designators,
+ since they specify the summary at reporting time.
+ * Users wish to store or share a bug list that contains a keyword
+ s
+ column. Hence they wish to be able to specify what columns app
+ ear
+ in the bug list URL, as mentioned earlier. They can work aroun
+ d
+ this using summary designators, since almost all bug lists have
+ a
+ summary column.
+ * Users wish to be able to view keywords on a bug list. However
+ often they are only interested in a small number of keywords.
+ Having a bug list with a keywords column means that all keyword
+ s
+ will appear on a bug list. This can take a substantial amount
+ of
+ space where a bug has a lot of keywords, since the table column
+ s
+ in Bugzilla adjust to the largest cell in that column. Hence
+ users wish to be able to specify which keywords should appear i
+ n
+ the bug list. In a very real sense, each keyword is a field un
to
- a certain column width. This is a mistake Internet Mail and News has
- made, unlike every word processor in existence, and as a consequence,
- Usenet suffers to this day from bad software. Why has Bugzilla repeat
- ed
- the problem?
- Hard wrapping to a certain column width is open to abuse (see old
- Mozilla browsers that didn't wrap properly, resulting in many ugly bug
- reports we have to read to this day), and furthermore doesn't expand t
- o
- fill greater screen sizes. I'm also under the impression the current
- hard wrap uses a non-standard HTML facility. See
- "http://bugzilla.mozilla.org/show_bug.cgi?id=11901".
- 3. REMIND and LATER Are Evil
- I really hate REMIND and LATER. Not because they mean something
- won't be implemented, but because they aren't the best solutions.
- Why are they bad? Well, basically because they are not resolved, yet
- they are marked as such. Hence queries have to be well crafted to
- include them.
- LATER, according to Bugzilla, means it won't be done this release.
- There is a better mechanism of doing this, that is assigning to
- nobody@mozilla.org and making the milestone blank. It's more likely t
+ itself. Users can work around this by using summary designator
+ s,
+ since they keywords will share the space in the summary column.
+ * Users wish to know when bugs with a specific issue are resolved
+ .
+ Hence they wish to be able to receive notifications on all the
+ bugs with a specific keyword. The introduction a generic watch
+ ing
+ facility (also for things like watching all bugs in a component
+ )
+ would achieve this. Users can work around this by using tracki
+ ng
+ bugs, as dependencies have an existing way of detecting fixes t
o
- appear in a casual query, and it doesn't resolve the bug.
- REMIND, according to Bugzilla, means it might still be implemented thi
+ bug a bug was blocked by.
+ Dealing With The Keyword Overload
+ At the time of writing, the mozilla.org installation has approximat
+ ely
+ 100 keywords, and many more would be in use if the keywords system
+ didn't have the problems it does.
+ Such a large number of keywords introduces logistical problems:
+ * It must be easy for someone to learn what a keyword means. If
+ a
+ keyword is buried within a lot of other keywords, it can be
+ difficult to find.
+ * It must be easy to see what keywords are on a bug. If the numb
+ er
+ of keywords is large, then this can be difficult.
+ These lead some people to feel that there are "too many keywords".
+ These problems are not without solutions however. It is harder to
+ find a list of designators or tracking bugs than it is a list of
+ keywords.
+ The essential problem is it needs to be easy to find the keywords
+ we're interested in through the mass of keywords.
+ Keyword Applicability
+ As has been previously mentioned, it is desirable for fields to be
+ able to adapt to the values of other fields. This is certainly tru
+ e
+ for keywords. Many keywords are simply not relevant because of the
+ bugs product, component, etc.
+ Hence, by introducing keyword applicability, and not displaying
+ keywords that are not relevant to the current bug, or clearly
+ separating them, we can make the keyword overload problem less
+ significant.
+ Currently when you click on "keywords" on a bug, you get a list of
+ all
+ bugs. It would be desirable to introduce a list of keywords tailor
+ ed
+ to a specific bug, that reports, in order:
+ * the keywords currently on the bug
+ * the keywords not currently on the bug, but applicable to the bu
+ g
+ * optionally, the keywords not applicable to the bug
+ This essentially orders the keywords into three groups, where each
+ group is more important than the previous, and therefore appears
+ closer to the top.
+ Keyword Grouping & Ordering
+ We could further enhance both the global and bug specific keyword l
+ ist
+ by grouping keywords. We should always have a "flat" view of
+ keywords, but other ways of viewing the keywords would be useful to
+ o.
+ If keyword applicability was implemented, we could group keywords
+ based on their "applicability condition". Keywords that apply to a
+ ll
+ bugs could be separated from keywords that apply to a specific
+ product, both on the global keyword list and the keyword list of a
+ bug
+ that is in that product.
+ We could specify groups of our own. For example, many keywords are
+ in
+ a mutually exclusive group, essentially like radio buttons in a use
+ r
+ interface. This creates a natural grouping, although other groupin
+ gs
+ occur (which depends on your keywords).
+ It is possible that we could use collapsing/expanding operations on
+ "twisties" to only should the groups we are interested in.
+ And instead of grouping keywords, we could order them on some metri
+ c
+ of usefulness, such as:
+ * when the keyword was last added to a bug
+ * how many bugs the keyword is on
+ * how many open bugs the keyword is on
+ Opting Out Of Keywords
+ Not all people are going to care about all keywords. Therefore it
+ makes sense that you may wish to specify which keywords you are
+ interested in, either on the bug page, or on notifications.
+ Other keywords will therefore not bother users who are not interest
+ ed
+ in them.
+ Keyword Security
+ Currently all keywords are available and editable to all people wit
+ h
+ edit bugs access. This situation is clearly suboptimal.
+ Although relying on good behaviour for people to not do what they
+ shouldn't works reasonably well on the mozilla.org, it is better to
+ enforce that behaviour - it can be breached through malice, acciden
+ t
+ or ignorance.
+ And in the situation where it is desirable for the presence or abse
+ nce
+ of a keyword not to be revealed, organisations either need to be
+ content with the divulgence, or not use keywords at all.
+ In the situation where they choose to divulge, introducing the abil
+ ity
+ to restrict who can see the keyword would also reduce keyword
+ overload.
+ Personal Keywords
+ Keywords join together a set of bugs which would otherwise be
+ unrelated in the bug system.
+ We allow users to store their own queries. However we don't allow
+ them to store their own keywords on a bug. This reduces the
+ usefulness of personal queries, since you cannot join a set of
+ unrelated bugs together in a way that you wish. Lists of bug numbe
+ rs
+ can work, by they can only be used for small lists, and it is
+ impossible to share a list between multiple queries.
+ Personal keywords are necessary to replace personal tracking bugs,
+ as
+ they would not pollute the keyword space. Indeed, on many
+ installations this could remove some keywords out of the global
+ keyword space.
+ In a similar vein and with similar effects, group keywords could be
+ introduced that are only available to members of a specific group.
+ Keyword Restrictions
+ Keywords are not islands unto themselves. Along with their potenti
+ al
+ to be involved in the inter-field relationships mentioned earlier,
+ keywords can also be related to other keywords.
+ Essentially, there are two possibilities:
+ * a set of keywords are mutually exclusive
+ * the presence of a keyword implies another keyword must be prese
+ nt
+ Introduction of the ability to specify these restrictions would hav
+ e
+ benefits.
+ If mutually exclusive keywords were present on a bug, their removal
+ would fix up the database, as well as reducing the number of keywor
+ ds
+ on that bug.
+ In the situation where a keyword implies another keyword, there are
+ two possiblities as to how to handle the situation.
+ The first is automatically add the keyword. This would fix up the
+ database, but it would increase the number of keywords on a bug.
+ The second is to automatically remove the keyword, and alter querie
+ s
+ so they pick up the first keyword as well as the removed keyword.
+ This would fix up the database and reduce the number of keywords on
+ a
+ bug, but it might confuse users who don't see the keyword.
+ Alternatively, the implied keywords could be listed separately.
+ Notifications
+ Every time a bug gets changed notifications get sent out to people
+ letting them know about what changes have been made. This is a
+ significant feature, and all sorts of questions can be raised, but
+ they mainly boil down to when they should be sent and what they sho
+ uld
+ look like.
+ Changes You're Interested In
+ As of version 2.12 users can specify what sort of changes they are
+ interested in receiving notifications for. However, this is still
+ limited. As yet there is no facility to specify which keywords you
+ care about, and whether you care about changes to fields such as th
+ e
+ QA contact changes.
+ Furthermore, often an unnecessary comment will go along with a chan
+ ge,
+ either because it is required, or the commenter is ignorant of how
+ the
+ new system works. While explaining why you did something is useful
+ ,
+ merely commenting on what you did is not because that information i
s
- release. Well, why not just move it to a later milestone then? You'r
+ already accessible view "Bug Activity".
+ Because of this unnecessary comment, a lot of changes that would
+ otherwise not generate notifications for certain people do so, beca
+ use
+ few people are willing to turn off comments. One way to deal with
+ this problem is to allow people to specify that their comments are
+ purely explanatory, and that anyone who is not interested in the
+ change will not be interested in the comment.
+ Furthermore, one possible rationale for unnecessary comments is tha
+ t
+ the bug activity does not display on the normal page and hence it i
+ s
+ difficult to cross reference comments and actions. Hence, it would
+ be
+ beneficial to be able to do this.
+ Bugs You're Watching
+ Currently to receive a notification about a bug you need to have yo
+ ur
+ name on it. This is suboptimal because you need to know about a bu
+ g
+ before you can receive notifications on it. Often you are interest
+ ed
+ in any bug with a field set to a specific value. For example, you
+ might be interested in all bugs with a specific product, component
+ or
+ keyword.
+ If someone could automatically receive notifications about these bu
+ gs,
+ it would make everyone's lives easier. Currently the default assig
+ nee
+ and QA contact for a component will automatically receive
+ notifications for
+ Question: This moves half way to a BCC.
+ Bulk Changes
+ A very useful feature of Bugzilla is the ability to perform an acti
+ on
+ on multiple bugs at once. However, this means that similar
+ notifications are currently generated for each bug modified.
+ This can result in a torrent of notifications that can annoy.
+ Furthermore, since the bugs are all changed close to each other in
+ time, it is easy for someone to mass delete all the notifications
+ generated by a bulk change and miss an unrelated notification in th
e
- a lot less likely to forget it. If it's really needed, a keyword woul
+ middle.
+ These factors can lead to a tendency for people to delay bulk chang
+ es,
+ or avoid them entirely. This is suboptimal.
+ It would be better if a bulk change generated only one notification
+ mail. This would vastly reduce the annoyance factor, and prevent
+ accidental deletion of notifications.
+ One problem with this change is that some people separate out
+ notifications using filtering. This means that they would no longe
+ r
+ be match parts of a bulk change under different filtering rules.
+ One possibility to resolve this is to allow people to specify group
+ s
+ of bugs. All bugs within a group would go into the same
+ notification. The filters could then distinguish the different bug
+ groups.
+ In any case, it is likely there would need to be a transition perio
d
- be better.
- Some people can't use blank milestones to mean an untargetted mileston
+ to allow people to alter their filters.
+ Nominations
+ ?
+ Linking Bugzilla Installations
+ The first example of linking Bugzilla installations together has is
+ the introduction of bug moving in version 2.12. However, it would
+ be
+ useful to be able to link installations in more ways.
+ * Dependencies and other relationships between bugs in other
+ installations. This is difficult because dependencies are
+ synchronised on both bugs, so the installation that changes
+ dependencies would need to communicate the new state to the oth
+ er
+ installation. It would also mean that relationships and
+ notifications that refer to other bugs would need to communicat
+ e
+ with the other installation.
+ * References to bugs in other installations. Currently if you ty
+ pe
+ "bug XXX" or "bug #XXX" where XXX is a number, you get an
+ automatic hyperlink to that bug. It would be useful if you cou
+ ld
+ say "YYY bug #XXX" where YYY is the name of another installatio
+ n.
+ Retirement
+ ?
+ Whiny Reports
+ ?
+ Group Redesign
+ ?
+ Hard Wrapping Comments
+ Currently Bugzilla "hard wraps" its comments to a specific line siz
e,
- since they use this to assess new bugs that have no target. Hence, it
- would be nice to distinguish between bugs that have not yet been
- considered, and those that really are not assigned to any milestone in
- the future (assumedly beyond).
- All this is covered at
- "http://bugzilla.mozilla.org/show_bug.cgi?id=13534".
- 4. Create An Enhancement Field
- Currently enhancement is an option in severity. This means that
- important enhancements (like for example, POP3 support) are not proper
- ly
- distinguished as such, because they need a proper severity. This
- dilutes the meaning of enhancement.
- If enhancement was separated, we could properly see what was an
- enhancement. See "http://bugzilla.mozilla.org/show_bug.cgi?id=9412".
- I
- see keywords like [RFE] and [FEATURE] that seem to be compensating for
- this problem.
+ similar to E-Mail. This has various problems:
+ * The way it currently works, wrapping is done in the browser at
+ submission time using a non-standard HTML extension not support
+ ed
+ by some (uncommon) browsers. These browsers generate comments
+ that scroll off the right side of the screen.
+ * Because comments are of fixed width, when you expand your brows
+ er
+ window, the comments do not expand to fit available space.
+ It would be much better to move to a world of soft wrapping, where
+ the
+ browser wraps the text at display time, similar to a world processo
+ r.
+ And as in a word processor, soft wrapping does not preclude the
+ insertion of newlines.
+ Hard wrapping is too entrenched into text E-Mail to fix, but we can
+ fix Bugzilla without causing any problems. The old content will st
+ ill
+ be wrapped too early, but at least new content will work.
_________________________________________________________________
-6.5. Database Integrity
+Chapter 7. Bugzilla Variants and Competitors
- Bugzilla could be more proactive in detecting suboptimal situations an
- d
- prevent them or whine about them.
- 1. Bugzilla Crime #1: Marking A Bug Fixed With Unresolved Dependencies
- It can't be marked fixed with unresolved dependencies. Either mark it
- INVALID (tracking bugs), fix the dependencies at the same time, or
- resolve the blockers.
- See "http://bugzilla.mozilla.org/show_bug.cgi?id=24496".
- 2. Keyword Restrictions
- Some keywords should only apply in certain circumstances, eg beta1 =>
- Milestone <
- M14, css1 => Component = Style System are possibilities. See
- "http://bugzilla.mozilla.org/show_bug.cgi?id=26940".
- 3. Whine About Old Votes
- Old votes can just sit on resolved bugs. This is problematic with
- duplicates especially. Automatic transferral/removal is not
- appropriate since bugs can be reopened, but a whining solution might
- work. See "http://bugzilla.mozilla.org/show_bug.cgi?id=27553".
- 4. Whine And Warn About Milestone Mismatches
- Here's a fun one. Bug X (M17) depends on Bug Y (M15). Bug Y gets mov
- ed
- out to M19. The notification to the assignee of Bug X gets ignored (o
- f
- course) and Bug X is now due to be fixed before one of its blockers.
- Warnings about this when it is detected as well as whining about it in
- email would help bring these issues to the attention of people sooner.
- Note that this would be less of a problem if we didn't have so many
- tracking bugs since they aren't updated that often and often have this
- problem.
- See "http://bugzilla.mozilla.org/show_bug.cgi?id=16743".
+ 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
+ _________________________________________________________________
+
+7.1. Red Hat Bugzilla
+
+ Red Hat Bugzilla is probably the most popular Bugzilla variant on the
+ planet. One of the major benefits of Red Hat Bugzilla is the ability
+ to work with Oracle, MySQL, and PostGreSQL databases serving as the
+ back-end, instead of just MySQL. Dave Lawrence has worked very hard to
+ keep Red Hat Bugzilla up-to-date, and many people prefer the
+ snappier-looking page layout of Red Hat Bugzilla to the default
+ Mozilla-standard formatting.
+
+ URL: http://bugzilla.redhat.com/bugzilla/
+ _________________________________________________________________
+
+7.2. Loki Bugzilla (Fenris)
+
+ Fenris can be found at http://fenris.lokigames.com. It is a fork from
+ Bugzilla.
+ _________________________________________________________________
+
+7.3. Issuezilla
+
+ Issuezilla is another fork from Bugzilla, and seems nearly as popular
+ as the Red Hat Bugzilla fork. Some Issuezilla team members are regular
+ contributors to the Bugzilla mailing list/newsgroup. Issuezilla is not
+ the primary focus of bug-tracking at tigris.org, however. Their
+ Java-based bug-tracker, Scarab, a newfangled Java-based issue tracker,
+ is under heavy development and looks promising!
+
+ URL: http://issuezilla.tigris.org/servlets/ProjectHome
+ _________________________________________________________________
+
+7.4. Scarab
+
+ Scarab is a promising new bug-tracking system built using Java Serlet
+ technology. As of this writing, no source code has been released as a
+ package, but you can obtain the code from CVS.
+
+ URL: http://scarab.tigris.org
+ _________________________________________________________________
+
+7.5. Perforce SCM
+
+ Although Perforce isn't really a bug tracker, it can be used as such
+ through the "jobs" functionality.
+
+ http://www.perforce.com/perforce/technotes/note052.htmlhttp://www.perf
+ orce.com/perforce/technotes/note052.html
_________________________________________________________________
-6.6. Bugzilla 3.0
+7.6. SourceForge
- One day, Bugzilla 3.0 will have lots of cool stuff.
+ SourceForge is more of a way of coordinating geographically
+ distributed free software and open source projects over the Internet
+ than strictly a bug tracker, but if you're hunting for bug-tracking
+ for your open project, it may be just what the software engineer
+ ordered!
+
+ URL: http://www.sourceforge.net
_________________________________________________________________
Appendix A. The Bugzilla FAQ
@@ -2765,9 +3913,7 @@ Appendix A. The Bugzilla FAQ
3. Loki Bugzilla (AKA Fenris)
- A.3.1. What about Loki Bugzilla?
- A.3.2. Who maintains Fenris (Loki Bugzilla) now?
- A.3.3.
+ A.3.1. What is Loki Bugzilla (Fenris)?
4. Pointy-Haired-Boss Questions
@@ -2790,35 +3936,36 @@ Appendix A. The Bugzilla FAQ
of fields and format of them, and the choice of
acceptable values?
- A.4.7. Does Bugzilla provide any reporting features, metrics,
+ A.4.7. The index.html page doesn't show the footer. It's really
+ annoying to have to go to the querypage just to check my
+ "my bugs" link. How do I get a footer on static HTML
+ pages?
+
+ A.4.8. Does Bugzilla provide any reporting features, metrics,
graphs, etc? You know, the type of stuff that management
likes to see. :)
- A.4.8. Is there email notification and if so, what do you see
+ A.4.9. Is there email notification and if so, what do you see
when you get an email? Do you see bug number and title or
is it only the number?
- A.4.9. Can email notification be set up to send to multiple
+ A.4.10. Can email notification be set up to send to multiple
people, some on the To List, CC List, BCC List etc?
- A.4.10. If there is email notification, do users have to have any
+ A.4.11. If there is email notification, do users have to have any
particular type of email application?
- A.4.11. If I just wanted to track certain bugs, as they go
+ A.4.12. If I just wanted to track certain bugs, as they go
through life, can I set it up to alert me via email
whenever that bug changes, whether it be owner, status or
description etc.?
- A.4.12. Does Bugzilla allow data to be imported and exported? If
+ A.4.13. Does Bugzilla allow data to be imported and exported? If
I had outsiders write up a bug report using a MS Word bug
template, could that template be imported into "matching"
fields? If I wanted to take the results of a query and
export that data to MS Excel, could I do that?
- A.4.13. Does Bugzilla allow fields to be added, changed or
- deleted? If I want to customize the bug submission form
- to meet our needs, can I do that using our terminology?
-
A.4.14. Has anyone converted Bugzilla to another language to be
used in other countries? Is it localizable?
@@ -2873,7 +4020,7 @@ Appendix A. The Bugzilla FAQ
A.6.1. How do I completely disable MySQL security if it's giving
me problems (I've followed the instructions in the
- README!)?
+ installation section of this guide!)?
A.6.2. Are there any security problems with Bugzilla?
A.6.3. I've implemented the security fixes mentioned in Chris
@@ -3024,14 +4171,8 @@ Appendix A. The Bugzilla FAQ
A.1.5. Who maintains Bugzilla?
- There are many, many contributors from around the world maintaining
- Bugzilla. The designated "Maintainer" is Tara Hernandez, with QA
- support by Matthew Tuck. Dan Mosedale and Dawn Endico are employees of
- Mozilla.org responsible for the installation of Bugzilla there, and
- are very frequent code contributors. Terry Weissman originally ported
- Bugzilla, but "these days, Terry just hangs around and heckles." The
- rest of us are mostly transient developers; Bugzilla suits our needs,
- and we contribute code as we have needs for updates.
+ Bugzilla maintenance has been in a state of flux recently. Please
+ check the Bugzilla Project Page for the latest details.
A.1.6. How does Bugzilla stack up against other bug-tracking
databases?
@@ -3044,10 +4185,10 @@ Appendix A. The Bugzilla FAQ
email integration, and platform independence), improved scalability,
open source code, greater flexibility, and superior ease-of-use.
- If you happen to be a commercial Bugzilla vendor, please step forward
- with a rebuttal so I can include it in the FAQ. We're not in pursuit
- of Bugzilla ueber alles; we simply love having a powerful, open-source
- tool to get our jobs done.
+ If you happen to be a commercial bug-tracker vendor, please step
+ forward with a rebuttal so I can include it in the FAQ. We're not in
+ pursuit of Bugzilla ueber alles; we simply love having a powerful,
+ open-source tool to get our jobs done.
A.1.7. How do I change my user name in Bugzilla?
@@ -3111,19 +4252,23 @@ Appendix A. The Bugzilla FAQ
for the various webtools, and not subject to anyone else. Edit it
to point to whatever you like.
- Note: We always recommend that, if possible, you keep the path as
- /usr/bonsaitools/bin/perl, and simply add a /usr/bonsaitools and
- /usr/bonsaitools/bin directory, then symlink your version of perl
- to /usr/bonsaitools/bin/perl. This will make upgrading your
- Bugzilla much easier in the future.
+ Note
+
+ We always recommend that, if possible, you keep the path as
+ /usr/bonsaitools/bin/perl, and simply add a /usr/bonsaitools and
+ /usr/bonsaitools/bin directory, then symlink your version of perl to
+ /usr/bonsaitools/bin/perl. This will make upgrading your Bugzilla much
+ easier in the future.
- Obviously, if you do not have root access to your Bugzilla box, our
- suggestion is irrelevant.
+ Obviously, if you do not have root access to your Bugzilla box, our
+ suggestion is irrelevant.
2. Red Hat Bugzilla
- Note: This section is no longer up-to-date. Please see the section
- on "Red Hat Bugzilla" under "Variants" in The Bugzilla Guide.
+ Note
+
+ This section is no longer up-to-date. Please see the section on "Red
+ Hat Bugzilla" under "Variants" in The Bugzilla Guide.
A.2.1. What about Red Hat Bugzilla?
@@ -3217,10 +4362,11 @@ Appendix A. The Bugzilla FAQ
A.2.3. What's the current status of Red Hat Bugzilla?
- Note: This information is somewhat dated; I last updated it 7 June
- 2000. Please see the "Variants" section of "The Bugzilla Guide" for
- more up-to-date information regarding Red Hat Bugzilla.
+ Note
+ This information is somewhat dated; I last updated it 7 June 2000.
+ Please see the "Variants" section of "The Bugzilla Guide" for more
+ up-to-date information regarding Red Hat Bugzilla.
Dave Lawrence:
I suppose the current thread warrants an update on the status of
@@ -3269,45 +4415,23 @@ Appendix A. The Bugzilla FAQ
3. Loki Bugzilla (AKA Fenris)
- Note: Loki's "Fenris" Bugzilla is based upon the (now ancient)
- Bugzilla 2.8 tree, and is no longer actively maintained. It works
- well enough for Loki. Additionally, the major differences in Fenris
- have now been integrated into the main source tree of Bugzilla, so
- there's not much reason to go grab the source. I leave this section
- of the FAQ principally for historical interest, but unless Loki has
- further input into Bugzilla's future, it will be deprecated in
- future versions of the Guide.
-
- A.3.1. What about Loki Bugzilla?
+ A.3.1. What is Loki Bugzilla (Fenris)?
Loki Games has a customized version of Bugzilla available at
- http://fenris.lokigames.com. From that page,
-
- You may have noticed that Fenris is a fork from Bugzilla-- our
- patches weren't suitable for integration --and a few people have
- expressed interest in the code. Fenris has one major improvement
- over Bugzilla, and that is individual comments are not appended
- onto a string blob, they are stored as a record in a separate
- table. This allows you to, for instance, separate comments out
- according to privilege levels in case your bug database could
- contain sensitive information not for public eyes. We also provide
- things like email hiding to protect user's privacy, additional
- fields such as 'user_affected' in case someone enters someone
- else's bug, comment editing and deletion, and more conditional
- system variables than Bugzilla does (turn off attachments,
- qacontact, etc.).
-
- A.3.2. Who maintains Fenris (Loki Bugzilla) now?
-
- Raphael Barrerro <raistlin@lokigames.com>. Michael Vance created the
- initial fork, but no longer maintains the project.
-
- A.3.3.
+ http://fenris.lokigames.com. There are some advantages to using
+ Fenris, chief being separation of comments based upon user privacy
+ level, data hiding, forced login for any data retrieval, and some
+ additional fields. Loki has mainted their code, originally a fork from
+ the Bugzilla 2.8 code base, and it is quite a bit different than stock
+ Bugzilla at this point. I recommend you stick with official Bugzilla
+ version 2.14 rather than using a fork, but it's up to you.
4. Pointy-Haired-Boss Questions
- Note: The title of this section doesn't mean you're a PHB -- it
- just means you probably HAVE a PHB who wants to know this :)
+ Note
+
+ The title of this section doesn't mean you're a PHB -- it just means
+ you probably HAVE a PHB who wants to know this :)
A.4.1. Is Bugzilla web-based or do you have to have specific software
or specific operating system on your machine?
@@ -3320,10 +4444,7 @@ Appendix A. The Bugzilla FAQ
with Perforce (SCM software)?
Yes! You can find more information elsewhere in "The Bugzilla Guide"
- in the "Integration with Third-Party Products" section. The section on
- Perforce isn't very large, but as the maintainer of the Guide is
- charged with Perforce/Bugzilla integration by his company, you can
- expect this section to grow.
+ in the "Integration with Third-Party Products" section.
A.4.3. Does Bugzilla allow the user to track multiple projects?
@@ -3356,7 +4477,52 @@ Appendix A. The Bugzilla FAQ
progression states, also require adjusting the program logic to
compensate for the change.
- A.4.7. Does Bugzilla provide any reporting features, metrics, graphs,
+ 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
+
+ A.4.7. The index.html page doesn't show the footer. It's really
+ annoying to have to go to the querypage just to check my "my bugs"
+ link. How do I get a footer on static HTML pages?
+
+ It's possible to get the footer on the static index page using Server
+ Side Includes (SSI). The trick to doing this is making sure that your
+ web server is set up to allow SSI and specifically, the #exec
+ directive. You should also rename index.html to index.shtml.
+
+ After you've done all that, you can add the following line to
+ index.shtml:
+<!--#exec cmd="/usr/bin/perl -e "require 'CGI.pl'; PutFooter();"" -->
+
+ Note
+
+ This line will be replaced with the actual HTML for the footer when
+ the page is requested, so you should put this line where you want the
+ footer to appear.
+
+ Because this method depends on being able to use a #exec directive,
+ and most ISP's will not allow that, there is an alternative method.
+ You could have a small script (such as api.cgi) that basically looks
+ like:
+#!/usr/bonsaitools/bin/perl -w
+
+require 'globals.pl';
+
+if ($::FORM{sub} eq 'PutFooter') {
+ PutFooter();
+} else {
+ die 'api.cgi was incorrectly called';
+}
+
+ and then put this line in index.shtml.
+ <!--#include virtual="api.cgi?sub=PutFooter"-->
+
+ Note
+
+ This still requires being able to use Server Side Includes, if this
+ simply will not work for you, see bug 80183 for a third option.
+
+ A.4.8. 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
@@ -3371,7 +4537,7 @@ Appendix A. The Bugzilla FAQ
Advanced Reporting is a Bugzilla 3.X proposed feature.
- A.4.8. Is there email notification and if so, what do you see when you
+ A.4.9. Is there email notification and if so, what do you see when you
get an email? Do you see bug number and title or is it only the
number?
@@ -3379,26 +4545,27 @@ Appendix A. The Bugzilla FAQ
bug report accompany each email notification, along with a list of the
changes made.
- A.4.9. Can email notification be set up to send to multiple people,
+ A.4.10. Can email notification be set up to send to multiple people,
some on the To List, CC List, BCC List etc?
Yes.
- A.4.10. If there is email notification, do users have to have any
+ A.4.11. If there is email notification, do users have to have any
particular type of email application?
Bugzilla email is sent in plain text, the most compatible mail format
on the planet.
- Note: 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.
+ Note
+
+ 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.
- A.4.11. If I just wanted to track certain bugs, as they go through
+ A.4.12. If I just wanted to track certain bugs, as they go through
life, can I set it up to alert me via email whenever that bug changes,
whether it be owner, status or description etc.?
@@ -3407,7 +4574,7 @@ Appendix A. The Bugzilla FAQ
tab of the User Preferences screen in Bugzilla to the "Only those bugs
which I am listed on the CC line" option.
- A.4.12. Does Bugzilla allow data to be imported and exported? If I had
+ A.4.13. Does Bugzilla allow data to be imported and exported? If I had
outsiders write up a bug report using a MS Word bug template, could
that template be imported into "matching" fields? If I wanted to take
the results of a query and export that data to MS Excel, could I do
@@ -3429,12 +4596,6 @@ Appendix A. The Bugzilla FAQ
find an excellent example at
http://www.mozilla.org/quality/help/bugzilla-helper.html
- A.4.13. Does Bugzilla allow fields to be added, changed or deleted? If
- I want to customize the bug submission form to meet our needs, can I
- do that using our terminology?
-
- Yes.
-
A.4.14. Has anyone converted Bugzilla to another language to be used
in other countries? Is it localizable?
@@ -3532,7 +4693,7 @@ Appendix A. The Bugzilla FAQ
A.5.1. How do I download and install Bugzilla?
Check http://www.mozilla.org/projects/bugzilla/ for details. Once you
- download it, untar it, read the README and the Bugzilla Guide.
+ download it, untar it, read the Bugzilla Guide.
A.5.2. How do I install Bugzilla on Windows NT?
@@ -3546,7 +4707,8 @@ Appendix A. The Bugzilla FAQ
6. Bugzilla Security
A.6.1. How do I completely disable MySQL security if it's giving me
- problems (I've followed the instructions in the README!)?
+ problems (I've followed the instructions in the installation section
+ of this guide!)?
Run mysql like this: "mysqld --skip-grant-tables". Please remember
this makes mysql as secure as taping a $100 to the floor of a football
@@ -3558,7 +4720,7 @@ Appendix A. The Bugzilla FAQ
The Bugzilla code has not undergone a complete security audit. It is
recommended that you closely examine permissions on your Bugzilla
installation, and follow the recommended security guidelines found in
- the README and in The Bugzilla Guide.
+ The Bugzilla Guide.
A.6.3. 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
@@ -3613,18 +4775,11 @@ Appendix A. The Bugzilla FAQ
If you are using an alternate Mail Transport Agent (MTA other than
sendmail), make sure the options given in the "processmail" script for
- all instances of "sendmail" are correct for your MTA. If you are using
- Sendmail, you may wish to delete the "-ODeliveryMode=deferred" option
- in the "processmail" script for every invocation of "sendmail". (Be
- sure and leave the "-t" option, though!)
-
- A better alternative is to change the "-O" option to
- "-ODeliveryMode=background". This prevents Sendmail from hanging your
- Bugzilla Perl processes if the domain to which it must send mail is
- unavailable.
+ all instances of "sendmail" are correct for your MTA.
- This is now a configurable parameter called "sendmailnow", available
- from editparams.cgi.
+ If you are using Sendmail, try enabling "sendmailnow" in
+ editparams.cgi. If you are using Postfix, you will also need to enable
+ "sendmailnow".
A.7.7. How come email never reaches me from bugzilla changes?
@@ -3667,12 +4822,17 @@ Appendix A. The Bugzilla FAQ
A.8.3. I think my database might be corrupted, or contain invalid
entries. What do I do?
- Run the "sanity check" utility (./sanitycheck.cgi in the bugzilla_home
- directory) to see! If it all comes back, you're 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...
+ Run the "sanity check" utility (./sanitycheck.cgi in the Bugzilla_home
+ directory) from your web browser to see! If it finishes without
+ errors, you're probably 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.
A.8.4. I want to manually edit some entries in my database. How?
@@ -3728,10 +4888,10 @@ Appendix A. The Bugzilla FAQ
A.8.9. How come even after I delete bugs, the long descriptions show
up?
- Delete everything from $BUZILLA_HOME/shadow. Bugzilla creates shadow
- files there, with each filename corresponding to a bug number. Also be
- sure to run syncshadowdb to make sure, if you are using a shadow
- database, that the shadow database is current.
+ This should only happen with Bugzilla 2.14 if you are using the
+ "shadow database" feature, and your shadow database is out of sync.
+ Try running syncshadowdb -syncall to make sure your shadow database is
+ in synch with your primary database.
9. Bugzilla and Win32
@@ -3942,8 +5102,8 @@ Appendix A. The Bugzilla FAQ
Try this link to view current bugs or requests for enhancement for
Bugzilla.
- You can view bugs marked for 2.14 release here. This list includes
- bugs for the 2.14 release that have already been fixed and checked
+ You can view bugs marked for 2.16 release here. This list includes
+ bugs for the 2.16 release that have already been fixed and checked
into CVS. Please consult the Bugzilla Project Page for details on how
to check current sources out of CVS so you can have these bug fixes
early!
@@ -3963,8 +5123,7 @@ Appendix A. The Bugzilla FAQ
A.11.3. What's the best way to submit patches? What guidelines should
I follow?
- 1. Enter a bug into bugzilla.mozilla.org for the "Webtools" product,
- "Bugzilla" component.
+ 1. Enter a bug into bugzilla.mozilla.org for the "Bugzilla" product.
2. Upload your patch as a unified DIFF (having used "diff -u" against
the current sources checked out of CVS), or new source file by
clicking "Create a new attachment" link on the bug page you've
@@ -3995,7 +5154,7 @@ Appendix B. Software Download Links
Bugzilla: http://www.mozilla.org/projects/bugzilla/
- MySQL: http://www.mysql.org/
+ MySQL: http://www.mysql.com/
Perl: http://www.perl.org/
@@ -4026,9 +5185,11 @@ Appendix B. Software Download Links
Appendix C. The Bugzilla Database
- Note: This document really needs to be updated with more fleshed
- out information about primary keys, interrelationships, and maybe
- some nifty tables to document dependencies. Any takers?
+ Note
+
+ This document really needs to be updated with more fleshed out
+ information about primary keys, interrelationships, and maybe some
+ nifty tables to document dependencies. Any takers?
_________________________________________________________________
C.1. Database Schema Chart
@@ -4040,212 +5201,132 @@ C.1. Database Schema Chart
C.2. MySQL Bugzilla Database Introduction
- Contributor(s): Matthew P. Barnson (mbarnson@excitehome.net)
- Last update: May 16, 2000
- Changes:
- Version 1.0: Initial public release (May 16, 2000)
- Maintainer: Matthew P. Barnson (mbarnson@excitehome.net)
- ===
- Table Of Contents
- ===
- FOREWORD
- INTRODUCTION
- THE BASICS
- THE TABLES
- THE DETAILS
- ===
- FOREWORD
- ===
- This information comes straight from my life. I was forced to learn
- how
- Bugzilla organizes database because of nitpicky requests from users fo
- r 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.
- I'm sorry this version is plain text. I can whip this info out a lo
- t faster
- if I'm not concerned about complex formatting. I'll get it into sgml
- for easy
- portability as time permits.
- The Bugzilla Database Schema has a home! In addition to availabilit
- y via CVS
- and released versions 2.12 and higher of Bugzilla, you can find the la
- test &
- greatest version of the Bugzilla Database Schema at
- http://www.trilobyte.net/barnsons/. This is a living document; please
- be sure
- you are up-to-date with the latest version before mirroring.
- The Bugzilla Database Schema is designed to provide vital informatio
- n
- regarding the structure of the MySQL database. Where appropriate, thi
- s
- document will refer to URLs rather than including documents in their e
- ntirety
- to ensure completeness even should this paper become out of date.
- This document is not maintained by Netscape or Netscape employees, s
- o please
- do not contact them regarding errors or omissions contained herein. Pl
- ease
- direct all questions, comments, updates, flames, etc. to Matthew P. Ba
- rnson
- mbarnson@excitehome.net) (barnboy or barnhome on irc.mozilla.org in
- #mozwebtools).
- I'm sure I've made some glaring errors or omissions in this paper --
- please
- email me corrections or post corrections to the
- netscape.public.mozilla.webtools newsgroup.
- ===
- INTRODUCTION
- ===
- 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 da
- tabase
- flawlessly. Maybe you've even entered a few test bugs to make sure em
- ail's
- working; people seem to be notified of new bugs and changes, and you c
- an
- enter and edit bugs to your heart's content. Perhaps you've gone thro
- ugh the
- trouble of setting up a gateway for people to submit bugs to your data
- base via
- email, have had a few people test it, and received rave reviews from y
- our 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 too
- l you've
- labored over for hours.
- Your first training session starts off very well! You have a captiv
- e
- audience which seems enraptured by the efficiency embodied in this thi
- ng called
- "Bugzilla". You are caught up describing the nifty features, how peop
- le can
- save favorite queries in the database, set them up as headers and foot
- ers on
- their pages, customize their layouts, generate reports, track status w
- ith
- 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 o
- f the
- conference room. "I have a concern," the voice hisses from the darkne
- ss,
- "about the use of the word 'verified'.
- The room, previously filled with happy chatter, lapses into reverent
- ial
- silence as Certain Death (better known as the Vice President of Softwa
- re
- Engineering) continues. "You see, for two years we've used the word '
- verified'
- to indicate that a developer or quality assurance engineer has confirm
- ed 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 "ye
- s, yes, I
- don't think that would be a problem," You review the changes with Cert
- ain
- Death, and continue to jabber on, "no, it's not too big a change. I me
- an, 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 tinyin
- t
- definitions. The Adventure Awaits You!
- ===
- The 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 th
- e Vice
- President you couldn't care less about the difference between a "bigin
- t" and a
- "tinyint" entry in MySQL. I'd refer you first to the MySQL documentat
- ion,
- available at http://www.mysql.com/doc.html, but that's mostly a confus
- ing
- morass of high-level database jargon. Here are the basics you need to
- know
- about the database to proceed:
- 1. To connect to your database, type "mysql -u root" at the command p
- rompt as
- any user. If this works without asking you for a password, SHAME ON YO
- U! You
- should have locked your security down like the README told you to. Yo
- u can
- find details on locking down your database in the Bugzilla FAQ in this
- directory (under "Security"), or more robust security generalities in
- the
- MySQL searchable documentation at
- http://www.mysql.com/php/manual.php3?section=Privilege_system .
- 2. You should now be at a prompt that looks like this:
- mysql>
- At the prompt, if "bugs" is the name of your Bugzilla database, type:
- mysql> use bugs;
- (don't forget the ";" at the end of each line, or you'll be kicking yo
- urself
- all the way through this documentation)
- Young Grasshopper, you are now ready for the unveiling of the Bugzil
- la
- database, in the next section...
- ===
- THE TABLES
- ===
- 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;
- you'll be able to see all the "spreadsheets" (tables) in your database
- . Cool,
- huh? It's kinda' like a filesystem, only much faster and more robust.
- Come
- on, I'll show you more!
- From the command issued above, you should now have some output that
- looks
+ 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!
+ _________________________________________________________________
+
+C.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.
+
+ 1. To connect to your database:
+ bash#mysql-u root
+ If this works without asking you for a password, shame on you! 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 MySQL
+ searchable documentation at
+ http://www.mysql.com/php/manual.php3?section=Privilege_system .
+ 2. You should now be at a prompt that looks like this:
+ mysql>
+ At the prompt, if "bugs" is the name you chose in thelocalconfig
+ file for your Bugzilla database, type:
+ mysqluse bugs;
+
+ Note
+
+ Don't forget the ";" at the end of each line, or you'll be kicking
+ yourself later.
+ _________________________________________________________________
+
+C.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:
+
+ mysql>show tables from bugs;
+
+ you'll be able to see all the "spreadsheets" (tables) in your
+ database. It is similar to a file system, only faster and more robust
+ for certain types of operations.
+
+ From the command issued above, ou should have some output that looks
like this:
- +-------------------+
- | Tables in bugs |
- +-------------------+
- | attachments |
- | bugs |
- | bugs_activity |
- | cc |
- | components |
- | dependencies |
- | fielddefs |
- | groups |
- | keyworddefs |
- | keywords |
- | logincookies |
- | longdescs |
- | milestones |
- | namedqueries |
- | products |
- | profiles |
- | profiles_activity |
- | shadowlog |
- | versions |
- | votes |
- | watch |
- +-------------------+
- If it doesn't look quite the same, that probably means it's
- time to
- update this documentation :)
++-------------------+
+| 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 |
++-------------------+
+
Here's an overview of what each table does. Most columns in each ta
ble have
descriptive names that make it fairly trivial to figure out their jobs
@@ -4450,16 +5531,23 @@ C.2. MySQL Bugzilla Database Introduction
C.3. MySQL Permissions & Grant Tables
- Note: The following portion of documentation comes from my answer
- to an old discussion of Keystone, a cool product that does
- trouble-ticket tracking for IT departments. I wrote this post to
- the Keystone support group regarding MySQL grant table permissions,
- and how to use them effectively. It is badly in need of updating,
- as I believe MySQL has added a field or two to the grant tables
- since this time, but it serves as a decent introduction and
- troubleshooting document for grant table issues. I used Keynote to
- track my troubles until I discovered Bugzilla, which gave me a
- whole new set of troubles to work on : )
+ Note
+
+ The following portion of documentation comes from my answer to an old
+ discussion of Keystone, a cool product that does trouble-ticket
+ tracking for IT departments. I wrote this post to the Keystone support
+ group regarding MySQL grant table permissions, and how to use them
+ effectively. It is badly in need of updating, as I believe MySQL has
+ added a field or two to the grant tables since this time, but it
+ serves as a decent introduction and troubleshooting document for grant
+ table issues. I used Keynote to track my troubles until I discovered
+ Bugzilla, which gave me a whole new set of troubles to work on : )
+ Although it is of limited use, it still has SOME use, thus it's still
+ included.
+
+ Please note, however, that I was a relatively new user to MySQL at the
+ time. Some of my suggestions, particularly in how to set up security,
+ showed a terrible lack of security-related database experience.
From matt_barnson@singletrac.com Wed Jul 7 09:00:07 1999
Date: Mon, 1 Mar 1999 21:37:04 -0700
@@ -4636,118 +5724,35 @@ C.3. MySQL Permissions & Grant Tables
l. It
is more detailed than I!
http://www.mysql.com/Manual/manual.html.
- ----------------------------------------------------------------------
- ------
- 10/12/2000
- Matthew sent in some mail with updated contact information:
- NEW CONTACT INFORMATION:
- ------------------------
- Matthew P. Barnson
- Manager, Systems Administration
- Excite@Home Business Applications
- mbarnson@excitehome.net
- (801)234-8300
_________________________________________________________________
-C.4. Cleaning up after mucking with Bugzilla
+Appendix D. Useful Patches and Utilities for Bugzilla
- Contributed by Eric Hanson:
- There are several things, and one trick. There is a small tiny piece
- of
- documentation I saw once that said something very important.
- 1) After pretty much any manual working of the Mysql db, you must
- delete a file in the bugzilla directory: data/versioncache
- Versioncache basically is a way to speed up bugzilla (from what I
- understand). It stores a lot of commonly used information. However,
- this file is refreshed every so often (I can't remember the time
- interval though). So eventually all changes do propogate out, so you
- may see stuff suddenly working.
- 2) Assuming that failed, you will also have to check something with t
- he
- checksetup.pl file. It actually is run twice. The first time it
- creates the file: localconfig. You can modify localconfig, (or not if
- you are doing bug_status stuff) or you should delete localconfig and
- rerun your modified checksetup.pl. Since I don't actually see anythin
- g
- in localconfig pertaining to bug_status, this point is mainly a FYI.
+ Are you looking for a way to put your Bugzilla into overdrive? Catch
+ some of the niftiest tricks here in this section.
_________________________________________________________________
-Chapter 7. Bugzilla Variants
+D.1. Apache mod_rewrite magic
- Note: I know there are more variants than just RedHat Bugzilla out
- there. Please help me get information about them, their project
- status, and benefits there might be in using them or in using their
- code in main-tree Bugzilla.
- _________________________________________________________________
+ 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.
-7.1. Red Hat Bugzilla
+ 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
+ up your VirtualHost section for Bugzilla with a rule like this:
- Red Hat Bugzilla is probably the most popular Bugzilla variant, aside
- from Mozilla Bugzilla, on the planet. One of the major benefits of Red
- Hat Bugzilla is the ability to work with Oracle as a database, as well
- as MySQL. Here's what Dave Lawrence had to say about the status of Red
- Hat Bugzilla,
-
- Hello. I apologize that I am getting back to you so late. It has
- been difficult to keep
- up with email this past week. I have checked out your updated docum
- entation and I will
- have to say very good work. A few notes and additions as follows.
- (ed: from the FAQ)
- >For the record, we are not using any template type implementation
- for the cosmetic changes
- >maded to Bugzilla. It is just alot of html changes in the code its
- elf. I admit I may have
- >gotten a little carried away with it but the corporate types asked
- for a more standardized
- >interface to match up with other projects relating to Red Hat web
- sites. A lot of other web
- >based internal tools I am working on also look like Bugzilla.
- This should probably be changed since we are now in fact using Text
- ::Template for most
- of the html rendering. You actually state this later in your number
- ed list.
- Also number 6 contradicts number 8 where number 6 would be the most
- up to date status
- on the Oracle port.
- Additional Information:
- -----------------------------
- 1. Comments are now stored in varchar fields of 4k in size each. If
- the comment is more
- than 4k it is broken up into chunks and given a sort number so each
- comment can be re
- assembled in the correct order. This was done because originally I
- was storing the comments
- in a long datatype which unfortunately cannot be indexed or joined
- with another table. This
- cause the search of text within the long description to be disabled
- for a long time. That
- is now working and is nto showing any noticeble performance hit tha
- t I can tell.
- 2. Work is being started on internationalizing the Bugzilla source
- we have to allow our
- Japanese customers to enter bug reports into a single bugzilla syst
- em. This will probably
- be done by using the nvarchar data types supported by Oracle which
- allows storage of
- double byte characters and also the use of the Accept-Language in t
- he http header for
- detection by Bugilla of which language to render.
- 3. Of course even more cosmetic changes. It is difficult to keep up
- with the ever
- changing faces of www.redhat.com.
- 4. Some convenience enhancements in the administration utilities. A
- nd more integration
- with other internal/external Red Hat web sites.
- I hope this information may prove helpful for your documentation. P
- lease contact
- me if you have any more question or I can do anything else.
- Regards
- _________________________________________________________________
+<VirtualHost 12.34.56.78>
+RewriteEngine On
+RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R]
+</VirtualHost>
-Appendix D. Useful Patches and Utilities for Bugzilla
+ 2. There are many, many more things you can do with mod_rewrite. As
+ time goes on, I will include many more in the Guide. For now,
+ though, please refer to the mod_rewrite documentation at
+ http://www.apache.org
+ _________________________________________________________________
-D.1. The setperl.csh Utility
+D.2. The setperl.csh Utility
You can use the "setperl.csh" utility to quickly and easily change the
path to perl on all your Bugzilla files. This is a C-shell script; if
@@ -4770,7 +5775,7 @@ D.1. The setperl.csh Utility
bash# ./setperl.csh /usr/bin/perl
_________________________________________________________________
-D.2. Command-line Bugzilla Queries
+D.3. Command-line Bugzilla Queries
Users can query Bugzilla from the command line using this suite of
utilities.
@@ -4813,7 +5818,7 @@ D.2. Command-line Bugzilla Queries
2. Make your utilities executable: bash$ chmod u+x buglist bugs
_________________________________________________________________
-D.3. The Quicksearch Utility
+D.4. The Quicksearch Utility
Quicksearch is a new, experimental feature of the 2.12 release. It
consist of two Javascript files, "quicksearch.js" and
@@ -4844,6 +5849,109 @@ D.3. The Quicksearch Utility
has details.
_________________________________________________________________
+D.5. Hacking Bugzilla
+
+ What follows are some general guidelines for changing Bugzilla, and
+ adhering to good coding practice while doing so. We've had some
+ checkins in the past which ruined Bugzilla installations because of
+ disregard for these conventions. Sorry for the lack of formatting; I
+ got this info into the Guide on the day of 2.14 release and haven't
+ formatted it yet.
+
+ The following is a guide for reviewers when checking code into Bugzill
+ a's
+ CVS repostory at mozilla.org. If you wish to submit patches to Bugzil
+ la,
+ you should follow the rules and style conventions below. Any code tha
+ t
+ does not adhere to these basic rules will not be added to Bugzilla's
+ codebase.
+ 1. Usage of variables in Regular Expressions
+ It is very important that you don't use a variable in a regular
+ expression unless that variable is supposed to contain an expressi
+ on.
+ This especially applies when using grep. You should use:
+ grep ($_ eq $value, @array);
+ - NOT -
+ grep (/$value/, @array);
+ If you need to use a non-expression variable inside of an expressi
+ on, be
+ sure to quote it properly (using \Q..\E).
+ Coding Style for Bugzilla
+ -------------------------
+ While it's true that not all of the code currently in Bugzilla adheres
+ to
+ this styleguide, it is something that is being worked toward. Therefo
+ re,
+ we ask that all new code (submitted patches and new files) follow this
+ guide
+ as closely as possible (if you're only changing 1 or 2 lines, you don'
+ t have
+ to reformat the entire file :).
+ 1. Whitespace
+ Bugzilla's prefered indentation is 4 spaces (no tabs, please).
+ 2. Curly braces.
+ The opening brace of a block should be on the same line as the sta
+ tement
+ that is causing the block and the closing brace should be at the s
+ ame
+ indentation level as that statement, for example:
+ if ($var) {
+ print "The variable is true";
+ } else {
+ print "Try again";
+ }
+ - NOT -
+ if ($var)
+ {
+ print "The variable is true";
+ }
+ else
+ {
+ print "Try again";
+ }
+ 3. File Names
+ File names for bugzilla code and support documention should be leg
+ al across
+ multiple platforms. \ / : * ? " < > and | are all illegal charact
+ ers for
+ filenames on various platforms. Also, file names should not have
+ spaces in
+ them as they can cause confusion in CVS and other mozilla.org util
+ ities.
+ 4. Variable Names
+ If a variable is scoped globally ($::variable) its name should be
+ descriptive
+ of what it contains. Local variables can be named a bit looser, p
+ rovided the
+ context makes their content obvious. For example, $ret could be u
+ sed as a
+ staging variable for a routine's return value as the line |return
+ $ret;| will
+ make it blatently obvious what the variable holds and most likely
+ be shown
+ on the same screen as |my $ret = "";|.
+ 5. Cross Database Compatability
+ Bugzilla was originally written to work with MySQL and therefore t
+ ook advantage
+ of some of its features that aren't contained in other RDBMS softw
+ are. These
+ should be avoided in all new code. Examples of these features are
+ enums and
+ encrypt().
+ 6. Cross Platform Compatability
+ While Bugzilla was written to be used on Unix based systems (and U
+ nix/Linux is
+ still the only officially supported platform) there are many who d
+ esire/need to
+ run Bugzilla on Microsoft Windows boxes. Whenever possible, we sh
+ ould strive
+ not to make the lives of these people any more complicated and avo
+ id doing things
+ that break Bugzilla's ability to run on multiple operating systems
+ .
+ _________________________________________________________________
+
Appendix E. GNU Free Documentation License
Version 1.1, March 2000
@@ -5208,17 +6316,36 @@ How to use this License for your documents
Glossary
+0-9, high ascii
+
+ .htaccess
+ Apache web server, and other NCSA-compliant web servers,
+ observe the convention of using files in directories called
+ .htaccess files. These restrict parameters of the web server.
+ In Bugzilla, they are used to restrict access to certain files
+ which would otherwise compromise your installation. For
+ instance, the localconfig file contains the password to your
+ database. If this information were generally available, and
+ remote access to your database turned on, you risk corruption
+ of your database by computer criminals or the curious.
+
A
- There are no entries for A
+ Apache
+ In this context, Apache is the web server most commonly used
+ for serving up Bugzilla pages. Contrary to popular belief, the
+ apache web server has nothing to do with the ancient and noble
+ Native American tribe, but instead derived its name from the
+ fact that it was "a patchy" version of the original NCSA
+ world-wide-web server.
B
Bug
A "Bug" in Bugzilla refers to an issue entered into the
database which has an associated number, assignments, comments,
- etc. Many also refer to a "Ticket" or "Issue"; in this context,
- they are synonymous.
+ etc. Some also refer to a "tickets" or "issues"; in the context
+ of Bugzilla, they are synonymous.
Bug Number
Each Bugzilla Bug is assigned a number that uniquely identifies
@@ -5232,10 +6359,52 @@ B
verification. The "Bug Life Cycle" is moderately flexible
according to the needs of the organization using it, though.
+ Bugzilla
+ Bugzilla is the industry-standard bug tracking system. It is
+ quite popular among Open Source enthusiasts.
+
+ Component
+ A Component is a subsection of a Product. It should be a narrow
+ category, tailored to your organization. All Products must
+ contain at least one Component (and, as a matter of fact,
+ creating a Product with no Components will create an error in
+ Bugzilla).
+
+ CPAN
+ CPAN stands for the "Comprehensive Perl Archive Network". CPAN
+ maintains a large number of extremely useful Perl modules. By
+ themselves, Perl modules generally do nothing, but when used as
+ part of a larger program, they provide much-needed algorithms
+ and functionality.
+
+D
+
+ daemon
+ A daemon is a computer program which runs in the background. In
+ general, most daemons are started at boot time via System V
+ init scripts, or through RC scripts on BSD-based systems.
+ mysqld, the MySQL server, and apache, a web server, are
+ generally run as daemons.
+
+ Groups
+ The word "Groups" has a very special meaning to Bugzilla.
+ Bugzilla's main security mechanism comes by lumping users into
+ groups, and assigning those groups certain privileges to
+ Products and Components in the Bugzilla database.
+
I
Infinite Loop
- See: Recursion
+ A loop of information that never ends; see recursion.
+
+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.
P
@@ -5250,26 +6419,58 @@ P
A company sells a software product called "X". They also
maintain some older software called "Y", and have a secret
project "Z". An effective use of Products might be to create
- Products "X", "Y", and "Z", each with Components "User
- Interface", "Database", and "Business Logic". They might also
- change group permissions so that only those people who are
- members of Group "Z" can see components and bugs under Product
- "Z".
+ Products "X", "Y", "Z", each with Components of User Interface,
+ Database, and Business Logic. They might also change group
+ permissions so that only those people who are members of Group
+ "Z" can see components and bugs under Product "Z".
+
+ Perl
+ First written by Larry Wall, Perl is a remarkable program
+ language. It has the benefits of the flexibility of an
+ interpreted scripting language (such as shell script), combined
+ with the speed and power of a compiled language, such as C.
+ Bugzilla is maintained in Perl.
Q
- Q/A
- "Q/A" is short for "Quality Assurance". In most large software
- development organizations, there is a team devoted to ensuring
- the product meets minimum standards before shipping. This team
- will also generally want to track the progress of bugs over
- their life cycle, thus the need for the "Q/A Contact" field in
- a Bug.
+ QA
+ "QA", "Q/A", and "Q.A." are short for "Quality Assurance". In
+ most large software development organizations, there is a team
+ devoted to ensuring the product meets minimum standards before
+ shipping. This team will also generally want to track the
+ progress of bugs over their life cycle, thus the need for the
+ "QA Contact" field in a Bug.
R
Recursion
- See: Infinite Loop
+ The property of a function looking back at itself for
+ something. "GNU", for instance, stands for "GNU's Not UNIX",
+ thus recursing upon itself for definition. For further clarity,
+ see Infinite Loop.
+
+S
+
+ SGML
+ SGML stands for "Standard Generalized Markup Language". Created
+ in the 1980's to provide an extensible means to maintain
+ documentation based upon content instead of presentation, SGML
+ has withstood the test of time as a robust, powerful language.
+ XML is the "baby brother" of SGML; any valid XML document it,
+ by definition, a valid SGML document. The document you are
+ reading is written and maintained in SGML, and is also valid
+ XML if you modify the Document Type Definition.
+
+T
+
+ Target Milestone
+ Target Milestones are Product goals. They are configurable on a
+ per-Product basis. Most software development houses have a
+ concept of "milestones" where the people funding a project
+ expect certain functionality on certain dates. Bugzilla
+ facilitates meeting these milestones by giving you the ability
+ to declare by which milestone a bug will be fixed, or an
+ enhancement will be implemented.
Z
diff --git a/docs/txt/CVS/Entries b/docs/txt/CVS/Entries
index f189f5ea8..7392262c2 100644
--- a/docs/txt/CVS/Entries
+++ b/docs/txt/CVS/Entries
@@ -1,2 +1,2 @@
-/Bugzilla-Guide.txt/1.3/Wed Apr 25 07:38:24 2001//
+/Bugzilla-Guide.txt/1.8/Wed Aug 29 18:13:42 2001//TBUGZILLA-2_14
D
diff --git a/docs/txt/CVS/Tag b/docs/txt/CVS/Tag
new file mode 100644
index 000000000..c10f87310
--- /dev/null
+++ b/docs/txt/CVS/Tag
@@ -0,0 +1 @@
+NBUGZILLA-2_14
diff --git a/doeditparams.cgi b/doeditparams.cgi
index 148946fef..0ecd4be76 100755
--- a/doeditparams.cgi
+++ b/doeditparams.cgi
@@ -44,7 +44,7 @@ if (!UserInGroup("tweakparams")) {
}
-PutHeader("Saving new parameters", undef, undef, undef, 1);
+PutHeader("Saving new parameters");
foreach my $i (@::param_list) {
# print "Processing $i...<BR>\n";
@@ -67,7 +67,7 @@ foreach my $i (@::param_list) {
print "Changed $i.<br>\n";
# print "Old: '" . url_quote(Param($i)) . "'<BR>\n";
# print "New: '" . url_quote($::FORM{$i}) . "'<BR>\n";
- $::param{$i} = $::FORM{$i}
+ $::param{$i} = $::FORM{$i};
}
}
diff --git a/doeditvotes.cgi b/doeditvotes.cgi
index 7b830595a..75208ce35 100755
--- a/doeditvotes.cgi
+++ b/doeditvotes.cgi
@@ -19,17 +19,65 @@
# Rights Reserved.
#
# Contributor(s): Terry Weissman <terry@mozilla.org>
+# Christopher Aillon <christopher@aillon.com>
use diagnostics;
use strict;
require "CGI.pl";
+ConnectToDatabase();
+
confirm_login();
+######################################################################
+# Begin Data/Security Validation
+######################################################################
+
+# Build a list of bug IDs for which votes have been submitted. Votes
+# are submitted in form fields in which the field names are the bug
+# IDs and the field values are the number of votes.
+my @buglist = grep {/^[1-9][0-9]*$/} keys(%::FORM);
+
+# If no bugs are in the buglist, let's make sure the user gets notified
+# that their votes will get nuked if they continue.
+if (0 == @buglist) {
+ if (! defined $::FORM{'delete_all_votes'}) {
+ print "Content-type: text/html\n\n";
+ PutHeader("Remove your votes?");
+ print "<p>You are about to remove all of your bug votes. Are you sure you wish to remove your vote from every bug you've voted on?</p>";
+ print qq{<form action="doeditvotes.cgi" method="post">\n};
+ print qq{<p><input type="radio" name="delete_all_votes" value="1"> Yes</p>\n};
+ print qq{<p><input type="radio" name="delete_all_votes" value="0" checked="checked"> No</p>\n};
+ print qq{<p><a href="showvotes.cgi">Review your votes</a></p>\n};
+ print qq{<p><input type="submit" value="Submit"></p></form>\n};
+ PutFooter();
+ exit();
+ }
+ elsif ($::FORM{'delete_all_votes'} == 0) {
+ print "Location: showvotes.cgi\n\n";
+ exit();
+ }
+}
+
+# Call ValidateBugID on each bug ID to make sure it is a positive
+# integer representing an existing bug that the user is authorized
+# to access, and make sure the number of votes submitted is also
+# a non-negative integer (a series of digits not preceded by a
+# minus sign).
+foreach my $id (@buglist) {
+ ValidateBugID($id);
+ ($::FORM{$id} =~ /^\d+$/)
+ || DisplayError("Only use non-negative numbers for your bug votes.")
+ && exit;
+}
+
+######################################################################
+# End Data/Security Validation
+######################################################################
+
print "Content-type: text/html\n\n";
-ConnectToDatabase();
GetVersionTable();
my $who = DBNameToIdAndCheck($::COOKIE{'Bugzilla_login'});
@@ -43,60 +91,50 @@ if ( (! defined $who) || (!$who) ) {
exit();
}
-my @buglist = grep {/^\d+$/} keys(%::FORM);
-
-if (0 == @buglist) {
- PutHeader("Oops?");
- print "Something got confused. Please click <b>Back</b> and try again.";
- PutFooter();
- exit();
-}
-
-foreach my $id (@buglist) {
- $::FORM{$id} = trim($::FORM{$id});
- if ($::FORM{$id} !~ /\d+/ || $::FORM{$id} < 0) {
- PutHeader("Numbers only, please");
- print "Only use numeric values for your bug votes.\n";
- print "Please click <b>Back</b> and try again.<hr>\n";
- PutFooter();
- exit();
+# If the user is voting for bugs, make sure they aren't overstuffing
+# the ballot box.
+if (scalar(@buglist)) {
+ SendSQL("SELECT bugs.bug_id, bugs.product, products.maxvotesperbug " .
+ "FROM bugs, products " .
+ "WHERE products.product = bugs.product ".
+ " AND bugs.bug_id IN (" . join(", ", @buglist) . ")");
+
+ my %prodcount;
+
+ while (MoreSQLData()) {
+ my ($id, $prod, $max) = (FetchSQLData());
+ if (!defined $prodcount{$prod}) {
+ $prodcount{$prod} = 0;
+ }
+ $prodcount{$prod} += $::FORM{$id};
+ if ($::FORM{$id} > $max) {
+ PutHeader("Don't overstuff!", "Illegal vote");
+ print "You may only use at most $max votes for a single bug in the\n";
+ print "<tt>$prod</tt> product, but you are using $::FORM{$id}.\n";
+ print "<P>Please click <b>Back</b> and try again.<hr>\n";
+ PutFooter();
+ exit();
+ }
}
-}
-
-SendSQL("SELECT bugs.bug_id, bugs.product, products.maxvotesperbug " .
- "FROM bugs, products " .
- "WHERE products.product = bugs.product ".
- " AND bugs.bug_id IN (" . join(", ", @buglist) . ")");
-
-my %prodcount;
-while (MoreSQLData()) {
- my ($id, $prod, $max) = (FetchSQLData());
- if (!defined $prodcount{$prod}) {
- $prodcount{$prod} = 0;
- }
- $prodcount{$prod} += $::FORM{$id};
- if ($::FORM{$id} > $max) {
- PutHeader("Don't overstuff!", "Illegal vote");
- print "You may only use at most $max votes for a single bug in the\n";
- print "<tt>$prod</tt> product, but you are using $::FORM{$id}.\n";
- print "<P>Please click <b>Back</b> and try again.<hr>\n";
- PutFooter();
- exit();
- }
-}
-
-foreach my $prod (keys(%prodcount)) {
- if ($prodcount{$prod} > $::prodmaxvotes{$prod}) {
- PutHeader("Don't overstuff!", "Illegal vote");
- print "You may only use $::prodmaxvotes{$prod} votes for bugs in the\n";
- print "<tt>$prod</tt> product, but you are using $prodcount{$prod}.\n";
- print "<P>Please click <b>Back</b> and try again.<hr>\n";
- PutFooter();
- exit();
+ foreach my $prod (keys(%prodcount)) {
+ if ($prodcount{$prod} > $::prodmaxvotes{$prod}) {
+ PutHeader("Don't overstuff!", "Illegal vote");
+ print "You may only use $::prodmaxvotes{$prod} votes for bugs in the\n";
+ print "<tt>$prod</tt> product, but you are using $prodcount{$prod}.\n";
+ print "<P>Please click <b>Back</b> and try again.<hr>\n";
+ PutFooter();
+ exit();
+ }
}
}
+# Update the user's votes in the database. If the user did not submit
+# any votes, they may be using a form with checkboxes to remove all their
+# votes (checkboxes are not submitted along with other form data when
+# they are not checked, and Bugzilla uses them to represent single votes
+# for products that only allow one vote per bug). In that case, we still
+# need to clear the user's votes from the database.
my %affected;
SendSQL("lock tables bugs write, votes write");
SendSQL("select bug_id from votes where who = $who");
diff --git a/duplicates.cgi b/duplicates.cgi
index 9eeff20fd..d1640cbf6 100644
--- a/duplicates.cgi
+++ b/duplicates.cgi
@@ -86,7 +86,7 @@ else
}
else
{
- &die_politely("There are no duplicate statistics for today or yesterday.");
+ &die_politely("There are no duplicate statistics for today ($today) or yesterday.");
}
}
@@ -115,25 +115,10 @@ if (<data/duplicates/dupes$before*>)
print Param("mostfreqhtml");
-print "
-<table BORDER>
-<tr BGCOLOR=\"#CCCCCC\">
-
-<td><center><b>
-<a href=\"duplicates.cgi?sortby=bug_no&maxrows=$maxrows&changedsince=$changedsince\">Bug #</a>
-</b></center></td>
-<td><center><b>
-<a href=\"duplicates.cgi?sortby=dup_count&maxrows=$maxrows&changedsince=$changedsince\">Dupe<br>Count</a>
-</b></center></td>\n";
-
my %delta;
if ($dobefore)
{
- print "<td><center><b>
- <a href=\"duplicates.cgi?sortby=delta&maxrows=$maxrows&changedsince=$changedsince\">Change in
- last<br>$changedsince day(s)</a></b></center></td>";
-
# Calculate the deltas if we are doing a "before"
foreach (keys(%count))
{
@@ -141,14 +126,6 @@ if ($dobefore)
}
}
-print "
-<td><center><b>Component</b></center></td>
-<td><center><b>Severity</b></center></td>
-<td><center><b>Op Sys</b></center></td>
-<td><center><b>Target<br>Milestone</b></center></td>
-<td><center><b>Summary</b></center></td>
-</tr>\n\n";
-
# Sort, if required
my @sortedcount;
@@ -158,7 +135,7 @@ if ($sortby eq "delta")
}
elsif ($sortby eq "bug_no")
{
- @sortedcount = sort by_bug_no keys(%count);
+ @sortedcount = reverse sort by_bug_no keys(%count);
}
elsif ($sortby eq "dup_count")
{
@@ -167,30 +144,94 @@ elsif ($sortby eq "dup_count")
my $i = 0;
+# Produce a string of bug numbers for a Bugzilla buglist.
+my $commabugs = "";
+foreach (@sortedcount)
+{
+ last if ($i == $maxrows);
+
+ $commabugs .= ($_ . ",");
+ $i++;
+}
+
+# Avoid having a comma at the end - Bad Things happen.
+chop $commabugs;
+
+print qq|
+
+<form method="POST" action="buglist.cgi">
+<input type="hidden" name="bug_id" value="$commabugs">
+<input type="hidden" name="order" value="Reuse same sort as last time">
+Give this to me as a <input type="submit" value="Bug List">. (Note: the order may not be the same.)
+</form>
+
+<table BORDER>
+<tr BGCOLOR="#CCCCCC">
+
+<td><center><b>
+<a href="duplicates.cgi?sortby=bug_no&maxrows=$maxrows&changedsince=$changedsince">Bug #</a>
+</b></center></td>
+<td><center><b>
+<a href="duplicates.cgi?sortby=dup_count&maxrows=$maxrows&changedsince=$changedsince">Dupe<br>Count</a>
+</b></center></td>\n|;
+
+if ($dobefore)
+{
+ print "<td><center><b>
+ <a href=\"duplicates.cgi?sortby=delta&maxrows=$maxrows&changedsince=$changedsince\">Change in
+ last<br>$changedsince day(s)</a></b></center></td>";
+}
+
+print "
+<td><center><b>Component</b></center></td>
+<td><center><b>Severity</b></center></td>
+<td><center><b>Op Sys</b></center></td>
+<td><center><b>Target<br>Milestone</b></center></td>
+<td><center><b>Summary</b></center></td>
+</tr>\n\n";
+
+$i = 0;
+
foreach (@sortedcount)
{
my $id = $_;
- SendSQL("SELECT component, bug_severity, op_sys, target_milestone, short_desc, groupset " .
+ SendSQL("SELECT component, bug_severity, op_sys, target_milestone, short_desc, groupset, bug_status, resolution" .
" FROM bugs WHERE bug_id = $id");
- my ($component, $severity, $op_sys, $milestone, $summary, $groupset) = FetchSQLData();
- next unless $groupset == 0;
- $summary = html_quote($summary);
- print "<tr>";
- print '<td><center><A HREF="show_bug.cgi?id=' . $id . '">';
- print $id . "</A></center></td>";
- print "<td><center>$count{$id}</center></td>";
- if ($dobefore)
- {
- print "<td><center>$delta{$id}</center></td>";
+ my ($component, $severity, $op_sys, $milestone, $summary, $groupset, $bug_status, $resolution) = FetchSQLData();
+ next unless $groupset == 0;
+ $summary = html_quote($summary);
+
+ # Show all bugs except those CLOSED _OR_ VERIFIED but not INVALID or WONTFIX.
+ # We want to see VERIFIED INVALID and WONTFIX because common "bugs" which aren't
+ # bugs end up in this state.
+ unless ( ($bug_status eq "CLOSED") || ( ($bug_status eq "VERIFIED") &&
+ ! ( ($resolution eq "INVALID") || ($resolution eq "WONTFIX") ) ) ) {
+ print "<tr>";
+ print '<td><center>';
+ if ( ($bug_status eq "RESOLVED") || ($bug_status eq "VERIFIED") ) {
+ print "<strike>";
+ }
+ print "<A HREF=\"show_bug.cgi?id=" . $id . "\">";
+ print $id . "</A>";
+ if ( ($bug_status eq "RESOLVED") || ($bug_status eq "VERIFIED") ) {
+ print "</strike>";
+ }
+ print "</center></td>";
+ print "<td><center>$count{$id}</center></td>";
+ if ($dobefore)
+ {
+ print "<td><center>$delta{$id}</center></td>";
+ }
+ print "<td>$component</td>\n ";
+ print "<td><center>$severity</center></td>";
+ print "<td><center>$op_sys</center></td>";
+ print "<td><center>$milestone</center></td>";
+ print "<td>$summary</td>";
+ print "</tr>\n";
+
+ $i++;
}
- print "<td>$component</td>\n ";
- print "<td><center>$severity</center></td>";
- print "<td><center>$op_sys</center></td>";
- print "<td><center>$milestone</center></td>";
- print "<td>$summary</td>";
- print "</tr>\n";
-
- $i++;
+
if ($i == $maxrows)
{
last;
diff --git a/editcomponents.cgi b/editcomponents.cgi
index dcca05bba..30f9dd4ea 100755
--- a/editcomponents.cgi
+++ b/editcomponents.cgi
@@ -608,15 +608,11 @@ if ($action eq 'delete') {
while (MoreSQLData()) {
my $bugid = FetchOneColumn();
- my $query =
- $::db->query("DELETE FROM attachments WHERE bug_id=$bugid")
- or die "$::db_errstr";
- $query =
- $::db->query("DELETE FROM bugs_activity WHERE bug_id=$bugid")
- or die "$::db_errstr";
- $query =
- $::db->query("DELETE FROM dependencies WHERE blocked=$bugid")
- or die "$::db_errstr";
+ PushGlobalSQLState();
+ SendSQL("DELETE FROM attachments WHERE bug_id=$bugid");
+ SendSQL("DELETE FROM bugs_activity WHERE bug_id=$bugid");
+ SendSQL("DELETE FROM dependencies WHERE blocked=$bugid");
+ PopGlobalSQLState();
}
print "Attachments, bug activity and dependencies deleted.<BR>\n";
diff --git a/editgroups.cgi b/editgroups.cgi
index 79d448c47..1626fc3a4 100755
--- a/editgroups.cgi
+++ b/editgroups.cgi
@@ -19,6 +19,7 @@
# Rights Reserved.
#
# Contributor(s): Dave Miller <justdave@syndicomm.com>
+# Jake Steenhagen <jake@acutexx.net>
# Code derived from editowners.cgi and editusers.cgi
@@ -104,16 +105,17 @@ unless ($action) {
print "<th>Name</th>";
print "<th>Description</th>";
print "<th>User RegExp</th>";
+ print "<th>Active</th>";
print "<th>Action</th>";
print "</tr>\n";
- SendSQL("SELECT bit,name,description,userregexp " .
+ SendSQL("SELECT bit,name,description,userregexp,isactive " .
"FROM groups " .
"WHERE isbuggroup != 0 " .
"ORDER BY bit");
while (MoreSQLData()) {
- my ($bit, $name, $desc, $regexp) = FetchSQLData();
+ my ($bit, $name, $desc, $regexp, $isactive) = FetchSQLData();
print "<tr>\n";
print "<td valign=middle>$bit</td>\n";
print "<td><input size=20 name=\"name-$bit\" value=\"$name\">\n";
@@ -122,18 +124,19 @@ unless ($action) {
print "<input type=hidden name=\"olddesc-$bit\" value=\"$desc\"></td>\n";
print "<td><input size=30 name=\"regexp-$bit\" value=\"$regexp\">\n";
print "<input type=hidden name=\"oldregexp-$bit\" value=\"$regexp\"></td>\n";
+ print "<td><input type=\"checkbox\" name=\"isactive-$bit\" value=\"1\"" . ($isactive ? " checked" : "") . ">\n";
+ print "<input type=hidden name=\"oldisactive-$bit\" value=\"$isactive\"></td>\n";
print "<td align=center valign=middle><a href=\"editgroups.cgi?action=del&group=$bit\">Delete</a></td>\n";
print "</tr>\n";
}
print "<tr>\n";
- print "<td colspan=4></td>\n";
+ print "<td colspan=5></td>\n";
print "<td><a href=\"editgroups.cgi?action=add\">Add Group</a></td>\n";
print "</tr>\n";
print "</table>\n";
print "<input type=hidden name=\"action\" value=\"update\">";
print "<input type=submit value=\"Submit changes\">\n";
- print "</form>\n";
print "<p>";
print "<b>Name</b> is what is used with the UserInGroup() function in any
@@ -146,32 +149,47 @@ to others in the same group.<p>";
print "<b>User RegExp</b> is optional, and if filled in, will automatically
grant membership to this group to anyone creating a new account with an
email address that matches this regular expression.<p>";
+ print "The <b>Active</b> flag determines whether or not the group is active.
+If you deactivate a group it will no longer be possible for users to add bugs
+to that group, although bugs already in the group will remain in the group.
+Deactivating a group is a much less drastic way to stop a group from growing
+than deleting the group would be.<p>";
print "In addition, the following groups that determine user privileges
-exist. You can not edit these, but you need to know they are here, because
-you can't duplicate the Names of any of them in your user groups either.<p>";
+exist. You can only edit the User rexexp on these groups. You should also take
+care not to duplicate the Names of any of them in your user groups.<p>";
+ print "Also please note that both of the Submit Changes buttons on this page
+will submit the changes in both tables. There are two buttons simply for the
+sake of convience.<p>";
print "<table border=1>\n";
print "<tr>";
print "<th>Bit</th>";
print "<th>Name</th>";
print "<th>Description</th>";
+ print "<th>User RegExp</th>";
print "</tr>\n";
- SendSQL("SELECT bit,name,description " .
+ SendSQL("SELECT bit,name,description,userregexp " .
"FROM groups " .
"WHERE isbuggroup = 0 " .
"ORDER BY bit");
while (MoreSQLData()) {
- my ($bit, $name, $desc) = FetchSQLData();
+ my ($bit, $name, $desc, $regexp) = FetchSQLData();
print "<tr>\n";
print "<td>$bit</td>\n";
print "<td>$name</td>\n";
+ print "<input type=hidden name=\"name-$bit\" value=\"$name\">\n";
+ print "<input type=hidden name=\"oldname-$bit\" value=\"$name\">\n";
print "<td>$desc</td>\n";
+ print "<td><input type=text size=30 name=\"regexp-$bit\" value=\"$regexp\"></td>\n";
+ print "<input type=hidden name=\"oldregexp-$bit\" value=\"$regexp\">\n";
print "</tr>\n";
}
print "</table><p>\n";
+ print "<input type=submit value=\"Submit changes\">\n";
+ print "</form>\n";
PutFooter();
exit;
@@ -191,10 +209,12 @@ if ($action eq 'add') {
print "<th>New Name</th>";
print "<th>New Description</th>";
print "<th>New User RegExp</th>";
+ print "<th>Active</th>";
print "</tr><tr>";
print "<td><input size=20 name=\"name\"></td>\n";
print "<td><input size=40 name=\"desc\"></td>\n";
print "<td><input size=30 name=\"regexp\"></td>\n";
+ print "<td><input type=\"checkbox\" name=\"isactive\" value=\"1\" checked></td>\n";
print "</TR></TABLE>\n<HR>\n";
print "<INPUT TYPE=SUBMIT VALUE=\"Add\">\n";
print "<INPUT TYPE=HIDDEN NAME=\"action\" VALUE=\"new\">\n";
@@ -208,6 +228,12 @@ may not contain any spaces.<p>";
print "<b>Description</b> is what will be shown in the bug reports to
members of the group where they can choose whether the bug will be restricted
to others in the same group.<p>";
+ print "The <b>Active</b> flag determines whether or not the group is active.
+If you deactivate a group it will no longer be possible for users to add bugs
+to that group, although bugs already in the group will remain in the group.
+Deactivating a group is a much less drastic way to stop a group from growing
+than deleting the group would be. <b>Note: If you are creating a group, you
+probably want it to be active, in which case you should leave this checked.</b><p>";
print "<b>User RegExp</b> is optional, and if filled in, will automatically
grant membership to this group to anyone creating a new account with an
email address that matches this regular expression.<p>";
@@ -229,6 +255,10 @@ if ($action eq 'new') {
my $name = trim($::FORM{name} || '');
my $desc = trim($::FORM{desc} || '');
my $regexp = trim($::FORM{regexp} || '');
+ # convert an undefined value in the inactive field to zero
+ # (this occurs when the inactive checkbox is not checked
+ # and the browser does not send the field to the server)
+ my $isactive = $::FORM{isactive} || 0;
unless ($name) {
ShowError("You must enter a name for the new group.<BR>" .
@@ -249,6 +279,14 @@ if ($action eq 'new') {
exit;
}
+ if ($isactive != 0 && $isactive != 1) {
+ ShowError("The active flag was improperly set. There may be " .
+ "a problem with Bugzilla or a bug in your browser.<br>" .
+ "Please click the <b>Back</b> button and try again.");
+ PutFooter();
+ exit;
+ }
+
# Major hack for bit values... perl can't handle 64-bit ints, so I can't
# just do the math to get the next available bit number, gotta handle
# them as strings... also, we're actually only going to allow 63 bits
@@ -294,13 +332,14 @@ if ($action eq 'new') {
# Add the new group
SendSQL("INSERT INTO groups ( " .
- "bit, name, description, isbuggroup, userregexp" .
+ "bit, name, description, isbuggroup, userregexp, isactive" .
" ) VALUES ( " .
$bit . "," .
SqlQuote($name) . "," .
SqlQuote($desc) . "," .
"1," .
- SqlQuote($regexp) . ")" );
+ SqlQuote($regexp) . "," .
+ $isactive . ")" );
print "OK, done.<p>\n";
print "Your new group was assigned bit #$bit.<p>";
@@ -523,10 +562,18 @@ if ($action eq 'update') {
SendSQL("SELECT name FROM groups WHERE name=" .
SqlQuote($::FORM{"name-$v"}));
if (!FetchOneColumn()) {
- SendSQL("UPDATE groups SET name=" .
- SqlQuote($::FORM{"name-$v"}) .
- " WHERE bit=" . SqlQuote($v));
- print "Group $v name updated.<br>\n";
+ SendSQL("SELECT name FROM groups WHERE name=" .
+ SqlQuote($::FORM{"oldname-$v"}) .
+ " && isbuggroup = 0");
+ if (FetchOneColumn()) {
+ ShowError("You cannot update the name of a " .
+ "system group. Skipping $v");
+ } else {
+ SendSQL("UPDATE groups SET name=" .
+ SqlQuote($::FORM{"name-$v"}) .
+ " WHERE bit=" . SqlQuote($v));
+ print "Group $v name updated.<br>\n";
+ }
} else {
ShowError("Duplicate name '" . $::FORM{"name-$v"} .
"' specified for group $v.<BR>" .
@@ -555,6 +602,23 @@ if ($action eq 'update') {
" WHERE bit=" . SqlQuote($v));
print "Group $v user regexp updated.<br>\n";
}
+ # convert an undefined value in the inactive field to zero
+ # (this occurs when the inactive checkbox is not checked
+ # and the browser does not send the field to the server)
+ my $isactive = $::FORM{"isactive-$v"} || 0;
+ if ($::FORM{"oldisactive-$v"} != $isactive) {
+ $chgs = 1;
+ if ($isactive == 0 || $isactive == 1) {
+ SendSQL("UPDATE groups SET isactive=$isactive" .
+ " WHERE bit=" . SqlQuote($v));
+ print "Group $v active flag updated.<br>\n";
+ } else {
+ ShowError("The value '" . $isactive .
+ "' is not a valid value for the active flag.<BR>" .
+ "There may be a problem with Bugzilla or a bug in your browser.<br>" .
+ "Update of active flag for group $v skipped.");
+ }
+ }
}
}
if (!$chgs) {
diff --git a/editmilestones.cgi b/editmilestones.cgi
index 57fe78830..4ceda927a 100755
--- a/editmilestones.cgi
+++ b/editmilestones.cgi
@@ -425,15 +425,11 @@ if ($action eq 'delete') {
while (MoreSQLData()) {
my $bugid = FetchOneColumn();
- my $query =
- $::db->query("DELETE FROM attachments WHERE bug_id=$bugid")
- or die "$::db_errstr";
- $query =
- $::db->query("DELETE FROM bugs_activity WHERE bug_id=$bugid")
- or die "$::db_errstr";
- $query =
- $::db->query("DELETE FROM dependencies WHERE blocked=$bugid")
- or die "$::db_errstr";
+ PushGlobalSQLState();
+ SendSQL("DELETE FROM attachments WHERE bug_id=$bugid");
+ SendSQL("DELETE FROM bugs_activity WHERE bug_id=$bugid");
+ SendSQL("DELETE FROM dependencies WHERE blocked=$bugid");
+ PopGlobalSQLState();
}
print "Attachments, bug activity and dependencies deleted.<BR>\n";
diff --git a/editparams.cgi b/editparams.cgi
index 91ddca7f9..e416184f6 100755
--- a/editparams.cgi
+++ b/editparams.cgi
@@ -44,7 +44,7 @@ if (!UserInGroup("tweakparams")) {
-PutHeader("Edit parameters", undef, undef, undef, 1);
+PutHeader("Edit parameters");
print "This lets you edit the basic operating parameters of bugzilla.\n";
print "Be careful!\n";
diff --git a/editproducts.cgi b/editproducts.cgi
index f5486f37b..73fdbf487 100755
--- a/editproducts.cgi
+++ b/editproducts.cgi
@@ -599,15 +599,11 @@ if ($action eq 'delete') {
while (MoreSQLData()) {
my $bugid = FetchOneColumn();
- my $query =
- $::db->do("DELETE FROM attachments WHERE bug_id=$bugid")
- or die "$::db_errstr";
- $query =
- $::db->do("DELETE FROM bugs_activity WHERE bug_id=$bugid")
- or die "$::db_errstr";
- $query =
- $::db->do("DELETE FROM dependencies WHERE blocked=$bugid")
- or die "$::db_errstr";
+ PushGlobalSQLState();
+ SendSQL("DELETE FROM attachments WHERE bug_id=$bugid");
+ SendSQL("DELETE FROM bugs_activity WHERE bug_id=$bugid");
+ SendSQL("DELETE FROM dependencies WHERE blocked=$bugid");
+ PopGlobalSQLState();
}
print "Attachments, bug activity and dependencies deleted.<BR>\n";
diff --git a/editusers.cgi b/editusers.cgi
index 3fe7ccb8b..48dcfa0c1 100755
--- a/editusers.cgi
+++ b/editusers.cgi
@@ -97,10 +97,9 @@ sub EmitElement ($$)
# Displays the form to edit a user parameters
#
-sub EmitFormElements ($$$$$$$$)
+sub EmitFormElements ($$$$$)
{
- my ($user, $password, $realname, $groupset, $blessgroupset,
- $emailnotification, $disabledtext, $newemailtech) = @_;
+ my ($user, $realname, $groupset, $blessgroupset, $disabledtext) = @_;
print " <TH ALIGN=\"right\">Login name:</TH>\n";
EmitElement("user", $user);
@@ -115,29 +114,14 @@ sub EmitFormElements ($$$$$$$$)
if(Param('useLDAP')) {
print " <TD><FONT COLOR=RED>This site is using LDAP for authentication!</FONT></TD>\n";
} else {
- print " <TD><INPUT TYPE=\"PASSWORD\" SIZE=16 MAXLENGTH=16 NAME=\"password\" VALUE=\"$password\"></TD>\n";
+ print qq|
+ <TD><INPUT TYPE="PASSWORD" SIZE="16" MAXLENGTH="16" NAME="password" VALUE=""><br>
+ (enter new password to change)
+ </TD>
+ |;
}
print "</TR><TR>\n";
- if (!$newemailtech) {
- print " <TH ALIGN=\"right\">Email notification:</TH>\n";
- print qq{<TD><SELECT NAME="emailnotification">};
- foreach my $i (["ExcludeSelfChanges",
- "All qualifying bugs except those which I change"],
- ["CConly",
- "Only those bugs which I am listed on the CC line"],
- ["All", "All qualifying bugs"]) {
- my ($tag, $desc) = (@$i);
- my $selectpart = "";
- if ($tag eq $emailnotification) {
- $selectpart = " SELECTED";
- }
- print qq{<OPTION$selectpart VALUE="$tag">$desc\n};
- }
- print "</SELECT></TD>\n";
- print "</TR><TR>\n";
- }
-
print " <TH ALIGN=\"right\">Disable text:</TH>\n";
print " <TD ROWSPAN=2><TEXTAREA NAME=\"disabledtext\" ROWS=10 COLS=60>" .
value_quote($disabledtext) . "</TEXTAREA>\n";
@@ -148,55 +132,63 @@ sub EmitFormElements ($$$$$$$$)
}
- SendSQL("SELECT bit,name,description,bit & $groupset != 0, " .
- " bit & $blessgroupset " .
- "FROM groups " .
- "WHERE bit & $opblessgroupset != 0 AND isbuggroup " .
- "ORDER BY name");
- print "</TR><TR><TH VALIGN=TOP ALIGN=RIGHT>Group Access:</TH><TD><TABLE><TR>";
- if (MoreSQLData()) {
- if ($editall) {
- print "<TD COLSPAN=3 ALIGN=LEFT><B>Can turn this bit on for other users</B></TD>\n";
- print "</TR><TR>\n<TD ALIGN=CENTER><B>|</B></TD>\n";
+ if($user ne "") {
+ print "</TR><TR><TH VALIGN=TOP ALIGN=RIGHT>Group Access:</TH><TD><TABLE><TR>";
+ SendSQL("SELECT bit,name,description,bit & $groupset != 0, " .
+ " bit & $blessgroupset " .
+ "FROM groups " .
+ "WHERE bit & $opblessgroupset != 0 AND isbuggroup " .
+ "ORDER BY name");
+ if (MoreSQLData()) {
+ if ($editall) {
+ print "<TD COLSPAN=3 ALIGN=LEFT><B>Can turn this bit on for other users</B></TD>\n";
+ print "</TR><TR>\n<TD ALIGN=CENTER><B>|</B></TD>\n";
+ }
+ print "<TD COLSPAN=2 ALIGN=LEFT><B>User is a member of these groups</B></TD>\n";
}
- print "<TD COLSPAN=2 ALIGN=LEFT><B>User is a member of these groups</B></TD>\n";
- }
- while (MoreSQLData()) {
- my ($bit,$name,$description,$checked,$blchecked) = FetchSQLData();
- print "</TR><TR>\n";
- if ($editall) {
- $blchecked = ($blchecked) ? "CHECKED" : "";
- print "<TD ALIGN=CENTER><INPUT TYPE=CHECKBOX NAME=\"blbit_$name\" $blchecked VALUE=\"$bit\"></TD>";
+ while (MoreSQLData()) {
+ my ($bit,$name,$description,$checked,$blchecked) = FetchSQLData();
+ print "</TR><TR>\n";
+ if ($editall) {
+ $blchecked = ($blchecked) ? "CHECKED" : "";
+ print "<TD ALIGN=CENTER><INPUT TYPE=CHECKBOX NAME=\"blbit_$name\" $blchecked VALUE=\"$bit\"></TD>";
+ }
+ $checked = ($checked) ? "CHECKED" : "";
+ print "<TD ALIGN=CENTER><INPUT TYPE=CHECKBOX NAME=\"bit_$name\" $checked VALUE=\"$bit\"></TD>";
+ print "<TD><B>" . ucfirst($name) . "</B>: $description</TD>\n";
}
- $checked = ($checked) ? "CHECKED" : "";
- print "<TD ALIGN=CENTER><INPUT TYPE=CHECKBOX NAME=\"bit_$name\" $checked VALUE=\"$bit\"></TD>";
- print "<TD><B>" . ucfirst($name) . "</B>: $description</TD>\n";
- }
- print "</TR></TABLE></TD>\n";
-
- SendSQL("SELECT bit,name,description,bit & $groupset != 0, " .
- " bit & $blessgroupset " .
- "FROM groups " .
- "WHERE bit & $opblessgroupset != 0 AND !isbuggroup " .
- "ORDER BY name");
- print "</TR><TR><TH VALIGN=TOP ALIGN=RIGHT>Privileges:</TH><TD><TABLE><TR>";
- if (MoreSQLData()) {
- if ($editall) {
- print "<TD COLSPAN=3 ALIGN=LEFT><B>Can turn this bit on for other users</B></TD>\n";
- print "</TR><TR>\n<TD ALIGN=CENTER><B>|</B></TD>\n";
+ print "</TR></TABLE></TD>\n";
+
+ print "</TR><TR><TH VALIGN=TOP ALIGN=RIGHT>Privileges:</TH><TD><TABLE><TR>";
+ SendSQL("SELECT bit,name,description,bit & $groupset != 0, " .
+ " bit & $blessgroupset " .
+ "FROM groups " .
+ "WHERE bit & $opblessgroupset != 0 AND !isbuggroup " .
+ "ORDER BY name");
+ if (MoreSQLData()) {
+ if ($editall) {
+ print "<TD COLSPAN=3 ALIGN=LEFT><B>Can turn this bit on for other users</B></TD>\n";
+ print "</TR><TR>\n<TD ALIGN=CENTER><B>|</B></TD>\n";
+ }
+ print "<TD COLSPAN=2 ALIGN=LEFT><B>User has these priveleges</B></TD>\n";
}
- print "<TD COLSPAN=2 ALIGN=LEFT><B>User has these priveleges</B></TD>\n";
- }
- while (MoreSQLData()) {
- my ($bit,$name,$description,$checked,$blchecked) = FetchSQLData();
- print "</TR><TR>\n";
- if ($editall) {
- $blchecked = ($blchecked) ? "CHECKED" : "";
- print "<TD ALIGN=CENTER><INPUT TYPE=CHECKBOX NAME=\"blbit_$name\" $blchecked VALUE=\"$bit\"></TD>";
+ while (MoreSQLData()) {
+ my ($bit,$name,$description,$checked,$blchecked) = FetchSQLData();
+ print "</TR><TR>\n";
+ if ($editall) {
+ $blchecked = ($blchecked) ? "CHECKED" : "";
+ print "<TD ALIGN=CENTER><INPUT TYPE=CHECKBOX NAME=\"blbit_$name\" $blchecked VALUE=\"$bit\"></TD>";
+ }
+ $checked = ($checked) ? "CHECKED" : "";
+ print "<TD ALIGN=CENTER><INPUT TYPE=CHECKBOX NAME=\"bit_$name\" $checked VALUE=\"$bit\"></TD>";
+ print "<TD><B>" . ucfirst($name) . "</B>: $description</TD>\n";
}
- $checked = ($checked) ? "CHECKED" : "";
- print "<TD ALIGN=CENTER><INPUT TYPE=CHECKBOX NAME=\"bit_$name\" $checked VALUE=\"$bit\"></TD>";
- print "<TD><B>" . ucfirst($name) . "</B>: $description</TD>\n";
+ } else {
+ print "</TR><TR><TH ALIGN=RIGHT>Groups and<br>Priveleges:</TH><TD><TABLE><TR>";
+ print "<TD COLSPAN=3>The new user will be inserted into groups " .
+ "based on their userregexps.<BR>To change the group " .
+ "permissions for this user, you must edit the account after ".
+ "creating it.</TD>\n";
}
print "</TR></TABLE></TD>\n";
@@ -397,7 +389,7 @@ if ($action eq 'add') {
print "<FORM METHOD=POST ACTION=editusers.cgi>\n";
print "<TABLE BORDER=0 CELLPADDING=4 CELLSPACING=0><TR>\n";
- EmitFormElements('', '', '', 0, 0, 'ExcludeSelfChanges', '', 1);
+ EmitFormElements('', '', 0, 0, '');
print "</TR></TABLE>\n<HR>\n";
print "<INPUT TYPE=SUBMIT VALUE=\"Add\">\n";
@@ -434,7 +426,10 @@ if ($action eq 'new') {
# Cleanups and valididy checks
my $realname = trim($::FORM{realname} || '');
- my $password = trim($::FORM{password} || '');
+ # We don't trim the password since that could falsely lead the user
+ # to believe a password with a space was accepted even though a space
+ # is an illegal character in a Bugzilla password.
+ my $password = $::FORM{'password'};
my $disabledtext = trim($::FORM{disabledtext} || '');
my $emailregexp = Param("emailregexp");
@@ -456,37 +451,57 @@ if ($action eq 'new') {
PutTrailer($localtrailer);
exit;
}
- if ($password !~ /^[a-zA-Z0-9-_]*$/ || length($password) < 3 || length($password) > 16) {
- print "The new user must have a password. The password must be between ",
- "3 and 16 characters long and must contain only numbers, letters, ",
- "hyphens and underlines. Press <b>Back</b> and try again.\n";
+ my $passworderror = ValidatePassword($password);
+ if ( $passworderror ) {
+ print $passworderror;
PutTrailer($localtrailer);
exit;
}
+ # For new users, we use the regexps from the groups table to determine
+ # their initial group membership.
+ # We also keep a list of groups the user was added to for display on the
+ # confirmation page.
my $bits = "0";
- foreach (keys %::FORM) {
- next unless /^bit_/;
- #print "$_=$::FORM{$_}<br>\n";
- $bits .= "+ $::FORM{$_}";
+ my @grouplist = ();
+ SendSQL("select bit, name, userregexp from groups where userregexp != ''");
+ while (MoreSQLData()) {
+ my @row = FetchSQLData();
+ if ($user =~ m/$row[2]/i) {
+ $bits .= "+ $row[0]"; # Silly hack to let MySQL do the math,
+ # not Perl, since we're dealing with 64
+ # bit ints here, and I don't *think* Perl
+ # does that.
+ push(@grouplist, $row[1]);
+ }
}
-
# Add the new user
SendSQL("INSERT INTO profiles ( " .
- "login_name, password, cryptpassword, realname, groupset, " .
+ "login_name, cryptpassword, realname, groupset, " .
"disabledtext" .
" ) VALUES ( " .
SqlQuote($user) . "," .
- SqlQuote($password) . "," .
- "encrypt(" . SqlQuote($password) . ")," .
+ SqlQuote(Crypt($password)) . "," .
SqlQuote($realname) . "," .
$bits . "," .
SqlQuote($disabledtext) . ")" );
#+++ send e-mail away
- print "OK, done.<p>\n";
+ print "OK, done.<br>\n";
+ if($#grouplist > -1) {
+ print "New user added to these groups based on group regexps:\n";
+ print "<ul>\n";
+ foreach (@grouplist) {
+ print "<li>$_</li>\n";
+ }
+ print "</ul>\n";
+ } else {
+ print "New user not added to any groups.<br><br>\n";
+ }
+ print "To change ${user}'s permissions, go back and <a href=\"editusers.cgi?action=edit&user=" . url_quote($user)."\">edit this user</A>";
+ print "<p>\n";
PutTrailer($localtrailer,
"<a href=\"editusers.cgi?action=add\">add</a> another user.");
exit;
@@ -515,10 +530,9 @@ if ($action eq 'del') {
CheckUser($user);
# display some data about the user
- SendSQL("SELECT realname, groupset, emailnotification, newemailtech
- FROM profiles
+ SendSQL("SELECT realname, groupset FROM profiles
WHERE login_name=" . SqlQuote($user));
- my ($realname, $groupset, $emailnotification, $newemailtech) =
+ my ($realname, $groupset) =
FetchSQLData();
$realname ||= "<FONT COLOR=\"red\">missing</FONT>";
@@ -535,27 +549,19 @@ if ($action eq 'del') {
print " <TD VALIGN=\"top\">Real name:</TD>\n";
print " <TD VALIGN=\"top\">$realname</TD>\n";
- if ( !$newemailtech ) {
- print "</TR><TR>\n";
- print " <TD VALIGN=\"top\">E-Mail notification:</TD>\n";
- print " <TD VALIGN=\"top\">$emailnotification</TD>\n";
- }
-
print "</TR><TR>\n";
print " <TD VALIGN=\"top\">Group set:</TD>\n";
print " <TD VALIGN=\"top\">";
- SendSQL("SELECT bit, name
+ SendSQL("SELECT name
FROM groups
- ORDER BY name");
+ WHERE bit & $groupset = bit
+ ORDER BY isbuggroup, name");
my $found = 0;
while ( MoreSQLData() ) {
- my ($bit,$name) = FetchSQLData();
- my $cmpr = $bit & $groupset;
- if ($cmpr) {
- print "<br>\n" if $found;
- print ucfirst $name;
- $found = 1;
- }
+ my ($name) = FetchSQLData();
+ print "<br>\n" if $found;
+ print ucfirst $name;
+ $found = 1;
}
print "none" unless $found;
print "</TD>\n</TR>";
@@ -680,32 +686,23 @@ if ($action eq 'edit') {
CheckUser($user);
# get data of user
- SendSQL("SELECT password, realname, groupset, blessgroupset,
- emailnotification, disabledtext, newemailtech
+ SendSQL("SELECT realname, groupset, blessgroupset, disabledtext
FROM profiles
WHERE login_name=" . SqlQuote($user));
- my ($password, $realname, $groupset, $blessgroupset, $emailnotification,
- $disabledtext, $newemailtech) = FetchSQLData();
+ my ($realname, $groupset, $blessgroupset,
+ $disabledtext) = FetchSQLData();
print "<FORM METHOD=POST ACTION=editusers.cgi>\n";
print "<TABLE BORDER=0 CELLPADDING=4 CELLSPACING=0><TR>\n";
- EmitFormElements($user, $password, $realname, $groupset, $blessgroupset,
- $emailnotification, $disabledtext, $newemailtech);
+ EmitFormElements($user, $realname, $groupset, $blessgroupset, $disabledtext);
print "</TR></TABLE>\n";
print "<INPUT TYPE=HIDDEN NAME=\"userold\" VALUE=\"$user\">\n";
- if ($editall && !Param('useLDAP')) {
- print "<INPUT TYPE=HIDDEN NAME=\"passwordold\" VALUE=\"$password\">\n";
- }
print "<INPUT TYPE=HIDDEN NAME=\"realnameold\" VALUE=\"$realname\">\n";
print "<INPUT TYPE=HIDDEN NAME=\"groupsetold\" VALUE=\"$groupset\">\n";
print "<INPUT TYPE=HIDDEN NAME=\"blessgroupsetold\" VALUE=\"$blessgroupset\">\n";
- if (!$newemailtech) {
- print "<INPUT TYPE=HIDDEN NAME=\"emailnotificationold\" " .
- "VALUE=\"$emailnotification\">\n";
- }
print "<INPUT TYPE=HIDDEN NAME=\"disabledtextold\" VALUE=\"" .
value_quote($disabledtext) . "\">\n";
print "<INPUT TYPE=HIDDEN NAME=\"action\" VALUE=\"update\">\n";
@@ -729,10 +726,7 @@ if ($action eq 'update') {
my $userold = trim($::FORM{userold} || '');
my $realname = trim($::FORM{realname} || '');
my $realnameold = trim($::FORM{realnameold} || '');
- my $password = trim($::FORM{password} || '');
- my $passwordold = trim($::FORM{passwordold} || '');
- my $emailnotification = trim($::FORM{emailnotification} || '');
- my $emailnotificationold = trim($::FORM{emailnotificationold} || '');
+ my $password = $::FORM{password} || '';
my $disabledtext = trim($::FORM{disabledtext} || '');
my $disabledtextold = trim($::FORM{disabledtextold} || '');
my $groupsetold = trim($::FORM{groupsetold} || '0');
@@ -796,20 +790,19 @@ if ($action eq 'update') {
print "Updated ability to tweak permissions of other users.\n";
}
- if ($editall && $emailnotification ne $emailnotificationold) {
- SendSQL("UPDATE profiles
- SET emailnotification=" . SqlQuote($emailnotification) . "
- WHERE login_name=" . SqlQuote($userold));
- print "Updated email notification.<BR>\n";
- }
- if(!Param('useLDAP')) {
- if ($editall && $password ne $passwordold) {
- my $q = SqlQuote($password);
- SendSQL("UPDATE profiles
- SET password= $q, cryptpassword = ENCRYPT($q)
- WHERE login_name=" . SqlQuote($userold));
- print "Updated password.<BR>\n";
- }
+ # Update the database with the user's new password if they changed it.
+ if ( !Param('useLDAP') && $editall && $password ) {
+ my $passworderror = ValidatePassword($password);
+ if ( !$passworderror ) {
+ my $cryptpassword = SqlQuote(Crypt($password));
+ my $loginname = SqlQuote($userold);
+ SendSQL("UPDATE profiles
+ SET cryptpassword = $cryptpassword
+ WHERE login_name = $loginname");
+ print "Updated password.<BR>\n";
+ } else {
+ print "Did not update password: $passworderror<br>\n";
+ }
}
if ($editall && $realname ne $realnameold) {
SendSQL("UPDATE profiles
diff --git a/editversions.cgi b/editversions.cgi
index 0efbc070b..0ca0b932c 100755
--- a/editversions.cgi
+++ b/editversions.cgi
@@ -436,15 +436,11 @@ if ($action eq 'delete') {
while (MoreSQLData()) {
my $bugid = FetchOneColumn();
- my $query =
- $::db->query("DELETE FROM attachments WHERE bug_id=$bugid")
- or die "$::db_errstr";
- $query =
- $::db->query("DELETE FROM bugs_activity WHERE bug_id=$bugid")
- or die "$::db_errstr";
- $query =
- $::db->query("DELETE FROM dependencies WHERE blocked=$bugid")
- or die "$::db_errstr";
+ PushGlobalSQLState();
+ SendSQL("DELETE FROM attachments WHERE bug_id=$bugid");
+ SendSQL("DELETE FROM bugs_activity WHERE bug_id=$bugid");
+ SendSQL("DELETE FROM dependencies WHERE blocked=$bugid");
+ PopGlobalSQLState();
}
print "Attachments, bug activity and dependencies deleted.<BR>\n";
diff --git a/enter_bug.cgi b/enter_bug.cgi
index 10c328e1b..91622590c 100755
--- a/enter_bug.cgi
+++ b/enter_bug.cgi
@@ -79,7 +79,18 @@ if (!defined $::FORM{'product'}) {
}
push(@prodlist, $p);
}
- if (1 != @prodlist) {
+ if (0 == @prodlist) {
+ print "Content-type: text/html\n\n";
+ PutHeader("No Products Available");
+
+ print "Either no products have been defined to enter bugs against ";
+ print "or you have not been given access to any. Please email ";
+ print "<A HREF=\"mailto:" . Param("maintainer") . "\">";
+ print Param("maintainer") . "</A> if you feel this is in error.<P>\n";
+
+ PutFooter();
+ exit;
+ } elsif (1 < @prodlist) {
print "Content-type: text/html\n\n";
PutHeader("Enter Bug");
@@ -87,20 +98,9 @@ if (!defined $::FORM{'product'}) {
print "a bug.</H2>\n";
print "<table>";
foreach my $p (@prodlist) {
- if (defined $::proddesc{$p} && $::proddesc{$p} eq '0') {
- # Special hack. If we stuffed a "0" into proddesc, that means
- # that disallownew was set for this bug, and so we don't want
- # to allow people to specify that product here.
- next;
- }
- if(Param("usebuggroupsentry")
- && GroupExists($p)
- && !UserInGroup($p)) {
- # If we're using bug groups to restrict entry on products, and
- # this product has a bug group, and the user is not in that
- # group, we don't want to include that product in this list.
- next;
- }
+# removed $::proddesc{$p} eq '0' check and UserInGroup($p) check from here
+# because it's redundant. See the foreach loop above that created @prodlist.
+# 1/13/01 - dave@intrec.com
print "<tr><th align=right valign=top><a href=\"enter_bug.cgi?product=" . url_quote($p) . "\">$p</a>:</th>\n";
if (defined $::proddesc{$p}) {
print "<td valign=top>$::proddesc{$p}</td>\n";
@@ -237,7 +237,7 @@ my $platform_popup = make_popup('rep_platform', \@::legal_platform,
pickplatform(), 0);
my $opsys_popup = make_popup('op_sys', \@::legal_opsys, pickos(), 0);
-if (0 == $::components{$product}) {
+if (0 == @{$::components{$product}}) {
print "<H1>Permission Denied</H1>\n";
print "Sorry. You need to have at least one component for this product\n";
print "in order to create a new bug. Go to the \"Components\" link to create\n";
@@ -408,11 +408,23 @@ print "
";
if ($::usergroupset ne '0') {
- SendSQL("SELECT bit, description FROM groups " .
+ SendSQL("SELECT bit, name, description FROM groups " .
"WHERE bit & $::usergroupset != 0 " .
- " AND isbuggroup != 0 ORDER BY description");
- while (MoreSQLData()) {
- my ($bit, $description) = (FetchSQLData());
+ " AND isbuggroup != 0 AND isactive = 1 ORDER BY description");
+ # We only print out a header bit for this section if there are any
+ # results.
+ my $groupFound = 0;
+ while (MoreSQLData()) {
+ my ($bit, $prodname, $description) = (FetchSQLData());
+ # Don't want to include product groups other than this product.
+ unless(($prodname eq $product) || (!defined($::proddesc{$prodname}))) {
+ next;
+ }
+ if(!$groupFound) {
+ print "<br><b>Only users in the selected groups can view this bug:</b><br>\n";
+ print "<font size=\"-1\">(Leave all boxes unchecked to make this a public bug.)</font><br><br>\n";
+ $groupFound = 1;
+ }
# Rather than waste time with another Param check and another database
# access, $group_bit will only have a non-zero value if we're using
# bug groups and have one for this product, so I'll check on that
@@ -421,21 +433,20 @@ if ($::usergroupset ne '0') {
# select-box patch. Also, if $group_bit is 0, it won't match the
# current group, either, so I'll compare it to the current bit
# instead of checking for non-zero. -DDM, 3/11/00
- my $check = 0; # default selection
- if($group_bit == $bit) {
- # In addition, we need to handle the possibility that we're coming
- # from a bookmark template. We'll simply check if we've got a
- # parameter called bit-# passed. If so, then we're coming from a
- # template, and we'll use the template value.
- $check = formvalue("bit-$bit","1");
+ # Modifying this to use checkboxes instead of a select list.
+ # -JMR, 5/11/01
+ # If this is the group for this product, make it checked.
+ my $check = ($group_bit == $bit);
+ # If this is a bookmarked template, then we only want to set the bit
+ # for those bits set in the template.
+ if(formvalue("maketemplate","") eq "Remember values as bookmarkable template") {
+ $check = formvalue("bit-$bit",0);
}
- print BuildPulldown("bit-$bit",
- [["0",
- "People not in the \"$description\" group can see this bug"],
- ["1",
- "Only people in the \"$description\" group can see this bug"]],
- $check);
- print "<BR>\n";
+ my $checked = $check ? " CHECKED" : "";
+ # indent these a bit
+ print " ";
+ print "<input type=checkbox name=\"bit-$bit\" value=1$checked>\n";
+ print "$description<br>\n";
}
}
diff --git a/globals.pl b/globals.pl
index 120fd7d9f..70f60da4b 100644
--- a/globals.pl
+++ b/globals.pl
@@ -31,6 +31,7 @@ use strict;
sub globals_pl_sillyness {
my $zz;
+ $zz = @main::SqlStateStack;
$zz = @main::chooseone;
$zz = @main::default_column_list;
$zz = $main::defaultqueryname;
@@ -48,6 +49,7 @@ sub globals_pl_sillyness {
$zz = @main::legal_versions;
$zz = @main::milestoneurl;
$zz = @main::prodmaxvotes;
+ $zz = $main::superusergroupset;
}
#
@@ -66,11 +68,14 @@ use DBI;
use Date::Format; # For time2str().
use Date::Parse; # For str2time().
-# use Carp; # for confess
+#use Carp; # for confess
use RelationSet;
+# $ENV{PATH} is not taint safe
+delete $ENV{PATH};
+
# Contains the version string for the current running Bugzilla.
-$::param{'version'} = '2.12';
+$::param{'version'} = '2.14';
$::dontchange = "--do_not_change--";
$::chooseone = "--Choose_one:--";
@@ -82,6 +87,13 @@ $::dbwritesallowed = 1;
# Joe Robins, 7/5/00
$::superusergroupset = "9223372036854775807";
+#sub die_with_dignity {
+# my ($err_msg) = @_;
+# print $err_msg;
+# confess($err_msg);
+#}
+#$::SIG{__DIE__} = \&die_with_dignity;
+
sub ConnectToDatabase {
my ($useshadow) = (@_);
if (!defined $::db) {
@@ -107,8 +119,28 @@ sub ReconnectToShadowDatabase {
my $shadowchanges = 0;
sub SyncAnyPendingShadowChanges {
if ($shadowchanges) {
- system("./syncshadowdb &");
- $shadowchanges = 0;
+ my $pid;
+ FORK: {
+ if ($pid = fork) { # create a fork
+ # parent code runs here
+ $shadowchanges = 0;
+ return;
+ } elsif (defined $pid) {
+ # child process code runs here
+ exec("./syncshadowdb","--") or die "Unable to exec syncshadowdb: $!";
+ # the idea was that passing the second parameter tricks it into
+ # using execvp instead of running a shell. Not really necessary since
+ # there are no shell meta-characters, but it passes our tinderbox
+ # test that way. :) http://bugzilla.mozilla.org/show_bug.cgi?id=21253
+ } elsif ($! =~ /No more process/) {
+ # recoverable fork error, try again in 5 seconds
+ sleep 5;
+ redo FORK;
+ } else {
+ # something weird went wrong
+ die "Can't create background process to run syncshadowdb: $!";
+ }
+ }
}
}
@@ -168,6 +200,15 @@ sub SendSQL {
if ($str =~ /^LOCK TABLES/i && $str !~ /shadowlog/ && $::dbwritesallowed) {
$str =~ s/^LOCK TABLES/LOCK TABLES shadowlog WRITE, /i;
}
+ # If we are shutdown, we don't want to run queries except in special cases
+ if (Param('shutdownhtml')) {
+ if ($0 =~ m:[\\/]((do)?editparams.cgi|syncshadowdb)$:) {
+ $::ignorequery = 0;
+ } else {
+ $::ignorequery = 1;
+ return;
+ }
+ }
SqlLog($str);
$::currentquery = $::db->prepare($str);
$::currentquery->execute
@@ -189,6 +230,10 @@ sub SendSQL {
}
sub MoreSQLData {
+ # $::ignorequery is set in SendSQL
+ if ($::ignorequery) {
+ return 0;
+ }
if (defined @::fetchahead) {
return 1;
}
@@ -199,6 +244,10 @@ sub MoreSQLData {
}
sub FetchSQLData {
+ # $::ignorequery is set in SendSQL
+ if ($::ignorequery) {
+ return;
+ }
if (defined @::fetchahead) {
my @result = @::fetchahead;
undef @::fetchahead;
@@ -479,7 +528,7 @@ sub GenerateVersionTable {
foreach my $i (@list) {
if (!defined $::components{$i}) {
- $::components{$i} = "";
+ $::components{$i} = [];
}
}
@::legal_versions = sort {uc($a) cmp uc($b)} keys(%varray);
@@ -559,7 +608,9 @@ sub ModTime {
# This proc must be called before using legal_product or the versions array.
+$::VersionTableLoaded = 0;
sub GetVersionTable {
+ return if $::VersionTableLoaded;
my $mtime = ModTime("data/versioncache");
if (!defined $mtime || $mtime eq "") {
$mtime = 0;
@@ -576,25 +627,27 @@ sub GetVersionTable {
die "Can't generate file data/versioncache";
}
}
+ $::VersionTableLoaded = 1;
}
sub InsertNewUser {
my ($username, $realname) = (@_);
- my $password = "";
- for (my $i=0 ; $i<8 ; $i++) {
- $password .= substr("abcdefghijklmnopqrstuvwxyz", int(rand(26)), 1);
- }
- my $usenewemailtech = Param('newemailtech') & Param('newemailtechdefault');
+ # Generate a new random password for the user.
+ my $password = GenerateRandomPassword();
+ my $cryptpassword = Crypt($password);
+
+ # Determine what groups the user should be in by default
+ # and add them to those groups.
PushGlobalSQLState();
SendSQL("select bit, userregexp from groups where userregexp != ''");
my $groupset = "0";
while (MoreSQLData()) {
my @row = FetchSQLData();
- # Modified -Joe Robins, 2/17/00
- # Making this case insensitive, since usernames are email addresses,
- # and could be any case.
+ # Modified -Joe Robins, 2/17/00
+ # Making this case insensitive, since usernames are email addresses,
+ # and could be any case.
if ($username =~ m/$row[1]/i) {
$groupset .= "+ $row[0]"; # Silly hack to let MySQL do the math,
# not Perl, since we're dealing with 64
@@ -602,14 +655,100 @@ sub InsertNewUser {
# does that.
}
}
-
+
+ # Insert the new user record into the database.
$username = SqlQuote($username);
$realname = SqlQuote($realname);
- SendSQL("insert into profiles (login_name, realname, password, cryptpassword, groupset, newemailtech) values ($username, $realname, '$password', encrypt('$password'), $groupset, $usenewemailtech)");
+ $cryptpassword = SqlQuote($cryptpassword);
+ SendSQL("INSERT INTO profiles (login_name, realname, cryptpassword, groupset)
+ VALUES ($username, $realname, $cryptpassword, $groupset)");
PopGlobalSQLState();
+
+ # Return the password to the calling code so it can be included
+ # in an email sent to the user.
+ return $password;
+}
+
+sub GenerateRandomPassword {
+ my ($size) = @_;
+
+ # Generated passwords are eight characters long by default.
+ $size ||= 8;
+
+ # The list of characters that can appear in a randomly generated password.
+ # Note that users can put any character into a password they choose themselves.
+ my @pwchars = (0..9, 'A'..'Z', 'a'..'z', '-', '_', '!', '@', '#', '$', '%', '^', '&', '*');
+
+ # The number of characters in the list.
+ my $pwcharslen = scalar(@pwchars);
+
+ # Generate the password.
+ my $password = "";
+ for ( my $i=0 ; $i<$size ; $i++ ) {
+ $password .= $pwchars[rand($pwcharslen)];
+ }
+
+ # Return the password.
return $password;
}
+
+sub ValidatePassword {
+ # Determines whether or not a password is valid (i.e. meets Bugzilla's
+ # requirements for length and content). If the password is valid, the
+ # function returns boolean false. Otherwise it returns an error message
+ # (synonymous with boolean true) that can be displayed to the user.
+
+ # If a second password is passed in, this function also verifies that
+ # the two passwords match.
+
+ my ($password, $matchpassword) = @_;
+
+ if ( length($password) < 3 ) {
+ return "The password is less than three characters long. It must be at least three characters.";
+ } elsif ( length($password) > 16 ) {
+ return "The password is more than 16 characters long. It must be no more than 16 characters.";
+ } elsif ( $matchpassword && $password ne $matchpassword ) {
+ return "The two passwords do not match.";
+ }
+
+ return 0;
+}
+
+
+sub Crypt {
+ # Crypts a password, generating a random salt to do it.
+ # Random salts are generated because the alternative is usually
+ # to use the first two characters of the password itself, and since
+ # the salt appears in plaintext at the beginning of the crypted
+ # password string this has the effect of revealing the first two
+ # characters of the password to anyone who views the crypted version.
+
+ my ($password) = @_;
+
+ # The list of characters that can appear in a salt. Salts and hashes
+ # are both encoded as a sequence of characters from a set containing
+ # 64 characters, each one of which represents 6 bits of the salt/hash.
+ # The encoding is similar to BASE64, the difference being that the
+ # BASE64 plus sign (+) is replaced with a forward slash (/).
+ my @saltchars = (0..9, 'A'..'Z', 'a'..'z', '.', '/');
+
+ # Generate the salt. We use an 8 character (48 bit) salt for maximum
+ # security on systems whose crypt uses MD5. Systems with older
+ # versions of crypt will just use the first two characters of the salt.
+ my $salt = '';
+ for ( my $i=0 ; $i < 8 ; ++$i ) {
+ $salt .= $saltchars[rand(64)];
+ }
+
+ # Crypt the password.
+ my $cryptedpassword = crypt($password, $salt);
+
+ # Return the crypted password.
+ return $cryptedpassword;
+}
+
+
sub DBID_to_real_or_loginname {
my ($id) = (@_);
PushGlobalSQLState();
@@ -625,6 +764,12 @@ sub DBID_to_real_or_loginname {
sub DBID_to_name {
my ($id) = (@_);
+ # $id should always be a positive integer
+ if ($id =~ m/^([1-9][0-9]*)$/) {
+ $id = $1;
+ } else {
+ $::cachedNameArray{$id} = "__UNKNOWN__";
+ }
if (!defined $::cachedNameArray{$id}) {
PushGlobalSQLState();
SendSQL("select login_name from profiles where userid = $id");
@@ -644,15 +789,18 @@ sub DBname_to_id {
SendSQL("select userid from profiles where login_name = @{[SqlQuote($name)]}");
my $r = FetchOneColumn();
PopGlobalSQLState();
- if (!defined $r || $r eq "") {
+ # $r should be a positive integer, this makes Taint mode happy
+ if (defined $r && $r =~ m/^([1-9][0-9]*)$/) {
+ return $1;
+ } else {
return 0;
}
- return $r;
}
sub DBNameToIdAndCheck {
my ($name, $forceok) = (@_);
+ $name = html_quote($name);
my $result = DBname_to_id($name);
if ($result > 0) {
return $result;
@@ -666,6 +814,7 @@ sub DBNameToIdAndCheck {
print "Yikes; couldn't create user $name. Please report problem to " .
Param("maintainer") ."\n";
} else {
+ print "\n"; # http://bugzilla.mozilla.org/show_bug.cgi?id=80045
print "The name <TT>$name</TT> is not a valid username. Either you\n";
print "misspelled it, or the person has not registered for a\n";
print "Bugzilla account.\n";
@@ -674,6 +823,18 @@ sub DBNameToIdAndCheck {
exit(0);
}
+# Use detaint_string() when you know that there is no way that the data
+# in a scalar can be tainted, but taint mode still bails on it.
+# WARNING!! Using this routine on data that really could be tainted
+# defeats the purpose of taint mode. It should only be
+# used on variables that cannot be touched by users.
+
+sub detaint_string {
+ my ($str) = @_;
+ $str =~ m/^(.*)$/s;
+ $str = $1;
+}
+
# This routine quoteUrls contains inspirations from the HTML::FromText CPAN
# module by Gareth Rees <garethr@cre.canon.co.uk>. It has been heavily hacked,
# all that is really recognizable from the original is bits of the regular
@@ -940,6 +1101,8 @@ sub SqlQuote {
# }
$str =~ s/([\\\'])/\\$1/g;
$str =~ s/\0/\\0/g;
+ # If it's been SqlQuote()ed, then it's safe, so we tell -T that.
+ $str = detaint_string($str);
return "'$str'";
}
@@ -959,6 +1122,16 @@ sub UserInGroup {
return 0;
}
+sub BugInGroup {
+ my ($bugid, $groupname) = (@_);
+ my $groupbit = GroupNameToBit($groupname);
+ PushGlobalSQLState();
+ SendSQL("SELECT (bugs.groupset & $groupbit) != 0 FROM bugs WHERE bugs.bug_id = $bugid");
+ my $bugingroup = FetchOneColumn();
+ PopGlobalSQLState();
+ return $bugingroup;
+}
+
sub GroupExists {
my ($groupname) = (@_);
ConnectToDatabase();
@@ -967,6 +1140,31 @@ sub GroupExists {
return $count;
}
+# Given the name of an existing group, returns the bit associated with it.
+# If the group does not exist, returns 0.
+# !!! Remove this function when the new group system is implemented!
+sub GroupNameToBit {
+ my ($groupname) = (@_);
+ ConnectToDatabase();
+ PushGlobalSQLState();
+ SendSQL("SELECT bit FROM groups WHERE name = " . SqlQuote($groupname));
+ my $bit = FetchOneColumn() || 0;
+ PopGlobalSQLState();
+ return $bit;
+}
+
+# Determines whether or not a group is active by checking
+# the "isactive" column for the group in the "groups" table.
+# Note: This function selects groups by bit rather than by name.
+sub GroupIsActive {
+ my ($groupbit) = (@_);
+ $groupbit ||= 0;
+ ConnectToDatabase();
+ SendSQL("select isactive from groups where bit=$groupbit");
+ my $isactive = FetchOneColumn();
+ return $isactive;
+}
+
# Determines if the given bug_status string represents an "Opened" bug. This
# routine ought to be paramaterizable somehow, as people tend to introduce
# new states into Bugzilla.
@@ -987,36 +1185,87 @@ sub RemoveVotes {
if ($who) {
$whopart = " AND votes.who = $who";
}
- SendSQL("SELECT profiles.login_name, votes.count " .
- "FROM votes, profiles " .
+ SendSQL("SELECT profiles.login_name, profiles.userid, votes.count, " .
+ "products.votesperuser, products.maxvotesperbug " .
+ "FROM profiles " .
+ "LEFT JOIN votes ON profiles.userid = votes.who " .
+ "LEFT JOIN bugs USING(bug_id) " .
+ "LEFT JOIN products USING(product)" .
"WHERE votes.bug_id = $id " .
- "AND profiles.userid = votes.who" .
$whopart);
my @list;
while (MoreSQLData()) {
- my ($name, $count) = (FetchSQLData());
- push(@list, [$name, $count]);
+ my ($name, $userid, $oldvotes, $votesperuser, $maxvotesperbug) = (FetchSQLData());
+ push(@list, [$name, $userid, $oldvotes, $votesperuser, $maxvotesperbug]);
}
if (0 < @list) {
foreach my $ref (@list) {
- my ($name, $count) = (@$ref);
+ my ($name, $userid, $oldvotes, $votesperuser, $maxvotesperbug) = (@$ref);
+ my $s;
+
+ $maxvotesperbug = $votesperuser if ($votesperuser < $maxvotesperbug);
+
+ # If this product allows voting and the user's votes are in
+ # the acceptable range, then don't do anything.
+ next if $votesperuser && $oldvotes <= $maxvotesperbug;
+
+ # If the user has more votes on this bug than this product
+ # allows, then reduce the number of votes so it fits
+ my $newvotes = $votesperuser ? $maxvotesperbug : 0;
+
+ my $removedvotes = $oldvotes - $newvotes;
+
+ $s = $oldvotes == 1 ? "" : "s";
+ my $oldvotestext = "You had $oldvotes vote$s on this bug.";
+
+ $s = $removedvotes == 1 ? "" : "s";
+ my $removedvotestext = "You had $removedvotes vote$s removed from this bug.";
+
+ my $newvotestext;
+ if ($newvotes) {
+ SendSQL("UPDATE votes SET count = $newvotes " .
+ "WHERE bug_id = $id AND who = $userid");
+ $s = $newvotes == 1 ? "" : "s";
+ $newvotestext = "You still have $newvotes vote$s on this bug."
+ } else {
+ SendSQL("DELETE FROM votes WHERE bug_id = $id AND who = $userid");
+ $newvotestext = "You have no more votes remaining on this bug.";
+ }
+
+ # Notice that we did not make sure that the user fit within the $votesperuser
+ # range. This is considered to be an acceptable alternative to losing votes
+ # during product moves. Then next time the user attempts to change their votes,
+ # they will be forced to fit within the $votesperuser limit.
+
+ # Now lets send the e-mail to alert the user to the fact that their votes have
+ # been reduced or removed.
my $sendmailparm = '-ODeliveryMode=deferred';
if (Param('sendmailnow')) {
$sendmailparm = '';
}
if (open(SENDMAIL, "|/usr/lib/sendmail $sendmailparm -t")) {
my %substs;
+
$substs{"to"} = $name;
$substs{"bugid"} = $id;
$substs{"reason"} = $reason;
- $substs{"count"} = $count;
+
+ $substs{"votesremoved"} = $removedvotes;
+ $substs{"votesold"} = $oldvotes;
+ $substs{"votesnew"} = $newvotes;
+
+ $substs{"votesremovedtext"} = $removedvotestext;
+ $substs{"votesoldtext"} = $oldvotestext;
+ $substs{"votesnewtext"} = $newvotestext;
+
+ $substs{"count"} = $removedvotes . "\n " . $newvotestext;
+
my $msg = PerformSubsts(Param("voteremovedmail"),
\%substs);
print SENDMAIL $msg;
close SENDMAIL;
}
}
- SendSQL("DELETE FROM votes WHERE bug_id = $id" . $whopart);
SendSQL("SELECT SUM(count) FROM votes WHERE bug_id = $id");
my $v = FetchOneColumn();
$v ||= 0;
@@ -1064,6 +1313,35 @@ sub Param ($) {
die "Can't find param named $value";
}
+# Take two comma or space separated strings and return what
+# values were removed from or added to the new one.
+sub DiffStrings {
+ my ($oldstr, $newstr) = @_;
+
+ # Split the old and new strings into arrays containing their values.
+ $oldstr =~ s/[\s,]+/ /g;
+ $newstr =~ s/[\s,]+/ /g;
+ my @old = split(" ", $oldstr);
+ my @new = split(" ", $newstr);
+
+ my (@remove, @add) = ();
+
+ # Find values that were removed
+ foreach my $value (@old) {
+ push (@remove, $value) if !grep($_ eq $value, @new);
+ }
+
+ # Find values that were added
+ foreach my $value (@new) {
+ push (@add, $value) if !grep($_ eq $value, @old);
+ }
+
+ my $removed = join (", ", @remove);
+ my $added = join (", ", @add);
+
+ return ($removed, $added);
+}
+
sub PerformSubsts {
my ($str, $substs) = (@_);
$str =~ s/%([a-z]*)%/(defined $substs->{$1} ? $substs->{$1} : Param($1))/eg;
diff --git a/importxml.pl b/importxml.pl
index b4b27b1e0..a11f116d9 100755
--- a/importxml.pl
+++ b/importxml.pl
@@ -46,10 +46,16 @@ use strict;
# figure out which path this script lives in. Set the current path to
# this and add it to @INC so this will work when run as part of mail
# alias by the mailer daemon
-my $path = $0;
-$path =~ s#(.*)/[^/]+#$1#;
-chdir $path;
-use lib ($path);
+# since "use lib" is run at compile time, we need to enclose the
+# $::path declaration in a BEGIN block so that it is executed before
+# the rest of the file is compiled.
+BEGIN {
+ $::path = $0;
+ $::path =~ m#(.*)/[^/]+#;
+ $::path = $1;
+}
+chdir $::path;
+use lib ($::path);
use XML::Parser;
use Data::Dumper;
@@ -65,6 +71,7 @@ ConnectToDatabase();
sub sillyness {
my $zz;
+ $zz = $Data::Dumper::Useqq;
$zz = %::components;
$zz = %::versions;
$zz = %::keywordsbyname;
diff --git a/move.pl b/move.pl
index aed6649a4..37b8cb7ef 100755
--- a/move.pl
+++ b/move.pl
@@ -107,19 +107,19 @@ foreach my $id (split(/:/, $::FORM{'buglist'})) {
my $fieldid = GetFieldID("bug_status");
my $cur_status= $bug->bug_status;
SendSQL("INSERT INTO bugs_activity " .
- "(bug_id,who,bug_when,fieldid,oldvalue,newvalue) VALUES " .
+ "(bug_id,who,bug_when,fieldid,removed,added) VALUES " .
"($id,$exporterid,now(),$fieldid,'$cur_status','RESOLVED')");
- my $fieldid = GetFieldID("resolution");
+ $fieldid = GetFieldID("resolution");
my $cur_res= $bug->resolution;
SendSQL("INSERT INTO bugs_activity " .
- "(bug_id,who,bug_when,fieldid,oldvalue,newvalue) VALUES " .
+ "(bug_id,who,bug_when,fieldid,removed,added) VALUES " .
"($id,$exporterid,now(),$fieldid,'$cur_res','MOVED')");
SendSQL("UPDATE bugs SET bug_status =\"RESOLVED\" where bug_id=\"$id\"");
SendSQL("UPDATE bugs SET resolution =\"MOVED\" where bug_id=\"$id\"");
my $comment = "Bug moved to " . Param("move-to-url") . ".\n\n";
- $comment .= "If the move succeeded, $exporter will recieve a mail\n";
+ $comment .= "If the move succeeded, $exporter will receive a mail\n";
$comment .= "containing the number of the new bug in the other database.\n";
$comment .= "If all went well, please mark this bug verified, and paste\n";
$comment .= "in a link to the new bug. Otherwise, reopen this bug.\n";
diff --git a/newquip.html b/newquip.html
deleted file mode 100644
index abd1cdd51..000000000
--- a/newquip.html
+++ /dev/null
@@ -1,37 +0,0 @@
-<HTML>
-
-<!--
- 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):
-
- Contributor(s): Terry Weissman <terry@mozilla.org>
--->
-
-<TITLE>I'm So Pretty and Witty And Wise</TITLE>
-<H2>Add your own clever headline.</h2>
-The buglist picks a random quip for the headline, and
-you can extend the quip list. Type in something clever or
-funny or boring and bonk on the button.
-<HR>
-<FORM METHOD=POST ACTION="new_comment.cgi">
-<INPUT SIZE=80 NAME="comment"><BR>
-<INPUT TYPE="submit" VALUE="Add This Quip"></FORM>
-</HR>
-For the impatient, you can
-<A HREF="data/comments">view the whole quip list</A>.
diff --git a/oracle/CVS/Entries b/oracle/CVS/Entries
deleted file mode 100644
index 178481050..000000000
--- a/oracle/CVS/Entries
+++ /dev/null
@@ -1 +0,0 @@
-D
diff --git a/oracle/CVS/Repository b/oracle/CVS/Repository
deleted file mode 100644
index 5802d4b7b..000000000
--- a/oracle/CVS/Repository
+++ /dev/null
@@ -1 +0,0 @@
-mozilla/webtools/bugzilla/oracle
diff --git a/post_bug.cgi b/post_bug.cgi
index 90ca32f52..f1a3e6443 100755
--- a/post_bug.cgi
+++ b/post_bug.cgi
@@ -33,6 +33,7 @@ require "CGI.pl";
sub sillyness {
my $zz;
$zz = $::buffer;
+ $zz = $::usergroupset;
$zz = %::COOKIE;
$zz = %::components;
$zz = %::versions;
@@ -202,11 +203,22 @@ $comment = trim($comment);
# OK except for the fact that it causes e-mail to be suppressed.
$comment = $comment ? $comment : " ";
-$query .= "now(), 0";
+$query .= "now(), (0";
foreach my $b (grep(/^bit-\d*$/, keys %::FORM)) {
if ($::FORM{$b}) {
my $v = substr($b, 4);
+ $v =~ /^(\d+)$/
+ || PuntTryAgain("One of the group bits submitted was invalid.");
+ if (!GroupIsActive($v)) {
+ # Prevent the user from adding the bug to an inactive group.
+ # Should only happen if there is a bug in Bugzilla or the user
+ # hacked the "enter bug" form since otherwise the UI
+ # for adding the bug to the group won't appear on that form.
+ PuntTryAgain("You can't add this bug to the inactive group " .
+ "identified by the bit '$v'. This shouldn't happen, " .
+ "so it may indicate a bug in Bugzilla.");
+ }
$query .= " + $v"; # Carefully written so that the math is
# done by MySQL, which can handle 64-bit math,
# and not by Perl, which I *think* can not.
@@ -215,7 +227,7 @@ foreach my $b (grep(/^bit-\d*$/, keys %::FORM)) {
-$query .= ")\n";
+$query .= ") & $::usergroupset)\n";
my %ccids;
diff --git a/process_bug.cgi b/process_bug.cgi
index dded85dbb..70d2625ba 100755
--- a/process_bug.cgi
+++ b/process_bug.cgi
@@ -21,6 +21,7 @@
# Contributor(s): Terry Weissman <terry@mozilla.org>
# Dan Mosedale <dmose@mozilla.org>
# Dave Miller <justdave@syndicomm.com>
+# Christopher Aillon <christopher@aillon.com>
use diagnostics;
use strict;
@@ -48,6 +49,59 @@ my $whoid = confirm_login();
my $requiremilestone = 0;
+######################################################################
+# Begin Data/Security Validation
+######################################################################
+
+# Create a list of IDs of all bugs being modified in this request.
+# This list will either consist of a single bug number from the "id"
+# form/URL field or a series of numbers from multiple form/URL fields
+# named "id_x" where "x" is the bug number.
+my @idlist;
+if (defined $::FORM{'id'}) {
+ push @idlist, $::FORM{'id'};
+} else {
+ foreach my $i (keys %::FORM) {
+ if ($i =~ /^id_([1-9][0-9]*)/) {
+ push @idlist, $1;
+ }
+ }
+}
+
+# For each bug being modified, make sure its ID is a valid bug number
+# representing an existing bug that the user is authorized to access.
+foreach my $id (@idlist) {
+ ValidateBugID($id);
+}
+
+# If we are duping bugs, let's also make sure that we can change
+# the original. This takes care of issue A on bug 96085.
+if (defined $::FORM{'dup_id'} && $::FORM{'knob'} eq "duplicate") {
+ ValidateBugID($::FORM{'dup_id'});
+
+ # Also, let's see if the reporter has authorization to see the bug
+ # to which we are duping. If not we need to prompt.
+ DuplicateUserConfirm();
+}
+
+# If the user has a bug list and is processing one bug, then after
+# we process the bug we are going to show them the next bug on their
+# list. Thus we have to make sure this bug ID is also valid,
+# since a malicious cracker might alter their cookies for the purpose
+# gaining access to bugs they are not authorized to access.
+if ( $::COOKIE{"BUGLIST"} ne "" && defined $::FORM{'id'} ) {
+ my @buglist = split( /:/ , $::COOKIE{"BUGLIST"} );
+ my $idx = lsearch( \@buglist , $::FORM{"id"} );
+ if ($idx < $#buglist) {
+ my $nextbugid = $buglist[$idx + 1];
+ ValidateBugID($nextbugid);
+ }
+}
+
+######################################################################
+# End Data/Security Validation
+######################################################################
+
print "Content-type: text/html\n\n";
PutHeader ("Bug processed");
@@ -65,7 +119,19 @@ if ( Param("strictvaluechecks") ) {
}
}
-if ($::FORM{'product'} ne $::dontchange) {
+ConnectToDatabase();
+
+# Figure out whether or not the user is trying to change the product
+# (either the "product" variable is not set to "don't change" or the
+# user is changing a single bug and has changed the bug's product),
+# and make the user verify the version, component, target milestone,
+# and bug groups if so.
+if ( $::FORM{'id'} ) {
+ SendSQL("SELECT product FROM bugs WHERE bug_id = $::FORM{'id'}");
+ $::oldproduct = FetchSQLData();
+}
+if ( ($::FORM{'id'} && $::FORM{'product'} ne $::oldproduct)
+ || (!$::FORM{'id'} && $::FORM{'product'} ne $::dontchange) ) {
if ( Param("strictvaluechecks") ) {
CheckFormField(\%::FORM, 'product', \@::legal_product);
}
@@ -87,42 +153,105 @@ if ($::FORM{'product'} ne $::dontchange) {
$mok = lsearch($::target_milestone{$prod}, $::FORM{'target_milestone'}) >= 0;
}
- if (!$vok || !$cok || !$mok) {
- print "<H1>Changing product means changing version, target milestone and component.</H1>\n";
- print "You have chosen a new product, and now the version, target milestone and/or\n";
- print "component fields are not correct. (Or, possibly, the bug did\n";
- print "not have a valid target milestone, component or version field in the first place.)\n";
- print "Anyway, please set the version, target milestone and component now.<p>\n";
- print "<form>\n";
- print "<table>\n";
- print "<tr>\n";
- print "<td align=right><b>Product:</b></td>\n";
- print "<td>$prod</td>\n";
- print "</tr><tr>\n";
- print "<td align=right><b>Version:</b></td>\n";
- print "<td>" . Version_element($::FORM{'version'}, $prod) . "</td>\n";
- print "</tr><tr>\n";
-
- if ( Param("usetargetmilestone") ) {
- print "<td align=right><b>Target Milestone:</b></td>\n";
- print "<td>" . Milestone_element($::FORM{'target_milestone'}, $prod) . "</td>\n";
- print "</tr><tr>\n";
- }
+ # If anything needs to be verified, generate a form for verifying it.
+ if (!$vok || !$cok || !$mok || (Param('usebuggroups') && !defined($::FORM{'addtonewgroup'}))) {
- print "<td align=right><b>Component:</b></td>\n";
- print "<td>" . Component_element($::FORM{'component'}, $prod) . "</td>\n";
- print "</tr>\n";
- print "</table>\n";
+ # Start the form.
+ print qq|<form action="process_bug.cgi" method="post">\n|;
+
+ # Add all form fields to the form as hidden fields (except those
+ # being verified), so the user's changes are preserved.
foreach my $i (keys %::FORM) {
if ($i ne 'version' && $i ne 'component' && $i ne 'target_milestone') {
- print "<input type=hidden name=$i value=\"" .
- value_quote($::FORM{$i}) . "\">\n";
+ print qq|<input type="hidden" name="$i" value="| . value_quote($::FORM{$i}) . qq|">\n|;
+ }
+ }
+
+ # Display UI for verifying the version, component, and target milestone fields.
+ if (!$vok || !$cok || !$mok) {
+ my ($sectiontitle, $sectiondescription);
+ if ( Param('usetargetmilestone') ) {
+ $sectiontitle = "Verify Version, Component, Target Milestone";
+ $sectiondescription = qq|
+ You are moving the bug(s) to the product <b>$prod</b>, and now the
+ version, component, and/or target milestone fields are not correct
+ (or perhaps they were not correct in the first place). In any case,
+ please set the correct version, component, and target milestone now:
+ |;
+ } else {
+ $sectiontitle = "Verify Version, Component";
+ $sectiondescription = qq|
+ You are moving the bug(s) to the product <b>$prod</b>, and now the
+ version, and component fields are not correct (or perhaps they were
+ not correct in the first place). In any case, please set the correct
+ version and component now:
+ |;
+ }
+
+ my $versionmenu = Version_element($::FORM{'version'}, $prod);
+ my $componentmenu = Component_element($::FORM{'component'}, $prod);
+
+ print qq|
+ <h3>$sectiontitle</h3>
+
+ <p>
+ $sectiondescription
+ <p>
+
+ <table><tr>
+ <td>
+ <b>Version:</b><br>
+ $versionmenu
+ </td>
+ <td>
+ <b>Component:</b><br>
+ $componentmenu
+ </td>
+ |;
+
+ if ( Param("usetargetmilestone") ) {
+ my $milestonemenu = Milestone_element($::FORM{'target_milestone'}, $prod);
+ print qq|
+ <td>
+ <b>Target Milestone:</b><br>
+ $milestonemenu
+ </td>
+ |;
}
+
+ print qq|
+ </tr></table>
+ |;
+ }
+
+ # Display UI for determining whether or not to remove the bug from
+ # its old product's group and/or add it to its new product's group.
+ if (Param('usebuggroups') && !defined($::FORM{'addtonewgroup'})) {
+ print qq|
+ <h3>Verify Bug Group</h3>
+
+ <p>
+ Do you want to add the bug to its new product's group (if any)?
+ </p>
+
+ <p>
+ <input type="radio" name="addtonewgroup" value="no"><b>no</b><br>
+ <input type="radio" name="addtonewgroup" value="yes"><b>yes</b><br>
+ <input type="radio" name="addtonewgroup" value="yesifinold" checked>
+ <b>yes, but only if the bug was in its old product's group</b><br>
+ </p>
+ |;
}
- print "<input type=submit value=Commit>\n";
- print "</form>\n";
- print "</hr>\n";
- print "<a href=query.cgi>Cancel all this and go to the query page.</a>\n";
+
+ # End the form.
+ print qq|
+ <input type="submit" value="Commit">
+ </form>
+ <hr>
+ <a href="query.cgi">Cancel and Return to the Query Page</a>
+ |;
+
+ # End the page and stop processing.
PutFooter();
exit;
}
@@ -216,14 +345,97 @@ empowered user, may make that change to the $f field.
exit();
}
+# Confirm that the reporter of the current bug can access the bug we are duping to.
+sub DuplicateUserConfirm {
+ my $dupe = trim($::FORM{'id'});
+ my $original = trim($::FORM{'dup_id'});
+
+ SendSQL("SELECT reporter FROM bugs WHERE bug_id = " . SqlQuote($dupe));
+ my $reporter = FetchOneColumn();
+ SendSQL("SELECT profiles.groupset FROM profiles WHERE profiles.userid =".SqlQuote($reporter));
+ my $reportergroupset = FetchOneColumn();
+
+ SendSQL("SELECT ((groupset & $reportergroupset) = groupset) , reporter , assigned_to , qa_contact ,
+ reporter_accessible , assignee_accessible , qacontact_accessible , cclist_accessible
+ FROM bugs
+ WHERE bug_id = $original");
+
+ my ($isauthorized, $originalreporter, $assignee, $qacontact, $reporter_accessible,
+ $assignee_accessible, $qacontact_accessible, $cclist_accessible) = FetchSQLData();
+
+ # If reporter is authorized via the database, or is the original reporter, assignee,
+ # or QA Contact, we'll automatically confirm they can be added to the cc list
+ if ($isauthorized
+ || ($reporter_accessible && $originalreporter == $reporter)
+ || ($assignee_accessible && $assignee == $reporter)
+ || ($qacontact_accessible && $qacontact == $reporter)) {
+
+ $::FORM{'confirm_add_duplicate'} = "1";
+ return;
+ }
+
+ # Try to authorize the user one more time by seeing if they are on
+ # the cc: list. If so, finish validation and return.
+ if ($cclist_accessible ) {
+ my @cclist;
+ SendSQL("SELECT cc.who
+ FROM bugs , cc
+ WHERE bugs.bug_id = $original
+ AND cc.bug_id = bugs.bug_id
+ ");
+ while (my ($ccwho) = FetchSQLData()) {
+ if ($reporter == $ccwho) {
+ $::FORM{'confirm_add_duplicate'} = "1";
+ return;
+ }
+ }
+ }
+ if (defined $::FORM{'confirm_add_duplicate'}) {
+ return;
+ }
+ # Once in this part of the subroutine, the user has not been auto-validated
+ # and the duper has not chosen whether or not to add to CC list, so let's
+ # ask the duper what he/she wants to do.
+ # First, will the user gain access to this bug immediately by being CC'd?
+ my $reporter_access = $cclist_accessible ? "will immediately" : "might, in the future,";
+
+ print "Content-type: text/html\n\n";
+ PutHeader("Duplicate Warning");
+ print "<P>
+When marking a bug as a duplicate, the reporter of the
+duplicate is normally added to the CC list of the original.
+The permissions on bug #$original (the original) are currently set
+such that the reporter would not normally be able to see it.
+<P><B>Adding the reporter to the CC list of bug #$original
+$reporter_access allow him/her access to view this bug.</B>
+Do you wish to do this?</P>
+</P>
+";
+ print "<form method=post>\n\n";
+ foreach my $i (keys %::FORM) {
+ # Make sure we don't include the username/password fields in the
+ # HTML. If cookies are off, they'll have to reauthenticate after
+ # hitting "submit changes anyway".
+ # see http://bugzilla.mozilla.org/show_bug.cgi?id=15980
+ if ($i !~ /^(Bugzilla|LDAP)_(login|password)$/) {
+ my $value = value_quote($::FORM{$i});
+ print qq{<input type=hidden name="$i" value="$value">\n};
+ }
+ }
-my @idlist;
-if (defined $::FORM{'id'}) {
+ print qq{<p><input type=radio name="confirm_add_duplicate" value="1"> Yes, add the reporter to CC list on bug $original</p>\n};
+ print qq{<p><input type=radio name="confirm_add_duplicate" value="0" checked="checked"> No, do not add the reporter to CC list on bug $original</p>\n};
+ print qq{\n<p><a href="show_bug.cgi?id=$dupe">Throw away my changes, and go revisit bug $dupe</a>\n};
+ print qq{\n<p><input type="submit" value="Submit"></p></form>\n};
+ PutFooter();
+ exit;
+} # end DuplicateUserConfirm()
+if (defined $::FORM{'id'} && Param('strictvaluechecks')) {
# since this means that we were called from show_bug.cgi, now is a good
# time to do a whole bunch of error checking that can't easily happen when
# we've been called from buglist.cgi, because buglist.cgi only tweaks
@@ -231,31 +443,18 @@ if (defined $::FORM{'id'}) {
# (XXX those error checks need to happen too, but implementing them
# is more work in the current architecture of this script...)
#
- if ( Param('strictvaluechecks') ) {
- CheckFormField(\%::FORM, 'rep_platform', \@::legal_platform);
- CheckFormField(\%::FORM, 'priority', \@::legal_priority);
- CheckFormField(\%::FORM, 'bug_severity', \@::legal_severity);
- CheckFormField(\%::FORM, 'component',
- \@{$::components{$::FORM{'product'}}});
- CheckFormFieldDefined(\%::FORM, 'bug_file_loc');
- CheckFormFieldDefined(\%::FORM, 'short_desc');
- CheckFormField(\%::FORM, 'product', \@::legal_product);
- CheckFormField(\%::FORM, 'version',
- \@{$::versions{$::FORM{'product'}}});
- CheckFormField(\%::FORM, 'op_sys', \@::legal_opsys);
- CheckFormFieldDefined(\%::FORM, 'longdesclength');
- CheckPosInt($::FORM{'id'});
- }
- push @idlist, $::FORM{'id'};
-} else {
- foreach my $i (keys %::FORM) {
- if ($i =~ /^id_/) {
- if ( Param('strictvaluechecks') ) {
- CheckPosInt(substr($i, 3));
- }
- push @idlist, substr($i, 3);
- }
- }
+ CheckFormField(\%::FORM, 'rep_platform', \@::legal_platform);
+ CheckFormField(\%::FORM, 'priority', \@::legal_priority);
+ CheckFormField(\%::FORM, 'bug_severity', \@::legal_severity);
+ CheckFormField(\%::FORM, 'component',
+ \@{$::components{$::FORM{'product'}}});
+ CheckFormFieldDefined(\%::FORM, 'bug_file_loc');
+ CheckFormFieldDefined(\%::FORM, 'short_desc');
+ CheckFormField(\%::FORM, 'product', \@::legal_product);
+ CheckFormField(\%::FORM, 'version',
+ \@{$::versions{$::FORM{'product'}}});
+ CheckFormField(\%::FORM, 'op_sys', \@::legal_opsys);
+ CheckFormFieldDefined(\%::FORM, 'longdesclength');
}
my $action = '';
@@ -354,20 +553,49 @@ sub CheckonComment( $ ) {
return( ! $ret ); # Return val has to be inverted
}
-
-my $foundbit = 0;
-foreach my $b (grep(/^bit-\d*$/, keys %::FORM)) {
- if (!$foundbit) {
- $foundbit = 1;
- DoComma();
- $::query .= "groupset = 0";
- }
- if ($::FORM{$b}) {
- my $v = substr($b, 4);
- $::query .= "+ $v"; # Carefully written so that the math is
- # done by MySQL, which can handle 64-bit math,
- # and not by Perl, which I *think* can not.
+# Changing this so that it will process groups from checkboxes instead of
+# select lists. This means that instead of looking for the bit-X values in
+# the form, we need to loop through all the bug groups this user has access
+# to, and for each one, see if it's selected.
+# In addition, adding a little extra work so that we don't clobber groupsets
+# for bugs where the user doesn't have access to the group, but does to the
+# bug (as with the proposed reporter access patch.)
+if($::usergroupset ne '0') {
+ # We want to start from zero and build up, since if all boxes have been
+ # unchecked, we want to revert to 0.
+ DoComma();
+ $::query .= "groupset = 0";
+ my ($id) = (@idlist);
+ SendSQL(<<_EOQ_);
+ SELECT bit, bit & $::usergroupset != 0, bit & bugs.groupset != 0
+ FROM groups, bugs
+ WHERE isbuggroup != 0 AND bug_id = $id
+ ORDER BY bit
+_EOQ_
+ while (my ($b, $userhasgroup, $bughasgroup) = FetchSQLData()) {
+ if (!$::FORM{"bit-$b"}) {
+ # If we make it here, the item didn't exist on the form or the user
+ # said to clear it. The only time we add this group back in is if
+ # the bug already has this group on it and the user can't access it.
+ if ($bughasgroup && !$userhasgroup) {
+ $::query .= " + $b";
+ }
+ } elsif ($::FORM{"bit-$b"} == -1) {
+ # If we get here, the user came from the change several bugs form, and
+ # said not to change this group restriction. So we'll add this group
+ # back in only if the bug already has it.
+ if ($bughasgroup) {
+ $::query .= " + $b";
+ }
+ } else {
+ # If we get here, the user said to set this group. If they don't have
+ # access to it, we'll use what's already on the bug, otherwise we'll
+ # add this one in.
+ if ($userhasgroup || $bughasgroup) {
+ $::query .= " + $b";
+ }
}
+ }
}
foreach my $field ("rep_platform", "priority", "bug_severity",
@@ -396,34 +624,76 @@ if (defined $::FORM{'qa_contact'}) {
}
-ConnectToDatabase();
+# If the user is submitting changes from show_bug.cgi for a single bug,
+# and that bug is restricted to a group, process the checkboxes that
+# allowed the user to set whether or not the reporter, assignee, QA contact,
+# and cc list can see the bug even if they are not members of all groups
+# to which the bug is restricted.
+if ( $::FORM{'id'} ) {
+ SendSQL("SELECT groupset FROM bugs WHERE bug_id = $::FORM{'id'}");
+ my ($groupset) = FetchSQLData();
+ if ( $groupset ) {
+ DoComma();
+ $::FORM{'reporter_accessible'} = $::FORM{'reporter_accessible'} ? '1' : '0';
+ $::query .= "reporter_accessible = $::FORM{'reporter_accessible'}";
+
+ DoComma();
+ $::FORM{'assignee_accessible'} = $::FORM{'assignee_accessible'} ? '1' : '0';
+ $::query .= "assignee_accessible = $::FORM{'assignee_accessible'}";
+
+ DoComma();
+ $::FORM{'qacontact_accessible'} = $::FORM{'qacontact_accessible'} ? '1' : '0';
+ $::query .= "qacontact_accessible = $::FORM{'qacontact_accessible'}";
+
+ DoComma();
+ $::FORM{'cclist_accessible'} = $::FORM{'cclist_accessible'} ? '1' : '0';
+ $::query .= "cclist_accessible = $::FORM{'cclist_accessible'}";
+ }
+}
+
-my $formCcSet = new RelationSet;
-my $origCcSet = new RelationSet;
-my $origCcString;
-my $removedCcString = "";
my $duplicate = 0;
-# We make sure to check out the CC list before we actually start touching any
-# bugs. mergeFromString() ultimately searches the database using a quoted
-# form of the data it gets from $::FORM{'cc'}, so anything bogus from a
-# security standpoint should trigger an abort there.
-#
-if (defined $::FORM{'newcc'} && defined $::FORM{'id'}) {
- $origCcSet->mergeFromDB("select who from cc where bug_id = $::FORM{'id'}");
- $formCcSet->mergeFromDB("select who from cc where bug_id = $::FORM{'id'}");
- $origCcString = $origCcSet->toString(); # cache a copy of the string vers
- if ((exists $::FORM{'removecc'}) && (exists $::FORM{'cc'})) {
-
- # save off the folks removed from the CC list so they can be given to
- # the processmaill command line so they can be sent mail about it.
- #
- $removedCcString = join (',', @{$::MFORM{'cc'}});
- $formCcSet->removeItemsInArray(@{$::MFORM{'cc'}});
+# We need to check the addresses involved in a CC change before we touch any bugs.
+# What we'll do here is formulate the CC data into two hashes of ID's involved
+# in this CC change. Then those hashes can be used later on for the actual change.
+my (%cc_add, %cc_remove);
+if (defined $::FORM{newcc} || defined $::FORM{removecc} || defined $::FORM{masscc}) {
+ # If masscc is defined, then we came from buglist and need to either add or
+ # remove cc's... otherwise, we came from bugform and may need to do both.
+ my ($cc_add, $cc_remove) = "";
+ if (defined $::FORM{masscc}) {
+ if ($::FORM{ccaction} eq 'add') {
+ $cc_add = $::FORM{masscc};
+ } elsif ($::FORM{ccaction} eq 'remove') {
+ $cc_remove = $::FORM{masscc};
+ }
+ } else {
+ $cc_add = $::FORM{newcc};
+ # We came from bug_form which uses a select box to determine what cc's
+ # need to be removed...
+ if (defined $::FORM{removecc}) {
+ $cc_remove = join (",", @{$::MFORM{cc}});
+ }
+ }
+
+ if ($cc_add) {
+ $cc_add =~ s/[\s,]+/ /g; # Change all delimiters to a single space
+ foreach my $person ( split(" ", $cc_add) ) {
+ my $pid = DBNameToIdAndCheck($person);
+ $cc_add{$pid} = $person;
+ }
+ }
+ if ($cc_remove) {
+ $cc_remove =~ s/[\s,]+/ /g; # Change all delimiters to a single space
+ foreach my $person ( split(" ", $cc_remove) ) {
+ my $pid = DBNameToIdAndCheck($person);
+ $cc_remove{$pid} = $person;
+ }
}
- $formCcSet->mergeFromString($::FORM{'newcc'});
}
+
if ( Param('strictvaluechecks') ) {
CheckFormFieldDefined(\%::FORM, 'knob');
}
@@ -575,7 +845,8 @@ if ($::FORM{'keywords'}) {
}
my $i = GetKeywordIdFromName($keyword);
if (!$i) {
- PuntTryAgain("Unknown keyword named <code>$keyword</code>. " .
+ PuntTryAgain("Unknown keyword named <code>" .
+ html_quote($keyword) . "</code>. " .
"<P>The legal keyword names are " .
"<A HREF=describekeywords.cgi>" .
"listed here</A>.");
@@ -624,14 +895,65 @@ sub SnapShotDeps {
my $timestamp;
+sub FindWrapPoint {
+ my ($string, $startpos) = @_;
+ if (!$string) { return 0 }
+ if (length($string) < $startpos) { return length($string) }
+ my $wrappoint = rindex($string, ",", $startpos); # look for comma
+ if ($wrappoint < 0) { # can't find comma
+ $wrappoint = rindex($string, " ", $startpos); # look for space
+ if ($wrappoint < 0) { # can't find space
+ $wrappoint = rindex($string, "-", $startpos); # look for hyphen
+ if ($wrappoint < 0) { # can't find hyphen
+ $wrappoint = $startpos; # just truncate it
+ } else {
+ $wrappoint++; # leave hyphen on the left side
+ }
+ }
+ }
+ return $wrappoint;
+}
+
+sub LogActivityEntry {
+ my ($i,$col,$removed,$added) = @_;
+ # in the case of CCs, deps, and keywords, there's a possibility that someone
+ # might try to add or remove a lot of them at once, which might take more
+ # space than the activity table allows. We'll solve this by splitting it
+ # into multiple entries if it's too long.
+ while ($removed || $added) {
+ my ($removestr, $addstr) = ($removed, $added);
+ if (length($removestr) > 254) {
+ my $commaposition = FindWrapPoint($removed, 254);
+ $removestr = substr($removed,0,$commaposition);
+ $removed = substr($removed,$commaposition);
+ $removed =~ s/^[,\s]+//; # remove any comma or space
+ } else {
+ $removed = ""; # no more entries
+ }
+ if (length($addstr) > 254) {
+ my $commaposition = FindWrapPoint($added, 254);
+ $addstr = substr($added,0,$commaposition);
+ $added = substr($added,$commaposition);
+ $added =~ s/^[,\s]+//; # remove any comma or space
+ } else {
+ $added = ""; # no more entries
+ }
+ $addstr = SqlQuote($addstr);
+ $removestr = SqlQuote($removestr);
+ my $fieldid = GetFieldID($col);
+ SendSQL("INSERT INTO bugs_activity " .
+ "(bug_id,who,bug_when,fieldid,removed,added) VALUES " .
+ "($i,$whoid,$timestamp,$fieldid,$removestr,$addstr)");
+ }
+}
+
sub LogDependencyActivity {
my ($i, $oldstr, $target, $me) = (@_);
my $newstr = SnapShotDeps($i, $target, $me);
if ($oldstr ne $newstr) {
- my $fieldid = GetFieldID($target);
- SendSQL("INSERT INTO bugs_activity " .
- "(bug_id,who,bug_when,fieldid,oldvalue,newvalue) VALUES " .
- "($i,$whoid,$timestamp,$fieldid,'$oldstr','$newstr')");
+ # Figure out what's really different...
+ my ($removed, $added) = DiffStrings($oldstr, $newstr);
+ LogActivityEntry($i,$target,$removed,$added);
return 1;
}
return 0;
@@ -696,8 +1018,14 @@ The changes made were:
$::FORM{'delta_ts'} = $delta_ts;
print "<li><form method=post>";
foreach my $i (keys %::FORM) {
- my $value = value_quote($::FORM{$i});
- print qq{<input type=hidden name="$i" value="$value">\n};
+ # Make sure we don't include the username/password fields in the
+ # HTML. If cookies are off, they'll have to reauthenticate after
+ # hitting "submit changes anyway".
+ # see http://bugzilla.mozilla.org/show_bug.cgi?id=15980
+ if ($i !~ /^(Bugzilla|LDAP)_(login|password)$/) {
+ my $value = value_quote($::FORM{$i});
+ print qq{<input type=hidden name="$i" value="$value">\n};
+ }
}
print qq{<input type=submit value="Submit my changes anyway">\n};
print " This will cause all of the above changes to be overwritten";
@@ -835,25 +1163,42 @@ The changes made were:
AppendComment($id, $::FORM{'who'}, $::FORM{'comment'});
}
- if (defined $::FORM{'newcc'} && defined $::FORM{'id'}
- && ! $origCcSet->isEqual($formCcSet) ) {
-
- # update the database to look like the form
- #
- my @CCDELTAS = $origCcSet->generateSqlDeltas($formCcSet, "cc",
- "bug_id", $::FORM{'id'},
- "who");
- $CCDELTAS[0] eq "" || SendSQL($CCDELTAS[0]);
- $CCDELTAS[1] eq "" || SendSQL($CCDELTAS[1]);
-
- my $col = GetFieldID('cc');
- my $origq = SqlQuote($origCcString);
- my $newq = SqlQuote($formCcSet->toString());
- SendSQL("INSERT INTO bugs_activity " .
- "(bug_id,who,bug_when,fieldid,oldvalue,newvalue) VALUES " .
- "($id,$whoid,'$timestamp',$col,$origq,$newq)");
+ my $removedCcString = "";
+ if (defined $::FORM{newcc} || defined $::FORM{removecc} || defined $::FORM{masscc}) {
+ # Get the current CC list for this bug
+ my %oncc;
+ SendSQL("SELECT who FROM cc WHERE bug_id = $id");
+ while (MoreSQLData()) {
+ $oncc{FetchOneColumn()} = 1;
+ }
+
+ my (@added, @removed) = ();
+ foreach my $pid (keys %cc_add) {
+ # If this person isn't already on the cc list, add them
+ if (! $oncc{$pid}) {
+ SendSQL("INSERT INTO cc (bug_id, who) VALUES ($id, $pid)");
+ push (@added, $cc_add{$pid});
+ $oncc{$pid} = 1;
+ }
+ }
+ foreach my $pid (keys %cc_remove) {
+ # If the person is on the cc list, remove them
+ if ($oncc{$pid}) {
+ SendSQL("DELETE FROM cc WHERE bug_id = $id AND who = $pid");
+ push (@removed, $cc_remove{$pid});
+ $oncc{$pid} = 0;
+ }
+ }
+ # Save off the removedCcString so it can be fed to processmail
+ $removedCcString = join (",", @removed);
+
+ # If any changes were found, record it in the activity log
+ if (scalar(@removed) || scalar(@added)) {
+ my $removed = join(", ", @removed);
+ my $added = join(", ", @added);
+ LogActivityEntry($id,"cc",$removed,$added);
+ }
}
-
if (defined $::FORM{'dependson'}) {
my $me = "blocked";
@@ -907,6 +1252,69 @@ The changes made were:
}
}
+ # When a bug changes products and the old or new product is associated
+ # with a bug group, it may be necessary to remove the bug from the old
+ # group or add it to the new one. There are a very specific series of
+ # conditions under which these activities take place, more information
+ # about which can be found in comments within the conditionals below.
+ if (
+ # the "usebuggroups" parameter is on, indicating that products
+ # are associated with groups of the same name;
+ Param('usebuggroups')
+
+ # the user has changed the product to which the bug belongs;
+ && defined $::FORM{'product'}
+ && $::FORM{'product'} ne $::dontchange
+ && $::FORM{'product'} ne $oldhash{'product'}
+ ) {
+ if (
+ # the user wants to add the bug to the new product's group;
+ ($::FORM{'addtonewgroup'} eq 'yes'
+ || ($::FORM{'addtonewgroup'} eq 'yesifinold'
+ && GroupNameToBit($oldhash{'product'}) & $oldhash{'groupset'}))
+
+ # the new product is associated with a group;
+ && GroupExists($::FORM{'product'})
+
+ # the bug is not already in the group; (This can happen when the user
+ # goes to the "edit multiple bugs" form with a list of bugs at least
+ # one of which is in the new group. In this situation, the user can
+ # simultaneously change the bugs to a new product and move the bugs
+ # into that product's group, which happens earlier in this script
+ # and thus is already done. If we didn't check for this, then this
+ # situation would cause us to add the bug to the group twice, which
+ # would result in the bug being added to a totally different group.)
+ && !BugInGroup($id, $::FORM{'product'})
+
+ # the user is a member of the associated group, indicating they
+ # are authorized to add bugs to that group, *or* the "usebuggroupsentry"
+ # parameter is off, indicating that users can add bugs to a product
+ # regardless of whether or not they belong to its associated group;
+ && (UserInGroup($::FORM{'product'}) || !Param('usebuggroupsentry'))
+
+ # the associated group is active, indicating it can accept new bugs;
+ && GroupIsActive(GroupNameToBit($::FORM{'product'}))
+ ) {
+ # Add the bug to the group associated with its new product.
+ my $groupbit = GroupNameToBit($::FORM{'product'});
+ SendSQL("UPDATE bugs SET groupset = groupset + $groupbit WHERE bug_id = $id");
+ }
+
+ if (
+ # the old product is associated with a group;
+ GroupExists($oldhash{'product'})
+
+ # the bug is a member of that group;
+ && BugInGroup($id, $oldhash{'product'})
+ ) {
+ # Remove the bug from the group associated with its old product.
+ my $groupbit = GroupNameToBit($oldhash{'product'});
+ SendSQL("UPDATE bugs SET groupset = groupset - $groupbit WHERE bug_id = $id");
+ }
+
+ print qq|</p>|;
+ }
+
# get a snapshot of the newly set values out of the database,
# and then generate any necessary bug activity entries by seeing
# what has changed since before we wrote out the new values.
@@ -949,23 +1357,23 @@ The changes made were:
$origQaContact = $old;
}
+ # If this is the keyword field, only record the changes, not everything.
+ if ($col eq 'keywords') {
+ ($old, $new) = DiffStrings($old, $new);
+ }
+
if ($col eq 'product') {
RemoveVotes($id, 0,
"This bug has been moved to a different product");
}
- $col = GetFieldID($col);
- $old = SqlQuote($old);
- $new = SqlQuote($new);
- my $q = "insert into bugs_activity (bug_id,who,bug_when,fieldid,oldvalue,newvalue) values ($id,$whoid,'$timestamp',$col,$old,$new)";
- # puts "<pre>$q</pre>"
- SendSQL($q);
+ LogActivityEntry($id,$col,$old,$new);
}
}
print "<TABLE BORDER=1><TD><H2>Changes to bug $id submitted</H2>\n";
SendSQL("unlock tables");
- my @ARGLIST = ("./processmail");
+ my @ARGLIST = ();
if ( $removedCcString ne "" ) {
push @ARGLIST, ("-forcecc", $removedCcString);
}
@@ -976,7 +1384,7 @@ The changes made were:
push @ARGLIST, ( "-forceqacontact", $origQaContact);
}
push @ARGLIST, ($id, $::FORM{'who'});
- system @ARGLIST;
+ system ("./processmail",@ARGLIST);
print "<TD><A HREF=\"show_bug.cgi?id=$id\">Back To BUG# $id</A></TABLE>\n";
@@ -988,19 +1396,10 @@ The changes made were:
my $isreporter = FetchOneColumn();
SendSQL("SELECT who FROM cc WHERE bug_id = " . SqlQuote($duplicate) . " and who = $reporter");
my $isoncc = FetchOneColumn();
- unless ($isreporter || $isoncc) {
- # The reporter is oblivious to the existance of the new bug... add 'em to the cc (and record activity)
- SendSQL("SELECT who FROM cc WHERE bug_id = " . SqlQuote($duplicate));
- my @dupecc;
- while (MoreSQLData()) {
- push (@dupecc, DBID_to_name(FetchOneColumn()));
- }
- my @newdupecc = @dupecc;
- push (@newdupecc, DBID_to_name($reporter));
- my $ccid = GetFieldID("cc");
- my $whochange = DBNameToIdAndCheck($::FORM{'who'});
- SendSQL("INSERT INTO bugs_activity (bug_id,who,bug_when,fieldid,oldvalue,newvalue) VALUES " .
- "('$duplicate','$whochange',now(),$ccid,'" . join (",", sort @dupecc) . "','" . join (",", sort @newdupecc) . "')");
+ unless ($isreporter || $isoncc || ! $::FORM{'confirm_add_duplicate'}) {
+ # The reporter is oblivious to the existance of the new bug and is permitted access
+ # ... add 'em to the cc (and record activity)
+ LogActivityEntry($duplicate,"cc","",DBID_to_name($reporter));
SendSQL("INSERT INTO cc (who, bug_id) VALUES ($reporter, " . SqlQuote($duplicate) . ")");
}
AppendComment($duplicate, $::FORM{'who'}, "*** Bug $::FORM{'id'} has been marked as a duplicate of this bug. ***");
diff --git a/processmail b/processmail
index c4b275500..1a506211b 100755
--- a/processmail
+++ b/processmail
@@ -1,4 +1,4 @@
-#!/usr/bonsaitools/bin/perl -w
+#!/usr/bonsaitools/bin/perl -wT
# -*- Mode: perl; indent-tabs-mode: nil -*-
#
# The contents of this file are subject to the Mozilla Public
@@ -22,24 +22,30 @@
# Bryce Nesbitt <bryce-mozilla@nextbus.com>
# Dan Mosedale <dmose@mozilla.org>
# Alan Raetz <al_raetz@yahoo.com>
-#
-
-# To recreate the shadow database, run "processmail regenerate" .
+# Jacob Steenhagen <jake@actex.net>
+# Matthew Tuck <matty@chariot.net.au>
use diagnostics;
use strict;
+use lib ".";
require "globals.pl";
use RelationSet;
+
+# Shut up misguided -w warnings about "used only once".
+sub processmail_sillyness {
+ my $zz;
+ $zz = $::db;
+}
+
$| = 1;
umask(0);
-$::lockcount = 0;
-my $regenerate = 0;
my $nametoexclude = "";
+my %nomail;
my @excludedAddresses = ();
@@ -53,276 +59,9 @@ my %force;
@{$force{'CClist'}} = ();
@{$force{'Voter'}} = ();
-sub Lock {
- if ($::lockcount <= 0) {
- $::lockcount = 0;
- if (!open(LOCKFID, ">>data/maillock")) {
- mkdir "data", 0777;
- chmod 0777, "data";
- open(LOCKFID, ">>data/maillock") || die "Can't open lockfile.";
- }
- my $val = flock(LOCKFID,2);
- if (!$val) { # '2' is magic 'exclusive lock' const.
- print "Lock failed: $val\n";
- }
- chmod 0666, "data/maillock";
- }
- $::lockcount++;
-}
-
-sub Unlock {
- $::lockcount--;
- if ($::lockcount <= 0) {
- flock(LOCKFID,8); # '8' is magic 'unlock' const.
- close LOCKFID;
- }
-}
-
-sub FileSize {
- my ($filename) = (@_);
- my ($dev,$ino,$mode,$nlink,$uid,$gid,$rdev,$size,
- $atime,$mtime,$ctime,$blksize,$blocks)
- = stat($filename);
- if (defined $size) {
- return $size;
- }
- return -1;
-}
-
-
-
-sub Different {
- my ($file1, $file2) = (@_);
- my $size1 = FileSize($file1);
- my $size2 = FileSize($file2);
- if ($size1 != $size2) {
- return 1;
- }
- open(FID1, "<$file1") || die "Can't open $file1";
- open(FID2, "<$file2") || die "Can't open $file2";
- my $d1;
- my $d2;
- if (read(FID1, $d1, $size1) ne $size1) {
- die "Can't read $size1 bytes from $file1";
- }
- if (read(FID2, $d2, $size2) ne $size2) {
- die "Can't read $size2 bytes from $file2";
- }
- close FID1;
- close FID2;
- return ($d1 ne $d2);
-}
-
-
-sub DescCC {
- my $cclist = shift();
-
- return "" if ( $cclist->size() == 0 );
-
- return "Cc: " . $cclist->toString() . "\n";
-}
-
-
-sub DescDependencies {
- my ($id) = (@_);
- if (!Param("usedependencies")) {
- return "";
- }
- my $result = "";
- my $me = "blocked";
- my $target = "dependson";
- my $title = "BugsThisDependsOn";
- for (1..2) {
- SendSQL("select $target from dependencies where $me = $id order by $target");
- my @list;
- while (MoreSQLData()) {
- push(@list, FetchOneColumn());
- }
- if (@list) {
- my @verbose;
- my $count = 0;
- foreach my $i (@list) {
- SendSQL("select bug_status, resolution from bugs where bug_id = $i");
- my ($bug_status, $resolution) = (FetchSQLData());
- my $desc;
- if ($bug_status eq "NEW" || $bug_status eq "ASSIGNED" ||
- $bug_status eq "REOPENED" || $bug_status eq "UNCONFIRMED") {
- $desc = "";
- } else {
- $desc = "[$resolution]";
- }
- push(@verbose, $i . "$desc");
- $count++;
- }
- if ($count > 5) {
- $result .= "$title: Big list (more than 5) has been omitted\n";
- } else {
- $result .= "$title: " . join(', ', @verbose) . "\n";
- }
- }
- my $tmp = $me;
- $me = $target;
- $target = $tmp;
- $title = "OtherBugsDependingOnThis";
- }
- return $result;
-}
-
-
-
-sub GetBugText {
- my ($id) = (@_);
- undef %::bug;
-
- my @collist = ("bug_id", "product", "version", "rep_platform", "op_sys",
- "bug_status", "resolution", "priority", "bug_severity",
- "assigned_to", "reporter", "bug_file_loc",
- "short_desc", "component", "qa_contact", "target_milestone",
- "status_whiteboard", "groupset");
-
- my $query = "select " . join(", ", @collist) .
- " from bugs where bug_id = $id";
-
- SendSQL($query);
-
- my @row;
- if (!(@row = FetchSQLData())) {
- return "";
- }
- foreach my $field (@collist) {
- $::bug{$field} = shift @row;
- if (!defined $::bug{$field}) {
- $::bug{$field} = "";
- }
- }
-
- $::bug{'assigned_to'} = DBID_to_name($::bug{'assigned_to'});
- $::bug{'reporter'} = DBID_to_name($::bug{'reporter'});
- my $qa_contact = "";
- my $target_milestone = "";
- my $status_whiteboard = "";
- if (Param('useqacontact') && $::bug{'qa_contact'} > 0) {
- $::bug{'qa_contact'} = DBID_to_name($::bug{'qa_contact'});
- $qa_contact = "QAContact: $::bug{'qa_contact'}\n";
- } else {
- $::bug{'qa_contact'} = "";
- }
- if (Param('usetargetmilestone') && $::bug{'target_milestone'} ne "") {
- $target_milestone = "TargetMilestone: $::bug{'target_milestone'}\n";
- }
- if (Param('usestatuswhiteboard') && $::bug{'status_whiteboard'} ne "") {
- $status_whiteboard = "StatusWhiteboard: $::bug{'status_whiteboard'}\n";
- }
-
- $::bug{'long_desc'} = GetLongDescriptionAsText($id);
-
- my $cclist = new RelationSet();
- $cclist->mergeFromDB("select who from cc where bug_id = $id");
- my @voterlist;
- SendSQL("select profiles.login_name from votes, profiles where votes.bug_id = $id and profiles.userid = votes.who");
- while (MoreSQLData()) {
- my $v = FetchOneColumn();
- push(@voterlist, $v);
- }
- $::bug{'cclist'} = $cclist->toString();
- $::bug{'voterlist'} = join(',', @voterlist);
-
- if (Param("prettyasciimail")) {
- $^A = "";
- my $temp = formline <<'END',$::bug{'short_desc'},$id,$::bug{'product'},$::bug{'bug_status'},$::bug{'version'},$::bug{'resolution'},$::bug{'rep_platform'},$::bug{'bug_severity'},$::bug{'op_sys'},$::bug{'priority'},$::bug{'component'},$::bug{'assigned_to'},$::bug{'reporter'},$qa_contact,DescCC($cclist),$target_milestone,${status_whiteboard},$::bug{'bug_file_loc'},DescDependencies($id);
-+============================================================================+
-| @<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< |
-+----------------------------------------------------------------------------+
-| Bug #: @<<<<<<<<<<< Product: @<<<<<<<<<<<<<<<<<<<<<< |
-| Status: @<<<<<<<<<<<<<<<<<< Version: @<<<<<<<<<<<<<<<<<<<<<< |
-| Resolution: @<<<<<<<<<<<<<<<<<< Platform: @<<<<<<<<<<<<<<<<<<<<<< |
-| Severity: @<<<<<<<<<<<<<<<<<< OS/Version: @<<<<<<<<<<<<<<<<<<<<<< |
-| Priority: @<<<<<<<<<<<<<<<<<< Component: @<<<<<<<<<<<<<<<<<<<<<< |
-+----------------------------------------------------------------------------+
-| Assigned To: @<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< |
-| Reported By: @<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< |
-| ~QA Contact: ^<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< |
-| ~ CC list: ^<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< |
-+----------------------------------------------------------------------------+
-| ~ Milestone: ^<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< |
-|~ Whiteboard: ^<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< |
-| URL: @<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< |
-|~Dependencies: ^<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< |
-+============================================================================+
-| DESCRIPTION |
-END
-
- my $prettymail = $^A . $::bug{'long_desc'};
- return $prettymail;
-
-
- } else {
- return "Bug\#: $id
-Product: $::bug{'product'}
-Version: $::bug{'version'}
-Platform: $::bug{'rep_platform'}
-OS/Version: $::bug{'op_sys'}
-Status: $::bug{'bug_status'}
-Resolution: $::bug{'resolution'}
-Severity: $::bug{'bug_severity'}
-Priority: $::bug{'priority'}
-Component: $::bug{'component'}
-AssignedTo: $::bug{'assigned_to'}
-ReportedBy: $::bug{'reporter'}
-$qa_contact$target_milestone${status_whiteboard}URL: $::bug{'bug_file_loc'}
-" . DescCC($cclist) . "Summary: $::bug{'short_desc'}
-" . DescDependencies($id) . "
-$::bug{'long_desc'}
-";
-}
-
-}
-
my %seen;
my @sentlist;
-sub fixaddresses {
- my ($field, $list) = (@_);
- my @result;
- foreach my $i (@$list) {
- if (!defined $i || $i eq "") {
- next;
- }
- SendSQL("select emailnotification, groupset & $::bug{'groupset'} from profiles where login_name = " .
- SqlQuote($i));
- my ($emailnotification, $groupset) = (FetchSQLData());
- if ($groupset ne $::bug{'groupset'}) {
- next;
- }
- if ($emailnotification eq "CConly") {
- if ($field ne "cc") {
- next;
- }
- }
- if ($emailnotification eq "ExcludeSelfChanges" &&
- (lc($i) eq $nametoexclude)) {
- push @excludedAddresses, $nametoexclude;
- next;
- }
-
- if (!defined $::nomail{$i} && !defined $seen{$i}) {
- push(@result, $i . Param('emailsuffix'));
- $seen{$i} = 1;
- }
- }
- return join(", ", @result);
-}
-
-
-sub Log {
- my ($str) = (@_);
- Lock();
- open(FID, ">>data/maillog") || die "Can't write to data/maillog";
- print FID time2str("%D %H:%M", time()) . ": $str\n";
- close FID;
- Unlock();
-}
-
sub FormatTriple {
my ($a, $b, $c) = (@_);
@@ -346,7 +85,7 @@ END
}
-sub NewProcessOneBug {
+sub ProcessOneBug {
my ($id) = (@_);
my @headerlist;
@@ -371,15 +110,19 @@ sub NewProcessOneBug {
$values{$i} = shift(@row);
}
my ($start, $end) = (@row);
+ # $start and $end are considered safe because users can't touch them
+ $start = detaint_string($start);
+ $end = detaint_string($end);
+
my $ccSet = new RelationSet();
$ccSet->mergeFromDB("SELECT who FROM cc WHERE bug_id = $id");
$values{'cc'} = $ccSet->toString();
- my @voterlist;
+ my @voterList;
SendSQL("SELECT profiles.login_name FROM votes, profiles " .
"WHERE votes.bug_id = $id AND profiles.userid = votes.who");
while (MoreSQLData()) {
- push(@voterlist, FetchOneColumn());
+ push(@voterList, FetchOneColumn());
}
$values{'assigned_to'} = DBID_to_name($values{'assigned_to'});
@@ -392,7 +135,7 @@ sub NewProcessOneBug {
SendSQL("SELECT profiles.login_name, fielddefs.description, " .
- " bug_when, oldvalue, newvalue " .
+ " bug_when, removed, added " .
"FROM bugs_activity, fielddefs, profiles " .
"WHERE bug_id = $id " .
" AND fielddefs.fieldid = bugs_activity.fieldid " .
@@ -414,7 +157,7 @@ sub NewProcessOneBug {
if ($who ne $lastwho) {
$lastwho = $who;
$difftext .= "\n$who" . Param('emailsuffix') . " changed:\n\n";
- $difftext .= FormatTriple("What ", "Old Value", "New Value");
+ $difftext .= FormatTriple("What ", "Removed", "Added");
$difftext .= ('-' x 76) . "\n";
}
$difftext .= FormatTriple($what, $old, $new);
@@ -428,7 +171,7 @@ sub NewProcessOneBug {
my $resid =
SendSQL("SELECT bugs_activity.bug_id, fielddefs.name, " .
- " oldvalue, newvalue " .
+ " removed, added " .
"FROM bugs_activity, dependencies, fielddefs ".
"WHERE bugs_activity.bug_id = dependencies.dependson " .
" AND dependencies.blocked = $id " .
@@ -473,119 +216,106 @@ sub NewProcessOneBug {
my $newcomments = GetLongDescriptionAsText($id, $start, $end);
- if (Param('newemailtech')) {
-
- #
- # Start of email filtering code
- #
- # Even if the user sending the email has not enabled #
- # 'newEmailTech', we still want to filter the email
- # based on other user's email preferences if the global Param
- # 'newemailtech' is enabled.
- #
- # Note: users who have not enabled newEmailTech will default
- # to no filtering (they will get all email Bugzilla sends).
-
- my $count = 0;
-
- my @currentEmailAttributes = getEmailAttributes($newcomments,
- @diffs);
- my (@assigned_toList,@reporterList,@qa_contactList,@ccList) =
- ();
-
- #open(LOG, ">>/tmp/maillog");
- #print LOG "\nBug ID: $id CurrentEmailAttributes:";
- #print LOG join(',', @currentEmailAttributes) . "\n";
-
- @excludedAddresses = (); # zero out global list
-
- @assigned_toList = filterEmailGroup('Owner',
- \@currentEmailAttributes,
- $values{'assigned_to'});
- @reporterList = filterEmailGroup('Reporter',
- \@currentEmailAttributes,
- $values{'reporter'});
- if (Param('useqacontact') && $values{'qa_contact'}) {
- @qa_contactList = filterEmailGroup('QAcontact',
- \@currentEmailAttributes,
- $values{'qa_contact'});
- } else {
- @qa_contactList = ();
- }
+ #
+ # Start of email filtering code
+ #
+ my $count = 0;
- @ccList = filterEmailGroup('CClist', \@currentEmailAttributes,
- $values{'cc'});
+ my @currentEmailAttributes = getEmailAttributes($newcomments, @diffs);
+ my (@assigned_toList,@reporterList,@qa_contactList,@ccList) = ();
- @voterlist = filterEmailGroup('Voter', \@currentEmailAttributes,
- join(',',@voterlist));
+ #open(LOG, ">>/tmp/maillog");
+ #print LOG "\nBug ID: $id CurrentEmailAttributes:";
+ #print LOG join(',', @currentEmailAttributes) . "\n";
- my @emailList = (@assigned_toList, @reporterList,
- @qa_contactList, @ccList, @voterlist);
+ @excludedAddresses = (); # zero out global list
- # only need one entry per person
- my @allEmail = ();
- my %AlreadySeen = ();
- foreach my $person (@emailList) {
- if ( !($AlreadySeen{$person}) ) {
- push(@allEmail,$person);
- $AlreadySeen{$person}++;
- }
+ @assigned_toList = filterEmailGroup('Owner',
+ \@currentEmailAttributes,
+ $values{'assigned_to'});
+ @reporterList = filterEmailGroup('Reporter',
+ \@currentEmailAttributes,
+ $values{'reporter'});
+ if (Param('useqacontact') && $values{'qa_contact'}) {
+ @qa_contactList = filterEmailGroup('QAcontact',
+ \@currentEmailAttributes,
+ $values{'qa_contact'});
+ } else {
+ @qa_contactList = ();
+ }
+
+ @ccList = filterEmailGroup('CClist', \@currentEmailAttributes,
+ $values{'cc'});
+
+ @voterList = filterEmailGroup('Voter', \@currentEmailAttributes,
+ join(',',@voterList));
+
+ my @emailList = (@assigned_toList, @reporterList,
+ @qa_contactList, @ccList, @voterList);
+
+ # only need one entry per person
+ my @allEmail = ();
+ my %AlreadySeen = ();
+ foreach my $person (@emailList) {
+ if ( !($AlreadySeen{$person}) ) {
+ push(@allEmail,$person);
+ $AlreadySeen{$person}++;
}
+ }
- #print LOG "\nbug $id email sent: " . join(',', @allEmail) . "\n";
+ #print LOG "\nbug $id email sent: " . join(',', @allEmail) . "\n";
- @excludedAddresses = filterExcludeList(\@excludedAddresses,
- \@allEmail);
+ @excludedAddresses = filterExcludeList(\@excludedAddresses,
+ \@allEmail);
- # print LOG "excluded: " . join(',',@excludedAddresses) . "\n\n";
+ # print LOG "excluded: " . join(',',@excludedAddresses) . "\n\n";
- foreach my $person ( @allEmail ) {
- $count++;
- if ( !defined(NewProcessOnePerson($person, $count, \@headerlist,
- \%values, \%defmailhead,
- \%fielddescription, $difftext,
- $newcomments, $start, $id))) {
+ foreach my $person ( @allEmail ) {
+ my @reasons;
- # if a value is not returned, this means that the person
- # was not sent mail. add them to the excludedAddresses list.
- # it will be filtered later for dups.
- #
- push @excludedAddresses, $person;
+ $count++;
- }
- }
+ push(@reasons, 'AssignedTo') if lsearch(\@assigned_toList, $person) != -1;
+ push(@reasons, 'Reporter') if lsearch(\@reporterList, $person) != -1;
+ push(@reasons, 'QAContact') if lsearch(\@qa_contactList, $person) != -1;
+ push(@reasons, 'CC') if lsearch(\@ccList, $person) != -1;
+ push(@reasons, 'Voter') if lsearch(\@voterList, $person) != -1;
- } else {
- my $count = 0;
- my @personlist = ($values{'assigned_to'}, $values{'reporter'},
- split(/,/, $values{'cc'}),
- @voterlist,
- $force{'CClist'});
- if ($values{'qa_contact'}) { push @personlist, $values{'qa_contact'} }
- for my $person (@personlist) {
- $count++;
-
- my $match = "^[^@, ]*@[^@, ]*\.[^@, ]*\$";
- if ($person !~ /$match/) {
- $person = $person . Param('emailsuffix');
- }
+ if ( !defined(NewProcessOnePerson($person, $count, \@headerlist,
+ \@reasons, \%values,
+ \%defmailhead,
+ \%fielddescription, $difftext,
+ $newcomments, $start, $id))) {
- if ( !defined(NewProcessOnePerson($person, $count, \@headerlist,
- \%values, \%defmailhead,
- \%fielddescription, $difftext,
- $newcomments, $start, $id))) {
+ # if a value is not returned, this means that the person
+ # was not sent mail. add them to the excludedAddresses list.
+ # it will be filtered later for dups.
+ #
+ push @excludedAddresses, $person;
- # if a value is not returned, this means that the person
- # was not sent mail. add them to the excludedAddresses list.
- # it will be filtered later for dups.
- #
- push @excludedAddresses, $person;
- }
}
}
+
SendSQL("UPDATE bugs SET lastdiffed = '$end', delta_ts = delta_ts " .
"WHERE bug_id = $id");
+
+ # Filter the exclude list for dupes one last time
+ @excludedAddresses = filterExcludeList(\@excludedAddresses,
+ \@sentlist);
+ if (@sentlist) {
+ print "<b>Email sent to:</b> " . join(", ", @sentlist) ."<br>\n";
+ } else {
+ print "<b>Email sent to:</b> no one<br>\n";
+ }
+
+ if (@excludedAddresses) {
+ print "<b>Excluding:</b> " . join(", ", @excludedAddresses) . "\n";
+ }
+
+ print "<br><center>If you wish to tweak the kinds of mail Bugzilla sends you, you can";
+ print " <a href=\"userprefs.cgi?bank=diffs\">change your preferences</a></center>\n";
+
}
# When one person is in different fields on one bug, they may be
@@ -621,6 +351,7 @@ sub filterExcludeList ($$) {
# match found, so we remove the entry
if ($included eq $excluded) {
pop(@result);
+ last;
}
}
}
@@ -693,9 +424,7 @@ sub getEmailAttributes ($@) {
} elsif ($fieldName eq 'QAContact') {
push (@{$force{'QAContact'}}, $new);
} elsif ($fieldName eq 'CC') {
- my @oldVal = split (/,/, $old);
- my @newVal = split (/,/, $new);
- my @added = filterExcludeList(\@newVal, \@oldVal);
+ my @added = split (/[ ,]/, $new);
push (@{$force{'CClist'}}, @added);
}
}
@@ -762,32 +491,22 @@ sub filterEmailGroup ($$$) {
foreach my $person (@emailList) {
- my $userid;
my $lastCount = @filteredList;
if ( $person eq '' ) { next; }
- SendSQL("SELECT userid FROM profiles WHERE login_name = "
- . SqlQuote($person) );
+ my $userid = DBname_to_id($person);
- if ( !($userid = FetchSQLData()) ) {
+ if ( ! $userid ) {
push(@filteredList,$person);
next;
}
- SendSQL("SELECT emailflags, newemailtech FROM profiles WHERE " .
+ SendSQL("SELECT emailflags FROM profiles WHERE " .
"userid = $userid" );
-
- my ($userFlagString, $newemailtech) = FetchSQLData();
-
- # people who are not using newemailtech get skipped; they will
- # be dealt with later by the old email tech code in
- # ProcessOneBug().
- #
- if (!defined($newemailtech) || $newemailtech == 0) {
- next;
- }
+ my ($userFlagString) = FetchSQLData();
+
# If the sender doesn't want email, exclude them from list
if (lc($person) eq $nametoexclude) {
@@ -904,28 +623,34 @@ sub filterEmailGroup ($$$) {
return @filteredList;
}
-sub NewProcessOnePerson ($$$$$$$$$$) {
- my ($person, $count, $hlRef, $valueRef, $dmhRef, $fdRef, $difftext,
+sub NewProcessOnePerson ($$$$$$$$$$$) {
+ my ($person, $count, $hlRef, $reasonsRef, $valueRef, $dmhRef, $fdRef, $difftext,
$newcomments, $start, $id) = @_;
my %values = %$valueRef;
my @headerlist = @$hlRef;
+ my @reasons = @$reasonsRef;
my %defmailhead = %$dmhRef;
my %fielddescription = %$fdRef;
if ($seen{$person}) {
return;
}
+
+ if ($nomail{$person}) {
+ return;
+ }
- SendSQL("SELECT userid, emailnotification, newemailtech," .
- " groupset & $values{'groupset'} " .
+ # Sanitize $values{'groupset'}
+ if ($values{'groupset'} =~ m/(\d+)/) {
+ $values{'groupset'} = $1;
+ } else {
+ $values{'groupset'} = 0;
+ }
+ SendSQL("SELECT userid, groupset & $values{'groupset'} " .
"FROM profiles WHERE login_name = " . SqlQuote($person));
- my ($userid, $emailnotification, $newemailtech,
- $groupset) = (FetchSQLData());
+ my ($userid, $groupset) = (FetchSQLData());
- if (!$newemailtech || !Param('newemailtech')) {
- return;
- }
$seen{$person} = 1;
@@ -940,16 +665,6 @@ sub NewProcessOnePerson ($$$$$$$$$$) {
if ($groupset ne $values{'groupset'}) {
return;
}
- if ($emailnotification eq "ExcludeSelfChanges" &&
- lc($person) eq $nametoexclude) {
- push @excludedAddresses, $nametoexclude;
- return;
- }
- # "$count < 3" means "this person is either assigned_to or reporter"
- #
- if ($emailnotification eq "CCOnly" && $count < 3) {
- return;
- }
my %mailhead = %defmailhead;
@@ -958,8 +673,8 @@ sub NewProcessOnePerson ($$$$$$$$$$) {
foreach my $f (@headerlist) {
if ($mailhead{$f}) {
my $value = $values{$f};
- if (!defined $value) {
- # Probaby ought to whine or something. ###
+ # If there isn't anything to show, don't include this header
+ if (! $value) {
next;
}
my $desc = $fielddescription{$f};
@@ -972,6 +687,28 @@ sub NewProcessOnePerson ($$$$$$$$$$) {
return;
}
+ my $reasonsbody = "------- You are receiving this mail because: -------\n";
+
+ if (scalar(@reasons) == 0) {
+ $reasonsbody .= "Whoops! I have no idea!\n";
+ } else {
+ foreach my $reason (@reasons) {
+ if ($reason eq 'AssignedTo') {
+ $reasonsbody .= "You are the assignee for the bug, or are watching the assignee.\n";
+ } elsif ($reason eq 'Reporter') {
+ $reasonsbody .= "You reported the bug, or are watching the reporter.\n";
+ } elsif ($reason eq 'QAContact') {
+ $reasonsbody .= "You are the QA contact for the bug, or are watching the QA contact.\n";
+ } elsif ($reason eq 'CC') {
+ $reasonsbody .= "You are on the CC list for the bug, or are watching someone who is.\n";
+ } elsif ($reason eq 'Voter') {
+ $reasonsbody .= "You are a voter for the bug, or are watching someone who is.\n";
+ } else {
+ $reasonsbody .= "Whoops! There is an unknown reason!\n";
+ }
+ }
+ }
+
my $isnew = ($start !~ m/[1-9]/);
my %substs;
@@ -992,6 +729,8 @@ sub NewProcessOnePerson ($$$$$$$$$$) {
$substs{"diffs"} = $difftext . "\n\n" . $newcomments;
}
$substs{"summary"} = $values{'short_desc'};
+ $substs{"reasonsheader"} = join(" ", @reasons);
+ $substs{"reasonsbody"} = $reasonsbody;
my $template = Param("newchangedmail");
@@ -1013,160 +752,23 @@ sub NewProcessOnePerson ($$$$$$$$$$) {
return 1;
}
-
-sub ProcessOneBug {
- my $i = $_[0];
- NewProcessOneBug($i);
-
- # Make sure that everyone who was excluded because of the advanced
- # filtering options (and thus are using new email tech) has the
- # corresponding element in %seen set. This is so that they won't
- # also be processed by the old email tech code, which follows.
- #
- # It's necessary because people who are excluded by the advanced
- # filtering code never make it into NewProcessOnePerson(), which is
- # where %seen would have otherwise been touched for them.
- #
- foreach my $person (@excludedAddresses) {
- $seen{$person} = 1;
- }
-
- my $old = "shadow/$i";
- my $new = "shadow/$i.tmp.$$";
- my $diffs = "shadow/$i.diffs.$$";
- my $verb = "Changed";
- if (!stat($old)) {
- mkdir "shadow", 0777;
- chmod 0777, "shadow";
- open(OLD, ">$old") || die "Couldn't create null $old";
- close OLD;
- $verb = "New";
- }
- my $text = GetBugText($i);
- if ($text eq "") {
- die "Couldn't find bug $i.";
- }
- open(FID, ">$new") || die "Couldn't create $new";
- print FID $text;
- close FID;
- if (Different($old, $new)) {
- system("diff -c -b $old $new > $diffs");
- my $tolist = fixaddresses("to",
- [$::bug{'assigned_to'}, $::bug{'reporter'},
- $::bug{'qa_contact'}]);
- my @combinedcc;
- foreach my $v (split(/,/, "$::bug{'cclist'},$::bug{'voterlist'}")) {
- push @combinedcc, $v;
- }
- push (@combinedcc, (@{$force{'CClist'}}, @{$force{'QAcontact'}},
- @{$force{'Reporter'}}, @{$force{'Owner'}}));
- my $cclist = fixaddresses("cc", \@combinedcc);
- my $logstr = "Bug $i $verb";
- if ($tolist ne "" || $cclist ne "") {
- my %substs;
-
- $substs{"fullbugreport"} = $text; # added ability to include the full bug report
- $substs{"to"} = $tolist;
- $substs{"cc"} = $cclist;
- $substs{"bugid"} = $i;
- $substs{"diffs"} = "";
- open(DIFFS, "<$diffs") || die "Can't open $diffs";
- while (<DIFFS>) {
- $substs{"diffs"} .= $_;
- }
- close DIFFS;
- $substs{"neworchanged"} = ($verb eq "New") ? "New: " : "";
- $substs{"summary"} = $::bug{'short_desc'};
- my $msg = PerformSubsts(Param("changedmail"), \%substs);
-
- if (!$regenerate) {
- # Note: fixaddresses may result in a Cc: only. This seems
- # harmless.
- my $sendmailparam = "-ODeliveryMode=deferred";
- if (Param("sendmailnow")) {
- $sendmailparam = "";
- }
- if ($enableSendMail==1) {
- open(SENDMAIL,
- "|/usr/lib/sendmail $sendmailparam -t") ||
- die "Can't open sendmail";
-
- print SENDMAIL $msg;
- close SENDMAIL;
- }
- foreach my $n (split(/[, ]+/, "$tolist,$cclist")) {
- if ($n ne "") {
- push(@sentlist, $n);
- }
- }
-
- $logstr = "$logstr; mail sent to $tolist, $cclist";
- }
- }
- unlink($diffs);
- Log($logstr);
- }
-
- # on the off chance that there are duplicate addresses in the exclude list,
- # we filter it for dups one more time. They could have gotten there in
- # fixaddresses(), NewProcessOnePerson(), or NewProcessOneBug.
- #
- @excludedAddresses = filterExcludeList(\@excludedAddresses,
- \@sentlist);
-
- if (!$regenerate) {
- if (@sentlist) {
- print "<B>Email sent to:</B> " . join(", ", @sentlist) . "<br>\n";
- } else {
- print "<B>Email sent to:</B> no one<br>\n";
- }
-
- if ( @excludedAddresses ) {
- print "<br><B>Excluding: </B>" . join(", ", @excludedAddresses) .
- "\n";
- }
-
- print "<br><br><center>New: <a href=\"userprefs.cgi\?bank=diffs\">" .
- "change your email preferences<\/a> if you wish to tweak the " .
- "kinds of Bugzilla email you get.<\/center>\n";
- }
- rename($new, $old) || die "Can't rename $new to $old";
- chmod 0666, $old;
- if ($regenerate) {
- print "$i ";
- }
- %seen = ();
- @sentlist = ();
-}
-
# Code starts here
ConnectToDatabase();
+# Set Taint mode for the SQL
+$::db->{Taint} = 1;
+# ^^^ Taint mode is still a work in progress...
GetVersionTable();
-Lock();
if (open(FID, "<data/nomail")) {
while (<FID>) {
- $::nomail{trim($_)} = 1;
+ $nomail{trim($_)} = 1;
}
close FID;
}
-# To recreate the shadow database, run "processmail regenerate" .
if ($#ARGV >= 0 && $ARGV[0] eq "regenerate") {
- $regenerate = 1;
- shift @ARGV;
- SendSQL("select bug_id from bugs order by bug_id");
- my @regenerate_list;
- while (my @row = FetchSQLData()) {
- push @regenerate_list, $row[0];
- }
- foreach my $i (@regenerate_list) {
- ProcessOneBug($i);
- Unlock();
- Lock();
- }
- print("\n");
+ print "Regenerating is no longer required or supported\n";
exit;
}
@@ -1190,7 +792,7 @@ if ($#ARGV >= 0 && $ARGV[0] eq "-forceqacontact") {
if (($#ARGV < 0) || ($#ARGV > 1)) {
print "Usage:\n processmail {bugid} {nametoexclude} " .
"[-forcecc list,of,users]\n [-forceowner name] " .
- "[-forceqacontact name]\nor\n processmail regenerate\nor\n" .
+ "[-forceqacontact name]\nor\n" .
" processmail rescanall\n";
exit;
}
@@ -1212,7 +814,14 @@ if ($ARGV[0] eq "rescanall") {
ProcessOneBug($ARGV[0]);
}
} else {
- ProcessOneBug($ARGV[0]);
+ my $bugnum;
+ if ($ARGV[0] =~ m/^([1-9][0-9]*)$/) {
+ $bugnum = $1;
+ } else {
+ print "Error calling processmail (bug id is not an integer)<br>\n";
+ exit;
+ }
+ ProcessOneBug($bugnum);
}
exit;
diff --git a/query.cgi b/query.cgi
index 0c171ce58..16c783864 100755
--- a/query.cgi
+++ b/query.cgi
@@ -292,8 +292,10 @@ foreach my $p (@::legal_product) {
next;
}
push @::product_list, $p;
- foreach my $c (@{$::components{$p}}) {
- $component_set{$c} = 1;
+ if ($::components{$p}) {
+ foreach my $c (@{$::components{$p}}) {
+ $component_set{$c} = 1;
+ }
}
foreach my $v (@{$::versions{$p}}) {
$version_set{$v} = 1;
@@ -531,8 +533,7 @@ ENDSCRIPT
PutHeader("Bugzilla Query Page", "Query",
"This page lets you search the database for recorded bugs.",
- q{onLoad="selectProduct(document.forms[0]);"},
- 0, $jscript);
+ q{onLoad="selectProduct(document.forms[0]);"}, $jscript);
push @::legal_resolution, "---"; # Oy, what a hack.
@@ -701,10 +702,12 @@ sub StringSearch {
<td><SELECT NAME=$type>
};
if ($default{$type} eq "") {
- $default{$type} = "substring";
+ $default{$type} = "allwordssubstr";
}
foreach my $i (["substring", "case-insensitive substring"],
["casesubstring", "case-sensitive substring"],
+ ["allwordssubstr", "all words as substrings"],
+ ["anywordssubstr", "any words as substrings"],
["allwords", "all words"],
["anywords", "any words"],
["regexp", "regular expression"],
@@ -778,6 +781,8 @@ my @types = (
["casesubstring", "contains (case-sensitive) substring"],
["substring", "contains (case-insensitive) substring"],
["notsubstring", "does not contain (case-insensitive) substring"],
+ ["allwordssubstr", "all words as (case-insensitive) substrings"],
+ ["anywordssubstr", "any words as (case-insensitive) substrings"],
["regexp", "contains regexp"],
["notregexp", "does not contain regexp"],
["lessthan", "less than"],
diff --git a/quicksearch.js b/quicksearch.js
index e4c21868b..7778d3598 100644
--- a/quicksearch.js
+++ b/quicksearch.js
@@ -12,6 +12,38 @@
//
// Created by
// Andreas Franke <afranke@mathweb.org>
+//
+// Contributors:
+// Stephen Lee <slee@uk.bnsmc.com>
+
+
+// Use no_result variable to avoid problems with "undefined" on some browsers
+
+var no_result="---";
+
+// do_unshift(l, s) is equivalent to l.unshift(s), but some browsers do not
+// support the built-in function.
+
+function do_unshift(l, s) {
+ l.length = l.length + 1;
+ for (var i=l.length-1; i>0; i--) {
+ l[i] = l[i-1];
+ }
+ l[0] = s;
+ return l.length;
+}
+
+// do_shift(l) is equivalent to l.shift(s), but some browsers do not
+// support the built-in function.
+
+function do_shift(l) {
+ var l0=l[0];
+ for (var i=0; i<l.length-1; i++) {
+ l[i] = l[i+1];
+ }
+ l.length = l.length - 1;
+ return l0;
+}
function go_to (url) {
document.location.href = url;
@@ -19,7 +51,7 @@ function go_to (url) {
}
function map(l, f) {
- l1 = new Array();
+ var l1 = new Array();
for (var i=0; i<l.length; i++) {
l1[i] = f(l[i]);
}
@@ -32,13 +64,15 @@ function isPrefix(s1, s2) {
}
function member(s, l) {
- return (l.length > 0)
- && ((s == l[0]) || member(s, l.slice(1)));
+ for (var i=0; i<l.length; i++) {
+ if (l[i] == s) return true;
+ }
+ return false;
}
function add(s, l) {
if (! member(s, l)) {
- l.unshift(s);
+ do_unshift(l,s);
}
}
@@ -141,7 +175,7 @@ function findIndex(array,value) {
function mapField(fieldname) {
var i = findIndex(f1,fieldname);
if (i >= 0) return f2[i];
- return undefined;
+ return no_result;
}
// `keywords' is defined externally
@@ -165,14 +199,14 @@ function is_severity(str) {
// `product_exceptions' is defined externally
function match_product(str) {
- s = str.toLowerCase();
+ var s = str.toLowerCase();
return (s.length > 2) && (! member(s,product_exceptions));
}
// `component_exceptions are defined externally
function match_component(str) {
- s = str.toLowerCase();
+ var s = str.toLowerCase();
return (s.length > 2) && (! member(s,component_exceptions));
}
@@ -222,27 +256,62 @@ function make_query_URL(url, input, searchLong) {
status_and_resolution = "";
charts = "";
- var searchURL = url; //bugzilla + "buglist.cgi";
- var abort = false;
+ // declare all variables used in this function
+
+ var searchURL = url; // bugzilla + "buglist.cgi" (or "query.cgi")
+ var abort = false; // global flag, checked upon return
+
+ var i,j,k,l; // index counters used in 'for' loops
+ var parts,input2; // escape "quoted" parts of input
+
+ var word; // array of words
+ // (space-separated parts of input2)
+ var alternative; // array of parts of an element of 'word'
+ // (separated by '|', sometimes by comma)
+ var comma_separated_words; // array of parts of an element of 'alternative'
+ var w; // current element of one of these arrays:
+ // word, alternative, comma_separated_words
+
+ var w0; // first element of 'word'
+ var prefixes; // comma-separated parts of w0
+ // (prefixes of status/resolution values)
+
+ var expr; // used for 'priority' support
+ var n,separator; // used for 'votes' support
+
+ var colon_separated_parts, fields,values,field;
+ // used for generic fields:values notation
+
+ var chart,and,or; // counters used in add_chart
+ var negation; // boolean flag used in add_chart
+
+ // `statuses_open' and `statuses_resolved' are defined externally
+ var statusOpen = statuses_open;
+ var statusResolved = statuses_resolved;
+ var statusAll = statusOpen.concat(statusResolved);
+
+ // `resolutions' is defined externally
+ var bug_status = statusOpen.slice().reverse(); //reverse is just cosmetic
+ var resolution = new Array();
// escape everything between quotes: "foo bar" --> "foo%20bar"
- var parts = input.split('"');
+ parts = input.split('"');
if ((parts.length % 2) != 1) {
alert('Unterminated quote');
abort = true;
- return undefined;
+ return no_result;
}
- for (var i=1; i<parts.length; i+=2) {
+ for (i=1; i<parts.length; i+=2) {
parts[i] = escape(parts[i]);
}
- var input2 = parts.join('"');
+ input2 = parts.join('"');
// abort if there are still brackets
if (input2.match(/[(]|[\)]/)) {
alert('Brackets (...) are not supported.\n' +
'Use quotes "..." for values that contain special characters.');
abort = true;
- return undefined;
+ return no_result;
}
// translate " AND "," OR "," NOT " to space,comma,dash
@@ -251,20 +320,11 @@ function make_query_URL(url, input, searchLong) {
input2 = input2.replace(/[\s]+NOT[\s]+/g," -");
// now split into words at space positions
- var word = input2.split(/[\s]+/);
+ word = input2.split(/[\s]+/);
// determine bug_status and resolution
// the first word may contain relevant info
- // `statuses_open' and `statuses_resolved' are defined externally
- var statusOpen = statuses_open;
- var statusResolved = statuses_resolved;
- var statusAll = statusOpen.concat(statusResolved);
-
- // `resolutions' is defined externally
- var bug_status = statusOpen.slice().reverse(); //reverse is just cosmetic
- var resolution = new Array();
-
// This function matches the given prefixes against the given statuses and
// resolutions. Matched statuses are added to bug_status, matched
// resolutions are added to resolution. Returns true iff some matches
@@ -292,24 +352,24 @@ function make_query_URL(url, input, searchLong) {
if (word[0] == "ALL") {
// special case: search for bugs regardless of status
addAll(statusResolved,bug_status);
- word.shift();
+ do_shift(word);
} else if (word[0] == "OPEN") {
// special case: search for open bugs only
- word.shift();
+ do_shift(word);
} else if (word[0].match("^[+][A-Z]+(,[A-Z]+)*$")) {
// e.g. +DUP,FIX
- w0 = word.shift();
+ w0 = do_shift(word);
prefixes = w0.substring(1).split(",");
if (! matchPrefixes(prefixes,statusResolved,resolutions)) {
- word.unshift(w0);
+ do_unshift(word,w0);
}
} else if (word[0].match("^[A-Z]+(,[A-Z]+)*$")) {
// e.g. NEW,ASSI,REOP,FIX
bug_status = new Array(); // reset
- w0 = word.shift();
+ w0 = do_shift(word);
prefixes = w0.split(",");
if (! matchPrefixes(prefixes,statusAll,resolutions)) {
- word.unshift(w0);
+ do_unshift(word,w0);
bug_status = statusOpen.reverse(); //reset to default bug_status
}
} else {
@@ -320,7 +380,7 @@ function make_query_URL(url, input, searchLong) {
}
if (resolution.length > 0) {
resolution = resolution.reverse();
- resolution.unshift("---");
+ do_unshift(resolution,"---");
addAll(statusResolved,bug_status);
}
bug_status = bug_status.reverse();
@@ -336,11 +396,11 @@ function make_query_URL(url, input, searchLong) {
// end of bug_status & resolution stuff
- var chart = 0;
- var and = 0;
- var or = 0;
+ chart = 0;
+ and = 0;
+ or = 0;
- var negation = false;
+ negation = false;
function negate_comparison_type(type) {
switch(type) {
@@ -351,6 +411,7 @@ function make_query_URL(url, input, searchLong) {
// e.g. "greaterthan"
alert("Can't negate comparison type: `" + type + "'");
abort = true;
+ return "dummy";
}
}
@@ -379,20 +440,20 @@ function make_query_URL(url, input, searchLong) {
}
}
- for (var i=0; i<word.length; i++, chart++) {
+ for (i=0; i<word.length; i++, chart++) {
w = word[i];
negation = false;
- if (w[0] == "-") {
+ if (w.charAt(0) == "-") {
negation = true;
w = w.substring(1);
}
- switch (w[0]) {
+ switch (w.charAt(0)) {
case "+":
alternative = w.substring(1).split(/[|,]/);
- for (var j=0; j<alternative.length; j++)
+ for (j=0; j<alternative.length; j++)
add_chart("short_desc","substring",alternative[j]);
break;
case "#":
@@ -403,14 +464,14 @@ function make_query_URL(url, input, searchLong) {
break;
case ":":
alternative = w.substring(1).split(",");
- for ( var j=0; j<alternative.length; j++) {
+ for (j=0; j<alternative.length; j++) {
add_chart("product","substring",alternative[j]);
add_chart("component","substring",alternative[j]);
}
break;
case "@":
alternative = w.substring(1).split(",");
- for ( var j=0; j<alternative.length; j++)
+ for (j=0; j<alternative.length; j++)
add_chart("assigned_to","substring",alternative[j]);
break;
case "[":
@@ -422,7 +483,7 @@ function make_query_URL(url, input, searchLong) {
break;
default:
alternative=w.split("|");
- for (var j=0; j<alternative.length; j++) {
+ for (j=0; j<alternative.length; j++) {
w=alternative[j];
@@ -434,18 +495,18 @@ function make_query_URL(url, input, searchLong) {
}
// generic field1,field2,field3:value1,value2 notation
if (w.match("^[^:]+[:][^:\/][^:]*$")) {
- parts = w.split(":");
- fields = parts[0].split(/[,]+/);
- values = parts[1].split(/[,]+/);
- for (var k=0; k<fields.length; k++) {
+ colon_separated_parts = w.split(":");
+ fields = colon_separated_parts[0].split(/[,]+/);
+ values = colon_separated_parts[1].split(/[,]+/);
+ for (k=0; k<fields.length; k++) {
field = mapField(fields[k]);
- if (field == undefined) {
+ if (field == no_result) {
alert("`"+fields[k]+"'"+
" is not a valid field name.");
abort = true;
- return undefined;
+ return no_result;
} else {
- for (var l=0; l<values.length; l++) {
+ for (l=0; l<values.length; l++) {
add_chart(field,"substring",values[l]);
}
}
@@ -453,7 +514,7 @@ function make_query_URL(url, input, searchLong) {
continue;
}
comma_separated_words=w.split(/[,]+/);
- for (var k=0; k<comma_separated_words.length; k++) {
+ for (k=0; k<comma_separated_words.length; k++) {
w=comma_separated_words[k];
// platform
@@ -531,7 +592,7 @@ function make_query_URL(url, input, searchLong) {
if (abort == false) {
return searchURL;
} else {
- return undefined;
+ return no_result;
}
}
@@ -542,7 +603,7 @@ function unique_id () {
function ShowURL(mode) {
var input = document.f.id.value;
var searchURL = make_query_URL(bugzilla+"buglist.cgi", input, false);
- if (searchURL != undefined) {
+ if (searchURL != no_result) {
var pieces = searchURL.replace(/[\?]/g,"\n?").replace(/[\&]/g,"\n&");
if (mode == "alert") {
alert(pieces);
@@ -601,7 +662,7 @@ function Search(url, input, searchLong) {
return;
}
var searchURL = make_query_URL(url, inputstring, searchLong);
- if (searchURL != undefined) {
+ if (searchURL != no_result) {
go_to(searchURL);
//window.open(searchURL, "other" );
} else {
@@ -639,6 +700,9 @@ function QuickSearch ()
{
var input = document.f.id.value;
+ //remove leading and trailing whitespace
+ input = input.replace(/^[\s]+/,"").replace(/[\s]+$/,"");
+
if (input == "")
{
//once this _is_ on http://bugzilla.mozilla.org, it should just return;
@@ -664,6 +728,10 @@ function QuickSearch ()
function LoadQuery() {
var input = document.f.id.value;
+
+ //remove leading and trailing whitespace
+ input = input.replace(/^[\s]+/,"").replace(/[\s]+$/,"");
+
Search(bugzilla+"query.cgi",input,false);
return;
}
diff --git a/quips.cgi b/quips.cgi
new file mode 100755
index 000000000..3fde88c9c
--- /dev/null
+++ b/quips.cgi
@@ -0,0 +1,65 @@
+#!/usr/bonsaitools/bin/perl
+# -*- 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): Owen Taylor <otaylor@redhat.com>
+
+use diagnostics;
+use strict;
+use vars ( %::FORM );
+
+require "CGI.pl";
+
+print "Content-type: text/html\n\n";
+
+PutHeader("Quips for the impatient", "Add your own clever headline");
+
+print qq{
+The buglist picks a random quip for the headline, and
+you can extend the quip list. Type in something clever or
+funny or boring and bonk on the button.
+
+<FORM METHOD=POST ACTION="new_comment.cgi">
+<INPUT SIZE=80 NAME="comment"><BR>
+<INPUT TYPE="submit" VALUE="Add This Quip">
+</FORM>
+};
+
+if (exists $::FORM{show_quips}) {
+
+ print qq{
+<H2>Existing headlines</H2>
+};
+
+ if (open (COMMENTS, "<data/comments")) {
+ while (<COMMENTS>) {
+ print $_,"<br>\n";
+ }
+ close COMMENTS;
+ }
+ print "<P>";
+} else {
+ print qq{
+For the impatient, you can
+<A HREF="quips.cgi?show_quips=yes">view the whole quip list</A>.
+};
+ print "<P>";
+}
+
+PutFooter();
diff --git a/reports.cgi b/reports.cgi
index 8fefd50ac..c76a411f7 100755
--- a/reports.cgi
+++ b/reports.cgi
@@ -35,6 +35,8 @@
# daily stats file, so now works independently of collectstats.pl
# version
# Added image caching by date and datasets
+# Myk Melez <myk@mozilla.org):
+# Implemented form field validation and reorganized code.
use diagnostics;
use strict;
@@ -58,7 +60,6 @@ my %bugsperperson;
# while this looks odd/redundant, it allows us to name
# functions differently than the value passed in
-
my %reports =
(
"most_doomed" => \&most_doomed,
@@ -72,19 +73,6 @@ my %reports =
ConnectToDatabase(1);
quietly_check_login();
-print "Content-type: text/html\n";
-
-# Changing attachment to inline to resolve 46897 - zach@zachlipton.com
-print "Content-disposition: inline; filename=bugzilla_report.html\n\n";
-
-# If we're here for the first time, give a banner. Else respect the banner flag.
-if ( (!defined $FORM{'product'}) || ($FORM{'banner'}) ) {
- PutHeader ("Bug Reports")
-}
-else {
- print("<html><head><title>Bug Reports</title></head><body bgcolor=\"#FFFFFF\">");
-}
-
GetVersionTable();
# If the usebuggroups parameter is set, we don't want to list all products.
@@ -103,54 +91,60 @@ if(Param("usebuggroups")) {
push( @myproducts, "-All-", @legal_product );
}
-$FORM{'output'} ||= "most_doomed"; # a reasonable default
-
if (! defined $FORM{'product'}) {
+
+ print "Content-type: text/html\n\n";
+ PutHeader("Bug Reports");
&choose_product;
-}
-else {
+ PutFooter();
+
+} else {
+
+ # For security and correctness, validate the value of the "product" form variable.
+ # Valid values are those products for which the user has permissions which appear
+ # in the "product" drop-down menu on the report generation form.
+ grep($_ eq $FORM{'product'}, @myproducts)
+ || DisplayError("You entered an invalid product name.") && exit;
+
# If usebuggroups is on, we don't want people to be able to view
# reports for products they don't have permissions for...
- if(Param("usebuggroups") &&
- GroupExists($FORM{'product'}) &&
- !UserInGroup($FORM{'product'}))
- {
- print "<H1>Permission denied.</H1>\n";
- print "Sorry; you do not have the permissions necessary to view\n";
- print "reports for this product.\n";
- print "<P>\n";
- PutFooter();
- exit;
- }
+ Param("usebuggroups")
+ && GroupExists($FORM{'product'})
+ && !UserInGroup($FORM{'product'})
+ && DisplayError("You do not have the permissions necessary to view reports for this product.")
+ && exit;
- # we want to be careful about what subroutines
- # can be called from outside. modify %reports
- # accordingly when a new report type is added
-
- if (! exists $reports{$FORM{'output'}}) {
- $FORM{'output'} = "most_doomed"; # a reasonable default
+ # For security and correctness, validate the value of the "output" form variable.
+ # Valid values are the keys from the %reports hash defined above which appear in
+ # the "output" drop-down menu on the report generation form.
+ $FORM{'output'} ||= "most_doomed"; # a reasonable default
+ grep($_ eq $FORM{'output'}, keys %reports)
+ || DisplayError("You entered an invalid output type.")
+ && exit;
+
+ # Output appropriate HTTP response headers
+ print "Content-type: text/html\n";
+ # Changing attachment to inline to resolve 46897 - zach@zachlipton.com
+ print "Content-disposition: inline; filename=bugzilla_report.html\n\n";
+
+ if ($FORM{'banner'}) {
+ PutHeader("Bug Reports");
+ }
+ else {
+ print("<html><head><title>Bug Reports</title></head><body bgcolor=\"#FFFFFF\">");
}
-
- my $f = $reports{$FORM{'output'}};
- if (! defined $f) {
- print "start over, your form data was all messed up.<p>\n";
- foreach (keys %::FORM) {
- print "<font color=blue>$_</font> : " .
- ($FORM{$_} ? $FORM{$_} : "undef") . "<br>\n";
- }
- PutFooter() if $FORM{banner};
- exit;
- }
+ # Execute the appropriate report generation function
+ # (the one whose name is the same as the value of the "output" form variable).
+ &{$reports{$FORM{'output'}}};
- &{$f};
-}
+ # ??? why is this necessary? formatting looks fine without it
+ print "<p>";
-print <<FIN;
-<p>
-FIN
+ PutFooter() if $FORM{banner};
+
+}
-PutFooter() if $FORM{banner};
##################################
@@ -257,7 +251,6 @@ FIN
FIN
#Add this above to get a control for showing the SQL query:
#<input type=checkbox name=showsql value=1> Show SQL<br>
- PutFooter();
}
sub most_doomed {
@@ -485,11 +478,6 @@ FIN
FIN
}
-sub is_legal_product {
- my $product = shift;
- return grep { $_ eq $product} @myproducts;
-}
-
sub daily_stats_filename {
my ($prodname) = @_;
$prodname =~ s/\//-/gs;
@@ -501,10 +489,6 @@ sub show_chart {
# here. Should probably return some decent error message.
return unless $use_gd;
- if (! is_legal_product ($FORM{'product'})) {
- &die_politely ("Unknown product: $FORM{'product'}");
- }
-
if (! $FORM{datasets}) {
die_politely("You didn't select any datasets to plot");
}
@@ -541,23 +525,13 @@ sub chart_image_type {
sub chart_image_name {
my ($data_file, $type) = @_;
- my $id = datasets_id($FORM{datasets});
- my $doy = day_of_year();
+ # Cache charts by generating a unique filename based on what they
+ # show. Charts should be deleted by collectstats.pl nightly.
+ my $id = join ("_", split (":", $FORM{datasets}));
return "${data_file}_${id}.$type";
}
-# Cache charts by generating a unique filename based on what they
-# show. Charts should be deleted by collectstats.pl nightly.
-sub datasets_id {
- # Current method is very long filenames...
- my $longname = "";
- foreach (@_) {
- $longname .= $_;
- }
- return $longname;
-}
-
sub day_of_year {
my ($mday, $month, $year) = (localtime())[3 .. 5];
$month += 1;
diff --git a/sanitycheck.cgi b/sanitycheck.cgi
index 2da7fde2f..c8f628e58 100755
--- a/sanitycheck.cgi
+++ b/sanitycheck.cgi
@@ -27,10 +27,25 @@ require "CGI.pl";
use vars %::FORM;
+ConnectToDatabase();
+
+confirm_login();
+
+# Make sure the user is authorized to access sanitycheck.cgi. Access
+# is restricted to logged-in users who have "editbugs" privileges,
+# which is a reasonable compromise between allowing all users to access
+# the script (creating the potential for denial of service attacks)
+# and restricting access to this installation's administrators (which
+# prevents users with a legitimate interest in Bugzilla integrity
+# from accessing the script).
+UserInGroup("editbugs")
+ || DisplayError("You are not authorized to access this script,
+ which is reserved for users with the ability to edit bugs.")
+ && exit;
+
print "Content-type: text/html\n";
print "\n";
-ConnectToDatabase();
SendSQL("set SQL_BIG_TABLES=1");
my $offervotecacherebuild = 0;
@@ -150,25 +165,6 @@ CrossCheck("profiles", "userid",
["components", "initialowner", "value"],
["components", "initialqacontact", "value", ["0"]]);
-Status("Checking passwords");
-SendSQL("SELECT COUNT(*) FROM profiles WHERE cryptpassword != ENCRYPT(password, left(cryptpassword, 2))");
-my $count = FetchOneColumn();
-if ($count) {
- Alert("$count entries have problems in their crypted password.");
- if ($::FORM{'rebuildpasswords'}) {
- Status("Rebuilding passwords");
- SendSQL("UPDATE profiles
- SET cryptpassword = ENCRYPT(password,
- left(cryptpassword, 2))
- WHERE cryptpassword != ENCRYPT(password,
- left(cryptpassword, 2))");
- Status("Passwords have been rebuilt.");
- } else {
- print qq{<a href="sanitycheck.cgi?rebuildpasswords=1">Click here to rebuild the crypted passwords</a><p>\n};
- }
-}
-
-
Status("Checking groups");
SendSQL("select bit from groups where bit != pow(2, round(log(bit) / log(2)))");
diff --git a/show_activity.cgi b/show_activity.cgi
index d6e388afc..fccc21cd4 100755
--- a/show_activity.cgi
+++ b/show_activity.cgi
@@ -19,21 +19,40 @@
# Rights Reserved.
#
# Contributor(s): Terry Weissman <terry@mozilla.org>
+# Myk Melez <myk@mozilla.org>
use diagnostics;
use strict;
require "CGI.pl";
+ConnectToDatabase();
+
+######################################################################
+# Begin Data/Security Validation
+######################################################################
+
+# Check whether or not the user is currently logged in. This function
+# sets the value of $::usergroupset, the binary number that records
+# the set of groups to which the user belongs and which we can use
+# to determine whether or not the user is authorized to access this bug.
+quietly_check_login();
+
+# Make sure the bug ID is a positive integer representing an existing
+# bug that the user is authorized to access.
+ValidateBugID($::FORM{'id'});
+
+######################################################################
+# End Data/Security Validation
+######################################################################
+
print "Content-type: text/html\n\n";
PutHeader("Changes made to bug $::FORM{'id'}", "Activity log",
"Bug $::FORM{'id'}");
-ConnectToDatabase();
-
DumpBugActivity($::FORM{'id'});
-print "<hr><a href=show_bug.cgi?id=$::FORM{'id'}>Back to bug $::FORM{'id'}</a>\n";
+print qq|<hr><a href="show_bug.cgi?id=$::FORM{'id'}">Back to bug $::FORM{'id'}</a>\n|;
PutFooter();
diff --git a/show_bug.cgi b/show_bug.cgi
index 83baa42b5..eced9cfbe 100755
--- a/show_bug.cgi
+++ b/show_bug.cgi
@@ -29,12 +29,28 @@ ConnectToDatabase();
if ($::FORM{'GoAheadAndLogIn'}) {
confirm_login();
+} else {
+ quietly_check_login();
}
+######################################################################
+# Begin Data/Security Validation
+######################################################################
+
+# Make sure the bug ID is a positive integer representing an existing
+# bug that the user is authorized to access.
+if (defined ($::FORM{'id'})) {
+ ValidateBugID($::FORM{'id'});
+}
+
+######################################################################
+# End Data/Security Validation
+######################################################################
+
print "Content-type: text/html\n";
print "\n";
-if (!defined $::FORM{'id'} || $::FORM{'id'} !~ /^\s*\d+\s*$/) {
+if (!defined $::FORM{'id'}) {
PutHeader("Search by bug number");
print "<FORM METHOD=GET ACTION=\"show_bug.cgi\">\n";
print "You may find a single bug by entering its bug id here: \n";
@@ -47,14 +63,13 @@ if (!defined $::FORM{'id'} || $::FORM{'id'} !~ /^\s*\d+\s*$/) {
GetVersionTable();
-SendSQL("select short_desc, groupset from bugs where bug_id = $::FORM{'id'}");
-my ($summary, $groupset) = FetchSQLData();
-if( $summary && $groupset == 0) {
- $summary = html_quote($summary);
- PutHeader("Bug $::FORM{'id'} - $summary", "Bugzilla Bug $::FORM{'id'}", $summary );
-}else {
- PutHeader("Bugzilla bug $::FORM{'id'}", "Bugzilla Bug", $::FORM{'id'});
-}
+# Get the bug's summary (short description) and display it as
+# the page title.
+SendSQL("SELECT short_desc FROM bugs WHERE bug_id = $::FORM{'id'}");
+my ($summary) = FetchSQLData();
+$summary = html_quote($summary);
+PutHeader("Bug $::FORM{'id'} - $summary", "Bugzilla Bug $::FORM{'id'}", $summary );
+
navigation_header();
print "<HR>\n";
diff --git a/showattachment.cgi b/showattachment.cgi
index 22cfa9087..ae81117e5 100755
--- a/showattachment.cgi
+++ b/showattachment.cgi
@@ -19,6 +19,7 @@
# Rights Reserved.
#
# Contributor(s): Terry Weissman <terry@mozilla.org>
+# Jacob Steenhagen <jake@acutex.net>
use diagnostics;
use strict;
@@ -27,17 +28,24 @@ require "CGI.pl";
ConnectToDatabase();
-my @row;
-if (defined $::FORM{'attach_id'}) {
- SendSQL("select mimetype, thedata from attachments where attach_id =".SqlQuote($::FORM{'attach_id'}));
- @row = FetchSQLData();
+quietly_check_login();
+
+if ($::FORM{attach_id} !~ /^[1-9][0-9]*$/) {
+ DisplayError("Attachment ID should be numeric.");
+ exit;
}
-if (!@row) {
- print "Content-type: text/html\n\n";
- PutHeader("Bad ID");
- print "Please hit back and try again.\n";
+
+SendSQL("select bug_id, mimetype, thedata from attachments where attach_id = $::FORM{'attach_id'}");
+my ($bug_id, $mimetype, $thedata) = FetchSQLData();
+
+if (!$bug_id) {
+ DisplayError("Attachment $::FORM{attach_id} does not exist.");
exit;
}
-print qq{Content-type: $row[0]\n\n$row[1]};
+
+# Make sure the user can see the bug to which this file is attached
+ValidateBugID($bug_id);
+
+print qq{Content-type: $mimetype\n\n$thedata};
diff --git a/showdependencygraph.cgi b/showdependencygraph.cgi
index f15534be3..df377c096 100755
--- a/showdependencygraph.cgi
+++ b/showdependencygraph.cgi
@@ -25,8 +25,28 @@ use strict;
require "CGI.pl";
+ConnectToDatabase();
+
+quietly_check_login();
+
+$::usergroupset = $::usergroupset; # More warning suppression silliness.
+
+######################################################################
+# Begin Data/Security Validation
+######################################################################
+
+# Make sure the bug ID is a positive integer representing an existing
+# bug that the user is authorized to access.
+if (defined $::FORM{'id'}) {
+ ValidateBugID($::FORM{'id'});
+}
+
+######################################################################
+# End Data/Security Validation
+######################################################################
+
my $id = $::FORM{'id'};
-die "Invalid id: $id" unless $id =~ /^\s*\d+\s*$/;
+
my $urlbase = Param("urlbase");
my %seen;
@@ -51,10 +71,6 @@ $::FORM{'rankdir'} = "LR" if !defined $::FORM{'rankdir'};
if (defined $id) {
- ConnectToDatabase();
- quietly_check_login();
- $::usergroupset = $::usergroupset; # More warning suppression silliness.
-
mkdir("data/webdot", 0777);
my $filename = "data/webdot/$$.dot";
diff --git a/showdependencytree.cgi b/showdependencytree.cgi
index 74e2778bc..bab36da61 100755
--- a/showdependencytree.cgi
+++ b/showdependencytree.cgi
@@ -29,6 +29,23 @@ require "CGI.pl";
use vars %::FORM;
+ConnectToDatabase();
+
+quietly_check_login();
+
+$::usergroupset = $::usergroupset; # More warning suppression silliness.
+
+######################################################################
+# Begin Data/Security Validation
+######################################################################
+
+# Make sure the bug ID is a positive integer representing an existing
+# bug that the user is authorized to access.
+ValidateBugID($::FORM{'id'});
+
+######################################################################
+# End Data/Security Validation
+######################################################################
my $id = $::FORM{'id'};
my $linkedid = qq{<a href="show_bug.cgi?id=$id">$id</a>};
@@ -36,12 +53,6 @@ my $linkedid = qq{<a href="show_bug.cgi?id=$id">$id</a>};
print "Content-type: text/html\n\n";
PutHeader("Dependency tree", "Dependency tree", "Bug $linkedid");
-ConnectToDatabase();
-
-quietly_check_login();
-
-$::usergroupset = $::usergroupset; # More warning suppression silliness.
-
my %seen;
sub DumpKids {
diff --git a/showvotes.cgi b/showvotes.cgi
index 8e7dc0d4d..bb87848f0 100755
--- a/showvotes.cgi
+++ b/showvotes.cgi
@@ -26,20 +26,59 @@ use strict;
require "CGI.pl";
+ConnectToDatabase();
+
if (defined $::FORM{'voteon'} || (!defined $::FORM{'bug_id'} &&
!defined $::FORM{'user'})) {
confirm_login();
- ConnectToDatabase();
$::FORM{'user'} = DBNameToIdAndCheck($::COOKIE{'Bugzilla_login'});
+} else {
+ # Check whether or not the user is currently logged in without throwing
+ # an error if the user is not logged in. This function sets the value
+ # of $::usergroupset, the binary number that records the set of groups
+ # to which the user belongs and which gets used in ValidateBugID below
+ # to determine whether or not the user is authorized to access the bug
+ # whose votes are being shown or which is being voted on.
+ quietly_check_login();
+}
+
+################################################################################
+# Begin Data/Security Validation
+################################################################################
+
+# Make sure the bug ID is a positive integer representing an existing
+# bug that the user is authorized to access.
+if (defined $::FORM{'bug_id'}) {
+ ValidateBugID($::FORM{'bug_id'});
}
+# Make sure the bug ID being voted on is a positive integer representing
+# an existing bug that the user is authorized to access.
+if (defined $::FORM{'voteon'}) {
+ ValidateBugID($::FORM{'voteon'});
+}
+
+# Make sure the user ID is a positive integer representing an existing user.
+if (defined $::FORM{'user'}) {
+ $::FORM{'user'} =~ /^([1-9][0-9]*)$/
+ || DisplayError("The user number is invalid.")
+ && exit;
+ SendSQL("SELECT 1 FROM profiles WHERE userid = $::FORM{'user'}");
+ FetchSQLData()
+ || DisplayError("User #$::FORM{'user'} does not exist.")
+ && exit;
+}
+
+################################################################################
+# End Data/Security Validation
+################################################################################
+
print "Content-type: text/html\n\n";
if (defined $::FORM{'bug_id'}) {
my $id = $::FORM{'bug_id'};
my $linkedid = qq{<a href="show_bug.cgi?id=$id">$id</a>};
PutHeader("Show votes", "Show votes", "Bug $linkedid");
- ConnectToDatabase();
SendSQL("select profiles.login_name, votes.who, votes.count from votes, profiles where votes.bug_id = " . SqlQuote($id) . " and profiles.userid = votes.who");
print "<table>\n";
print "<tr><th>Who</th><th>Number of votes</th></tr>\n";
@@ -52,7 +91,6 @@ if (defined $::FORM{'bug_id'}) {
print "</table>";
print "<p>Total votes: $sum<p>\n";
} elsif (defined $::FORM{'user'}) {
- ConnectToDatabase();
quietly_check_login();
GetVersionTable();
my $who = $::FORM{'user'};
diff --git a/syncshadowdb b/syncshadowdb
index 94e492044..4733dbb58 100755
--- a/syncshadowdb
+++ b/syncshadowdb
@@ -32,6 +32,7 @@ require "defparams.pl";
sub sillyness {
my $zz;
+ open SAVEOUT,">/dev/null";
$zz = $::db;
$zz = $::dbwritesallowed;
}
@@ -50,6 +51,9 @@ foreach my $opt (@ARGV) {
} elsif ($opt eq '-syncall') {
$syncall = 1;
$verbose = 1;
+ } elsif ($opt eq '--') {
+ # do nothing - null parameter so we can use
+ # multi-param system() call in globals.pl
} else {
Usage();
}
@@ -68,9 +72,6 @@ sub Verbose ($) {
}
}
}
-
-my $db_name = "bugs";
-require "localconfig";
if (!Param("shadowdb")) {
Verbose("We don't have shadow databases turned on; no syncing performed.");
@@ -97,7 +98,7 @@ if (!FetchOneColumn()) {
exit;
}
-my $shadowtable = "$db_name.shadowlog";
+my $shadowtable = "$::db_name.shadowlog";
if (!$syncall) {
Verbose("Looking for requests to sync the whole database.");
@@ -143,7 +144,7 @@ if ($syncall) {
# into the shadowdb database. Then mark everything in the shadowlog
# as reflected. Only then unlock everything. This sequence causes
# us to be sure not to miss anything or get something twice.
- SendSQL("USE $db_name");
+ SendSQL("USE $::db_name");
SendSQL("SHOW TABLES");
@tables = ();
$query = "LOCK TABLES shadowlog WRITE";
@@ -156,14 +157,23 @@ if ($syncall) {
}
Verbose("Locking entire database");
SendSQL($query);
- my $tablelist = join(' ', @tables);
my $tempfile = "data/tmpsyncshadow.$$";
Verbose("Dumping database to a temp file ($tempfile).");
- system("mysqldump -l -e $db_name $tablelist > $tempfile");
+ my @ARGS = ("-u", $::db_user);
+ if ($::db_pass) { push @ARGS, "-p$::db_pass" }
+ push @ARGS, "-l", "-e", $::db_name, @tables;
+ open SAVEOUT, ">&STDOUT"; # stash the original output stream
+ open STDOUT, ">$tempfile"; # redirect to file
+ select STDOUT; $| = 1; # disable buffering
+ system("mysqldump", @ARGS);
+ open STDOUT, ">&SAVEOUT"; # redirect back to original stream
Verbose("Restoring from tempfile into shadowdb");
- my $extra = "";
+ my $extra = "-u $::db_user";
+ if ($::db_pass) {
+ $extra .= " -p$::db_pass";
+ }
if ($verbose) {
- $extra = "-v";
+ $extra .= " -v";
}
open(MYSQL, "cat $tempfile | mysql $extra " .
Param("shadowdb") . "|") || die "Couldn't do db copy";
diff --git a/template/CVS/Entries b/template/CVS/Entries
deleted file mode 100644
index 178481050..000000000
--- a/template/CVS/Entries
+++ /dev/null
@@ -1 +0,0 @@
-D
diff --git a/template/CVS/Repository b/template/CVS/Repository
deleted file mode 100644
index 02f572838..000000000
--- a/template/CVS/Repository
+++ /dev/null
@@ -1 +0,0 @@
-mozilla/webtools/bugzilla/template
diff --git a/template/CVS/Root b/template/CVS/Root
deleted file mode 100644
index cdb6f4a07..000000000
--- a/template/CVS/Root
+++ /dev/null
@@ -1 +0,0 @@
-:pserver:anonymous@cvs-mirror.mozilla.org:/cvsroot
diff --git a/token.cgi b/token.cgi
new file mode 100755
index 000000000..2fed15ad0
--- /dev/null
+++ b/token.cgi
@@ -0,0 +1,243 @@
+#!/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 Netscape Communications
+# Corporation. Portions created by Netscape are
+# Copyright (C) 1998 Netscape Communications Corporation. All
+# Rights Reserved.
+#
+# Contributor(s): Myk Melez <myk@mozilla.org>
+
+############################################################################
+# Script Initialization
+############################################################################
+
+# Make it harder for us to do dangerous things in Perl.
+use diagnostics;
+use strict;
+
+# Include the Bugzilla CGI and general utility library.
+require "CGI.pl";
+
+# Establish a connection to the database backend.
+ConnectToDatabase();
+
+# Use the "Token" module that contains functions for doing various
+# token-related tasks.
+use Token;
+
+################################################################################
+# Data Validation / Security Authorization
+################################################################################
+
+# Throw an error if the form does not contain an "action" field specifying
+# what the user wants to do.
+$::FORM{'a'}
+ || DisplayError("I could not figure out what you wanted to do.")
+ && exit;
+
+# Assign the action to a global variable.
+$::action = $::FORM{'a'};
+
+# If a token was submitted, make sure it is a valid token that exists in the
+# database and is the correct type for the action being taken.
+if ($::FORM{'t'}) {
+ # Assign the token and its SQL quoted equivalent to global variables.
+ $::token = $::FORM{'t'};
+ $::quotedtoken = SqlQuote($::token);
+
+ # Make sure the token contains only valid characters in the right amount.
+ my $validationerror = ValidatePassword($::token);
+ if ($validationerror) {
+ DisplayError('The token you entered is invalid.');
+ exit;
+ }
+
+ # Make sure the token exists in the database.
+ SendSQL( "SELECT tokentype FROM tokens WHERE token = $::quotedtoken" );
+ (my $tokentype = FetchSQLData())
+ || DisplayError("The token you submitted does not exist.")
+ && exit;
+
+ # Make sure the token is the correct type for the action being taken.
+ if ( grep($::action eq $_ , qw(cfmpw cxlpw chgpw)) && $tokentype ne 'password' ) {
+ DisplayError("That token cannot be used to change your password.");
+ Token::Cancel($::token, "user tried to use token to change password");
+ exit;
+ }
+}
+
+# If the user is requesting a password change, make sure they submitted
+# their login name and it exists in the database.
+if ( $::action eq 'reqpw' ) {
+ defined $::FORM{'loginname'}
+ || DisplayError("You must enter a login name when requesting to change your password.")
+ && exit;
+
+ # Make sure the login name looks like an email address. This function
+ # displays its own error and stops execution if the login name looks wrong.
+ CheckEmailSyntax($::FORM{'loginname'});
+
+ my $quotedloginname = SqlQuote($::FORM{'loginname'});
+ SendSQL("SELECT userid FROM profiles WHERE login_name = $quotedloginname");
+ FetchSQLData()
+ || DisplayError("There is no Bugzilla account with that login name.")
+ && exit;
+}
+
+# If the user is changing their password, make sure they submitted a new
+# password and that the new password is valid.
+if ( $::action eq 'chgpw' ) {
+ defined $::FORM{'password'}
+ && defined $::FORM{'matchpassword'}
+ || DisplayError("You cannot change your password without submitting a new one.")
+ && exit;
+
+ my $passworderror = ValidatePassword($::FORM{'password'}, $::FORM{'matchpassword'});
+ if ( $passworderror ) {
+ DisplayError($passworderror);
+ exit;
+ }
+}
+
+################################################################################
+# Main Body Execution
+################################################################################
+
+# All calls to this script should contain an "action" variable whose value
+# determines what the user wants to do. The code below checks the value of
+# that variable and runs the appropriate code.
+
+if ($::action eq 'reqpw') {
+ requestChangePassword();
+} elsif ($::action eq 'cfmpw') {
+ confirmChangePassword();
+} elsif ($::action eq 'cxlpw') {
+ cancelChangePassword();
+} elsif ($::action eq 'chgpw') {
+ changePassword();
+} else {
+ # If the action that the user wants to take (specified in the "a" form field)
+ # is none of the above listed actions, display an error telling the user
+ # that we do not understand what they would like to do.
+ DisplayError("I could not figure out what you wanted to do.");
+}
+
+exit;
+
+################################################################################
+# Functions
+################################################################################
+
+sub requestChangePassword {
+
+ Token::IssuePasswordToken($::FORM{'loginname'});
+
+ # Return HTTP response headers.
+ print "Content-Type: text/html\n\n";
+
+ PutHeader("Request to Change Password");
+ print qq|
+ <p>
+ A token for changing your password has been emailed to you.
+ Follow the instructions in that email to change your password.
+ </p>
+ |;
+ PutFooter();
+}
+
+sub confirmChangePassword {
+
+ # Return HTTP response headers.
+ print "Content-Type: text/html\n\n";
+
+ PutHeader("Change Password");
+ print qq|
+ <p>
+ To change your password, enter a new password twice:
+ </p>
+ <form method="post" action="token.cgi">
+ <input type="hidden" name="t" value="$::token">
+ <input type="hidden" name="a" value="chgpw">
+ <table>
+ <tr>
+ <th align="right">New Password:</th>
+ <td><input type="password" name="password" size="16" maxlength="16"></td>
+ </tr>
+ <tr>
+ <th align="right">New Password Again:</th>
+ <td><input type="password" name="matchpassword" size="16" maxlength="16"></td>
+ </tr>
+ <tr>
+ <th align="right"> </th>
+ <td><input type="submit" value="Submit"></td>
+ </tr>
+ </table>
+ </form>
+ |;
+ PutFooter();
+}
+
+sub cancelChangePassword {
+
+ Token::Cancel($::token, "user requested cancellation");
+
+ # Return HTTP response headers.
+ print "Content-Type: text/html\n\n";
+
+ PutHeader("Cancel Request to Change Password");
+ print qq|
+ <p>
+ Your request has been cancelled.
+ </p>
+ |;
+ PutFooter();
+}
+
+sub changePassword {
+
+ # Quote the password and token for inclusion into SQL statements.
+ my $cryptedpassword = Crypt($::FORM{'password'});
+ my $quotedpassword = SqlQuote($cryptedpassword);
+
+ # Get the user's ID from the tokens table.
+ SendSQL("SELECT userid FROM tokens WHERE token = $::quotedtoken");
+ my $userid = FetchSQLData();
+
+ # Update the user's password in the profiles table and delete the token
+ # from the tokens table.
+ SendSQL("LOCK TABLES profiles WRITE , tokens WRITE");
+ SendSQL("UPDATE profiles
+ SET cryptpassword = $quotedpassword
+ WHERE userid = $userid");
+ SendSQL("DELETE FROM tokens WHERE token = $::quotedtoken");
+ SendSQL("UNLOCK TABLES");
+
+ # Return HTTP response headers.
+ print "Content-Type: text/html\n\n";
+
+ # Let the user know their password has been changed.
+ PutHeader("Password Changed");
+ print qq|
+ <p>
+ Your password has been changed.
+ </p>
+ |;
+ PutFooter();
+}
+
+
+
+
diff --git a/userprefs.cgi b/userprefs.cgi
index e2fcbf0db..0eeda0e71 100755
--- a/userprefs.cgi
+++ b/userprefs.cgi
@@ -61,6 +61,7 @@ my @emailFlags = (
);
my $defaultEmailFlagString =
+ 'ExcludeSelf~' . 'on~' .
'emailOwnerRemoveme~' . 'on~' .
'emailOwnerComments~' . 'on~' .
@@ -100,7 +101,7 @@ my $defaultEmailFlagString =
'emailVoterRemoveme~' . 'on~' .
'emailVoterComments~' . 'on~' .
- 'emailVoterAttachemnts~' . 'on~' .
+ 'emailVoterAttachments~' . 'on~' .
'emailVoterStatus~' . 'on~' .
'emailVoterResolved~' . 'on~' .
'emailVoterKeywords~' . 'on~' .
@@ -129,9 +130,10 @@ sub ShowAccount {
my ($realname) = (FetchSQLData());
$realname = value_quote($realname);
-
+
EmitEntry("Old password",
- qq{<input type=password name="oldpwd">});
+ qq|<input type=hidden name="Bugzilla_login" value="$::COOKIE{Bugzilla_login}">| .
+ qq|<input type=password name="Bugzilla_password">|);
EmitEntry("New password",
qq{<input type=password name="pwd1">});
EmitEntry("Re-enter new password",
@@ -141,14 +143,17 @@ sub ShowAccount {
}
sub SaveAccount {
- if ($::FORM{'oldpwd'} ne ""
+ if ($::FORM{'Bugzilla_password'} ne ""
|| $::FORM{'pwd1'} ne "" || $::FORM{'pwd2'} ne "") {
- my $old = SqlQuote($::FORM{'oldpwd'});
+ my $old = SqlQuote($::FORM{'Bugzilla_password'});
my $pwd1 = SqlQuote($::FORM{'pwd1'});
my $pwd2 = SqlQuote($::FORM{'pwd2'});
- SendSQL("SELECT cryptpassword = ENCRYPT($old, LEFT(cryptpassword, 2)) " .
- "FROM profiles WHERE userid = $userid");
- if (!FetchOneColumn()) {
+ SendSQL("SELECT cryptpassword FROM profiles WHERE userid = $userid");
+ my $oldcryptedpwd = FetchOneColumn();
+ if ( !$oldcryptedpwd ) {
+ Error("I was unable to retrieve your old password from the database.");
+ }
+ if ( crypt($::FORM{'Bugzilla_password'}, $oldcryptedpwd) ne $oldcryptedpwd ) {
Error("You did not enter your old password correctly.");
}
if ($pwd1 ne $pwd2) {
@@ -157,9 +162,13 @@ sub SaveAccount {
if ($::FORM{'pwd1'} eq '') {
Error("You must enter a new password.");
}
- SendSQL("UPDATE profiles SET password = $pwd1, " .
- "cryptpassword = ENCRYPT($pwd1) " .
- "WHERE userid = $userid");
+ my $passworderror = ValidatePassword($::FORM{'pwd1'});
+ Error($passworderror) if $passworderror;
+
+ my $cryptedpassword = SqlQuote(Crypt($::FORM{'pwd1'}));
+ SendSQL("UPDATE profiles
+ SET cryptpassword = $cryptedpassword
+ WHERE userid = $userid");
}
SendSQL("UPDATE profiles SET " .
"realname = " . SqlQuote($::FORM{'realname'}) .
@@ -180,103 +189,28 @@ sub setEmailFlags ($) {
sub ShowEmailOptions () {
- SendSQL("SELECT emailnotification, newemailtech FROM profiles " .
- "WHERE userid = $userid");
- my ($emailnotification, $dbNewEmailTech) = (FetchSQLData());
-
- # Override the database value with the current form value
- # if the disable/enable button has been pressed.
- if ( defined $::FORM{'newEmailTech'} ) {
-
- # If the user has clicked on 'Disable New Email Tech',
- # clear out their email flag preferences.
- if ($dbNewEmailTech == 1) {
- setEmailFlags('');
- }
-
- $showNewEmailTech = $::FORM{'newEmailTech'};
- } else {
- $showNewEmailTech = $dbNewEmailTech;
- }
-
- #print "<BR>database newemailtech = $showNewEmailTech<br>";
-
- my $qacontactpart = "";
- if (Param('useqacontact')) {
- $qacontactpart = ", the current QA Contact";
- }
-
- if ($showNewEmailTech==0) {
- print <<"--endquote--";
-<TABLE>
-<TR><TD COLSPAN="2">
-Bugzilla will send out email notification of changed bugs to
-the current owner, the Reporter of the bug$qacontactpart, and anyone on the
-CC list. However, you can suppress some of those email notifications.
-On which of these bugs would you like email notification of changes?
-</TD></TR>
---endquote--
- my $entry =
- BuildPulldown("emailnotification",
- [["ExcludeSelfChanges",
- "All qualifying bugs except those which I change"],
- ["CConly",
- "Only those bugs which I am listed on the CC line"],
- ["All",
- "All qualifying bugs"]],
- $emailnotification);
- EmitEntry("Notify me of changes to", $entry);
- print "</TABLE>";
- }
-
- if (Param("newemailtech")) {
- print qq{
-<TR><TD COLSPAN="2"><HR></TD></TR>
-<TR><TD COLSPAN="2"><FONT COLOR="red">Updated!</FONT>
-Bugzilla's new standard email notification scheme allows for the use of
-features such as watching other users and selecting which bug changes you get
-mail about. Although it's still possible to use the old notification scheme,
-this isn't recommended, because the old scheme is no longer
-supported and will be going away in an upcoming version of Bugzilla.
-<FONT COLOR="red">Note that after clicking the link below, you must still click
-on the <B>Submit Changes</B> button in order for your email tech change to be saved.</FONT>
-</TD></TR>};
-
- if ($showNewEmailTech == 1) {
- print qq{
- <tr><td colspan=2><center>
- <A HREF="userprefs.cgi?bank=diffs&newEmailTech=0">Disable New Email Tech</A>
- </center></td></tr>};
- } else {
- print qq{<tr><td colspan=2><center><A HREF="userprefs.cgi?bank=diffs&newEmailTech=1">Enable New Email Tech</A></center></td></tr>};
- }
-
- if (Param("supportwatchers") && $showNewEmailTech == 1) {
-
- my $watcheduserSet = new RelationSet;
- $watcheduserSet->mergeFromDB("SELECT watched FROM watch WHERE" .
+ if (Param("supportwatchers")) {
+ my $watcheduserSet = new RelationSet;
+ $watcheduserSet->mergeFromDB("SELECT watched FROM watch WHERE" .
" watcher=$userid");
- my $watchedusers = $watcheduserSet->toString();
+ my $watchedusers = $watcheduserSet->toString();
- print qq{
+ print qq{
<TR><TD COLSPAN="4"><HR></TD></TR>
<TR><TD COLSPAN="4">
-<FONT COLOR="red">New Email Tech Feature: </FONT>If you want to help cover for someone when they're on vacation, or if
+If you want to help cover for someone when they're on vacation, or if
you need to do the QA related to all of their bugs, you can tell bugzilla
to send mail related to their bugs to you also. List the email addresses
of any users you wish to watch here, separated by commas.
</TD></TR>};
- EmitEntry("Users to watch",
+ EmitEntry("Users to watch",
qq{<INPUT SIZE=35 NAME="watchedusers" VALUE="$watchedusers">});
- }
+ }
- print qq{<TR><TD COLSPAN="2"><HR></TD></TR>};
+ print qq{<TR><TD COLSPAN="2"><HR></TD></TR>};
- if ($showNewEmailTech == 1) {
- showAdvancedEmailFilterOptions();
- }
- }
+ showAdvancedEmailFilterOptions();
print qq {
<TABLE CELLSPACING="0" CELLPADDING="10" BORDER=0 WIDTH="100%">
@@ -296,38 +230,25 @@ sub showAdvancedEmailFilterOptions () {
</center>
</TD></TR><tr><td colspan="2">
<p>
- <center><FONT COLOR="red">New Email Tech Feature:</FONT>
- Filter email notifications for <b>modified</b>
- bugs (does not effect new bug email notices).
+ <center>
+ If you don't like getting a notification for "trivial"
+ changes to bugs, you can use the settings below to
+ filter some (or even all) notifications.
</center></td></tr></table>
<hr width=800 align=center>
};
- SendSQL("SELECT emailflags, emailnotification FROM profiles WHERE " .
- "userid = $userid");
+ SendSQL("SELECT emailflags FROM profiles WHERE userid = $userid");
- ($flags, $notify) = FetchSQLData();
+ ($flags) = FetchSQLData();
# if the emailflags haven't been set before, that means that this user
# hasn't been to (the email pane of?) userprefs.cgi since the change to
- # use emailflags. create a default flagset for them, mostly based on
- # static defaults, but setting ExcludeSelf based on the old
- # emailnotification column.
+ # use emailflags. create a default flagset for them, based on
+ # static defaults.
#
if ( !$flags ) {
-
- if ( !$notify ) {
- confess("neither \$flags nor \$notify was set");
- }
-
- my $notifyString;
- if ( $notify eq 'ExcludeSelfChanges' ) {
- $notifyString = "ExcludeSelf~on~";
- } else {
- $notifyString = "ExcludeSelf~~";
- }
-
- $flags = $notifyString . $defaultEmailFlagString;
+ $flags = $defaultEmailFlagString;
setEmailFlags($flags);
}
@@ -440,52 +361,36 @@ sub SaveEmailOptions () {
my $useNewEmailTech = $::FORM{'savedEmailTech'};
my $updateString;
- if ($useNewEmailTech == 0) {
-
- # we force the NEW email filter entry to allow all email
- # (empty string defaults to allowing all email).
- $updateString = '';
-
+ if ( defined $::FORM{'ExcludeSelf'}) {
+ $updateString .= 'ExcludeSelf~on';
} else {
- if ( defined $::FORM{'ExcludeSelf'}) {
- $updateString .= 'ExcludeSelf~on';
- } else {
- $updateString .= 'ExcludeSelf~';
- }
- my @tmpGroups = @emailGroups;
-
- while ((my $groupName,my $groupText) = splice(@tmpGroups,0,2) ) {
+ $updateString .= 'ExcludeSelf~';
+ }
+ my @tmpGroups = @emailGroups;
- my @tmpFlags = @emailFlags;
+ while ((my $groupName,my $groupText) = splice(@tmpGroups,0,2) ) {
- while ((my $flagName,my $flagText) = splice(@tmpFlags,0,2) ) {
+ my @tmpFlags = @emailFlags;
- my $entry = 'email' . $groupName . $flagName;
- my $entryValue;
+ while ((my $flagName,my $flagText) = splice(@tmpFlags,0,2) ) {
- if (!defined $::FORM{$entry} ) {
- $entryValue = "";
- } else {
- $entryValue = $::FORM{$entry};
- }
+ my $entry = 'email' . $groupName . $flagName;
+ my $entryValue;
- $updateString .= '~' . $entry . '~' . $entryValue;
+ if (!defined $::FORM{$entry} ) {
+ $entryValue = "";
+ } else {
+ $entryValue = $::FORM{$entry};
}
- }
- # we force the OLD email tech flag to allow all email
- $::FORM{'emailnotification'} = "All";
+ $updateString .= '~' . $entry . '~' . $entryValue;
+ }
}
#open(FID,">updateString");
#print qq{UPDATE STRING: $updateString <br>};
#close(FID);
- SendSQL("UPDATE profiles SET emailnotification = "
- . SqlQuote($::FORM{'emailnotification'})
- . ", newemailtech = $useNewEmailTech "
- . "WHERE userid = $userid" );
-
SendSQL("UPDATE profiles SET emailflags = " .
SqlQuote($updateString) . " WHERE userid = $userid");
@@ -493,9 +398,6 @@ sub SaveEmailOptions () {
if (exists $::FORM{'watchedusers'}) {
- Error ('You must have "New email tech" set to watch someone')
- if ( $::FORM{'watchedusers'} ne "" && $useNewEmailTech == 0);
-
# Just in case. Note that this much locking is actually overkill:
# we don't really care if anyone reads the watch table. So
# some small amount of contention could be gotten rid of by
--
GitLab