Your message dated Tue, 21 May 2019 19:03:34 +
with message-id
and subject line Bug#924393: fixed in acme-tiny 1:4.0.4-1
has caused the Debian Bug report #924393,
regarding acme-tiny: Please update to ACMEv2 API
to be marked as done.
This means that you claim that the problem has been dealt
Hi all,
Uploaded to the DELAYED queue with 7 days delay.
On Sun, 12 May 2019 at 14:58, Samuel Henrique wrote:
> Hello Niels,
>
> Sorry for the delay on this.
>>
>
> No worries, I know you've been doing lots of work during the freeze, and I
> noticed that you also proactively unblocked some of m
nrique
Hi Samuel,
I have a question about bugs 905720 and 924393.
For both, you said there is a fix ([0]) and you mentionned the discution on
debian-devel list ([1]) related the first epoch for acme-tiny.
My question: do you think bug 905720 should be merged into bug 924393 ?
I looked at th
Control: tags -1 patch
Fix available on https://salsa.debian.org/samueloph/acme-tiny
Discussion about the epoch bump:
https://lists.debian.org/debian-devel/2019/04/msg00052.html
--
Samuel Henrique
Package: acme-tiny
Version: 20171115-2
Severity: serious
Hi,
the package is using the ACME-v1 API. Since v4.0.0 (available since Thu
Mar 15 22:03:38 2018 -0700) it is using the ACME-v2 API. One difference
is that the received certificate contains the parent certificate.
The important part and t
5 matches
Mail list logo