Bug#801389: Disabling timedatectl/NTP across package upgrades

[Yuri D'Elia]

On 09/10/15 16:08, Michael Biebl wrote:
>> I'm following unstable on a KVM instance where I explicitly do not want
>> time sync, so I'm unsure on which version this got re-enabled.
>>
>> I noticed this issue some months ago, where I disabled the service on
>> two occasions, then tried using timedatectl, and noticed today that the
>> service got re-enabled again just before reporting the issue.
> 
> You are saying that the service was disabled before the 227-1 update and
> re-enabled after the 227-1 update?
> How do you know it was disabled before the update?

I know it was disabled only before the 226-1 upgrade. I cannot be sure
if that's the package upgrade process that enabled the service again though.

> Yes, for systemd-timesyncd it was always there.
> We started enabled timesyncd by default in 219-1 and the code to not
> re-enable services on upgrades was added way before in 214-1
> 
> Please double check if it's really the systemd upgrade which re-enables
> the service.

I'll have a closer look at the logs and see if I can find what enabled
it again.

> If you do the steps I posted, is the service re-enabled for you?

No it's not, as expected.