Package: xen-utils-4.4
Severity: normal
Dear Maintainer,
the xen-utils-4.4 and xen-utils-4.1 prerm maintainer scripts contain the
following code snippet:
remove|upgrade)
update-alternatives --remove xen-default /usr/lib/xen-4.4
if [ -x "/etc/init.d/xen" ]; then
invoke-rc.d xen stop || exit $?
fi
;;
which, in conjunction with the postinst script triggers a xend and xenconsoled
restart that relies on both maintainer scripts being executed.
We triggered a xen stop by removing obsolete xen-utils-4.1 packages while
already using xen-utils-4.4.
Can you think of a way to implement the restart and stop more robustly in that
the stop and start actions are performed atomically or the service shipped in
the unversioned xen-utils-common is not stopped if it has been started by the
maintainer script of a different (newer) xen-utils-X.Y package?
-- System Information:
Debian Release: 9.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf-8, LC_CTYPE=en_GB.utf-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
