Bugzilla在Win 32 Install 官方文档

60 阅读 0 评论 40 点赞

我是靠谱客的博主小巧牛排，最近开发中收集的这篇文章主要介绍Bugzilla在Win 32 Install 官方文档，觉得挺不错的，现在分享给大家，希望可以做个参考。

概述

Bugzilla:Win32Install
Home » Bugzilla:Win32Install

Content
1 Installing Bugzilla on Microsoft Windows with Apache
1.1 Bugzilla
1.1.1 Installing Bugzilla From CVS
1.1.2 Upgrading From CVS
1.1.3 Installing Bugzilla From the TarBall
1.1.4 Upgrading From TarBall
1.2 MySQL
1.2.1 Download MySQL
1.2.2 Install
1.2.3 Create Bugs Database User
1.3 ActiveState Perl
1.3.1 Download ActiveState Perl 5.8.1 or Higher
1.3.2 Install
1.3.3 Upgrading Existing Installs
1.3.4 Create Temp Directory
1.3.5 Install Modules
1.4 Apache
1.4.1 Download Apache 2.x
1.4.2 Install
1.4.3 Grant write access for Apache account
1.4.4 Configure Port and DocumentRoot
1.4.5 Configure CGI
1.4.6 Disable Logging
1.4.7 Restart Apache
1.5 Extras
1.6 Configure Bugzilla
1.6.1 checksetup.pl
1.6.2 Edit localconfig
1.6.3 checksetup.pl
1.6.4 Parameters
1.7 Scheduled Tasks
1.7.1 collectstats.pl
1.7.2 whineatnews.pl
1.7.3 Backing up Bugzilla
1.7.4 Testing if Bugzilla works
1.7.5 Congratulations, the Bugzilla installation process is complete!
2 Installing Bugzilla on Microsoft Windows with IIS
2.1 Common Problems
2.1.1 Bugzilla runs but I can't log in
2.1.2 IIS returns HTTP 502 errors

If you want a single-package installer that will install Apache, MySQL, Perl, and Bugzilla all at once and configure them all for you, check out the Windows Install Packages.

If you prefer to do everything yourself, the below instructions explain how to manually configure Bugzilla on Windows.
Installing Bugzilla on Microsoft Windows with Apache

Original author: Byron Jones

Bugzilla version 2.18 was the first release that runs unmodified on Windows. This document guides you step by step through the installation process.

Note that there are a few things that don't work very well on Windows, such as mod_perl.
Bugzilla

There's two main methods to getting the Bugzilla source - from CVS or in a tarball. The best method for fetching Bugzilla is to grab it directly from CVS, as this will allow for simple upgrades, even if you have customised Bugzilla.

Read the Release Notes before you do anything.
Installing Bugzilla From CVS

Download the CVSNT client from [1] (2.15 Meg).

Run the installation, you'll only need to install the Command line client and the Password Server (:pserver:) Protocol. Once the install has completed, log out and log in again to pick up the changes to the PATH.

Note: this document assumes you want to install Bugzilla into C:Bugzilla.

Open the command line, and cd to the parent of the directory you want to install Bugzilla into. As we'll be installing Bugzilla into C:Bugzilla, the current directory must be C:.

C:>set CVSROOT=:pserver:anonymous@cvs-mirror.mozilla.org:/cvsroot

C:>cvs login

Logging in to :pserver:anonymous@cvs-mirror.mozilla.org:2401:/cvsroot
CVS password: anonymous

C:>cvs checkout -d Bugzilla -rBugzilla_Stable Bugzilla
cvs checkout: cwd=C: ,current=C:
cvs checkout: Updating Bugzilla
U Bugzilla/.cvsignore
U Bugzilla/Bugzilla.pm
...
U Bugzilla/template/en/default/whine/multipart-mime.txt.tmpl
U Bugzilla/template/en/default/whine/schedule.html.tmpl
cvs checkout: Updating Bugzilla/template/en/extension
U Bugzilla/template/en/extension/filterexceptions.pl
cvs checkout: Updating Bugzilla/template/en/extension/hook

C:>

Upgrading From CVS

If you've already installed an earlier version of Bugzilla from CVS or from a TarBall, updating is easy. Even if you've made customisations, CVS is smart enough to merge. If CVS needs help merging, it displays a C in the first column of its report. You need to resolve such conflicts manually.

C:Bugzilla>cvs update -R -d -rBugzilla_Stable
cvs update: Updating .
P editusers.cgi
cvs update: Updating Bugzilla
P Bugzilla/Bug.pm
P Bugzilla/BugMail.pm
P Bugzilla/Chart.pm
P Bugzilla/Flag.pm
P Bugzilla/User.pm
P Bugzilla/Util.pm
cvs update: Updating Bugzilla/Auth
U Bugzilla/Auth/CGI.pm
cvs update: Updating Bugzilla/Template
cvs update: Updating Bugzilla/Template/Plugin
...
cvs update: Updating template/en/default/search
cvs update: Updating template/en/default/whine
cvs update: Updating template/en/extension

C:Bugzilla>

[color=red]Installing Bugzilla From the TarBall[/color]

Download Bugzilla from [2] (2.4 Meg).

Bugzilla ships as a Tarball, which has the extension[color=red] .tar.gz.[/color] Any decent Windows archive tool should be able to extract tarballs.

Extract the archive to the directory of your choice. For the remainder of this document I will assume that you have extracted Bugzilla into [color=red]C:Bugzilla.[/color]
Upgrading From TarBall

If you installed Bugzilla from the TarBall, the simplest way to upgrade is to follow the CVS Upgrading instructions.
MySQL
Download MySQL

Download the MySQL "Windows Essentials" installer from http://dev.mysql.com/downloads/mysql/4.1.html (14.1 Meg).

[color=red]MySQL 5.x is now stable enough and can be used.[/color]
Install

MySQL has a standard Windows installer. It's ok to select a Typical MySQL install (the default). For the remainder of this document I will assume you have installed MySQL into [color=red]C:mysql.[/color]

Now change a few settings. Goto[color=red] C:mysqlbinmy.ini[/color] and set the [color=red]max_allowed_packet setting to 4M[/color]. Underneath that, add the following line:

[color=red]ft_min_word_len = 2[/color]

Create Bugs Database User

Use the mysql command line utility to create a MySQL account for Bugzilla.

Note in the following example 'sockmonkey' is my password for the bugs account:

[color=red]C:mysqlbin>mysql --user=root -p mysql[/color]

Enter password: ********
Welcome to the MySQL monitor. Commands end with ; or g.
Your MySQL connection id is 15 to server version: 4.0.20a-debug

Type 'help;' or 'h' for help. Type 'c' to clear the buffer.

mysql> [color=red]GRANT ALL PRIVILEGES ON bugs.* TO 'bugs'@'localhost' IDENTIFIED BY 'sockmonkey';[/color]
Query OK, 0 rows affected (0.03 sec)

mysql> quit

Bye

C:mysqlbin>

If you are running MySQL 4.1, you may encounter the Client does not support authentication protocol requested by server error message. To fix this, once the user has been created you will have to reset the password using OLD_PASSWORD:

C:mysqlbin>mysql --user=root -p mysql
Enter password: ********

Welcome to the MySQL monitor. Commands end with ; or g.
Your MySQL connection id is 15 to server version: 4.1.11-nt

Type 'help;' or 'h' for help. Type 'c' to clear the buffer.

mysql> set password for 'bugs'@'localhost' = OLD_PASSWORD('sockmonkey');
Query OK, 0 rows affected (0.00 sec)

mysql> quit

Bye

C:mysqlbin>

ActiveState Perl
[color=red]Download ActiveState Perl 5.8.1 or Higher[/color]

Download the ActiveState Perl 5.8.1 or Higher MSI from: http://www.activestate.com/activeperl/ .

Note that Bugzilla requires ActiveState Perl 5.8.1 as it needs CGI.pm version 2.93 or higher. 5.8.0 ships with CGI.pm version 2.81, 5.8.1 ships with CGI.pm version 3.00.

There is a bug in Time::Local 1.10, which is shipped with ActiveState Perl 5.8.6, that will cause warnings to be generated at the top of every buglist. It's a good idea to avoid version 5.8.6 (version 5.8.4 works without issue).
Install

ActiveState Perl uses a standard Windows Installer. Install, sticking with the defaults, which will install Perl into [color=red]C:Perl.[/color]

Note: Installing Perl into a directory that contains a space (eg "C:Program Files") will break the Template-Toolkit installer.

Once the install has completed, log out and log in again to pick up the changes to the PATH.
Upgrading Existing Installs

If you already have ActiveState Perl installed, now's a good time to ensure you're running the latest version of ActiveState Perl, along with the latest versions of the modules.

To upgrade ActiveState Perl, follow the directions at: http://aspn.activestate.com/ASPN/docs/ActivePerl/install.html

To upgrade your modules, simply run ppm upgrade
Create Temp Directory

On Windows, Perl has a hard time of locating the correct directory to write its temporary files (CGI.pm, File::Spec). Basically it has a list of paths hard coded to use, instead of querying Windows for the correct path.

To avoid problems, create the[color=red] C:Temp[/color] directory (it has to be on drive C) and ensure SYSTEM has write and modify access.
Install Modules

Bugzilla requires a number of perl modules to be installed. They are available in the ActiveState repository and the following additional repositories:
Perl 5.8.x:
http://theoryx5.uwinnipeg.ca/ppms/
[color=red]Perl 5.10.x:
http://cpan.uwinnipeg.ca/PPMPackages/10xx/ and
http://trouchelle.com/ppm10/[/color]

If you use a proxy server or a firewall you may have trouble running PPM. This is covered in the ActivePerl FAQ.

The Net::LDAP module is only required if you want to use Active Directory for authentication.

The following are the commands and ouput for a 5.10.x perl module installation:

C:>[color=red]ppm version[/color]
ppm 4.06 (ActivePerl 1006)
Copyright (C) 2009 ActiveState Software Inc. All rights reserved.

C:>[color=red]ppm repo add UWinnipeg http://cpan.uwinnipeg.ca/PPMPackages/10xx/[/color]
Downloading ActiveState Package Repository packlist...done
Updating ActiveState Package Repository database...done
Downloading UWinnipeg packlist...done
Updating UWinnipeg database...done
Repo 2 added.

C:>[color=red]ppm repo add Trouchelle http://trouchelle.com/ppm10/[/color]
Downloading Trouchelle packlist...done
Updating Trouchelle database...done
Repo 3 added.

C:>[color=red]ppm repo list[/color]
+---------------------------------------------+
¦ id ¦ pkgs ¦ name ¦
+----+-------+--------------------------------¦
¦ 1 ¦ 11417 ¦ ActiveState Package Repository ¦
¦ 2 ¦ 291 ¦ UWinnipeg ¦
¦ 3 ¦ 11737 ¦ Trouchelle ¦
+---------------------------------------------+
(3 enabled repositories)

C:>[color=red]ppm upgrade[/color]
Syncing site PPM database with .packlists...done
Archive-Tar 1.54 (have 1.52-r1)
Attribute-Handlers 0.87 (have 0.86)
AutoLoader 5.70 (have 5.69)
Bit-Vector 7.1 (have 6.9)
Class-Accessor 0.34 (have 0.33)
Class-ISA 0.36 (have 0.33)
Compress-Raw-Bzip2 2.021 (have 2.020)
Compress-Raw-Zlib 2.021 (have 2.020)
DBD-ODBC 1.23 (have 1.22)
DBI 1.609 (have 1.607)
Date-Calc 5.8 (have 5.6)
Encode 2.37 (have 2.35)
ExtUtils-CBuilder 0.260301 (have 0.2603)
ExtUtils-Manifest 1.57 (have 1.56)
ExtUtils-ParseXS 2.21 (have 2.2002)
File-Path 2.08 (have 2.07_03)
File-Which 1.09 (have 1.07)
IO-Compress 2.021 (have 2.020)
IPC-Cmd 0.50 (have 0.46)
Log-Message-Simple 0.06 (have 0.04)
Math-BigRat 0.24 (have 0.22)
Module-CoreList 2.20 (have 2.17)
Module-Loaded 0.06 (have 0.02)
Object-Accessor 0.36 (have 0.34)
Safe 2.19 (have 2.17)
Test-Simple 0.94 (have 0.92)
Text-CSV_XS 0.68 (have 0.67)
Text-Reform 1.20 (have 1.11)
constant 1.19 (have 1.18)
parent 0.223 (have 0.221)
version 0.7702 (have 0.7701)

C:>[color=red]ppm install AppConfig[/color]
Downloading AppConfig-1.66...done
Unpacking AppConfig-1.66...done
Generating HTML for AppConfig-1.66...done
Updating files in site area...done
14 files installed

C:>[color=red]ppm install TimeDate[/color]
Downloading TimeDate-1.19...done
Unpacking TimeDate-1.19...done
Generating HTML for TimeDate-1.19...done
Updating files in site area...done
41 files installed

C:>[color=red]ppm install DBI[/color]
No missing packages to install

C:>[color=red]ppm install DBD-mysql[/color]
Downloading DBD-mysql-4.011...done
Unpacking DBD-mysql-4.011...done
Generating HTML for DBD-mysql-4.011...done
Updating files in site area...done
12 files installed

C:[color=red]>ppm install Template-Toolkit[/color]
Downloading Template-Toolkit-2.22...done
Unpacking Template-Toolkit-2.22...done
Generating HTML for Template-Toolkit-2.22...done
Updating files in site area...done
140 files installed

C:>[color=red]ppm install MailTools[/color]
Downloading MailTools-2.04...done
Downloading Test-Pod-1.40...done
Unpacking MailTools-2.04...done
Unpacking Test-Pod-1.40...done
Generating HTML for MailTools-2.04...done
Generating HTML for Test-Pod-1.40...done
Updating files in site area...done
43 files installed

C:>[color=red]ppm install GD[/color]
No missing packages to install

C:>[color=red]ppm install Chart[/color]
Downloading Chart-2.4.1...done
Unpacking Chart-2.4.1...done
Generating HTML for Chart-2.4.1...done
Updating files in site area...done
16 files installed

C:>[color=red]ppm install GDGraph[/color]
Downloading GDGraph-1.44...done
Unpacking GDGraph-1.44...done
Generating HTML for GDGraph-1.44...done
Updating files in site area...done
21 files installed

C:>[color=red]ppm install PatchReader[/color]
Downloading PatchReader-0.9.5...done
Unpacking PatchReader-0.9.5...done
Generating HTML for PatchReader-0.9.5...done
Updating files in site area...done
12 files installed

C:>[color=red]ppm install Net-LDAP-Express[/color]
Downloading Net-LDAP-Express-0.11...done
Downloading perl-ldap-0.39...done
Downloading Convert-ASN1-0.22...done
Unpacking Net-LDAP-Express-0.11...done
Unpacking perl-ldap-0.39...done
Unpacking Convert-ASN1-0.22...done
Generating HTML for Net-LDAP-Express-0.11...done
Generating HTML for perl-ldap-0.39...done
Generating HTML for Convert-ASN1-0.22...done
Updating files in site area...done
103 files installed

Apache

It is recommended that you run Bugzilla with the Apache web server. If you want to use IIS to run Bugzilla, there are configuration instructions in the Bugzilla documentation.
Download Apache 2.x

Download the Apache HTTP Server version 2.x or high from: http://httpd.apache.org/download.cgi (5.8 Meg).
Install

Yet another standard Windows Installer. Just follow the prompts, making sure you Install for All Users. Be aware the Apache will always install itself into an Apache2 directory under what ever path you specify. The default install path will be displayed as C:Program FilesApache Group which will result in Apache being installed to C:Program FilesApache GroupApache2. This gets me every time.

For the remainder of this document I will assume you installed Apache into the default location, C:Program FilesApache GroupApache2.

If you are already running IIS, you must configure apache to run on a port other than 80, however you aren't asked the port to listen on at install time. Choose All Users (which says port 80), and we'll change the port later.

By default Apache installs itself to run as the SYSTEM account. For security reasons it's better the reconfigure the service to run as an Apache user. Create a user that is a member of no groups, and reconfigure the Apache2 service to run as that account.
Grant write access for Apache account

By default Apache will run as the SYSTEM account. This account needs write and modify access to the following directorys, and all their subdirectories. Depending on your version of Windows, this access may already be granted.

C:Bugzilladata
C:Program FilesApache GroupApache2logs
C:Temp
C:WindowsTemp

Note that C:Bugzilladata is created the first time you run checksetup.pl.
Configure Port and DocumentRoot

Edit C:Program FilesApache GroupApache2confhttpd.conf with your favourite text editor.

To change the port that Apache runs on (listens on, or binds to), edit the Listen option.

#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
#
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses (0.0.0.0)
#
#Listen 12.34.56.78:80
Listen 80

Change the DocumentRoot setting to point to C:Bugzilla. Note there are two locations in httpd.conf that need to be updated. Note you need to use / instead of as a path separator.

#
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#

DocumentRoot "C:/Bugzilla"

#
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
#
# First, we configure the "default" to be a very restrictive set of
# features.
#
<Directory />
Options FollowSymLinks
AllowOverride None
</Directory>

#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#

#
# This should be changed to whatever you set DocumentRoot to.
#
<Directory "C:/Bugzilla">

Configure CGI

To enable CGI support in Apache, you need to enable the CGI handler, by uncommenting the AddHandler cgi-script .cgi line.

#
# AddHandler allows you to map certain file extensions to "handlers":
# actions unrelated to filetype. These can be either built into the server
# or added with the Action directive (see below)
#
# To use CGI scripts outside of ScriptAliased directories:
# (You will also need to add "ExecCGI" to the "Options" directive.)
#
AddHandler cgi-script .cgi

And allow .cgi scripts in the Bugzilla directory by adding the ExecCGI option. We also need to allow Bugzilla's .htaccess file to restrict access to sensitive documents by allowing it to override the defaults. This involves changing AllowOverride None to AllowOverride All.

Apache also needs to know to use Perl to execute .cgi files, via the ScriptInterpreterSource directive.

#
# This should be changed to whatever you set DocumentRoot to.
#
<Directory "C:/Bugzilla">

#
# Possible values for the Options directive are "None", "All",
# or any combination of:
# Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
#
# Note that "MultiViews" must be named *explicitly* --- "Options All"
# doesn't give it to you.
#
# The Options directive is both complicated and important. Please see
# http://httpd.apache.org/docs-2.0/mod/core.html#options
# for more information.
#
Options Indexes FollowSymLinks ExecCGI

#
# AllowOverride controls what directives may be placed in .htaccess files.
# It can be "All", "None", or any combination of the keywords:
# Options FileInfo AuthConfig Limit
#
AllowOverride All

#
# Controls who can get stuff from this server.
#
Order allow,deny
Allow from all

#
# Tell Apache to use Perl to execute .cgi
#
ScriptInterpreterSource Registry-Strict

</Directory>

You also should add index.cgi to the DirectoryIndex list.

#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
# The index.html.var file (a type-map) is used to deliver content-
# negotiated documents. The MultiViews Option can be used for the
# same purpose, but it is much slower.
#
DirectoryIndex index.html index.html.var index.cgi

In order for ScriptInterpreterSource Registry-Strict to work, you also need to add an entry to the Registry so Apache will use Perl to execute .cgi files.

Create a key HKEY_CLASSES_ROOT.cgiShellExecCGICommand with the default value of the full path of perl.exe with a -T parameter. For example C:Perlbinperl.exe -T

Regedit
Disable Logging

Unless you want to keep statistics on how many hits your Bugzilla install is getting, it's a good idea to disable logging by commenting out the CustomLog directive.

#
# The location and format of the access logfile (Common Logfile Format).
# If you do not define any access logfiles within a <VirtualHost>
# container, they will be logged here. Contrariwise, if you *do*
# define per-<VirtualHost> access logfiles, transactions will be
# logged therein and *not* in this file.
#
#CustomLog logs/access.log common

Restart Apache

Finally, restart Apache to get it pick up the changes.

C:>net stop apache2
The Apache2 service is stopping..
The Apache2 service was stopped successfully.

C:>net start apache2
The Apache2 service is starting.
The Apache2 service was started successfully.

C:>

Extras

While Bugzilla 2.20 has built in support for SMTP servers, it doesn't (yet) support SMTP authentication or debugging of SMTP errors.

If you require SMTP authentiation (including POP before SMTP), you can use Glob's sendmail wrapper. Download and install as per the instructions on that site.

If you enable logging in Sendmail, you need to ensure that your Apache account has write access to C:usrlib.
Configure Bugzilla
checksetup.pl

Run checksetup.pl. This will check your Perl modules and create localconfig.

C:>cd bugzilla

C:bugzilla>perl checksetup.pl

Checking perl modules ...
Checking for AppConfig (v1.52) ok: found v1.55
Checking for CGI (v2.93) ok: found v3.10
Checking for Data::Dumper (any) ok: found v2.121_04
Checking for Date::Format (v2.21) ok: found v2.22
Checking for DBI (v1.38) ok: found v1.48
Checking for File::Spec (v0.84) ok: found v3.05
Checking for File::Temp (any) ok: found v0.16
Checking for Template (v2.08) ok: found v2.13
Checking for Text::Wrap (v2001.0131) ok: found v2001.09293
Checking for Mail::Mailer (v1.65) ok: found v1.67
Checking for Storable (any) ok: found v2.13

The following Perl modules are optional:
Checking for GD (v1.20) ok: found v2.16
Checking for Chart::Base (v1.0) ok: found v2.3
Checking for XML::Parser (any) ok: found v2.34
Checking for GD::Graph (any) ok: found v1.43
Checking for GD::Text::Align (any) ok: found v1.18
Checking for PatchReader (v0.9.4) ok: found v0.9.5

Most ActivePerl modules are available at Apache's ppm repository.
A list of mirrors is available at
http://www.apache.org/dyn/closer.cgi/perl/win32-bin/ppms/
You can add the repository with the following command:
ppm rep add apache http://www.apache.org/dist/perl/win32-bin/ppms/

Checking user setup ...

This version of Bugzilla contains some variables that you may want
to change and adapt to your local settings. Please edit the file
'./localconfig' and rerun checksetup.pl

The following variables are new to localconfig since you last ran
checksetup.pl: index_html cvsbin interdiffbin diffpath create_htaccess
webservergroup db_driver db_host db_pass db_sock db_check

C:bugzilla>

Edit localconfig

Open C:Bugzillalocalconfig in your favourite text editor to configure Bugzilla.

You have to tell Bugzilla how to access your database. If you used bugs/bugs, you'll only have to set db_pass.

#
# How to access the SQL database:
#
$db_host = "localhost"; # where is the database?
$db_port = 3306; # which port to use
$db_name = "bugs"; # name of the MySQL database
$db_user = "bugs"; # user to attach to the MySQL database

#
# Enter your database password here. It's normally advisable to specify
# a password for your bugzilla database user.
# If you use apostrophe (') or a backslash () in your password, you'll
# need to escape it by preceding it with a character. (') or (\)
#
$db_pass = 'sockmonkey';

checksetup.pl

Run checksetup.pl again. This time it will build your database tables and initialise Bugzilla.

C:bugzilla>perl checksetup.pl

Checking perl modules ...
Checking for AppConfig (v1.52) ok: found v1.55
Checking for CGI (v2.93) ok: found v3.10
Checking for Data::Dumper (any) ok: found v2.121_04
Checking for Date::Format (v2.21) ok: found v2.22
Checking for DBI (v1.38) ok: found v1.48
Checking for File::Spec (v0.84) ok: found v3.05
Checking for File::Temp (any) ok: found v0.16
Checking for Template (v2.08) ok: found v2.13
Checking for Text::Wrap (v2001.0131) ok: found v2001.09293
Checking for Mail::Mailer (v1.65) ok: found v1.67
Checking for Storable (any) ok: found v2.13

The following Perl modules are optional:
Checking for GD (v1.20) ok: found v2.16
Checking for Chart::Base (v1.0) ok: found v2.3
Checking for XML::Parser (any) ok: found v2.34
Checking for GD::Graph (any) ok: found v1.43
Checking for GD::Text::Align (any) ok: found v1.18
Checking for PatchReader (v0.9.4) ok: found v0.9.5

Most ActivePerl modules are available at Apache's ppm repository.
A list of mirrors is available at
http://www.apache.org/dyn/closer.cgi/perl/win32-bin/ppms/
You can add the repository with the following command:
ppm rep add apache http://www.apache.org/dist/perl/win32-bin/ppms/

Checking user setup ...
Creating data directory (./data) ...
Creating graphs directory...
Creating .htaccess...
Creating Bugzilla/.htaccess...
Creating ./data/.htaccess...
Creating ./template/.htaccess...
Creating ./data/webdot/.htaccess...
Precompiling templates ...
Checking for MySQL Server (v3.23.41) ok: found v4.0.20a-debug

Creating table user_group_map ...
Creating table series_data ...
Creating table longdescs ...
Creating table dependencies ...
Creating table components ...
Creating table keywords ...
Creating table cc ...
Creating table duplicates ...
Creating table groups ...
Creating table flagtypes ...
Creating table profiles ...
Creating table products ...
Creating table bugs_activity ...
Creating table series_categories ...
Creating table keyworddefs ...
Creating table fielddefs ...
Creating table group_control_map ...
Creating table profiles_activity ...
Creating table group_group_map ...
Creating table user_series_map ...
Creating table bugs ...
Creating table series ...
Creating table versions ...
Creating table flagexclusions ...
Creating table logincookies ...
Creating table watch ...
Creating table bug_group_map ...
Creating table votes ...
Creating table attachments ...
Creating table flags ...
Creating table milestones ...
Creating table tokens ...
Creating table flaginclusions ...
Creating table quips ...
Creating table namedqueries ...
Creating initial dummy product 'TestProduct' ...
Populating duplicates table...
Creating duplicates directory...
Migrating old chart data into database ...
Adding group tweakparams ...
Adding group editusers ...
Adding group creategroups ...
Adding group editcomponents ...
Adding group editkeywords ...
Adding group admin ...
Adding group editbugs ...
Adding group canconfirm ...

Looks like we don't have an administrator set up yet. Either this is your
first time using Bugzilla, or your administrator's privileges might have
accidently been deleted.
Enter the e-mail address of the administrator: byron@example.com
You entered 'byron@example.com'. Is this correct? [Y/n] y
Enter the real name of the administrator: Byron Jones

Enter a password for the administrator account: beef

Please retype the password to verify: beef

'byron@example.com' is now set up as an administrator account.

C:bugzilla>

Parameters

You should now be able to log into to Bugzilla using the account checksetup.pl just created. Point your web browser to >http://localhost/, choose Log in to an existing account, and login.

In the page footer, choose Parameters.

Put in your email address as the maintainer.

maintainer:
byron@example.com

Put in the URL to Bugzilla in the urlbase field. This URL will be used in emails, so don't use localhost.

urlbase:
http://bugzilla.example.com/

Download and install WebDot from http://www.graphviz.org/Download_windows.php. Put the complete path to dot.exe in webdotbase.

webdotbase:
C:/Program Files/ATT/Graphviz/bin/dot.exe

Scheduled Tasks
collectstats.pl

Add a Scheduled Task to run collectstats.pl nightly.

Step-by-step for Windows XP:

Control Panel --> Scheduled Tasks --> Add Scheduled Task
Next
Browse
Find perl.exe (normally C:Perlbinperl.exe)
Give it a name, such as "Bugzilla Collect Stats"
Perfom the task daily at your desired time
If you're running Apache as a user, not as SYSTEM, enter that user here. Otherwise you're best off creating an account that has write access to the Bugzilla directory and using that
Tick "Open Advanced Properties.." and click Finish
Append the script name to the end of the "Run" field. eg C:Perlbinperl.exe C:Bugzillacollectstats.pl
Change "start in" to the Bugzilla directory

whineatnews.pl

Add a Scheduled Task to run whineatnews.pl nightly.

The steps for setting up whineatnews.pl are as per collectstats.pl
Backing up Bugzilla

You may want to backup the entire Bugzilla directory. It's small and you'll get all your settings and customisations on your backup media.

The most important component of Bugzilla to backup is the Bugzilla Database. It contains all your Bugs, Users, Attachments, pretty well everything. Like most databases, backups with MySql are performed by generating a dump of the database and backing up the dump.

Schedule the mysqldump utility to create the dump, and add the resulting file to your backup media. You'll find MySql's mysqldump documentation at http://dev.mysql.com/doc/mysql/en/mysqldump.html.

Testing if Bugzilla works

Try to access the your BugZilla by : (for example ) http://localhost:8080

If it doesn't display a BugZilla page, but "It works!!!", somehow your Apache still sees somehow original version of httpd.conf. Check if Apache picks another copy of httpd.conf. If you installed Apache once and somehow uninstalled it and install it again, it can see a copied version in conf/original of Apache directory. When you edited conf/httpd.conf, try this :

1. Stop Apache service
2. Invoke your Apache in a console : httpd.exe -f conf/httpd.conf

If your httpd.conf setting is all correct, it should display BugZilla page on your web browser.

However, if it still shows the same problem, and looks like that the Apache doesn't pick your modification in httpd.conf, you probably use Windows 7. Windows 7 has a new feature called "VirtualStore". To figure out about it more and how to fix it, try to read this blog article.

http://blog.netscraps.com/bugs/apache-httpd-conf-changes-ignored-in-windows-7.html

If it still fails but display "Internal Error..." message, ScriptInterpreterSource Registry-Strict is not set. Check again if it is set properly.

When everything works, stop the httpd.exe invoked from your console and start it as a service. Be sure to make it pick a right httpd.conf.
Congratulations, the Bugzilla installation process is complete!
Installing Bugzilla on Microsoft Windows with IIS

Bugzilla works with IIS as a normal CGI application; follow the Microsoft documentation with regards to configuring IIS.
Common Problems
Bugzilla runs but I can't log in

You've probably configured IIS to use ActiveState's ISAPI DLL -- in other words you're using PerlEx, or the executable IIS is configured to use is PerlS.dll or Perl30.dll.

Reconfigure IIS to use perl.exe
IIS returns HTTP 502 errors

You probably forgot the -T argument to perl when configuring the executable in IIS:

C:Perlbinperl.exe -T "%s" %s