Am 01.09.2014 13:25, schrieb Michael Biebl: > Am 01.09.2014 12:50, schrieb Ritesh Raj Sarraf: >> I fixed this one by adding a build-dep to systemd dev library. But for >> some reason, the build is failing on all architectures. But the same >> builds fine in my pbuilder. Any help ?? > > Looking at the build logs [1], the package itself builds fine but you > have missing files, which dh_install --fail-missing complains about: > > dh_install: multipath-tools missing files (/usr/lib/systemd/system/*), > aborting > > Keep in mind, that in Debian the systemd service files are installed in > /lib/systemd/system. 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 → /lib/systemd/system/<upstream_service_file_name> or mask the SysV init script by shipping a symlink pointing to /dev/null. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
Attachment:
signature.asc
Description: OpenPGP digital signature