Bug 238073 - security/acme-client: should either be retired or changed to rely on the OpenBSD base version
Summary: security/acme-client: should either be retired or changed to rely on the Open...
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: Bernard Spil
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-23 13:38 UTC by Peter Putzer
Modified: 2019-11-08 18:53 UTC (History)
6 users (show)

See Also:
bugzilla: maintainer-feedback? (brnrd)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Putzer 2019-05-23 13:38:52 UTC
The upstream "portable" version of acme-client is currently unmaintained (https://github.com/kristapsdz/acme-client-portable). The port should either be retired or changed to rely on the OpenBSD base version (https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.sbin/acme-client/).
Comment 1 Bernard Spil freebsd_committer freebsd_triage 2019-05-26 13:39:26 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.
Comment 2 Peter Putzer 2019-05-26 13:51:08 UTC
(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.
Comment 3 commit-hook freebsd_committer freebsd_triage 2019-05-26 14:55:21 UTC
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/
Comment 4 Bernard Spil freebsd_committer freebsd_triage 2019-05-26 14:57:41 UTC
I'm not going to have time to maintain a portable port either. Pitty, acme-client worked well for me!

Thanks Peter :D
Comment 5 Arnaud de Prelle 2019-05-28 15:14:47 UTC
Indeed, that's a pitty. I was also using this port since a long time w/o any trouble.
Comment 6 Bernard Spil freebsd_committer freebsd_triage 2019-05-28 19:26:24 UTC
(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.
Comment 7 Arnaud de Prelle 2019-05-28 19:34:02 UTC
(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.