Bug 445061 - Don't require network access to build the docs

r=colin.olgilvie


git-svn-id: svn://10.0.0.236/branches/BUGZILLA-2_16-BRANCH@253018 18797224-902f-48f8-a5cc-f745e15eee43

mozilla/webtools/bugzilla/Attachment.pm

@@ -43,7 +43,7 @@ sub query
   # "attachments" variable.
   my ($bugid) = @_;
 
-  my $in_editbugs = &::UserInGroup($::userid, "editbugs");
+  my $in_editbugs = &::UserInGroup("editbugs");
 
   # Retrieve a list of attachments for this bug and write them into an array
   # of hashes in which each hash represents a single attachment.

mozilla/webtools/bugzilla/Bug.pm

@@ -36,8 +36,8 @@ my %ok_field;
 for my $key (qw (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 
-                delta_ts votes whoid comment query error) ){
+                qa_contact status_whiteboard creation_ts groupset 
+                delta_ts votes whoid usergroupset comment query error) ){
     $ok_field{$key}++;
     }
 
@@ -101,65 +101,51 @@ sub initBug  {
 
 
   $self->{'whoid'} = $user_id;
+  &::SendSQL("SELECT groupset FROM profiles WHERE userid=$self->{'whoid'}");
+  my $usergroupset = &::FetchOneColumn();
+  if (!$usergroupset) { $usergroupset = '0' }
+  $self->{'usergroupset'} = $usergroupset;
 
-  # First check that we can see it
-  if (!&::CanSeeBug($bug_id, $user_id)) {
-      # is it not there, or are we just forbidden to see it?
-      &::SendSQL("SELECT bug_id FROM bugs WHERE bug_id = $bug_id");
-      if (&::FetchSQLData()) {
-          $self->{'error'} = "NotPermitted";
-      } else {
-          $self->{'error'} = "NotFound";
-      }
-      $self->{'bug_id'} = $bug_id;
-      return $self;
-  }
-
-    my $query = "";
-    if ($::driver eq 'mysql') {
-        $query = "
+  my $query = "
     select
       bugs.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, date_format(creation_ts,'%Y-%m-%d %H:%i'),
-      delta_ts, sum(votes.count)
+      groupset, delta_ts, ifnull(sum(votes.count),0)
     from bugs left join votes using(bug_id)
     where bugs.bug_id = $bug_id
     group by bugs.bug_id";
-    } elsif ($::driver eq 'Pg') {
-        $query = "
-    select
-      bugs.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,
-      delta_ts, sum(votes.count)
-    from bugs left join votes using(bug_id)
-    where bugs.bug_id = $bug_id
-    group by bugs.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, delta_ts";
-    }
 
-  &::SendSQL($query);
+  &::SendSQL(&::SelectVisible($query, $user_id, $usergroupset));
   my @row;
 
-  @row = &::FetchSQLData();
-  my $count = 0;
-  my %fields;
-  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",
-                     "delta_ts", "votes") {
-      $fields{$field} = shift @row;
-      if ($fields{$field}) {
-          $self->{$field} = $fields{$field};
-      }
-      $count++;
+  if (@row = &::FetchSQLData()) {
+    my $count = 0;
+    my %fields;
+    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") {
+        $fields{$field} = shift @row;
+        if ($fields{$field}) {
+            $self->{$field} = $fields{$field};
+        }
+        $count++;
+    }
+  } else {
+    &::SendSQL("select groupset from bugs where bug_id = $bug_id");
+    if (@row = &::FetchSQLData()) {
+      $self->{'bug_id'} = $bug_id;
+      $self->{'error'} = "NotPermitted";
+      return $self;
+    } else {
+      $self->{'bug_id'} = $bug_id;
+      $self->{'error'} = "NotFound";
+      return $self;
+    }
   }
 
   $self->{'assigned_to'} = &::DBID_to_name($self->{'assigned_to'});
@@ -363,14 +349,24 @@ sub XML_Footer {
 sub UserInGroup {
     my $self = shift();
     my ($groupname) = (@_);
-    return &::UserInGroup($self->{'whoid'}, $groupname);
+    if ($self->{'usergroupset'} eq "0") {
+        return 0;
+    }
+    &::ConnectToDatabase();
+    &::SendSQL("select (bit & $self->{'usergroupset'}) != 0 from groups where name = " 
+           . &::SqlQuote($groupname));
+    my $bit = &::FetchOneColumn();
+    if ($bit) {
+        return 1;
+    }
+    return 0;
 }
 
 sub CanChangeField {
    my $self = shift();
    my ($f, $oldvalue, $newvalue) = (@_);
-   my $UserInEditGroup = -1;
-   my $UserInCanConfirmGroup = -1;
+   my $UserInEditGroupSet = -1;
+   my $UserInCanConfirmGroupSet = -1;
    my $ownerid;
    my $reporterid;
    my $qacontactid;
@@ -393,10 +389,10 @@ sub CanChangeField {
     if ($f =~ /^longdesc/) {
         return 1;
     }
-    if ($UserInEditGroup < 0) {
-        $UserInEditGroup = UserInGroup($self, "editbugs");
+    if ($UserInEditGroupSet < 0) {
+        $UserInEditGroupSet = UserInGroup($self, "editbugs");
     }
-    if ($UserInEditGroup) {
+    if ($UserInEditGroupSet) {
         return 1;
     }
     &::SendSQL("SELECT reporter, assigned_to, qa_contact FROM bugs " .
@@ -417,10 +413,10 @@ sub CanChangeField {
         # group?  Or, has it ever been confirmed?  If not, then this
         # isn't legal.
 
-        if ($UserInCanConfirmGroup < 0) {
-            $UserInCanConfirmGroup = &::UserInGroup($self->{'whoid'},"canconfirm");
+        if ($UserInCanConfirmGroupSet < 0) {
+            $UserInCanConfirmGroupSet = &::UserInGroup("canconfirm");
         }
-        if ($UserInCanConfirmGroup) {
+        if ($UserInCanConfirmGroupSet) {
             return 1;
         }
         &::SendSQL("SELECT everconfirmed FROM bugs WHERE bug_id = $self->{'bug_id'}");
@@ -441,18 +437,14 @@ sub Collision {
     my $self = shift();
     my $write = "WRITE";        # Might want to make a param to control
                                 # whether we do LOW_PRIORITY ...
-    if ($::driver eq 'mysql') {
-        &::SendSQL("LOCK TABLES bugs $write, bugs_activity $write, cc $write, " .
-                "cc AS selectVisible_cc $write, " .
-                "profiles $write, dependencies $write, votes $write, " .
-                "keywords $write, longdescs $write, fielddefs $write, " .
-                "keyworddefs READ, groups READ, attachments READ, products READ");
-    } 
+    &::SendSQL("LOCK TABLES bugs $write, bugs_activity $write, cc $write, " .
+               "cc AS selectVisible_cc $write, " .
+            "profiles $write, dependencies $write, votes $write, " .
+            "keywords $write, longdescs $write, fielddefs $write, " .
+            "keyworddefs READ, groups READ, attachments READ, products READ");
     &::SendSQL("SELECT delta_ts FROM bugs where bug_id=$self->{'bug_id'}");
     my $delta_ts = &::FetchOneColumn();
-    if ($::driver eq 'mysql') {
-        &::SendSQL("unlock tables");
-    }
+    &::SendSQL("unlock tables");
     if ($self->{'delta_ts'} ne $delta_ts) {
        return 1;
     }

mozilla/webtools/bugzilla/CGI.pl

@@ -58,7 +58,7 @@ use vars qw($template $vars);
 # to the user about the downtime.  (do)editparams.cgi is exempted from
 # this message, of course, since it needs to be available in order for
 # the administrator to open Bugzilla back up.
-if (Param("shutdownhtml") && $0 !~ m:[\\/](do)?editparams.cgi$:) {
+if (Param("shutdownhtml") && $0 !~ m:(^|[\\/])(do)?editparams\.cgi$:) {
     # The shut down message we are going to display to the user.
     $::vars->{'title'} = "Bugzilla is Down";
     $::vars->{'h1'} = "Bugzilla is Down";
@@ -80,7 +80,7 @@ if (Param("shutdownhtml") && $0 !~ m:[\\/](do)?editparams.cgi$:) {
 sub url_decode {
     my ($todecode) = (@_);
     $todecode =~ tr/+/ /;       # pluses become spaces
-    $todecode =~ s/%([0-9a-fA-F]{2})/pack("c",hex($1))/ge;
+    $todecode =~ s/%([0-9a-fA-F]{2})/pack("C",hex($1))/ge;
     return $todecode;
 }
 
@@ -92,34 +92,24 @@ sub url_quote {
 }
 
 sub ParseUrlString {
-    # We don't want to detaint the user supplied data...
-    use re 'taint';
-
     my ($buffer, $f, $m) = (@_);
     undef %$f;
     undef %$m;
 
     my %isnull;
-    my $remaining = $buffer;
-    while ($remaining ne "") {
-        my $item;
-        if ($remaining =~ /^([^&]*)&(.*)$/) {
-            $item = $1;
-            $remaining = $2;
-        } else {
-            $item = $remaining;
-            $remaining = "";
-        }
 
-        my $name;
-        my $value;
-        if ($item =~ /^([^=]*)=(.*)$/) {
-            $name = $1;
-            $value = url_decode($2);
-        } else {
-            $name = $item;
-            $value = "";
-        }
+    # We must make sure that the CGI params remain tainted.
+    # This means that if for some reason you want to make this code
+    # use a regexp and $1, $2, ... (or use a helper function which does so)
+    # you must |use re 'taint'| _and_ make sure that you don't run into
+    # http://bugs.perl.org/perlbug.cgi?req=bug_id&bug_id=20020704.001
+    my @args = split('&', $buffer);
+    foreach my $arg (@args) {
+        my ($name, $value) = split('=', $arg, 2);
+        $value = '' if not defined $value;
+
+        $name = url_decode($name);
+        $value = url_decode($value);
 
         if ($value ne "") {
             if (defined $f->{$name}) {
@@ -254,42 +244,35 @@ sub ValidateBugID {
     # database, and that the user is authorized to access that bug.
     # We detaint the number here, too
 
-    # Make sure the bug number is a positive integer.
-    # Whitespace can be ignored because the SQL server will ignore it.
     $_[0] = trim($_[0]); # Allow whitespace arround the number
     detaint_natural($_[0])
-        || DisplayError("The bug number is invalid. If you are trying to use " .
+      || DisplayError("The bug number is invalid. If you are trying to use " .
                       "QuickSearch, you need to enable JavaScript in your " .
                       "browser. To help us fix this limitation, look " .
                       "<a href=\"http://bugzilla.mozilla.org/show_bug.cgi?id=70907\">here</a>.") 
       && exit;
 
-    # Only assign vars here, because we ahve to detaint the reference so that
-    # it passses taint checks in the caller
-    my ($id, $userid) = @_;
+    my ($id) = @_;
 
-    # Users are authorized to access bugs if they are a member of one of
-    # groups to which the bug is restricted.    
-    # 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.
+    # 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.
 
     # First check that the bug exists
     SendSQL("SELECT bug_id FROM bugs WHERE bug_id = $id");
 
     FetchOneColumn()
       || DisplayError("Bug #$id does not exist.")
-      && exit;
+        && exit;
 
-    return if CanSeeBug($id, $userid);
+    return if CanSeeBug($id, $::userid, $::usergroupset);
 
     # 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) {
+    if ($::userid) {
         DisplayError("You are not authorized to access bug #$id.");
     } else {
         DisplayError(
@@ -299,6 +282,7 @@ sub ValidateBugID {
         );
     }
     exit;
+
 }
 
 sub ValidateComment {
@@ -441,14 +425,15 @@ sub PasswordForLogin {
     return $result;
 }
 
-sub quietly_check_login {
-    my ($userid, $loginname, $ok, $disabledtext);
-    $userid = 0;
+sub quietly_check_login() {
+    $::usergroupset = '0';
+    my $loginok = 0;
     $::disabledreason = '';
+    $::userid = 0;
     if (defined $::COOKIE{"Bugzilla_login"} &&
         defined $::COOKIE{"Bugzilla_logincookie"}) {
         ConnectToDatabase();
-        SendSQL("SELECT profiles.userid, " .
+        SendSQL("SELECT profiles.userid, profiles.groupset, " .
                 "profiles.login_name, " .
                 "profiles.login_name = " .
                 SqlQuote($::COOKIE{"Bugzilla_login"}) .
@@ -460,21 +445,21 @@ sub quietly_check_login {
                 " AND profiles.userid = logincookies.userid");
         my @row;
         if (@row = FetchSQLData()) {
-            ($userid, $loginname, $ok, $disabledtext) = (@row);
+            my ($userid, $groupset, $loginname, $ok, $disabledtext) = (@row);
             if ($ok) {
                 if ($disabledtext eq '') {
+                    $loginok = 1;
+                    $::userid = $userid;
+                    $::usergroupset = $groupset;
                     $::COOKIE{"Bugzilla_login"} = $loginname; # Makes sure case
                                                               # is in
                                                               # canonical form.
                     # We've just verified that this is ok
                     detaint_natural($::COOKIE{"Bugzilla_logincookie"});
                 } else {
-                    $userid = 0;
                     $::disabledreason = $disabledtext;
                 }
-            } else {
-                $userid = 0;
-            } 
+            }
         }
     }
     # if 'who' is passed in, verify that it's a good value
@@ -482,12 +467,13 @@ sub quietly_check_login {
         my $whoid = DBname_to_id($::FORM{'who'});
         delete $::FORM{'who'} unless $whoid;
     }
-    if (!$userid) {
+    if (!$loginok) {
         delete $::COOKIE{"Bugzilla_login"};
     }
-
-    $vars->{'user'} = GetUserInfo($userid);
-    return $userid;
+                    
+    $vars->{'user'} = GetUserInfo($::userid);
+    
+    return $loginok;
 }
 
 # Populate a hash with information about this user. 
@@ -503,10 +489,10 @@ sub GetUserInfo {
     $user{'login'} = $::COOKIE{"Bugzilla_login"};
     $user{'userid'} = $userid;
     
-    SendSQL("SELECT mybugslink, realname FROM profiles " . 
-            "WHERE userid = $userid");
-    ($user{'showmybugslink'}, $user{'realname'}) =
-                                                                 FetchSQLData();
+    SendSQL("SELECT mybugslink, realname, groupset, blessgroupset " . 
+            "FROM profiles WHERE userid = $userid");
+    ($user{'showmybugslink'}, $user{'realname'}, $user{'groupset'},
+                                       $user{'blessgroupset'}) = FetchSQLData();
 
     SendSQL("SELECT name, query, linkinfooter FROM namedqueries " .
             "WHERE userid = $userid");
@@ -519,12 +505,10 @@ sub GetUserInfo {
 
     $user{'queries'} = \@queries;
 
-    SendSQL("SELECT groups.name FROM groups, user_group_map " . 
-            "WHERE groups.group_id = user_group_map.group_id " .
-            "AND user_group_map.user_id = $userid");
+    SendSQL("select name, (bit & $user{'groupset'}) != 0 from groups");
     while (MoreSQLData()) {
-        my ($name) = FetchSQLData();
-        $groups{$name} = 1;
+        my ($name, $bit) = FetchSQLData();    
+        $groups{$name} = $bit;
     }
 
     $user{'groups'} = \%groups;
@@ -766,21 +750,22 @@ sub confirm_login {
      if($enteredlogin ne "") {
        $::COOKIE{"Bugzilla_login"} = $enteredlogin;
        SendSQL("insert into logincookies (userid,ipaddr) values (@{[DBNameToIdAndCheck($enteredlogin)]}, @{[SqlQuote($ENV{'REMOTE_ADDR'})]})");
-       my $logincookie = CurrId("logincookies_cookie_seq");
+       SendSQL("select LAST_INSERT_ID()");
+       my $logincookie = FetchOneColumn();
 
        $::COOKIE{"Bugzilla_logincookie"} = $logincookie;
        my $cookiepath = Param("cookiepath");
-       print "Set-Cookie: Bugzilla_login=$enteredlogin ; path=$cookiepath; expires=Sun, 30-Jun-2029 00:00:00 GMT\n";
-       print "Set-Cookie: Bugzilla_logincookie=$logincookie ; path=$cookiepath; expires=Sun, 30-Jun-2029 00:00:00 GMT\n";
+       print "Set-Cookie: Bugzilla_login=$enteredlogin ; path=$cookiepath; expires=Sat, 30-Jun-2029 00:00:00 GMT\n";
+       print "Set-Cookie: Bugzilla_logincookie=$logincookie ; path=$cookiepath; expires=Sat, 30-Jun-2029 00:00:00 GMT\n";
     }
 
-    my $userid = quietly_check_login();
+    my $loginok = quietly_check_login();
 
-    if (!$userid) {
+    if ($loginok != 1) {
         if ($::disabledreason) {
             my $cookiepath = Param("cookiepath");
-            print "Set-Cookie: Bugzilla_login= ; path=$cookiepath; expires=Sun, 30-Jun-80 00:00:00 GMT
-Set-Cookie: Bugzilla_logincookie= ; path=$cookiepath; expires=Sun, 30-Jun-80 00:00:00 GMT
+            print "Set-Cookie: Bugzilla_login= ; path=$cookiepath; expires=Tue, 15-Sep-1998 21:49:00 GMT
+Set-Cookie: Bugzilla_logincookie= ; path=$cookiepath; expires=Tue, 15-Sep-1998 21:49:00 GMT
 Content-type: text/html
 
 ";
@@ -879,13 +864,8 @@ Content-type: text/html
         # crufty junk in the logincookies table.  Get rid of any entry
         # that hasn't been used in a month.
         if ($::dbwritesallowed) {
-            if ($::driver eq 'mysql') {
-                SendSQL("DELETE FROM logincookies " .
-                        "WHERE TO_DAYS(NOW()) - TO_DAYS(lastused) > 30");
-            } elsif ($::driver eq 'Pg') {
-                 SendSQL("DELETE FROM logincookies " .
-                         "WHERE NOW() - lastused > 30");
-            }
+            SendSQL("DELETE FROM logincookies " .
+                    "WHERE TO_DAYS(NOW()) - TO_DAYS(lastused) > 30");
         }
 
         
@@ -895,10 +875,10 @@ Content-type: text/html
 
     # Update the timestamp on our logincookie, so it'll keep on working.
     if ($::dbwritesallowed) {
-        SendSQL("UPDATE logincookies SET lastused = NULL " .
+        SendSQL("UPDATE logincookies SET lastused = null " .
                 "WHERE cookie = $::COOKIE{'Bugzilla_logincookie'}");
     }
-    return $userid;
+    return $::userid;
 }
 
 sub PutHeader {
@@ -930,8 +910,6 @@ sub DisplayError {
   $template->process("global/user-error.html.tmpl", $vars)
     || ThrowTemplateError($template->error());   
 
-  RollBack();
-  
   return 1;
 }
 
@@ -941,16 +919,14 @@ sub ThrowCodeError {
   ($vars->{'error'}, $vars->{'variables'}, my $unlock_tables) = (@_);
   $vars->{'title'} = "Code Error";
 
-  SendSQL("UNLOCK TABLES") if $unlock_tables && $::driver eq 'mysql';
+  SendSQL("UNLOCK TABLES") if $unlock_tables;
   
   # We may optionally log something to file here.
   
   print "Content-type: text/html\n\n" if !$vars->{'header_done'};
   $template->process("global/code-error.html.tmpl", $vars)
     || ThrowTemplateError($template->error());
- 
-  RollBack();
-   
+    
   exit;
 }
 
@@ -959,7 +935,7 @@ sub ThrowUserError {
   ($vars->{'error'}, $vars->{'title'}, my $unlock_tables) = (@_);
   $vars->{'title'} ||= "Error";
 
-  SendSQL("UNLOCK TABLES") if $unlock_tables && $::driver eq 'mysql';
+  SendSQL("UNLOCK TABLES") if $unlock_tables;
   
   print "Content-type: text/html\n\n" if !$vars->{'header_done'};
   $template->process("global/user-error.html.tmpl", $vars)
@@ -989,7 +965,11 @@ sub ThrowTemplateError {
             time this message appeared.
           </p>
           <script> <!--
-            document.write("<p>URL: " + document.location + "</p>");
+            document.write("<p>URL: " +
+                           document.location.href.replace(/&/g, "&amp;")
+                                                 .replace(/</g, "&lt;")
+                                                 .replace(/>/g, "&gt;") +
+                           "</p>");
           // -->
           </script>
           <p>Template->process() failed twice.<br>
@@ -1042,48 +1022,25 @@ sub CheckIfVotedConfirmed {
 sub GetBugActivity {
     my ($id, $starttime) = (@_);
     my $datepart = "";
-    my $query = "";
 
     die "Invalid id: $id" unless $id=~/^\s*\d+\s*$/;
 
     if (defined $starttime) {
         $datepart = "and bugs_activity.bug_when > " . SqlQuote($starttime);
     }
-        
-    if ($::driver eq 'mysql') {
-        $query = "
-        SELECT 
-            IFNULL(fielddefs.name, bugs_activity.fieldid), 
-            bugs_activity.attach_id,
-            bugs_activity.bug_when, ";
-
-    } elsif ($::driver eq 'Pg') {
-#        $query = "
-#        SELECT 
-#            COALESCE(fielddefs.name, chr(bugs_activity.fieldid)), 
-#            bugs_activity.attach_id,
-#            TO_CHAR(bugs_activity.bug_when, 'YYYY-MM-DD'), ";
-        $query = "
-        SELECT 
-            bugs_activity.fieldid, 
-            bugs_activity.attach_id,
-            TO_CHAR(bugs_activity.bug_when, 'YYYY-MM-DD'), ";
-
-    }
-
-    $query .= "
-            bugs_activity.removed,
-            bugs_activity.added,
-            profiles.login_name
-        FROM 
-            bugs_activity LEFT JOIN fielddefs ON 
-            bugs_activity.fieldid = fielddefs.fieldid,
-            profiles
-        WHERE 
-            bugs_activity.bug_id = $id $datepart
-            AND profiles.userid = bugs_activity.who
-        ORDER BY 
-            bugs_activity.bug_when";
+    
+    my $query = "
+        SELECT IFNULL(fielddefs.description, bugs_activity.fieldid),
+                bugs_activity.attach_id,
+                bugs_activity.bug_when,
+                bugs_activity.removed, bugs_activity.added,
+                profiles.login_name
+        FROM bugs_activity LEFT JOIN fielddefs ON 
+                                     bugs_activity.fieldid = fielddefs.fieldid,
+             profiles
+        WHERE bugs_activity.bug_id = $id $datepart
+              AND profiles.userid = bugs_activity.who
+        ORDER BY bugs_activity.bug_when";
 
     SendSQL($query);
     
@@ -1176,7 +1133,9 @@ if (defined $ENV{"HTTP_COOKIE"}) {
     foreach my $pair (split(/;/, $ENV{"HTTP_COOKIE"})) {
         $pair = trim($pair);
         if ($pair =~ /^([^=]*)=(.*)$/) {
-            $::COOKIE{$1} = $2;
+            if (!exists($::COOKIE{$1})) {
+                $::COOKIE{$1} = $2;
+            }
         } else {
             $::COOKIE{$pair} = "";
         }

mozilla/webtools/bugzilla/Token.pm

@@ -114,22 +114,30 @@ sub IssuePasswordToken {
 
     # Retrieve the user's ID from the database.
     my $quotedloginname = &::SqlQuote($loginname);
-    &::SendSQL("SELECT userid FROM profiles WHERE login_name = $quotedloginname");
-    my ($userid) = &::FetchSQLData();
+    &::SendSQL("SELECT profiles.userid, tokens.issuedate FROM profiles 
+                    LEFT JOIN tokens
+                    ON tokens.userid = profiles.userid
+                    AND tokens.tokentype = 'password'
+                    AND tokens.issuedate > DATE_SUB(NOW(), INTERVAL 10 MINUTE)
+                    WHERE login_name = $quotedloginname");
+    my ($userid, $toosoon) = &::FetchSQLData();
+
+    if ($toosoon) {
+        &::DisplayError('Too Soon For Another Password Token') && exit;
+    };
 
     my $token_ts = time();
-    my $issuedate = time2str("%Y-%m-%d %H:%M", $token_ts);
 
     # 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 TABLE tokens WRITE") if $::driver eq 'mysql';
+    &::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 , '$issuedate' , $quotedtoken , 'password' , $quotedipaddr )");
-    &::SendSQL("UNLOCK TABLES") if $::driver eq 'mysql';
+                VALUES      ( $userid , NOW() , $quotedtoken , 'password' , $quotedipaddr )");
+    &::SendSQL("UNLOCK TABLES");
 
     # Mail the user the token along with instructions for using it.
     
@@ -155,13 +163,10 @@ sub IssuePasswordToken {
 
 
 sub CleanTokenTable {
-    &::SendSQL("LOCK TABLES tokens WRITE") if $::driver eq 'mysql';
-    if ($::driver eq 'mysql') {
-        &::SendSQL("DELETE FROM tokens WHERE TO_DAYS(NOW()) - TO_DAYS(issuedate) >= " . $maxtokenage);
-    } elsif ($::driver eq 'Pg') {
-        &::SendSQL("DELETE FROM tokens WHERE now() - issuedate >= '$maxtokenage days'");
-    }
-    &::SendSQL("UNLOCK TABLES") if $::driver eq 'mysql';
+    &::SendSQL("LOCK TABLES tokens WRITE");
+    &::SendSQL("DELETE FROM tokens 
+                WHERE TO_DAYS(NOW()) - TO_DAYS(issuedate) >= " . $maxtokenage);
+    &::SendSQL("UNLOCK TABLES");
 }
 
 
@@ -238,9 +243,9 @@ sub Cancel {
     close SENDMAIL;
 
     # Delete the token from the database.
-    &::SendSQL("LOCK TABLE tokens WRITE") if $::driver eq 'mysql';
+    &::SendSQL("LOCK TABLES tokens WRITE");
     &::SendSQL("DELETE FROM tokens WHERE token = $quotedtoken");
-    &::SendSQL("UNLOCK TABLES") if $::driver eq 'mysql';
+    &::SendSQL("UNLOCK TABLES");
 }
 
 sub HasPasswordToken {
@@ -260,10 +265,9 @@ sub HasEmailChangeToken {
     
     my ($userid) = @_;
     
-    &::SendSQL("SELECT token FROM tokens 
-                 WHERE userid = $userid 
-                   AND tokentype = 'emailnew' 
-                    OR tokentype = 'emailold' LIMIT 1");
+    &::SendSQL("SELECT token FROM tokens WHERE userid = $userid " . 
+               "AND (tokentype = 'emailnew' OR tokentype = 'emailold') " . 
+               "LIMIT 1");
     my ($token) = &::FetchSQLData();
     
     return $token;

mozilla/webtools/bugzilla/attachment.cgi

@@ -42,8 +42,9 @@ require "CGI.pl";
 # Establish a connection to the database backend.
 ConnectToDatabase();
 
-# Check whether or not the user is logged in and, if so, set the $userid 
-my $userid = quietly_check_login();
+# Check whether or not the user is logged in and, if so, set the $::userid 
+# and $::usergroupset variables.
+quietly_check_login();
 
 ################################################################################
 # Main Body Execution
@@ -63,19 +64,19 @@ if ($action eq "view")
 }
 elsif ($action eq "viewall") 
 { 
-  ValidateBugID($::FORM{'bugid'}, $userid);
+  ValidateBugID($::FORM{'bugid'});
   viewall(); 
 }
 elsif ($action eq "enter") 
 { 
-  my $userid = confirm_login();
-  ValidateBugID($::FORM{'bugid'}, $userid);
+  confirm_login();
+  ValidateBugID($::FORM{'bugid'});
   enter(); 
 }
 elsif ($action eq "insert")
 {
-  my $userid = confirm_login();
-  ValidateBugID($::FORM{'bugid'}, $userid);
+  confirm_login();
+  ValidateBugID($::FORM{'bugid'});
   ValidateComment($::FORM{'comment'});
   validateFilename();
   validateData();
@@ -94,10 +95,7 @@ elsif ($action eq "edit")
 }
 elsif ($action eq "update") 
 { 
-  my $userid = confirm_login();
-  UserInGroup($userid, "editbugs")
-    || DisplayError("You are not authorized to edit attachments.")
-    && exit;
+  confirm_login();
   ValidateComment($::FORM{'comment'});
   validateID();
   validateCanEdit($::FORM{'id'});
@@ -136,7 +134,7 @@ sub validateID
 
   # Make sure the user is authorized to access this attachment's bug.
   my ($bugid) = FetchSQLData();
-  ValidateBugID($bugid, $userid);
+  ValidateBugID($bugid);
 }
 
 sub validateCanEdit
@@ -147,14 +145,14 @@ sub validateCanEdit
     # the edit scrren to be displayed to people who aren't logged in.
     # People not logged in can't actually commit changes, because that code
     # calls confirm_login, not quietly_check_login, before calling this sub
-    return if $userid == 0;
+    return if $::userid == 0;
 
     # People in editbugs can edit all attachments
-    return if UserInGroup($userid, "editbugs");
+    return if UserInGroup("editbugs");
 
     # Bug 97729 - the submitter can edit their attachments
     SendSQL("SELECT attach_id FROM attachments WHERE " .
-            "attach_id = $attach_id AND submitter_id = $userid");
+            "attach_id = $attach_id AND submitter_id = $::userid");
 
     FetchSQLData()
       || DisplayError("You are not authorised to edit attachment #$attach_id")
@@ -430,8 +428,8 @@ sub enter
   # Retrieve the attachments the user can edit from the database and write
   # them into an array of hashes where each hash represents one attachment.
   my $canEdit = "";
-  if (!UserInGroup($userid, "editbugs")) {
-      $canEdit = "AND submitter_id = $userid";
+  if (!UserInGroup("editbugs")) {
+      $canEdit = "AND submitter_id = $::userid";
   }
   SendSQL("SELECT attach_id, description 
            FROM attachments
@@ -477,10 +475,11 @@ sub insert
 
   # Insert the attachment into the database.
   SendSQL("INSERT INTO attachments (bug_id, filename, description, mimetype, ispatch, submitter_id, thedata) 
-           VALUES ($::FORM{'bugid'}, $filename, $description, $contenttype, $::FORM{'ispatch'}, $userid, $thedata)");
+           VALUES ($::FORM{'bugid'}, $filename, $description, $contenttype, $::FORM{'ispatch'}, $::userid, $thedata)");
 
   # Retrieve the ID of the newly created attachment record.
-  my $attachid = CurrId('attachments_attach_id_seq');
+  SendSQL("SELECT LAST_INSERT_ID()");
+  my $attachid = FetchOneColumn();
 
   # Insert a comment about the new attachment into the database.
   my $comment = "Created an attachment (id=$attachid)\n$::FORM{'description'}\n";
@@ -500,14 +499,14 @@ sub insert
   foreach my $attachid (@{$::MFORM{'obsolete'}}) {
     SendSQL("UPDATE attachments SET isobsolete = 1 WHERE attach_id = $attachid");
     SendSQL("INSERT INTO bugs_activity (bug_id, attach_id, who, bug_when, fieldid, removed, added) 
-             VALUES ($::FORM{'bugid'}, $attachid, $userid, NOW(), $fieldid, '0', '1')");
+             VALUES ($::FORM{'bugid'}, $attachid, $::userid, NOW(), $fieldid, '0', '1')");
   }
 
   # Send mail to let people know the attachment has been created.  Uses a 
   # special syntax of the "open" and "exec" commands to capture the output of 
   # "processmail", which "system" doesn't allow, without running the command 
   # through a shell, which backticks (``) do.
-  #system ("./processmail", $bugid , $userid);
+  #system ("./processmail", $bugid , $::userid);
   #my $mailresults = `./processmail $bugid $::userid`;
   my $mailresults = '';
   open(PMAIL, "-|") or exec('./processmail', $::FORM{'bugid'}, $::COOKIE{'Bugzilla_login'});
@@ -528,7 +527,6 @@ sub insert
   # Generate and return the UI (HTML page) from the appropriate template.
   $template->process("attachment/created.html.tmpl", $vars)
     || ThrowTemplateError($template->error());
-  SendSQL("SELECT short_desc FROM bugs WHERE bug_id = $::FORM{'bugid'}");
 }
 
 
@@ -554,7 +552,7 @@ sub edit
   # Retrieve a list of status flags that have been set on the attachment.
   my %statuses;
   SendSQL("SELECT  id, name 
-           FROM    attachstatuses, attachstatusdefs 
+           FROM    attachstatuses JOIN attachstatusdefs 
            WHERE   attachstatuses.statusid = attachstatusdefs.id 
            AND     attach_id = $::FORM{'id'}");
   while ( my ($id, $name) = FetchSQLData() )
@@ -607,7 +605,7 @@ sub edit
 }
 
 
-sub update 
+sub update
 {
   # Update an attachment record.
 
@@ -618,10 +616,8 @@ sub update
     && exit;
 
   # Lock database tables in preparation for updating the attachment.
-  if ($::driver eq 'mysql') {
-    SendSQL("LOCK TABLES attachments WRITE , attachstatuses WRITE , 
-             attachstatusdefs READ , fielddefs READ , bugs_activity WRITE");
-  }
+  SendSQL("LOCK TABLES attachments WRITE , attachstatuses WRITE , 
+           attachstatusdefs READ , fielddefs READ , bugs_activity WRITE");
 
   # Get a copy of the attachment record before we make changes
   # so we can record those changes in the activity table.
@@ -684,23 +680,23 @@ sub update
     my $quotedolddescription = SqlQuote($olddescription);
     my $fieldid = GetFieldID('attachments.description');
     SendSQL("INSERT INTO bugs_activity (bug_id, attach_id, who, bug_when, fieldid, removed, added) 
-             VALUES ($bugid, $::FORM{'id'}, $userid, NOW(), $fieldid, $quotedolddescription, $quoteddescription)");
+             VALUES ($bugid, $::FORM{'id'}, $::userid, NOW(), $fieldid, $quotedolddescription, $quoteddescription)");
   }
   if ($oldcontenttype ne $::FORM{'contenttype'}) {
     my $quotedoldcontenttype = SqlQuote($oldcontenttype);
     my $fieldid = GetFieldID('attachments.mimetype');
     SendSQL("INSERT INTO bugs_activity (bug_id, attach_id, who, bug_when, fieldid, removed, added) 
-             VALUES ($bugid, $::FORM{'id'}, $userid, NOW(), $fieldid, $quotedoldcontenttype, $quotedcontenttype)");
+             VALUES ($bugid, $::FORM{'id'}, $::userid, NOW(), $fieldid, $quotedoldcontenttype, $quotedcontenttype)");
   }
   if ($oldispatch ne $::FORM{'ispatch'}) {
     my $fieldid = GetFieldID('attachments.ispatch');
     SendSQL("INSERT INTO bugs_activity (bug_id, attach_id, who, bug_when, fieldid, removed, added) 
-             VALUES ($bugid, $::FORM{'id'}, $userid, NOW(), $fieldid, $oldispatch, $::FORM{'ispatch'})");
+             VALUES ($bugid, $::FORM{'id'}, $::userid, NOW(), $fieldid, $oldispatch, $::FORM{'ispatch'})");
   }
   if ($oldisobsolete ne $::FORM{'isobsolete'}) {
     my $fieldid = GetFieldID('attachments.isobsolete');
     SendSQL("INSERT INTO bugs_activity (bug_id, attach_id, who, bug_when, fieldid, removed, added) 
-             VALUES ($bugid, $::FORM{'id'}, $userid, NOW(), $fieldid, $oldisobsolete, $::FORM{'isobsolete'})");
+             VALUES ($bugid, $::FORM{'id'}, $::userid, NOW(), $fieldid, $oldisobsolete, $::FORM{'isobsolete'})");
   }
   if ($oldstatuslist ne $newstatuslist) {
     my ($removed, $added) = DiffStrings($oldstatuslist, $newstatuslist);
@@ -708,13 +704,11 @@ sub update
     my $quotedadded = SqlQuote($added);
     my $fieldid = GetFieldID('attachstatusdefs.name');
     SendSQL("INSERT INTO bugs_activity (bug_id, attach_id, who, bug_when, fieldid, removed, added) 
-             VALUES ($bugid, $::FORM{'id'}, $userid, NOW(), $fieldid, $quotedremoved, $quotedadded)");
+             VALUES ($bugid, $::FORM{'id'}, $::userid, NOW(), $fieldid, $quotedremoved, $quotedadded)");
   }
 
   # Unlock all database tables now that we are finished updating the database.
-  if ($::driver eq 'mysql') {
-    SendSQL("UNLOCK TABLES");
-  }
+  SendSQL("UNLOCK TABLES");
 
   # If this installation has enabled the request manager, let the manager know
   # an attachment was updated so it can check for requests on that attachment
@@ -760,7 +754,9 @@ sub update
     }
 
     # Get the user's login name since the AppendComment function needs it.
-    my $who = DBID_to_name($userid);
+    my $who = DBID_to_name($::userid);
+    # Mention $::userid again so Perl doesn't give me a warning about it.
+    my $neverused = $::userid;
 
     # Append the comment to the list of comments in the database.
     AppendComment($bugid, $who, $wrappedcomment);
@@ -771,10 +767,10 @@ sub update
   # of the "open" and "exec" commands to capture the output of "processmail",
   # which "system" doesn't allow, without running the command through a shell,
   # which backticks (``) do.
-  #system ("./processmail", $bugid , $userid);
-  #my $mailresults = `./processmail $bugid $userid`;
+  #system ("./processmail", $bugid , $::userid);
+  #my $mailresults = `./processmail $bugid $::userid`;
   my $mailresults = '';
-  open(PMAIL, "-|") or exec('./processmail', $bugid, DBID_to_name($userid));
+  open(PMAIL, "-|") or exec('./processmail', $bugid, DBID_to_name($::userid));
   $mailresults .= $_ while <PMAIL>;
   close(PMAIL);
  

mozilla/webtools/bugzilla/bug_form.pl

@@ -62,7 +62,7 @@ sub show_bug {
     $vars->{'lsearch'} = \&lsearch,
     $vars->{'header_done'} = (@_),
 
-    my $userid = quietly_check_login();
+    quietly_check_login();
 
     my $id = $::FORM{'id'};
     
@@ -77,61 +77,16 @@ sub show_bug {
 
     # Populate the bug hash with the info we get directly from the DB.
     my $query = "
-SELECT
-    bugs.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, ";
-
-    if ($::driver eq 'mysql') {
-        $query .= "
-    date_format(creation_ts, '%Y-%m-%d %H:%i'),
-    delta_ts, ";
-    } elsif ($::driver eq 'Pg') {
-        $query .= "
-    TO_CHAR(creation_ts, 'YYYY-MM-DD HH24:MI:SS'),
-    TO_CHAR(delta_ts, 'YYYYMMDDHH24MISS'), ";
-    }
-
-    $query .= "
-    SUM(votes.count)
-FROM 
-    bugs LEFT JOIN votes USING(bug_id)
-WHERE 
-    bugs.bug_id = $id
-GROUP BY 
-    bugs.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,
-    delta_ts ";
+    SELECT bugs.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, 
+        date_format(creation_ts,'%Y-%m-%d %H:%i'),
+        groupset, delta_ts, ifnull(sum(votes.count),0)
+    FROM bugs LEFT JOIN votes USING(bug_id)
+    WHERE bugs.bug_id = $id
+    GROUP BY bugs.bug_id";
 
     SendSQL($query);
 
@@ -142,7 +97,7 @@ GROUP BY
                        "bug_severity", "component", "assigned_to", "reporter",
                        "bug_file_loc", "short_desc", "target_milestone",
                        "qa_contact", "status_whiteboard", "creation_ts",
-                       "delta_ts", "votes") 
+                       "groupset", "delta_ts", "votes") 
     {
         $value = shift(@row);
         $bug{$field} = defined($value) ? $value : "";
@@ -165,7 +120,15 @@ GROUP BY
             next;
         }
 
-        next if !CanSeeProduct($userid, $product);
+        if (Param("usebuggroupsentry")
+          && GroupExists($product)
+          && !UserInGroup($product))
+        {
+            # 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;
+        }
 
         push(@prodlist, $product);
     }
@@ -194,7 +157,8 @@ GROUP BY
     $bug{'milestoneurl'} = $::milestoneurl{$bug{'product'}} || 
                            "notargetmilestone.html";
 
-    $vars->{'use_votes'} = $::prodmaxvotes{$bug{'product'}};
+    $vars->{'use_votes'} = Param('usevotes')
+                           && $::prodmaxvotes{$bug{'product'}} > 0;
 
     # Add additional, calculated fields to the bug hash
     if (@::legal_keywords) {
@@ -239,49 +203,39 @@ GROUP BY
 
     # Groups
     my @groups;
-    my (%buggroups, %usergroups);
+    if ($::usergroupset ne '0' || $bug{'groupset'} ne '0') {      
+        my $bug_groupset = $bug{'groupset'};
 
-    # Find out if this bug is private to any group
-    SendSQL("SELECT group_id FROM bug_group_map WHERE bug_id = $id");
-    while (my $group_id = FetchOneColumn()) {
-        $buggroups{$group_id} = 1;
-    }
+        SendSQL("SELECT bit, name, description, (bit & $bug_groupset != 0),
+                 (bit & $::usergroupset != 0) FROM groups 
+                 WHERE 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 AND (bit & $::usergroupset != 0)) OR
+                 (bit & $bug_groupset != 0))");
 
-    # Get a list of active groups the user is in, subject to the above conditions
-    if ($userid) {
-        # NB - the number of groups is likely to be small - should we just select
-        # everything, and weed manually? OTOH, the number of products is likely
-        # to be small, too. This buggroup stuff needs to be rethought
-        SendSQL("SELECT groups.group_id, groups.isactive " .
-                "FROM user_group_map, " .
-                "groups LEFT JOIN products ON groups.name = products.product " .
-                "WHERE groups.group_id = user_group_map.group_id AND " .
-                "user_group_map.user_id = $userid AND groups.isbuggroup != 0 AND " .
-                "(groups.name = " . SqlQuote($bug{'product'}) . " OR " .
-                "products.product IS NULL)");
-        while (my $group_id = FetchOneColumn()) {
-            $usergroups{$group_id} = 1;
-        }
+        $user{'inallgroups'} = 1;
 
-        # Now get information about each group
-        SendSQL("SELECT group_id, name, description " .
-                "FROM groups " .
-                # "WHERE group_id IN (" . join(',', @groups) . ") " .
-                "ORDER BY description");
         while (MoreSQLData()) {
-            my ($group_id, $name, $description) = FetchSQLData();
-            my ($ison, $ingroup);
-    
-            if ($buggroups{$group_id} || 
-                ($usergroups{$group_id} && (($name eq $bug{'product'}) || 
-                                (!defined $::proddesc{$name})))) 
+            my ($bit, $name, $description, $ison, $ingroup) = FetchSQLData();
+            # For product groups, we only want to display the checkbox if either
+            # (1) The bit is already set, or
+            # (2) The user is in the group, but either:
+            #     (a) The group is a product group for the current product, or
+            #     (b) The group name isn't a product name
+            # This means that all product groups will be skipped, but 
+            # non-product bug groups will still be displayed.
+            if($ison || 
+               ($ingroup && (($name eq $bug{'product'}) ||
+                             (!defined $::proddesc{$name}))))
             {
                 $user{'inallgroups'} &= $ingroup;
 
-                push (@groups, { "bit" => $group_id,
-                                 "ison" => $buggroups{$group_id},
-                                 "ingroup" => $usergroups{$group_id},
-                                 "description" => $description });
+                push (@groups, { "bit" => $bit,
+                                 "ison" => $ison,
+                                 "ingroup" => $ingroup,
+                                 "description" => $description });            
             }
         }
 
@@ -289,7 +243,7 @@ GROUP BY
         # the user to set whether or not the reporter 
         # and cc list can see the bug even if they are not members of all 
         # groups to which the bug is restricted.
-        if (%buggroups) {
+        if ($bug{'groupset'} != 0) {
             $bug{'inagroup'} = 1;
 
             # Determine whether or not the bug is always accessible by the
@@ -321,8 +275,10 @@ GROUP BY
                        || $::userid == $bug{'reporter'}
                        || $::userid == $bug{'qa_contact'}
                        || $::userid == $bug{'assigned_to'}
-                       || UserInGroup($userid, "editbugs");                   
-    $user{'canconfirm'} = ($::userid == 0) || UserInGroup($userid, "canconfirm");
+                       || UserInGroup("editbugs");
+    $user{'canconfirm'} = ($::userid == 0)
+                          || UserInGroup("canconfirm")
+                          || UserInGroup("editbugs");
 
     # Bug states
     $bug{'isunconfirmed'} = ($bug{'bug_status'} eq $::unconfirmedstate);
@@ -358,9 +314,13 @@ GROUP BY
     $vars->{'bug'} = \%bug;
     $vars->{'user'} = \%user;
 
+    # Create the <link> elements for browsing bug lists
+    $vars->{'navigation_links'} = navigation_links(join(':',@bug_list));
+
     # Generate and return the UI (HTML page) from the appropriate template.
     $template->process("bug/edit.html.tmpl", $vars)
       || ThrowTemplateError($template->error());
 }
  
 1;
+

mozilla/webtools/bugzilla/bug_status.html

@@ -114,10 +114,10 @@ certain status transitions are allowed.
      duplicate requires the bug# of the duplicating bug and will at
      least put that bug number in the description field.
 <DT><B>WORKSFORME</B>
-<DD> All attempts at reproducing this bug were futile, reading the
-     code produces no clues as to why this behavior would occur. If
-     more information appears later, please re-assign the bug, for
-     now, file it.
+<DD> All attempts at reproducing this bug were futile, 
+     and reading the code produces no clues as to why the described
+     behavior would occur. If more information appears later, the
+     bug can be reopened.
 </DL>
 </TABLE>
 

mozilla/webtools/bugzilla/buglist.cgi

@@ -56,6 +56,7 @@ sub sillyness {
     $zz = @::settable_resolution;
     $zz = @::target_milestone;
     $zz = $::unconfirmedstate;
+    $zz = $::userid;
     $zz = @::versions;
 };
 
@@ -65,14 +66,28 @@ ConnectToDatabase();
 # Data and Security Validation
 ################################################################################
 
+# Whether or not the user wants to change multiple bugs.
+my $dotweak = $::FORM{'tweak'} ? 1 : 0;
+
+# Log the user in
+if ($dotweak) {
+    confirm_login();
+    if (!UserInGroup("editbugs")) {
+        DisplayError("Sorry, you do not have sufficient privileges to edit
+                      multiple bugs.");
+        exit;
+    }
+    GetVersionTable();
+}
+else {
+    quietly_check_login();
+}
+
 # Determine the format in which the user would like to receive the output.
 # Uses the default format if the user did not specify an output format;
 # otherwise validates the user's choice against the list of available formats.
 my $format = ValidateOutputFormat($::FORM{'format'}, "list");
 
-# Whether or not the user wants to change multiple bugs.
-my $dotweak = $::FORM{'tweak'} ? 1 : 0;
-
 # Use server push to display a "Please wait..." message for the user while
 # executing their query if their browser supports it and they are viewing
 # the bug list as HTML and they have not disabled it by adding &serverpush=0
@@ -86,9 +101,10 @@ my $serverpush =
   exists $ENV{'HTTP_USER_AGENT'} 
     && $ENV{'HTTP_USER_AGENT'} =~ /Mozilla.[3-9]/ 
       && $ENV{'HTTP_USER_AGENT'} !~ /[Cc]ompatible/
-        && $format->{'extension'} eq "html"
-          && !defined($::FORM{'serverpush'})
-            || $::FORM{'serverpush'};
+        && $ENV{'HTTP_USER_AGENT'} !~ /WebKit/
+          && $format->{'extension'} eq "html"
+            && !defined($::FORM{'serverpush'})
+              || $::FORM{'serverpush'};
 
 my $order = $::FORM{'order'} || "";
 my $order_from_cookie = 0;  # True if $order set using $::COOKIE{'LASTORDER'}
@@ -136,21 +152,6 @@ if ($::FORM{'cmdtype'} eq 'runnamed') {
     $filename =~ s/\s//;
 }
 
-my $userid = 0;
-if ($dotweak) {
-    $userid = confirm_login();
-    if (!UserInGroup($userid, "editbugs")) {
-        DisplayError("Sorry, you do not have sufficient privileges to edit
-                      multiple bugs.");
-        exit;
-    }
-    GetVersionTable();
-}
-else {
-    $userid = quietly_check_login();
-}
-
-
 ################################################################################
 # Utilities
 ################################################################################
@@ -195,7 +196,7 @@ sub GetByWordList {
             $word =~ s/^'//;
             $word =~ s/'$//;
             $word = '(^|[^a-z0-9])' . $word . '($|[^a-z0-9])';
-            push(@list, SqlRegEx($field, SqlQuote($word)));
+            push(@list, "lower($field) regexp '$word'");
         }
     }
 
@@ -211,7 +212,7 @@ sub GetByWordListSubstr {
 
     foreach my $word (split(/[\s,]+/, $strs)) {
         if ($word ne "") {
-            push(@list, SqlStrSearch($field, SqlQuote($word), "lower"));
+            push(@list, "INSTR(LOWER($field), " . lc(SqlQuote($word)) . ")");
         }
     }
 
@@ -251,16 +252,15 @@ sub GetQuip {
 }
 
 sub GetGroupsByGroupSet {
-    my ($userid) = @_;
+    my ($groupset) = @_;
 
-    return if !$userid;
+    return if !$groupset;
 
     SendSQL("
-        SELECT  groups.group_id, groups.name, groups.description, groups.isactive
+        SELECT  bit, name, description, isactive
           FROM  groups
-                LEFT JOIN user_group_map ON groups.group_id = user_group_map.group_id
-         WHERE  groups.isbuggroup != 0
-                AND user_group_map.user_id = $userid
+         WHERE  (bit & $groupset) != 0
+           AND  isbuggroup != 0
       ORDER BY  description ");
 
     my @groups;
@@ -283,32 +283,23 @@ sub GetGroupsByGroupSet {
 
 sub GenerateSQL {
     my $debug = 0;
-    my ($fieldsref, $urlstr, $groupbyref) = (@_);
+    my ($fieldsref, $urlstr) = (@_);
     my @fields;
-    my @groupbylist;
     my @supptables;
     my @wherepart;
     @fields = @$fieldsref if $fieldsref;
-    @groupbylist = @$groupbyref if $groupbyref;
     my %F;
     my %M;
     ParseUrlString($urlstr, \%F, \%M);
     my @specialchart;
     my @andlist;
 
-    my $userid = quietly_check_login();
-
     # First, deal with all the old hard-coded non-chart-based poop.
 
-#    unshift(@supptables,
-#            ("profiles map_assigned_to",
-#             "profiles map_reporter",
-#             "LEFT JOIN profiles map_qa_contact  ON bugs.qa_contact = map_qa_contact.userid"));
-
     unshift(@supptables,
             ("profiles map_assigned_to",
-             "profiles map_reporter"));
-
+             "profiles map_reporter",
+             "LEFT JOIN profiles map_qa_contact ON bugs.qa_contact = map_qa_contact.userid"));
     unshift(@wherepart,
             ("bugs.assigned_to = map_assigned_to.userid",
              "bugs.reporter = map_reporter.userid"));
@@ -348,7 +339,7 @@ sub GenerateSQL {
     my @legal_fields = ("product", "version", "rep_platform", "op_sys",
                         "bug_status", "resolution", "priority", "bug_severity",
                         "assigned_to", "reporter", "component",
-                        "target_milestone");
+                        "target_milestone", "groupset");
 
     foreach my $field (keys %F) {
         if (lsearch(\@legal_fields, $field) != -1) {
@@ -642,11 +633,7 @@ sub GenerateSQL {
              }
          },
          "^changedin," => sub {
-            if ($::driver eq 'mysql') {
-                $f = "(to_days(now()) - to_days(bugs.delta_ts))";
-            } elsif ($::driver eq 'Pg') {
-                $f = "(now() - bugs.delta_ts)";
-            }
+             $f = "(to_days(now()) - to_days(bugs.delta_ts))";
          },
 
          "^keywords," => sub {
@@ -714,19 +701,19 @@ sub GenerateSQL {
              $term = "$ff != $q";
          },
          ",casesubstring" => sub {
-            $term = SqlStrSearch($ff, $q);
+             $term = "INSTR($ff, $q)";
          },
          ",(substring|substr)" => sub {
-            $term = SqlStrSearch($ff, $q, "lower", "not");
+             $term = "INSTR(LOWER($ff), " . lc($q) . ")";
          },
          ",notsubstring" => sub {
-            $term = SqlStrSearch($ff, $q, "lower");
+             $term = "INSTR(LOWER($ff), " . lc($q) . ") = 0";
          },
          ",regexp" => sub {
-            $term = SqlRegEx($ff, $q);
+             $term = "LOWER($ff) REGEXP $q";
          },
-         ",notregexp" => sub {    
-            $term = SqlRegEx($ff, $q);
+         ",notregexp" => sub {
+             $term = "LOWER($ff) NOT REGEXP $q";
          },
          ",lessthan" => sub {
              $term = "$ff < $q";
@@ -829,6 +816,13 @@ sub GenerateSQL {
         push(@funcnames, $key);
     }
 
+    if ($debug) {
+        # If we're going to be printing debug stuff, we need the content
+        # type. This doesn't affect later stuff, because we call exit, and
+        # never return from this sub
+        print "Content-Type: text/html\n\n";
+    }
+
     # first we delete any sign of "Chart #-1" from the HTML form hash
     # since we want to guarantee the user didn't hide something here
     my @badcharts = grep /^(field|type|value)-1-/, (keys %F);
@@ -1016,7 +1010,6 @@ sub GenerateSQL {
             }
         }
     }
-
     my %suppseen = ("bugs" => 1);
     my $suppstring = "bugs";
     foreach my $str (@supptables) {
@@ -1030,10 +1023,9 @@ sub GenerateSQL {
     }
     my $query =  ("SELECT DISTINCT " . join(', ', @fields) .
                   " FROM $suppstring" .
-                  " WHERE " . join(' AND ', (@wherepart, @andlist)) .
-                  " GROUP BY " . join(", ", @groupbylist));
+                  " WHERE " . join(' AND ', (@wherepart, @andlist)));
 
-    # $query = SelectVisible($query, $::userid, $::usergroupset);
+    $query = SelectVisible($query, $::userid, $::usergroupset);
 
     if ($debug) {
         print "<P><CODE>" . value_quote($query) . "</CODE><P>\n";
@@ -1077,6 +1069,16 @@ CMD: for ($::FORM{'cmdtype'}) {
         my $userid = DBNameToIdAndCheck($::COOKIE{"Bugzilla_login"});
         my $qname = SqlQuote($::FORM{'namedcmd'});
         SendSQL("DELETE FROM namedqueries WHERE userid = $userid AND name = $qname");
+        # Now remove this query from the footer
+        my $count = 0;
+        foreach my $q (@{$::vars->{'user'}{'queries'}}) {
+            if ($q->{'name'} eq $::FORM{'namedcmd'}) {
+                splice(@{$::vars->{'user'}{'queries'}}, $count, 1);
+                last;
+            }
+            $count++;
+        }
+
         print "Content-Type: text/html\n\n";
         # Generate and return the UI (HTML page) from the appropriate template.
         $vars->{'title'} = "Query is gone";
@@ -1093,21 +1095,8 @@ CMD: for ($::FORM{'cmdtype'}) {
         my $userid = DBNameToIdAndCheck($::COOKIE{"Bugzilla_login"});
         my $qname = SqlQuote($::defaultqueryname);
         my $qbuffer = SqlQuote($::buffer);
-        if ($::driver eq 'mysql') {
-            SendSQL("REPLACE INTO namedqueries (userid, name, query)" .
-                    "VALUES ($userid, $qname, $qbuffer)");
-        } elsif ($::driver eq 'Pg') {
-            SendSQL("SELECT userid FROM namedqueries WHERE userid = $userid " .
-                    "AND name = $qname");
-            my $result = FetchOneColumn();
-            if ( $result ) {
-                SendSQL("UPDATE namedqueries SET query = $qbuffer " .
-                        "WHERE userid = $userid AND name = $qname");
-            } else {
-                SendSQL("INSERT INTO namedqueries (userid, name, query, watchfordiffs, linkinfooter) VALUES " .
-                        "($userid, $qname, $qbuffer, '', '')");
-            }
-        }
+        SendSQL("REPLACE INTO namedqueries (userid, name, query)
+                 VALUES ($userid, $qname, $qbuffer)");
         print "Content-Type: text/html\n\n";
         # Generate and return the UI (HTML page) from the appropriate template.
         $vars->{'title'} = "OK, default is set";
@@ -1146,7 +1135,7 @@ CMD: for ($::FORM{'cmdtype'}) {
                       WHERE  userid = $userid AND name = $qname");
         }
         else {
-            SendSQL("INSERT INTO namedqueries (userid, name, query, linkinfooter)
+            SendSQL("REPLACE INTO namedqueries (userid, name, query, linkinfooter)
                      VALUES ($userid, $qname, $qbuffer, $tofooter)");
         }
         
@@ -1207,17 +1196,9 @@ sub DefineColumn {
 
 # Column:     ID                    Name                           Title
 DefineColumn("id"                , "bugs.bug_id"                , "ID"               );
-if ($::driver eq 'mysql') {
-    DefineColumn("opendate", "unix_timestamp(bugs.creation_ts)", "Opened",
-           "bugs.creation_ts");
-    DefineColumn("changeddate", "unix_timestamp(bugs.delta_ts)", "Changed",
-           "bugs.delta_ts");
-} elsif ($::driver eq 'Pg') {
-    DefineColumn("opendate", "bugs.creation_ts", "Opened",
-           "bugs.creation_ts");
-    DefineColumn("changeddate", "bugs.delta_ts", "Changed",
-           "bugs.delta_ts");
-}
+DefineColumn("groupset"          , "bugs.groupset"              , "Groupset"         );
+DefineColumn("opendate"          , "bugs.creation_ts"           , "Opened"           );
+DefineColumn("changeddate"       , "bugs.delta_ts"              , "Changed"          );
 DefineColumn("severity"          , "bugs.bug_severity"          , "Severity"         );
 DefineColumn("priority"          , "bugs.priority"              , "Priority"         );
 DefineColumn("platform"          , "bugs.rep_platform"          , "Platform"         );
@@ -1273,6 +1254,9 @@ else {
 # and are hard-coded into the display templates.
 @displaycolumns = grep($_ ne 'id', @displaycolumns);
 
+# IMPORTANT! Never allow the groupset column to be displayed!
+@displaycolumns = grep($_ ne 'groupset', @displaycolumns);
+
 # Add the votes column to the list of columns to be displayed
 # in the bug list if the user is searching for bugs with a certain
 # number of votes and the votes column is not already on the list.
@@ -1284,9 +1268,6 @@ if (trim($::FORM{'votes'}) && !grep($_ eq 'votes', @displaycolumns)) {
     push(@displaycolumns, 'votes');
 }
 
-################################################################################
-# Select Column Determination
-################################################################################
 
 ################################################################################
 # Select Column Determination
@@ -1294,23 +1275,20 @@ if (trim($::FORM{'votes'}) && !grep($_ eq 'votes', @displaycolumns)) {
 
 # Generate the list of columns that will be selected in the SQL query.
 
-# The bug ID is always selected because bug IDs are always
-# displayed
-my @selectcolumns = ("id");
-my @groupbylist = ("id");
+# The bug ID and groupset are always selected because bug IDs are always
+# displayed and we need the groupset to determine whether or not the bug
+# is visible to the user.
+my @selectcolumns = ("id", "groupset");
 
 # Display columns are selected because otherwise we could not display them.
 push (@selectcolumns, @displaycolumns);
-push (@groupbylist, @displaycolumns);
 
 # If the user is editing multiple bugs, we also make sure to select the product
 # and status because the values of those fields determine what options the user
 # has for modifying the bugs.
 if ($dotweak) {
     push(@selectcolumns, "product") if !grep($_ eq 'product', @selectcolumns);
-    push(@groupbylist, "product") if !grep($_ eq 'product', @groupbylist);
     push(@selectcolumns, "status") if !grep($_ eq 'status', @selectcolumns);
-    push(@groupbylist, "status") if !grep($_ eq 'product', @groupbylist);
 }
 
 
@@ -1320,17 +1298,17 @@ if ($dotweak) {
 
 # Convert the list of columns being selected into a list of column names.
 my @selectnames = map($columns->{$_}->{'name'}, @selectcolumns);
-my @groupbynames = map($columns->{$_}->{'name'}, @groupbylist);
 
 # Generate the basic SQL query that will be used to generate the bug list.
-my $query = GenerateSQL(\@selectnames, $::buffer, \@groupbynames);
+my $query = GenerateSQL(\@selectnames, $::buffer);
+
 
 ################################################################################
 # Sort Order Determination
 ################################################################################
 
 # Add to the query some instructions for sorting the bug list.
-if ($::COOKIE{'LASTORDER'} && !$order || $order =~ /^reuse/i) {
+if ($::COOKIE{'LASTORDER'} && (!$order || $order =~ /^reuse/i)) {
     $order = url_decode($::COOKIE{'LASTORDER'});
     $order_from_cookie = 1;
 }
@@ -1342,18 +1320,20 @@ if ($order) {
     # by which to sort the results.
     ORDER: for ($order) {
         /\./ && do {
+            my @columnnames = map($columns->{lc($_)}->{'name'}, keys(%$columns));
             # A custom list of columns.  Make sure each column is valid.
-            foreach my $fragment (split(/[,\s]+/, $order)) {
-                next if $fragment =~ /^asc|desc$/i;
-                my @columnnames = map($columns->{lc($_)}->{'name'}, keys(%$columns));
-                if (!grep($_ eq $fragment, @columnnames)) {
+            foreach my $fragment (split(/,/, $order)) {
+                $fragment = trim($fragment);
+                # Accept an order fragment matching a column name, with
+                # asc|desc optionally following (to specify the direction)
+                if (!grep($fragment =~ /^\Q$_\E(\s+(asc|desc))?$/, @columnnames)) {
                     my $qfragment = html_quote($fragment);
                     my $error = "The custom sort order you specified in your "
                               . "form submission contains an invalid column "
                               . "name <em>$qfragment</em>.";
                     if ($order_from_cookie) {
                         my $cookiepath = Param("cookiepath");
-                        print "Set-Cookie: LASTORDER= ; path=$cookiepath; expires=Sun, 30-Jun-80 00:00:00 GMT\n";
+                        print "Set-Cookie: LASTORDER= ; path=$cookiepath; expires=Tue, 15-Sep-1998 21:49:00 GMT\n";
                         $error =~ s/form submission/cookie/;
                         $error .= "  The cookie has been cleared.";
                     }
@@ -1375,7 +1355,7 @@ if ($order) {
             last ORDER;
         };
         /Assign/ && do {
-            $order = "map_assigned_to.login_name, bugs.bug_status, priority, bugs.bug_id";
+            $order = "map_assigned_to.login_name, bugs.bug_status, bugs.priority, bugs.bug_id";
             last ORDER;
         };
         /Changed/ && do {
@@ -1395,10 +1375,9 @@ if ($order) {
         $query =~ s/\sWHERE\s/ LEFT JOIN milestones ms_order ON ms_order.value = bugs.target_milestone AND ms_order.product = bugs.product WHERE /;
     }
 
-    # If we are sorting by votes, sort in descending order.
-    if ($db_order =~ /bugs.votes\s+(asc|desc){0}/i) {
-        $db_order =~ s/bugs.votes/bugs.votes desc/i;
-    }
+    # If we are sorting by votes, sort in descending order if no explicit
+    # sort order was given
+    $db_order =~ s/bugs.votes\s*(,|$)/bugs.votes desc$1/i;
 
     $query .= " ORDER BY $db_order ";
 }
@@ -1428,7 +1407,7 @@ ReconnectToShadowDatabase();
 
 # Tell MySQL to store temporary tables on the hard drive instead of memory
 # to avoid "table out of space" errors on MySQL versions less than 3.23.2.
-SendSQL("SET OPTION SQL_BIG_TABLES=1") if Param('expectbigqueries') && $::driver eq 'mysql';
+SendSQL("SET OPTION SQL_BIG_TABLES=1") if Param('expectbigqueries');
 
 # Normally, we ignore SIGTERM and SIGPIPE (see globals.pl) but we need to
 # respond to them here to prevent someone DOSing us by reloading a query
@@ -1439,6 +1418,7 @@ $::SIG{PIPE} = 'DEFAULT';
 # Execute the query.
 SendSQL($query);
 
+
 ################################################################################
 # Results Retrieval
 ################################################################################
@@ -1449,8 +1429,6 @@ SendSQL($query);
 my $bugowners = {};
 my $bugproducts = {};
 my $bugstatuses = {};
-my @buglist = ();
-my @canseebugs = ();
 
 my @bugs; # the list of records
 
@@ -1475,24 +1453,15 @@ while (my @row = FetchSQLData()) {
     $bugproducts->{$bug->{'product'}} = 1 if $bug->{'product'};
     $bugstatuses->{$bug->{'status'}} = 1 if $bug->{'status'};
 
-    # Keep list of bugs so we can check them later for permission
-    push(@buglist, $bug->{id});
-
     # Add the record to the list.
     push(@bugs, $bug);
 }
 
-# Check to see which bugs we have permission to see
-my $canseeref = CanSeeBug(\@buglist, $userid);
-foreach my $bug (@bugs) {
-#    next if !$canseeref->{$bug->{id}};
-    push(@canseebugs, $bug);
-}
-
 # Switch back from the shadow database to the regular database so PutFooter()
 # can determine the current user even if the "logincookies" table is corrupted
 # in the shadow database.
-SendSQL("USE $::db_name") if $::driver eq 'mysql';
+SendSQL("USE $::db_name");
+
 
 ################################################################################
 # Template Variable Definition
@@ -1523,7 +1492,8 @@ $vars->{'order'} = $order;
 # The user's login account name (i.e. email address).
 my $login = $::COOKIE{'Bugzilla_login'};
 
-$vars->{'caneditbugs'} = UserInGroup($userid, 'editbugs');
+$vars->{'caneditbugs'} = UserInGroup('editbugs');
+$vars->{'usebuggroups'} = Param('usebuggroups');
 
 # Whether or not this user is authorized to move bugs to another installation.
 $vars->{'ismover'} = 1
@@ -1532,7 +1502,7 @@ $vars->{'ismover'} = 1
       && Param('movers') =~ /^(\Q$login\E[,\s])|([,\s]\Q$login\E[,\s]+)/;
 
 my @bugowners = keys %$bugowners;
-if (scalar(@bugowners) > 1 && UserInGroup($userid, 'editbugs')) {
+if (scalar(@bugowners) > 1 && UserInGroup('editbugs')) {
     my $suffix = Param('emailsuffix');
     map(s/$/$suffix/, @bugowners) if $suffix;
     my $bugowners = join(",", @bugowners);
@@ -1555,8 +1525,10 @@ $vars->{'currenttime'} = time2str("%a %b %e %T %Z %Y", time());
 if ($dotweak) {
     $vars->{'dotweak'} = 1;
     $vars->{'use_keywords'} = 1 if @::legal_keywords;
-
-    $vars->{'products'} = \@::legal_product;
+    my @entry_products = grep {(!Param("usebuggroups") 
+                             || !GroupExists($_) 
+                             || UserInGroup($_))} @::legal_product;
+    $vars->{'products'} = \@entry_products;
     $vars->{'platforms'} = \@::legal_platform;
     $vars->{'priorities'} = \@::legal_priority;
     $vars->{'severities'} = \@::legal_severity;
@@ -1570,7 +1542,7 @@ if ($dotweak) {
     $vars->{'bugstatuses'} = [ keys %$bugstatuses ];
 
     # The groups to which the user belongs.
-    $vars->{'groups'} = GetGroupsByGroupSet($userid) if $userid ne '0';
+    $vars->{'groups'} = GetGroupsByGroupSet($::usergroupset) if $::usergroupset ne '0';
 
     # If all bugs being changed are in the same product, the user can change
     # their version and component, so generate a list of products, a list of
@@ -1585,6 +1557,7 @@ if ($dotweak) {
     }
 }
 
+
 ################################################################################
 # HTTP Header Generation
 ################################################################################
@@ -1605,15 +1578,15 @@ if ($format->{'extension'} eq "html") {
 
     if ($order) {
         my $qorder = url_quote($order);
-        print "Set-Cookie: LASTORDER=$qorder ; path=$cookiepath; expires=Sun, 30-Jun-2029 00:00:00 GMT\n";
+        print "Set-Cookie: LASTORDER=$qorder ; path=$cookiepath; expires=Sat, 30-Jun-2029 00:00:00 GMT\n";
     }
     my $bugids = join(":", map( $_->{'id'}, @bugs));
     # See also Bug 111999
     if (length($bugids) < 4000) {
-        print "Set-Cookie: BUGLIST=$bugids ; path=$cookiepath; expires=Sun, 30-Jun-2029 00:00:00 GMT\n";
+        print "Set-Cookie: BUGLIST=$bugids ; path=$cookiepath; expires=Sat, 30-Jun-2029 00:00:00 GMT\n";
     }
     else {
-        print "Set-Cookie: BUGLIST= ; path=$cookiepath; expires=Sun, 30-Jun-2029 00:00:00 GMT\n";
+        print "Set-Cookie: BUGLIST= ; path=$cookiepath; expires=Sat, 30-Jun-2029 00:00:00 GMT\n";
         $vars->{'toolong'} = 1;
     }
 }
@@ -1638,4 +1611,3 @@ $template->process("list/$format->{'template'}", $vars)
 ################################################################################
 
 print "\n--thisrandomstring--\n" if $serverpush;
-

mozilla/webtools/bugzilla/bugwritinghelp.html

@@ -280,7 +280,7 @@ Bugzilla database.<br>
 </blockquote>
 
 <hr>
-<h3>More Information on Writing Good Bugs</h3>
+<h3>More Information on Writing Good Bug Reports</h3>
 
 <blockquote>
 <p><b><a name="tips"></a> 1. General Tips for a Useful Bug

mozilla/webtools/bugzilla/checksetup.pl

@@ -203,6 +203,10 @@ my $modules = [
         name => 'File::Spec', 
         version => '0.82' 
     }, 
+    { 
+        name => 'File::Temp',
+        version => '0'
+    },
     { 
         name => 'Template', 
         version => '2.07' 
@@ -387,7 +391,7 @@ LocalVar('webservergroup', '
 #
 # This is the group your web server runs on.
 # If you have a windows box, ignore this setting.
-# If you do not wish for checksetup to adjust the permissions of anything,
+# If you do not have access to the group your web server runs under,
 # set this to "". If you do set this to "", then your Bugzilla installation
 # will be _VERY_ insecure, because some files will be world readable/writable,
 # and so anyone who can get local access to your machine can do whatever they
@@ -395,14 +399,15 @@ LocalVar('webservergroup', '
 # and you cannot set this up any other way. YOU HAVE BEEN WARNED.
 # If you set this to anything besides "", you will need to run checksetup.pl
 # as root, or as a user who is a member of the specified group.
-$webservergroup = "nobody";
+$webservergroup = "apache";
 ');
 
+
+
 LocalVar('db_host', '
 #
 # How to access the SQL database:
 #
-$db_driver = "mysql";           # Which database we are using
 $db_host = "localhost";         # where is the database?
 $db_port = 3306;                # which port to use
 $db_name = "bugs";              # name of the MySQL database
@@ -635,11 +640,16 @@ $::ENV{'PATH'} = $origPath;
 # Create initial --DATA-- directory and make the initial empty files there:
 #
 
-unless (-d 'data') {
+# The |require "globals.pl"| above ends up creating a template object with
+# a COMPILE_DIR of 'data'. This means that TT creates the directory for us,
+# so this code wouldn't run if we just checked for the existence of the
+# directory. Instead, check for the existence of 'data/nomail', which is
+# created in this block
+unless (-d 'data' && -e 'data/nomail') {
     print "Creating data directory ...\n";
     # permissions for non-webservergroup are fixed later on
-    mkdir 'data', 0770; 
-    mkdir 'data/mimedump-tmp', 01777; 
+    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;
@@ -724,7 +734,16 @@ unless (-d 'graphs') {
 
         close(IN);
         close(OUT);
-    }    
+    }
+}
+
+unless (-d 'data/mining') {
+    mkdir 'data/mining', 0700;
+}
+
+unless (-d 'data/webdot') {
+    # perms/ownership are fixed up later
+    mkdir 'data/webdot', 0700;
 }
 
 if ($my_create_htaccess) {
@@ -739,12 +758,35 @@ if ($my_create_htaccess) {
     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|runtests.sh)$>
+<FilesMatch ^(.*\.pl|.*localconfig.*|processmail|syncshadowdb|runtests.sh)$>
   deny from all
 </FilesMatch>
+<FilesMatch ^(localconfig.js|localconfig.rdf)$>
+  allow from all
+</FilesMatch>
 END
     close HTACCESS;
     chmod $fileperm, ".htaccess";
+  } else {
+    # 2002-12-21 Bug 186383
+    open HTACCESS, ".htaccess";
+    my $oldaccess = "";
+    while (<HTACCESS>) {
+      $oldaccess .= $_;
+    }
+    close HTACCESS;
+    if ($oldaccess =~ s/\|localconfig\|/\|.*localconfig.*\|/) {
+      print "Repairing .htaccess...\n";
+      open HTACCESS, ">.htaccess";
+      print HTACCESS $oldaccess;
+      print HTACCESS <<'END';
+<FilesMatch ^(localconfig.js|localconfig.rdf)$>
+  allow from all
+</FilesMatch>
+END
+      close HTACCESS;
+    }
+
   }
   if (!-e "data/.htaccess") {
     print "Creating data/.htaccess...\n";
@@ -769,24 +811,19 @@ END
     chmod $fileperm, "template/.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';
 # Restrict access to .dot files to the public webdot server at research.att.com 
 # if research.att.com ever changed their IP, or if you use a different
 # webdot server, you'll need to edit this
-<FilesMatch ^[0-9]+\.dot$>
+<FilesMatch \.dot$>
   Allow from 192.20.225.10
   Deny from all
 </FilesMatch>
 
-# Allow access by a local copy of 'dot' to .png, .gif, .jpg, and
-# .map files
-<FilesMatch ^[0-9]+\.(png|gif|jpg|map)$>
+# Allow access to .png files created by a local copy of 'dot'
+<FilesMatch \.png$>
   Allow from all
 </FilesMatch>
 
@@ -840,6 +877,8 @@ END
     if (-e 'data/template') {
         unless (-d 'data/template' && -e 'data/template/.lastRebuild' &&
                 (stat('data/template/.lastRebuild'))[9] >= $lastTemplateParamChange) {
+            print "Removing existing compiled templates ...\n";
+
             # If File::Path::rmtree reported errors, then I'd use that
             use File::Find;
             sub remove {
@@ -878,8 +917,8 @@ END
          strike => sub { return $_; } ,
          js => sub { return $_; },
          html => sub { return $_; },
+         html_linebreak => sub { return $_; },
          url_quote => sub { return $_; },
-         no_break => sub { return $_; }
         },
       }) || die ("Could not create Template: " . Template->error() . "\n");
 
@@ -903,6 +942,8 @@ END
     }
 
     {
+        print "Precompiling templates ...\n";
+
         use File::Find;
 
         use Cwd;
@@ -973,8 +1014,8 @@ if (-e "data/params") {
 #
 # Here we use --CHMOD-- and friends to set the file permissions
 #
-# The rationale is that the web server generally runs as nobody and so the cgi
-# scripts should not be writable for nobody, otherwise someone may be possible
+# The rationale is that the web server generally runs as apache and so the cgi
+# scripts should not be writable for apache, otherwise someone may be possible
 # to change the cgi's when exploiting some security flaw somewhere (not
 # necessarily in Bugzilla!)
 #
@@ -1068,28 +1109,46 @@ if ($my_webservergroup) {
     # userid.
     fixPerms('.htaccess', $<, $webservergid, 027); # glob('*') doesn't catch dotfiles
     fixPerms('data/.htaccess', $<, $webservergid, 027);
+    fixPerms('data/duplicates', $<, $webservergid, 027, 1);
+    fixPerms('data/mining', $<, $webservergid, 027, 1);
     fixPerms('data/template', $<, $webservergid, 007, 1); # webserver will write to these
+    fixPerms('data/webdot', $<, $webservergid, 007, 1);
     fixPerms('data/webdot/.htaccess', $<, $webservergid, 027);
     fixPerms('data/params', $<, $webservergid, 017);
+    fixPerms('data/comments', $<, $webservergid, 017);
     fixPerms('*', $<, $webservergid, 027);
     fixPerms('template', $<, $webservergid, 027, 1);
     fixPerms('css', $<, $webservergid, 027, 1);
     chmod 0644, 'globals.pl';
     chmod 0644, 'RelationSet.pm';
+
+    # Don't use fixPerms here, because it won't change perms on the directory
+    # unless its using recursion
+    chown $<, $webservergid, 'data';
     chmod 0771, 'data';
+    chown $<, $webservergid, 'graphs';
     chmod 0770, 'graphs';
 } else {
     # get current gid from $( list
     my $gid = (split " ", $()[0];
     fixPerms('.htaccess', $<, $gid, 022); # glob('*') doesn't catch dotfiles
     fixPerms('data/.htaccess', $<, $gid, 022);
-    fixPerms('data/template', $<, $gid, 022, 1);
+    fixPerms('data/duplicates', $<, $gid, 022, 1);
+    fixPerms('data/mining', $<, $gid, 022, 1);
+    fixPerms('data/template', $<, $gid, 000, 1); # webserver will write to these
+    fixPerms('data/webdot', $<, $gid, 000, 1);
+    chmod 01777, 'data/webdot';
     fixPerms('data/webdot/.htaccess', $<, $gid, 022);
     fixPerms('data/params', $<, $gid, 011);
     fixPerms('*', $<, $gid, 022);
     fixPerms('template', $<, $gid, 022, 1);
     fixPerms('css', $<, $gid, 022, 1);
+
+    # Don't use fixPerms here, because it won't change perms on the directory
+    # unless its using recursion
+    chown $<, $gid, 'data';
     chmod 0777, 'data';
+    chown $<, $gid, 'graphs';
     chmod 01777, 'graphs';
 }
 
@@ -1142,7 +1201,7 @@ if ($my_db_check) {
     if ( vers_cmp($sql_vers,$sql_want) > -1 ) {
         print "ok: found v$sql_vers\n";
     } else {
-        die "Your MySQL server v$sql_vers is too old./n" . 
+        die "\nYour 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";
     }
@@ -1291,6 +1350,7 @@ $table{attachstatusdefs} =
 #
 $table{bugs} =
    'bug_id mediumint not null auto_increment primary key,
+    groupset bigint not null,
     assigned_to mediumint not null, # This is a comment.
     bug_file_loc text,
     bug_severity enum($my_severities) not null,
@@ -1377,6 +1437,13 @@ $table{dependencies} =
     index(dependson)';
 
 
+# Group bits must be a power of two. Groups are identified by a bit; sets of
+# groups are indicated by or-ing these values together.
+#
+# isbuggroup is nonzero if this is a group that controls access to a set
+# of bugs.  In otherword, the groupset field in the bugs table should only
+# have this group's bit set if isbuggroup is nonzero.
+#
 # 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.
@@ -1389,14 +1456,14 @@ $table{dependencies} =
 # http://bugzilla.mozilla.org/show_bug.cgi?id=75482
 
 $table{groups} =
-    'group_id mediumint not null auto_increment primary key,
+   'bit bigint not null,
     name varchar(255) not null,
     description text not null,
     isbuggroup tinyint not null,
     userregexp tinytext not null,
     isactive tinyint not null default 1,
 
-    unique(group_id),
+    unique(bit),
     unique(name)';
 
 $table{logincookies} =
@@ -1409,8 +1476,7 @@ $table{logincookies} =
 
 
 $table{products} =
-   'product_id mediumint primary key auto_increment not null,
-    product varchar(64),
+   'product varchar(64),
     description mediumtext,
     milestoneurl tinytext not null,
     disallownew tinyint not null,
@@ -1426,10 +1492,12 @@ $table{profiles} =
     login_name varchar(255) not null,
     cryptpassword varchar(34),
     realname varchar(255),
+    groupset bigint not null,
     disabledtext mediumtext not null,
     mybugslink tinyint not null default 1,
+    blessgroupset bigint not null default 0,
     emailflags mediumtext,
-    admin tinyint not null default 0,
+
 
     unique(login_name)';
 
@@ -1535,46 +1603,22 @@ $table{tokens} =
 
      index(userid)';
 
-# 2001-09-18, dkl@redhat.com
-# Group tables for tracking group memberships, admin memberships, 
-# product permissions, and bug permissions.
-#
-# This table determines the groups that a user belongs to
-# and the level that they can bless others to.
-# canbless:
-# 0 = Cannot bless others into the group
-# 1 = Can bless others into the group
-# 2 = Can give others permission to bless people into the group
-$table{user_group_map} = 
-    'user_id mediumint not null,
-     group_id mediumint not null,
-     canbless smallint default 0,
 
-     unique(user_id, group_id),    
-     index(group_id)';
-
-# This table determines which groups have permission to see a bug
-$table{bug_group_map} =
-    'bug_id mediumint not null,
-     group_id mediumint not null,
-
-     unique(bug_id, group_id),
-     index(group_id)';
-
-# This table determines which groups may report bugs against a product
-$table{product_group_map} =
-    'product_id mediumint not null,
-     group_id mediumint not null,
-
-     unique(product_id, group_id),
-     index(group_id)';
 
 ###########################################################################
 # Create tables
 ###########################################################################
 
 # Get a list of the existing tables (if any) in the database
-my @tables = map { $_ =~ s/.*\.//; $_ } $dbh->tables;
+my @tables;
+my $zz = $DBI::VERSION; # mention it to eliminate "used only once" warning on perl 5.00503
+if ($DBI::VERSION < 1.20) {
+    @tables = map { $_ =~ s/.*\.//; $_ } $dbh->tables;
+}
+else {
+    my $sth = $dbh->table_info(undef, undef, undef, "TABLE");
+    @tables = @{$dbh->selectcol_arrayref($sth, { Columns => [3] })};
+}
 #print 'Tables: ', join " ", @tables, "\n";
 
 # add lines here if you add more --LOCAL-- config vars that end up in the enums:
@@ -1597,7 +1641,7 @@ while (my ($tabname, $fielddef) = each %table) {
     $fielddef =~ s/\$my_opsys/$my_opsys/;
     $fielddef =~ s/\$my_platforms/$my_platforms/;
 
-    $dbh->do("CREATE TABLE $tabname (\n$fielddef\n)")
+    $dbh->do("CREATE TABLE $tabname (\n$fielddef\n) TYPE = MYISAM")
         or die "Could not create table '$tabname'. Please check your '$db_base' access.\n";
 }
 
@@ -1609,24 +1653,6 @@ while (my ($tabname, $fielddef) = each %table) {
 # Populate groups table
 ###########################################################################
 
-# We need to add a couple of columns first if this is our first time
-# using the new group schema and populate the group ids
-# 2002/01/23 dkl@redhat.com
-if (&GetFieldDef('groups', 'bit')) {
-    &AddField('groups', 'group_id', 'mediumint primary key auto_increment not null');
-    &AddField('profiles', 'admin', 'smallint default 0');
-    my $currentgroupid = 1;
-    my $query = "select bit from groups order by bit";
-    my $sth = $dbh->prepare($query);
-    $sth->execute();
-    while (my ($bit) = $sth->fetchrow_array()) {
-        my $query = "update groups set group_id = $currentgroupid where bit = $bit";
-        my $sth2 = $dbh->prepare($query);
-        $sth2->execute();
-        $currentgroupid++;
-    }
-}
-
 sub GroupDoesExist ($)
 {
     my ($name) = @_;
@@ -1641,7 +1667,7 @@ sub GroupDoesExist ($)
 
 #
 # This subroutine checks if a group exist. If not, it will be automatically
-# created with the next available groupid 
+# created with the next available bit set
 #
 
 sub AddGroup {
@@ -1650,17 +1676,26 @@ sub AddGroup {
 
     return if GroupDoesExist($name);
     
+    # get highest bit number
+    my $sth = $dbh->prepare("SELECT bit FROM groups ORDER BY bit DESC");
+    $sth->execute;
+    my @row = $sth->fetchrow_array;
+
+    # normalize bits
+    my $bit;
+    if (defined $row[0]) {
+        $bit = $row[0] << 1;
+    } else {
+        $bit = 1;
+    }
+
+   
     print "Adding group $name ...\n";
-    my $sth = $dbh->prepare('INSERT INTO groups
-                          (name, description, userregexp, isbuggroup)
-                          VALUES (?, ?, ?, ?)');
-    $sth->execute($name, $desc, $userregexp, 0);
-
-    $sth = $dbh->prepare("select last_insert_id()");
-    $sth->execute();
-    my ($last) = $sth->fetchrow_array();
-
-    return $last;
+    $sth = $dbh->prepare('INSERT INTO groups
+                          (bit, name, description, userregexp, isbuggroup)
+                          VALUES (?, ?, ?, ?, ?)');
+    $sth->execute($bit, $name, $desc, $userregexp, 0);
+    return $bit;
 }
 
 
@@ -1674,27 +1709,24 @@ AddGroup 'creategroups',     'Can create and destroy groups.';
 AddGroup 'editcomponents',   'Can create, destroy, and edit components.';
 AddGroup 'editkeywords',   'Can create, destroy, and edit keywords.';
 
+# Add the groupset field here because this code is run before the
+# code that updates the database structure.
+&AddField('profiles', 'groupset', 'bigint not null');
+
 if (!GroupDoesExist("editbugs")) {
     my $id = AddGroup('editbugs',  'Can edit all aspects of any bug.', ".*");
-    my $sth = $dbh->prepare("SELECT userid FROM profiles ORDER BY userid");
-    $sth->execute();
-    while ( my ($userid) = $sth->fetchrow_array() ) {
-        $dbh->do("INSERT INTO user_group_map VALUES ($userid, $id)");
-    }
+    $dbh->do("UPDATE profiles SET groupset = groupset | $id");
 }
 
 if (!GroupDoesExist("canconfirm")) {
     my $id = AddGroup('canconfirm',  'Can confirm a bug.', ".*");
-    my $sth = $dbh->prepare("SELECT userid FROM profiles ORDER BY userid");
-    $sth->execute();
-    while ( my ($userid) = $sth->fetchrow_array() ) {
-        $dbh->do("INSERT INTO user_group_map VALUES ($userid, $id)");
-    }
+    $dbh->do("UPDATE profiles SET groupset = groupset | $id");
 }
 
 
 
 
+
 ###########################################################################
 # Populate the list of fields.
 ###########################################################################
@@ -1877,25 +1909,17 @@ CheckEnumField('bugs', 'rep_platform', @my_platforms);
 #  Prompt the user for the email address and name of an administrator.  Create
 #  that login, if it doesn't exist already, and make it a member of all groups.
 
-my @groups = ();
-my $sth = $dbh->prepare("select group_id from groups");
-$sth->execute();
-while ( my @row = $sth->fetchrow_array() ) {
-    push (@groups, $row[0]);
-}
-
 sub bailout {   # this is just in case we get interrupted while getting passwd
     system("stty","echo"); # re-enable input echoing
     exit 1;
 }
 
-$sth = $dbh->prepare(<<_End_Of_SQL_);
-  SELECT login_name  
+my $sth = $dbh->prepare(<<_End_Of_SQL_);
+  SELECT login_name
   FROM profiles
-  WHERE admin = 1 
+  WHERE groupset=9223372036854775807
 _End_Of_SQL_
 $sth->execute;
-
 # when we have no admin users, prompt for admin email address and password ...
 if ($sth->rows == 0) {
   my $login = "";
@@ -2000,8 +2024,10 @@ _End_Of_SQL_
         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.";
+        } elsif ( $pass1 !~ /^[a-zA-Z0-9-_]{3,16}$/ ) {
+          print "\n\nThe password must be 3-16 characters in length, " .
+                "and it may\ncontain only letters, digits, " .
+                "underscores (_), and hyphens (-).\n";
         }
       }
       print "\nPlease retype the password to verify: ";
@@ -2028,52 +2054,15 @@ _End_Of_SQL_
 
     $dbh->do(<<_End_Of_SQL_);
       INSERT INTO profiles
-      (login_name, realname, cryptpassword, admin)
-      VALUES ($login, $realname, $cryptedpassword, 1)
+      (login_name, realname, cryptpassword, groupset)
+      VALUES ($login, $realname, $cryptedpassword, 0x7fffffffffffffff)
 _End_Of_SQL_
-
-    # Put the admin in each group if not already    
-    my $query = "select userid from profiles where login_name = $login";    
-    $sth = $dbh->prepare($query); 
-    $sth->execute();
-    my ($userid) = $sth->fetchrow_array();
-
-    foreach my $group ( @groups ) {
-        my $query = "SELECT user_id FROM user_group_map WHERE group_id = $group AND user_id = $userid"; 
-        $sth = $dbh->prepare($query);
-        $sth->execute();
-
-        if ( !$sth->fetchrow_array() ) {
-            $dbh->do("INSERT INTO user_group_map VALUES ($userid, $group, 1)");
-        } else {
-            $dbh->do("UPDATE user_group_map SET canbless = 1 WHERE user_id = $userid AND group_id = $group");
-        }
-    }
-
   } else {
     $dbh->do(<<_End_Of_SQL_);
       UPDATE profiles
-      SET admin=1
+      SET groupset=0x7fffffffffffffff
       WHERE login_name=$login
 _End_Of_SQL_
-
-    # Put the admin in each group if not already    
-    my $query = "SELECT userid FROM profiles WHERE login_name = $login";
-    $sth = $dbh->prepare($query);
-    $sth->execute();
-    my ($userid) = $sth->fetchrow_array();
-    
-    foreach my $group ( @groups ) {
-        my $query = "SELECT user_id FROM user_group_map WHERE group_id = $group AND user_id = $userid";
-        $sth = $dbh->prepare($query);
-        $sth->execute();
-
-        if ( !$sth->fetchrow_array() ) {
-            $dbh->do("INSERT INTO user_group_map VALUES ($userid, $group, 1)");
-        } else {
-            $dbh->do("UPDATE user_group_map SET canbless = 1 WHERE user_id = $userid AND group_id = $group");
-        }
-    }
   }
   print "\n$login is now set up as the administrator account.\n";
 }
@@ -2088,7 +2077,7 @@ _End_Of_SQL_
 $sth = $dbh->prepare(<<_End_Of_SQL_);
   SELECT userid
   FROM profiles
-  WHERE admin=1
+  WHERE groupset=9223372036854775807
 _End_Of_SQL_
 $sth->execute;
 my ($adminuid) = $sth->fetchrow_array;
@@ -2215,6 +2204,7 @@ sub TableExists ($)
 # but aren't in very old bugzilla's (like 2.1)
 # Steve Stock (sstock@iconnect-inc.com)
 AddField('bugs', 'target_milestone', 'varchar(20) not null default "---"');
+AddField('bugs', 'groupset', 'bigint not null');
 AddField('bugs', 'qa_contact', 'mediumint not null');
 AddField('bugs', 'status_whiteboard', 'mediumtext not null');
 AddField('products', 'disallownew', 'tinyint not null');
@@ -2512,7 +2502,7 @@ if (!GetFieldDef('bugs', 'lastdiffed')) {
 # in my database.  This code detects that, cleans up the duplicates, and
 # then tweaks the table to declare the field to be unique.  What a pain.
 
-if (GetIndexDef('profiles', 'login_name')) {
+if (GetIndexDef('profiles', 'login_name')->[1]) {
     print "Searching for duplicate entries in the profiles table ...\n";
     while (1) {
         # This code is weird in that it loops around and keeps doing this
@@ -2645,6 +2635,7 @@ if (!GetFieldDef('bugs', 'everconfirmed')) {
 }
 AddField('products', 'maxvotesperbug', 'smallint not null default 10000');
 AddField('products', 'votestoconfirm', 'smallint not null');
+AddField('profiles', 'blessgroupset', 'bigint not null');
 
 # 2000-03-21 Adding a table for target milestones to 
 # database - matthew@zeroknowledge.com
@@ -2768,7 +2759,8 @@ if (!($sth->fetchrow_arrayref()->[0])) {
 
         foreach $key (keys(%dupes))
         {
-                $dupes{$key} =~ s/.*\*\*\* This bug has been marked as a duplicate of (\d{1,5}) \*\*\*.*?/$1/sm;
+                $dupes{$key} =~ /^.*\*\*\* This bug has been marked as a duplicate of (\d+) \*\*\*$/ms;
+                $dupes{$key} = $1;
                 $dbh->do("INSERT INTO duplicates VALUES('$dupes{$key}', '$key')");
                 #                                        BugItsADupeOf   Dupe
         }
@@ -2972,116 +2964,7 @@ AddField("bugs", "cclist_accessible", "tinyint not null default 1");
 # using the attachment manager can record changes to attachments.
 AddField("bugs_activity", "attach_id", "mediumint null");
 
-# 2002-01-20 dkl@redhat.com 68022
-# Drop bit, groupset, blessgroupset fields from certain tables after converting 
-# all users and bugs to new group schema
-if (GetFieldDef('groups', 'bit')) {
-    print "Converting bug database to new group schema format...\n";
-    my $superusergroupset = '9223372036854775807';
-    my %bit_groups = ();
-    my $sth;
-    my $sth2;
-    my $sth3;
-    
-    $sth = $dbh->prepare("select bit, group_id from groups order by bit");
-    $sth->execute();
-    while (my ($bit, $groupid) = $sth->fetchrow_array()) {
-        $bit_groups{$bit} = $groupid;
-    }
-    $sth->finish;
-
-    print "Populating user_group_map and bless_group_map table from users in profiles...\n";
-    foreach my $bit (sort keys %bit_groups) {
-        # Fix profiles table first
-        $sth = $dbh->prepare("select userid from profiles where (groupset & $bit) != 0 order by userid");
-        $sth->execute();
-        while (my ($userid) = $sth->fetchrow_array()) {
-            $sth2 = $dbh->prepare("select user_id from user_group_map where " . 
-                                  "user_id = $userid and group_id = $bit_groups{$bit}");
-            $sth2->execute();
-            my ($result) = $sth2->fetchrow_array();
-            if (!$result) { 
-                $sth2 = $dbh->prepare("insert into user_group_map values ($userid, $bit_groups{$bit}, 0)");
-                $sth2->execute();
-            }
-            $sth2->finish;   
-        }
-        # Next fix bless group privileges
-        $sth = $dbh->prepare("select userid from profiles where blessgroupset & $bit != 0 order by userid");
-        $sth->execute();
-        while (my ($userid) = $sth->fetchrow_array()) {
-            $sth2 = $dbh->prepare("select user_id from user_group_map " . 
-                                  "where user_id = $userid and group_id = $bit_groups{$bit}");
-            $sth2->execute();
-            my ($result) = $sth->fetchrow_array();
-            if (!$result) {
-                $sth2->prepare("update user_group_map set canbless = 1 where user_id = $userid " . 
-                               "and group_id = $bit_groups{$bit}");
-                $sth2->execute();
-            } else {
-                $sth2 = $dbh->prepare("insert into user_group_map values ($userid, $bit_groups{$bit}, 1)");
-                $sth2->execute();
-            }
-            $sth2->finish;
-        }
-        $sth->finish;
-    }
-    
-    # Fix super users by adding 1 to admin column
-    # We shouldn't need to add them to any groups since that would have been done earlier.
-    print "Populating profile's admin column for super users...\n";
-    $sth = $dbh->prepare("select userid from profiles where groupset = $superusergroupset order by userid");
-    $sth->execute();
-    while (my ($userid) = $sth->fetchrow_array()) {
-        my $sth2 = $dbh->prepare("update profiles set admin = 1 where userid = $userid");
-        $sth2->execute();
-        $sth2->finish;
-    }
-    $sth->finish;
-
-    # Fix bug groupsets
-    print "Populating bug_group_map table with bugs that are marked private...\n";   
-    foreach my $bit (sort keys %bit_groups) {
-        $sth = $dbh->prepare("select bug_id from bugs where (groupset & $bit) != 0 order by bug_id");
-        $sth->execute();
-        while (my ($id) = $sth->fetchrow_array()) {
-            $sth2 = $dbh->prepare("select bug_id from bug_group_map " .
-                                  "where bug_id = $id and group_id = $bit_groups{$bit}");
-            $sth2->execute();
-            my ($result) = $sth->fetchrow_array();
-            if (!$result) {
-                $sth2 = $dbh->prepare("insert into bug_group_map values ($id, $bit_groups{$bit})");
-                $sth2->execute();
-            }
-            $sth2->finish;
-        }
-        $sth->finish;
-    }
-
-    DropField('bugs', 'groupset');
-    DropField('profiles', 'groupset');
-    DropField('profiles', 'blessgroupset');
-    DropField('groups', 'bit');
-}
-
-# Added product_group_map table for product privacy
-# Adding product_id column to products table to allow this to work
-# 2002/01/24 dkl@redhat.com
-if (!GetFieldDef('products', 'product_id')) {
-    AddField('products', 'product_id', 'mediumint primary key auto_increment not null');
-    my $sth = $dbh->prepare('select product from products');
-    $sth->execute();
-    my $currproductid = 1;
-    while (my ($name) = $sth->fetchrow_array()) {
-        my $sth2 = $dbh->prepare("update products set product_id = $currproductid where product = " . 
-                                 $dbh->quote($name));
-        $sth2->execute();
-        $sth2->finish;
-    }
-    $sth->finish;
-}
-
-# 2001-01-17 bbaetz@student.usyd.edu.au bug 95732
+# 2002-02-04 bbaetz@student.usyd.edu.au bug 95732
 # Remove logincookies.cryptpassword, and delete entries which become
 # invalid
 if (GetFieldDef("logincookies", "cryptpassword")) {
@@ -3115,9 +2998,8 @@ if (GetFieldDef("bugs","qacontact_accessible")) {
 }
 
 # 2002-03-15 bbaetz@student.usyd.edu.au - bug 129466
-# 2002-05-13 preed@sigkill.com - bug 129446 patch backported to the 
+# 2002-05-13 preed@sigkill.com - bug 129446 patch backported to the
 #  BUGZILLA-2_14_1-BRANCH as a security blocker for the 2.14.2 release
-# 
 # Use the ip, not the hostname, in the logincookies table
 if (GetFieldDef("logincookies", "hostname")) {
     # We've changed what we match against, so all entries are now invalid
@@ -3128,6 +3010,25 @@ if (GetFieldDef("logincookies", "hostname")) {
     AddField("logincookies", "ipaddr", "varchar(40) NOT NULL");
 }
 
+# Fixup for Bug 101380
+# "Newlines, nulls, leading/trailing spaces are getting into summaries"
+
+my $controlchar_bugs =
+    $dbh->selectall_arrayref("SELECT short_desc, bug_id FROM bugs WHERE " .
+                             "'short_desc' REGEXP '[[:cntrl:]]'");
+if (@$controlchar_bugs)
+{
+    print 'Cleaning control characters from bug summaries...';
+    foreach (@$controlchar_bugs) {
+        my ($short_desc, $bug_id) = @$_;
+        print " $bug_id...";
+        $short_desc = clean_text($short_desc);
+        $dbh->do("UPDATE bugs SET short_desc = ? WHERE bug_id = ?",
+                 undef, $short_desc, $bug_id);
+    }
+    print " done.\n";
+}
+
 # If you had to change the --TABLE-- definition in any way, then add your
 # differential change code *** A B O V E *** this comment.
 #
@@ -3142,4 +3043,3 @@ if (GetFieldDef("logincookies", "hostname")) {
 
 unlink "data/versioncache";
 
-print "Reminder: Bugzilla now requires version 8.7 or later of sendmail.\n";

mozilla/webtools/bugzilla/colchange.cgi

@@ -34,50 +34,23 @@ use vars qw(
 
 require "CGI.pl";
 
-# Use the template toolkit (http://www.template-toolkit.org/) to generate
-# the user interface (HTML pages and mail messages) using templates in the
-# "template/" subdirectory.
-use Template;
-
-# Create the global template object that processes templates and specify
-# configuration parameters that apply to all templates processed in this script.
-my $template = Template->new(
-{
-    # Colon-separated list of directories containing templates.
-    INCLUDE_PATH => "template/custom:template/default",
-    # Allow templates to be specified with relative paths.
-    RELATIVE => 1,
-    PRE_CHOMP => 1,
-});
-
-# Define the global variables and functions that will be passed to the UI 
-# template.  Individual functions add their own values to this hash before
-# sending them to the templates they process.
-my $vars = 
-{
-    # Function for retrieving global parameters.
-    'Param' => \&Param, 
-
-    # Function for processing global parameters that contain references
-    # to other global parameters.
-    'PerformSubsts' => \&PerformSubsts,
-
-    # Function to search an array for a value   
-    'lsearch' => \&lsearch,
-};
+ConnectToDatabase();
+quietly_check_login();
 
 print "Content-type: text/html\n";
 
 # The master list not only says what fields are possible, but what order
 # they get displayed in.
 
-ConnectToDatabase();
 GetVersionTable();
 
 my @masterlist = ("opendate", "changeddate", "severity", "priority",
                   "platform", "owner", "reporter", "status", "resolution",
-                  "product", "component", "version", "os", "votes");
+                  "product", "component", "version", "os");
 
+if (Param("usevotes")) {
+    push(@masterlist, "votes");
+}
 if (Param("usetargetmilestone")) {
     push(@masterlist, "target_milestone");
 }
@@ -114,8 +87,8 @@ if (defined $::FORM{'rememberedquery'}) {
     my $list = join(" ", @collist);
     my $urlbase = Param("urlbase");
     my $cookiepath = Param("cookiepath");
-    print "Set-Cookie: COLUMNLIST=$list ; path=$cookiepath ; expires=Sun, 30-Jun-2029 00:00:00 GMT\n";
-    print "Set-Cookie: SPLITHEADER=$::FORM{'splitheader'} ; path=$cookiepath ; expires=Sun, 30-Jun-2029 00:00:00 GMT\n";
+    print "Set-Cookie: COLUMNLIST=$list ; path=$cookiepath ; expires=Sat, 30-Jun-2029 00:00:00 GMT\n";
+    print "Set-Cookie: SPLITHEADER=$::FORM{'splitheader'} ; path=$cookiepath ; expires=Sat, 30-Jun-2029 00:00:00 GMT\n";
     print "Refresh: 0; URL=buglist.cgi?$::FORM{'rememberedquery'}\n";
     print "\n";
     print "<META HTTP-EQUIV=Refresh CONTENT=\"1; URL=$urlbase"."buglist.cgi?$::FORM{'rememberedquery'}\">\n";

mozilla/webtools/bugzilla/collectstats.pl

@@ -57,7 +57,7 @@ foreach (@myproducts) {
 sub check_data_dir {
     my $dir = shift;
 
-    if (! -d) {
+    if (! -d $dir) {
         mkdir $dir, 0777;
         chmod 0777, $dir;
     }
@@ -82,7 +82,7 @@ sub collect_stats {
             if( $product eq "-All-" ) {
                 SendSQL("select count(bug_status) from bugs where bug_status='$status'");
             } else {
-                SendSQL("select count(bug_status) from bugs where bug_status='$status' and product='$product'");
+                SendSQL("select count(bug_status) from bugs where bug_status='$status' and product=" . SqlQuote($product));
             }
 
             push @row, FetchOneColumn();
@@ -92,7 +92,7 @@ sub collect_stats {
             if( $product eq "-All-" ) {
                 SendSQL("select count(resolution) from bugs where resolution='$resolution'");
             } else {
-                SendSQL("select count(resolution) from bugs where resolution='$resolution' and product='$product'");
+                SendSQL("select count(resolution) from bugs where resolution='$resolution' and product=" . SqlQuote($product));
             }
 
             push @row, FetchOneColumn();
@@ -118,7 +118,7 @@ FIN
 }
 
 sub calculate_dupes {
-    SendSQL("SELECT * FROM duplicates");
+    SendSQL("SELECT dupe_of, dupe FROM duplicates");
 
     my %dupes;
     my %count;

mozilla/webtools/bugzilla/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.9 2001-05-25 12:48:47 jake%acutex.net Exp $
+# $Id: bug_email.pl,v 1.9.12.3 2004-04-09 02:23:46 jocuri%softhome.net Exp $
 ###############################################################
 
 # 02/12/2000 (SML)
@@ -70,7 +70,9 @@ use diagnostics;
 use strict;
 use MIME::Parser;
 
-push @INC, "../."; # this script now lives in contrib
+chdir '..';        # this script lives in contrib
+push @INC, "contrib/.";
+push @INC, ".";
 
 require "globals.pl";
 require "BugzillaEmail.pm";
@@ -736,10 +738,10 @@ my $parser = new MIME::Parser;
 
 # Create and set the output directory:
 # FIXME: There should be a $BUGZILLA_HOME variable (SML)
-(-d "../data/mimedump-tmp") or mkdir "../data/mimedump-tmp",0755 or die "mkdir: $!";
-(-w "../data/mimedump-tmp") or die "can't write to directory";
+(-d "data/mimedump-tmp") or mkdir "data/mimedump-tmp",0755 or die "mkdir: $!";
+(-w "data/mimedump-tmp") or die "can't write to directory";
 
-$parser->output_dir("../data/mimedump-tmp");
+$parser->output_dir("data/mimedump-tmp");
     
 # Read the MIME message:
 my $entity = $parser->read(\*STDIN) or die "couldn't parse MIME stream";
@@ -841,7 +843,7 @@ if (Param("useqacontact")) {
     SendSQL("select initialqacontact from components where program=" .
             SqlQuote($Control{'product'}) .
             " and value=" . SqlQuote($Control{'component'}));
-    $Control{'qacontact'} = FetchOneColumn();
+    $Control{'qa_contact'} = FetchOneColumn();
 }
 
 # Set Assigned - assigned_to depends on the product, cause initialowner 
@@ -1233,8 +1235,8 @@ END
 	my $long_desc_query = "INSERT INTO longdescs SET bug_id=$id, who=$userid, bug_when=\'$bug_when\', thetext=" . SqlQuote($comment);
 	SendSQL($long_desc_query);
 
-	# Cool, the mail was successfull
-	system("cd .. ; ./processmail $id '$Sender'");
+	# Cool, the mail was successful
+        system("./processmail", $id, $SenderShort);
     } else {
 	$id = 0xFFFF;  # TEST !
 	print "\n-------------------------------------------------------------------------\n";

mozilla/webtools/bugzilla/contrib/bugzilla_email_append.pl

@@ -32,7 +32,9 @@ use diagnostics;
 use strict;
 use MIME::Parser;
 
-push @INC, "../."; # this script lives in contrib
+chdir "..";        # this script lives in contrib, change to main
+push @INC, "contrib";
+push @INC, "."; # this script lives in contrib
 require "globals.pl";
 require "BugzillaEmail.pm";
 
@@ -43,10 +45,10 @@ my $Comment = "";
 
 # Create and set the output directory:
 # FIXME: There should be a $BUGZILLA_HOME variable (SML)
-(-d "../data/mimedump-tmp") or mkdir "../data/mimedump-tmp",0755 or die "mkdir: $!";
-(-w "../data/mimedump-tmp") or die "can't write to directory";
+(-d "data/mimedump-tmp") or mkdir "data/mimedump-tmp",0755 or die "mkdir: $!";
+(-w "data/mimedump-tmp") or die "can't write to directory";
 
-$parser->output_dir("../data/mimedump-tmp");
+$parser->output_dir("data/mimedump-tmp");
     
 # Read the MIME message:
 my $entity = $parser->read(\*STDIN) or die "couldn't parse MIME stream";
@@ -115,11 +117,12 @@ my $Body = "Subject: " . $Subject . "\n" . $Comment;
 my $long_desc_query = "INSERT INTO longdescs SET bug_id=$found_id, who=$userid, bug_when=NOW(), thetext=" . SqlQuote($Body) . ";";
 SendSQL($long_desc_query);
 
-system("cd .. ; ./processmail $found_id '$SenderShort'");
+system("./processmail", $found_id, $SenderShort);
 
 sub DealWithError {
   my ($reason) = @_;
   print $reason . "\n";
+  exit 100;
 }
 
 # Yanking this wholesale from bug_email, 'cause I know this works.  I'll

mozilla/webtools/bugzilla/createaccount.cgi

@@ -30,19 +30,21 @@ use strict;
 use lib qw(.);
 
 require "CGI.pl";
-require "globals.pl";
 
 # Shut up misguided -w warnings about "used only once":
 use vars qw(
-%FORM
-$template
-$vars
+  %FORM
+  $template
+  $vars
 );
 
 ConnectToDatabase();
 
 # If we're using LDAP for login, then we can't create a new account here.
 if(Param('useLDAP')) {
+  # Just in case someone already has an account, let them get the correct
+  # footer on the error message
+  quietly_check_login();
   DisplayError("This site is using LDAP for authentication.  Please contact 
                 an LDAP administrator to get a new account created.",
                "Can't create LDAP accounts");
@@ -53,20 +55,19 @@ if(Param('useLDAP')) {
 # Clear out the login cookies.  Make people log in again if they create an
 # account; otherwise, they'll probably get confused.
 my $cookiepath = Param("cookiepath");
-print "Set-Cookie: Bugzilla_login= ; path=$cookiepath; expires=Sun, 30-Jun-80 00:00:00 GMT
-Set-Cookie: Bugzilla_logincookie= ; path=$cookiepath; expires=Sun, 30-Jun-80 00:00:00 GMT\n";
-
-print "Content-Type: text/html\n\n";
+print "Set-Cookie: Bugzilla_login= ; path=$cookiepath; expires=Tue, 15-Sep-1998 21:49:00 GMT
+Set-Cookie: Bugzilla_logincookie= ; path=$cookiepath; expires=Tue, 15-Sep-1998 21:49:00 GMT\n";
 
 my $login = $::FORM{'login'};
-my $realname = trim($::FORM{'realname'});
 
 if (defined($login)) {
     # We've been asked to create an account.
+    my $realname = trim($::FORM{'realname'});
     CheckEmailSyntax($login);
-    trick_taint($login);
     $vars->{'login'} = $login;
     
+    print "Content-Type: text/html\n\n";
+
     if (!ValidateNewUser($login)) {
         # Account already exists        
         $template->process("account/exists.html.tmpl", $vars)
@@ -83,6 +84,8 @@ if (defined($login)) {
     exit;
 }
 
+print "Content-Type: text/html\n\n";
+
 # Show the standard "would you like to create an account?" form.
 $template->process("account/create.html.tmpl", $vars)
   || ThrowTemplateError($template->error());

mozilla/webtools/bugzilla/defparams.pl

@@ -55,15 +55,16 @@ sub WriteParams {
         }
     }
 
-    my $tmpname = "data/params.$$";
-    open(FID, ">$tmpname") || die "Can't create $tmpname";
+    require File::Temp;
+    my ($fh, $tmpname) = File::Temp::tempfile("params.XXXXX",
+                                              DIR=>'data');
     my $v = $::param{'version'};
     delete $::param{'version'};  # Don't write the version number out to
                                 # the params file.
-    print FID GenerateCode('%::param');
+    print $fh (GenerateCode('%::param'));
     $::param{'version'} = $v;
-    print FID "1;\n";
-    close FID;
+    print $fh "1;\n";
+    close $fh;
     rename $tmpname, "data/params" || die "Can't rename $tmpname to data/params";
     ChmodDataFile('data/params', 0666);
 }
@@ -92,6 +93,12 @@ sub check_numeric {
 sub check_shadowdb {
     my ($value) = (@_);
     $value = trim($value);
+    if ($value =~ /^([A-Za-z0-9_]+)$/) {
+        $value = $1;
+    }
+    else {
+        return "Invalid database name.  Database names must include only alphanumeric characters and underscores.";
+    }
     if ($value eq "") {
         return "";
     }
@@ -126,7 +133,7 @@ DefParam("maintainer",
          'THE MAINTAINER HAS NOT YET BEEN SET');
 
 DefParam("urlbase",
-         "The URL that is the common initial leading part of all Bugzilla URLs. Must end with a / character.",
+         "The URL that is the common initial leading part of all Bugzilla URLs.",
          "t",
          "http://cvs-mirror.mozilla.org/webtools/bugzilla/",
          \&check_urlbase);
@@ -149,14 +156,20 @@ DefParam("usequip",
         "b",
         1);
 
-# Added parameter - dkl, 5/28/02
-DefParam("usetransactions",
-         "If this is on, Bugzilla will enable transaction support (currently PostgreSQL only).",
+# Added parameter - JMR, 2/16/00
+DefParam("usebuggroups",
+         "If this is on, Bugzilla will associate a bug group with each product in the database, and use it for querying bugs.",
          "b",
-         0);
+         0); 
+
+# Added parameter - JMR, 2/16/00
+DefParam("usebuggroupsentry",
+         "If this is on, Bugzilla will use product bug groups to restrict who can enter bugs.  Requires usebuggroups to be on as well.",
+         "b",
+         0); 
 
 DefParam("shadowdb",
-         "If non-empty, then this is the name of another database in which Bugzilla will keep a shadow read-only copy of everything.  This is done so that long slow read-only operations can be used against this db, and not lock up things for everyone else.  Turning on this parameter will create the given database; be careful not to use the name of an existing database with useful data in it!",
+         "If non-empty, then this is the name of another database in which Bugzilla will keep a shadow read-only copy of everything.  This is done so that long slow read-only operations can be used against this db, and not lock up things for everyone else.  Turning on this parameter will create the given database; be careful not to use the name of an existing database with useful data in it! The db_user you defined in the localconfig file must already have permission to access and write to the new database name before entering the name here, or the database creation will fail.  The same permissions should be granted as for the primary database used by Bugzilla.",
          "t",
          "",
          \&check_shadowdb);
@@ -200,7 +213,8 @@ DefParam("LDAPmailattribute",
 DefParam("mostfreqthreshold",
          "The minimum number of duplicates a bug needs to show up on the <A HREF=\"duplicates.cgi\">most frequently reported bugs page</a>. If you have a large database and this page takes a long time to load, try increasing this number.",
          "t",
-         "2");
+         "2",
+         \&check_numeric);
 
 
 DefParam("mybugstemplate",
@@ -215,9 +229,9 @@ DefParam("shutdownhtml",
          "");
 
 DefParam("sendmailnow",
-         "If this is on, Bugzilla will tell sendmail to send any e-mail immediately. If you have a large number of users with a large amount of e-mail traffic, enabling this option may dramatically slow down Bugzilla. Best used for smaller installations of Bugzilla.",
+         "Sites using anything older than version 8.12 of \'sendmail\' can achieve a significant performance increase in the UI -- at the cost of delaying the sending of mail -- by disabling this parameter. Sites using 'sendmail' 8.12 or higher should leave this on, as they will see no benefit from turning it off. Sites using an MTA other than 'sendmail' *must* leave it on, or no bug mail will be sent.",
          "b",
-         0);
+         1);
 
 DefParam("passwordmail",
 q{The email that gets sent to people to tell them their password.  Within
@@ -322,7 +336,7 @@ You will get this message once a day until you've dealt with these bugs!
 
 
 DefParam("defaultquery",
-          "This is the default query that initially comes up when you submit a bug.  It's in URL parameter format, which makes it hard to read.  Sorry!",
+          "This is the default query that initially comes up when you access the query page.  It's in URL parameter format, which makes it hard to read.  Sorry!",
          "t",
          "bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailqa_contact2=1&order=%22Importance%22");
 
@@ -394,6 +408,11 @@ DefParam("usedependencies",
          "b",
          1);
 
+DefParam("usevotes",
+         "Do you wish to allow users to vote for bugs? Note that in order for this to be effective, you will have to change the maximum votes allowed in a product to be non-zero in <a href=\"editproducts.cgi\">the product edit page</a>.",
+         "b",
+         1);
+
 DefParam("webdotbase",
          "It is possible to show graphs of dependent bugs. You may set this parameter to
 any of the following:
@@ -406,7 +425,11 @@ href=\"http://www.research.att.com/~north/cgi-bin/webdot.cgi\">webdot
 package</a> will generate the graphs remotely.</li>
 <li>A blank value will disable dependency graphing.</li>
 </ul>
-The default value is a publically-accessible webdot server.",
+The default value is a publically-accessible webdot server. If you change
+this value, make certain that the webdot server can read files from your
+data/webdot directory. On Apache you do this by editing the .htaccess file,
+for other systems the needed measures may vary. You can run checksetup.pl
+to recreate the .htaccess file if it has been lost.",
          "t",
          "http://www.research.att.com/~north/cgi-bin/webdot.cgi/%urlbase%",
          \&check_webdotbase);
@@ -424,8 +447,8 @@ sub check_webdotbase {
         # Check .htaccess allows access to generated images
         if(-e "data/webdot/.htaccess") {
             open HTACCESS, "data/webdot/.htaccess";
-            if(! grep(/png/,<HTACCESS>)) {
-                print "Dependency graph images are not accessible.\nDelete data/webdot/.htaccess and re-run checksetup.pl to rectify.\n";
+            if(! grep(/ \\\.png\$/,<HTACCESS>)) {
+                print "Dependency graph images are not accessible.\nAssuming that you have not modified the file, delete data/webdot/.htaccess and re-run checksetup.pl to rectify.\n";
             }
             close HTACCESS;
         }
@@ -582,7 +605,8 @@ DefParam("maxpatchsize",
           To accept patches of any size (subject to the limitations of 
           your server software), set this value to zero." ,
          "t",
-         '1000');
+         '1000',
+         \&check_numeric);
 
 DefParam("maxattachmentsize" , 
          "The maximum size (in kilobytes) of non-patch attachments.  Bugzilla 
@@ -590,6 +614,7 @@ DefParam("maxattachmentsize" ,
           in size.  To accept attachments of any size (subject to the
           limitations of your server software), set this value to zero." , 
          "t" , 
-         '1000');
+         '1000',
+         \&check_numeric);
 
 1;

mozilla/webtools/bugzilla/describecomponents.cgi

@@ -23,7 +23,6 @@
 
 use vars qw(
   %FORM
-  %proddesc
   $userid
 );
 
@@ -35,17 +34,25 @@ use lib qw(.);
 require "CGI.pl";
 
 ConnectToDatabase();
-GetVersionTable();
+quietly_check_login();
 
-my $userid = quietly_check_login();
+GetVersionTable();
 
 if (!defined $::FORM{'product'}) {
     # Reference to a subset of %::proddesc, which the user is allowed to see
     my %products;
 
-    foreach my $p (@::legal_product) {
-        next if !CanSeeProduct($userid, $p);
-        $products{$p} = $::proddesc{$p};
+    if (Param("usebuggroups")) {
+        # OK, now only add products the user can see
+        confirm_login() unless $::userid;
+        foreach my $p (@::legal_product) {
+            if (!GroupExists($p) || UserInGroup($p)) {
+                $products{$p} = $::proddesc{$p};
+            }
+        }
+    }
+    else {
+          %products = %::proddesc;
     }
 
     my $prodsize = scalar(keys %products);
@@ -83,9 +90,12 @@ grep($product eq $_ , @::legal_product)
   && exit;
 
 # Make sure the user is authorized to access this product.
-!CanSeeProduct($userid, $product)
-      && DisplayError("You are not authorized to access that product.")
-      && exit;
+if (Param("usebuggroups") && GroupExists($product)) {
+    confirm_login() unless $::userid;
+    UserInGroup($product)
+      || DisplayError("You are not authorized to access that product.")
+        && exit;
+}
 
 ######################################################################
 # End Data/Security Validation

mozilla/webtools/bugzilla/describekeywords.cgi

@@ -32,12 +32,12 @@ use vars qw($vars $template);
 
 ConnectToDatabase();
 
-my $userid = quietly_check_login();
+quietly_check_login();
 
 SendSQL("SELECT keyworddefs.name, keyworddefs.description, 
                 COUNT(keywords.bug_id)
          FROM keyworddefs LEFT JOIN keywords ON keyworddefs.id=keywords.keywordid
-         GROUP BY keyworddefs.id, keyworddefs.name, keyworddefs.description, keywords.bug_id
+         GROUP BY keyworddefs.id
          ORDER BY keyworddefs.name");
 
 my @keywords;
@@ -51,7 +51,7 @@ while (MoreSQLData()) {
 }
    
 $vars->{'keywords'} = \@keywords;
-$vars->{'caneditkeywords'} = UserInGroup($userid, "editkeywords");
+$vars->{'caneditkeywords'} = UserInGroup("editkeywords");
 
 print "Content-type: text/html\n\n";
 $template->process("reports/keywords.html.tmpl", $vars)

mozilla/webtools/bugzilla/docs/README.docs

@@ -2,35 +2,33 @@ Welcome to the Bugzilla documentation project!
 You'll find these directories and files here:
 
 README.docs	# This README file
-html/		# The compiled HTML docs from SGML sources (do not edit)
-sgml/		# The original SGML doc sources (edit these)
-txt/		# The compiled text docs from SGML sources
-ps/		# The compiled PostScript docs from SGML sources
-pdf/		# The compiled Adobe PDF docs from SGML sources
+html/		# The compiled HTML docs from XML sources (do not edit)
+txt/		# The compiled text docs from XML sources (do not edit)
+xml/		# The original XML doc sources (edit these)
 
-A note about SGML:
-  The documentation is written in DocBook 3.1/4.1 SGML, and attempts to adhere
-to the LinuxDoc standards everywhere applicable (http://www.linuxdoc.org).
-Please consult "The LDP Author Guide" at linuxdoc.org for details on how
-to set up your personal environment for compiling SGML files.
+A note about the XML:
+  The documentation is written in DocBook 4.1.2, and attempts to adhere
+to the LinuxDoc standards where applicable (http://www.tldp.org).
+Please consult "The LDP Author Guide" at tldp.org for details on how
+to set up your personal environment for compiling XML files.
   If you need to make corrections to typographical errors, or other minor
-editing duties, feel free to use any text editor to make the changes.  SGML
+editing duties, feel free to use any text editor to make the changes.  XML
 is not rocket science -- simply make sure your text appears between 
 appropriate tags (like <para>This is a paragraph</para>) and we'll be fine.
 If you are making more extensive changes, please ensure you at least validate
-your SGML before checking it in with something like:
-	nsgmls -s Bugzilla-Guide.sgml
+your XML before checking it in with something like:
+	nsgmls -s $JADE_PUB/xml.dcl Bugzilla-Guide.xml
 
-  When you validate, please validate the master document (Bugzilla-Guide.sgml)
+  When you validate, please validate the master document (Bugzilla-Guide.xml)
 as well as the document you edited to ensure there are no critical errors.
 The following errors are considered "normal" when validating with nsgmls:
 
  DTDDECL catalog entries are not supported
  "DOCTYPE" declaration not allowed in instance
 
-  The reason these occur is that free sgml validators do not yet support
+  The reason these occur is that free sgml/xml validators do not yet support
 the DTDDECL catalog entries, and I've included DOCTYPE declarations in
-entities referenced from Bugzilla-Guide.sgml so these entities can compile
+entities referenced from Bugzilla-Guide.xml so these entities can compile
 individually, if necessary.  I suppose I ought to comment them out at some
 point, but for now they are convenient and don't hurt anything.
 
@@ -39,13 +37,13 @@ documentation.  Please address comments and questions to the newsgroup:
 news://news.mozilla.org/netscape/public/mozilla/webtools .
 
 ==========
-HOW TO SET UP YOUR OWN SGML EDITING ENVIRONMENT:
+HOW TO SET UP YOUR OWN XML EDITING ENVIRONMENT:
 ==========
 
-Trying to set up an SGML/XML Docbook editing environment the 
+Trying to set up an XML Docbook editing environment the 
 first time can be a daunting task.
 I use Linux-Mandrake, in part, because it has a fully-functional
-SGML/XML Docbook editing environment included as part of the
+XML Docbook editing environment included as part of the
 distribution CD's.  If you have easier instructions for how to
 do this for a particular Linux distribution or platform, please
 let the team know at the mailing list: mozilla-webtools@mozilla.org.
@@ -74,9 +72,10 @@ sgml-common
 
 If you're getting these from RedHat, make sure you get the ones in the
 rawhide area.  The ones in the 7.2 distribution are too old and don't
-include the XML stuff.
+include the XML stuff.  The packages distrubuted with RedHat 8.0 and 9
+and known to work.
 
-Download "ldp.dsl" from the Resources page on linuxdoc.org.  This is the 
+Download "ldp.dsl" from the Resources page on tldp.org.  This is the 
 stylesheet I use to get the HTML and text output.  It works well, and has a 
 nice, consistent look with the rest of the linuxdoc documents.  You'll have to 
 adjust the paths in ldp.dsl at the top of the file to reflect the actual 
@@ -92,6 +91,8 @@ dsssl>
 Note the difference is the top one points to the HTML docbook stylesheet, 
 and the next one points to the PRINT docbook stylesheet.
 
+Also note that modifying ldp.dsl doesn't seem to be needed on RedHat 9.
+
   You know, this sure looks awful involved.  Anyway, once you have this in
 place, add to your .bashrc:
 export SGML_CATALOG_FILES=/etc/sgml/catalog
@@ -111,13 +112,16 @@ for tcsh users.
 folders are anywhere else on your system (for example, the openjade version
 might change if you get a new version at some point).
 
-  I suggest xemacs for editing your SGML/XML Docbook documents.  The darn
+  I suggest xemacs for editing your XML Docbook documents.  The darn
 thing just works, and generally includes PSGML mode by default.  Not to
 mention you can validate the SGML from right within it without having to
 remember the command-line syntax for nsgml (not that it's that hard
 anyway).  If not, you can download psgml at
 http://www.sourceforge.net/projects/psgml.
 
+  Another good editor is the latest releases of vim and gvim.  Vim will
+recognize DocBook tags and give them a different color than unreconized tags.
+
 ==========
 NOTES:
 ==========
@@ -125,15 +129,17 @@ NOTES:
   Here are the commands I use to maintain this documentation.
   You MUST have DocBook 4.1.2 set up correctly in order for this to work.
 
+  These commands can be run all at once using the ./makedocs.pl script.
+
 To create HTML documentation:
 bash$ cd html
 bash$ jade -t sgml -i html -d $LDP_HOME/ldp.dsl\#html \
-$JADE_PUB/xml.dcl ../sgml/Bugzilla-Guide.sgml
+$JADE_PUB/xml.dcl ../xml/Bugzilla-Guide.xml
 
 To create HTML documentation as a single big HTML file:
 bash$ cd html
 bash$ jade -V nochunks -t sgml -i html -d $LDP_HOME/ldp.dsl\#html \
-$JADE_PUB/xml.dcl ../sgml/Bugzilla-Guide.sgml >Bugzilla-Guide.html
+$JADE_PUB/xml.dcl ../xml/Bugzilla-Guide.xml >Bugzilla-Guide.html
 
 To create TXT documentation as a single big TXT file:
 bash$ cd txt

mozilla/webtools/bugzilla/docs/html/about.html

@@ -1,178 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->About This Guide</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="PREVIOUS"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="NEXT"
-TITLE="Purpose and Scope of this Guide"
-HREF="aboutthisguide.html"></HEAD
-><BODY
-CLASS="chapter"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="index.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="aboutthisguide.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="chapter"
-><H1
-><A
-NAME="about">Chapter 1. About This Guide</H1
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->1.1. <A
-HREF="aboutthisguide.html"
->Purpose and Scope of this Guide</A
-></DT
-><DT
->1.2. <A
-HREF="copyright.html"
->Copyright Information</A
-></DT
-><DT
->1.3. <A
-HREF="disclaimer.html"
->Disclaimer</A
-></DT
-><DT
->1.4. <A
-HREF="newversions.html"
->New Versions</A
-></DT
-><DT
->1.5. <A
-HREF="credits.html"
->Credits</A
-></DT
-><DT
->1.6. <A
-HREF="translations.html"
->Translations</A
-></DT
-><DT
->1.7. <A
-HREF="conventions.html"
->Document Conventions</A
-></DT
-></DL
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="aboutthisguide.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->The Bugzilla Guide</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
->&nbsp;</TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Purpose and Scope of this Guide</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/aboutthisguide.html

@@ -1,184 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Purpose and Scope of this Guide</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="About This Guide"
-HREF="about.html"><LINK
-REL="PREVIOUS"
-TITLE="About This Guide"
-HREF="about.html"><LINK
-REL="NEXT"
-TITLE="Copyright Information"
-HREF="copyright.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="about.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 1. About This Guide</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="copyright.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="aboutthisguide">1.1. Purpose and Scope of this Guide</H1
-><P
->&#13;      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
->&#13;      This release of the Bugzilla Guide is the
-      <EM
->2.16</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
->odd-numbered</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. 
-    </P
-><P
->&#13;      Newer revisions of the Bugzilla Guide follow the numbering
-      conventions of the main-tree Bugzilla releases, available at
-      <A
-HREF="http://www.bugzilla.org/"
-TARGET="_top"
->http://www.bugzilla.org/</A
->.  Intermediate releases will have
-      a minor revision number following a period.  The current version
-      of Bugzilla, as of this writing (April 2nd, 2002) is 2.16; 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.16.1, 2.16.2, etc.).
-      Got it?  Good.
-    </P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="about.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="copyright.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->About This Guide</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="about.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Copyright Information</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/administration.html

@@ -1,233 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Administering Bugzilla</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="PREVIOUS"
-TITLE="Win32 Installation Notes"
-HREF="win32.html"><LINK
-REL="NEXT"
-TITLE="Post-Installation Checklist"
-HREF="postinstall-check.html"></HEAD
-><BODY
-CLASS="chapter"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="win32.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="postinstall-check.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="chapter"
-><H1
-><A
-NAME="administration">Chapter 4. Administering Bugzilla</H1
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->4.1. <A
-HREF="postinstall-check.html"
->Post-Installation Checklist</A
-></DT
-><DT
->4.2. <A
-HREF="useradmin.html"
->User Administration</A
-></DT
-><DD
-><DL
-><DT
->4.2.1. <A
-HREF="useradmin.html#defaultuser"
->Creating the Default User</A
-></DT
-><DT
->4.2.2. <A
-HREF="useradmin.html#manageusers"
->Managing Other Users</A
-></DT
-></DL
-></DD
-><DT
->4.3. <A
-HREF="programadmin.html"
->Product, Component, Milestone, and Version
-      Administration</A
-></DT
-><DD
-><DL
-><DT
->4.3.1. <A
-HREF="programadmin.html#products"
->Products</A
-></DT
-><DT
->4.3.2. <A
-HREF="programadmin.html#components"
->Components</A
-></DT
-><DT
->4.3.3. <A
-HREF="programadmin.html#versions"
->Versions</A
-></DT
-><DT
->4.3.4. <A
-HREF="programadmin.html#milestones"
->Milestones</A
-></DT
-><DT
->4.3.5. <A
-HREF="programadmin.html#voting"
->Voting</A
-></DT
-><DT
->4.3.6. <A
-HREF="programadmin.html#groups"
->Groups and Group Security</A
-></DT
-></DL
-></DD
-><DT
->4.4. <A
-HREF="security.html"
->Bugzilla Security</A
-></DT
-></DL
-></DIV
-><FONT
-COLOR="RED"
->&#13;    Or, I just got this cool thing installed.  Now what the heck do I
-    do with it?
-  </FONT
-><P
->&#13;    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"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="win32.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="postinstall-check.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Win32 Installation Notes</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
->&nbsp;</TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Post-Installation Checklist</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/bonsai.html

@@ -1,160 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Bonsai</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Integrating Bugzilla with Third-Party Tools"
-HREF="integration.html"><LINK
-REL="PREVIOUS"
-TITLE="Integrating Bugzilla with Third-Party Tools"
-HREF="integration.html"><LINK
-REL="NEXT"
-TITLE="CVS"
-HREF="cvs.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="integration.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 5. Integrating Bugzilla with Third-Party Tools</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="cvs.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="bonsai">5.1. Bonsai</H1
-><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"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="integration.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="cvs.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Integrating Bugzilla with Third-Party Tools</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="integration.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->CVS</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/bsdinstall.html

@@ -1,149 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->BSD Installation Notes</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Installation"
-HREF="installation.html"><LINK
-REL="PREVIOUS"
-TITLE="Mac OS X Installation Notes"
-HREF="osx.html"><LINK
-REL="NEXT"
-TITLE="Installation General Notes"
-HREF="geninstall.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="osx.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 3. Installation</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="geninstall.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="bsdinstall">3.4. BSD Installation Notes</H1
-><P
->&#13;      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"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="osx.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="geninstall.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Mac OS X Installation Notes</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="installation.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Installation General Notes</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/bzhacking.html

@@ -1,492 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Hacking Bugzilla</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><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
-SUMMARY="Header navigation 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"
-ACCESSKEY="P"
->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"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="bzhacking">D.5. Hacking Bugzilla</H1
-><P
->&#13;      The following is a guide for reviewers when checking code into Bugzilla's
-      CVS repostory at mozilla.org.  If you wish to submit patches to Bugzilla,
-      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.
-    </P
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="AEN2436">D.5.1. Things that have caused problems and should be avoided</H2
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->&#13;            Usage of variables in Regular Expressions
-          </P
-><P
->&#13;            It is very important that you don't use a variable in a regular
-            expression unless that variable is supposed to contain an expression.
-            This especially applies when using grep.  You should use:
-          </P
-><P
->&#13;            <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->&#13;grep ($_ eq $value, @array);
-            </PRE
-></FONT
-></TD
-></TR
-></TABLE
->
-          </P
-><P
->&#13;            -- NOT THIS --
-          </P
-><P
->&#13;            <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->&#13;grep (/$value/, @array);
-            </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
->&#13;              If you need to use a non-expression variable inside of an expression, be
-              sure to quote it properly (using <TT
-CLASS="function"
->\Q..\E</TT
->).
-            </P
-></TD
-></TR
-></TABLE
-></DIV
-></LI
-></OL
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="AEN2450">D.5.2. Coding Style for Bugzilla</H2
-><P
->&#13;        While it's true that not all of the code currently in Bugzilla adheres to
-        this (or any) styleguide, it is something that is being worked toward.  Therefore,
-        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 :).
-      </P
-><P
->&#13;        The Bugzilla development team has decided to adopt the perl style guide as
-        published by Larry Wall.  This giude can be found in <SPAN
-CLASS="QUOTE"
->"Programming
-        Perl"</SPAN
-> (the camel book) or by typing <B
-CLASS="command"
->man perlstyle</B
-> at
-        your favorite shell prompt.
-      </P
-><P
->&#13;        What appears below if a brief summary, please refer to the perl style
-        guide if you don't see your question covered here.  It is much better to submit
-	a patch which fails these criteria than no patch at all, but please try to meet
-	these minimum standards when submitting code to Bugzilla.
-      </P
-><P
-></P
-><UL
-><LI
-><P
->&#13;            Whitespace
-          </P
-><P
->&#13;            Bugzilla's preferred indentation is 4 spaces (no tabs, please).
-          </P
-></LI
-><LI
-><P
->&#13;            Curly braces.
-          </P
-><P
->&#13;            The opening brace of a block should be on the same line as the statement
-            that is causing the block and the closing brace should be at the same
-            indentation level as that statement, for example:
-          </P
-><P
->&#13;            <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->&#13;if ($var) {
-    print "The variable is true";
-}
-else {
-    print "Try again";
-}
-            </PRE
-></FONT
-></TD
-></TR
-></TABLE
->
-          </P
-><P
->&#13;            -- NOT THIS --
-          </P
-><P
->&#13;            <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->&#13;if ($var)
-{
-    print "The variable is true";
-}
-else
-{
-    print "Try again";
-}
-            </PRE
-></FONT
-></TD
-></TR
-></TABLE
->
-          </P
-></LI
-><LI
-><P
->&#13;	    Cookies
-	  </P
-><P
->&#13;	    Bugzilla uses cookies to ease the user experience, but no new patches
-	    should <EM
->require</EM
-> user-side cookies.
-	  </P
-></LI
-><LI
-><P
->&#13;            File Names
-          </P
-><P
->&#13;            File names for bugzilla code and support documention should be legal across
-            multiple platforms. <TT
-CLASS="computeroutput"
->\ / : * ? " &#60; &#62;</TT
->
-            and <TT
-CLASS="computeroutput"
->|</TT
-> 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.
-          </P
-></LI
-><LI
-><P
->&#13;	    Javascript dependencies
-	  </P
-><P
->&#13;	    While Bugzilla uses Javascript to make the user experience easier, no patch
-	    to Bugzilla should <EM
->require</EM
-> Javascript.
-	  </P
-></LI
-><LI
-><P
->&#13;	    Patch Format
-	  </P
-><P
->&#13;	    All patches submitted for inclusion into Bugzilla should be in the form of a
-	    <SPAN
-CLASS="QUOTE"
->"unified diff"</SPAN
->.  This comes from using <SPAN
-CLASS="QUOTE"
->"diff -u"</SPAN
->
-	    instead of simply <SPAN
-CLASS="QUOTE"
->"diff"</SPAN
-> when creating your patch.  This will
-	    result in quicker acceptance of the patch.
-	  </P
-></LI
-><LI
-><P
->&#13;	    Schema Changes
-	  </P
-><P
->&#13;	    If you make schema changes, you should modify <TT
-CLASS="filename"
->sanitycheck.cgi</TT
->
-	    to support the new schema.  All referential columns should be checked.
-	  </P
-></LI
-><LI
-><P
->&#13;	    Taint Mode
-	  </P
-><P
->&#13;	    All new cgis must run in Taint mode (Perl taint and DBI taint), and existing cgi's
-	    which run in taint mode must not have taint mode turned off.
-	  </P
-></LI
-><LI
-><P
->&#13;	    Templatization
-	  </P
-><P
->&#13;	    Patches to Bugzilla need to support templates so they do not force user interface choices
-	    on Bugzilla administrators.
-	  </P
-></LI
-><LI
-><P
->&#13;            Variable Names
-          </P
-><P
->&#13;            If a variable is scoped globally (<TT
-CLASS="computeroutput"
->$::variable</TT
->)
-            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,
-            <TT
-CLASS="computeroutput"
->$ret</TT
-> could be used as a staging variable for a
-             routine's return value as the line <TT
-CLASS="computeroutput"
->return $ret;</TT
->
-             will make it blatantly obvious what the variable holds and most likely be shown
-             on the same screen as <TT
-CLASS="computeroutput"
->my $ret = "";</TT
->.
-          </P
-></LI
-><LI
-><P
->&#13;            Cross Database Compatability
-          </P
-><P
->&#13;            Bugzilla was originally written to work with MySQL and therefore took advantage
-            of some of its features that aren't contained in other RDBMS software.  These
-            should be avoided in all new code.  Examples of these features are enums and
-            <TT
-CLASS="function"
->encrypt()</TT
->.
-          </P
-></LI
-><LI
-><P
->&#13;            Cross Platform Compatability
-          </P
-><P
->&#13;            While Bugzilla was written to be used on Unix based systems (and Unix/Linux is
-            still the only officially supported platform) there are many who desire/need to
-            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.
-          </P
-></LI
-></UL
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="quicksearch.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="gfdl.html"
-ACCESSKEY="N"
->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"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->GNU Free Documentation License</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/cmdline.html

@@ -1,269 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Command-line Bugzilla Queries</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><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 setperl.csh Utility"
-HREF="setperl.html"><LINK
-REL="NEXT"
-TITLE="The Quicksearch Utility"
-HREF="quicksearch.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="setperl.html"
-ACCESSKEY="P"
->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="quicksearch.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="cmdline">D.3. Command-line Bugzilla Queries</H1
-><P
->&#13;      Users can query Bugzilla from the command line using this suite
-      of utilities.
-    </P
-><P
->&#13;      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"
-    </P
-><P
->&#13;      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
->&#13;      The columlist is taken from the COLUMNLIST environment variable.
-      This is equivalent to the "Change Columns" option when you list
-      bugs in buglist.cgi.  If you have already used Bugzilla, use
-      <B
-CLASS="command"
->grep COLUMLIST ~/.netscape/cookies</B
-> to see
-      your current COLUMNLIST setting.
-    </P
-><P
->&#13;      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
-CLASS="command"
->sed -e 's/,/ /g' | wc |
-	awk '{printf $2 "\n"}'</B
->
-    </P
-><P
->&#13;      Akkana says she has good results piping buglist output through
-      <B
-CLASS="command"
->w3m -T text/html -dump</B
->
-    </P
-><DIV
-CLASS="procedure"
-><OL
-TYPE="1"
-><LI
-><P
->&#13;	  Download three files:
-	</P
-><OL
-CLASS="SUBSTEPS"
-TYPE="a"
-><LI
-><P
->&#13;	      <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->bash$</TT
-> <B
-CLASS="command"
->wget -O
-		  query.conf
-		  'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26157'</B
-> </TT
->
-	    </P
-></LI
-><LI
-><P
->&#13;	      <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->bash$</TT
-> <B
-CLASS="command"
->wget -O
-		  buglist
-		  'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26944'</B
-> </TT
->
-	    </P
-></LI
-><LI
-><P
->&#13;	      <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->bash#</TT
-> <B
-CLASS="command"
->wget -O
-		  bugs
-		  'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26215'</B
-> </TT
->
-	    </P
-></LI
-></OL
-></LI
-><LI
-><P
->&#13;	  Make your utilities executable:
-	  <TT
-CLASS="computeroutput"
->&#13;	    <TT
-CLASS="prompt"
->bash$</TT
->
-	    <B
-CLASS="command"
->chmod u+x buglist bugs</B
->
-	  </TT
->
-	</P
-></LI
-></OL
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="setperl.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="quicksearch.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->The setperl.csh Utility</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="patches.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->The Quicksearch Utility</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/contributors.html

@@ -1,150 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Contributors</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="About This Guide"
-HREF="about.html"><LINK
-REL="PREVIOUS"
-TITLE="Credits"
-HREF="credits.html"><LINK
-REL="NEXT"
-TITLE="Feedback"
-HREF="feedback.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="credits.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 1. About This Guide</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="feedback.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="contributors">1.6. Contributors</H1
-><P
->&#13;      Thanks go to these people for significant contributions to this
-      documentation (in no particular order):
-    </P
-><P
->&#13;      Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen, Ron
-      Teitelbaum, Jacob Steenhagen, Joe Robins
-    </P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="credits.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="feedback.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Credits</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="about.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Feedback</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/conventions.html

@@ -1,462 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Document Conventions</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="About This Guide"
-HREF="about.html"><LINK
-REL="PREVIOUS"
-TITLE="Translations"
-HREF="translations.html"><LINK
-REL="NEXT"
-TITLE="Using Bugzilla"
-HREF="using.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="translations.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 1. About This Guide</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="using.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="conventions">1.7. Document Conventions</H1
-><P
->&#13;    This document uses the following conventions
-  </P
-><DIV
-CLASS="informaltable"
-><A
-NAME="AEN91"><P
-></P
-><TABLE
-BORDER="0"
-CLASS="CALSTABLE"
-><THEAD
-><TR
-><TH
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Descriptions</TH
-><TH
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Appearance</TH
-></TR
-></THEAD
-><TBODY
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Warnings</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-><DIV
-CLASS="caution"
-><P
-></P
-><TABLE
-CLASS="caution"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/caution.gif"
-HSPACE="5"
-ALT="Caution"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Don't run with scissors!</P
-></TD
-></TR
-></TABLE
-></DIV
-></TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Hint</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-><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
->Warm jar lids under the hot tap to loosen them.</P
-></TD
-></TR
-></TABLE
-></DIV
-></TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Notes</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Dear John...</P
-></TD
-></TR
-></TABLE
-></DIV
-></TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Information requiring special attention</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-><DIV
-CLASS="warning"
-><P
-></P
-><TABLE
-CLASS="warning"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/warning.gif"
-HSPACE="5"
-ALT="Warning"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Read this or the cat gets it.</P
-></TD
-></TR
-></TABLE
-></DIV
-></TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->File Names</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-><TT
-CLASS="filename"
->file.extension</TT
-></TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Directory Names</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-><TT
-CLASS="filename"
->directory</TT
-></TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Commands to be typed</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-><B
-CLASS="command"
->command</B
-></TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Applications Names</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-><SPAN
-CLASS="application"
->application</SPAN
-></TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-><I
-CLASS="foreignphrase"
->Prompt</I
-> of users command under bash shell</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->bash$</TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-><I
-CLASS="foreignphrase"
->Prompt</I
-> of root users command under bash shell</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->bash#</TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-><I
-CLASS="foreignphrase"
->Prompt</I
-> of user command under tcsh shell</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->tcsh$</TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Environment Variables</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-><TT
-CLASS="envar"
->VARIABLE</TT
-></TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Emphasized word</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-><EM
->word</EM
-></TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
->Code Example</TD
-><TD
-ALIGN="LEFT"
-VALIGN="MIDDLE"
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
-><TT
-CLASS="sgmltag"
->&#60;para&#62;</TT
->Beginning and end of paragraph<TT
-CLASS="sgmltag"
->&#60;/para&#62;</TT
-></PRE
-></FONT
-></TD
-></TR
-></TABLE
-></TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="translations.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="using.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Translations</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="about.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Using Bugzilla</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/copyright.html

@@ -1,191 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Copyright Information</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="About This Guide"
-HREF="about.html"><LINK
-REL="PREVIOUS"
-TITLE="Purpose and Scope of this Guide"
-HREF="aboutthisguide.html"><LINK
-REL="NEXT"
-TITLE="Disclaimer"
-HREF="disclaimer.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="aboutthisguide.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 1. About This Guide</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="disclaimer.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="copyright">1.2. Copyright Information</H1
-><A
-NAME="AEN39"><TABLE
-BORDER="0"
-WIDTH="100%"
-CELLSPACING="0"
-CELLPADDING="0"
-CLASS="BLOCKQUOTE"
-><TR
-><TD
-WIDTH="10%"
-VALIGN="TOP"
->&nbsp;</TD
-><TD
-WIDTH="80%"
-VALIGN="TOP"
-><P
->&#13;	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
-WIDTH="10%"
-VALIGN="TOP"
->&nbsp;</TD
-></TR
-><TR
-><TD
-COLSPAN="2"
-ALIGN="RIGHT"
-VALIGN="TOP"
->--<SPAN
-CLASS="attribution"
->Copyright (c) 2000-2002 Matthew P. Barnson and The Bugzilla Team</SPAN
-></TD
-><TD
-WIDTH="10%"
->&nbsp;</TD
-></TR
-></TABLE
-><P
->&#13;      If you have any questions regarding this document, its
-      copyright, or publishing this document in non-electronic form,
-      please contact The Bugzilla Team. 
-    </P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="aboutthisguide.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="disclaimer.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Purpose and Scope of this Guide</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="about.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Disclaimer</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/credits.html

@@ -1,208 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Credits</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="About This Guide"
-HREF="about.html"><LINK
-REL="PREVIOUS"
-TITLE="New Versions"
-HREF="newversions.html"><LINK
-REL="NEXT"
-TITLE="Translations"
-HREF="translations.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="newversions.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 1. About This Guide</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="translations.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="credits">1.5. Credits</H1
-><P
->&#13;      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
->&#13;      <A
-HREF="mailto://mbarnson@sisna.com"
-TARGET="_top"
->Matthew P. Barnson</A
->
-      for pulling together the Bugzilla Guide and shepherding it to 2.14.
-    </P
-><P
->&#13;      <A
-HREF="mailto://terry@mozilla.org"
-TARGET="_top"
->Terry Weissman</A
->
-      for initially writing Bugzilla and creating the
-      README upon which the UNIX installation documentation is largely based.
-    </P
-><P
->&#13;      <A
-HREF="mailto://tara@tequilarista.org"
-TARGET="_top"
->Tara
-	Hernandez</A
->  for keeping Bugzilla development going
-      strong after Terry left Mozilla.org
-    </P
-><P
->&#13;      <A
-HREF="mailto://dkl@redhat.com"
-TARGET="_top"
->Dave Lawrence</A
-> for
-      providing insight into the key differences between Red Hat's
-      customized Bugzilla, and being largely responsible for the "Red
-      Hat Bugzilla" appendix
-    </P
-><P
->&#13;      <A
-HREF="mailto://endico@mozilla.org"
-TARGET="_top"
->Dawn Endico</A
-> for
-      being a hacker extraordinaire and putting up with my incessant
-      questions and arguments on irc.mozilla.org in #mozwebtools
-    </P
-><P
->&#13;      Last but not least, all the members of the <A
-HREF="news://news.mozilla.org/netscape/public/mozilla/webtools"
-TARGET="_top"
-> netscape.public.mozilla.webtools</A
-> newsgroup.  Without your discussions, insight, suggestions, and patches, this could never have happened.
-    </P
-><P
->&#13;      Thanks also go to the following people for significant contributions 
-      to this documentation (in no particular order):
-    </P
-><P
->&#13;      Zach Liption, Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen,
-      Ron Teitelbaum, Jacob Steenhagen, Joe Robins.
-    </P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="newversions.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="translations.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->New Versions</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="about.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Translations</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/cvs.html

@@ -1,174 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->CVS</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Integrating Bugzilla with Third-Party Tools"
-HREF="integration.html"><LINK
-REL="PREVIOUS"
-TITLE="Bonsai"
-HREF="bonsai.html"><LINK
-REL="NEXT"
-TITLE="Perforce SCM"
-HREF="scm.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="bonsai.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 5. Integrating Bugzilla with Third-Party Tools</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="scm.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="cvs">5.2. CVS</H1
-><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
->&#13;      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
->&#13;      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"
->&#13;      http://homepages.kcbbs.gen.nz/~tonyg/</A
->, under the
-      <SPAN
-CLASS="QUOTE"
->"cvszilla"</SPAN
-> link.
-    </P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="bonsai.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="scm.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Bonsai</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="integration.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Perforce SCM</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/database.html

@@ -1,185 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->The Bugzilla Database</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="PREVIOUS"
-TITLE="Software Download Links"
-HREF="downloadlinks.html"><LINK
-REL="NEXT"
-TITLE="Database Schema Chart"
-HREF="dbschema.html"></HEAD
-><BODY
-CLASS="appendix"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="downloadlinks.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="dbschema.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="appendix"
-><H1
-><A
-NAME="database">Appendix C. The Bugzilla Database</H1
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->C.1. <A
-HREF="dbschema.html"
->Database Schema Chart</A
-></DT
-><DT
->C.2. <A
-HREF="dbdoc.html"
->MySQL Bugzilla Database Introduction</A
-></DT
-><DT
->C.3. <A
-HREF="granttables.html"
->MySQL Permissions &#38; Grant Tables</A
-></DT
-></DL
-></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
->&#13;      This document really needs to be updated with more fleshed out information about primary keys, interrelationships, and maybe some nifty tables to document dependencies.  Any takers?
-    </P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="downloadlinks.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="dbschema.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Software Download Links</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
->&nbsp;</TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Database Schema Chart</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/dbdoc.html

@@ -1,576 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->MySQL Bugzilla Database Introduction</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="The Bugzilla Database"
-HREF="database.html"><LINK
-REL="PREVIOUS"
-TITLE="Database Schema Chart"
-HREF="dbschema.html"><LINK
-REL="NEXT"
-TITLE="MySQL Permissions & Grant Tables"
-HREF="granttables.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="dbschema.html"
-ACCESSKEY="P"
->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="granttables.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="dbdoc">C.2. MySQL Bugzilla Database Introduction</H1
-><P
->&#13;      This information comes straight from my life.  I was forced to learn how
-      Bugzilla organizes database because of nitpicky requests from users for tiny
-      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
->&#13;      So, here you are with your brand-new installation of Bugzilla.  You've got
-      MySQL set up, Apache working right, Perl DBI and DBD talking to the database
-      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
->&#13;      What's the next thing you do?  Outline a training strategy for your
-      development team, of course, and bring them up to speed on the new tool you've
-      labored over for hours.
-    </P
-><P
->&#13;      Your first training session starts off very well!  You have a captive
-      audience which seems enraptured by the efficiency embodied in this thing called
-      "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
->&#13;      But Certain Death speaks up -- a tiny voice, from the dark corners of the
-      conference room.  "I have a concern," the voice hisses from the darkness,
-      "about the use of the word 'verified'.
-    </P
-><P
->&#13;      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
->&#13;      Oh no!  Terror strikes your heart, as you find yourself mumbling "yes, yes, I
-      don't think that would be a problem," You review the changes with Certain
-      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
->&#13;      Thus begins your adventure into the heart of Bugzilla.  You've been forced
-      to learn about non-portable enum() fields, varchar columns, and tinyint
-      definitions. The Adventure Awaits You!
-    </P
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="AEN2272">C.2.1. Bugzilla Database Basics</H2
-><P
->&#13;	If you were like me, at this point you're totally clueless
-	about the internals of MySQL, and if it weren't for this
-	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
->&#13;	      To connect to your database:
-	    </P
-><P
->&#13;	      <TT
-CLASS="prompt"
->bash#</TT
-><B
-CLASS="command"
->mysql</B
-><TT
-CLASS="parameter"
-><I
->-u root</I
-></TT
->
-	    </P
-><P
->&#13;	      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&#62;</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="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
->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="AEN2301">C.2.1.1. Bugzilla Database Tables</H3
-><P
->  Imagine your MySQL database as a series of
-	  spreadsheets, and you won't be too far off.  If you use this
-	  command:</P
-><P
-><TT
-CLASS="prompt"
->mysql&#62;</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"
->&#13;+-------------------+
-| 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>
-<br>
-&nbsp;&nbsp;Here's&nbsp;an&nbsp;overview&nbsp;of&nbsp;what&nbsp;each&nbsp;table&nbsp;does.&nbsp;&nbsp;Most&nbsp;columns&nbsp;in&nbsp;each&nbsp;table&nbsp;have<br>
-descriptive&nbsp;names&nbsp;that&nbsp;make&nbsp;it&nbsp;fairly&nbsp;trivial&nbsp;to&nbsp;figure&nbsp;out&nbsp;their&nbsp;jobs.<br>
-<br>
-attachments:&nbsp;This&nbsp;table&nbsp;stores&nbsp;all&nbsp;attachments&nbsp;to&nbsp;bugs.&nbsp;&nbsp;It&nbsp;tends&nbsp;to&nbsp;be&nbsp;your<br>
-largest&nbsp;table,&nbsp;yet&nbsp;also&nbsp;generally&nbsp;has&nbsp;the&nbsp;fewest&nbsp;entries&nbsp;because&nbsp;file<br>
-attachments&nbsp;are&nbsp;so&nbsp;(relatively)&nbsp;large.<br>
-<br>
-bugs:&nbsp;&nbsp;This&nbsp;is&nbsp;the&nbsp;core&nbsp;of&nbsp;your&nbsp;system.&nbsp;&nbsp;The&nbsp;bugs&nbsp;table&nbsp;stores&nbsp;most&nbsp;of&nbsp;the<br>
-current&nbsp;information&nbsp;about&nbsp;a&nbsp;bug,&nbsp;with&nbsp;the&nbsp;exception&nbsp;of&nbsp;the&nbsp;info&nbsp;stored&nbsp;in&nbsp;the<br>
-other&nbsp;tables.<br>
-<br>
-bugs_activity:&nbsp;&nbsp;This&nbsp;stores&nbsp;information&nbsp;regarding&nbsp;what&nbsp;changes&nbsp;are&nbsp;made&nbsp;to&nbsp;bugs<br>
-when&nbsp;--&nbsp;a&nbsp;history&nbsp;file.<br>
-<br>
-cc:&nbsp;&nbsp;This&nbsp;tiny&nbsp;table&nbsp;simply&nbsp;stores&nbsp;all&nbsp;the&nbsp;CC&nbsp;information&nbsp;for&nbsp;any&nbsp;bug&nbsp;which&nbsp;has<br>
-any&nbsp;entries&nbsp;in&nbsp;the&nbsp;CC&nbsp;field&nbsp;of&nbsp;the&nbsp;bug.&nbsp;&nbsp;Note&nbsp;that,&nbsp;like&nbsp;most&nbsp;other&nbsp;tables&nbsp;in<br>
-Bugzilla,&nbsp;it&nbsp;does&nbsp;not&nbsp;refer&nbsp;to&nbsp;users&nbsp;by&nbsp;their&nbsp;user&nbsp;names,&nbsp;but&nbsp;by&nbsp;their&nbsp;unique<br>
-userid,&nbsp;stored&nbsp;as&nbsp;a&nbsp;primary&nbsp;key&nbsp;in&nbsp;the&nbsp;profiles&nbsp;table.<br>
-<br>
-components:&nbsp;This&nbsp;stores&nbsp;the&nbsp;programs&nbsp;and&nbsp;components&nbsp;(or&nbsp;products&nbsp;and<br>
-components,&nbsp;in&nbsp;newer&nbsp;Bugzilla&nbsp;parlance)&nbsp;for&nbsp;Bugzilla.&nbsp;&nbsp;Curiously,&nbsp;the&nbsp;"program"<br>
-(product)&nbsp;field&nbsp;is&nbsp;the&nbsp;full&nbsp;name&nbsp;of&nbsp;the&nbsp;product,&nbsp;rather&nbsp;than&nbsp;some&nbsp;other&nbsp;unique<br>
-identifier,&nbsp;like&nbsp;bug_id&nbsp;and&nbsp;user_id&nbsp;are&nbsp;elsewhere&nbsp;in&nbsp;the&nbsp;database.<br>
-<br>
-dependencies:&nbsp;Stores&nbsp;data&nbsp;about&nbsp;those&nbsp;cool&nbsp;dependency&nbsp;trees.<br>
-<br>
-fielddefs:&nbsp;&nbsp;A&nbsp;nifty&nbsp;table&nbsp;that&nbsp;defines&nbsp;other&nbsp;tables.&nbsp;&nbsp;For&nbsp;instance,&nbsp;when&nbsp;you<br>
-submit&nbsp;a&nbsp;form&nbsp;that&nbsp;changes&nbsp;the&nbsp;value&nbsp;of&nbsp;"AssignedTo"&nbsp;this&nbsp;table&nbsp;allows<br>
-translation&nbsp;to&nbsp;the&nbsp;actual&nbsp;field&nbsp;name&nbsp;"assigned_to"&nbsp;for&nbsp;entry&nbsp;into&nbsp;MySQL.<br>
-<br>
-groups:&nbsp;&nbsp;defines&nbsp;bitmasks&nbsp;for&nbsp;groups.&nbsp;&nbsp;A&nbsp;bitmask&nbsp;is&nbsp;a&nbsp;number&nbsp;that&nbsp;can&nbsp;uniquely<br>
-identify&nbsp;group&nbsp;memberships.&nbsp;&nbsp;For&nbsp;instance,&nbsp;say&nbsp;the&nbsp;group&nbsp;that&nbsp;is&nbsp;allowed&nbsp;to<br>
-tweak&nbsp;parameters&nbsp;is&nbsp;assigned&nbsp;a&nbsp;value&nbsp;of&nbsp;"1",&nbsp;the&nbsp;group&nbsp;that&nbsp;is&nbsp;allowed&nbsp;to&nbsp;edit<br>
-users&nbsp;is&nbsp;assigned&nbsp;a&nbsp;"2",&nbsp;and&nbsp;the&nbsp;group&nbsp;that&nbsp;is&nbsp;allowed&nbsp;to&nbsp;create&nbsp;new&nbsp;groups&nbsp;is<br>
-assigned&nbsp;the&nbsp;bitmask&nbsp;of&nbsp;"4".&nbsp;&nbsp;By&nbsp;uniquely&nbsp;combining&nbsp;the&nbsp;group&nbsp;bitmasks&nbsp;(much<br>
-like&nbsp;the&nbsp;chmod&nbsp;command&nbsp;in&nbsp;UNIX,)&nbsp;you&nbsp;can&nbsp;identify&nbsp;a&nbsp;user&nbsp;is&nbsp;allowed&nbsp;to&nbsp;tweak<br>
-parameters&nbsp;and&nbsp;create&nbsp;groups,&nbsp;but&nbsp;not&nbsp;edit&nbsp;users,&nbsp;by&nbsp;giving&nbsp;him&nbsp;a&nbsp;bitmask&nbsp;of<br>
-"5",&nbsp;or&nbsp;a&nbsp;user&nbsp;allowed&nbsp;to&nbsp;edit&nbsp;users&nbsp;and&nbsp;create&nbsp;groups,&nbsp;but&nbsp;not&nbsp;tweak<br>
-parameters,&nbsp;by&nbsp;giving&nbsp;him&nbsp;a&nbsp;bitmask&nbsp;of&nbsp;"6"&nbsp;Simple,&nbsp;huh?<br>
-&nbsp;&nbsp;If&nbsp;this&nbsp;makes&nbsp;no&nbsp;sense&nbsp;to&nbsp;you,&nbsp;try&nbsp;this&nbsp;at&nbsp;the&nbsp;mysql&nbsp;prompt:<br>
-mysql&#62;&nbsp;select&nbsp;*&nbsp;from&nbsp;groups;<br>
-&nbsp;&nbsp;You'll&nbsp;see&nbsp;the&nbsp;list,&nbsp;it&nbsp;makes&nbsp;much&nbsp;more&nbsp;sense&nbsp;that&nbsp;way.<br>
-<br>
-keyworddefs:&nbsp;&nbsp;Definitions&nbsp;of&nbsp;keywords&nbsp;to&nbsp;be&nbsp;used<br>
-<br>
-keywords:&nbsp;Unlike&nbsp;what&nbsp;you'd&nbsp;think,&nbsp;this&nbsp;table&nbsp;holds&nbsp;which&nbsp;keywords&nbsp;are<br>
-associated&nbsp;with&nbsp;which&nbsp;bug&nbsp;id's.<br>
-<br>
-logincookies:&nbsp;This&nbsp;stores&nbsp;every&nbsp;login&nbsp;cookie&nbsp;ever&nbsp;assigned&nbsp;to&nbsp;you&nbsp;for&nbsp;every<br>
-machine&nbsp;you've&nbsp;ever&nbsp;logged&nbsp;into&nbsp;Bugzilla&nbsp;from.&nbsp;&nbsp;Curiously,&nbsp;it&nbsp;never&nbsp;does&nbsp;any<br>
-housecleaning&nbsp;--&nbsp;I&nbsp;see&nbsp;cookies&nbsp;in&nbsp;this&nbsp;file&nbsp;I've&nbsp;not&nbsp;used&nbsp;for&nbsp;months.&nbsp;&nbsp;However,<br>
-since&nbsp;Bugzilla&nbsp;never&nbsp;expires&nbsp;your&nbsp;cookie&nbsp;(for&nbsp;convenience'&nbsp;sake),&nbsp;it&nbsp;makes<br>
-sense.<br>
-<br>
-longdescs:&nbsp;&nbsp;The&nbsp;meat&nbsp;of&nbsp;bugzilla&nbsp;--&nbsp;here&nbsp;is&nbsp;where&nbsp;all&nbsp;user&nbsp;comments&nbsp;are&nbsp;stored!<br>
-You've&nbsp;only&nbsp;got&nbsp;2^24&nbsp;bytes&nbsp;per&nbsp;comment&nbsp;(it's&nbsp;a&nbsp;mediumtext&nbsp;field),&nbsp;so&nbsp;speak<br>
-sparingly&nbsp;--&nbsp;that's&nbsp;only&nbsp;the&nbsp;amount&nbsp;of&nbsp;space&nbsp;the&nbsp;Old&nbsp;Testament&nbsp;from&nbsp;the&nbsp;Bible<br>
-would&nbsp;take&nbsp;(uncompressed,&nbsp;16&nbsp;megabytes).&nbsp;&nbsp;Each&nbsp;comment&nbsp;is&nbsp;keyed&nbsp;to&nbsp;the<br>
-bug_id&nbsp;to&nbsp;which&nbsp;it's&nbsp;attached,&nbsp;so&nbsp;the&nbsp;order&nbsp;is&nbsp;necessarily&nbsp;chronological,&nbsp;for<br>
-comments&nbsp;are&nbsp;played&nbsp;back&nbsp;in&nbsp;the&nbsp;order&nbsp;in&nbsp;which&nbsp;they&nbsp;are&nbsp;received.<br>
-<br>
-milestones:&nbsp;&nbsp;Interesting&nbsp;that&nbsp;milestones&nbsp;are&nbsp;associated&nbsp;with&nbsp;a&nbsp;specific&nbsp;product<br>
-in&nbsp;this&nbsp;table,&nbsp;but&nbsp;Bugzilla&nbsp;does&nbsp;not&nbsp;yet&nbsp;support&nbsp;differing&nbsp;milestones&nbsp;by<br>
-product&nbsp;through&nbsp;the&nbsp;standard&nbsp;configuration&nbsp;interfaces.<br>
-<br>
-namedqueries:&nbsp;&nbsp;This&nbsp;is&nbsp;where&nbsp;everybody&nbsp;stores&nbsp;their&nbsp;"custom&nbsp;queries".&nbsp;&nbsp;Very<br>
-cool&nbsp;feature;&nbsp;it&nbsp;beats&nbsp;the&nbsp;tar&nbsp;out&nbsp;of&nbsp;having&nbsp;to&nbsp;bookmark&nbsp;each&nbsp;cool&nbsp;query&nbsp;you<br>
-construct.<br>
-<br>
-products:&nbsp;&nbsp;What&nbsp;products&nbsp;you&nbsp;have,&nbsp;whether&nbsp;new&nbsp;bug&nbsp;entries&nbsp;are&nbsp;allowed&nbsp;for&nbsp;the<br>
-product,&nbsp;what&nbsp;milestone&nbsp;you're&nbsp;working&nbsp;toward&nbsp;on&nbsp;that&nbsp;product,&nbsp;votes,&nbsp;etc.&nbsp;&nbsp;It<br>
-will&nbsp;be&nbsp;nice&nbsp;when&nbsp;the&nbsp;components&nbsp;table&nbsp;supports&nbsp;these&nbsp;same&nbsp;features,&nbsp;so&nbsp;you<br>
-could&nbsp;close&nbsp;a&nbsp;particular&nbsp;component&nbsp;for&nbsp;bug&nbsp;entry&nbsp;without&nbsp;having&nbsp;to&nbsp;close&nbsp;an<br>
-entire&nbsp;product...<br>
-<br>
-profiles:&nbsp;&nbsp;Ahh,&nbsp;so&nbsp;you&nbsp;were&nbsp;wondering&nbsp;where&nbsp;your&nbsp;precious&nbsp;user&nbsp;information&nbsp;was<br>
-stored?&nbsp;&nbsp;Here&nbsp;it&nbsp;is!&nbsp;&nbsp;With&nbsp;the&nbsp;passwords&nbsp;in&nbsp;plain&nbsp;text&nbsp;for&nbsp;all&nbsp;to&nbsp;see!&nbsp;(but<br>
-sshh...&nbsp;don't&nbsp;tell&nbsp;your&nbsp;users!)<br>
-<br>
-profiles_activity:&nbsp;&nbsp;Need&nbsp;to&nbsp;know&nbsp;who&nbsp;did&nbsp;what&nbsp;when&nbsp;to&nbsp;who's&nbsp;profile?&nbsp;&nbsp;This'll<br>
-tell&nbsp;you,&nbsp;it's&nbsp;a&nbsp;pretty&nbsp;complete&nbsp;history.<br>
-<br>
-shadowlog:&nbsp;&nbsp;I&nbsp;could&nbsp;be&nbsp;mistaken&nbsp;here,&nbsp;but&nbsp;I&nbsp;believe&nbsp;this&nbsp;table&nbsp;tells&nbsp;you&nbsp;when<br>
-your&nbsp;shadow&nbsp;database&nbsp;is&nbsp;updated&nbsp;and&nbsp;what&nbsp;commands&nbsp;were&nbsp;used&nbsp;to&nbsp;update&nbsp;it.&nbsp;&nbsp;We<br>
-don't&nbsp;use&nbsp;a&nbsp;shadow&nbsp;database&nbsp;at&nbsp;our&nbsp;site&nbsp;yet,&nbsp;so&nbsp;it's&nbsp;pretty&nbsp;empty&nbsp;for&nbsp;us.<br>
-<br>
-versions:&nbsp;&nbsp;Version&nbsp;information&nbsp;for&nbsp;every&nbsp;product<br>
-<br>
-votes:&nbsp;&nbsp;Who&nbsp;voted&nbsp;for&nbsp;what&nbsp;when<br>
-<br>
-watch:&nbsp;&nbsp;Who&nbsp;(according&nbsp;to&nbsp;userid)&nbsp;is&nbsp;watching&nbsp;who's&nbsp;bugs&nbsp;(according&nbsp;to&nbsp;their<br>
-userid).<br>
-<br>
-<br>
-===<br>
-THE&nbsp;DETAILS<br>
-===<br>
-<br>
-&nbsp;&nbsp;Ahh,&nbsp;so&nbsp;you're&nbsp;wondering&nbsp;just&nbsp;what&nbsp;to&nbsp;do&nbsp;with&nbsp;the&nbsp;information&nbsp;above?&nbsp;&nbsp;At&nbsp;the<br>
-mysql&nbsp;prompt,&nbsp;you&nbsp;can&nbsp;view&nbsp;any&nbsp;information&nbsp;about&nbsp;the&nbsp;columns&nbsp;in&nbsp;a&nbsp;table&nbsp;with<br>
-this&nbsp;command&nbsp;(where&nbsp;"table"&nbsp;is&nbsp;the&nbsp;name&nbsp;of&nbsp;the&nbsp;table&nbsp;you&nbsp;wish&nbsp;to&nbsp;view):<br>
-<br>
-mysql&#62;&nbsp;show&nbsp;columns&nbsp;from&nbsp;table;<br>
-<br>
-&nbsp;&nbsp;You&nbsp;can&nbsp;also&nbsp;view&nbsp;all&nbsp;the&nbsp;data&nbsp;in&nbsp;a&nbsp;table&nbsp;with&nbsp;this&nbsp;command:<br>
-<br>
-mysql&#62;&nbsp;select&nbsp;*&nbsp;from&nbsp;table;<br>
-<br>
-&nbsp;&nbsp;--&nbsp;note:&nbsp;this&nbsp;is&nbsp;a&nbsp;very&nbsp;bad&nbsp;idea&nbsp;to&nbsp;do&nbsp;on,&nbsp;for&nbsp;instance,&nbsp;the&nbsp;"bugs"&nbsp;table&nbsp;if<br>
-you&nbsp;have&nbsp;50,000&nbsp;bugs.&nbsp;&nbsp;You'll&nbsp;be&nbsp;sitting&nbsp;there&nbsp;a&nbsp;while&nbsp;until&nbsp;you&nbsp;ctrl-c&nbsp;or<br>
-50,000&nbsp;bugs&nbsp;play&nbsp;across&nbsp;your&nbsp;screen.<br>
-<br>
-&nbsp;&nbsp;You&nbsp;can&nbsp;limit&nbsp;the&nbsp;display&nbsp;from&nbsp;above&nbsp;a&nbsp;little&nbsp;with&nbsp;the&nbsp;command,&nbsp;where<br>
-"column"&nbsp;is&nbsp;the&nbsp;name&nbsp;of&nbsp;the&nbsp;column&nbsp;for&nbsp;which&nbsp;you&nbsp;wish&nbsp;to&nbsp;restrict&nbsp;information:<br>
-<br>
-mysql&#62;&nbsp;select&nbsp;*&nbsp;from&nbsp;table&nbsp;where&nbsp;(column&nbsp;=&nbsp;"some&nbsp;info");<br>
-<br>
-&nbsp;&nbsp;--&nbsp;or&nbsp;the&nbsp;reverse&nbsp;of&nbsp;this<br>
-<br>
-mysql&#62;&nbsp;select&nbsp;*&nbsp;from&nbsp;table&nbsp;where&nbsp;(column&nbsp;!=&nbsp;"some&nbsp;info");<br>
-<br>
-&nbsp;&nbsp;Let's&nbsp;take&nbsp;our&nbsp;example&nbsp;from&nbsp;the&nbsp;introduction,&nbsp;and&nbsp;assume&nbsp;you&nbsp;need&nbsp;to&nbsp;change<br>
-the&nbsp;word&nbsp;"verified"&nbsp;to&nbsp;"approved"&nbsp;in&nbsp;the&nbsp;resolution&nbsp;field.&nbsp;&nbsp;We&nbsp;know&nbsp;from&nbsp;the<br>
-above&nbsp;information&nbsp;that&nbsp;the&nbsp;resolution&nbsp;is&nbsp;likely&nbsp;to&nbsp;be&nbsp;stored&nbsp;in&nbsp;the&nbsp;"bugs"<br>
-table.&nbsp;Note&nbsp;we'll&nbsp;need&nbsp;to&nbsp;change&nbsp;a&nbsp;little&nbsp;perl&nbsp;code&nbsp;as&nbsp;well&nbsp;as&nbsp;this&nbsp;database<br>
-change,&nbsp;but&nbsp;I&nbsp;won't&nbsp;plunge&nbsp;into&nbsp;that&nbsp;in&nbsp;this&nbsp;document.&nbsp;Let's&nbsp;verify&nbsp;the<br>
-information&nbsp;is&nbsp;stored&nbsp;in&nbsp;the&nbsp;"bugs"&nbsp;table:<br>
-<br>
-mysql&#62;&nbsp;show&nbsp;columns&nbsp;from&nbsp;bugs<br>
-<br>
-&nbsp;&nbsp;(exceedingly&nbsp;long&nbsp;output&nbsp;truncated&nbsp;here)<br>
-|&nbsp;bug_status|&nbsp;enum('UNCONFIRMED','NEW','ASSIGNED','REOPENED','RESOLVED','VERIFIED','CLOSED')||MUL&nbsp;|&nbsp;UNCONFIRMED||<br>
-<br>
-&nbsp;&nbsp;Sorry&nbsp;about&nbsp;that&nbsp;long&nbsp;line.&nbsp;&nbsp;We&nbsp;see&nbsp;from&nbsp;this&nbsp;that&nbsp;the&nbsp;"bug&nbsp;status"&nbsp;column&nbsp;is<br>
-an&nbsp;"enum&nbsp;field",&nbsp;which&nbsp;is&nbsp;a&nbsp;MySQL&nbsp;peculiarity&nbsp;where&nbsp;a&nbsp;string&nbsp;type&nbsp;field&nbsp;can<br>
-only&nbsp;have&nbsp;certain&nbsp;types&nbsp;of&nbsp;entries.&nbsp;&nbsp;While&nbsp;I&nbsp;think&nbsp;this&nbsp;is&nbsp;very&nbsp;cool,&nbsp;it's&nbsp;not<br>
-standard&nbsp;SQL.&nbsp;&nbsp;Anyway,&nbsp;we&nbsp;need&nbsp;to&nbsp;add&nbsp;the&nbsp;possible&nbsp;enum&nbsp;field&nbsp;entry<br>
-'APPROVED'&nbsp;by&nbsp;altering&nbsp;the&nbsp;"bugs"&nbsp;table.<br>
-<br>
-mysql&#62;&nbsp;ALTER&nbsp;table&nbsp;bugs&nbsp;CHANGE&nbsp;bug_status&nbsp;bug_status<br>
-&nbsp;&nbsp;&nbsp;&nbsp;-&#62;&nbsp;enum("UNCONFIRMED",&nbsp;"NEW",&nbsp;"ASSIGNED",&nbsp;"REOPENED",&nbsp;"RESOLVED",<br>
-&nbsp;&nbsp;&nbsp;&nbsp;-&#62;&nbsp;"VERIFIED",&nbsp;"APPROVED",&nbsp;"CLOSED")&nbsp;not&nbsp;null;<br>
-<br>
-&nbsp;&nbsp;&nbsp;&nbsp;(note&nbsp;we&nbsp;can&nbsp;take&nbsp;three&nbsp;lines&nbsp;or&nbsp;more&nbsp;--&nbsp;whatever&nbsp;you&nbsp;put&nbsp;in&nbsp;before&nbsp;the<br>
-semicolon&nbsp;is&nbsp;evaluated&nbsp;as&nbsp;a&nbsp;single&nbsp;expression)<br>
-<br>
-Now&nbsp;if&nbsp;you&nbsp;do&nbsp;this:<br>
-<br>
-mysql&#62;&nbsp;show&nbsp;columns&nbsp;from&nbsp;bugs;<br>
-<br>
-&nbsp;&nbsp;you'll&nbsp;see&nbsp;that&nbsp;the&nbsp;bug_status&nbsp;field&nbsp;has&nbsp;an&nbsp;extra&nbsp;"APPROVED"&nbsp;enum&nbsp;that's<br>
-available!&nbsp;&nbsp;Cool&nbsp;thing,&nbsp;too,&nbsp;is&nbsp;that&nbsp;this&nbsp;is&nbsp;reflected&nbsp;on&nbsp;your&nbsp;query&nbsp;page&nbsp;as<br>
-well&nbsp;--&nbsp;you&nbsp;can&nbsp;query&nbsp;by&nbsp;the&nbsp;new&nbsp;status.&nbsp;&nbsp;But&nbsp;how's&nbsp;it&nbsp;fit&nbsp;into&nbsp;the&nbsp;existing<br>
-scheme&nbsp;of&nbsp;things?<br>
-&nbsp;&nbsp;Looks&nbsp;like&nbsp;you&nbsp;need&nbsp;to&nbsp;go&nbsp;back&nbsp;and&nbsp;look&nbsp;for&nbsp;instances&nbsp;of&nbsp;the&nbsp;word&nbsp;"verified"<br>
-in&nbsp;the&nbsp;perl&nbsp;code&nbsp;for&nbsp;Bugzilla&nbsp;--&nbsp;wherever&nbsp;you&nbsp;find&nbsp;"verified",&nbsp;change&nbsp;it&nbsp;to<br>
-"approved"&nbsp;and&nbsp;you're&nbsp;in&nbsp;business&nbsp;(make&nbsp;sure&nbsp;that's&nbsp;a&nbsp;case-insensitive&nbsp;search).<br>
-Although&nbsp;you&nbsp;can&nbsp;query&nbsp;by&nbsp;the&nbsp;enum&nbsp;field,&nbsp;you&nbsp;can't&nbsp;give&nbsp;something&nbsp;a&nbsp;status<br>
-of&nbsp;"APPROVED"&nbsp;until&nbsp;you&nbsp;make&nbsp;the&nbsp;perl&nbsp;changes.&nbsp;&nbsp;&nbsp;Note&nbsp;that&nbsp;this&nbsp;change&nbsp;I<br>
-mentioned&nbsp;can&nbsp;also&nbsp;be&nbsp;done&nbsp;by&nbsp;editing&nbsp;checksetup.pl,&nbsp;which&nbsp;automates&nbsp;a&nbsp;lot&nbsp;of<br>
-this.&nbsp;&nbsp;But&nbsp;you&nbsp;need&nbsp;to&nbsp;know&nbsp;this&nbsp;stuff&nbsp;anyway,&nbsp;right?<br>
-<br>
-&nbsp;&nbsp;I&nbsp;hope&nbsp;this&nbsp;database&nbsp;tutorial&nbsp;has&nbsp;been&nbsp;useful&nbsp;for&nbsp;you.&nbsp;&nbsp;If&nbsp;you&nbsp;have&nbsp;comments<br>
-to&nbsp;add,&nbsp;questions,&nbsp;concerns,&nbsp;etc.&nbsp;please&nbsp;direct&nbsp;them&nbsp;to<br>
-mbarnson@excitehome.net.&nbsp;&nbsp;Please&nbsp;direct&nbsp;flames&nbsp;to&nbsp;/dev/null&nbsp;:)&nbsp;&nbsp;Have&nbsp;a&nbsp;nice<br>
-day!<br>
-<br>
-<br>
-<br>
-===<br>
-LINKS<br>
-===<br>
-<br>
-Great&nbsp;MySQL&nbsp;tutorial&nbsp;site:<br>
-http://www.devshed.com/Server_Side/MySQL/<br>
-<br>
-	</P
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="dbschema.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="granttables.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Database Schema Chart</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="database.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->MySQL Permissions &#38; Grant Tables</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/dbschema.html

@@ -1,156 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Database Schema Chart</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="The Bugzilla Database"
-HREF="database.html"><LINK
-REL="PREVIOUS"
-TITLE="The Bugzilla Database"
-HREF="database.html"><LINK
-REL="NEXT"
-TITLE="MySQL Bugzilla Database Introduction"
-HREF="dbdoc.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="database.html"
-ACCESSKEY="P"
->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="dbdoc.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="dbschema">C.1. Database Schema Chart</H1
-><P
->&#13;      <DIV
-CLASS="mediaobject"
-><P
-><IMG
-SRC="../images/dbschema.jpg"><DIV
-CLASS="caption"
-><P
->Bugzilla database relationships chart</P
-></DIV
-></P
-></DIV
->
-    </P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="database.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="dbdoc.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->The Bugzilla Database</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="database.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->MySQL Bugzilla Database Introduction</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/disclaimer.html

@@ -1,184 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Disclaimer</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="About This Guide"
-HREF="about.html"><LINK
-REL="PREVIOUS"
-TITLE="Copyright Information"
-HREF="copyright.html"><LINK
-REL="NEXT"
-TITLE="New Versions"
-HREF="newversions.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="copyright.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 1. About This Guide</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="newversions.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="disclaimer">1.3. Disclaimer</H1
-><P
->&#13;      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.
-    </P
-><P
->&#13;      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
->&#13;      Naming of particular products or brands should not be seen as
-      endorsements, with the exception of the term "GNU/Linux".  We
-      wholeheartedly endorse the use of GNU/Linux in every situation
-      where it is appropriate.  It is an extremely versatile, stable,
-      and robust operating system that offers an ideal operating
-      environment for Bugzilla.
-    </P
-><P
->&#13;      You are strongly recommended to make a backup of your system
-      before installing Bugzilla and at regular intervals thereafter.
-      If you implement any suggestion in this Guide, implement this one!
-    </P
-><P
->&#13;      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
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="copyright.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="newversions.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Copyright Information</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="about.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->New Versions</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/downloadlinks.html

@@ -1,237 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Software Download Links</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="PREVIOUS"
-TITLE="The Bugzilla FAQ"
-HREF="faq.html"><LINK
-REL="NEXT"
-TITLE="The Bugzilla Database"
-HREF="database.html"></HEAD
-><BODY
-CLASS="appendix"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="faq.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="database.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="appendix"
-><H1
-><A
-NAME="downloadlinks">Appendix B. Software Download Links</H1
-><P
->&#13;    All of these sites are current as of April, 2001.  Hopefully
-    they'll stay current for a while.
-  </P
-><P
->&#13;    Apache Web Server: <A
-HREF="http://www.apache.org/"
-TARGET="_top"
->http://www.apache.org</A
->
-    Optional web server for Bugzilla, but recommended because of broad user base and support.
-  </P
-><P
->&#13;    Bugzilla: <A
-HREF="http://www.mozilla.org/projects/bugzilla/"
-TARGET="_top"
->&#13;      http://www.mozilla.org/projects/bugzilla/</A
->
-  </P
-><P
->&#13;    MySQL: <A
-HREF="http://www.mysql.com/"
-TARGET="_top"
->http://www.mysql.com/</A
->
-  </P
-><P
->&#13;    Perl: <A
-HREF="http://www.perl.org"
-TARGET="_top"
->http://www.perl.org/</A
->
-  </P
-><P
->&#13;    CPAN: <A
-HREF="http://www.cpan.org/"
-TARGET="_top"
->http://www.cpan.org/</A
->
-  </P
-><P
->&#13;    DBI Perl module: 
-    <A
-HREF="http://www.cpan.org/modules/by-module/DBI/"
-TARGET="_top"
->&#13;      http://www.cpan.org/modules/by-module/DBI/</A
->
-  </P
-><P
->&#13;    Data::Dumper module: 
-    <A
-HREF="http://www.cpan.org/modules/by-module/Data/"
-TARGET="_top"
->&#13;      http://www.cpan.org/modules/by-module/Data/</A
->
-  </P
-><P
->&#13;    MySQL related Perl modules:
-    <A
-HREF="http://www.cpan.org/modules/by-module/Mysql/"
-TARGET="_top"
->&#13;      http://www.cpan.org/modules/by-module/Mysql/</A
->
-  </P
-><P
->&#13;    TimeDate Perl module collection:
-    <A
-HREF="http://www.cpan.org/modules/by-module/Date/"
-TARGET="_top"
->&#13;      http://www.cpan.org/modules/by-module/Date/</A
->
-  </P
-><P
->&#13;    GD Perl module:
-    <A
-HREF="http://www.cpan.org/modules/by-module/GD/"
-TARGET="_top"
->&#13;      http://www.cpan.org/modules/by-module/GD/</A
->
-    Alternately, you should be able to find the latest version of
-    GD at <A
-HREF="http://www.boutell.com/gd/"
-TARGET="_top"
->http://www.boutell.com/gd/</A
->
-  </P
-><P
->&#13;    Chart::Base module:
-    <A
-HREF="http://www.cpan.org/modules/by-module/Chart/"
-TARGET="_top"
->&#13;    http://www.cpan.org/modules/by-module/Chart/</A
->
-  </P
-><P
->&#13;    LinuxDoc Software: 
-    <A
-HREF="http://www.linuxdoc.org/"
-TARGET="_top"
->http://www.linuxdoc.org/</A
->
-    (for documentation maintenance)
-  </P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="faq.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="database.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->The Bugzilla FAQ</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
->&nbsp;</TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->The Bugzilla Database</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/errata.html

@@ -1,279 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->ERRATA</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><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
-SUMMARY="Header navigation 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"
-ACCESSKEY="P"
->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"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="errata">3.1. ERRATA</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
->&#13;	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
->&#13;	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
->&#13;	Release Notes for Bugzilla 2.16 are available at
-	<TT
-CLASS="filename"
->docs/rel_notes.txt</TT
-> in your Bugzilla
-	source distribution.
-      </TD
-></TR
-><TR
-><TD
->&#13;	  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
->&#13;	Bugzilla is not a package where you can just plop it in a directory,
-	twiddle a few things, and you're off.  Installing Bugzilla assumes you
-	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
->&#13;	Bugzilla has not undergone a complete security review. Security holes
-	may exist in the code.  Great care should be taken both in the installation
-	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
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="installation.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="stepbystep.html"
-ACCESSKEY="N"
->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"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Step-by-step Install</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/feedback.html

@@ -1,161 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Feedback</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="About This Guide"
-HREF="about.html"><LINK
-REL="PREVIOUS"
-TITLE="Contributors"
-HREF="contributors.html"><LINK
-REL="NEXT"
-TITLE="Translations"
-HREF="translations.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="contributors.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 1. About This Guide</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="translations.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="feedback">1.7. Feedback</H1
-><P
->&#13;      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"
->&#60;<A
-HREF="mailto:barnboy@trilobyte.net"
->barnboy@trilobyte.net</A
->&#62;</TT
->.  Please send flames to
-      <TT
-CLASS="email"
->&#60;<A
-HREF="mailto:devnull@localhost"
->devnull@localhost</A
->&#62;</TT
->
-    </P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="contributors.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="translations.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Contributors</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="about.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Translations</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/geninstall.html

@@ -1,489 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Installation General Notes</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><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
-SUMMARY="Header navigation 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"
-ACCESSKEY="P"
->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"
-ACCESSKEY="N"
->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</H1
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="AEN874">3.5.1. Modifying Your Running System</H2
-><P
->&#13;	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
->&#13;	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
->&#13;	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="AEN881">3.5.2. Upgrading From Previous Versions</H2
-><P
->&#13;  A plain Bugzilla is fairly easy to upgrade from one version to a newer one.
-  However, things get a bit more complicated if you've made changes to 
-  Bugzilla's code. In this case, you may have to re-make or reapply those
-  changes.
-  It is recommended that you take a backup of your database and your entire
-  Bugzilla installation before attempting an upgrade. You can upgrade a 'clean'
-  installation by untarring a new tarball over the old installation. If you
-  are upgrading from 2.12 or later, you can type <TT
-CLASS="filename"
->cvs -z3 
-  update</TT
->, and resolve conflicts if there are any.   
-      </P
-><P
->&#13;	Because the developers of Bugzilla are constantly adding new tables, columns
-  and fields, you'll probably get SQL errors if you just update the code and
-  attempt to use Bugzilla. Always run the checksetup.pl script whenever
-	you upgrade your installation. 
-      </P
-><P
->&#13;	If you are running Bugzilla version 2.8 or lower, and wish to upgrade to
-	the latest version, please consult the file, "UPGRADING-pre-2.8" in the
-	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</H2
-><P
->&#13;	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. These .htaccess files
-  will not work with Apache 1.2.x - but this has security holes, so you
-  shouldn't be using it anyway.
-	
-	<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
->&#13;	    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
->&#13;	The default .htaccess file may not provide adequate access
-	restrictions, depending on your web server configuration.
-	Be sure to check the &#60;Directory&#62; entries for your
-	Bugzilla directory so that the <TT
-CLASS="filename"
->.htaccess</TT
->
-	file is allowed to override web server defaults.  For instance,
-	let's assume your installation of Bugzilla is installed to 
-	<TT
-CLASS="filename"
->/usr/local/bugzilla</TT
->.  You should have
-	this &#60;Directory&#62; entry in your <TT
-CLASS="filename"
->httpd.conf</TT
->
-	file:
-      </P
-><P
->&#13;	<TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->&#13;
-&#60;Directory /usr/local/bugzilla/&#62;
-  Options +FollowSymLinks +Indexes +Includes +ExecCGI
-  AllowOverride All
-&#60;/Directory&#62;
-
-	</PRE
-></FONT
-></TD
-></TR
-></TABLE
->
-      </P
-><P
->&#13;	The important part above is <SPAN
-CLASS="QUOTE"
->"AllowOverride All"</SPAN
->.
-	Without that, the <TT
-CLASS="filename"
->.htaccess</TT
-> file created by 
-	<TT
-CLASS="filename"
->checksetup.pl</TT
-> will not have sufficient
-	permissions to protect your Bugzilla installation.
-      </P
-><P
->&#13;	If you are using Internet Information Server or other web
-	server which does not observe <TT
-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</H2
-><P
->&#13;	It is possible for a user, by mistake or on purpose, to access
-	the database many times in a row which can result in very slow
-	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</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"
->&#13;bash# cd $BUGZILLA_HOME; for i in `ls *.cgi`; \
-	  do cat $i | sed 's/Content-type\: text\/html/Content-Type: text\/html\; charset=ISO-8859-1/' &#62;$i.tmp; \
-	  mv $i.tmp $i; done
-	</PRE
-></FONT
-></TD
-></TR
-></TABLE
-></P
-><P
->&#13;	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</H2
-><P
->&#13;	This document was originally adapted from the Bonsai
-	installation instructions by Terry Weissman
-	&#60;terry@mozilla.org&#62;.
-      </P
-><P
->&#13;	The February 25, 1999 re-write of this page was done by Ry4an
-	Brase &#60;ry4an@ry4an.org&#62;, with some edits by Terry
-	Weissman, Bryce Nesbitt, Martin Pool, &#38; 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
->&#13;	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
->&#13;	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
->&#13;	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
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="bsdinstall.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="win32.html"
-ACCESSKEY="N"
->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"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Win32 Installation Notes</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/gfdl-0.html

@@ -1,165 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->PREAMBLE</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="GNU Free Documentation License"
-HREF="gfdl.html"><LINK
-REL="PREVIOUS"
-TITLE="GNU Free Documentation License"
-HREF="gfdl.html"><LINK
-REL="NEXT"
-TITLE="APPLICABILITY AND DEFINITIONS"
-HREF="gfdl-1.html"></HEAD
-><BODY
-CLASS="sect1"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="gfdl.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix E. GNU Free Documentation License</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="gfdl-1.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="gfdl-0">0. PREAMBLE</H1
-><P
->The purpose of this License is to make a manual, textbook,
-    or other written document "free" in the sense of freedom: to
-    assure everyone the effective freedom to copy and redistribute it,
-    with or without modifying it, either commercially or
-    noncommercially.  Secondarily, this License preserves for the
-    author and publisher a way to get credit for their work, while not
-    being considered responsible for modifications made by
-    others.</P
-><P
->This License is a kind of "copyleft", which means that
-    derivative works of the document must themselves be free in the
-    same sense.  It complements the GNU General Public License, which
-    is a copyleft license designed for free software.</P
-><P
->We have designed this License in order to use it for manuals
-    for free software, because free software needs free documentation:
-    a free program should come with manuals providing the same
-    freedoms that the software does.  But this License is not limited
-    to software manuals; it can be used for any textual work,
-    regardless of subject matter or whether it is published as a
-    printed book.  We recommend this License principally for works
-    whose purpose is instruction or reference.</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="gfdl.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="gfdl-1.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->GNU Free Documentation License</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="gfdl.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->APPLICABILITY AND DEFINITIONS</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/gfdl-1.html

@@ -1,206 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->APPLICABILITY AND DEFINITIONS</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="GNU Free Documentation License"
-HREF="gfdl.html"><LINK
-REL="PREVIOUS"
-TITLE="PREAMBLE"
-HREF="gfdl-0.html"><LINK
-REL="NEXT"
-TITLE="VERBATIM COPYING"
-HREF="gfdl-2.html"></HEAD
-><BODY
-CLASS="sect1"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="gfdl-0.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix E. GNU Free Documentation License</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="gfdl-2.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="gfdl-1">1. APPLICABILITY AND DEFINITIONS</H1
-><P
->This License applies to any manual or other work that
-    contains a notice placed by the copyright holder saying it can be
-    distributed under the terms of this License.  The "Document",
-    below, refers to any such manual or work.  Any member of the
-    public is a licensee, and is addressed as "you".</P
-><P
->A "Modified Version" of the Document means any work
-    containing the Document or a portion of it, either copied
-    verbatim, or with modifications and/or translated into another
-    language.</P
-><P
->A "Secondary Section" is a named appendix or a front-matter
-    section of the Document that deals exclusively with the
-    relationship of the publishers or authors of the Document to the
-    Document's overall subject (or to related matters) and contains
-    nothing that could fall directly within that overall subject.
-    (For example, if the Document is in part a textbook of
-    mathematics, a Secondary Section may not explain any mathematics.)
-    The relationship could be a matter of historical connection with
-    the subject or with related matters, or of legal, commercial,
-    philosophical, ethical or political position regarding
-    them.</P
-><P
->The "Invariant Sections" are certain Secondary Sections
-    whose titles are designated, as being those of Invariant Sections,
-    in the notice that says that the Document is released under this
-    License.</P
-><P
->The "Cover Texts" are certain short passages of text that
-    are listed, as Front-Cover Texts or Back-Cover Texts, in the
-    notice that says that the Document is released under this
-    License.</P
-><P
->A "Transparent" copy of the Document means a
-    machine-readable copy, represented in a format whose specification
-    is available to the general public, whose contents can be viewed
-    and edited directly and straightforwardly with generic text
-    editors or (for images composed of pixels) generic paint programs
-    or (for drawings) some widely available drawing editor, and that
-    is suitable for input to text formatters or for automatic
-    translation to a variety of formats suitable for input to text
-    formatters.  A copy made in an otherwise Transparent file format
-    whose markup has been designed to thwart or discourage subsequent
-    modification by readers is not Transparent.  A copy that is not
-    "Transparent" is called "Opaque".</P
-><P
->Examples of suitable formats for Transparent copies include
-    plain ASCII without markup, Texinfo input format, LaTeX input
-    format, SGML or XML using a publicly available DTD, and
-    standard-conforming simple HTML designed for human modification.
-    Opaque formats include PostScript, PDF, proprietary formats that
-    can be read and edited only by proprietary word processors, SGML
-    or XML for which the DTD and/or processing tools are not generally
-    available, and the machine-generated HTML produced by some word
-    processors for output purposes only.</P
-><P
->The "Title Page" means, for a printed book, the title page
-    itself, plus such following pages as are needed to hold, legibly,
-    the material this License requires to appear in the title page.
-    For works in formats which do not have any title page as such,
-    "Title Page" means the text near the most prominent appearance of
-    the work's title, preceding the beginning of the body of the
-    text.</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="gfdl-0.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="gfdl-2.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->PREAMBLE</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="gfdl.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->VERBATIM COPYING</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/gfdl-10.html

@@ -1,162 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->FUTURE REVISIONS OF THIS LICENSE</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="GNU Free Documentation License"
-HREF="gfdl.html"><LINK
-REL="PREVIOUS"
-TITLE="TERMINATION"
-HREF="gfdl-9.html"><LINK
-REL="NEXT"
-TITLE="How to use this License for your documents"
-HREF="gfdl-howto.html"></HEAD
-><BODY
-CLASS="sect1"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="gfdl-9.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix E. GNU Free Documentation License</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="gfdl-howto.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="gfdl-10">10. FUTURE REVISIONS OF THIS LICENSE</H1
-><P
->The Free Software Foundation may publish new, revised
-    versions of the GNU Free Documentation License from time to time.
-    Such new versions will be similar in spirit to the present
-    version, but may differ in detail to address new problems or
-    concerns.  See <A
-HREF="http://www.gnu.org/copyleft/"
-TARGET="_top"
->http://www.gnu.org/copyleft/</A
->.</P
-><P
->Each version of the License is given a distinguishing
-    version number.  If the Document specifies that a particular
-    numbered version of this License "or any later version" applies to
-    it, you have the option of following the terms and conditions
-    either of that specified version or of any later version that has
-    been published (not as a draft) by the Free Software Foundation.
-    If the Document does not specify a version number of this License,
-    you may choose any version ever published (not as a draft) by the
-    Free Software Foundation.</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="gfdl-9.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="gfdl-howto.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->TERMINATION</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="gfdl.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->How to use this License for your documents</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/gfdl-2.html

@@ -1,156 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->VERBATIM COPYING</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="GNU Free Documentation License"
-HREF="gfdl.html"><LINK
-REL="PREVIOUS"
-TITLE="APPLICABILITY AND DEFINITIONS"
-HREF="gfdl-1.html"><LINK
-REL="NEXT"
-TITLE="COPYING IN QUANTITY"
-HREF="gfdl-3.html"></HEAD
-><BODY
-CLASS="sect1"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="gfdl-1.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix E. GNU Free Documentation License</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="gfdl-3.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="gfdl-2">2. VERBATIM COPYING</H1
-><P
->You may copy and distribute the Document in any medium,
-    either commercially or noncommercially, provided that this
-    License, the copyright notices, and the license notice saying this
-    License applies to the Document are reproduced in all copies, and
-    that you add no other conditions whatsoever to those of this
-    License.  You may not use technical measures to obstruct or
-    control the reading or further copying of the copies you make or
-    distribute.  However, you may accept compensation in exchange for
-    copies.  If you distribute a large enough number of copies you
-    must also follow the conditions in section 3.</P
-><P
->You may also lend copies, under the same conditions stated
-    above, and you may publicly display copies.</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="gfdl-1.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="gfdl-3.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->APPLICABILITY AND DEFINITIONS</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="gfdl.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->COPYING IN QUANTITY</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/gfdl-3.html

@@ -1,180 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->COPYING IN QUANTITY</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="GNU Free Documentation License"
-HREF="gfdl.html"><LINK
-REL="PREVIOUS"
-TITLE="VERBATIM COPYING"
-HREF="gfdl-2.html"><LINK
-REL="NEXT"
-TITLE="MODIFICATIONS"
-HREF="gfdl-4.html"></HEAD
-><BODY
-CLASS="sect1"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="gfdl-2.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix E. GNU Free Documentation License</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="gfdl-4.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="gfdl-3">3. COPYING IN QUANTITY</H1
-><P
->If you publish printed copies of the Document numbering more
-    than 100, and the Document's license notice requires Cover Texts,
-    you must enclose the copies in covers that carry, clearly and
-    legibly, all these Cover Texts: Front-Cover Texts on the front
-    cover, and Back-Cover Texts on the back cover.  Both covers must
-    also clearly and legibly identify you as the publisher of these
-    copies.  The front cover must present the full title with all
-    words of the title equally prominent and visible.  You may add
-    other material on the covers in addition.  Copying with changes
-    limited to the covers, as long as they preserve the title of the
-    Document and satisfy these conditions, can be treated as verbatim
-    copying in other respects.</P
-><P
->If the required texts for either cover are too voluminous to
-    fit legibly, you should put the first ones listed (as many as fit
-    reasonably) on the actual cover, and continue the rest onto
-    adjacent pages.</P
-><P
->If you publish or distribute Opaque copies of the Document
-    numbering more than 100, you must either include a
-    machine-readable Transparent copy along with each Opaque copy, or
-    state in or with each Opaque copy a publicly-accessible
-    computer-network location containing a complete Transparent copy
-    of the Document, free of added material, which the general
-    network-using public has access to download anonymously at no
-    charge using public-standard network protocols.  If you use the
-    latter option, you must take reasonably prudent steps, when you
-    begin distribution of Opaque copies in quantity, to ensure that
-    this Transparent copy will remain thus accessible at the stated
-    location until at least one year after the last time you
-    distribute an Opaque copy (directly or through your agents or
-    retailers) of that edition to the public.</P
-><P
->It is requested, but not required, that you contact the
-    authors of the Document well before redistributing any large
-    number of copies, to give them a chance to provide you with an
-    updated version of the Document.</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="gfdl-2.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="gfdl-4.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->VERBATIM COPYING</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="gfdl.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->MODIFICATIONS</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/gfdl-4.html

@@ -1,286 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->MODIFICATIONS</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="GNU Free Documentation License"
-HREF="gfdl.html"><LINK
-REL="PREVIOUS"
-TITLE="COPYING IN QUANTITY"
-HREF="gfdl-3.html"><LINK
-REL="NEXT"
-TITLE="COMBINING DOCUMENTS"
-HREF="gfdl-5.html"></HEAD
-><BODY
-CLASS="sect1"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="gfdl-3.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix E. GNU Free Documentation License</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="gfdl-5.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="gfdl-4">4. MODIFICATIONS</H1
-><P
->You may copy and distribute a Modified Version of the
-    Document under the conditions of sections 2 and 3 above, provided
-    that you release the Modified Version under precisely this
-    License, with the Modified Version filling the role of the
-    Document, thus licensing distribution and modification of the
-    Modified Version to whoever possesses a copy of it.  In addition,
-    you must do these things in the Modified Version:</P
-><P
-></P
-><OL
-TYPE="A"
-><LI
-><P
->Use in the Title Page
-      (and on the covers, if any) a title distinct from that of the
-      Document, and from those of previous versions (which should, if
-      there were any, be listed in the History section of the
-      Document).  You may use the same title as a previous version if
-      the original publisher of that version gives permission.</P
-></LI
-><LI
-><P
->List on the Title Page,
-      as authors, one or more persons or entities responsible for
-      authorship of the modifications in the Modified Version,
-      together with at least five of the principal authors of the
-      Document (all of its principal authors, if it has less than
-      five).</P
-></LI
-><LI
-><P
->State on the Title page
-      the name of the publisher of the Modified Version, as the
-      publisher.</P
-></LI
-><LI
-><P
->Preserve all the
-      copyright notices of the Document.</P
-></LI
-><LI
-><P
->Add an appropriate
-      copyright notice for your modifications adjacent to the other
-      copyright notices.</P
-></LI
-><LI
-><P
->Include, immediately
-      after the copyright notices, a license notice giving the public
-      permission to use the Modified Version under the terms of this
-      License, in the form shown in the Addendum below.</P
-></LI
-><LI
-><P
->Preserve in that license
-      notice the full lists of Invariant Sections and required Cover
-      Texts given in the Document's license notice.</P
-></LI
-><LI
-><P
->Include an unaltered
-      copy of this License.</P
-></LI
-><LI
-><P
->Preserve the section
-      entitled "History", and its title, and add to it an item stating
-      at least the title, year, new authors, and publisher of the
-      Modified Version as given on the Title Page.  If there is no
-      section entitled "History" in the Document, create one stating
-      the title, year, authors, and publisher of the Document as given
-      on its Title Page, then add an item describing the Modified
-      Version as stated in the previous sentence.</P
-></LI
-><LI
-><P
->Preserve the network
-      location, if any, given in the Document for public access to a
-      Transparent copy of the Document, and likewise the network
-      locations given in the Document for previous versions it was
-      based on.  These may be placed in the "History" section.  You
-      may omit a network location for a work that was published at
-      least four years before the Document itself, or if the original
-      publisher of the version it refers to gives permission.</P
-></LI
-><LI
-><P
->In any section entitled
-      "Acknowledgements" or "Dedications", preserve the section's
-      title, and preserve in the section all the substance and tone of
-      each of the contributor acknowledgements and/or dedications
-      given therein.</P
-></LI
-><LI
-><P
->Preserve all the
-      Invariant Sections of the Document, unaltered in their text and
-      in their titles.  Section numbers or the equivalent are not
-      considered part of the section titles.</P
-></LI
-><LI
-><P
->Delete any section
-      entitled "Endorsements".  Such a section may not be included in
-      the Modified Version.</P
-></LI
-><LI
-><P
->Do not retitle any
-      existing section as "Endorsements" or to conflict in title with
-      any Invariant Section.</P
-></LI
-></OL
-><P
->If the Modified Version includes new front-matter sections
-    or appendices that qualify as Secondary Sections and contain no
-    material copied from the Document, you may at your option
-    designate some or all of these sections as invariant.  To do this,
-    add their titles to the list of Invariant Sections in the Modified
-    Version's license notice.  These titles must be distinct from any
-    other section titles.</P
-><P
->You may add a section entitled "Endorsements", provided it
-    contains nothing but endorsements of your Modified Version by
-    various parties--for example, statements of peer review or that
-    the text has been approved by an organization as the authoritative
-    definition of a standard.</P
-><P
->You may add a passage of up to five words as a Front-Cover
-    Text, and a passage of up to 25 words as a Back-Cover Text, to the
-    end of the list of Cover Texts in the Modified Version.  Only one
-    passage of Front-Cover Text and one of Back-Cover Text may be
-    added by (or through arrangements made by) any one entity.  If the
-    Document already includes a cover text for the same cover,
-    previously added by you or by arrangement made by the same entity
-    you are acting on behalf of, you may not add another; but you may
-    replace the old one, on explicit permission from the previous
-    publisher that added the old one.</P
-><P
->The author(s) and publisher(s) of the Document do not by
-    this License give permission to use their names for publicity for
-    or to assert or imply endorsement of any Modified Version.</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="gfdl-3.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="gfdl-5.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->COPYING IN QUANTITY</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="gfdl.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->COMBINING DOCUMENTS</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/gfdl-5.html

@@ -1,165 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->COMBINING DOCUMENTS</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="GNU Free Documentation License"
-HREF="gfdl.html"><LINK
-REL="PREVIOUS"
-TITLE="MODIFICATIONS"
-HREF="gfdl-4.html"><LINK
-REL="NEXT"
-TITLE="COLLECTIONS OF DOCUMENTS"
-HREF="gfdl-6.html"></HEAD
-><BODY
-CLASS="sect1"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="gfdl-4.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix E. GNU Free Documentation License</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="gfdl-6.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="gfdl-5">5. COMBINING DOCUMENTS</H1
-><P
->You may combine the Document with other documents released
-    under this License, under the terms defined in section 4 above for
-    modified versions, provided that you include in the combination
-    all of the Invariant Sections of all of the original documents,
-    unmodified, and list them all as Invariant Sections of your
-    combined work in its license notice.</P
-><P
->The combined work need only contain one copy of this
-    License, and multiple identical Invariant Sections may be replaced
-    with a single copy.  If there are multiple Invariant Sections with
-    the same name but different contents, make the title of each such
-    section unique by adding at the end of it, in parentheses, the
-    name of the original author or publisher of that section if known,
-    or else a unique number.  Make the same adjustment to the section
-    titles in the list of Invariant Sections in the license notice of
-    the combined work.</P
-><P
->In the combination, you must combine any sections entitled
-    "History" in the various original documents, forming one section
-    entitled "History"; likewise combine any sections entitled
-    "Acknowledgements", and any sections entitled "Dedications".  You
-    must delete all sections entitled "Endorsements."</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="gfdl-4.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="gfdl-6.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->MODIFICATIONS</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="gfdl.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->COLLECTIONS OF DOCUMENTS</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/gfdl-6.html

@@ -1,155 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->COLLECTIONS OF DOCUMENTS</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="GNU Free Documentation License"
-HREF="gfdl.html"><LINK
-REL="PREVIOUS"
-TITLE="COMBINING DOCUMENTS"
-HREF="gfdl-5.html"><LINK
-REL="NEXT"
-TITLE="AGGREGATION WITH INDEPENDENT WORKS"
-HREF="gfdl-7.html"></HEAD
-><BODY
-CLASS="sect1"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="gfdl-5.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix E. GNU Free Documentation License</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="gfdl-7.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="gfdl-6">6. COLLECTIONS OF DOCUMENTS</H1
-><P
->You may make a collection consisting of the Document and
-    other documents released under this License, and replace the
-    individual copies of this License in the various documents with a
-    single copy that is included in the collection, provided that you
-    follow the rules of this License for verbatim copying of each of
-    the documents in all other respects.</P
-><P
->You may extract a single document from such a collection,
-    and distribute it individually under this License, provided you
-    insert a copy of this License into the extracted document, and
-    follow this License in all other respects regarding verbatim
-    copying of that document.</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="gfdl-5.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="gfdl-7.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->COMBINING DOCUMENTS</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="gfdl.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->AGGREGATION WITH INDEPENDENT WORKS</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/gfdl-7.html

@@ -1,159 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->AGGREGATION WITH INDEPENDENT WORKS</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="GNU Free Documentation License"
-HREF="gfdl.html"><LINK
-REL="PREVIOUS"
-TITLE="COLLECTIONS OF DOCUMENTS"
-HREF="gfdl-6.html"><LINK
-REL="NEXT"
-TITLE="TRANSLATION"
-HREF="gfdl-8.html"></HEAD
-><BODY
-CLASS="sect1"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="gfdl-6.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix E. GNU Free Documentation License</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="gfdl-8.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="gfdl-7">7. AGGREGATION WITH INDEPENDENT WORKS</H1
-><P
->A compilation of the Document or its derivatives with other
-    separate and independent documents or works, in or on a volume of
-    a storage or distribution medium, does not as a whole count as a
-    Modified Version of the Document, provided no compilation
-    copyright is claimed for the compilation.  Such a compilation is
-    called an "aggregate", and this License does not apply to the
-    other self-contained works thus compiled with the Document, on
-    account of their being thus compiled, if they are not themselves
-    derivative works of the Document.</P
-><P
->If the Cover Text requirement of section 3 is applicable to
-    these copies of the Document, then if the Document is less than
-    one quarter of the entire aggregate, the Document's Cover Texts
-    may be placed on covers that surround only the Document within the
-    aggregate.  Otherwise they must appear on covers around the whole
-    aggregate.</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="gfdl-6.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="gfdl-8.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->COLLECTIONS OF DOCUMENTS</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="gfdl.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->TRANSLATION</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/gfdl-8.html

@@ -1,154 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->TRANSLATION</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="GNU Free Documentation License"
-HREF="gfdl.html"><LINK
-REL="PREVIOUS"
-TITLE="AGGREGATION WITH INDEPENDENT WORKS"
-HREF="gfdl-7.html"><LINK
-REL="NEXT"
-TITLE="TERMINATION"
-HREF="gfdl-9.html"></HEAD
-><BODY
-CLASS="sect1"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="gfdl-7.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix E. GNU Free Documentation License</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="gfdl-9.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="gfdl-8">8. TRANSLATION</H1
-><P
->Translation is considered a kind of modification, so you may
-    distribute translations of the Document under the terms of section
-    4.  Replacing Invariant Sections with translations requires
-    special permission from their copyright holders, but you may
-    include translations of some or all Invariant Sections in addition
-    to the original versions of these Invariant Sections.  You may
-    include a translation of this License provided that you also
-    include the original English version of this License.  In case of
-    a disagreement between the translation and the original English
-    version of this License, the original English version will
-    prevail.</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="gfdl-7.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="gfdl-9.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->AGGREGATION WITH INDEPENDENT WORKS</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="gfdl.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->TERMINATION</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/gfdl-9.html

@@ -1,151 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->TERMINATION</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="GNU Free Documentation License"
-HREF="gfdl.html"><LINK
-REL="PREVIOUS"
-TITLE="TRANSLATION"
-HREF="gfdl-8.html"><LINK
-REL="NEXT"
-TITLE="FUTURE REVISIONS OF THIS LICENSE"
-HREF="gfdl-10.html"></HEAD
-><BODY
-CLASS="sect1"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="gfdl-8.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix E. GNU Free Documentation License</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="gfdl-10.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="gfdl-9">9. TERMINATION</H1
-><P
->You may not copy, modify, sublicense, or distribute the
-    Document except as expressly provided for under this License.  Any
-    other attempt to copy, modify, sublicense or distribute the
-    Document is void, and will automatically terminate your rights
-    under this License.  However, parties who have received copies, or
-    rights, from you under this License will not have their licenses
-    terminated so long as such parties remain in full
-    compliance.</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="gfdl-8.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="gfdl-10.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->TRANSLATION</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="gfdl.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->FUTURE REVISIONS OF THIS LICENSE</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/gfdl-howto.html

@@ -1,171 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->How to use this License for your documents</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="GNU Free Documentation License"
-HREF="gfdl.html"><LINK
-REL="PREVIOUS"
-TITLE="FUTURE REVISIONS OF THIS LICENSE"
-HREF="gfdl-10.html"><LINK
-REL="NEXT"
-TITLE="Glossary"
-HREF="glossary.html"></HEAD
-><BODY
-CLASS="sect1"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="gfdl-10.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix E. GNU Free Documentation License</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="glossary.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="gfdl-howto">How to use this License for your documents</H1
-><P
->To use this License in a document you have written, include
-    a copy of the License in the document and put the following
-    copyright and license notices just after the title page:</P
-><A
-NAME="AEN2605"><BLOCKQUOTE
-CLASS="BLOCKQUOTE"
-><P
->&#13;      Copyright (c)  YEAR  YOUR NAME.
-      Permission is granted to copy, distribute and/or modify this document
-      under the terms of the GNU Free Documentation License, Version 1.1
-      or any later version published by the Free Software Foundation;
-      with the Invariant Sections being LIST THEIR TITLES, with the
-      Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
-      A copy of the license is included in the section entitled "GNU
-      Free Documentation License".
-</P
-></BLOCKQUOTE
-><P
->If you have no Invariant Sections, write "with no Invariant
-    Sections" instead of saying which ones are invariant.  If you have
-    no Front-Cover Texts, write "no Front-Cover Texts" instead of
-    "Front-Cover Texts being LIST"; likewise for Back-Cover
-    Texts.</P
-><P
->If your document contains nontrivial examples of program
-    code, we recommend releasing these examples in parallel under your
-    choice of free software license, such as the GNU General Public
-    License, to permit their use in free software.</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="gfdl-10.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="glossary.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->FUTURE REVISIONS OF THIS LICENSE</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="gfdl.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Glossary</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/gfdl.html

@@ -1,214 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->GNU Free Documentation License</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="PREVIOUS"
-TITLE="Hacking Bugzilla"
-HREF="bzhacking.html"><LINK
-REL="NEXT"
-TITLE="PREAMBLE"
-HREF="gfdl-0.html"></HEAD
-><BODY
-CLASS="appendix"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="bzhacking.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="gfdl-0.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="appendix"
-><H1
-><A
-NAME="gfdl">Appendix E. GNU Free Documentation License</H1
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->0. <A
-HREF="gfdl-0.html"
->PREAMBLE</A
-></DT
-><DT
->1. <A
-HREF="gfdl-1.html"
->APPLICABILITY AND DEFINITIONS</A
-></DT
-><DT
->2. <A
-HREF="gfdl-2.html"
->VERBATIM COPYING</A
-></DT
-><DT
->3. <A
-HREF="gfdl-3.html"
->COPYING IN QUANTITY</A
-></DT
-><DT
->4. <A
-HREF="gfdl-4.html"
->MODIFICATIONS</A
-></DT
-><DT
->5. <A
-HREF="gfdl-5.html"
->COMBINING DOCUMENTS</A
-></DT
-><DT
->6. <A
-HREF="gfdl-6.html"
->COLLECTIONS OF DOCUMENTS</A
-></DT
-><DT
->7. <A
-HREF="gfdl-7.html"
->AGGREGATION WITH INDEPENDENT WORKS</A
-></DT
-><DT
->8. <A
-HREF="gfdl-8.html"
->TRANSLATION</A
-></DT
-><DT
->9. <A
-HREF="gfdl-9.html"
->TERMINATION</A
-></DT
-><DT
->10. <A
-HREF="gfdl-10.html"
->FUTURE REVISIONS OF THIS LICENSE</A
-></DT
-><DT
-><A
-HREF="gfdl-howto.html"
->How to use this License for your documents</A
-></DT
-></DL
-></DIV
-><P
->Version 1.1, March 2000</P
-><A
-NAME="AEN2515"><BLOCKQUOTE
-CLASS="BLOCKQUOTE"
-><P
->Copyright (C) 2000  Free Software Foundation, Inc.
-59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
-Everyone is permitted to copy and distribute verbatim copies
-of this license document, but changing it is not allowed.</P
-></BLOCKQUOTE
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="bzhacking.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="gfdl-0.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Hacking Bugzilla</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
->&nbsp;</TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->PREAMBLE</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/glossary.html

@@ -1,677 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Glossary</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="PREVIOUS"
-TITLE="How to use this License for your documents"
-HREF="gfdl-howto.html"></HEAD
-><BODY
-CLASS="glossary"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="gfdl-howto.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
->&nbsp;</TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="GLOSSARY"
-><H1
-><A
-NAME="glossary">Glossary</H1
-><DIV
-CLASS="glossdiv"
-><H1
-CLASS="glossdiv"
-><A
-NAME="AEN2610">0-9, high ascii</H1
-><DL
-><DT
-><B
->.htaccess</B
-></DT
-><DD
-><P
->&#13;	    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</H1
-><DL
-><DT
-><B
->Apache</B
-></DT
-><DD
-><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
-><DIV
-CLASS="glossdiv"
-><H1
-CLASS="glossdiv"
-><A
-NAME="gloss-b">B</H1
-><DL
-><DT
-><B
->Bug</B
-></DT
-><DD
-><P
->&#13;	    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
->Bug Number</B
-></DT
-><DD
-><P
->&#13;	    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
->Bug Life Cycle</B
-></DT
-><DD
-><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
->&#13;	    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"></H1
-><DL
-><DT
-><A
-NAME="gloss-component"><B
->Component</B
-></DT
-><DD
-><P
->&#13;	    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
-></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</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"></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
-><DIV
-CLASS="glossdiv"
-><H1
-CLASS="glossdiv"
-><A
-NAME="gloss-i">I</H1
-><DL
-><DT
-><A
-NAME="gloss-infiniteloop"><B
->Infinite Loop</B
-></DT
-><DD
-><P
->A loop of information that never ends; see recursion.</P
-></DD
-></DL
-></DIV
-><DIV
-CLASS="glossdiv"
-><H1
-CLASS="glossdiv"
-><A
-NAME="gloss-m">M</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&#38;T System
-	    V-based systems, such as Solaris and HP/UX, or through the
-	    RC scripts on BSD-based systems.</P
-></DD
-></DL
-></DIV
-><DIV
-CLASS="glossdiv"
-><H1
-CLASS="glossdiv"
-><A
-NAME="gloss-p">P</H1
-><DL
-><DT
-><B
->Product</B
-></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
-><DIV
-CLASS="example"
-><A
-NAME="AEN2701"><P
-><B
->Example 1. A Sample Product</B
-></P
-><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
-CLASS="glossdiv"
-><H1
-CLASS="glossdiv"
-><A
-NAME="gloss-q">Q</H1
-><DL
-><DT
-><B
->QA</B
-></DT
-><DD
-><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
-><DIV
-CLASS="glossdiv"
-><H1
-CLASS="glossdiv"
-><A
-NAME="gloss-r">R</H1
-><DL
-><DT
-><A
-NAME="gloss-recursion"><B
->Recursion</B
-></DT
-><DD
-><P
->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
-NAME="gloss-s">S</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</H1
-><DL
-><DT
-><A
-NAME="gloss-target-milestone"><B
->Target Milestone</B
-></DT
-><DD
-><P
->&#13;	    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
-><DIV
-CLASS="glossdiv"
-><H1
-CLASS="glossdiv"
-><A
-NAME="gloss-z">Z</H1
-><DL
-><DT
-><A
-NAME="zarro-boogs-found"><B
->Zarro Boogs Found</B
-></DT
-><DD
-><P
->This is the cryptic response sent by Bugzilla when a
-	    query returned no results.  It is just a goofy way of
-	    saying "Zero Bugs Found".</P
-></DD
-></DL
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="gfdl-howto.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->&nbsp;</TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->How to use this License for your documents</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
->&nbsp;</TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->&nbsp;</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/granttables.html

@@ -1,351 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->MySQL Permissions &#38; Grant Tables</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><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 Bugzilla Database Introduction"
-HREF="dbdoc.html"><LINK
-REL="NEXT"
-TITLE="Useful Patches and Utilities for Bugzilla"
-HREF="patches.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation 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="dbdoc.html"
-ACCESSKEY="P"
->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="patches.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="granttables">C.3. MySQL Permissions &#38; Grant Tables</H1
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->The following portion of documentation comes from my
-	answer to an old discussion of Keystone, a cool product that
-	does trouble-ticket tracking for IT departments.  I wrote this
-	post to the  Keystone support group regarding MySQL grant
-	table permissions, and how to use them effectively. It is
-	badly in need of updating, as I believe MySQL has added a
-	field or two to the grant tables  since this time, but it
-	serves as a decent introduction and troubleshooting document
-	for grant table issues.  I used Keynote to track my troubles
-	until I discovered Bugzilla, which gave me a whole new set of
-	troubles to work on : )  Although it is of limited use, it
-	still has SOME use, thus it's still included.</P
-><P
->&#13;	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"
-><br>
-From&nbsp;matt_barnson@singletrac.com&nbsp;Wed&nbsp;Jul&nbsp;&nbsp;7&nbsp;09:00:07&nbsp;1999<br>
-Date:&nbsp;Mon,&nbsp;1&nbsp;Mar&nbsp;1999&nbsp;21:37:04&nbsp;-0700&nbsp;<br>
-From:&nbsp;Matthew&nbsp;Barnson&nbsp;matt_barnson@singletrac.com<br>
-To:&nbsp;keystone-users@homeport.org<br>
-Subject:&nbsp;[keystone-users]&nbsp;Grant&nbsp;Tables&nbsp;FAQ<br>
-<br>
-&nbsp;&nbsp;&nbsp;&nbsp;[The&nbsp;following&nbsp;text&nbsp;is&nbsp;in&nbsp;the&nbsp;"iso-8859-1"&nbsp;character&nbsp;set]<br>
-&nbsp;&nbsp;&nbsp;&nbsp;[Your&nbsp;display&nbsp;is&nbsp;set&nbsp;for&nbsp;the&nbsp;"US-ASCII"&nbsp;character&nbsp;set]<br>
-&nbsp;&nbsp;&nbsp;&nbsp;[Some&nbsp;characters&nbsp;may&nbsp;be&nbsp;displayed&nbsp;incorrectly]<br>
-<br>
-Maybe&nbsp;we&nbsp;can&nbsp;include&nbsp;this&nbsp;rambling&nbsp;message&nbsp;in&nbsp;the&nbsp;Keystone&nbsp;FAQ?&nbsp;&nbsp;It&nbsp;gets<br>
-asked&nbsp;a&nbsp;lot,&nbsp;and&nbsp;the&nbsp;only&nbsp;option&nbsp;current&nbsp;listed&nbsp;in&nbsp;the&nbsp;FAQ&nbsp;is<br>
-"--skip-grant-tables".<br>
-<br>
-Really,&nbsp;you&nbsp;can't&nbsp;go&nbsp;wrong&nbsp;by&nbsp;reading&nbsp;section&nbsp;6&nbsp;of&nbsp;the&nbsp;MySQL&nbsp;manual,&nbsp;at<br>
-http://www.mysql.com/Manual/manual.html.&nbsp;&nbsp;I&nbsp;am&nbsp;sure&nbsp;their&nbsp;description&nbsp;is<br>
-better&nbsp;than&nbsp;mine.<br>
-<br>
-MySQL&nbsp;runs&nbsp;fine&nbsp;without&nbsp;permissions&nbsp;set&nbsp;up&nbsp;correctly&nbsp;if&nbsp;you&nbsp;run&nbsp;the&nbsp;mysql<br>
-daemon&nbsp;with&nbsp;the&nbsp;"--skip-grant-tables"&nbsp;option.&nbsp;&nbsp;Running&nbsp;this&nbsp;way&nbsp;denies<br>
-access&nbsp;to&nbsp;nobody.&nbsp;&nbsp;Unfortunately,&nbsp;unless&nbsp;you've&nbsp;got&nbsp;yourself&nbsp;firewalled&nbsp;it<br>
-also&nbsp;opens&nbsp;the&nbsp;potential&nbsp;for&nbsp;abuse&nbsp;if&nbsp;someone&nbsp;knows&nbsp;you're&nbsp;running&nbsp;it.<br>
-<br>
-Additionally,&nbsp;the&nbsp;default&nbsp;permissions&nbsp;for&nbsp;MySQL&nbsp;allow&nbsp;anyone&nbsp;at&nbsp;localhost<br>
-access&nbsp;to&nbsp;the&nbsp;database&nbsp;if&nbsp;the&nbsp;database&nbsp;name&nbsp;begins&nbsp;with&nbsp;"test_"&nbsp;or&nbsp;is&nbsp;named<br>
-"test"&nbsp;(i.e.&nbsp;"test_keystone").&nbsp;&nbsp;You&nbsp;can&nbsp;change&nbsp;the&nbsp;name&nbsp;of&nbsp;your&nbsp;database&nbsp;in<br>
-the&nbsp;keystone.conf&nbsp;file&nbsp;($sys_dbname).&nbsp;&nbsp;This&nbsp;is&nbsp;the&nbsp;way&nbsp;I&nbsp;am&nbsp;doing&nbsp;it&nbsp;for<br>
-some&nbsp;of&nbsp;my&nbsp;databases,&nbsp;and&nbsp;it&nbsp;works&nbsp;fine.<br>
-<br>
-The&nbsp;methods&nbsp;described&nbsp;below&nbsp;assume&nbsp;you're&nbsp;running&nbsp;MySQL&nbsp;on&nbsp;the&nbsp;same&nbsp;box&nbsp;as<br>
-your&nbsp;webserver,&nbsp;and&nbsp;that&nbsp;you&nbsp;don't&nbsp;mind&nbsp;if&nbsp;your&nbsp;$sys_dbuser&nbsp;for&nbsp;Keystone&nbsp;has<br>
-superuser&nbsp;access.&nbsp;&nbsp;See&nbsp;near&nbsp;the&nbsp;bottom&nbsp;of&nbsp;this&nbsp;message&nbsp;for&nbsp;a&nbsp;description&nbsp;of<br>
-what&nbsp;each&nbsp;field&nbsp;does.<br>
-<br>
-Method&nbsp;#1:<br>
-<br>
-1.&nbsp;&nbsp;cd&nbsp;/var/lib<br>
-	#location&nbsp;where&nbsp;you'll&nbsp;want&nbsp;to&nbsp;run&nbsp;/usr/bin/mysql_install_db&nbsp;shell<br>
-script&nbsp;from&nbsp;to&nbsp;get&nbsp;it&nbsp;to&nbsp;work.<br>
-<br>
-2.&nbsp;&nbsp;ln&nbsp;-s&nbsp;mysql&nbsp;data&nbsp;&nbsp;<br>
-	#&nbsp;soft&nbsp;links&nbsp;the&nbsp;"mysql"&nbsp;directory&nbsp;to&nbsp;"data",&nbsp;which&nbsp;is&nbsp;what<br>
-mysql_install_db&nbsp;expects.&nbsp;&nbsp;Alternately,&nbsp;you&nbsp;can&nbsp;edit&nbsp;mysql_install_db&nbsp;and<br>
-change&nbsp;all&nbsp;the&nbsp;"./data"&nbsp;references&nbsp;to&nbsp;"./mysql".<br>
-<br>
-3.&nbsp;&nbsp;Edit&nbsp;/usr/bin/mysql_install_db&nbsp;with&nbsp;your&nbsp;favorite&nbsp;text&nbsp;editor&nbsp;(vi,<br>
-emacs,&nbsp;jot,&nbsp;pico,&nbsp;etc.)<br>
-A)&nbsp;&nbsp;Copy&nbsp;the&nbsp;"INSERT&nbsp;INTO&nbsp;db&nbsp;VALUES<br>
-('%','test\_%','','Y','Y','Y','Y','Y','Y');"&nbsp;and&nbsp;paste&nbsp;it&nbsp;immediately&nbsp;after<br>
-itself.&nbsp;&nbsp;Chage&nbsp;the&nbsp;'test\_%'&nbsp;value&nbsp;to&nbsp;'keystone',&nbsp;or&nbsp;the&nbsp;value&nbsp;of<br>
-$sys_dbname&nbsp;in&nbsp;keystone.conf.<br>
-B)&nbsp;&nbsp;If&nbsp;you&nbsp;are&nbsp;running&nbsp;your&nbsp;keystone&nbsp;database&nbsp;with&nbsp;any&nbsp;user,&nbsp;you'll&nbsp;need&nbsp;to<br>
-copy&nbsp;the&nbsp;"INSERT&nbsp;INTO&nbsp;user&nbsp;VALUES<br>
-('localhost','root','','Y','Y','Y','Y','Y','Y','Y','Y','Y','Y');"&nbsp;line&nbsp;after<br>
-itself&nbsp;and&nbsp;change&nbsp;'root'&nbsp;to&nbsp;the&nbsp;name&nbsp;of&nbsp;the&nbsp;keystone&nbsp;database&nbsp;user<br>
-($sys_dbuser)&nbsp;in&nbsp;keystone.conf.<br>
-<br>
-	#&nbsp;adds&nbsp;entries&nbsp;to&nbsp;the&nbsp;script&nbsp;to&nbsp;create&nbsp;grant&nbsp;tables&nbsp;for&nbsp;specific<br>
-hosts&nbsp;and&nbsp;users.&nbsp;&nbsp;The&nbsp;user&nbsp;you&nbsp;set&nbsp;up&nbsp;has&nbsp;super-user&nbsp;access&nbsp;($sys_dbuser)&nbsp;--<br>
-you&nbsp;may&nbsp;or&nbsp;may&nbsp;not&nbsp;want&nbsp;this.&nbsp;&nbsp;The&nbsp;layout&nbsp;of&nbsp;mysql_install_db&nbsp;is&nbsp;really&nbsp;very<br>
-uncomplicated.<br>
-<br>
-4.&nbsp;&nbsp;/usr/bin/mysqladmin&nbsp;shutdown<br>
-	#&nbsp;ya&nbsp;gotta&nbsp;shut&nbsp;it&nbsp;down&nbsp;before&nbsp;you&nbsp;can&nbsp;reinstall&nbsp;the&nbsp;grant&nbsp;tables!<br>
-<br>
-5.&nbsp;&nbsp;rm&nbsp;-i&nbsp;/var/lib/mysql/mysql/*.IS?'&nbsp;and&nbsp;answer&nbsp;'Y'&nbsp;to&nbsp;the&nbsp;deletion<br>
-questions.<br>
-	#&nbsp;nuke&nbsp;your&nbsp;current&nbsp;grant&nbsp;tables.&nbsp;&nbsp;This&nbsp;WILL&nbsp;NOT&nbsp;delete&nbsp;any&nbsp;other<br>
-databases&nbsp;than&nbsp;your&nbsp;grant&nbsp;tables.<br>
-<br>
-6.&nbsp;&nbsp;/usr/bin/mysql_install_db<br>
-	#&nbsp;run&nbsp;the&nbsp;script&nbsp;you&nbsp;just&nbsp;edited&nbsp;to&nbsp;install&nbsp;your&nbsp;new&nbsp;grant&nbsp;tables.<br>
-<br>
-7.&nbsp;&nbsp;mysqladmin&nbsp;-u&nbsp;root&nbsp;password&nbsp;(new_password)&nbsp;&nbsp;<br>
-	#&nbsp;change&nbsp;the&nbsp;root&nbsp;MySQL&nbsp;password,&nbsp;or&nbsp;else&nbsp;anyone&nbsp;on&nbsp;localhost&nbsp;can<br>
-login&nbsp;to&nbsp;MySQL&nbsp;as&nbsp;root&nbsp;and&nbsp;make&nbsp;changes.&nbsp;&nbsp;You&nbsp;can&nbsp;skip&nbsp;this&nbsp;step&nbsp;if&nbsp;you&nbsp;want<br>
-keystone&nbsp;to&nbsp;connect&nbsp;as&nbsp;root&nbsp;with&nbsp;no&nbsp;password.<br>
-<br>
-8.&nbsp;&nbsp;mysqladmin&nbsp;-u&nbsp;(webserver_user_name)&nbsp;password&nbsp;(new_password)&nbsp;&nbsp;<br>
-	#&nbsp;change&nbsp;the&nbsp;password&nbsp;of&nbsp;the&nbsp;$sys_dbuser.&nbsp;&nbsp;Note&nbsp;that&nbsp;you&nbsp;will&nbsp;need<br>
-to&nbsp;change&nbsp;the&nbsp;password&nbsp;in&nbsp;the&nbsp;keystone.conf&nbsp;file&nbsp;as&nbsp;well&nbsp;in&nbsp;$sys_dbpasswd,<br>
-and&nbsp;if&nbsp;your&nbsp;permissions&nbsp;are&nbsp;set&nbsp;up&nbsp;incorrectly&nbsp;anybody&nbsp;can&nbsp;type&nbsp;the&nbsp;URL&nbsp;to<br>
-your&nbsp;keystone.conf&nbsp;file&nbsp;and&nbsp;get&nbsp;the&nbsp;password.&nbsp;&nbsp;Not&nbsp;that&nbsp;this&nbsp;will&nbsp;help&nbsp;them<br>
-much&nbsp;if&nbsp;your&nbsp;permissions&nbsp;are&nbsp;set&nbsp;to&nbsp;@localhost.<br>
-<br>
-<br>
-<br>
-Method&nbsp;#2:&nbsp;&nbsp;easier,&nbsp;but&nbsp;a&nbsp;pain&nbsp;reproducing&nbsp;if&nbsp;you&nbsp;have&nbsp;to&nbsp;delete&nbsp;your&nbsp;grant<br>
-tables.&nbsp;&nbsp;This&nbsp;is&nbsp;the&nbsp;"recommended"&nbsp;method&nbsp;for&nbsp;altering&nbsp;grant&nbsp;tables&nbsp;in<br>
-MySQL.&nbsp;&nbsp;I&nbsp;don't&nbsp;use&nbsp;it&nbsp;because&nbsp;I&nbsp;like&nbsp;the&nbsp;other&nbsp;way&nbsp;:)<br>
-<br>
-shell&#62;&nbsp;mysql&nbsp;--user=root&nbsp;keystone<br>
-<br>
-mysql&#62;&nbsp;GRANT<br>
-SELECT,INSERT,UPDATE,DELETE,INDEX,ALTER,CREATE,DROP,RELOAD,SHUTDOWN,PROCESS,<br>
-FILE,<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ON&nbsp;keystone.*<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;TO&nbsp;&#60;$sys_dbuser&nbsp;name&#62;@localhost<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;IDENTIFIED&nbsp;BY&nbsp;'(password)'<br>
-	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;WITH&nbsp;GRANT&nbsp;OPTION;<br>
-<br>
-OR<br>
-<br>
-mysql&#62;&nbsp;GRANT&nbsp;ALL&nbsp;PRIVILEGES&nbsp;<br>
-		ON&nbsp;keystone.*<br>
-		TO&nbsp;&#60;$sys_dbuser&nbsp;name&#62;@localhost<br>
-		IDENTIFIED&nbsp;BY&nbsp;'(password)'<br>
-		WITH&nbsp;GRANT&nbsp;OPTION;<br>
-<br>
-	#&nbsp;this&nbsp;grants&nbsp;the&nbsp;required&nbsp;permissions&nbsp;to&nbsp;the&nbsp;keystone&nbsp;($sys_dbuser)<br>
-account&nbsp;defined&nbsp;in&nbsp;keystone.conf.&nbsp;&nbsp;However,&nbsp;if&nbsp;you&nbsp;are&nbsp;runnning&nbsp;many<br>
-different&nbsp;MySQL-based&nbsp;apps,&nbsp;as&nbsp;we&nbsp;are,&nbsp;it's&nbsp;generally&nbsp;better&nbsp;to&nbsp;edit&nbsp;the<br>
-mysql_install_db&nbsp;script&nbsp;to&nbsp;be&nbsp;able&nbsp;to&nbsp;quickly&nbsp;reproduce&nbsp;your&nbsp;permissions<br>
-structure&nbsp;again.&nbsp;&nbsp;Note&nbsp;that&nbsp;the&nbsp;FILE&nbsp;privelege&nbsp;and&nbsp;WITH&nbsp;GRANT&nbsp;OPTION&nbsp;may&nbsp;not<br>
-be&nbsp;in&nbsp;your&nbsp;best&nbsp;interest&nbsp;to&nbsp;include.<br>
-<br>
-<br>
-GRANT&nbsp;TABLE&nbsp;FIELDS&nbsp;EXPLANATION:<br>
-Quick&nbsp;syntax&nbsp;summary:&nbsp;&nbsp;"%"&nbsp;in&nbsp;MySQL&nbsp;is&nbsp;a&nbsp;wildcard.&nbsp;&nbsp;I.E.,&nbsp;if&nbsp;you&nbsp;are<br>
-defining&nbsp;your&nbsp;DB&nbsp;table&nbsp;and&nbsp;in&nbsp;the&nbsp;'host'&nbsp;field&nbsp;and&nbsp;enter&nbsp;'%',&nbsp;that&nbsp;means<br>
-that&nbsp;any&nbsp;host&nbsp;can&nbsp;access&nbsp;that&nbsp;database.&nbsp;&nbsp;Of&nbsp;course,&nbsp;that&nbsp;host&nbsp;must&nbsp;also&nbsp;have<br>
-a&nbsp;valid&nbsp;db&nbsp;user&nbsp;in&nbsp;order&nbsp;to&nbsp;do&nbsp;anything&nbsp;useful.&nbsp;&nbsp;'db'=name&nbsp;of&nbsp;database.&nbsp;&nbsp;In<br>
-our&nbsp;case,&nbsp;it&nbsp;should&nbsp;be&nbsp;"keystone".&nbsp;&nbsp;"user"&nbsp;should&nbsp;be&nbsp;your&nbsp;"$sys_dbuser"<br>
-defined&nbsp;in&nbsp;keystone.conf.&nbsp;&nbsp;Note&nbsp;that&nbsp;you&nbsp;CANNOT&nbsp;add&nbsp;or&nbsp;change&nbsp;a&nbsp;password&nbsp;by<br>
-using&nbsp;the&nbsp;"INSERT&nbsp;INTO&nbsp;db&nbsp;(X)"&nbsp;command&nbsp;--&nbsp;you&nbsp;must&nbsp;change&nbsp;it&nbsp;with&nbsp;the&nbsp;mysql<br>
--u&nbsp;command&nbsp;as&nbsp;defined&nbsp;above.&nbsp;&nbsp;Passwords&nbsp;are&nbsp;stored&nbsp;encrypted&nbsp;in&nbsp;the&nbsp;MySQL<br>
-database,&nbsp;and&nbsp;if&nbsp;you&nbsp;try&nbsp;to&nbsp;enter&nbsp;it&nbsp;directly&nbsp;into&nbsp;the&nbsp;table&nbsp;they&nbsp;will&nbsp;not<br>
-match.<br>
-<br>
-TABLE:&nbsp;&nbsp;USER.&nbsp;&nbsp;Everything&nbsp;after&nbsp;"password"&nbsp;is&nbsp;a&nbsp;privelege&nbsp;granted&nbsp;(Y/N).<br>
-This&nbsp;table&nbsp;controls&nbsp;individual&nbsp;user&nbsp;global&nbsp;access&nbsp;rights.<br>
-<br>
-'host','user','password','select','insert','update','delete','index','alter'<br>
-,'create','drop','grant','reload','shutdown','process','file'<br>
-<br>
-TABLE:&nbsp;&nbsp;DB.&nbsp;&nbsp;This&nbsp;controls&nbsp;access&nbsp;of&nbsp;USERS&nbsp;to&nbsp;databases.<br>
-<br>
-'host','db','user','select','insert','update','delete','index','alter','crea<br>
-te','drop','grant'<br>
-<br>
-TABLE:&nbsp;&nbsp;HOST.&nbsp;&nbsp;This&nbsp;controls&nbsp;which&nbsp;HOSTS&nbsp;are&nbsp;allowed&nbsp;what&nbsp;global&nbsp;access<br>
-rights.&nbsp;&nbsp;Note&nbsp;that&nbsp;the&nbsp;HOST&nbsp;table,&nbsp;USER&nbsp;table,&nbsp;and&nbsp;DB&nbsp;table&nbsp;are&nbsp;very&nbsp;closely<br>
-connected&nbsp;--&nbsp;if&nbsp;an&nbsp;authorized&nbsp;USER&nbsp;attempts&nbsp;an&nbsp;SQL&nbsp;request&nbsp;from&nbsp;an<br>
-unauthorized&nbsp;HOST,&nbsp;she's&nbsp;denied.&nbsp;&nbsp;If&nbsp;a&nbsp;request&nbsp;from&nbsp;an&nbsp;authorized&nbsp;HOST&nbsp;is<br>
-not&nbsp;an&nbsp;authorized&nbsp;USER,&nbsp;it&nbsp;is&nbsp;denied.&nbsp;&nbsp;If&nbsp;a&nbsp;globally&nbsp;authorized&nbsp;USER&nbsp;does<br>
-not&nbsp;have&nbsp;rights&nbsp;to&nbsp;a&nbsp;certain&nbsp;DB,&nbsp;she's&nbsp;denied.&nbsp;&nbsp;Get&nbsp;the&nbsp;picture?<br>
-<br>
-'host','db','select','insert','update','delete','index','alter','create','dr<br>
-op','grant'<br>
-<br>
-<br>
-You&nbsp;should&nbsp;now&nbsp;have&nbsp;a&nbsp;working&nbsp;knowledge&nbsp;of&nbsp;MySQL&nbsp;grant&nbsp;tables.&nbsp;&nbsp;If&nbsp;there&nbsp;is<br>
-anything&nbsp;I've&nbsp;left&nbsp;out&nbsp;of&nbsp;this&nbsp;answer&nbsp;that&nbsp;you&nbsp;feel&nbsp;is&nbsp;pertinent,&nbsp;or&nbsp;if&nbsp;my<br>
-instructions&nbsp;don't&nbsp;work&nbsp;for&nbsp;you,&nbsp;please&nbsp;let&nbsp;me&nbsp;know&nbsp;and&nbsp;I'll&nbsp;re-post&nbsp;this<br>
-letter&nbsp;again,&nbsp;corrected.&nbsp;&nbsp;I&nbsp;threw&nbsp;it&nbsp;together&nbsp;one&nbsp;night&nbsp;out&nbsp;of&nbsp;exasperation<br>
-for&nbsp;all&nbsp;the&nbsp;newbies&nbsp;who&nbsp;don't&nbsp;know&nbsp;squat&nbsp;about&nbsp;MySQL&nbsp;yet,&nbsp;so&nbsp;it&nbsp;is&nbsp;almost<br>
-guaranteed&nbsp;to&nbsp;have&nbsp;errors.<br>
-<br>
-Once&nbsp;again,&nbsp;you&nbsp;can't&nbsp;go&nbsp;wrong&nbsp;by&nbsp;reading&nbsp;section&nbsp;6&nbsp;of&nbsp;the&nbsp;MySQL&nbsp;manual.&nbsp;&nbsp;It<br>
-is&nbsp;more&nbsp;detailed&nbsp;than&nbsp;I!<br>
-http://www.mysql.com/Manual/manual.html.<br>
-<br>
-&nbsp;&nbsp;&nbsp;&nbsp;</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="dbdoc.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="patches.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->MySQL Bugzilla Database Introduction</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="database.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Useful Patches and Utilities for Bugzilla</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/how.html

@@ -1,788 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->How do I use Bugzilla?</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Using Bugzilla"
-HREF="using.html"><LINK
-REL="PREVIOUS"
-TITLE="Why Should We Use Bugzilla?"
-HREF="why.html"><LINK
-REL="NEXT"
-TITLE="Where can I find my user preferences?"
-HREF="init4me.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="why.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 2. Using Bugzilla</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="init4me.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="how">2.3. How do I use Bugzilla?</H1
-><TABLE
-BORDER="0"
-WIDTH="100%"
-CELLSPACING="0"
-CELLPADDING="0"
-CLASS="EPIGRAPH"
-><TR
-><TD
-WIDTH="45%"
->&nbsp;</TD
-><TD
-WIDTH="45%"
-ALIGN="LEFT"
-VALIGN="TOP"
-><I
-><P
-><I
->Hey!  I'm Woody!  Howdy, Howdy, Howdy!</I
-></P
-></I
-></TD
-></TR
-></TABLE
-><P
->&#13;      This section contains information for end-users of Bugzilla. 
-      If you are administering a Bugzilla installation, please consult the
-      Installing and Administering Bugzilla portions of this Guide.
-    </P
-><P
->&#13;      There is a Bugzilla test installation, called
-      <A
-HREF="http://landfill.tequilarista.org/"
-TARGET="_top"
->&#13;	    Landfill</A
->, which you are welcome to play with.
-      However, it does not necessarily have all Bugzilla features
-      enabled, and often runs cutting-edge versions of Bugzilla for
-      testing, so some things may work slightly differently than
-      mentioned here.
-    </P
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="myaccount">2.3.1. Create a Bugzilla Account</H2
-><P
->&#13;	If you want to use Bugzilla, first you
-	need to create an account.  Consult with the administrator
-	responsible for your installation of Bugzilla for the URL you
-	should use to access it. If you're test-driving Bugzilla, 
-  use this URL: <A
-HREF="http://landfill.tequilarista.org/bugzilla-tip/"
-TARGET="_top"
-> http://landfill.tequilarista.org/bugzilla-tip/</A
->
-      </P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->&#13;	    Click the <SPAN
-CLASS="QUOTE"
->"Open a new Bugzilla account"</SPAN
-> link, enter your 
-      email address and, optionally, your name in the spaces provided,
-	    then click <SPAN
-CLASS="QUOTE"
->"Create Account"</SPAN
->.
-	  </P
-></LI
-><LI
-><P
->&#13;	    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 can be changed to something more memorable.
-	  </P
-></LI
-><LI
-><P
->&#13;	    Click the <SPAN
-CLASS="QUOTE"
->"Log In"</SPAN
-> link in the yellow area at
-	    the bottom of the page in your browser, enter your
-	    email address and password into the spaces provided, and click
-	    <SPAN
-CLASS="QUOTE"
->"Login"</SPAN
->.
-	  </P
-></LI
-></OL
-><P
->&#13;	You are now logged in. Bugzilla uses cookies for authentication, so
-  (unless your IP address changes) you should not have to log in again.
-      </P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="bug_page">2.3.2. Anatomy of a Bug</H2
-><P
->&#13;        The core of Bugzilla is the screen which displays a particular bug.
-        It's a good place to explain some Bugzilla concepts. 
-        <A
-HREF="http://landfill.tequilarista.org/bugzilla-tip/show_bug.cgi?id=1"
-TARGET="_top"
->Bug 1 on Landfill</A
-> is a good example. Note that the names of most fields
-        are hyperlinks; clicking them will take you to context-sensitive
-        help on that particular field.
-      </P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->&#13;      <EM
->Product and Component</EM
->:
-      Bugs are divided up by Product and Component, with a Product having one
-      or more Components in it. For example, bugzilla.mozilla.org's 
-      "Bugzilla" Product is composed of several Components:
-		  <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><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
-><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
-
-        </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
-><P
-></P
->
-		</P
-></LI
-><LI
-><P
->&#13;      <EM
->Status and Resolution</EM
->: 
-      A bug passes through several Statuses in its lifetime, and ends up in the
-      RESOLVED status, with one of a set of Resolutions (e.g. FIXED, INVALID.)
-      The different possible
-      values for Status and Resolution on your installation will be documented
-      in the context-sensitive help for those items.
-		</P
-></LI
-><LI
-><P
->&#13;      <EM
->Assigned To</EM
->:
-      The person responsible for fixing the bug.
-	  </P
-></LI
-><LI
-><P
->&#13;      <EM
->URL</EM
->:
-      A URL associated with the bug, if any.
-	  </P
-></LI
-><LI
-><P
->&#13;      <EM
->Summary</EM
->:
-      A one-sentence summary of the problem.
-	  </P
-></LI
-><LI
-><P
->&#13;	    <EM
->Status Whiteboard</EM
->: (a.k.a. Whiteboard) A
-      free-form text area for adding short notes and tags to a bug.
-	  </P
-></LI
-><LI
-><P
->&#13;      <EM
->Keywords</EM
->:
-      The administrator can define keywords which you can use to tag and
-      categorise bugs - e.g. The Mozilla Project has keywords like crash
-      and regression.
-	  </P
-></LI
-><LI
-><P
->&#13;      <EM
->Platform and OS</EM
->:
-      These indicate the computing environment where the bug was found.
-	  </P
-></LI
-><LI
-><P
->&#13;      <EM
->Version</EM
->:
-      The "Version" field is usually used for versions of a product which have
-      been released, and is set to indicate which versions of a Component
-      have the particular problem the bug report is about.
-	  </P
-></LI
-><LI
-><P
->&#13;      <EM
->Priority</EM
->:
-      The bug assignee uses this field to prioritise his or her bugs. It's
-      a good idea not to change this on other people's bugs.
-	  </P
-></LI
-><LI
-><P
->&#13;      <EM
->Severity</EM
->:
-      This indicates how severe the problem is - from blocker ("application
-      unusable") to trivial ("minor cosmetic issue"). You can also use this
-      field to indicate whether a bug is an enhancement request.
-	  </P
-></LI
-><LI
-><P
->&#13;      <EM
->Target</EM
->:
-	    (a.k.a. Target Milestone) A future version by which the bug is to be
-      fixed. e.g. The Bugzilla Project's milestones for future
-	    Bugzilla versions are 2.18, 2.20, 3.0, etc. Milestones are 
-      not restricted to numbers, thought - you can use any text strings, 
-      such as dates.  
-	  </P
-></LI
-><LI
-><P
->&#13;      <EM
->Reporter</EM
->:
-      The person who filed the bug.
-	  </P
-></LI
-><LI
-><P
->&#13;      <EM
->CC list</EM
->:
-      A list of people who get mail when the bug changes.
-	  </P
-></LI
-><LI
-><P
->&#13;      <EM
->Attachments</EM
->:
-      You can attach files (e.g. testcases or patches) to bugs. If there are
-      any attachments, they are listed in this section.
-	  </P
-></LI
-><LI
-><P
->&#13;      <EM
->Dependencies</EM
->:
-      If this bug cannot be fixed unless other bugs are fixed (depends on), or
-      this bug stops other bugs being fixed (blocks), their numbers are 
-      recorded here.
-	  </P
-></LI
-><LI
-><P
->&#13;      <EM
->Votes</EM
->:
-      Whether this bug has any votes.
-	  </P
-></LI
-><LI
-><P
->&#13;      <EM
->Additional Comments</EM
->:
-      You can add your two cents to the bug discussion here, if you have 
-      something worthwhile to say.
-	  </P
-></LI
-></OL
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="query">2.3.3. Searching for Bugs</H2
-><P
->&#13;	The Bugzilla Search page is is the interface where you can
-	find any bug report, comment, or patch currently in the
-	Bugzilla system. You can play with it here:
-	<A
-HREF="http://landfill.tequilarista.org/bugzilla-tip/query.cgi"
-TARGET="_top"
->&#13;	landfill.tequilarista.org/bugzilla-tip/query.cgi</A
->.
-  </P
-><P
->&#13;    The Search page has controls for selecting different possible values
-    for all of the fields in a bug, as described above. Once you've defined
-    a search, you can either run it, or save it as a Remembered Query, which
-    can optionally appear in the footer of your pages.
-  </P
-><P
->&#13;    Highly advanced querying is done using Boolean Charts, which have their
-    own <A
-HREF="http://landfill.tequilarista.org/bugzilla-tip/booleanchart.html"
-TARGET="_top"
->context-sensitive help</A
->.
-  </P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="list">2.3.4. Bug Lists</H2
-><P
->&#13;        If you run a search, a list of matching bugs will be returned. 
-        The default search is to return all open bugs on the system -
-        don't try running this search on a Bugzilla installation with
-        a lot of bugs!
-      </P
-><P
->&#13;        The format of the list is configurable. For example, it can be 
-        sorted by clicking the column headings. Other useful features
-        can be accessed using the links at the bottom of the list:
-	<P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
-><EM
->Long Format</EM
->: this gives you a large page
-    with a non-editable summary of the fields of each bug.</TD
-></TR
-><TR
-><TD
-><EM
->Change Columns</EM
->: change the bug 
-    attributes which appear in the list.</TD
-></TR
-><TR
-><TD
-><EM
->Change several bugs at once</EM
->: If
-	    your account is sufficiently empowered, you can make the same
-      change to all the bugs in the list - for example, changing their
-      owner.</TD
-></TR
-><TR
-><TD
-><EM
->Send mail to bug owners</EM
->: Sends mail
-    to the owners of all bugs on the list.</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
->
-      </P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="bugreports">2.3.5. Filing Bugs</H2
-><TABLE
-BORDER="0"
-WIDTH="100%"
-CELLSPACING="0"
-CELLPADDING="0"
-CLASS="EPIGRAPH"
-><TR
-><TD
-WIDTH="45%"
->&nbsp;</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
-><P
->&#13;	  Years of bug writing experience has been distilled for your reading
-    pleasure into the <A
-HREF="http://landfill.tequilarista.org/bugzilla-tip/bugwritinghelp.html"
-TARGET="_top"
->&#13;    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.
-	</P
-><P
->&#13;    The procedure for filing a test bug is as follows:
-  </P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->&#13;	      Go to <A
-HREF="http://landfill.tequilarista.org/bugzilla-tip/"
-TARGET="_top"
->Landfill</A
-> 
-        in your browser and click  
-        <A
-HREF="http://landfill.tequilarista.org/bugzilla-tip/enter_bug.cgi"
-TARGET="_top"
-> Enter a new bug report</A
->.
-	    </P
-></LI
-><LI
-><P
->&#13;	      Select a product - any one will do.
-	    </P
-></LI
-><LI
-><P
->&#13;        Fill in the fields.
-	      Bugzilla should have made reasonable guesses, based upon
-	      your browser, for the "Platform" and "OS" drop-down
-	      boxes. If they are wrong, change them.
-	    </P
-></LI
-><LI
-><P
->&#13;	      Select "Commit" and send in your bug report. 
-	    </P
-></LI
-></OL
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="why.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="init4me.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Why Should We Use Bugzilla?</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="using.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Where can I find my user preferences?</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/index.html

@@ -1,586 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->The Bugzilla Guide</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="NEXT"
-TITLE="About This Guide"
-HREF="about.html"><META
-NAME="KEYWORD"
-CONTENT="Bugzilla"><META
-NAME="KEYWORD"
-CONTENT="Guide"><META
-NAME="KEYWORD"
-CONTENT="installation"><META
-NAME="KEYWORD"
-CONTENT="FAQ"><META
-NAME="KEYWORD"
-CONTENT="administration"><META
-NAME="KEYWORD"
-CONTENT="integration"><META
-NAME="KEYWORD"
-CONTENT="MySQL"><META
-NAME="KEYWORD"
-CONTENT="Mozilla"><META
-NAME="KEYWORD"
-CONTENT="webtools"></HEAD
-><BODY
-CLASS="book"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="BOOK"
-><A
-NAME="index"><DIV
-CLASS="TITLEPAGE"
-><H1
-CLASS="title"
-><A
-NAME="AEN2">The Bugzilla Guide</H1
-><H3
-CLASS="author"
-><A
-NAME="AEN5">Matthew P. Barnson</H3
-><DIV
-CLASS="affiliation"
-><DIV
-CLASS="address"
-><P
-CLASS="address"
->mbarnson@sisna.com</P
-></DIV
-></DIV
-><DIV
-><DIV
-CLASS="abstract"
-><A
-NAME="AEN12"><P
-></P
-><P
->&#13;	This is the documentation for Bugzilla, the mozilla.org
-	bug-tracking system.
-	Bugzilla is an enterprise-class piece of software
-	that powers issue-tracking for hundreds of
-	organizations around the world, tracking millions of bugs.
-      </P
-><P
->&#13;	This documentation is maintained in DocBook 4.1.2 XML format.
-  Changes are best submitted as plain text or SGML diffs, attached
-  to a Bugzilla bug.
-      </P
-><P
-></P
-></DIV
-></DIV
-><HR></DIV
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->1. <A
-HREF="about.html"
->About This Guide</A
-></DT
-><DD
-><DL
-><DT
->1.1. <A
-HREF="aboutthisguide.html"
->Purpose and Scope of this Guide</A
-></DT
-><DT
->1.2. <A
-HREF="copyright.html"
->Copyright Information</A
-></DT
-><DT
->1.3. <A
-HREF="disclaimer.html"
->Disclaimer</A
-></DT
-><DT
->1.4. <A
-HREF="newversions.html"
->New Versions</A
-></DT
-><DT
->1.5. <A
-HREF="credits.html"
->Credits</A
-></DT
-><DT
->1.6. <A
-HREF="translations.html"
->Translations</A
-></DT
-><DT
->1.7. <A
-HREF="conventions.html"
->Document Conventions</A
-></DT
-></DL
-></DD
-><DT
->2. <A
-HREF="using.html"
->Using Bugzilla</A
-></DT
-><DD
-><DL
-><DT
->2.1. <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
-><DT
->2.4. <A
-HREF="init4me.html"
->Where can I find my user preferences?</A
-></DT
-><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
->3.1. <A
-HREF="errata.html"
->ERRATA</A
-></DT
-><DT
->3.2. <A
-HREF="stepbystep.html"
->Step-by-step Install</A
-></DT
-><DT
->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
-><DT
->3.6. <A
-HREF="win32.html"
->Win32 Installation Notes</A
-></DT
-></DL
-></DD
-><DT
->4. <A
-HREF="administration.html"
->Administering Bugzilla</A
-></DT
-><DD
-><DL
-><DT
->4.1. <A
-HREF="postinstall-check.html"
->Post-Installation Checklist</A
-></DT
-><DT
->4.2. <A
-HREF="useradmin.html"
->User Administration</A
-></DT
-><DT
->4.3. <A
-HREF="programadmin.html"
->Product, Component, Milestone, and Version
-      Administration</A
-></DT
-><DT
->4.4. <A
-HREF="security.html"
->Bugzilla Security</A
-></DT
-></DL
-></DD
-><DT
->5. <A
-HREF="integration.html"
->Integrating Bugzilla with Third-Party Tools</A
-></DT
-><DD
-><DL
-><DT
->5.1. <A
-HREF="bonsai.html"
->Bonsai</A
-></DT
-><DT
->5.2. <A
-HREF="cvs.html"
->CVS</A
-></DT
-><DT
->5.3. <A
-HREF="scm.html"
->Perforce SCM</A
-></DT
-><DT
->5.4. <A
-HREF="tinderbox.html"
->Tinderbox/Tinderbox2</A
-></DT
-></DL
-></DD
-><DT
->6. <A
-HREF="variants.html"
->Bugzilla Variants and Competitors</A
-></DT
-><DD
-><DL
-><DT
->6.1. <A
-HREF="rhbugzilla.html"
->Red Hat Bugzilla</A
-></DT
-><DT
->6.2. <A
-HREF="variant-fenris.html"
->Loki Bugzilla (Fenris)</A
-></DT
-><DT
->6.3. <A
-HREF="variant-issuezilla.html"
->Issuezilla</A
-></DT
-><DT
->6.4. <A
-HREF="variant-scarab.html"
->Scarab</A
-></DT
-><DT
->6.5. <A
-HREF="variant-perforce.html"
->Perforce SCM</A
-></DT
-><DT
->6.6. <A
-HREF="variant-sourceforge.html"
->SourceForge</A
-></DT
-></DL
-></DD
-><DT
->A. <A
-HREF="faq.html"
->The Bugzilla FAQ</A
-></DT
-><DT
->B. <A
-HREF="downloadlinks.html"
->Software Download Links</A
-></DT
-><DT
->C. <A
-HREF="database.html"
->The Bugzilla Database</A
-></DT
-><DD
-><DL
-><DT
->C.1. <A
-HREF="dbschema.html"
->Database Schema Chart</A
-></DT
-><DT
->C.2. <A
-HREF="dbdoc.html"
->MySQL Bugzilla Database Introduction</A
-></DT
-><DT
->C.3. <A
-HREF="granttables.html"
->MySQL Permissions &#38; Grant Tables</A
-></DT
-></DL
-></DD
-><DT
->D. <A
-HREF="patches.html"
->Useful Patches and Utilities for Bugzilla</A
-></DT
-><DD
-><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.3. <A
-HREF="cmdline.html"
->Command-line Bugzilla Queries</A
-></DT
-><DT
->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
->E. <A
-HREF="gfdl.html"
->GNU Free Documentation License</A
-></DT
-><DD
-><DL
-><DT
->0. <A
-HREF="gfdl-0.html"
->PREAMBLE</A
-></DT
-><DT
->1. <A
-HREF="gfdl-1.html"
->APPLICABILITY AND DEFINITIONS</A
-></DT
-><DT
->2. <A
-HREF="gfdl-2.html"
->VERBATIM COPYING</A
-></DT
-><DT
->3. <A
-HREF="gfdl-3.html"
->COPYING IN QUANTITY</A
-></DT
-><DT
->4. <A
-HREF="gfdl-4.html"
->MODIFICATIONS</A
-></DT
-><DT
->5. <A
-HREF="gfdl-5.html"
->COMBINING DOCUMENTS</A
-></DT
-><DT
->6. <A
-HREF="gfdl-6.html"
->COLLECTIONS OF DOCUMENTS</A
-></DT
-><DT
->7. <A
-HREF="gfdl-7.html"
->AGGREGATION WITH INDEPENDENT WORKS</A
-></DT
-><DT
->8. <A
-HREF="gfdl-8.html"
->TRANSLATION</A
-></DT
-><DT
->9. <A
-HREF="gfdl-9.html"
->TERMINATION</A
-></DT
-><DT
->10. <A
-HREF="gfdl-10.html"
->FUTURE REVISIONS OF THIS LICENSE</A
-></DT
-><DT
-><A
-HREF="gfdl-howto.html"
->How to use this License for your documents</A
-></DT
-></DL
-></DD
-><DT
-><A
-HREF="glossary.html"
->Glossary</A
-></DT
-></DL
-></DIV
-><DIV
-CLASS="LOT"
-><DL
-CLASS="LOT"
-><DT
-><B
->List of Examples</B
-></DT
-><DT
->3-1. <A
-HREF="stepbystep.html#AEN641"
->Setting up bonsaitools symlink</A
-></DT
-><DT
->3-2. <A
-HREF="stepbystep.html#AEN732"
->Running checksetup.pl as the web user</A
-></DT
-><DT
->3-3. <A
-HREF="win32.html#AEN985"
->Installing ActivePerl ppd Modules on Microsoft Windows</A
-></DT
-><DT
->3-4. <A
-HREF="win32.html#AEN998"
->Installing OpenInteract ppd Modules manually on Microsoft
-              Windows</A
-></DT
-><DT
->3-5. <A
-HREF="win32.html#AEN1180"
->Removing encrypt() for Windows NT Bugzilla version
-	      2.12 or earlier</A
-></DT
-><DT
->4-1. <A
-HREF="programadmin.html#AEN1405"
->Creating some Components</A
-></DT
-><DT
->4-2. <A
-HREF="programadmin.html#AEN1434"
->Common Use of Versions</A
-></DT
-><DT
->4-3. <A
-HREF="programadmin.html#AEN1438"
->A Different Use of Versions</A
-></DT
-><DT
->4-4. <A
-HREF="programadmin.html#AEN1466"
->Using SortKey with Target Milestone</A
-></DT
-><DT
->4-5. <A
-HREF="programadmin.html#AEN1502"
->When to Use Group Security</A
-></DT
-><DT
->4-6. <A
-HREF="programadmin.html#AEN1519"
->Creating a New Group</A
-></DT
-><DT
->4-7. <A
-HREF="programadmin.html#AEN1536"
->Bugzilla Groups</A
-></DT
-><DT
->D-1. <A
-HREF="setperl.html#AEN2380"
->Using Setperl to set your perl path</A
-></DT
-><DT
->1. <A
-HREF="glossary.html#AEN2701"
->A Sample Product</A
-></DT
-></DL
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->&nbsp;</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
->&nbsp;</TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="about.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->&nbsp;</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
->&nbsp;</TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->About This Guide</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/init4me.html

@@ -1,451 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Where can I find my user preferences?</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Using Bugzilla"
-HREF="using.html"><LINK
-REL="PREVIOUS"
-TITLE="How do I use Bugzilla?"
-HREF="how.html"><LINK
-REL="NEXT"
-TITLE="Using Bugzilla-Conclusion"
-HREF="usingbz-conc.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="how.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 2. Using Bugzilla</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="usingbz-conc.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="init4me">2.4. Where can I find my user preferences?</H1
-><TABLE
-BORDER="0"
-WIDTH="100%"
-CELLSPACING="0"
-CELLPADDING="0"
-CLASS="EPIGRAPH"
-><TR
-><TD
-WIDTH="45%"
->&nbsp;</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
-></TABLE
-><P
->&#13;      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"
-><H2
-CLASS="section"
-><A
-NAME="accountsettings">2.4.1. Account Settings</H2
-><P
->&#13;	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"
-><H2
-CLASS="section"
-><A
-NAME="emailsettings">2.4.2. Email Settings</H2
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="notification">2.4.2.1. Email Notification</H3
-><P
->&#13;	  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
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="newemailtech">2.4.2.2. New Email Technology</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
->&#13;	    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
-></TABLE
-></DIV
-><P
->&#13;	  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
->&#13;	  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"
-><H3
-CLASS="section"
-><A
-NAME="watchsettings">2.4.2.3. "Watching" Users</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
->&#13;	    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
->&#13;	  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"
-><H2
-CLASS="section"
-><A
-NAME="footersettings">2.4.3. Page Footer</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
->&#13;	  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
->&#13;	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
-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"
-><H2
-CLASS="section"
-><A
-NAME="permissionsettings">2.4.4. Permissions</H2
-><P
->&#13;	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="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="how.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="usingbz-conc.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->How do I use Bugzilla?</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="using.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Using Bugzilla-Conclusion</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/installation.html

@@ -1,341 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Installation</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="PREVIOUS"
-TITLE="Using Bugzilla-Conclusion"
-HREF="usingbz-conc.html"><LINK
-REL="NEXT"
-TITLE="ERRATA"
-HREF="errata.html"></HEAD
-><BODY
-CLASS="chapter"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="usingbz-conc.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="errata.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="chapter"
-><H1
-><A
-NAME="installation">Chapter 3. Installation</H1
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->3.1. <A
-HREF="errata.html"
->ERRATA</A
-></DT
-><DT
->3.2. <A
-HREF="stepbystep.html"
->Step-by-step Install</A
-></DT
-><DD
-><DL
-><DT
->3.2.1. <A
-HREF="stepbystep.html#AEN441"
->Introduction</A
-></DT
-><DT
->3.2.2. <A
-HREF="stepbystep.html#AEN447"
->Installing the Prerequisites</A
-></DT
-><DT
->3.2.3. <A
-HREF="stepbystep.html#install-mysql"
->Installing MySQL Database</A
-></DT
-><DT
->3.2.4. <A
-HREF="stepbystep.html#install-perl"
->Perl (5.004 or greater)</A
-></DT
-><DT
->3.2.5. <A
-HREF="stepbystep.html#AEN534"
->DBI Perl Module</A
-></DT
-><DT
->3.2.6. <A
-HREF="stepbystep.html#AEN572"
->Data::Dumper Perl Module</A
-></DT
-><DT
->3.2.7. <A
-HREF="stepbystep.html#AEN577"
->MySQL related Perl Module Collection</A
-></DT
-><DT
->3.2.8. <A
-HREF="stepbystep.html#AEN586"
->TimeDate Perl Module Collection</A
-></DT
-><DT
->3.2.9. <A
-HREF="stepbystep.html#AEN590"
->GD Perl Module (1.8.3)</A
-></DT
-><DT
->3.2.10. <A
-HREF="stepbystep.html#AEN599"
->Chart::Base Perl Module (0.99c)</A
-></DT
-><DT
->3.2.11. <A
-HREF="stepbystep.html#AEN603"
->DB_File Perl Module</A
-></DT
-><DT
->3.2.12. <A
-HREF="stepbystep.html#AEN606"
->HTTP Server</A
-></DT
-><DT
->3.2.13. <A
-HREF="stepbystep.html#AEN625"
->Installing the Bugzilla Files</A
-></DT
-><DT
->3.2.14. <A
-HREF="stepbystep.html#AEN654"
->Setting Up the MySQL Database</A
-></DT
-><DT
->3.2.15. <A
-HREF="stepbystep.html#AEN701"
->Tweaking <TT
-CLASS="filename"
->localconfig</TT
-></A
-></DT
-><DT
->3.2.16. <A
-HREF="stepbystep.html#AEN739"
->Setting Up Maintainers Manually (Optional)</A
-></DT
-><DT
->3.2.17. <A
-HREF="stepbystep.html#AEN750"
->The Whining Cron (Optional)</A
-></DT
-><DT
->3.2.18. <A
-HREF="stepbystep.html#AEN760"
->Bug Graphs (Optional)</A
-></DT
-><DT
->3.2.19. <A
-HREF="stepbystep.html#AEN772"
->Securing MySQL</A
-></DT
-></DL
-></DD
-><DT
->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
->3.5.1. <A
-HREF="geninstall.html#AEN874"
->Modifying Your Running System</A
-></DT
-><DT
->3.5.2. <A
-HREF="geninstall.html#AEN881"
->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
->3.6. <A
-HREF="win32.html"
->Win32 Installation Notes</A
-></DT
-><DD
-><DL
-><DT
->3.6.1. <A
-HREF="win32.html#wininstall"
->Win32 Installation: Step-by-step</A
-></DT
-><DT
->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
->&#13;      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"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="usingbz-conc.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="errata.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Using Bugzilla-Conclusion</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
->&nbsp;</TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->ERRATA</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/integration.html

@@ -1,163 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Integrating Bugzilla with Third-Party Tools</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="PREVIOUS"
-TITLE="Bugzilla Security"
-HREF="security.html"><LINK
-REL="NEXT"
-TITLE="Bonsai"
-HREF="bonsai.html"></HEAD
-><BODY
-CLASS="chapter"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="security.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="bonsai.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="chapter"
-><H1
-><A
-NAME="integration">Chapter 5. Integrating Bugzilla with Third-Party Tools</H1
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->5.1. <A
-HREF="bonsai.html"
->Bonsai</A
-></DT
-><DT
->5.2. <A
-HREF="cvs.html"
->CVS</A
-></DT
-><DT
->5.3. <A
-HREF="scm.html"
->Perforce SCM</A
-></DT
-><DT
->5.4. <A
-HREF="tinderbox.html"
->Tinderbox/Tinderbox2</A
-></DT
-></DL
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="security.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="bonsai.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Bugzilla Security</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
->&nbsp;</TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Bonsai</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/newversions.html

@@ -1,188 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->New Versions</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="About This Guide"
-HREF="about.html"><LINK
-REL="PREVIOUS"
-TITLE="Disclaimer"
-HREF="disclaimer.html"><LINK
-REL="NEXT"
-TITLE="Credits"
-HREF="credits.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="disclaimer.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 1. About This Guide</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="credits.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="newversions">1.4. New Versions</H1
-><P
->&#13;      This is the 2.16 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
->&#13;      This document can be found in the following places:
-    </P
-><P
->&#13;      <P
-></P
-><UL
-><LI
-><P
->&#13;	    <A
-HREF="http://www.bugzilla.org/"
-TARGET="_top"
->bugzilla.org</A
->
-	  </P
-></LI
-><LI
-><P
->&#13;	    <A
-HREF="http://www.linuxdoc.org/"
-TARGET="_top"
->The Linux
-	      Documentation Project</A
->
-	  </P
-></LI
-></UL
->
-    </P
-><P
->&#13;      The latest version of this document can be checked out via CVS.
-	Please follow the instructions available at <A
-HREF="http://www.mozilla.org/cvs.html"
-TARGET="_top"
->the Mozilla CVS page</A
->, and check out the <TT
-CLASS="filename"
->mozilla/webtools/bugzilla/docs/</TT
-> branch.
-    </P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="disclaimer.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="credits.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Disclaimer</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="about.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Credits</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/osx.html

@@ -1,296 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Mac OS X Installation Notes</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><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
-SUMMARY="Header navigation 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"
-ACCESSKEY="P"
->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"
-ACCESSKEY="N"
->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</H1
-><P
->&#13;      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
->&#13;      The easiest way to get a lot of these is with a program called
-      Fink, which is similar in nature to the CPAN installer, but
-      installs common GNU utilities.  Fink is available from
-      &#60;http://sourceforge.net/projects/fink/&#62;.
-    </P
-><P
->&#13;      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
->&#13;      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
->&#13;      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
->&#13;      Instead of typing <SPAN
-CLASS="QUOTE"
->"install GD"</SPAN
-> at the
-      <TT
-CLASS="prompt"
->cpan&#62;</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 &#60;
-	patchfile</B
->:
-    </P
-><P
->&#13;      <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->&#13;
-	
---- 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";
- 
- # =====&#62; PATHS: CHECK AND ADJUST &#60;=====
--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' &#38;&#38; $^O ne 'MSWin32') {
-
- 
-      </PRE
-></FONT
-></TD
-></TR
-></TABLE
->
-    </P
-><P
->&#13;      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
->&#13;      Happy Hacking!
-    </P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="stepbystep.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="bsdinstall.html"
-ACCESSKEY="N"
->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"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->BSD Installation Notes</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/patches.html

@@ -1,190 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Useful Patches and Utilities for Bugzilla</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="PREVIOUS"
-TITLE="MySQL Permissions & Grant Tables"
-HREF="granttables.html"><LINK
-REL="NEXT"
-TITLE="Apache mod_rewrite magic"
-HREF="rewrite.html"></HEAD
-><BODY
-CLASS="appendix"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="granttables.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="rewrite.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="appendix"
-><H1
-><A
-NAME="patches">Appendix D. Useful Patches and Utilities for Bugzilla</H1
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></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.3. <A
-HREF="cmdline.html"
->Command-line Bugzilla Queries</A
-></DT
-><DT
->D.4. <A
-HREF="quicksearch.html"
->The Quicksearch Utility</A
-></DT
-><DT
->D.5. <A
-HREF="bzhacking.html"
->Hacking Bugzilla</A
-></DT
-><DD
-><DL
-><DT
->D.5.1. <A
-HREF="bzhacking.html#AEN2436"
->Things that have caused problems and should be avoided</A
-></DT
-><DT
->D.5.2. <A
-HREF="bzhacking.html#AEN2450"
->Coding Style for Bugzilla</A
-></DT
-></DL
-></DD
-></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"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="granttables.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="rewrite.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->MySQL Permissions &#38; Grant Tables</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
->&nbsp;</TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Apache <TT
-CLASS="filename"
->mod_rewrite</TT
-> magic</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/postinstall-check.html

@@ -1,565 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Post-Installation Checklist</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Administering Bugzilla"
-HREF="administration.html"><LINK
-REL="PREVIOUS"
-TITLE="Administering Bugzilla"
-HREF="administration.html"><LINK
-REL="NEXT"
-TITLE="User Administration"
-HREF="useradmin.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="administration.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 4. Administering Bugzilla</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="useradmin.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="postinstall-check">4.1. Post-Installation Checklist</H1
-><P
->&#13;      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
->&#13;	  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
->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
->&#13;	  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
->The <SPAN
-CLASS="QUOTE"
->"urlbase"</SPAN
-> parameter defines the fully
-	  qualified domain name and web server path to your Bugzilla
-	  installation.</P
-><P
->&#13;	  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
-><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
->&#13;	  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
->&#13;	  <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
->&#13;	  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
->&#13;	  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
->&#13;	  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
->&#13;	      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
->&#13;	  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
-><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
->&#13;	  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"
-><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
->&#13;	      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
-></LI
-><LI
-><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
->&#13;	  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
-><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
->&#13;	  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
->&#13;	  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
->&#13;	  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
-></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
->&#13;	      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
-></LI
-><LI
-><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 privileges.  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
->&#13;	  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="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="administration.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="useradmin.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Administering Bugzilla</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="administration.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->User Administration</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/quicksearch.html

@@ -1,197 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->The Quicksearch Utility</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><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="Command-line Bugzilla Queries"
-HREF="cmdline.html"><LINK
-REL="NEXT"
-TITLE="Hacking Bugzilla"
-HREF="bzhacking.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="cmdline.html"
-ACCESSKEY="P"
->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="bzhacking.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="quicksearch">D.4. The Quicksearch Utility</H1
-><P
->&#13;      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"
-    </P
-><P
->&#13;      The index.html page has been updated to include the QuickSearch
-      text box.
-    </P
-><P
->&#13;      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
->&#13;      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
->&#13;      Workarounds for Bugzilla users:
-      <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><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
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
-    </P
-><P
->&#13;      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.
-    </P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="cmdline.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="bzhacking.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Command-line Bugzilla Queries</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="patches.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Hacking Bugzilla</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/rewrite.html

@@ -1,199 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Apache mod_rewrite magic</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><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
-SUMMARY="Header navigation 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"
-ACCESSKEY="P"
->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"
-ACCESSKEY="N"
->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</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
->&#13;	  Make it so if someone types
-	  <TT
-CLASS="computeroutput"
->http://www.foo.com/12345</TT
->,
-	  Bugzilla spits back
-	  http://www.foo.com/show_bug.cgi?id=12345. Try setting up
-	  your VirtualHost section for Bugzilla with a rule like
-	  this:</P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->&#13;
-&#60;VirtualHost 12.34.56.78&#62;
-RewriteEngine On
-RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R]
-&#60;/VirtualHost&#62;
-
-	</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
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="patches.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="setperl.html"
-ACCESSKEY="N"
->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"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->The setperl.csh Utility</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/rhbugzilla.html

@@ -1,157 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Red Hat Bugzilla</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><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="Bugzilla Variants and Competitors"
-HREF="variants.html"><LINK
-REL="NEXT"
-TITLE="Loki Bugzilla (Fenris)"
-HREF="variant-fenris.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="variants.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 6. Bugzilla Variants and Competitors</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="variant-fenris.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="rhbugzilla">6.1. Red Hat Bugzilla</H1
-><P
->&#13;      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"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="variants.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="variant-fenris.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Bugzilla Variants and Competitors</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="variants.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Loki Bugzilla (Fenris)</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/scm.html

@@ -1,166 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Perforce SCM</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Integrating Bugzilla with Third-Party Tools"
-HREF="integration.html"><LINK
-REL="PREVIOUS"
-TITLE="CVS"
-HREF="cvs.html"><LINK
-REL="NEXT"
-TITLE="Tinderbox/Tinderbox2"
-HREF="tinderbox.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="cvs.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 5. Integrating Bugzilla with Third-Party Tools</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="tinderbox.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="scm">5.3. Perforce SCM</H1
-><P
->&#13;      You can find the project page for Bugzilla and Teamtrack
-      Perforce integration (p4dti) at: <A
-HREF="http://www.ravenbrook.com/project/p4dti/"
-TARGET="_top"
-> http://www.ravenbrook.com/project/p4dti</A
-> .  <SPAN
-CLASS="QUOTE"
->"p4dti"</SPAN
-> is now an officially supported product from Perforce, and you can find the "Perforce Public Depot" p4dti page at <A
-HREF="http://public.perforce.com/public/perforce/p4dti/index.html"
-TARGET="_top"
-> http://public.perforce.com/public/perforce/p4dti/index.html</A
->.
-    </P
-><P
->&#13;      Integration of Perforce with Bugzilla, once patches are applied,
-      is seamless.  Perforce replication information will appear below
-      the comments of each bug.  Be certain you have a matching set of
-      patches for the Bugzilla version you are installing.  p4dti is
-      designed to support multiple defect trackers, and maintains its
-      own documentation for it. Please consult the pages linked above
-      for further information.
-    </P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="cvs.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="tinderbox.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->CVS</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="integration.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Tinderbox/Tinderbox2</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/security.html

@@ -1,478 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Bugzilla Security</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Administering Bugzilla"
-HREF="administration.html"><LINK
-REL="PREVIOUS"
-TITLE="Product, Component, Milestone, and Version
-      Administration"
-HREF="programadmin.html"><LINK
-REL="NEXT"
-TITLE="Integrating Bugzilla with Third-Party Tools"
-HREF="integration.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="programadmin.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 4. Administering Bugzilla</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="integration.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="security">4.4. Bugzilla Security</H1
-><TABLE
-BORDER="0"
-WIDTH="100%"
-CELLSPACING="0"
-CELLPADDING="0"
-CLASS="EPIGRAPH"
-><TR
-><TD
-WIDTH="45%"
->&nbsp;</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
-></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
->&#13;	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
->&#13;      Secure your installation.
-      <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
->&#13;	  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
->&#13;	    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
->&#13;	    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
->&#13;	    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
->&#13;	    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="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
->&#13;		<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
->&#13;	    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="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
->&#13;	      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
->&#13;	      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
->&#13;        When you run checksetup.pl, the script will attempt to modify various
-        permissions on files which Bugzilla uses. If you do not have a
-        webservergroup set in the localconfig file, then Bugzilla will have to
-        make certain files world readable and/or writable. <EM
->THIS IS
-        INSECURE!</EM
->. This means that anyone who can get access to
-        your system can do whatever they want to your Bugzilla installation.
-      </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
->&#13;          This also means that if your webserver runs all cgi scripts as the
-          same user/group, anyone on the system who can run cgi scripts will
-          be able to take control of your Bugzilla installation.
-        </P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->&#13;	    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
->&#13;	    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
->&#13;	    Place the following text into a file named ".htaccess",
-	    readable by your web server, in your $BUGZILLA_HOME/data
-	    directory. <P
-CLASS="literallayout"
->&nbsp;&#60;Files&nbsp;comments&#62;&nbsp;allow<br>
-	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;from&nbsp;all&nbsp;&#60;/Files&#62;&nbsp;deny&nbsp;from&nbsp;all&nbsp;</P
->
-	  </P
-><P
->&#13;	    Place the following text into a file named ".htaccess",
-	    readable by your web server, in your $BUGZILLA_HOME/
-	    directory. <P
-CLASS="literallayout"
->&nbsp;&#60;Files&nbsp;localconfig&#62;&nbsp;deny<br>
-	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;from&nbsp;all&nbsp;&#60;/Files&#62;&nbsp;allow&nbsp;from&nbsp;all&nbsp;</P
->
-	  </P
-><P
->&#13;	    Place the following text into a file named ".htaccess",
-	    readable by your web server, in your $BUGZILLA_HOME/shadow
-	    directory. <P
-CLASS="literallayout"
->&nbsp;deny&nbsp;from&nbsp;all&nbsp;</P
->
-	  </P
-></LI
-></OL
->
-    </P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="programadmin.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="integration.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Product, Component, Milestone, and Version
-      Administration</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="administration.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Integrating Bugzilla with Third-Party Tools</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/setperl.html

@@ -1,312 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->The setperl.csh Utility</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><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="Apache mod_rewrite magic"
-HREF="rewrite.html"><LINK
-REL="NEXT"
-TITLE="Command-line Bugzilla Queries"
-HREF="cmdline.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="rewrite.html"
-ACCESSKEY="P"
->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="cmdline.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="setperl">D.2. The setperl.csh Utility</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!
-    </P
-><DIV
-CLASS="procedure"
-><OL
-TYPE="1"
-><LI
-><P
->&#13;	  Download the "setperl.csh" utility to your Bugzilla
-	  directory and make it executable.
-	</P
-><OL
-CLASS="SUBSTEPS"
-TYPE="a"
-><LI
-><P
->&#13;	      <TT
-CLASS="computeroutput"
->&#13;		<TT
-CLASS="prompt"
->bash#</TT
->
-		<B
-CLASS="command"
->cd /your/path/to/bugzilla</B
->
-	      </TT
->
-	    </P
-></LI
-><LI
-><P
->&#13;	      <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->bash#</TT
-> <B
-CLASS="command"
->wget -O
-		  setperl.csh
-		  'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'</B
-> </TT
->
-	    </P
-></LI
-><LI
-><P
->&#13;	      <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->bash#</TT
-> <B
-CLASS="command"
->chmod
-		  u+x setperl.csh</B
-> </TT
->
-	    </P
-></LI
-></OL
-></LI
-><LI
-><P
->&#13;	  Prepare (and fix) Bugzilla file permissions.
-	</P
-><OL
-CLASS="SUBSTEPS"
-TYPE="a"
-><LI
-><P
->&#13;	      <TT
-CLASS="computeroutput"
->&#13;		<TT
-CLASS="prompt"
->bash#</TT
->
-		<B
-CLASS="command"
->chmod u+w *</B
->
-	      </TT
->
-	    </P
-></LI
-><LI
-><P
->&#13;	      <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->bash#</TT
-> <B
-CLASS="command"
->chmod
-		  u+x duplicates.cgi</B
-> </TT
->
-	    </P
-></LI
-><LI
-><P
->&#13;	      <TT
-CLASS="computeroutput"
->&#13;		<TT
-CLASS="prompt"
->bash#</TT
->
-		<B
-CLASS="command"
->chmod a-x bug_status.html</B
->
-	      </TT
->
-	    </P
-></LI
-></OL
-></LI
-><LI
-><P
->&#13;	  Run the script:
-	</P
-><P
->&#13;	  <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->bash#</TT
->
-	    <B
-CLASS="command"
->./setperl.csh /your/path/to/perl</B
->
-	  </TT
->
-<DIV
-CLASS="example"
-><A
-NAME="AEN2380"><P
-><B
->Example D-1. Using Setperl to set your perl path</B
-></P
-><P
->&#13;	      <TT
-CLASS="computeroutput"
-> <TT
-CLASS="prompt"
->bash#</TT
->
-		<B
-CLASS="command"
->./setperl.csh /usr/bin/perl</B
->
-	      </TT
->
-            </P
-></DIV
->
-	</P
-></LI
-></OL
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="rewrite.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="cmdline.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Apache <TT
-CLASS="filename"
->mod_rewrite</TT
-> magic</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="patches.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Command-line Bugzilla Queries</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/tinderbox.html

@@ -1,144 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Tinderbox/Tinderbox2</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Integrating Bugzilla with Third-Party Tools"
-HREF="integration.html"><LINK
-REL="PREVIOUS"
-TITLE="Perforce SCM"
-HREF="scm.html"><LINK
-REL="NEXT"
-TITLE="Bugzilla Variants and Competitors"
-HREF="variants.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="scm.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 5. Integrating Bugzilla with Third-Party Tools</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="variants.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="tinderbox">5.4. Tinderbox/Tinderbox2</H1
-><P
->We need Tinderbox integration information.</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="scm.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="variants.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Perforce SCM</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="integration.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Bugzilla Variants and Competitors</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/translations.html

@@ -1,156 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Translations</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="About This Guide"
-HREF="about.html"><LINK
-REL="PREVIOUS"
-TITLE="Credits"
-HREF="credits.html"><LINK
-REL="NEXT"
-TITLE="Document Conventions"
-HREF="conventions.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="credits.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 1. About This Guide</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="conventions.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="translations">1.6. Translations</H1
-><P
->&#13;      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"
->&#60;<A
-HREF="mailto:mozilla-webtools@mozilla.org"
->mozilla-webtools@mozilla.org</A
->&#62;</TT
->, and arrange with
-      The Bugzilla Team to check it into CVS.
-    </P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="credits.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="conventions.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Credits</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="about.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Document Conventions</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/useradmin.html

@@ -1,707 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->User Administration</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Administering Bugzilla"
-HREF="administration.html"><LINK
-REL="PREVIOUS"
-TITLE="Post-Installation Checklist"
-HREF="postinstall-check.html"><LINK
-REL="NEXT"
-TITLE="Product, Component, Milestone, and Version
-      Administration"
-HREF="programadmin.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="postinstall-check.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 4. Administering Bugzilla</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="programadmin.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="useradmin">4.2. User Administration</H1
-><P
->&#13;      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"
-><H2
-CLASS="section"
-><A
-NAME="defaultuser">4.2.1. Creating the Default User</H2
-><P
->&#13;	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"
-><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
->&#13;       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&#62;" denotes the  mysql prompt, not
-	  something you should type in):
-	  <B
-CLASS="command"
-><TT
-CLASS="prompt"
->mysql&#62;</TT
-> use bugs;</B
->
-	  <B
-CLASS="command"
-><TT
-CLASS="prompt"
->mysql&#62;</TT
-> update profiles set
-	    groupset=0x7ffffffffffffff where login_name = "(user's
-	    login name)"; </B
->
-	</P
-><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
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="manageusers">4.2.2. Managing Other Users</H2
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="login">4.2.2.1. Logging In</H3
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->&#13;	      Open the index.html page for your Bugzilla installation
-	      in your browser window.
-	    </P
-></LI
-><LI
-><P
->&#13;	      Click the "Query Existing Bug Reports" link.
-	    </P
-></LI
-><LI
-><P
->&#13;	      Click the "Log In" link at the foot of the page.
-	    </P
-></LI
-><LI
-><P
->&#13;	      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
->Congratulations, you are logged in!</P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="createnewusers">4.2.2.2. Creating new users</H3
-><P
->&#13;	  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
-><OL
-TYPE="1"
-><LI
-><P
->&#13;	      After logging in, click the "Users" link at the footer
-	      of the query page.
-	    </P
-></LI
-><LI
-><P
->&#13;	      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"
-><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
->&#13;		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
->&#13;	      Click the "Add New User" link at the bottom of the user
-	      list
-	    </P
-></LI
-><LI
-><P
->&#13;	      Fill out the form presented.  This page is
-	      self-explanatory.  When done, click "submit".
-	    </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
->&#13;		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
-></OL
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="disableusers">4.2.2.3. Disabling Users</H3
-><P
->&#13;	  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"
-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
->&#13;	      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
->
-	</P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="modifyusers">4.2.2.4. Modifying Users</H3
-><P
->&#13;	  Here I will attempt to describe the function of each option
-	  on the Edit User screen.
-	</P
-><P
-></P
-><UL
-><LI
-><P
->&#13;	      <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
-></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
->&#13;		  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
->&#13;	      <EM
->Real Name</EM
->: Duh!
-	    </P
-></LI
-><LI
-><P
->&#13;	      <EM
->Password</EM
->:  You can change the user
-	      password here.  It is normal to only see asterisks.
-	    </P
-></LI
-><LI
-><P
->&#13;	      <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="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
->Don't disable the administrator account!</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
->&#13;		  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
->&#13;	      <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
->&#13;	      <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
->&#13;	      <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
-></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
->&#13;		  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
->&#13;	      <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
->&#13;	      <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
->&#13;	      <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 privileges from other users or grant them
-	      to themselves.  Enable with care.
-	    </P
-></LI
-><LI
-><P
->&#13;	      <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
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="postinstall-check.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="programadmin.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Post-Installation Checklist</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="administration.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Product, Component, Milestone, and Version
-      Administration</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/using.html

@@ -1,244 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Using Bugzilla</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="PREVIOUS"
-TITLE="Document Conventions"
-HREF="conventions.html"><LINK
-REL="NEXT"
-TITLE="What is Bugzilla?"
-HREF="whatis.html"></HEAD
-><BODY
-CLASS="chapter"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="conventions.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="whatis.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="chapter"
-><H1
-><A
-NAME="using">Chapter 2. Using Bugzilla</H1
-><TABLE
-BORDER="0"
-WIDTH="100%"
-CELLSPACING="0"
-CELLPADDING="0"
-CLASS="EPIGRAPH"
-><TR
-><TD
-WIDTH="45%"
->&nbsp;</TD
-><TD
-WIDTH="45%"
-ALIGN="LEFT"
-VALIGN="TOP"
-><I
-><P
-><I
->What, Why, How, &#38; Where?</I
-></P
-></I
-></TD
-></TR
-></TABLE
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->2.1. <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#bug_page"
->Anatomy of a Bug</A
-></DT
-><DT
->2.3.3. <A
-HREF="how.html#query"
->Searching for Bugs</A
-></DT
-><DT
->2.3.4. <A
-HREF="how.html#list"
->Bug Lists</A
-></DT
-><DT
->2.3.5. <A
-HREF="how.html#bugreports"
->Filing Bugs</A
-></DT
-></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
-><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
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="conventions.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="whatis.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Document Conventions</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
->&nbsp;</TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->What is Bugzilla?</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/usingbz-conc.html

@@ -1,152 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Using Bugzilla-Conclusion</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Using Bugzilla"
-HREF="using.html"><LINK
-REL="PREVIOUS"
-TITLE="Where can I find my user preferences?"
-HREF="init4me.html"><LINK
-REL="NEXT"
-TITLE="Installation"
-HREF="installation.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="init4me.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 2. Using Bugzilla</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="installation.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="usingbz-conc">2.5. Using Bugzilla-Conclusion</H1
-><P
->&#13;      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
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="init4me.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="installation.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Where can I find my user preferences?</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="using.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Installation</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/variant-fenris.html

@@ -1,148 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Loki Bugzilla (Fenris)</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><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
-SUMMARY="Header navigation 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"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 6. Bugzilla Variants and Competitors</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="variant-issuezilla.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="variant-fenris">6.2. Loki Bugzilla (Fenris)</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
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="rhbugzilla.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="variant-issuezilla.html"
-ACCESSKEY="N"
->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"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Issuezilla</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/variant-issuezilla.html

@@ -1,159 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Issuezilla</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><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
-SUMMARY="Header navigation 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"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 6. Bugzilla Variants and Competitors</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="variant-scarab.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="variant-issuezilla">6.3. Issuezilla</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
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="variant-fenris.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="variant-scarab.html"
-ACCESSKEY="N"
->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"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Scarab</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/variant-perforce.html

@@ -1,154 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Perforce SCM</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><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
-SUMMARY="Header navigation 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"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 6. Bugzilla Variants and Competitors</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="variant-sourceforge.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="variant-perforce">6.5. Perforce SCM</H1
-><P
->Although Perforce isn't really a bug tracker, it can be used
-      as such through the <SPAN
-CLASS="QUOTE"
->"jobs"</SPAN
-> functionality.</P
-><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
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="variant-scarab.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="variant-sourceforge.html"
-ACCESSKEY="N"
->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"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->SourceForge</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/variant-scarab.html

@@ -1,154 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Scarab</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><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
-SUMMARY="Header navigation 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"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 6. Bugzilla Variants and Competitors</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="variant-perforce.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="variant-scarab">6.4. Scarab</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
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="variant-issuezilla.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="variant-perforce.html"
-ACCESSKEY="N"
->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"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Perforce SCM</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/variant-sourceforge.html

@@ -1,154 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->SourceForge</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><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
-SUMMARY="Header navigation 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"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 6. Bugzilla Variants and Competitors</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="faq.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="variant-sourceforge">6.6. SourceForge</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
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="variant-perforce.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="faq.html"
-ACCESSKEY="N"
->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"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->The Bugzilla FAQ</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/variants.html

@@ -1,182 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Bugzilla Variants and Competitors</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="PREVIOUS"
-TITLE="Tinderbox/Tinderbox2"
-HREF="tinderbox.html"><LINK
-REL="NEXT"
-TITLE="Red Hat Bugzilla"
-HREF="rhbugzilla.html"></HEAD
-><BODY
-CLASS="chapter"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation 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="tinderbox.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="rhbugzilla.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="chapter"
-><H1
-><A
-NAME="variants">Chapter 6. Bugzilla Variants and Competitors</H1
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->6.1. <A
-HREF="rhbugzilla.html"
->Red Hat Bugzilla</A
-></DT
-><DT
->6.2. <A
-HREF="variant-fenris.html"
->Loki Bugzilla (Fenris)</A
-></DT
-><DT
->6.3. <A
-HREF="variant-issuezilla.html"
->Issuezilla</A
-></DT
-><DT
->6.4. <A
-HREF="variant-scarab.html"
->Scarab</A
-></DT
-><DT
->6.5. <A
-HREF="variant-perforce.html"
->Perforce SCM</A
-></DT
-><DT
->6.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"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="tinderbox.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="rhbugzilla.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Tinderbox/Tinderbox2</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
->&nbsp;</TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Red Hat Bugzilla</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/whatis.html

@@ -1,213 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->What is Bugzilla?</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Using Bugzilla"
-HREF="using.html"><LINK
-REL="PREVIOUS"
-TITLE="Using Bugzilla"
-HREF="using.html"><LINK
-REL="NEXT"
-TITLE="Why Should We Use Bugzilla?"
-HREF="why.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="using.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 2. Using Bugzilla</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="why.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="whatis">2.1. What is Bugzilla?</H1
-><P
->&#13;      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 by
-Netscape Communications.  Terry later ported Bugzilla to Perl from
-TCL, and in Perl it remains to this day. Most commercial
-defect-tracking software vendors at the time charged enormous
-licensing fees, and Bugzilla quickly became a favorite of the
-open-source crowd (with its genesis in the open-source browser
-project, Mozilla).  It is now the de-facto standard defect-tracking
-system against which all others are measured.
-    </P
-><P
->&#13;      Bugzilla has matured immensely, and now boasts many advanced features.  These include:
-      <P
-></P
-><UL
-><LI
-><P
->Powerful searching</P
-></LI
-><LI
-><P
->User-configurable email notifications of bug changes</P
-></LI
-><LI
-><P
->Full change history</P
-></LI
-><LI
-><P
->Inter-bug dependency tracking and graphing</P
-></LI
-><LI
-><P
->Excellent attachment management</P
-></LI
-><LI
-><P
->Integrated, product-based, granular security schema</P
-></LI
-><LI
-><P
->Fully security-audited, and runs under Perl's taint mode</P
-></LI
-><LI
-><P
->A robust, stable RDBMS back-end</P
-></LI
-><LI
-><P
->Web, XML, email and console interfaces</P
-></LI
-><LI
-><P
->Completely customisable and/or localisable web user interface</P
-></LI
-><LI
-><P
->Extensive configurability</P
-></LI
-><LI
-><P
->Smooth upgrade pathway between versions</P
-></LI
-></UL
->
-    </P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="using.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="why.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Using Bugzilla</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="using.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Why Should We Use Bugzilla?</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/html/why.html

@@ -1,222 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Why Should We Use Bugzilla?</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Using Bugzilla"
-HREF="using.html"><LINK
-REL="PREVIOUS"
-TITLE="What is Bugzilla?"
-HREF="whatis.html"><LINK
-REL="NEXT"
-TITLE="How do I use Bugzilla?"
-HREF="how.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="whatis.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 2. Using Bugzilla</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="how.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="why">2.2. Why Should We Use Bugzilla?</H1
-><TABLE
-BORDER="0"
-WIDTH="100%"
-CELLSPACING="0"
-CELLPADDING="0"
-CLASS="EPIGRAPH"
-><TR
-><TD
-WIDTH="45%"
->&nbsp;</TD
-><TD
-WIDTH="45%"
-ALIGN="LEFT"
-VALIGN="TOP"
-><I
-><P
-><I
->No, Who's on first...</I
-></P
-></I
-></TD
-></TR
-></TABLE
-><P
->&#13;      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
->&#13;      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
->&#13;      But why should <EM
->you</EM
-> use Bugzilla?
-    </P
-><P
->&#13;      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
->&#13;      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
->&#13;      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="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="whatis.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="how.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->What is Bugzilla?</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="using.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->How do I use Bugzilla?</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->

mozilla/webtools/bugzilla/docs/makedocs.pl

@@ -0,0 +1,107 @@
+#!/usr/bin/perl -w
+# -*- Mode: perl; indent-tabs-mode: nil -*-
+#
+# The contents of this file are subject to the Mozilla Public
+# License Version 1.1 (the "License"); you may not use this file
+# except in compliance with the License. You may obtain a copy of
+# the License at http://www.mozilla.org/MPL/
+#
+# Software distributed under the License is distributed on an "AS
+# IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or
+# implied. See the License for the specific language governing
+# rights and limitations under the License.
+#
+# The Original Code is the Bugzilla Bug Tracking System.
+#
+# The Initial Developer of the Original Code is Netscape Communications
+# Corporation. Portions created by Netscape are
+# Copyright (C) 1998 Netscape Communications Corporation. All
+# Rights Reserved.
+#
+# Contributor(s): Matthew Tuck <matty@chariot.net.au>
+#                 Jacob Steenhagen <jake@bugzilla.org>
+
+# This script compiles all the documentation.
+
+use diagnostics;
+use strict;
+
+use File::Basename;
+
+###############################################################################
+# Environment Variable Checking
+###############################################################################
+
+my ($JADE_PUB, $LDP_HOME);
+
+if (defined $ENV{JADE_PUB} && $ENV{JADE_PUB} ne '') {
+    $JADE_PUB = $ENV{JADE_PUB};
+}
+else {
+    die "You need to set the JADE_PUB environment variable first.";
+}
+
+if (defined $ENV{LDP_HOME} && $ENV{LDP_HOME} ne '') {
+    $LDP_HOME = $ENV{LDP_HOME};
+}
+else {
+    die "You need to set the LDP_HOME environment variable first.";
+}
+
+###############################################################################
+# Subs
+###############################################################################
+
+sub MakeDocs($$) {
+
+    my ($name, $cmdline) = @_;
+
+    print "Creating $name documentation ...\n" if defined $name;
+    print "$cmdline\n\n";
+    system $cmdline;
+    print "\n";
+
+}
+
+###############################################################################
+# Make the docs ...
+###############################################################################
+
+chdir dirname($0);
+
+if (!-d 'html') {
+    unlink 'html';
+    mkdir 'html', 0755;
+}
+if (!-d 'txt') {
+    unlink 'txt';
+    mkdir 'txt', 0755;
+}
+if (!-d 'pdf') {
+    unlink 'pdf';
+    mkdir 'pdf', 0755;
+}
+
+chdir 'html';
+
+MakeDocs('separate HTML', "jade -t sgml -i html -d $LDP_HOME/ldp.dsl\#html " .
+	 "$JADE_PUB/xml.dcl ../xml/Bugzilla-Guide.xml");
+MakeDocs('big HTML', "jade -V nochunks -t sgml -i html -d " .
+         "$LDP_HOME/ldp.dsl\#html $JADE_PUB/xml.dcl " .
+	 "../xml/Bugzilla-Guide.xml > Bugzilla-Guide.html");
+MakeDocs('big text', "lynx -dump -justify=off -nolist Bugzilla-Guide.html " .
+	 "> ../txt/Bugzilla-Guide.txt");
+
+if (! grep("--with-pdf", @ARGV)) {
+    exit;
+}
+
+MakeDocs('PDF', "jade -t tex -d $LDP_HOME/ldp.dsl\#print $JADE_PUB/xml.dcl " .
+         '../xml/Bugzilla-Guide.xml');
+chdir '../pdf';
+MakeDocs(undef, 'mv ../xml/Bugzilla-Guide.tex .');
+MakeDocs(undef, 'pdfjadetex Bugzilla-Guide.tex');
+MakeDocs(undef, 'pdfjadetex Bugzilla-Guide.tex');
+MakeDocs(undef, 'pdfjadetex Bugzilla-Guide.tex');
+MakeDocs(undef, 'rm Bugzilla-Guide.tex Bugzilla-Guide.log Bugzilla-Guide.aux Bugzilla-Guide.out');
+

mozilla/webtools/bugzilla/docs/sgml/about.sgml

@@ -1,224 +0,0 @@
-<!-- <!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>
-      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>
-  </section>
-
-  <section id="copyright">
-    <title>Copyright Information</title>
-    <blockquote>
-      <attribution>Copyright (c) 2000-2002 Matthew P. Barnson and &bzg-auth;</attribution>
-      <para>
-	Permission is granted to copy, distribute and/or modify this
-	document under the terms of the GNU Free Documentation
-	License, Version 1.1 or any later version published  by the
-	Free Software Foundation; with no Invariant Sections, no
-	Front-Cover Texts, and  with no Back-Cover Texts.  A copy of
-	the license is included 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.
-    </para>
-    <para>
-      Naming of particular products or brands should not be seen as
-      endorsements, with the exception of the term "GNU/Linux".  We
-      wholeheartedly endorse the use of GNU/Linux in every situation
-      where it is appropriate.  It is an extremely versatile, stable,
-      and robust operating system that offers an ideal operating
-      environment for Bugzilla.
-    </para>
-    <para>
-      You are strongly recommended to make a backup of your system
-      before installing Bugzilla and at regular intervals thereafter.
-      If you implement any suggestion in this Guide, implement this one!
-    </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 &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.bugzilla.org/">bugzilla.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 <filename>mozilla/webtools/bugzilla/docs/</filename> 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://mbarnson@sisna.com">Matthew P. Barnson</ulink>
-      for pulling together the Bugzilla Guide and shepherding it to 2.14.
-    </para>
-    <para>
-      <ulink url="mailto://terry@mozilla.org">Terry Weissman</ulink>
-      for initially writing Bugzilla and creating the
-      README upon which the UNIX installation documentation is largely based.
-    </para>
-    <para>
-      <ulink url="mailto://tara@tequilarista.org">Tara
-	Hernandez</ulink>  for keeping Bugzilla development going
-      strong after Terry left Mozilla.org
-    </para>
-    <para>
-      <ulink url="mailto://dkl@redhat.com">Dave Lawrence</ulink> for
-      providing insight into the key differences between Red Hat's
-      customized Bugzilla, and being largely responsible for the "Red
-      Hat Bugzilla" appendix
-    </para>
-    <para>
-      <ulink url="mailto://endico@mozilla.org">Dawn Endico</ulink> for
-      being a hacker extraordinaire and putting up with my incessant
-      questions and arguments on irc.mozilla.org in #mozwebtools
-    </para>
-    <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>
-    <para>
-      Thanks also go to the following people for significant contributions 
-      to this documentation (in no particular order):
-    </para>
-    <para>
-      Zach Liption, Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen,
-      Ron Teitelbaum, Jacob Steenhagen, Joe Robins.
-    </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
-      &bzg-auth; to check it into CVS.
-    </para>
-  </section>
-
-  <!-- conventions used here (didn't want to give it a chapter of its own) -->
-&conventions;
- </chapter> 
-
-<!-- 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: -->

mozilla/webtools/bugzilla/docs/sgml/database.sgml

@@ -1,461 +0,0 @@
-<!-- <!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>
-
-        <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&gt;</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&gt;</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 |
-        +-------------------+ | attachments | | bugs | | bugs_activity | | cc
-        | | components | | dependencies | | fielddefs | | groups | |
-        keyworddefs | | keywords | | logincookies | | longdescs | |
-        milestones | | namedqueries | | products | | profiles | |
-        profiles_activity | | shadowlog | | tokens | | versions | | votes | |
-        watch | +-------------------+</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. attachments: This table stores all
-        attachments to bugs. It tends to be your largest table, yet also
-        generally has the fewest entries because file attachments are so
-        (relatively) large. bugs: This is the core of your system. The bugs
-        table stores most of the current information about a bug, with the
-        exception of the info stored in the other tables. bugs_activity: This
-        stores information regarding what changes are made to bugs when -- a
-        history file. cc: This tiny table simply stores all the CC
-        information for any bug which has any entries in the CC field of the
-        bug. Note that, like most other tables in Bugzilla, it does not refer
-        to users by their user names, but by their unique userid, stored as a
-        primary key in the profiles table. components: This stores the
-        programs and components (or products and components, in newer
-        Bugzilla parlance) for Bugzilla. Curiously, the "program" (product)
-        field is the full name of the product, rather than some other unique
-        identifier, like bug_id and user_id are elsewhere in the database.
-        dependencies: Stores data about those cool dependency trees.
-        fielddefs: A nifty table that defines other tables. For instance,
-        when you submit a form that changes the value of "AssignedTo" this
-        table allows translation to the actual field name "assigned_to" for
-        entry into MySQL. groups: defines bitmasks for groups. A bitmask is a
-        number that can uniquely identify group memberships. For instance,
-        say the group that is allowed to tweak parameters is assigned a value
-        of "1", the group that is allowed to edit users is assigned a "2",
-        and the group that is allowed to create new groups is assigned the
-        bitmask of "4". By uniquely combining the group bitmasks (much like
-        the chmod command in UNIX,) you can identify a user is allowed to
-        tweak parameters and create groups, but not edit users, by giving him
-        a bitmask of "5", or a user allowed to edit users and create groups,
-        but not tweak parameters, by giving him a bitmask of "6" Simple, huh?
-        If this makes no sense to you, try this at the mysql prompt:
-        mysql&gt; select * from groups; You'll see the list, it makes much
-        more sense that way. keyworddefs: Definitions of keywords to be used
-        keywords: Unlike what you'd think, this table holds which keywords
-        are associated with which bug id's. logincookies: This stores every
-        login cookie ever assigned to you for every machine you've ever
-        logged into Bugzilla from. Curiously, it never does any housecleaning
-        -- I see cookies in this file I've not used for months. However,
-        since Bugzilla never expires your cookie (for convenience' sake), it
-        makes sense. longdescs: The meat of bugzilla -- here is where all
-        user comments are stored! You've only got 2^24 bytes per comment
-        (it's a mediumtext field), so speak sparingly -- that's only the
-        amount of space the Old Testament from the Bible would take
-        (uncompressed, 16 megabytes). Each comment is keyed to the bug_id to
-        which it's attached, so the order is necessarily chronological, for
-        comments are played back in the order in which they are received.
-        milestones: Interesting that milestones are associated with a
-        specific product in this table, but Bugzilla does not yet support
-        differing milestones by product through the standard configuration
-        interfaces. namedqueries: This is where everybody stores their
-        "custom queries". Very cool feature; it beats the tar out of having
-        to bookmark each cool query you construct. products: What products
-        you have, whether new bug entries are allowed for the product, what
-        milestone you're working toward on that product, votes, etc. It will
-        be nice when the components table supports these same features, so
-        you could close a particular component for bug entry without having
-        to close an entire product... profiles: Ahh, so you were wondering
-        where your precious user information was stored? Here it is! With the
-        passwords in plain text for all to see! (but sshh... don't tell your
-        users!) profiles_activity: Need to know who did what when to who's
-        profile? This'll tell you, it's a pretty complete history. shadowlog:
-        I could be mistaken here, but I believe this table tells you when
-        your shadow database is updated and what commands were used to update
-        it. We don't use a shadow database at our site yet, so it's pretty
-        empty for us. versions: Version information for every product votes:
-        Who voted for what when watch: Who (according to userid) is watching
-        who's bugs (according to their userid). === THE DETAILS === Ahh, so
-        you're wondering just what to do with the information above? At the
-        mysql prompt, you can view any information about the columns in a
-        table with this command (where "table" is the name of the table you
-        wish to view): mysql&gt; show columns from table; You can also view
-        all the data in a table with this command: mysql&gt; select * from
-        table; -- note: this is a very bad idea to do on, for instance, the
-        "bugs" table if you have 50,000 bugs. You'll be sitting there a while
-        until you ctrl-c or 50,000 bugs play across your screen. You can
-        limit the display from above a little with the command, where
-        "column" is the name of the column for which you wish to restrict
-        information: mysql&gt; select * from table where (column = "some
-        info"); -- or the reverse of this mysql&gt; select * from table where
-        (column != "some info"); Let's take our example from the
-        introduction, and assume you need to change the word "verified" to
-        "approved" in the resolution field. We know from the above
-        information that the resolution is likely to be stored in the "bugs"
-        table. Note we'll need to change a little perl code as well as this
-        database change, but I won't plunge into that in this document. Let's
-        verify the information is stored in the "bugs" table: mysql&gt; show
-        columns from bugs (exceedingly long output truncated here) |
-        bug_status|
-        enum('UNCONFIRMED','NEW','ASSIGNED','REOPENED','RESOLVED','VERIFIED','CLOSED')||MUL
-        | UNCONFIRMED|| Sorry about that long line. We see from this that the
-        "bug status" column is an "enum field", which is a MySQL peculiarity
-        where a string type field can only have certain types of entries.
-        While I think this is very cool, it's not standard SQL. Anyway, we
-        need to add the possible enum field entry 'APPROVED' by altering the
-        "bugs" table. mysql&gt; ALTER table bugs CHANGE bug_status bug_status
-        -&gt; enum("UNCONFIRMED", "NEW", "ASSIGNED", "REOPENED", "RESOLVED",
-        -&gt; "VERIFIED", "APPROVED", "CLOSED") not null; (note we can take
-        three lines or more -- whatever you put in before the semicolon is
-        evaluated as a single expression) Now if you do this: mysql&gt; show
-        columns from bugs; you'll see that the bug_status field has an extra
-        "APPROVED" enum that's available! Cool thing, too, is that this is
-        reflected on your query page as well -- you can query by the new
-        status. But how's it fit into the existing scheme of things? Looks
-        like you need to go back and look for instances of the word
-        "verified" in the perl code for Bugzilla -- wherever you find
-        "verified", change it to "approved" and you're in business (make sure
-        that's a case-insensitive search). Although you can query by the enum
-        field, you can't give something a status of "APPROVED" until you make
-        the perl changes. Note that this change I mentioned can also be done
-        by editing checksetup.pl, which automates a lot of this. But you need
-        to know this stuff anyway, right? I hope this database tutorial has
-        been useful for you. If you have comments to add, questions,
-        concerns, etc. please direct them to mbarnson@excitehome.net. Please
-        direct flames to /dev/null :) Have a nice day! === LINKS === Great
-        MySQL tutorial site:
-        http://www.devshed.com/Server_Side/MySQL/</literallayout>
-      </section>
-    </section>
-  </section>
-
-  <section id="granttables">
-    <title>MySQL Permissions &amp; 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 To: keystone-users@homeport.org Subject:
-    [keystone-users] Grant Tables FAQ [The following text is in the
-    "iso-8859-1" character set] [Your display is set for the "US-ASCII"
-    character set] [Some characters may be displayed incorrectly] Maybe we
-    can include this rambling message in the Keystone FAQ? It gets asked a
-    lot, and the only option current listed in the FAQ is
-    "--skip-grant-tables". Really, you can't go wrong by reading section 6 of
-    the MySQL manual, at http://www.mysql.com/Manual/manual.html. I am sure
-    their description is better than mine. MySQL runs fine without
-    permissions set up correctly if you run the mysql daemon with the
-    "--skip-grant-tables" option. Running this way denies access to nobody.
-    Unfortunately, unless you've got yourself firewalled it also opens the
-    potential for abuse if someone knows you're running it. Additionally, the
-    default permissions for MySQL allow anyone at localhost access to the
-    database if the database name begins with "test_" or is named "test"
-    (i.e. "test_keystone"). You can change the name of your database in the
-    keystone.conf file ($sys_dbname). This is the way I am doing it for some
-    of my databases, and it works fine. The methods described below assume
-    you're running MySQL on the same box as your webserver, and that you
-    don't mind if your $sys_dbuser for Keystone has superuser access. See
-    near the bottom of this message for a description of what each field
-    does. Method #1: 1. cd /var/lib #location where you'll want to run
-    /usr/bin/mysql_install_db shell script from to get it to work. 2. ln -s
-    mysql data # soft links the "mysql" directory to "data", which is what
-    mysql_install_db expects. Alternately, you can edit mysql_install_db and
-    change all the "./data" references to "./mysql". 3. Edit
-    /usr/bin/mysql_install_db with your favorite text editor (vi, emacs, jot,
-    pico, etc.) A) Copy the "INSERT INTO db VALUES
-    ('%','test\_%','','Y','Y','Y','Y','Y','Y');" and paste it immediately
-    after itself. Chage the 'test\_%' value to 'keystone', or the value of
-    $sys_dbname in keystone.conf. B) If you are running your keystone
-    database with any user, you'll need to copy the "INSERT INTO user VALUES
-    ('localhost','root','','Y','Y','Y','Y','Y','Y','Y','Y','Y','Y');" line
-    after itself and change 'root' to the name of the keystone database user
-    ($sys_dbuser) in keystone.conf. # adds entries to the script to create
-    grant tables for specific hosts and users. The user you set up has
-    super-user access ($sys_dbuser) -- you may or may not want this. The
-    layout of mysql_install_db is really very uncomplicated. 4.
-    /usr/bin/mysqladmin shutdown # ya gotta shut it down before you can
-    reinstall the grant tables! 5. rm -i /var/lib/mysql/mysql/*.IS?' and
-    answer 'Y' to the deletion questions. # nuke your current grant tables.
-    This WILL NOT delete any other databases than your grant tables. 6.
-    /usr/bin/mysql_install_db # run the script you just edited to install
-    your new grant tables. 7. mysqladmin -u root password (new_password) #
-    change the root MySQL password, or else anyone on localhost can login to
-    MySQL as root and make changes. You can skip this step if you want
-    keystone to connect as root with no password. 8. mysqladmin -u
-    (webserver_user_name) password (new_password) # change the password of
-    the $sys_dbuser. Note that you will need to change the password in the
-    keystone.conf file as well in $sys_dbpasswd, and if your permissions are
-    set up incorrectly anybody can type the URL to your keystone.conf file
-    and get the password. Not that this will help them much if your
-    permissions are set to @localhost. Method #2: easier, but a pain
-    reproducing if you have to delete your grant tables. This is the
-    "recommended" method for altering grant tables in MySQL. I don't use it
-    because I like the other way :) shell&gt; mysql --user=root keystone
-    mysql&gt; GRANT
-    SELECT,INSERT,UPDATE,DELETE,INDEX,ALTER,CREATE,DROP,RELOAD,SHUTDOWN,PROCESS,
-    FILE, ON keystone.* TO &lt;$sys_dbuser name&gt;@localhost IDENTIFIED BY
-    '(password)' WITH GRANT OPTION; OR mysql&gt; GRANT ALL PRIVILEGES ON
-    keystone.* TO &lt;$sys_dbuser name&gt;@localhost IDENTIFIED BY
-    '(password)' WITH GRANT OPTION; # this grants the required permissions to
-    the keystone ($sys_dbuser) account defined in keystone.conf. However, if
-    you are runnning many different MySQL-based apps, as we are, it's
-    generally better to edit the mysql_install_db script to be able to
-    quickly reproduce your permissions structure again. Note that the FILE
-    privelege and WITH GRANT OPTION may not be in your best interest to
-    include. GRANT TABLE FIELDS EXPLANATION: Quick syntax summary: "%" in
-    MySQL is a wildcard. I.E., if you are defining your DB table and in the
-    'host' field and enter '%', that means that any host can access that
-    database. Of course, that host must also have a valid db user in order to
-    do anything useful. 'db'=name of database. In our case, it should be
-    "keystone". "user" should be your "$sys_dbuser" defined in keystone.conf.
-    Note that you CANNOT add or change a password by using the "INSERT INTO
-    db (X)" command -- you must change it with the mysql -u command as
-    defined above. Passwords are stored encrypted in the MySQL database, and
-    if you try to enter it directly into the table they will not match.
-    TABLE: USER. Everything after "password" is a privelege granted (Y/N).
-    This table controls individual user global access rights.
-    'host','user','password','select','insert','update','delete','index','alter'
-    ,'create','drop','grant','reload','shutdown','process','file' TABLE: DB.
-    This controls access of USERS to databases.
-    'host','db','user','select','insert','update','delete','index','alter','crea
-    te','drop','grant' TABLE: HOST. This controls which HOSTS are allowed
-    what global access rights. Note that the HOST table, USER table, and DB
-    table are very closely connected -- if an authorized USER attempts an SQL
-    request from an unauthorized HOST, she's denied. If a request from an
-    authorized HOST is not an authorized USER, it is denied. If a globally
-    authorized USER does not have rights to a certain DB, she's denied. Get
-    the picture?
-    'host','db','select','insert','update','delete','index','alter','create','dr
-    op','grant' You should now have a working knowledge of MySQL grant
-    tables. If there is anything I've left out of this answer that you feel
-    is pertinent, or if my instructions don't work for you, please let me
-    know and I'll re-post this letter again, corrected. I threw it together
-    one night out of exasperation for all the newbies who don't know squat
-    about MySQL yet, so it is almost guaranteed to have errors. 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.</literallayout>
-  </section>
-</appendix>
-
-<!-- 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:
--->
-

mozilla/webtools/bugzilla/docs/sgml/patches.sgml

@@ -1,306 +0,0 @@
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
-<appendix id="patches" xreflabel="Useful Patches and Utilities for Bugzilla">
-  <title>Useful Patches and Utilities for Bugzilla</title>
-
-  <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>
-
-    <procedure>
-      <step>
-        <para>Download the "setperl.csh" utility to your Bugzilla directory
-        and make it executable.</para>
-
-        <substeps>
-          <step>
-            <para>
-              <computeroutput>
-                <prompt>bash#</prompt>
-
-                <command>cd /your/path/to/bugzilla</command>
-              </computeroutput>
-            </para>
-          </step>
-
-          <step>
-            <para>
-              <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>
-            </para>
-          </step>
-        </substeps>
-      </step>
-
-      <step>
-        <para>Prepare (and fix) Bugzilla file permissions.</para>
-
-        <substeps>
-          <step>
-            <para>
-              <computeroutput>
-                <prompt>bash#</prompt>
-
-                <command>chmod u+w *</command>
-              </computeroutput>
-            </para>
-          </step>
-
-          <step>
-            <para>
-              <computeroutput>
-                <prompt>bash#</prompt>
-
-                <command>chmod u+x duplicates.cgi</command>
-              </computeroutput>
-            </para>
-          </step>
-
-          <step>
-            <para>
-              <computeroutput>
-                <prompt>bash#</prompt>
-
-                <command>chmod a-x bug_status.html</command>
-              </computeroutput>
-            </para>
-          </step>
-        </substeps>
-      </step>
-
-      <step>
-        <para>Run the script:</para>
-
-        <para>
-          <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>
-            </para>
-          </example>
-        </para>
-      </step>
-    </procedure>
-  </section>
-
-  <section id="cmdline">
-    <title>Command-line Bugzilla Queries</title>
-
-    <para>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"</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=".</para>
-
-    <para>The columlist is taken from the COLUMNLIST environment variable.
-    This is equivalent to the "Change Columns" option when you list bugs in
-    buglist.cgi. If you have already used Bugzilla, use 
-    <command>grep COLUMLIST ~/.netscape/cookies</command>
-
-    to see your current COLUMNLIST setting.</para>
-
-    <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>
-    </para>
-
-    <para>Akkana says she has good results piping buglist output through 
-    <command>w3m -T text/html -dump</command>
-    </para>
-
-    <procedure>
-      <step>
-        <para>Download three files:</para>
-
-        <substeps>
-          <step>
-            <para>
-              <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>
-            </para>
-          </step>
-
-          <step>
-            <para>
-              <computeroutput>
-                <prompt>bash#</prompt>
-
-                <command>wget -O bugs
-                'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26215'</command>
-              </computeroutput>
-            </para>
-          </step>
-        </substeps>
-      </step>
-
-      <step>
-        <para>Make your utilities executable: 
-        <computeroutput>
-          <prompt>bash$</prompt>
-
-          <command>chmod u+x buglist bugs</command>
-        </computeroutput>
-        </para>
-      </step>
-    </procedure>
-  </section>
-
-  <section id="quicksearch">
-    <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"</para>
-
-    <para>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.</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".</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>
-    </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.</para>
-  </section>
-</appendix>
-
-<!-- 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:
--->
-

mozilla/webtools/bugzilla/docs/sgml/requiredsoftware.sgml

@@ -1,88 +0,0 @@
-<!-- <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
-<appendix id="downloadlinks">
-  <title>Software Download Links</title>
-
-  <para>All of these sites are current as of April, 2001. Hopefully they'll
-  stay current for a while.</para>
-
-  <para>Apache Web Server: 
-  <ulink url="http://www.apache.org/">http://www.apache.org</ulink>
-
-  Optional web server for Bugzilla, but recommended because of broad user
-  base and support.</para>
-
-  <para>Bugzilla: 
-  <ulink url="http://www.bugzilla.org/">
-  http://www.bugzilla.org/</ulink>
-  </para>
-
-  <para>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>
-  </para>
-
-  <para>CPAN: 
-  <ulink url="http://www.cpan.org/">http://www.cpan.org/</ulink>
-  </para>
-
-  <para>DBI Perl module: 
-  <ulink url="http://www.cpan.org/modules/by-module/DBI/">
-  http://www.cpan.org/modules/by-module/DBI/</ulink>
-  </para>
-
-  <para>Data::Dumper module: 
-  <ulink url="http://www.cpan.org/modules/by-module/Data/">
-  http://www.cpan.org/modules/by-module/Data/</ulink>
-  </para>
-
-  <para>MySQL related Perl modules: 
-  <ulink url="http://www.cpan.org/modules/by-module/Mysql/">
-  http://www.cpan.org/modules/by-module/Mysql/</ulink>
-  </para>
-
-  <para>TimeDate Perl module collection: 
-  <ulink url="http://www.cpan.org/modules/by-module/Date/">
-  http://www.cpan.org/modules/by-module/Date/</ulink>
-  </para>
-
-  <para>GD Perl module: 
-  <ulink url="http://www.cpan.org/modules/by-module/GD/">
-  http://www.cpan.org/modules/by-module/GD/</ulink>
-
-  Alternately, you should be able to find the latest version of GD at 
-  <ulink url="http://www.boutell.com/gd/">http://www.boutell.com/gd/</ulink>
-  </para>
-
-  <para>Chart::Base module: 
-  <ulink url="http://www.cpan.org/modules/by-module/Chart/">
-  http://www.cpan.org/modules/by-module/Chart/</ulink>
-  </para>
-
-  <para>(But remember, Bundle::Bugzilla will install all the modules for you.)
-  </para>
-</appendix>
-
-<!-- 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:
--->
-