Bug#848113: libcrypt-openssl-rsa-perl: binary incompatibility with libcrypt-openssl-pkcs10-perl (openssl versions)

Sebastian Andrzej Siewior sebastian at breakpoint.cc
Sat Dec 17 20:35:16 UTC 2016


On 2016-12-17 20:38:43 [+0200], Niko Tyni wrote:
> > > For reference, here's a list of lib.*-perl packages depending on libssl1.*.
> > As of unstable, there should be nothing perl related depending on libssl1.0.
> > If there is then please let me know because it probably might be good to
> > port it to 1.1.
> 
> I see three here:
> 
>   # grep-dctrl -P perl /var/lib/apt/lists/localhost:3142_debian_dists_unstable_main_binary-amd64_Packages|grep-dctrl -n -sPackage -FDepends libssl1.0
>   liblasso-perl
lasso, does not look like perl. A binNMU worked on 2016-08-26.

>   libnet-ldns-perl
and this binNMUed just fine. Missed that because it does not depend on
libssl-dev.

Two binNMUs here and we should be good here…

>   libsnmp-perl
and this looks problematic. This is from net-snmp. There is another RC
bug asking to stay with 1.0 due to libssh. The .so files within
libsnmp-perl are linked against libcrypto.so.1.0.2. I can't find a
single symbol that is exported by libcrypto and required by any of the
.so files within libsnmp-perl. So I *think* there is no need for the
perl package to link against libcrypto and we can ignore this one.
Given that I think we could leave net-snmp with 1.0 for Stretch.

Sebastian



More information about the pkg-perl-maintainers mailing list