Summary: | security/letsencrypt.sh: Update to 0.3.0 | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | Sascha Holzleiter <sascha> | ||||||||||
Component: | Individual Port(s) | Assignee: | Thomas Zander <riggs> | ||||||||||
Status: | Closed FIXED | ||||||||||||
Severity: | Affects Only Me | CC: | riggs | ||||||||||
Priority: | --- | Keywords: | patch | ||||||||||
Version: | Latest | ||||||||||||
Hardware: | Any | ||||||||||||
OS: | Any | ||||||||||||
Attachments: |
|
Poudriere run: https://pkgs.blumenschaender.de/data/host_103amd64-default/2016-09-08_14h08m52s/logs/letsencrypt.sh-0.3.0.log Thank you Sascha. QA logs are not longer required as attachments, but are preferred if requested, over remote URL's, so that all information is self-contained in the issue. Unless requested, just mention that QA has passed in your descriptions, like: portlint: OK (looks fine.) testport: OK (poudriere: <versions>, <archs>, <options> tested) Feel free to include an UPDATING entry in the patch as well Forgot to note: UPDATING entries are preferable to pkg-messages for one-off version -> version updates/instructions and don't need to be removed in future commits like pkg-message messaging Created attachment 174531 [details]
v0.3.0 diff
Created attachment 174532 [details]
UPDATING entry
Thanks for clarifying! I've generated a new diff without the pkg-message warning and added an attachment with an UPDATING entry. Created attachment 174533 [details]
UPDATING entry
Forgot the obligatory "users of" phrase within AFFECTS:
A commit references this bug: Author: riggs Date: Sat Sep 10 16:21:53 UTC 2016 New revision: 421708 URL: https://svnweb.freebsd.org/changeset/ports/421708 Log: Update to upstream version 0.3.0 Detailed maintainer log regarding breaking upstream changes: - The config filename has been changed from "config.sh" to "config" - The WELLKNOWN location has been changed upstream to "/var/www/letsencrypt" The port uses "%%PREFIX%%/www/letsencrypt" in accordance to hier(7). PR: 212485 Submitted by: sascha@root-login.org (maintainer) Changes: head/security/letsencrypt.sh/Makefile head/security/letsencrypt.sh/distinfo head/security/letsencrypt.sh/files/000.letsencrypt.sh.in head/security/letsencrypt.sh/files/pkg-message.in A commit references this bug: Author: riggs Date: Sat Sep 10 16:31:58 UTC 2016 New revision: 421709 URL: https://svnweb.freebsd.org/changeset/ports/421709 Log: Document breaking upstream changes in security/letsencrypt.sh PR: 212485 Submitted by: sascha@root-login.org (maintainer security/letsencrypt.sh) Reviewed by: riggs Changes: head/UPDATING I have committed the UPDATING entry with modifications (wording) and changed author. Reason is that by convention a committer must be the author responsible for an UPDATING entry. |
Created attachment 174526 [details] v0.3.0 diff This patch updates letsencrypt.sh to Version 0.3.0 . There have been breaking changes upstream. I added a warning about it to pkg-message but maybe this should also go into UPDATING. The specifics: - The config filename has been changed from "config.sh" to "config" - The WELLKNOWN location has been changed upstream to "/var/www/letsencrypt". I patched that to be "%%PREFIX%%/www/letsencrypt" in accordance to hier(7). Both will require existing users to change their configs.