From owner-freebsd-questions@freebsd.org Mon Feb 22 15:52:35 2021 Return-Path: Delivered-To: freebsd-questions@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 D2D3A543860 for ; Mon, 22 Feb 2021 15:52:35 +0000 (UTC) (envelope-from jerry@seibercom.net) Received: from mail-qk1-x72e.google.com (mail-qk1-x72e.google.com [IPv6:2607:f8b0:4864:20::72e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DkmsZ5wtjz3qvQ for ; Mon, 22 Feb 2021 15:52:34 +0000 (UTC) (envelope-from jerry@seibercom.net) Received: by mail-qk1-x72e.google.com with SMTP id 81so13001568qkf.4 for ; Mon, 22 Feb 2021 07:52:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=seibercom.net; s=google; h=date:from:to:subject:message-id:in-reply-to:references:reply-to :organization:mime-version; bh=v/mdtqQmjTbnKZrkuzw9kfaYTjKpoN3tyEImn9E1UP8=; b=VGaYYosag7UEaMzWjOONOSiU5iUZnze6SCUZrpWwNfIrSif9oqCfH2Y7cTOoZ2PWpc ndiNh8HdKS89l0GVdymsN4EAvhsdjZ4NRXFtPjX3mOoZfsNlMl5ka3bB6WsRDyiXPj+s SZE/He+oASvmU5Gb46QITuUG0ITheMo50h0SQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:reply-to:organization:mime-version; bh=v/mdtqQmjTbnKZrkuzw9kfaYTjKpoN3tyEImn9E1UP8=; b=NuPxUXCtbnQOgE2BZ4AJ0aUPbDFXPAX5YzitB2vZZEdUy4DW8ZLPgv5U86PkXJ4qKK a9WvMQgPX6j6yV3oXokbfmHFSt5C0zmurXVUGuQGqbdXj1bnpy/RkXPw17qwUQSAiJov vW796pPtBcO598VtRtmEbIDArCkTKh2QgDNm1B7Pxf1/XlMwIXdwMgp3Zy04hBV7P9/R DtUslHOlpZmt0cDuVsKidGhaVjVqP6hQuDaKP5R32Re8n4WXBwyiZRZJhE6PbF/mj2Gg iq1IMsD6DEXMKTEoZajT7a0L0E+qZwf6z4pHjnvwis3bRY8CykW3K4IP6edtS85YqrIV eANQ== X-Gm-Message-State: AOAM5334NJvKIgMpYy5+LmxpSpHDiDmcy/wD3yfrqpZ7xj8DShXBIOAs 2BnDnpBkS9M1969JB5m9gFHP03IzucratA== X-Google-Smtp-Source: ABdhPJyMXsc++zSU3n5/CXXHlsACcwgAZwgt+3iGrDlT7Mh0TomOhgw7AZyKSDeqYD5TY47iUZmLqQ== X-Received: by 2002:ae9:f442:: with SMTP id z2mr5986452qkl.303.1614009153284; Mon, 22 Feb 2021 07:52:33 -0800 (PST) Received: from scorpio.seibercom.net (cpe-174-109-231-236.nc.res.rr.com. [174.109.231.236]) by smtp.gmail.com with ESMTPSA id y15sm2784990qtb.29.2021.02.22.07.52.31 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 22 Feb 2021 07:52:32 -0800 (PST) Received: from localhost (zeus.seibercom.net [192.168.1.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: jerry@seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 4DkmsW0NGZz1Fr4 for ; Mon, 22 Feb 2021 10:52:31 -0500 (EST) Date: Mon, 22 Feb 2021 10:52:12 -0500 From: Jerry To: freebsd-questions@freebsd.org Subject: Re: Certbot crashes after update of python installed Message-ID: <20210222105212.00004188@seibercom.net> In-Reply-To: <410a3440-45a2-cad8-b186-19e7e7945366@tundraware.com> References: <018a01d70888$7b2fe5b0$718fb110$@seibercom.net> <20210221205146.364356E6BDB0@ary.qy> <6b735533-ad9a-441d-817f-afb4100b43bc@yggdrasil.evilham.com> <410a3440-45a2-cad8-b186-19e7e7945366@tundraware.com> Reply-To: freebsd-questions@freebsd.org Organization: seibercom.net X-Mailer: Claws Mail 3.17.4 (GTK+ 2.24.32; i686-w64-mingw32) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/nJORgLCKPwiTQU1iLHYPndR"; protocol="application/pgp-signature" X-Rspamd-Queue-Id: 4DkmsZ5wtjz3qvQ X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org; dkim=pass header.d=seibercom.net header.s=google header.b=VGaYYosa; dmarc=none; spf=pass (mx1.freebsd.org: domain of jerry@seibercom.net designates 2607:f8b0:4864:20::72e as permitted sender) smtp.mailfrom=jerry@seibercom.net X-Spamd-Result: default: False [1.56 / 15.00]; HAS_REPLYTO(0.00)[freebsd-questions@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; GREYLIST(0.00)[pass,meta]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; TO_DN_NONE(0.00)[]; HAS_ORG_HEADER(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; DKIM_TRACE(0.00)[seibercom.net:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RECEIVED_SPAMHAUS_PBL(0.00)[174.109.231.236:received]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; REPLYTO_EQ_TO_ADDR(5.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2607:f8b0:4864:20::72e:from]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.84)[-0.841]; R_DKIM_ALLOW(-0.20)[seibercom.net:s=google]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; DMARC_NA(0.00)[seibercom.net]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[2607:f8b0:4864:20::72e:from:127.0.2.255]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::72e:from]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-questions] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Feb 2021 15:52:35 -0000 --Sig_/nJORgLCKPwiTQU1iLHYPndR Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Mon, 22 Feb 2021 09:26:24 -0600, Tim Daneliuk stated: >On 2/22/21 1:20 AM, Evilham wrote: >>=20 >> It now requires version 3.2 or newer of the python cryptography >> package but=C2=A0the=C2=A0version=C2=A0in=C2=A0the=C2=A0ports=C2=A0and= =C2=A0packages=C2=A0is=C2=A0only=C2=A02.9.2. =20 > > >The best way around this is to install the 'pew' Python virtual >environment manager and create a Python 3 virtualenv into which you >install certbot. > >As a general practice, I avoid using system Python on any system under >my control. I also do not pip install much for the system instance of >the language. Pew/Virtualenvs give me a clean way to manage all that >without soiling the base installation with odd additions and updates. At the very least, there should be something in "UPDATING" that references this problem, and a reasonable method to work around this problem. --=20 Jerry --Sig_/nJORgLCKPwiTQU1iLHYPndR Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQGzBAEBCAAdFiEELeCiu2K+9VmEYYgTgHBP8gv9FXcFAmAz0zIACgkQgHBP8gv9 FXdprQv/esksOXeNGbPngOetsTvN4DlEcpIzxBei0YUVyRbCX0rrWacajN5xRU0m bcSv2HoNOcprq6DHzHzJJzlKeC+SXl8RqJOFY//IowXYd6lmprUynIpKJjJnsXQJ Zg7kuwJhOFMmhQ3LNGRs3h1opd9rGYq6hm/22MPVoLR1YUSK11eQibCIJifU1YgH JKxG8C7E/Va93fB83+9gs6REEOBQM+/uS5TIRLdLy1+8C2zcokhgRfyeNYeDkKi7 sGXvz/vWzSygMpwWiWwWOlIvvwDVo4GpJE4GXyFTU2pmUNkf8gO+L+eGNDspmH+z Ce27kGY6hDUBUQi155fk5Z4EcU3OsHYlwvsWMAhsvTijWiGYiLl7po8NgX474wmE n1VggdIawoJXmo+rOfKRjk/H4stZQIuk59q4fpdTx2pS9d+CIDB6HTy1TsLATE7b n9lna78+JIGTt9SG1wWq/r5ogxHMlpES+I/pnakf5WmhUHPmG8ojVPkfQzOk5PvC zWbigvyB =KH1Q -----END PGP SIGNATURE----- --Sig_/nJORgLCKPwiTQU1iLHYPndR--