Which Directory Service do you use for your network?
None NIS LDAP LDAP + Kerberos Samba Active Directory eDirectory other ( 741 votes ~ 14 comments )
You are not currently logged in. If you do not have a user account then please consider creating one and logging in before you post your comment. This will allow you to track replies to your comment, and take part in the site much more freely.
To add your comment, fill in all the boxes below and then preview it to make sure you're happy with the way that it looks.
This is the comment you were replying to, attached to the article Apache/perl package install and testing (e.g. mod-perl and Mason):
#3 Re: Apache/perl package install and testing (e.g. mod-perl and Mason) Posted by mwarnock (66.87.xx.xx) on Wed 17 Aug 2005 at 16:27 Thanks for all the help. I guess I had used server-status under 1.3 but not server-info. server-info seems to provide much of the apache debugging/configuration info I was looking for, and it does appear to show that mod_perl isn't even loading. As a Debian newbie, I guess I don't understand how backports/fixes work. Is this a known bug that will be fixed in the distribution (given some more time)? Or do stable packages only get security fixes, no matter how horrendously broken they may be in terms of functionality? Do I need to watch "backports" sites for this kind of thing? Please explain your last two sentences a bit further, if you don't mind, please. Is it the "backported" libapache2-mod-perl2 packages that work for you, while libapreq2 doesn't? Isn't libapreq2 required for mod_perl2? I read that libapreq2 contains the perl language interface to apache, and I assumed you couldn't run mod_perl without it? I just read the following at MasonHQ.com: In mod_perl version 1.999022 (2.0.0-RC5), there was a big renaming of the namespace of the mod_perl2 API. This was not backward compatible, and many modules, such as libapreq2, CGI, and HTML::Mason had to be updated to support the new API. If you upgrade to mod_perl-2.0.0 and are using any of the modules below, you will also have to upgrade the modules to the versions indicated. CGI 3.08 libapreq2 2.05 HTML::Mason 1.30 Support for mod_perl-2.0.0 has been released as Mason-1.29_02 (or newer). If you get errors about the Apache2::Request object, you have two choices: 1) install libapreq2, or 2) change MasonArgsMethod to "CGI". Apache2::Request is part of the libapreq2 package. It is still in the development stage, so to find it on CPAN, you must search for "libapreq2", and not for "Apache2::Request". Mason 1.27 (released 10/28/2004), contains support for Apache/mod_perl-1.99. The current debian Mason package is 1.27. Maybe it is just easier to forget about apache2 and go back to apache 1.3... :^(
As a Debian newbie, I guess I don't understand how backports/fixes work. Is this a known bug that will be fixed in the distribution (given some more time)? Or do stable packages only get security fixes, no matter how horrendously broken they may be in terms of functionality? Do I need to watch "backports" sites for this kind of thing?
Please explain your last two sentences a bit further, if you don't mind, please. Is it the "backported" libapache2-mod-perl2 packages that work for you, while libapreq2 doesn't? Isn't libapreq2 required for mod_perl2? I read that libapreq2 contains the perl language interface to apache, and I assumed you couldn't run mod_perl without it?
I just read the following at MasonHQ.com:
In mod_perl version 1.999022 (2.0.0-RC5), there was a big renaming of the namespace of the mod_perl2 API. This was not backward compatible, and many modules, such as libapreq2, CGI, and HTML::Mason had to be updated to support the new API. If you upgrade to mod_perl-2.0.0 and are using any of the modules below, you will also have to upgrade the modules to the versions indicated. CGI 3.08 libapreq2 2.05 HTML::Mason 1.30 Support for mod_perl-2.0.0 has been released as Mason-1.29_02 (or newer). If you get errors about the Apache2::Request object, you have two choices: 1) install libapreq2, or 2) change MasonArgsMethod to "CGI". Apache2::Request is part of the libapreq2 package. It is still in the development stage, so to find it on CPAN, you must search for "libapreq2", and not for "Apache2::Request". Mason 1.27 (released 10/28/2004), contains support for Apache/mod_perl-1.99.
The current debian Mason package is 1.27. Maybe it is just easier to forget about apache2 and go back to apache 1.3... :^(
Posting Format:
Inappropriate comments will be removed.
Some help on entry formatting is available
Username:
Password:
[ Advanced Login ]
Register Account
