[p4dti-discussion] P4DTI and Bugzilla 2.18.3

[Nick Barnes]

At 2005-10-04 20:02:12+0000, Stephen Vance writes:
> When I apply the patch for Bugzilla 2.18, Bugzilla dies with internal 
> server errors. I haven't figured out exactly why it is happening at 
> this point. It happens with all pages that I've tried. Running 'perl 
> -wT index.cgi' from the command line produces the index page 
> correctly. It's only in the Apache environment that it fails. I did 
> run checksetup.pl after applying the patch.
> 
> I'm using Perl 5.8.5, Apache 2.0.53, and P4DTI 2.2.2. The P4DTI isn't 
> actually running yet so the versions for Python (2.3.4) and Perforce 
> (2005.1) aren't that relevant.
> 
> Here are the Apache error log entries for the failure:
> 
> [Tue Oct 04 14:10:30 2005] [error] [client 127.0.0.1] Couldn't do 
> defparams.pl: No such file or directory at Bugzilla/Config.pm line 132.
> [Tue Oct 04 14:10:30 2005] [error] [client 127.0.0.1] Compilation 
> failed in require at Bugzilla/Util.pm line 38.
> [Tue Oct 04 14:10:30 2005] [error] [client 127.0.0.1] BEGIN 
> failed--compilation aborted at Bugzilla/Util.pm line 38.
> [Tue Oct 04 14:10:30 2005] [error] [client 127.0.0.1] Compilation 
> failed in require at CGI.pl line 43.
> [Tue Oct 04 14:10:30 2005] [error] [client 127.0.0.1] BEGIN 
> failed--compilation aborted at CGI.pl line 43.
> [Tue Oct 04 14:10:30 2005] [error] [client 127.0.0.1] Compilation 
> failed in require at /var/www/html/bugzilla/index.cgi line 33.
> [Tue Oct 04 14:10:30 2005] [error] [client 127.0.0.1] Premature end 
> of script headers: index.cgi
> 
> Perforce Support mentioned the upcoming P4DTI 2.3.0, but 
> unfortunately my time line would be hurt by waiting for it. You can't 
> even download bugzilla-2.18 anymore, only the point releases.
> 
> Suggestions on what to fix?

I'm a little baffled; I have applied that patch to various Bugzilla
releases, including 2.18.3 and 2.18.4, without a hitch.  "Couldn't do
defparams.pl" sounds pretty serious.  Can you send us the shell output
of applying the patch?  Can you confirm that you have a defparams.pl
file in your Bugzilla directory, after applying the patch?  Can you
send us that file?  Can you search your Bugzilla directory tree for
files matching *.rej (patch failure files)?  Can you manually run a
diff -ruN on a vanilla Bugzilla 2.18.3 and a patched one, and send the
result of that?

If it helps, you can download Bugzilla 2.18 from:

<http://www.ravenbrook.com/project/p4dti/import/2005-01-15/bugzilla-2.18/>

(and other releases from similar places, see the index:
<http://www.ravenbrook.com/project/p4dti/import/>).  But of course
that won't have the security fixes in later 2.18.* releases.

I have cc'ed Perforce Support on this, as they will probably want to
know the outcome.

Nick Barnes
P4DTI Project
Ravenbrook Limited