Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

certbot-auto no longer works on any OS #240

Closed
carljohnstone opened this issue Mar 18, 2021 · 2 comments · Fixed by #235
Closed

certbot-auto no longer works on any OS #240

carljohnstone opened this issue Mar 18, 2021 · 2 comments · Fixed by #235

Comments

@carljohnstone
Copy link

See https://community.letsencrypt.org/t/certbot-auto-no-longer-works-on-debian-based-systems/139702/6

certbot-auto is no longer being supported, so therefore refuses to update/install certbot. This removal has been rolled out in monthly stages over the last few months. Their recommendation is to now use snap as the installation method.

When vcs is used as the install method, the certbot-auto script is called which now fails. As all the per-OS CI tests use the vcs installation method, this has had the effect of breaking CI for any change.

@carljohnstone carljohnstone changed the title certbot-auto is deprecated on all OS certbot-auto no longer works on any OS Mar 18, 2021
@carljohnstone
Copy link
Author

#235 #238 #239 are all PRs failing CI due to this issue

CallumBanbery added a commit to CallumBanbery/puppet-letsencrypt that referenced this issue Mar 21, 2021
As referenced in voxpupuli#240 the official installation method was changed
in December 2020, deprecating the use of the `certbot-auto` script,
and recommending `snap` as the primary package source.

As `snap` isn't yet a builtin package provider in Puppet and I don't
fancy creating a dependency on a third party module, nor do I want
to add a load of `exec` commands for managing snap packages I chose
to fix the VCS install method, and since it's used in the CI there's
less to change.

Since we can no longer use the `certbot-auto` script we should
follow the setup instructions provided by Letsencrypt's development
guide https://certbot.eff.org/docs/contributing.html.  Their guide
simply states to call a python script which configures the virtual
environment, and since the script is gone we no longer need the
VENV_PATH environment variable.

As the command needs to create a python virtual environment we
need to add the required package to the VCS dependencies, and from
testing I found there was no need to call the initialisation command
when installing from a package source, so I've made it conditional
to the VCS installation.

I've also taken the opportunity to update the version of `certbot`
that's checked out during VCS installation since `0.39.0` is now
around 1.5 years old.  Version `1.7.0` is the latest version that
is supported by Python 3.5 which is the lowest Python3 version
that's installed by default via package managers.
CallumBanbery added a commit to CallumBanbery/puppet-letsencrypt that referenced this issue Mar 21, 2021
As referenced in voxpupuli#240 the official installation method was changed
in December 2020, deprecating the use of the `certbot-auto` script,
and recommending `snap` as the primary package source.

As `snap` isn't yet a builtin package provider in Puppet and I don't
fancy creating a dependency on a third party module, nor do I want
to add a load of `exec` commands for managing snap packages I chose
to fix the VCS install method, and since it's used in the CI there's
less to change.

Since we can no longer use the `certbot-auto` script we should
follow the setup instructions provided by Letsencrypt's development
guide https://certbot.eff.org/docs/contributing.html.  Their guide
simply states to call a python script which configures the virtual
environment, and since the script is gone we no longer need the
VENV_PATH environment variable.

As the command needs to create a python virtual environment we
need to add the required package to the VCS dependencies, and from
testing I found there was no need to call the initialisation command
when installing from a package source, so I've made it conditional
to the VCS installation.

I've also taken the opportunity to update the version of `certbot`
that's checked out during VCS installation since `0.39.0` is now
around 1.5 years old.  Version `1.7.0` is the latest version that
is supported by Python 3.5 which is the lowest Python3 version
that's installed by default via package managers.
CallumBanbery added a commit to CallumBanbery/puppet-letsencrypt that referenced this issue Mar 21, 2021
As referenced in voxpupuli#240 the official installation method was changed
in December 2020, deprecating the use of the `certbot-auto` script,
and recommending `snap` as the primary package source.

As `snap` isn't yet a builtin package provider in Puppet and I don't
fancy creating a dependency on a third party module, nor do I want
to add a load of `exec` commands for managing snap packages I chose
to fix the VCS install method, and since it's used in the CI there's
less to change.

Since we can no longer use the `certbot-auto` script we should
follow the setup instructions provided by Letsencrypt's development
guide https://certbot.eff.org/docs/contributing.html.  Their guide
simply states to call a python script which configures the virtual
environment, and since the script is gone we no longer need the
VENV_PATH environment variable.

As the command needs to create a python virtual environment we
need to add the required package to the VCS dependencies, and from
testing I found there was no need to call the initialisation command
when installing from a package source, so I've made it conditional
to the VCS installation.

I've also taken the opportunity to update the version of `certbot`
that's checked out during VCS installation since `0.39.0` is now
around 1.5 years old.  Version `1.7.0` is the latest version that
is supported by Python 3.5 which is the lowest Python3 version
that's installed by default via package managers.
CallumBanbery added a commit to CallumBanbery/puppet-letsencrypt that referenced this issue Mar 21, 2021
As referenced in voxpupuli#240 the official installation method was changed
in December 2020, deprecating the use of the `certbot-auto` script,
and recommending `snap` as the primary package source.

As `snap` isn't yet a builtin package provider in Puppet and I don't
fancy creating a dependency on a third party module, nor do I want
to add a load of `exec` commands for managing snap packages I chose
to fix the VCS install method, and since it's used in the CI there's
less to change.

Since we can no longer use the `certbot-auto` script we should
follow the setup instructions provided by Letsencrypt's development
guide https://certbot.eff.org/docs/contributing.html.  Their guide
simply states to call a python script which configures the virtual
environment, and since the script is gone we no longer need the
VENV_PATH environment variable.

As the command needs to create a python virtual environment we
need to add the required package to the VCS dependencies, and from
testing I found there was no need to call the initialisation command
when installing from a package source, so I've made it conditional
to the VCS installation.

I've also taken the opportunity to update the version of `certbot`
that's checked out during VCS installation since `0.39.0` is now
around 1.5 years old.  Version `1.7.0` is the latest version that
is supported by Python 3.5 which is the lowest Python3 version
that's installed by default via package managers.
CallumBanbery added a commit to CallumBanbery/puppet-letsencrypt that referenced this issue Mar 22, 2021
As referenced in voxpupuli#240 the official installation method was changed
in December 2020, deprecating the use of the `certbot-auto` script,
and recommending `snap` as the primary package source.

As `snap` isn't yet a builtin package provider in Puppet and I don't
fancy creating a dependency on a third party module, nor do I want
to add a load of `exec` commands for managing snap packages I chose
to fix the VCS install method, and since it's used in the CI there's
less to change.

Since we can no longer use the `certbot-auto` script we should
follow the setup instructions provided by Letsencrypt's development
guide https://certbot.eff.org/docs/contributing.html.  Their guide
simply states to call a python script which configures the virtual
environment, and since the script is gone we no longer need the
VENV_PATH environment variable.

As the command needs to create a python virtual environment we
need to add the required package to the VCS dependencies, and from
testing I found there was no need to call the initialisation command
when installing from a package source, so I've made it conditional
to the VCS installation.

I've also taken the opportunity to update the version of `certbot`
that's checked out during VCS installation since `0.39.0` is now
around 1.5 years old.  Version `1.7.0` is the latest version that
is supported by Python 3.5 which is the lowest Python3 version
that's installed by default via package managers.
CallumBanbery added a commit to CallumBanbery/puppet-letsencrypt that referenced this issue Mar 22, 2021
As referenced in voxpupuli#240 the official installation method was changed
in December 2020, deprecating the use of the `certbot-auto` script,
and recommending `snap` as the primary package source.

As `snap` isn't yet a builtin package provider in Puppet and I don't
fancy creating a dependency on a third party module, nor do I want
to add a load of `exec` commands for managing snap packages I chose
to fix the VCS install method, and since it's used in the CI there's
less to change.

Since we can no longer use the `certbot-auto` script we should
follow the setup instructions provided by Letsencrypt's development
guide https://certbot.eff.org/docs/contributing.html.  Their guide
simply states to call a python script which configures the virtual
environment, and since the script is gone we no longer need the
VENV_PATH environment variable.

As the command needs to create a python virtual environment we
need to add the required package to the VCS dependencies, and from
testing I found there was no need to call the initialisation command
when installing from a package source, so I've made it conditional
to the VCS installation.

I've also taken the opportunity to update the version of `certbot`
that's checked out during VCS installation since `0.39.0` is now
around 1.5 years old.  Version `1.7.0` is the latest version that
is supported by Python 3.5 which is the lowest Python3 version
that's installed by default via package managers.
CallumBanbery added a commit to CallumBanbery/puppet-letsencrypt that referenced this issue Mar 22, 2021
As referenced in voxpupuli#240 the official installation method was changed
in December 2020, deprecating the use of the `certbot-auto` script,
and recommending `snap` as the primary package source.

As `snap` isn't yet a builtin package provider in Puppet and I don't
fancy creating a dependency on a third party module, nor do I want
to add a load of `exec` commands for managing snap packages I chose
to fix the VCS install method, and since it's used in the CI there's
less to change.

Since we can no longer use the `certbot-auto` script we should
follow the setup instructions provided by Letsencrypt's development
guide https://certbot.eff.org/docs/contributing.html.  Their guide
simply states to call a python script which configures the virtual
environment, and since the script is gone we no longer need the
VENV_PATH environment variable.

As the command needs to create a python virtual environment we
need to add the required package to the VCS dependencies, and from
testing I found there was no need to call the initialisation command
when installing from a package source, so I've made it conditional
to the VCS installation.

I've also taken the opportunity to update the version of `certbot`
that's checked out during VCS installation since `0.39.0` is now
around 1.5 years old.  Version `1.7.0` is the latest version that
is supported by Python 3.5 which is the lowest Python3 version
that's installed by default via package managers.
@ekohl ekohl linked a pull request Jun 30, 2021 that will close this issue
@ekohl
Copy link
Member

ekohl commented Jun 30, 2021

We ended up removing VCS support in ee77abc and always use packages.

@ekohl ekohl closed this as completed Jun 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants