From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Package request: uacme
Date: Sun, 24 Jul 2022 11:04:18 +0200 [thread overview]
Message-ID: <20220724090418.l8n46bvHqAlIE6EnrM5jz470ppUcCht2BZHRkaSyAl0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38155@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]
Closed issue by dirkson on void-packages repository
https://github.com/void-linux/void-packages/issues/38155
Description:
### Package name
uacme
### Package homepage
https://github.com/ndilieto/uacme
### Description
An ACMEv2 client written in C. Basically a Let'sEncrypt client. I think just making the binary available is enough - The rest of the config is specific to each user.
For our distro it would depend on openssl and libcurl .
Releases are provided as git tags in the upstream/latest branch, as per the readme. Anything here ( https://github.com/ndilieto/uacme/tags ) with the tag 'upstream/x.x.x' is considered a release. This is an unusual method of packaging releases, but I don't see where it fails to meet any void requirements because of it.
I've been using this in a light production environment since 2020. I believe I started using it because it was the only Let'sEncrypt client I could find that would allow me to get an ECC cert.
### Does the requested package meet the quality requirements?
System, Compiled
### Is the requested package released?
Yes
prev parent reply other threads:[~2022-07-24 9:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 17:46 [ISSUE] Package request: dirkson
2022-07-24 9:04 ` sgn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220724090418.l8n46bvHqAlIE6EnrM5jz470ppUcCht2BZHRkaSyAl0@z \
--to=sgn@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).