Re: Perl:2, Apache:0
On Mon, Jun 25, 2001 at 12:58:44PM -0500, dmaziuk@yola.bmrb.wisc.edu wrote:
> Guys, we have a problem:
>
> # /etc/init.d/apache start
> Starting web server: apache.
> [Mon Jun 25 12:34:34 2001] [error] Can't locate Apache.pm in @INC
> (@INC contains: /usr/local/lib/perl/5.6.1 /usr/local/share/perl/5.6.1
> /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.6.1 /usr/share/perl/5.6.1
> /usr/local/lib/site_perl/i386-linux /usr/local/lib/site_perl /usr/lib/perl5/5.6
> /usr/lib/perl5/5.005/i386-linux /usr/lib/perl5/5.005 . /etc/apache/
> /etc/apache/lib/perl) at (eval 1) line 3.
>
> /usr/sbin/apachectl start: httpd could not be started
>
> after perl update (to 5.6.1-4, testing). This is the second time (at least
> this time debconf didn't die ;)
>
> So, how TF can one upgrade perl without screwing up apache? Include Apache.pm
> in one of the perl packages? Make apache install Apache.pm in e.g. /etc/apache?
> Keep perl away from package pool until upgraded apache packages get there? Or
> maybe we could just let /usr/lib/perl/5.6.0 stay in @INC?
>
> For now I've created a bunch of symlinks to /usr/lib/perl/5.6.0 in
> /usr/local/lib/site_perl. This doesn't look optimal to me, but it works.
This has nothign to do with either perl or apache; well, only
peripherally. It means I'm behind on modperl maintenance.
If you're using the shared modperl, a fix should be available today.
If you're using apache-perl, it will take longer. There's a problem
with current apache.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
Reply to: