[Letsencrypt-devel] Bug#853242: marked as done (certbot: Renewal is set up in both cron and systemd - it should only exist in one)

Mon Jan 30 19:27:06 UTC 2017

Your message dated Mon, 30 Jan 2017 19:25:54 +0000
with message-id <45292D96-E218-4018-957A-F7B1D60E2B41 at debian.org>
and subject line Re: Bug#853242: certbot: Renewal is set up in both cron and systemd - it should only exist in one
has caused the Debian Bug report #853242,
regarding certbot: Renewal is set up in both cron and systemd - it should only exist in one
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)

-- 
853242: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853242
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Nye Liu <nyet at nyet.org>
Subject: certbot: Renewal is set up in both cron and systemd - it should only exist in one
Date: Mon, 30 Jan 2017 11:11:43 -0800
Size: 2506
URL: <http://lists.alioth.debian.org/pipermail/letsencrypt-devel/attachments/20170130/1a2f0d77/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: James Clarke <jrtc27 at debian.org>
Subject: Re: Bug#853242: certbot: Renewal is set up in both cron and systemd - it should only exist in one
Date: Mon, 30 Jan 2017 19:25:54 +0000
Size: 3650
URL: <http://lists.alioth.debian.org/pipermail/letsencrypt-devel/attachments/20170130/1a2f0d77/attachment-0001.mht>