Re: [RELEASE CANDIDATE] mod_perl-2.0.12 RC1

Steve Hay <[email protected]>
Newsgroups gmane.comp.apache.mod-perl,gmane.comp.apache.sling.devel
Message-ID <CADED=K4=EJXGntFO-7z7EkShx4SdLFvXeXop08iQBhfm9iNPiA@mail.gmail.com>
On Mon, 8 Nov 2021 at 20:34, [email protected]
<[email protected]> wrote:
>
> On Sun, 7 Nov 2021 13:48:58 +0000
> Steve Hay <[email protected]> wrote:
>
> > Please download, test, and report back on this mod_perl 2.0.12 release
> > candidate.
> >
> > https://dist.apache.org/repos/dist/dev/perl/mod_perl-2.0.12-rc1.tar.gz
> >
>
> Hi Steve,
>
> Tested on Debian 10.10 (Buster)
>
> I had to do the following to run the test suite :
>
> Got the error
> /usr/bin/ld: cannot find -lperl
>
> Followed this advice
> https://stackoverflow.com/questions/335928/ld-cannot-find-an-existing-library
>
> and linked libperl.so to libperl.so.5.28.1 (the current library)
>
> Then got this error :
>
> ~..(13)Permission denied: AH00091: apache2: could not open error log file /home/vincent/tmp/mod_perl-2.0.12-rc1/t/logs/error_log.
> AH00015: Unable to open logs
>
> So :
>
> /tmp/mod_perl-2.0.12-rc1/t# chgrp vincent logs
> ~/tmp/mod_perl-2.0.12-rc1/t# chmod g+w logs
>
> Tests runs fine, with this warning for just about all tests :
>
> t/protocol/echo_filter.t ................ [Mon Nov 08 21:03:49.933516 2021] [core:warn] [pid 25091] AH00111: Config variable ${APACHE_RUN_DIR} is not defined
> apache2: Syntax error on line 80 of /etc/apache2/httpd.conf: DefaultRuntimeDir must be a valid directory, absolute or relative to ServerRoot
>
>
> Here is the Test Summary Report
>
> -------------------
> t/apache/daemon.t                     (Wstat: 0 Tests: 2 Failed: 2)
>   Failed tests:  1-2
> t/filter/in_bbs_inject_header.t       (Wstat: 0 Tests: 36 Failed: 3)
>   Failed tests:  22, 26, 30
> Files=245, Tests=3505, 758 wallclock secs ( 2.95 usr  1.22 sys + 574.12 cusr 163.00 csys = 741.29 CPU)
> Result: FAIL

Thanks for testing, and apologies for the slow response.

The t/filter/in_bbs_inject_header.t failure is documented in the
README. I don't recall seeing the t/apache/daemon.t failure before.
Does it happen with the current release version (2.0.11) as well?
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.