1. with libressl-2.5.1 installed, triggers remerge of dev-perl/Net-SSLeay, which results in: SSLeay.xs: In function ‘XS_Net__SSLeay_set_state’: SSLeay.xs:4641:6: error: ‘SSL’ has no member named ‘state’ ssl->state = state; ^ make: *** [Makefile:359: SSLeay.o] Error 1 2. checkout 8d91ea8b7732fe2a8b4b13749987a130a3cd93e0 3. emerge libressl-2.5.0 to test the difference, Net-SSLeay merges fine. 4. retry libressl-2.5.1 -- same result What I've done is I've rolled back to 2.5.0 from an overlay until I have time to look into this or someone else does.
If you get time, can you report back on whether or not dev-perl/Net-SSLeay-1.800.0 (~arch) resolves this? Getting concrete understanding of support from upstream is hard for libressl :)
Sure, maybe in the next day or two. But I think this is an API change on the libressl 2.5.1 side which came weeks after Net-SSLeay-1.800.0. Moreover, I don't think there were any changes in 1.800.0 specific to libressl. Therefore this is a conflict. IMHO, libressl-2.5.0 needs to be put back until dependencies can be fixed.
(In reply to Dylan Carlson from comment #2) dev-perl/Net-SSLeay-1.800.0 compiles againstl ibressl-2.5.1 here at my hardened server
(In reply to Dylan Carlson from comment #2) > Moreover, I don't think there were any changes in 1.800.0 specific to > libressl. Therefore this is a conflict. > There probably isn't, but there was a fair few changes for OpenSSL 1.1 interop between 1.72 and 1.80[1] , and I'm just hoping blindly that the changes libressl introduced might have been similar to the ones OpenSSL introduced. 1.75 for instance mentions: + Testing with LibreSSL 2.4.1, with compatibility patch from Steffen + Ullrich. Thanks Steffen. And the docs now state: +LibreSSL is also supported. I know its a stretch though. :) 1: https://metacpan.org/diff/file?target=MIKEM%2FNet-SSLeay-1.80%2F&source=MIKEM%2FNet-SSLeay-1.72#Changes Though ideally this should eventually get reported upstream if upstreams version doesn't work.
Until we sort this out, 2.5.0 is back on the tree.
(In reply to Kent Fredric (IRC: kent\n) from comment #4) > > 1.75 for instance mentions: > + Testing with LibreSSL 2.4.1, with compatibility patch from Steffen > + Ullrich. Thanks Steffen. > Did not see that. Thanks for the correction. dev-perl/Net-SSLeay-1.800.0 compiles against dev-libs/libressl-2.5.1 successfully for me, seems to work fine. Cheers
For the record, dev-perl/Net-SSLeay-1.800.0 works. The reason why previous versions break is that in 2.5.1, the LibreSSL guys decided to hide a lot of public symbols which they deemed to be "revealing implementation details". net-misc/openconnect is also affected by this change.
adding to above: dev-python/cryptography-1.7.1, openvpn-2.4.0, and qtnetwork-5.6.2 (which I overlay patched for libressl-2.5.0) broke for me. Haven't gone into logs yet.
Please don't stack multiple failures into a single bug. Either this is a bug with Net-SSLeay, or its a tracker for libressl. But if its a tracker, each breakage should still be an individual bug.
Just for the record. Confirmed I am hitting this bug on arm arch. The workaround emerging =dev-perl/Net-SSLeay-1.800.0 works. Thanks,
dev-perl/Net-SSLeay-1.800.0 is now stable everywhere. commit f4a499d5c03a0046cf2f4c25c92cfb4356331be7 Author: Andreas K. Hüttel <dilfridge@gentoo.org> Date: Thu Mar 16 23:46:22 2017 +0100 dev-perl/Net-SSLeay: Remove old. Resolves bug 608050. Package-Manager: Portage-2.3.4, Repoman-2.3.2 dev-perl/Net-SSLeay/Manifest | 1 - dev-perl/Net-SSLeay/Net-SSLeay-1.720.0-r1.ebuild | 63 --------------------------------------------------------------- 2 files changed, 64 deletions(-)
