Bug 207532 - security/letsencrypt.sh weekly fails because curl not in path
Summary: security/letsencrypt.sh weekly fails because curl not in path
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Kurt Jaeger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-26 21:15 UTC by mjl
Modified: 2016-02-27 17:29 UTC (History)
2 users (show)

See Also:
sascha: maintainer-feedback+


Attachments
Periodic script fix (824 bytes, patch)
2016-02-27 16:08 UTC, Sascha Holzleiter
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description mjl 2016-02-26 21:15:04 UTC
I have weekly_letsencrypt_enable="YES" in my /etc/periodic.conf, but last night the letsencrypt run failed, with:

ERROR: This script requires curl.

in the weekly run output email.  I have curl installed from ports.  I think the issue is that PATH does not include /usr/local/bin, where curl is present, when the periodic script is run.
Comment 1 Sascha Holzleiter 2016-02-27 16:08:31 UTC
Created attachment 167482 [details]
Periodic script fix
Comment 2 Sascha Holzleiter 2016-02-27 16:09:23 UTC
Good catch, thanks! The added patch should fix that.
Comment 3 commit-hook freebsd_committer freebsd_triage 2016-02-27 17:29:18 UTC
A commit references this bug:

Author: pi
Date: Sat Feb 27 17:29:05 UTC 2016
New revision: 409674
URL: https://svnweb.freebsd.org/changeset/ports/409674

Log:
  security/letsencrypt.sh: periodic script needs to find curl in $PATH

  PR:		207532
  Reported by:	mjl@luckie.org.nz
  Submitted by:	Sascha Holzleiter <sascha@root-login.org> (maintainer)

Changes:
  head/security/letsencrypt.sh/Makefile
  head/security/letsencrypt.sh/files/000.letsencrypt.sh.in
Comment 4 Kurt Jaeger freebsd_committer freebsd_triage 2016-02-27 17:29:42 UTC
Committed, thanks.