Bugzilla

Bugzilla is a web application for tracking bugs.

Installation

USE flags

Emerge

Install www-apps/bugzilla :

Database

MySQL

Install dev-db/mysql but prefer a 5.x version ^[1] , then create a user for the bugzilla database:

mysql> CREATE USER 'bugs'@'localhost' IDENTIFIED BY '$db_pass';
mysql> GRANT SELECT, INSERT,
UPDATE, DELETE, INDEX, ALTER, CREATE, LOCK TABLES,
CREATE TEMPORARY TABLES, DROP, REFERENCES ON bugs.*
TO bugs@localhost IDENTIFIED BY '$db_pass';
mysql> FLUSH PRIVILEGES;
mysql> \q

PostgreSQL

Once PostgreSQL is installed and set up on the system, install bugzilla with the postgres USE flag, then create a user and a database for bugzilla to use:

Edit the following configuration file and add the following line (adjust according to PostgeSQL version):

host all bugs 127.0.0.1 255.255.255.255 md5

Then restart the database server:

Or:

Checksetup

Change directory to /var/www/localhost/htdocs/bugzilla, then execute checksetup.pl:

The first execution produces a localconfig file, in which the information about the database used must be put. The comments in that files are self-explanatory. Next, re-run checksetup.pl, which will create the database, configure bugzilla and create the admin user.

Configuration

Apache

Add bugzilla to the default vhost:

<Directory"/var/www/localhost/htdocs/bugzilla">
AddHandlercgi-script.cgi
Options+ExecCGI+FollowSymLinks
DirectoryIndexindex.cgiindex.html
AllowOverrideAll
</Directory>

Or alternatively define another vhost, which will make bugzilla directly available at https://127.0.0.1:

<VirtualHost*:80>
ServerNamelocalhost
DocumentRoot"/var/www/localhost/htdocs/bugzilla"
<Directory"/var/www/localhost/htdocs/bugzilla">
AddHandlercgi-script.cgi
Options+ExecCGI+FollowSymLinks
DirectoryIndexindex.cgiindex.html
AllowOverrideAll
Requireallgranted
</Directory>
<IfModulempm_peruser_module>
ServerEnvironmentapacheapache
</IfModule>
CustomLog/var/log/apache2/bugzilla_access.logcombined
ErrorLog/var/log/bugzilla_error.log
</VirtualHost>

Then restart the web server:

Web end

Finally, point a web browser to https://127.0.0.1/bugzilla/ or https://127.0.0.1 depending on the configuration. Log in with the admin account and bugzilla will invite to proceed to the essential post-installation configuration ^[2] .

Upgrading

To upgrade bugzilla app-admin/webapp-config ^[3] can be used. Upgrade is done automatically if the package is emerged without the vhosts flag. Finally, after upgrading, checksetup.pl should always be run to apply database changes and set file permissions ^[4] .

Upgrades can also be done manually as follows, which applies if you installed your bugzilla application to /var/www/localhost/htdocs/bugzilla, you may replace this location accordingly. Before emerging bugzilla, move your bugzilla directory:

Then emerge bugzilla:

Next, copy the directories data, lib (may be empty) and template/en/custom (may not exist) from your previous installation to your new installation, together with the previous localconfig file. Then run checksetup.pl:

After having ascertained that the new installation works as expected, the old bugzilla directory may be deleted.

Troubleshooting

If after executing checksetup.pl an output similar to the following is received:

Undefined subroutine utf8::SWASHNEW called at Bugzilla/Util.pm line 104. 
Compilation failed in require at Bugzilla/Mailer.pm line 21,  line 755.
BEGIN failed--compilation aborted at Bugzilla/Mailer.pm line 21,  line 755.
Compilation failed in require at Bugzilla/Auth.pm line 22,  line 755.
BEGIN failed--compilation aborted at Bugzilla/Auth.pm line 22,  line 755.
Compilation failed in require at Bugzilla.pm line 23,  line 755.
BEGIN failed--compilation aborted at Bugzilla.pm line 23,  line 755.
Compilation failed in require at ./checksetup.pl line 75,  line 755.

Then comment this line ^{[5] [6]} .

$var=~tr/\x{202a}-\x{202e}//d;

Then re-execute checksetup.pl.

More documentation

Find more documentation on the official bugzilla documentation page ^[7] .

References

• Stale
• Web application