Bug#947936: marked as done (chrony: Does (still) not start properly on boot on buster)

[Debian Bug Tracking System]

Your message dated Wed, 11 Mar 2020 20:50:26 +0000
with message-id <E1jC8J8-000E0z-1a at fasolo.debian.org>
and subject line Bug#947936: fixed in chrony 3.5-6
has caused the Debian Bug report #947936,
regarding chrony: Does (still) not start properly on boot on buster
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.)


-- 
947936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947936
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Santiago Vila <sanvila at unex.es>
Subject: chrony: Does (still) not start properly on boot on buster
Date: Thu, 2 Jan 2020 13:38:17 +0100 (CET)
Size: 7436
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20200311/5b1cd1ec/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Debian FTP Masters <ftpmaster at ftp-master.debian.org>
Subject: Bug#947936: fixed in chrony 3.5-6
Date: Wed, 11 Mar 2020 20:50:26 +0000
Size: 5783
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20200311/5b1cd1ec/attachment-0001.mht>