Bug#883241: marked as done (chrony: daemon doesn't automatically start)

[Debian Bug Tracking System]

Your message dated Mon, 2 Dec 2019 17:35:38 +0100
with message-id <ca969538-13eb-8628-e0a2-8bfedc38aa6f at debian.org>
and subject line Re: Bug#883241: chrony: daemon doesn't automatically start
has caused the Debian Bug report #883241,
regarding chrony: daemon doesn't automatically start
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.)


-- 
883241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883241
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Andres Salomon <dilinger at queued.net>
Subject: chrony: daemon doesn't automatically start
Date: Fri, 1 Dec 2017 00:38:26 -0800
Size: 3358
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20191202/2d97a102/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Michael Biebl <biebl at debian.org>
Subject: Re: Bug#883241: chrony: daemon doesn't automatically start
Date: Mon, 2 Dec 2019 17:35:38 +0100
Size: 7875
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20191202/2d97a102/attachment-0001.mht>