Front page | perl.perl5.porters |
Postings from April 2017
On Sun, 16 Apr 2017 07:41:13 GMT, slaven@rezic.de wrote: > Dana Wed, 12 Apr 2017 19:42:36 -0700, > andreas.koenig.7os6VVqR@franz.ak.mind.de reče: > > (Resending article > > http://www.nntp.perl.org/group/perl.perl5.porters/2017/04/msg243905.html > > with the attachment inline) > > > > From: Andreas Koenig <andreas.koenig.7os6VVqR@franz.ak.mind.de> > > To: Mailing list Perl5 <perl5-porters@perl.org> > > Subject: Pull request CPAN-2.18-TRIAL > > Date: Thu, 06 Apr 2017 21:59:50 +0200 > > Message-ID: <87r31571e1.fsf@k85.linux.bogus> > > > > CPAN-2.17-TRIAL tried to narrow the scope to the phases prepare, > > make, > > and test, but after some testing evidence took shape that > > PERL_USE_UNSAFE_INC=1 is also needed for the install phase. > > > > 2.18 provides this change. The second issue fixed in 2.18 addresses > > #120781, an ugly bug with a trivial fix. > > > > All tests are green at the time of this writing: > > http://matrix.cpantesters.org/?dist=CPAN%202.18-TRIAL > > > > Sorry for the inconvenience and the long time it took to understand > > the > > issue. > > > > Thanks, > > I find this issue quite critical. Currently large parts of the CPAN > appear broken. Will the issue be addressed in 5.25.12? > > Regards, > Slaven I hope so, but since we're in code freeze it's the pumpking's prerogative as to when to merge this into blead and/or when to generate a perl-5.25.12. But I would also like to ask: Do we have a plan for when, subsequent to perl-5.26.0, we have CPAN.pm -- and other CPAN installers -- revert to PERL_USE_UNSAFE_INC=0? Thank you very much. -- James E Keenan (jkeenan@cpan.org) --- via perlbug: queue: perl5 status: open https://rt.perl.org/Ticket/Display.html?id=131141Thread Next