develooper Front page | perl.perl5.porters | Postings from April 2017

Re: [perl #131141] [PATCH] Pull request CPAN-2.18-TRIAL

Thread Previous
From:
Leon Timmermans
Date:
April 16, 2017 12:35
Subject:
Re: [perl #131141] [PATCH] Pull request CPAN-2.18-TRIAL
Message ID:
CAHhgV8iQvOLVYezrCzAwpxUiTgnmC5Ku7e6L0BhYhXE6cm4OmQ@mail.gmail.com
On Sun, Apr 16, 2017 at 9:41 AM, slaven@rezic.de via RT
<perlbug-followup@perl.org> 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?

I agree the PERL_USE_UNSAFE_INC fix is quite essential, and not
applying it will result in some CPAN dists.

Leon

Thread Previous


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About