Bug#759849: multipath-tools: FTBFS: uxsock.c:20:31: fatal error: systemd/sd-daemon.h: No such file or directory
biebl at debian.org
Mon Sep 1 21:30:57 UTC 2014
Am 01.09.2014 14:26, schrieb Michael Biebl:
> Am 01.09.2014 13:37, schrieb Michael Biebl:
>> By quickly glancing over the package, I also noted that you ship a
>> systemd .service file named multipathd.service but the SysV init scripts
>> are named /etc/init.d/multipath-tools and
>> /etc/init.d/multipath-tools-boot (not quite sure why there are two).
>> systemd continues to start your SysV init scripts, but I assume this is
>> not wanted? Typically, the SysV init script and the systemd .service
>> file should have the same name, this way systemd will automatically pick
>> the native .service unit.
>> If you want to keep the upstream name for the .service, this is
>> absolutely file as well (and even encouraged), but you should make sure
>> the SysV init script is not run then.
>> There are two possible ways: Provide a symlink(alias)
>> /lib/systemd/system/<sysvinit_name>.service →
>> or mask the SysV init script by shipping a symlink pointing to /dev/null.
Also, please don't simply override the lintian warning . It is there
for a reason.
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 819 bytes
Desc: OpenPGP digital signature
More information about the pkg-lvm-maintainers