Date: Tue, 26 May 2020 17:01:43 -0700 From: Pete Wright <pete@nomadlogic.org> To: FreeBSD <freebsd-ports@freebsd.org> Subject: might need to bump version of python ports after recent openssl changes Message-ID: <63bc596e-0e78-7ed0-236e-5a11f017ba26@nomadlogic.org>
next in thread | raw e-mail | index | archive | help
hello - on current i found myself in a situation where python37 was unable to import ssl: $ python3.7 Python 3.7.7 (default, May 9 2020, 01:37:42) [Clang 10.0.0 (git@github.com:llvm/llvm-project.git llvmorg-10.0.0-0-gd32170dbd on freebsd13 Type "help", "copyright", "credits" or "license" for more information. >>> import ssl Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/local/lib/python3.7/ssl.py", line 98, in <module> import _ssl # if we can't import it, let the error propagate ImportError: /usr/local/lib/python3.7/lib-dynload/_ssl.so: Undefined symbol "SSLv3_method@OPENSSL_1_1_0" >>> after a little digging it looks like we recently disabled SSLv3 on CURRENT (huzzah!): https://reviews.freebsd.org/D24945 After forcing a re-install of python37 things are working again as it looked like the pbuilder did rebuild python after this commit. But pkg upgrade didn't detect a new version, so I think it might be helpful to bump the python version's so that people on CURRENT don't end up in the same situation I was in? Not sure what the usual process is for stuff like this... cheers, -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?63bc596e-0e78-7ed0-236e-5a11f017ba26>