On Tue, Jan 28, 2025 at 19:07:51 +0100, Patrice Duroux wrote: > Of course, maybe I misspoke but my point wasn't about the configuration files > remaining as expected just removing the package and not purging it. It is > about > the broken symlink to its service file which is for sure no more present > whatever a removal or a purge. Or is such a symlink considered as part of > configuration files? I don't think so, but I might be wrong.
The question is about this dangling symlink: hobbit:/etc/systemd/system$ ls -l dbus-org.freedesktop.timesync1.service lrwxrwxrwx 1 root root 45 Feb 17 2024 dbus-org.freedesktop.timesync1.service -> /lib/systemd/system/systemd-timesyncd.service hobbit:/etc/systemd/system$ ls -lL dbus-org.freedesktop.timesync1.service ls: cannot access 'dbus-org.freedesktop.timesync1.service': No such file or directory This symlink is not part of the package's inventory: hobbit:~$ dpkg -l systemd-timesyncd | tail -n1 rc systemd-timesyncd 252.22-1~deb12u1 amd64 minimalistic service to synchronize local time with NTP servers hobbit:~$ dpkg -L systemd-timesyncd /etc /etc/dhcp /etc/dhcp/dhclient-exit-hooks.d /etc/dhcp/dhclient-exit-hooks.d/timesyncd /etc/systemd /etc/systemd/timesyncd.conf I'm unclear on exactly how this symlink gets created. (If I still had the package installed, I would look at the postinst script and so on, but since I've removed the package, that's more difficult. Also, <http://packages.debian.org/systemd-timesyncd> is not responding at the moment.) As far as I can tell, the dangling symlink is not doing any harm. Therefore, I've never felt any need to investigate it.
