On 7/23/19 4:07 PM, niek wrote: > [...] > 2019-07-21 07:38:40 status installed xen-utils-4.8:amd64 > 4.8.5+shim4.10.2+xsa282-1+deb9u11 > 2019-07-21 07:38:40 remove xen-utils-4.8:amd64 > 4.8.5+shim4.10.2+xsa282-1+deb9u11 <none> > 2019-07-21 07:38:40 status half-configured xen-utils-4.8:amd64 > 4.8.5+shim4.10.2+xsa282-1+deb9u11 > 2019-07-21 07:38:41 status half-installed xen-utils-4.8:amd64 > 4.8.5+shim4.10.2+xsa282-1+deb9u11 > 2019-07-21 07:38:41 status config-files xen-utils-4.8:amd64 > 4.8.5+shim4.10.2+xsa282-1+deb9u11 > 2019-07-21 07:38:41 status not-installed xen-utils-4.8:amd64 <none> > 2019-07-21 07:38:41 status installed libxen-4.8:amd64 > 4.8.5+shim4.10.2+xsa282-1+deb9u11 > 2019-07-21 07:38:41 remove libxen-4.8:amd64 > 4.8.5+shim4.10.2+xsa282-1+deb9u11 <none> > 2019-07-21 07:38:41 status half-configured libxen-4.8:amd64 > 4.8.5+shim4.10.2+xsa282-1+deb9u11 > 2019-07-21 07:38:41 status half-installed libxen-4.8:amd64 > 4.8.5+shim4.10.2+xsa282-1+deb9u11 > 2019-07-21 07:38:41 status config-files libxen-4.8:amd64 > 4.8.5+shim4.10.2+xsa282-1+deb9u11 > 2019-07-21 07:38:41 status not-installed libxen-4.8:amd64 <none> > [...] > 2019-07-21 07:38:42 status installed xen-hypervisor-4.8-amd64:amd64 > 4.8.5+shim4.10.2+xsa282-1+deb9u11 > 2019-07-21 07:38:42 remove xen-hypervisor-4.8-amd64:amd64 > 4.8.5+shim4.10.2+xsa282-1+deb9u11 <none> > 2019-07-21 07:38:42 status half-configured > xen-hypervisor-4.8-amd64:amd64 4.8.5+shim4.10.2+xsa282-1+deb9u11 > 2019-07-21 07:38:42 status half-installed xen-hypervisor-4.8-amd64:amd64 > 4.8.5+shim4.10.2+xsa282-1+deb9u11 > 2019-07-21 07:39:41 status config-files xen-hypervisor-4.8-amd64:amd64 > 4.8.5+shim4.10.2+xsa282-1+deb9u11
Ok, so, the most interesting question for me is... On line 50 in the init script: https://salsa.debian.org/xen-team/debian-xen/blob/master/debian/xen-utils-common.xen.init case $DPKG_MAINTSCRIPT_PACKAGE in xen-utils-$VERSION) ;; # xen-utils-V maintscript, under Xen X=V xen-utils-*) exit 0;; # xen-utils-V maintscript, but under Xen X!=V *) ;; # maybe not under dpkg, etc. esac What is the value of this $DPKG_MAINTSCRIPT_PACKAGE when it happens? Could it be something else than something beginning with xen-utils-? I have a suspicion that the systemd[1]: Reloading. has something to do with it. Or the triggers? Anyway, if DPKG_MAINTSCRIPT_PACKAGE gets lost *anywhere* in whatever happens, it might end up as empty, and then matching just *. But, we really need find out how to reproduce it in a test environment. :| Hans
