Your message dated Fri, 20 Apr 2018 19:18:37 +0200
with message-id <[email protected]>
and subject line Re: Bug#895978: FSHS violation: systemd-timesyncd installed in
/lib
has caused the Debian Bug report #895978,
regarding FSHS violation: systemd-timesyncd installed in /lib
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
895978: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895978
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 232-25+deb9u2
Severity: serious
Hi,
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).
Please ping upstream and ask for sensible respect of the FSHS.
Cheers,
Thomas Goirand (zigo)
--- End Message ---
--- Begin Message ---
Am 18.04.2018 um 10:15 schrieb 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.
Having binaries in libexecdir which are not supposed to be started from
the command line by the user, i.e. need to be in PATH, is common
practice. systemd is doing nothing special here.
Just check the output of ps aux, I have dozens of processes running as
(/usr)/lib/$pkg/$binary
Given that, I'm closing this bug report.
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
