You have recently updated the letsencrypt software to use a new name.
It was called letsencrypt, like the command itself was named like that as well. It had been renamed to certbot, but the examples still use 'letsencrypt' (like pkg-message).
In addition, if you use the 'certbot' command standalone, you will get a help message that states;
No installers are available on your OS yet; try running "letsencrypt-auto certonly" to get a cert you can install manually
which also still mentions letsencrypt-auto in this case. Is this something we can change or ask upstream to clarify?
Would it be wise to have an entry in UPDATING so that people know that the commands change, and perhaps instruct on how to have a clean upgrade?
Thanks in advance, and thanks for your work! It is appreciated :)
Over to last committer
Remko, if you have proposals for changes in mind, please feel free to attach a patch
Thank you for the report
(In reply to Kubilay Kocak from comment #1)
I'll leave that at the discretion of the committer. I do not have the time nor wish to generate patches. I do think that an UPDATING entry should have been placed with this rename.
Something in the lines of:
Rename py-letsencrypt to py-certbot to follow the official name change. To upgrade your software use ``pkg set -o security/py-letsencrypt:security/py-certbot py27-letsencrypt´'.
Please update all your scripts, applications, cronjobs and such to use the 'certbot' application.
... or something similiar.
Thank feedback should be sufficient, thank you Remko
A commit references this bug:
Date: Fri Jun 24 21:21:08 UTC 2016
New revision: 417447
security/py-certbot: Complete renaming from letsencrypt
- Rename relevant occurences in pkg-descr and pkg-message
The review I had created contained an UPDATING entry. Feedback from portmgr was that `pkg` takes care of this and renames don't require an UPDATING entry.