On 09/10/15 16:57, Yuri D'Elia wrote: >> If you do the steps I posted, is the service re-enabled for you? > > No it's not, as expected.
Ok, just updated from 227-1 to 227-2 using aptitude: Performing actions... Preconfiguring packages ... (Reading database ... 35322 files and directories currently installed.) Preparing to unpack .../archives/udev_227-2_i386.deb ... Unpacking udev (227-2) over (227-1) ... Preparing to unpack .../libudev1_227-2_i386.deb ... Unpacking libudev1:i386 (227-2) over (227-1) ... <snip> Processing triggers for man-db (2.7.4-1) ... Processing triggers for libc-bin (2.19-22) ... Setting up libsystemd0:i386 (227-2) ... Setting up udev (227-2) ... addgroup: The group `input' already exists as a system group. Exiting. Setting up systemd (227-2) ... Created symlink from /etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service to /lib/systemd/system/systemd-timesyncd.service. addgroup: The group `systemd-journal' already exists as a system group. Exiting. Setting up systemd-sysv (227-2) ... Setting up libpam-systemd:i386 (227-2) ... Processing triggers for dbus (1.10.0-3) ... Processing triggers for libc-bin (2.19-22) ... Press Return to continue. # systemctl is-enabled systemd-timesyncd.service enabled