[p4dti-discussion] P4DTI and Bugzilla 2.18.3 (CALL#1108491)
Nick Barnes
nb at ravenbrook.com
Thu Oct 6 09:47:22 BST 2005
At 2005-10-05 21:09:58+0000, Stephen Vance writes:
> Sounded promising, but disabling mod_perl (by commenting out the Load
> line in /etc/httpd/conf.d/perl.conf and restarting the server) did
> not change the behavior.
>
> I've made sure to restart (full stop and full start) the server
> between configuration changes anyway.
>
> I don't need to go so far as to fully uninstall the mod_perl rpm or
> to reinstall a patched bugzilla from scratch, do I? It doesn't seem
> like I should.
I agree, that seems unlikely, although I don't know much about
mod_perl.
The error message seems to be saying that it can't find defparams.pl.
Given that defparams.pl is right there in your Bugzilla directory, and
has suitable permissions to be read by the Perl process, and parses
correctly as Perl, I'm a little stumped. It could be the Perl include
path @INC, but nothing in the P4DTI patch touches that.
I still can't reproduce this at all, so I'm dependent on you to debug
it. Try breaking the patch down manually; see if you can identify
which part of the patch breaks things. Start by reverting
defparams.pl.
Nick B
More information about the P4DTI-discussion
mailing list