On Mon, Jan 02, 2017 at 07:43:47PM +0200, Niko Tyni wrote: > I intend to convert the affected pkg-perl packages to use it and file > bugs for the rest (if any) in the next few days.
I've uploaded these: libnet-ssleay-perl_1.78-2 libcrypt-ssleay-perl_0.73.04-2 libcrypt-openssl-bignum-perl_0.07-2 libcrypt-openssl-dsa-perl_0.18-2 libcrypt-openssl-pkcs10-perl_0.16-2 libcrypt-openssl-pkcs12-perl_0.7-3 libcrypt-openssl-rsa-perl_0.28-5 libcrypt-openssl-x509-perl_1.8.7-3 libcrypt-smime-perl_0.19-2 Of those, I suspect at least libcrypt-smime-perl and libcrypt-openssl-pkcs12-perl were not strictly necessary and could probably coexist linked with different OpenSSL versions. But it didn't hurt to be on the safe side. I didn't touch libcrypt-openssl-random-perl as it looks quite clearly self-contained. I don't think any other packages on the earlier list are affected but I've only done a cursory check. > Once those are done, perl-openssl-defalts can Break all the earlier > versions to make sure all the packages get upgraded together (although > that's not strictly necessary for the jessie -> stretch upgrade as noted > earlier on this bug.) Will do this later, probably once these have migrated to stretch. -- Niko