Bug#848346: should be solved with 2.040

gregor herrmann gregoa at debian.org
Sat Dec 17 16:49:00 UTC 2016


On Sat, 17 Dec 2016 16:23:38 +0100, Steffen Ullrich wrote:

> Thanks for the analysis that the problem is caused by a change in the
> SSLEAY_DIR/OPENSSL_DIR constant with OpenSSL 1.1. I've adapted
> IO::Socket::SSL in 2.040 (just released) to try both constants so the
> problem should hopefully be solved by simply upgrading to 2.040.

Thank you!
Uploaded to Debian/unstable.
 
> Apart from that the problem would have probably be found by the live tests
> (t/external) since these check if the default trust path can be used to
> verify the certificte of some common sites. Unfortunately Debian explicitly
> does not run these live tests by default. But it might make sense to run
> these at least once before shipping a new version.

Ack, we should try to run them manually before an upload.
(Which I just did for 2.040-1.)

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Il Gran Ciambellano: Quando chidi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: Digital Signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-perl-maintainers/attachments/20161217/d342efd8/attachment.sig>


More information about the pkg-perl-maintainers mailing list