[Slackbuilds-users] letsencrypt updates

[Jason Graham]

Can we just patch the OS_DEFAULTS in the configurator until an OS override
can be added upstream?

Jason

On Jan 18, 2018 3:40 PM, "Francois Gingras" <francois.gingras at gmail.com>
wrote:

>
> On Thu, Jan 18, 2018 at 2:51 PM, Eric Pratt <eric.b.pratt at gmail.com>
> wrote:
>
>> On Thu, Jan 18, 2018 at 5:50 AM, Willy Sudiarto Raharjo <
>> willysr at slackbuilds.org> wrote:
>>
>>> 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
>>>
>>>
>> ​I think the correct solution is for Patrick to add a symlink in the
>> distro.  Since apachectl is the default, I don't know why we would want
>> that changed in slackware.  Making apache2ctl a symlink to apachectl would
>> seem to be the right solution.  However, I don't really think it matters
>> which one is the symlink.​
>>
>> I suspect it was called apache2ctl originally so you could have apache
>> 1.x and 2.x installed side-by-side on the same box.  The only real problem
>> this would create would be a conflict if someone is actually still running
>> apache 1.x on modern Slackware distros.  I doubt that's the case, but it's
>> not beyond the realm of possibility.  In that case, I would rather see the
>> apachectl for apache 1.x be renamed to apache1ctl or something like that
>> than to see the one from apache 2.x renamed.
>>
>> Although, I think the best solution would be a combination of 1 and 4.
>> We should try to get the override class in place, but we should also try to
>> stick with the apache default as much as possible even if letsencrypt
>> weren't an issue here.
>>
>>
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>>
>>
> I'm -1 on renaming the apachectl script - the script is called as such
> upstream, and I can't see a single valid reason to rename it.
>
> Just because other debian-based distros did that doesn't mean it's the
> sane approach.
>
> Now, I do realize that we do have to "play ball" with other distro's
> quirks, unfortunately. As such, creating a symlink from apache2ctl ->
> apachectl is probably the least disruptive approach.
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180118/eb8e88ad/attachment.html>