Creating .deb with systemd service but without SysV init scripts
Multi tool use
Clash Royale CLAN TAG#URR8PPP
up vote
3
down vote
favorite
I'm trying to add a systemd service file to an existing Debian package. I followed https://wiki.debian.org/Teams/pkg-systemd/Packaging, so I created debian/packagename.service. Because my debhelper is version 9.x, I also:
- added
dh-systemdtoBuild-Dependsindebian/control - added
--with systemdto thedhcommand indebian/rules.
Now when I rebuild the package with debuild -i -us -uc -b, it fails with this output:
Now running lintian...
[...]
W: packagename: init.d-script-not-marked-as-conffile etc/init.d/packagename
E: packagename: init.d-script-not-included-in-package etc/init.d/packagename
It seems like the build script expects an init.d script if there is a .service file. And indeed, the generated DEBIAN/postinst includes this section:
# Automatically added by dh_installinit
if [ -x "/etc/init.d/infinoted" ]; then
update-rc.d infinoted defaults >/dev/null
invoke-rc.d infinoted start || exit $?
fi
# End automatically added section
Is this expected behavior? Should I always include SysV init scripts when I include a .service file? If not, what is the recommended way to prevent the generation of this section?
My system is Debian Jessie.
debian systemd init.d packaging deb
asked Feb 19 '17 at 14:20
segfault
162
bumped to the homepage by Community♦ 28 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |Â
up vote
3
down vote
favorite
I'm trying to add a systemd service file to an existing Debian package. I followed https://wiki.debian.org/Teams/pkg-systemd/Packaging, so I created debian/packagename.service. Because my debhelper is version 9.x, I also:
- added
dh-systemdtoBuild-Dependsindebian/control - added
--with systemdto thedhcommand indebian/rules.
Now when I rebuild the package with debuild -i -us -uc -b, it fails with this output:
Now running lintian...
[...]
W: packagename: init.d-script-not-marked-as-conffile etc/init.d/packagename
E: packagename: init.d-script-not-included-in-package etc/init.d/packagename
It seems like the build script expects an init.d script if there is a .service file. And indeed, the generated DEBIAN/postinst includes this section:
# Automatically added by dh_installinit
if [ -x "/etc/init.d/infinoted" ]; then
update-rc.d infinoted defaults >/dev/null
invoke-rc.d infinoted start || exit $?
fi
# End automatically added section
Is this expected behavior? Should I always include SysV init scripts when I include a .service file? If not, what is the recommended way to prevent the generation of this section?
My system is Debian Jessie.
debian systemd init.d packaging deb
asked Feb 19 '17 at 14:20
segfault
162
bumped to the homepage by Community♦ 28 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |Â
up vote
3
down vote
favorite
up vote
3
down vote
favorite
I'm trying to add a systemd service file to an existing Debian package. I followed https://wiki.debian.org/Teams/pkg-systemd/Packaging, so I created debian/packagename.service. Because my debhelper is version 9.x, I also:
- added
dh-systemdtoBuild-Dependsindebian/control - added
--with systemdto thedhcommand indebian/rules.
Now when I rebuild the package with debuild -i -us -uc -b, it fails with this output:
Now running lintian...
[...]
W: packagename: init.d-script-not-marked-as-conffile etc/init.d/packagename
E: packagename: init.d-script-not-included-in-package etc/init.d/packagename
It seems like the build script expects an init.d script if there is a .service file. And indeed, the generated DEBIAN/postinst includes this section:
# Automatically added by dh_installinit
if [ -x "/etc/init.d/infinoted" ]; then
update-rc.d infinoted defaults >/dev/null
invoke-rc.d infinoted start || exit $?
fi
# End automatically added section
Is this expected behavior? Should I always include SysV init scripts when I include a .service file? If not, what is the recommended way to prevent the generation of this section?
My system is Debian Jessie.
debian systemd init.d packaging deb
asked Feb 19 '17 at 14:20
segfault
162
I'm trying to add a systemd service file to an existing Debian package. I followed https://wiki.debian.org/Teams/pkg-systemd/Packaging, so I created debian/packagename.service. Because my debhelper is version 9.x, I also:
- added
dh-systemdtoBuild-Dependsindebian/control - added
--with systemdto thedhcommand indebian/rules.
Now when I rebuild the package with debuild -i -us -uc -b, it fails with this output:
Now running lintian...
[...]
W: packagename: init.d-script-not-marked-as-conffile etc/init.d/packagename
E: packagename: init.d-script-not-included-in-package etc/init.d/packagename
It seems like the build script expects an init.d script if there is a .service file. And indeed, the generated DEBIAN/postinst includes this section:
# Automatically added by dh_installinit
if [ -x "/etc/init.d/infinoted" ]; then
update-rc.d infinoted defaults >/dev/null
invoke-rc.d infinoted start || exit $?
fi
# End automatically added section
Is this expected behavior? Should I always include SysV init scripts when I include a .service file? If not, what is the recommended way to prevent the generation of this section?
My system is Debian Jessie.
debian systemd init.d packaging deb
debian systemd init.d packaging deb
asked Feb 19 '17 at 14:20
segfault
162
asked Feb 19 '17 at 14:20
segfault
162
asked Feb 19 '17 at 14:20
segfault
162
asked Feb 19 '17 at 14:20
segfault
162
asked Feb 19 '17 at 14:20
segfault
162
162
bumped to the homepage by Community♦ 28 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 28 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
Overriding dh_installinit worked for me. I just added this to debian/rules:
override_dh_installinit:
true
It still installs the systemd unit and everything seems to work as expected.
But I still don't know if this is expected behavior or a bug. Note that I did not test this on Debian Stretch or Sid, only on Jessie.
answered Feb 19 '17 at 14:32
segfault
162
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Overriding dh_installinit worked for me. I just added this to debian/rules:
override_dh_installinit:
true
It still installs the systemd unit and everything seems to work as expected.
But I still don't know if this is expected behavior or a bug. Note that I did not test this on Debian Stretch or Sid, only on Jessie.
answered Feb 19 '17 at 14:32
segfault
162
add a comment |Â
up vote
0
down vote
Overriding dh_installinit worked for me. I just added this to debian/rules:
override_dh_installinit:
true
It still installs the systemd unit and everything seems to work as expected.
But I still don't know if this is expected behavior or a bug. Note that I did not test this on Debian Stretch or Sid, only on Jessie.
answered Feb 19 '17 at 14:32
segfault
162
add a comment |Â
up vote
0
down vote
up vote
0
down vote
Overriding dh_installinit worked for me. I just added this to debian/rules:
override_dh_installinit:
true
It still installs the systemd unit and everything seems to work as expected.
But I still don't know if this is expected behavior or a bug. Note that I did not test this on Debian Stretch or Sid, only on Jessie.
answered Feb 19 '17 at 14:32
segfault
162
Overriding dh_installinit worked for me. I just added this to debian/rules:
override_dh_installinit:
true
It still installs the systemd unit and everything seems to work as expected.
But I still don't know if this is expected behavior or a bug. Note that I did not test this on Debian Stretch or Sid, only on Jessie.
answered Feb 19 '17 at 14:32
segfault
162
answered Feb 19 '17 at 14:32
segfault
162
answered Feb 19 '17 at 14:32
segfault
162
answered Feb 19 '17 at 14:32
segfault
162
162
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f346109%2fcreating-deb-with-systemd-service-but-without-sysv-init-scripts%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password