From b9e18c1dae0c0ad2251a36ada569323580115fe2 Mon Sep 17 00:00:00 2001 From: Bruce Ashfield Date: Sun, 8 May 2022 23:19:32 -0400 Subject: xen-tools: correct xencommons initscript for systemd commit [xen-tools: don't declare xencommons as an initscript for systemd] was wrong in an amazing two ways. It has an extranenous } and it has inverted logic. The result is that xencommons is not being properly declared as an initscript for sysvinit, and hence we don't fully boot. It isn't a problem for most systemd configurations, so we were booting as the initscript wasn't firing. Signed-off-by: Bruce Ashfield --- recipes-extended/xen/xen-tools.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/recipes-extended/xen/xen-tools.inc b/recipes-extended/xen/xen-tools.inc index eabb8fac..d4999777 100644 --- a/recipes-extended/xen/xen-tools.inc +++ b/recipes-extended/xen/xen-tools.inc @@ -717,7 +717,7 @@ INSANE_SKIP:${PN} = "already-stripped" # configure init.d scripts INITSCRIPT_PACKAGES = "${PN}-xend ${PN}-xen-watchdog ${PN}-xendomains ${PN}-devd" -INITSCRIPT_PACKAGES += "${@bb.utils.contains('DISTRO_FEATURES', 'systemd', '${PN}-xencommons}', '', d)}" +INITSCRIPT_PACKAGES += "${@bb.utils.contains('DISTRO_FEATURES', 'systemd', '', '${PN}-xencommons', d)}" INITSCRIPT_NAME:${PN}-xencommons = "xencommons" INITSCRIPT_PARAMS:${PN}-xencommons = "defaults 80" INITSCRIPT_NAME:${PN}-xen-watchdog = "xen-watchdog" -- cgit v1.2.3-54-g00ecf