Summary: | security/acme-client: should either be retired or changed to rely on the OpenBSD base version | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | Peter Putzer <freebsd> |
Component: | Individual Port(s) | Assignee: | Bernard Spil <brnrd> |
Status: | Closed FIXED | ||
Severity: | Affects Many People | CC: | arnaud, chris, jamie, jdjedesroches, leres, uqs |
Priority: | --- | Flags: | bugzilla:
maintainer-feedback?
(brnrd) |
Version: | Latest | ||
Hardware: | Any | ||
OS: | Any |
Description
Peter Putzer
2019-05-23 13:38:52 UTC
Hi Peter, You are correct. I'm currently not using acme-client a lot, any new configs I need use acme.sh. Would you be able to provide a patch? Otherwise I'll delete the port. (In reply to Bernard Spil from comment #1) In theory, yes, but I don't think I'll have the time in the near future. A commit references this bug: Author: brnrd Date: Sun May 26 14:54:34 UTC 2019 New revision: 502723 URL: https://svnweb.freebsd.org/changeset/ports/502723 Log: security/acme-client: Remove port - the Portable acme-client is no longer maintained upstream See: https://kristaps.bsd.lv/acme-client/ PR: 238073 Changes: head/MOVED head/security/Makefile head/security/acme-client/ I'm not going to have time to maintain a portable port either. Pitty, acme-client worked well for me! Thanks Peter :D Indeed, that's a pitty. I was also using this port since a long time w/o any trouble. (In reply to Arnaud de Prelle from comment #5) In private email I had someone that wants to try and create a FreeBSD version of the upstream release again. So hold on, it may return! Keep your cc on this thread, I hope not to forget to update here. (In reply to Bernard Spil from comment #6) Thanks @Bernard for this information. In the meantime I switched to the acme.sh port which does the job in an even simpler way. |