File "/usr/lib/python3.7/site-packages/OpenSSL/SSL.py", line 149, in <module> OP_NO_TLSv1_3 = _lib.SSL_OP_NO_TLSv1_3 AttributeError: module 'lib' has no attribute 'SSL_OP_NO_TLSv1_3' * ERROR: dev-python/slixmpp-1.5.2::gentoo failed (compile phase): * (no error message) * ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_developer-libressl-20201126-001816 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-10.2.0 * clang version 11.0.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/11/bin /usr/lib/llvm/11 11.0.0 Available Python interpreters, in order of preference: [1] python3.7 [2] python3.9 (fallback) [3] python3.8 (fallback) Available Ruby profiles: [1] ruby25 (with Rubygems) [2] ruby26 (with Rubygems) [3] ruby27 (with Rubygems) * Available Rust versions: [1] rust-bin-1.48.0 * The following VMs are available for generation-2: *) AdoptOpenJDK 8.272_p10 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 system-vm The Glorious Glasgow Haskell Compilation System, version 8.8.4 timestamp(s) of HEAD at this tinderbox image: /var/db/repos/gentoo Mon Nov 30 10:35:36 AM UTC 2020 /var/db/repos/libressl Sat Nov 28 07:41:42 PM UTC 2020 emerge -qpvO dev-python/slixmpp [ebuild N ] dev-python/slixmpp-1.5.2 USE="-test" PYTHON_TARGETS="python3_7 -python3_8"
Created attachment 675931 [details] emerge-info.txt
Created attachment 675934 [details] dev-python:slixmpp-1.5.2:20201130-130517.log
Created attachment 675937 [details] emerge-history.txt
Created attachment 675940 [details] environment
Created attachment 675943 [details] etc.portage.tbz2
Created attachment 675946 [details] temp.tbz2
Thanks for reporting. Seems to be exactly the same as what is discussed in https://bugs.gentoo.org/757738 . It seems that whatever is the resolution, there will be no changes to be made to slixmpp ebuild itself.
https://bugs.gentoo.org/757738 , which seems to be the only cause of this issue, is now resolved. I am not willing to test this myself now. Please reopen or raise anew if this issue reoccurs.
