From owner-freebsd-ports@freebsd.org Wed May 27 02:44:09 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 B8BAB2FC0EE for ; Wed, 27 May 2020 02:44:09 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [174.136.98.114]) (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 (2048 bits) client-digest SHA256) (Client CN "mail.nomadlogic.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49WwBw4D9lz4R6R; Wed, 27 May 2020 02:44:08 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.196] (cpe-23-243-161-111.socal.res.rr.com [23.243.161.111]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id da4d8057 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Wed, 27 May 2020 02:44:07 +0000 (UTC) Subject: Re: might need to bump version of python ports after recent openssl changes To: Jan Beich Cc: FreeBSD References: <63bc596e-0e78-7ed0-236e-5a11f017ba26@nomadlogic.org> From: Pete Wright Message-ID: <418f2bab-7d50-ae90-185c-d7d3a26a07aa@nomadlogic.org> Date: Tue, 26 May 2020 19:44:01 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: 49WwBw4D9lz4R6R X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of pete@nomadlogic.org designates 174.136.98.114 as permitted sender) smtp.mailfrom=pete@nomadlogic.org X-Spamd-Result: default: False [-2.46 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[nomadlogic.org]; NEURAL_HAM_LONG(-0.96)[-0.962]; NEURAL_HAM_MEDIUM(-0.99)[-0.990]; TO_DN_ALL(0.00)[]; NEURAL_HAM_SHORT(-0.21)[-0.210]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:25795, ipnet:174.136.96.0/20, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[23.243.161.111:received] 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:44:09 -0000 On 5/26/20 5:24 PM, Jan Beich wrote: > 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  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 "", line 1, in >>   File "/usr/local/lib/python3.7/ssl.py", line 98, in >>     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