Date: Mon, 22 Feb 2021 12:16:14 -0600 From: "Dean E. Weimer" <dweimer@dweimer.net> To: Tim Daneliuk <tundra@tundraware.com> Cc: freebsd-questions@freebsd.org Subject: Re: Certbot crashes after update of python installed Message-ID: <cf62b748b2eac0cc4180c1cb40ece509@dweimer.net> In-Reply-To: <4e6bf84b-e68d-8506-281c-2810884cfee8@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> <20210222105212.00004188@seibercom.net> <4e6bf84b-e68d-8506-281c-2810884cfee8@tundraware.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2021-02-22 11:49 am, Tim Daneliuk wrote: > On 2/22/21 9:52 AM, Jerry wrote: >> At the very least, there should be something in "UPDATING" that >> references this problem, and a reasonable method to work around this >> problem. > > Well, Python 2.x has been noted as on its way to EOL for several years > and FreeBSD explicitly notes it as so. This seems like a non problem. > > > I have Python software that depends on 2.x and 3.x. To avoid having to > fiddle with what version is used where, I make use of the pew-based > solution which is simple puts what you need in distinct containers. Its not a Python 2.x to 3.x issue, its the Certbot dependency on py-openssl, the update made on Feb 19th to version 20.0.1 of py-openssl, missed a dependency requirement. I had mine working with python 3.9 for a while. It had recently broke after some updates, but I hadn't had time to look into yet. Here is what I found. from https://pypi.org/project/pyOpenSSL/ 20.0.0 (2020-11-27) Backward-incompatible changes: The minimum cryptography version is now 3.2. Remove deprecated OpenSSL.tsafe module. Removed deprecated OpenSSL.SSL.Context.set_npn_advertise_callback, OpenSSL.SSL.Context.set_npn_select_callback, and OpenSSL.SSL.Connection.get_next_proto_negotiated. Drop support for Python 3.4 Drop support for OpenSSL 1.0.1 and 1.0.2 So the real issue is the py-openssl port, and it looks like someone has already filed a bug report. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253711 -- Thanks, Dean E. Weimer http://www.dweimer.net/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cf62b748b2eac0cc4180c1cb40ece509>