In the thread at
https://rt.perl.org/rt3//Public/Bug/Display.html?id=115908 there's a
list of modules that were known to not be ready for Perl 5.18.  Some
of them have been fixed, and some haven't.

To that list, more digging has uncovered JSON::XS, Crypt::DES,
Crypt::Blowfish, Crypt::IDEA, Crypt::Twofish, Crypt::OpenPGP, and
still Template(toolkit).  ...and of course all modules that depend on
these.

JSON, for example, if installed non-interactively will try to install
JSON::XS, and will fail because JSON::XS has a broken test that relies
on hash ordering.  In the case of the Crypt::* modules, most of them
have a defect in their use of Sv_UPGRADE.  In both of these cases the
patch is fairly trivial, and yet despite the warning signs (smoke test
failures from Perl 5.17.x versions, as well as announcements of the
hash randomization changes) the modules haven't been updated to work
with Perl 5.18.

In the case of Crypt::DES and Crypt::Blowfish I've uploaded
unauthorized releases that apply the patch that was already suggested
in their respective RT queues.  I've also notified the
author/maintainer of the upload via email, and tried to remind that
this issue has now become critical.

I could continue going after these simple-fix ones, but I'm sure new
ones will be discovered as quickly as old ones are fixed.  Plus,
unauthorized releases aren't an ideal solution; they just sort of
serve to light a little fire, IMO.

So this is a reminder to authors; look at the smoke tests and verify
that you're passing on 5.18.  I appreciate that some modules are
obscure enough that it's ok for this to take some time.  But others
are in daily use, and need to be brought up to the current standard
quickly to minimize pain as people upgrade to Perl 5.18.

Dave

--

David Oswald
daosw...@gmail.com

Reply via email to