While debugging the xen-utils postinst/prerm to find the cause of the
mysteriously disappearing xenconsoled processes, I discovered that the
xen-utils-common postinst and prerm stop and start the xen init script
as well!
These commands are not visible in the packaging code, but they are added
by dh_installinit into the postinst and prerm during package build time.
We only want to call the script from xen-utils-V, so disable this
behavior by using --no-start
Signed-off-by: Hans van Kranenburg <hans@knorrie.org>
Reviewed-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
Closes: #932759 (2/2)
# We have two init scripts. (There used to be xend too.)
override_dh_installinit:
- dh_installinit --name xen -- defaults 20 21
+ dh_installinit --name xen --no-start -- defaults 20 21
dh_installinit --name xendomains --no-start -- defaults 21 20
# dh_strip in dh compat 10 and earlier (which we are at so this