You can do this from the command line by opening a Command Prompt and typing, IIRC, “ppm.bat” (without the quotes). Install the Perl modulesĬontinuing with the directions from the BZ IIS page, we next need to install the modules. We’ll need the variable set for the next step. Be sure to Log out, and Log back in, after installing Perl, because the PATH Environmental Variable was set by the Perl installation, and you need to Log out & back in to get the change picked up by Windows. To simplify things, I gave System, NETWORK_SERVICE, and IUSR_ write permission to this directory. Go ahead and follow the instructions to install Perl, and to create the C:\Temp directory and set the permissions. You will simply be told that the modules you need were not found. If you download the wrong version, you will not be able to install the required modules to get BugZilla working. What they don’t tell you is that the latest version of ActiveState Perl available at the time of this writing - 5.10.x - is NOT COMPATIBLE with BugZilla! To be specific, most of the Perl add-on modules required by BugZilla are not available for ActiveState Perl 5.10.x!! Don’t download v5.10.x!! Instead, download the previous version, 5.8.x. WARNING!! There is a HUGE “Gotcha” here! The directions state “Download the ActiveState Perl 5.8.1 or Higher.”. Once that’s done, the BZ IIS pagethen directs you to download and install ActiveState Perl. Again, it will make the later steps easier to follow. I strongly recommend that you move all the files and sub-directories under this sub-directory-on my system it was C:\Bugzilla\bugzilla-3.0.3-directly under the C:\Bugzilla directory. Note that, by default, when the TarBall is extracted, it will create a sub-directory under C:\Bugzilla with the version number. It makes it a lot easier to follow the directions if you do this. The directions suggest that you create, and extract the files into, C:\Bugzilla I second the recommendation. The instructions boil down to extracting the files into a directory WinZip will handle the extraction (there is a free evaluation version available at that link) if you don’t already have a utility that handles TarBalls. Instead, scroll down to the instructions under the heading “ Installing BugZilla From the TarBall“, and follow them. They start with instructions for downloading BugZilla from CVS I recommend that you don’t do this. Start there, and follow their directions to download BugZilla itself: version 3.0.3 is the latest stable release at the time of this writing. For simplicity’s sake, from now on I will refer to this page as “ the BZ IIS page“. Downloading the required softwareīugZilla has a page that will at least get you started installing BugZilla on Windows. NOTE: this information was accurate when I posted it, for my system I take no responsibility for any issues you may experience, and I can’t guarantee these steps will work for you. It occurred to me that, considering the difficulties I had, and the fact that the information that is available is spread out over the Internet, and much of the crucial information is not out there at all, it might be a service to the community to post what I found out. I chose to set BugZilla up to use IIS because I am already running it for web development, and I wanted to keep things relatively simple.Īfter a near-all-nighter, and another day of hair-pulling frustration, I got BugZilla up and working on IIS. On Windows, BugZilla gives you the choice of running in the open-source Apache webserver, or Windows’ built-in webserver, IIS. Never having used one, I decided to try the open-source BugZilla to get a feel for how these kinds of programs work and what the features are. Recently, I found myself in need of a bug-tracking solution. 13, 2010: I have just added a post on updating BugZilla to v3.6.2 from the below-mentioned version.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |