commit 59db46a016d269784791077998228ffab541fdfd Author: Matthew Thode <prometheanfire@gentoo.org> Date: Fri Sep 29 20:01:35 2017 -0500 dev-python/cryptography: stable for pike Package-Manager: Portage-2.3.8, Repoman-2.3.3 diff --git a/dev-python/cryptography/cryptography-2.0.2.ebuild b/dev-python/cryptography/cryptography-2.0.2.ebuild index 963e8c1c16d..c9d042f541e 100644 --- a/dev-python/cryptography/cryptography-2.0.2.ebuild +++ b/dev-python/cryptography/cryptography-2.0.2.ebuild @@ -14,7 +14,7 @@ SRC_URI="mirror://pypi/${PN:0:1}/${PN}/${P}.tar.gz" LICENSE="|| ( Apache-2.0 BSD )" SLOT="0" -KEYWORDS="~amd64 ~arm ~arm64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~x86" +KEYWORDS="amd64 arm arm64 hppa ia64 mips ppc ppc64 x86" Hi, you stabilised all arches for pike, but at least on ppc64, the upgrade from 1.7.1 broke my certbot install with errors like this: from cryptography.hazmat.bindings.openssl.binding import Binding File "/usr/lib64/python3.4/site-packages/cryptography/hazmat/bindings/openssl/binding.py", line 13, in <module> from cryptography.hazmat.bindings._openssl import ffi, lib ImportError: /usr/lib64/python3.4/site-packages/cryptography/hazmat/bindings/_openssl.abi3.so: undefined symbol: pthread_atfork cryptography-2.0.3.ebuild seems to add a blurb that adds -pthread to CFLAGS, which makes it work for me. Can we please stabilise 2.0.3 instead, or revbump 2.0.2 to include the pthread hack?
thanks, I've added the flag to 2.0.2-r1 and fast stabilized it
