Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 14 Jan 2020 02:46:03 +0000
From:      bugzilla-noreply@freebsd.org
To:        python@FreeBSD.org
Subject:   [Bug 239992] security/py-certbot@py27: script crashes with traceback
Message-ID:  <bug-239992-21822-JYV6ZXmQ0p@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-239992-21822@https.bugs.freebsd.org/bugzilla/>
References:  <bug-239992-21822@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D239992

--- Comment #3 from Kubilay Kocak <koobs@FreeBSD.org> ---
(In reply to jsmith from comment #2)

Python is EoL (as of Jan 1 2020), but is in sunset with a final release sti=
ll
to come (April, 2020 [1])

Nevertheless, Python 2.7 is set to be deprecated December 2020 in FreeBSD, =
with
work taking place to upgrade, or retire unmaintained an deprecated packages=
 in
the meantime.

What this means is that if an upstream package supports 2.7 and is maintain=
ed=20
(upstream and downstream), that it still ought to work, work meaning: gets
bugfixes if they are reproducible and resolvable

based on the description of the issue provided so far:

The first issue is the name of the executable changed from
/usr/local/bin/certbot to /usr/local/bin/certbot-2.7

This sounds like the default version of Python on that system is not 2.7. S=
ince
only the default version of Python ports/packages get canonical (not
version-suffixed script names, the lack of a certbot scriptname is intended=
. It
is up to the administrator to either:

 - Invoke python scripts using their script-X.Y version, OR
 - Ensure that if/when invoking <script> without a version suffix, ensure t=
hat
the systems configured default Python version is the one that's expected

On the second issue:

issue is running the new path of the script results in a Python traceback e=
rror
and no certificates being fetched

If this is still an issue, in any Python version of the certbot port, a full
command line invocation and traceback is what's required to isolate the iss=
ue,
along with information about where exactly said command points to (if one is
using 'certbot', not 'certbot-X.Y' as the invoking command

[1] "As a final service to the community, python-dev will bundle those fixe=
s --
and only those fixes -- into a final 2.7.18 release," the Python Foundation
noted in an update. "The release date for 2.7.18 will be in April 2020, bec=
ause
that allows time for the release managers to complete a release candidate a=
nd
final release."

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-239992-21822-JYV6ZXmQ0p>