Trying to use mod_perl on Mageia 1, you get: "You must install Linux::Pid for Apache::SizeLimit to work on your platform. at /usr/lib/perl5/vendor_perl/5.12.3/i386-linux-thread-multi/Apache/SizeLimit/Core.pm line 128." The corresponding code in Core.pm is: elsif ($Config{'osname'} eq 'linux') { _load('Linux::Pid'); But Linux::Pid is not available as a RPM in Mageia 1, and so mod_perl cannot be used.
You should also release Linux::Smaps, which is used in the same module, but which is optional (but still good to have).
Linux::Pid is a requires or a suggests? i.e. does Apache::SizeLimit provide a basic functionality or an optional one?
Linux::Pid is a requires. Apache::SizeLimit throws an error without it. Linux::Smaps is a suggests. Apache::SizeLimit can work without it.
perl-Linux-Pid and apache-mod_perl (with requires on Linux::Pid), should land in core/updates_testing, please test. perl-Linux-Smaps should land in core/backports_testing.
Linux::Pid is now correctly installed when installing mod_perl. My Bugzilla installation doesn't work correctly with mod_perl enabled, but this problem was already present without these new RPM.
Could you provide a test case for QA? (I don't use apache or mod_perl, myself).
Keywords: (none) => NEEDINFO
(In reply to comment #6) > Could you provide a test case for QA? (I don't use apache or mod_perl, myself). Note really, no. I just made sure that installing the mod_perl RPM also installed Linux::Pid, and then I accessed an installation which uses mod_perl and made sure it was using it.
OK, thanks. Official update request. Test case: - Not required in this case, as you can see from the bug description, the Linux::Pid module is used/required for Apache::SizeLimit to work. Advisory text: ================================== In the apache-mod_perl package in Mageia 1, Apache::SizeLimit needs the Linux::Pid perl module to work correctly. This update changes the apache-mod_perl package to require the perl-Linux-Pid package. ==================================
Keywords: NEEDINFO => TriagedAssignee: bugsquad => qa-bugs
One week since Ahmad's official request. What prevents perl-Linux-Pid-0.40.0-1.mga1.i586.rpm from being pushed into core/updates/ and perl-Linux-Smaps-0.90.0-1.mga1.noarch.rpm into core/backports/?
The absence of test case allowing to check that the bug is fixed and that mod_perl works is probably what made no tester have a look at it (given that we lack testers they have tested other packages). You already tested for i586, but policy asks for a test on x86_64 too. Could you either do it or tell us how to test (for example a sample perl script to use with mod_perl) ? Sorry for the delay.
CC: (none) => stormi
Tested OK on x86_64 Test Procedure: - Install apache-mod_perl on Mageia server Edit /etc/httpd/modules.d/75_mod_perl.conf and replace 127.0.0.1 in stanza <Location /perl-status> with IP address of desktop computer (if not running apache on localhost_ service httpd restart Point browser to httpd://server_ip/perl-status If successful menu of perl environment can be seen.
CC: (none) => derekjenn
Sorry typo in last post. That should be http://server_ip/perl-status
It works for me too. Please push perl-Linux-Pid and apache-mod_perl to updates. Advisory: In the apache-mod_perl package in Mageia 1, Apache::SizeLimit needs the Linux::Pid perl module to work correctly. This update changes the apache-mod_perl package to require the perl-Linux-Pid package.
Keywords: Triaged => validated_updateCC: (none) => sysadmin-bugs
Packages pushed to updates.
Status: NEW => RESOLVEDCC: (none) => boklmResolution: (none) => FIXED
CC: boklm => (none)