Bug#895978: FSHS violation: systemd-timesyncd installed in /lib

[Martin Pitt]

Control: tag -1 moreinfo

Hello Thomas,

Thomas Goirand [2018-04-18  9:36 +0200]:
> Package: systemd
> Version: 232-25+deb9u2
> Severity: serious

What is the rationale for this being release-critical?

> Doing my everyday $work, I found that a machine had systemd-timesyncd
> installed. To the contrary of a lot of people, I don't really mind it,
> if it does the job. Though it got installed in
> /lib/systemd/systemd-timesyncd. This makes no sense for a daemon, that
> must be installed in /bin (if needed at boot time) or in /usr/bin
> (more likely).

This isn't a program which you are supposed to run on the command line, so
putting it into $PATH makes no sense. This is a typical example of a program
that should be in LIBEXECDIR, which is {,/usr}/lib/<packagename> in Debian.

So it can certainly be argued that this (and a lot of similar programs) should
move to /usr/lib/systemd/systemd-timesyncd instead of /lib, but that doesn't
seem to be release critical to me. I can't find a Debian Policy requirement
that would mandate this, but maybe I'm overlooking something.

Martin