Front page | perl.perl5.porters |
Postings from January 2020
Re: CPAN from CPAN or git on perl-5.30.1
Thread Previous
|
Thread Next
From:
Dan Book
Date:
January 29, 2020 17:51
Subject:
Re: CPAN from CPAN or git on perl-5.30.1
Message ID:
CABMkAVX8U+-ozLtaVJrztnUXL_U_+oR8bRQ4vrHBxpqPwYfDEg@mail.gmail.com
On Wed, Jan 29, 2020 at 12:47 PM James E Keenan <jkeenan@pobox.com> wrote:
> On 1/29/20 12:13 PM, H.Merijn Brand wrote:
> > On Wed, 29 Jan 2020 11:35:09 -0500, James E Keenan <jkeenan@pobox.com>
> > wrote:
> >
> >> On 1/29/20 8:15 AM, H.Merijn Brand wrote:
> >>> I am working on a fresh installed CentOS 8.1 and installed 5.30.1
> >>> without any problem: All tests PASSed.
> >>>
> >>> 5.30.1 is shipped with CPAN-2.22
> >>>
> >>> That works fine.
> >>>
> >>> I then installed the modules I had installed on 5.28.2 on CentOS 7.7
> >>> and CPAN tells me there is a new(er) CPAN available.
> >>>
> >>> However, all 2.22, 2.25, 2.26, and 2.27 distributions and the
> >>> checkout of the git repo fail to pass the test suite. Using the
> >>> CPAN releases with perl-5.28.2 PASSes
> >>>
> >>> Linux 4.18.0-147.3.1.el8_1.x86_64 [CentOS Linux 8.1.1911 (Core)]
> >>>
> >>> This is perl 5, version 28, subversion 2 (v5.28.2) built for
> >>> x86_64-linux-thread-multi-ld This is perl 5, version 30, subversion
> >>> 1 (v5.30.1) built for x86_64-linux-thread-multi-ld
> >>>
> >>> Test Summary Report
> >>> -------------------
> >>> t/12cpan.t (Wstat: 768 Tests: 28 Failed: 3)
> >>> Failed tests: 15, 19-20
> >>> Non-zero exit status: 3
> >>> t/31sessions.t (Wstat: 7424 Tests: 96 Failed: 29)
> >>> Failed tests: 51-61, 63-66, 68, 71, 74, 77-82, 84, 89-91
> >>> 93
> >>> Non-zero exit status: 29
> >>> Files=31, Tests=859, 123 wallclock secs ( 0.36 usr 0.08 sys +
> >>> 75.71 cusr 10.66 csys = 86.81 CPU) Result: FAIL
> >>> Failed 2/31 test programs. 32/859 subtests failed.
> >> :
> >>
> >> Hmmm ... I tried a somewhat different procedure that resulted in
> >> successful installation of CPAN.pm version 2.27 against perl-5.30.1.
> >>
> >> I installed perl from git tag v5.30.1 on Linux, then installed
> >> 'cpanm' against that perl. (This is my customary procedure for
> >> testing against particular commits.) I then invoked 'cpanm' to
> >> install CPAN against that perl. The latest version of CPAN was
> >> successfully installed.
> >>
> >> #####
> >> [v5.30.1] 602 $ ./bin/perl -v | head -2 | tail -1
> >> This is perl 5, version 30, subversion 1 (v5.30.1) built for
> >> x86_64-linux [v5.30.1] 603 $ ./bin/perl -MCPAN -E 'say
> >> $CPAN::VERSION;' 2.27
> >> #####
> >
> > MIYAGAWA/App-cpanminus-1.7044.tar.gz
> > /usr/bin/make install -- OK
> > $ cpanm CPAN
> > --> Working on CPAN
> > Fetching http://www.cpan.org/authors/id/A/AN/ANDK/CPAN-2.27.tar.gz ...
> OK
> > Configuring CPAN-2.27 ... OK
> > Building and testing CPAN-2.27 ... FAIL
> > ! Installing CPAN failed. See .../.cpanm/work/1580317466.11626/build.log
> for details. Retry with --force to force install it.
> >
> > in there the same as with cpan or manual:
> >
> > Test Summary Report
> > -------------------
> > t/12cpan.t (Wstat: 768 Tests: 28 Failed: 3)
> > Failed tests: 15, 19-20
> > Non-zero exit status: 3
> > t/31sessions.t (Wstat: 7424 Tests: 96 Failed: 29)
> > Failed tests: 51-61, 63-66, 68, 71, 74, 77-82, 84, 89-91
> > 93
> > Non-zero exit status: 29
> > Files=31, Tests=859, 117 wallclock secs ( 0.53 usr 0.10 sys + 69.48
> cusr 11.98 csys = 82.09 CPU)
> > Result: FAIL
> > Failed 2/31 test programs. 32/859 subtests failed.
> >
> >> Jim Keenan
> >
> >
>
> I can now reproduce your failures against perl-5.30.1 by first
> installing as follows:
>
> #####
> ./bin/cpanm Module::Build YAML YAML::Syck
> #####
>
> Re-testing, I now get the output attached. Failures appear to be due to
> YAML or YAML::Syck. Do you have them loaded?
>
> Is this a problem for core or for CPAN distribution?
>
It appears the test is deserializing YAML and expecting blessed objects.
This now requires $YAML::LoadBlessed = 1 or $YAML::Syck::LoadBlessed = 1,
as described at
http://blogs.perl.org/users/tinita/2020/01/making-yamlpm-yamlsyck-and-yamlxs-safer-by-default.html
.
-Dan
Thread Previous
|
Thread Next