Date: Tue, 26 May 2020 19:44:01 -0700 From: Pete Wright <pete@nomadlogic.org> To: Jan Beich <jbeich@FreeBSD.org> Cc: FreeBSD <freebsd-ports@freebsd.org> Subject: Re: might need to bump version of python ports after recent openssl changes Message-ID: <418f2bab-7d50-ae90-185c-d7d3a26a07aa@nomadlogic.org> In-Reply-To: <sgfm-azdx-wny@FreeBSD.org> References: <63bc596e-0e78-7ed0-236e-5a11f017ba26@nomadlogic.org> <sgfm-azdx-wny@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5/26/20 5:24 PM, Jan Beich wrote: > Pete Wright <pete@nomadlogic.org> writes: > >> 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... > OSVERSION was already bumped in base r361410, so poudriere will > force-rebuild all packages. Those who hack .jailversion to avoid > rebuilds can only blame themselves. I don't do that - this is on two non-jailed systems running CURRENT so I'm not sure what you are inferring. a forced an update of the pkg cache and still did not pick up the new version with a pkg upgrade. The only way to fix this was to do a "pkg install -f python37" in my case. i have left one system in this state to aid with testing if there is any interest. if not no skin off my back... -p -- Pete Wright pete@nomadlogic.org @nomadlogicLA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?418f2bab-7d50-ae90-185c-d7d3a26a07aa>