> >>>It looks like my current 1.99.17 configuration has Registry.pm here: > >>> > >>>/usr/lib/perl5/vendor_perl/5.8.5/i686-linux/Apache2/ModPerl/Registry.pm > >>> > >>>and according to the logs the new one was installed here: > >>> > >>>/usr/lib/perl5/vendor_perl/5.8.5/i686-linux/ModPerl/Registry.pm > >>> > >>>Interchange::Link has always included this line which looks like the > >>>"new" namespace: > >>> > >>>use ModPerl::Registry; > >>> > >>>Also, the Gentoo notes I got at the end of the emerge said to change: > >>> > >>>Apache::ModPerl::Registry => ModPerl::Registry > >>> > >>>Link.pm already seemed to use that "new" namespace, but it errored as > >>>above. > >>> > >>>How would I fix this? Would I see others like it if I fixed it? > >> > >>Grant, how exactly did you remove 1.99.17? You were supposed to remove the > >>Apache2/ subdirectory and everything under it. Have you read: > >>http://perl.apache.org/docs/2.0/rename.html > > > > > > Hi Stas, > > > > I removed it with the Gentoo mechanism: > > > > emerge -C mod_perl > > > > What makes you think it wasn't removed properly? It is my current > > 1.99.17 installation that has Registry.pm under Apache2. 2.0.0rc5 > > installed it to: > > > > /usr/lib/perl5/vendor_perl/5.8.5/i686-linux/ModPerl/Registry.pm > > Ah, OK, I thought your *current* was the one you have the problem with. > > > I don't understand why error_log said it couldn't find that module. > > The above is in @INC. Maybe I should just try it again? > > Please do so. > > Your errors are very confusing, you said the error was that it couldn't > find ModPerl/Registry.pm, but when I asked you where it is you said it's: > > /usr/lib/perl5/vendor_perl/5.8.5/i686-linux/Apache2/ModPerl/Registry.pm > > which is wrong. It shouldn't be there if you have uninstalled 1.99.17 > > and then you said: > > > and according to the logs the new one was installed here: > > /usr/lib/perl5/vendor_perl/5.8.5/i686-linux/ModPerl/Registry.pm > > but apparently it is not there, so your log is wrong.
Well I was able to get mp2bug to report only CGI 3.05 by renaming some files but my errors haven't changed. I even tried changing all Apache2::Const::OK references to Apache2::OK and restarting apache2 but it still reports the same errors. I'm going to roll back. - Grant
