[ISSUE] Package request:

[ISSUE] Package request:

[dirkson]

[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]

New 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

Re: [ISSUE] [CLOSED] Package request: uacme

[sgn]

[-- 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