As usual no talking in here please.
If you have a package failing to compile against or working with >=dev-libs/openssl-1.1.0, file a new bug and make that new bug block this tracker bug.
Debian's build results:
Please address if setting OPENSSL_USE_DEPRECATED is an acceptable solution until upstream provide a proper fix.
*** Bug 614918 has been marked as a duplicate of this bug. ***
Maybe not passing "disable-deprecated" would help, it seems we are the only major distribution trying to disable them and probably causing most of the issues in reverse deps. In distributions like Debian, Fedora and OpenSuSE, it seems that most reverse are ok and they are using openssl-1.1 for some time :/
Author: Lars Wendler <email@example.com>
Date: Fri Mar 16 11:33:09 2018
dev-libs/openssl: Revbump to remove "disable-deprecated" option.
It breaks too many revdeps and many upstreams are not really eager to fix
them because "it works with deprecated features".
Package-Manager: Portage-2.3.24, Repoman-2.3.6
Maybe we could now have a separate tracker to try to unmask that revbumped version (we could suggest Toralf to run a tinderbox with that revision)
(In reply to Pacho Ramos from comment #6)
> Thanks! :)
> Maybe we could now have a separate tracker to try to unmask that revbumped
> version (we could suggest Toralf to run a tinderbox with that revision)
I doubt it. Gave that revbumped version a try yesterday and still had over a dozen of packages (among my 2000+ installed packages) that still don't build with openssl-1.1. I'm afraid that especially qt4 will be a showstopper until it finally got entirely removed from the tree.
Ah, the idea was to try to distinguish between old reported bugs regarding "deprecated" (that are likely harder to fix and make upstream to include the patch) than the new ones that would appear that we could try to handle "stealing" fixes from other distributions already shipping openssl-1.1
Depends on #673928