Bug#968105: marked as done (chrony still not started by systemd (on Buster))

[Debian Bug Tracking System]

Your message dated Wed, 12 Aug 2020 20:56:54 +0200
with message-id <0d52aedd-eaf3-82d1-74f1-4a3a606285ed at debian.org>
and subject line Re: Bug#968105: chrony still not started by systemd (on Buster)
has caused the Debian Bug report #968105,
regarding chrony still not started by systemd (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.)


-- 
968105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968105
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Harald Dunkel <harri at afaics.de>
Subject: chrony still not started by systemd (on Buster)
Date: Sat, 8 Aug 2020 19:41:12 +0200
Size: 3346
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20200812/f2d61cbc/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Michael Biebl <biebl at debian.org>
Subject: Re: Bug#968105: chrony still not started by systemd (on Buster)
Date: Wed, 12 Aug 2020 20:56:54 +0200
Size: 8902
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20200812/f2d61cbc/attachment-0001.mht>