Control: retitle -1 libcrypt-ssleay-perl: Missing dependency on liblwp-protocol-https-perl Control: forwarded -1 https://rt.cpan.org/Public/Bug/Display.html?id=73754
Hi On Tue, Jan 03, 2012 at 12:32:21AM +0100, gregor herrmann wrote: > On Wed, 20 Apr 2011 23:57:22 +0200, Sandro Tosi wrote: > > (New maintainer here :)) > > > > Checkgmail started to suddenly die with error message "Error: 500 Can't > > > connect > > > to www.google.com:443 (Crypt-SSLeay can't verify hostnames)". After some > > > time > > > spent with Google, I found that this problem is due to not installed > > > libio- > > > socket-ssl-perl. After installing this package checkgmail works as it > > > used to. > > > > > > Perhaps libio-socket-ssl-perl should be more likely be dependency of > > > libcrypt- > > > ssleay-perl, but this is more your decision than mine, as I don't know the > > > inner working of those modules. > > > > We are just using Crypt::SSLeay: > > > > $ grep -w use checkgmail | grep -i ssl > > use Crypt::SSLeay; > > > > so if this library needs libio-socket-ssl-perl it's its responsibility > > to add it, hence reassigning. > > Interesting. Crypt::SSLeay doesn't use IO::Socket::SSL; the nearest I > get is IO::Socket::INET in Net::SSL. > > (And checkgmail indeed doesn't use any IO::Socket::* anywhere.) > > Since libio-socket-ssl-perl depends on libcrypt-ssleay-perl, I'm not > going to introduce a circular dependency now. But we should find out > what's going on there ... It seems this was reported upstream as [1]. [1]: https://rt.cpan.org/Public/Bug/Display.html?id=73754 libio-socket-ssl-perl depends on libnet-ssleay-perl AFAICS, so adding a dependency for libcrypt-ssleay-perl on liblwp-protocol-https-perl should be fine. But I will doublecheck this, and then we can maybe upload the package with only the dependency added. (and ask for an unblock). (please do not upload libcrypt-ssleay-perl 0.60 yet) Regards, Salvatore
signature.asc
Description: Digital signature
