You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I installed Certbot with (snap, OS package manager, pip, certbot-auto, etc):
apt-get
I ran this command and it produced this output:
# certbot --version
certbot 1.21.0
Certbot's behavior differed from what I expected because:
It is typical to expect that packages in repositories to be at least reasonably up-to-date. This is what caused me to open ticket #9903.
What I would like:
For the Certbot maintainers to contact the Debian package maintainers, explain that Certbot is now a snap, the Debian package version is old and buggy, and that you would either like them to remove the package or replace it with a stub that prints out something about "use the snap instead".
The text was updated successfully, but these errors were encountered:
@paulehoffman, I doubt Debian will ship such stupid snap stubs. Debian 12 ships certbot 2.1.0. If you'd like to run this version on an older Debian version, you'd need to ask for a backport in the Debian backports project. Otherwise, you can still install any version you like via the pip installation method, on any Debian version you like.
My operating system is (include version):
Any recent version of Debian or Ubuntu
I installed Certbot with (snap, OS package manager, pip, certbot-auto, etc):
apt-get
I ran this command and it produced this output:
Certbot's behavior differed from what I expected because:
It is typical to expect that packages in repositories to be at least reasonably up-to-date. This is what caused me to open ticket #9903.
What I would like:
For the Certbot maintainers to contact the Debian package maintainers, explain that Certbot is now a snap, the Debian package version is old and buggy, and that you would either like them to remove the package or replace it with a stub that prints out something about "use the snap instead".
The text was updated successfully, but these errors were encountered: