This is an automated email from the git hooks/post-receive script.
hlieberman-guest pushed a commit to branch master
in repository libcrypt-ssleay-perl.
Author: Harlan Lieberman-Berg <h.liebermanb...@gmail.com>
Date: Mon Apr 28 18:31:46 2014 -0400
Add deprecation warning.
As upstream has seen fit to put a warning into the compilation to
indicate that users probably shouldn't be using this package
anymore, we should pass that message along to our users.
debian/NEWS.Debian | 25 +++++++++++++++++++++++++
1 file changed, 25 insertions(+)
diff --git a/debian/NEWS.Debian b/debian/NEWS.Debian
new file mode 100644
@@ -0,0 +1,25 @@
+libcrypt-ssleay-perl (0.72-1) UNRELEASED; urgency=medium
+ Starting with version 6.02 of LWP, https support was unbundled into
+ LWP::Protocol::https. This module specifies as one of its prerequisites
+ IO::Socket::SSL which is automatically used by LWP::UserAgent unless
+ this preference is overridden separately. IO::Socket::SSL is a more
+ complete implementation, and, crucially, it allows hostname
+ verification. Crypt::SSLeay does not support this. At this point,
+ Crypt::SSLeay is maintained to support existing software that already
+ depends on it.
+ However, it is possible that your software does not really depend on
+ Crypt::SSLeay, only on the ability of LWP::UserAgent class to
+ communicate with sites over SSL/TLS.
+ If are using version LWP 6.02 or later, and therefore have installed
+ LWP::Protocol::https and its dependencies, and do not explicitly use
+ Net::SSL before loading LWP::UserAgent, or override the default socket
+ class, you are probably using IO::Socket::SSL and do not really need
+ Before installing Crypt::SSLeay, you may want to try specifying a
+ dependency on LWP::Protocol::https.
+ -- Harlan Lieberman-Berg <h.liebermanb...@gmail.com> Mon, 28 Apr 2014
Alioth's /usr/local/bin/git-commit-notice on
Pkg-perl-cvs-commits mailing list