[p4dti-discussion] P4DTI and Bugzilla 2.18.3 (CALL#1108491)

[Stephen Vance]

Nick --

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.

Steve

At 03:34 PM 10/5/2005, Nick Barnes wrote:
>At 2005-10-05 16:59:24+0000, Stephen Vance writes:
> > Nick --
> >
> > I checked permissions on defparams.pl and there are no differences.
> >
> > Using the bugzilla-2.18 I downloaded from Ravenbrook, I experienced
> > the same problem. I installed and configured bugzilla and it worked
> > fine. I apply the patch, rerun checksetup.pl, and 500. I did have to
> > change the bugzilla root ownership. Apparently, checksetup.pl doesn't
> > manage that.
> >
> > I am running mod_perl. I have to run to a client site, but I'll try
> > removing mod_perl when I get back and see if it makes a difference.
>
>Aha.  Bugzilla doesn't work with mod_perl.  See
>
><https://bugzilla.mozilla.org/show_bug.cgi?id=87406>
>
>and
>
><http://perl.apache.org/docs/1.0/guide/porting.html#Sometimes_it_Works__Sometimes_it_Doesn_t>
>
>It's not clear to me why applying the P4DTI patch would break things,
>except possibly you should reset mod_perl (somehow?) when Perl sources
>change, but in any case, don't use mod_perl with Bugzilla.
>
>Nick Barnes
>P4DTI Project
>Ravenbrook Limited
>_______________________________________________
>P4DTI-discussion mailing list
>P4DTI-discussion at ravenbrook.com
>http://mailman.ravenbrook.com/mailman/listinfo/p4dti-discussion

Stephen Vance
mailto:steve at vance.com
http://www.vance.com/