packages/net/acme-acmesh, branch master

acme-acmesh: conflict with uacme

2026-10-30T05:33:29Z

acme-acmesh and uacme both install /usr/lib/acme/hook, the script that /etc/init.d/acme from acme-common runs. So only one of the two clients can be in use, but nothing marks them as conflicting. Their shared provide acme is virtual, so apk accepts both and then fails with an overwrite error for the hook when the second client is installed. Declare the conflict on acme-acmesh, because uacme-ualpn and uacme-dnsapi-adapter select uacme. Packages that depend on acme, like luci-app-acme, select acme-acmesh only when uacme is not built in. Checked with defconfig: acme-acmesh drops to m when uacme or uacme-ualpn is selected, and uacme-dnsapi-adapter or luci-app-acme next to uacme do not select it. Signed-off-by: Josef Schlehofer

acme-acmesh: update to 3.1.4

2026-09-18T16:26:45Z

Update acme.sh to 3.1.4. Release note: https://github.com/acmesh-official/acme.sh/releases/tag/3.1.4 Signed-off-by: Christian Wengel

net/acme-acmesh: prevent concurrent execution of acme.sh instances

2026-08-31T13:27:49Z

After switching ACME to being run through procd, individual ACME instances are now executed in parallel instead of sequentially. This causes acme.sh to become confused in certain cases. Petr reported that certificate files ended up with the wrong contents after updating to OpenWrt 25.12. Fix this by wrapping the acme.sh execution in a global `flock` keyed on a file in the state directory. The procd instances will still run in parallel, but they'll all serialise on the same lock, so only one acme.sh instance will run at a time. Fixes: 76b676e4ebbb ("acme.sh: move to procd to ensure logging gets to syslog") Reported-by: Petr Novák Signed-off-by: Toke Høiland-Jørgensen

acme-common: move nftables rule to hook

2026-07-04T15:27:50Z

The nftables rule in acme-common partially works, but it races against the acme.sh and uacme client. While the client is performing the renew the rule is being deleted because the client is run in the background. This change moves the rule management to the hook instead. While duplicate rules could be created, the benefits outway the potential costs. It is unknown how many installations issue/renew multiple certificates. Signed-off-by: Michael A Cassaniti

acme-acmesh: remove duplicated notification on certificate renewal

2026-07-01T12:50:15Z

fix #29703 Signed-off-by: Juanyong Dong

acme-acmsh: bump acme.sh to 3.1.3

2026-05-15T09:04:11Z

update acme.sh version to 3.1.3 Signed-off-by: Seo Suchan

acme: make 'acme' keyword actually virtual

2026-05-15T09:04:11Z

before acme is an empty package that depend either acme-acmesh or uacme. but this boolean logic in depend ignored by apk itself. let's make a virtual keyword witch both acme.sh and uacme provides. acme.sh is explicit default. Signed-off-by: Seo Suchan

uacme: update to 1.8.1

2026-04-14T07:38:06Z

update uacme version to 1.8.1 , release upstream 2026/4/5 Signed-off-by: Seo Suchan

uacme: use acme-common

2026-04-14T07:38:06Z

remake uacme hook scripts to base on acme-common, and implements helper to able to use acme.sh DNS APIs Signed-off-by: Seo Suchan

acme: make virtual package satisfiable by uacme

2026-04-14T07:38:06Z

currently acme metapackage only able to satisfied with acme-acmesh, but make is satisfieable by uacme if it's already installed. still defaults to acme.sh Signed-off-by: Seo Suchan