dosen't work after installation

[Reda El Khattabi]

Binary package hint: libapache2-mod-perl2

after installing mod-perl, it dosen't work, and it's very difficult to find documentation on how to make it work ..

The configuration file for this module /etc/apache2/mods-available/perl.conf is left empty, witch causes this error.

it should contain something like

<Files ~ "\.pl$">
 SetHandler perl-script
 PerlResponseHandler ModPerl::PerlRun
 Options +ExecCGI
 PerlSendHeader On
</Files>

to allow execution of all .pl files in the server by the module.

and maybe also comments for how to restrict execution of perl files to specific folders (the most important is to have it working, then if a user wants to tweak it, tell him how to do so)

[Ralph Janke (txwikinger)]

Could you please provide the version of ubuntu you use and and version of the mod-perl package you have installed.

Thanks

[Ralph Janke (txwikinger)]

I have confirmed that the file described (/etc/apache2/mods-available/perl.conf) is indeed empty (also in feisty). All other modules for apache are installed making them immediately functional as soon as the links are made from mods-enabled to mods-available. However, this package seems not functional without the described lines in the .conf file.

[Ralph Janke (txwikinger)]

Reported upstream to Debian

[Ralph Janke (txwikinger)]

Reda,

Here is the upstream response from the package maintainer for debian:

--------------------------start------------------------------------------------------------
Hi,

I'm downgrading this bug and tagging is as "wontfix". Your proposed
fix makes it a bit easier, yes, to use mod_perl2 to run Perl scripts
under ModPerl::PerlRun - But in my experience, this is not the usual
case (I do not even recall having ever seen this module!). So... Not
only does this does not solve the problem for every user who
explicitly develops (or uses) Apache Perl modules, but it introduces
an unexpected behaviour to many people who have .pl files anywhere in
their _static_ documents tree.

In my always very humble opinion ( ;-) ), mod_perl is explicitly
installed by people who know what it is about and how to handle
them. When it is implicitly installed by other packages, of course,
_those packages_ should include the needed Apache configuration to get
them working.

Of course, if you disent with me, we can further discuss this.

Greetings,

--
Gunnar Wolf - <email address hidden> - ([phone] / 1451-2244
PGP key 1024D/8BB527AF 2001-10-23
Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF
--------------------------end----------------------------------------------------------------

I have to say that I concur with this opinion. Usually a package that uses perl_mod
will do its own configuration, such that a unexperienced user will not really get into
the situation to have to configure it themselves. If a particular package does not
do so, a report should be filed against that package, not against perl_mod.

Therefore I would like to close this report with your permission.

Thanks

[Ralph Janke (txwikinger)]

This bug will not be fixed due to the reasons cited by the upstream maintainer/developer.

Thanks for your time trying to make Ubuntu better.