I was working on installing CollabNet Subversion on an RHEL5 server. A little about Scmbug:
Scmbug integrates software configuration management (SCM) with bug-tracking. It aims to solve the integration problem once and for all. It will glue any source code version control system (such as CVS/CVSNT, Subversion, Git) with any bug-tracking system (such as Bugzilla, Mantis, Request Tracker, Test Director).
My problem was that when I would try to start the scmbug-server daemon, it would fail instantly, and the following would be logged in the activity.log:
** Scmbug error 79: Package 'Bugzilla' not found in installation directory '/usr/share/bugzilla'.
Initialization of bug-tracking system 'Bugzilla' version '3.0.8' failed. This could be due to an unsupported version of this system, or misconfiguration.
After some research, I came up with nothing that would indicate a common problem. It turns out the solution is really simple. First off, you should keep a copy of the Bugzilla bits on the subversion server (assuming they're on two different hosts) to make things a little easier. As you can see, the bits in my case are located under /usr/share/bugzilla but it really doesn't matter where you set it, as long as you modify the daemon.conf for scmbug and specify the correct path.
To rectify the issue, go to your local Bugzilla directory, and run checksetup.pl. This file checks to find the necessary Perl module required by Bugzilla itself to run properly. You have to make sure that you have the core modules installed and available. Otherwise Scmbug will fail miserably, and you'll end up getting frustrated. The modules in question are: CGI.pm, TimeDate, DBI, PathTools, Template-Toolkit, Email-Send, Email-MIME, Email-MIME-Modifier and DBD-mysql.
If you're a lazy bastard like me, then you'll opt-in for yum install of these modules. However, you can install them via cpan which is recommended. Once you have those installed, go to your Bugzilla directory, then run checksetup.pl to make sure that all necessary modules are loaded. If they are, then you can run sanitycheck.pl, and then attempt to start the scmbug server.
Good luck and enjoy!