[Slackbuilds-users] letsencrypt updates

[Willy Sudiarto Raharjo]

Hi

If anyone wondered why there aren't any update to letsencrypt even
though new version gets released already, the answer is because there
has been a change upstream so it broke letsencrypt when deployed in
Slackware since 0.20.0 (https://github.com/certbot/certbot/issues/5332).

in short, they are checking for apache2ctl command instead of apachectl
which is by default used in Slackware. While they provided override
classes for other distributions, none for Slackware at this moment.

there are some solutions:
- ask for Patrick to add symlink in -stable (and -current)
- wait for upstream to fix the issue
- add the symlink manually
- someone make override class for Slackware and send PR to upstream

for those who prefer to try the third method, i have pushed a new branch
letsencrypt-review
(https://git.slackbuilds.org/slackbuilds/log/?h=letsencrypt-review) that
can be used to test the new version of letsencrypt, but please read the
README. You will also need josepy which is still in pending as a new
dependency for letsencrypt 0.21.0. Hopefully it can be merged in the
next public update.

I have tested 0.21.0 on a production machine with a manual symlink +
josepy and it worked fine for certificate renewals.


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180118/8a87ef0f/attachment.asc>