Hi, On 17 February 2015 00:52:20 CET, Michael Biebl <bi...@debian.org> wrote: >Sort of. The plan here is, that the individual ntp implementations ship >a native systemd unit file, which has >Conflicts=systemd-timesyncd.service [1] > >This will make sure, that if e.g. ntp is installed and enabled, ntp >will >be used instead of systemd-timesyncd. > >None of the ntp implementations currently ship such a native unit file >though, that's why we decided to add such a Condition to the >systemd-timesyncd.service unit file for the time being. > >There were concerns that adding this Conflicts to every time >synchronization service is a questionable approach [2]. > >Arguably, for ntp, chrony and openntpd, we can solve this on a >packaging >level, by making those packages conflict. > >If we want to enable timesyncd by default and keep it as a part of the >systemd package, this approach doesn't work, and we need the Conflicts= >on the systemd unit level. Perhaps just a bit too late for me, but how would package vdr be handled, which does _optionally_ set the system clock from the TV signal. Eric
-- I'm on debian-java, java maintainers, vdr maintainers and debian-mentors; no need to CC me on these lists. Thanks! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
