From owner-freebsd-ports@freebsd.org Wed May 27 02:24:29 2020 Return-Path: Delivered-To: freebsd-ports@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 22FE82FBF02 for ; Wed, 27 May 2020 02:24:29 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49WvmD6cDKz4Pdn; Wed, 27 May 2020 02:24:28 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1354) id D821EB451; Wed, 27 May 2020 02:24:28 +0000 (UTC) From: Jan Beich To: Pete Wright Cc: FreeBSD Subject: Re: might need to bump version of python ports after recent openssl changes References: <63bc596e-0e78-7ed0-236e-5a11f017ba26@nomadlogic.org> Date: Wed, 27 May 2020 04:24:26 +0200 In-Reply-To: <63bc596e-0e78-7ed0-236e-5a11f017ba26@nomadlogic.org> (Pete Wright's message of "Tue, 26 May 2020 17:01:43 -0700") Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 May 2020 02:24:29 -0000 Pete Wright 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=C2=A0 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): > =C2=A0 File "", line 1, in > =C2=A0 File "/usr/local/lib/python3.7/ssl.py", line 98, in > =C2=A0=C2=A0=C2=A0 import _ssl=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 # 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=20 > 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?=C2=A0 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.