Xen 4.10 -> 4.11 upgrade fails because libxentoolcore

ea2334df tries to provide a solution for the shlibs dependency problem that was introduced with the addition of libxentoolcore in Xen 4.10.

It puts the libxentoolcore-4.10.so.1 into the libxenstore3.0 package. However, when I build Xen 4.11, I end up with libxentoolcore-4.11.so.1.0 in the libxenstore3.0 package...

In this case I was one build of 4.10 behind on this dom0, and installed the 4.11 packages I just built.

Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  libxen-4.10 xen-hypervisor-4.10-amd64 xen-utils-4.10
Use 'apt autoremove' to remove them.
The following NEW packages will be installed:
  [...] libxen-4.11 xen-hypervisor-4.11-amd64 xen-utils-4.11
The following packages will be upgraded:
  libxen-4.10 libxenstore3.0 [...] xen-hypervisor-4.10-amd64 xen-hypervisor-common xen-system-amd64
  xen-utils-4.10 xen-utils-common xenstore-utils

So, everything explodes:

Setting up xen-utils-common (4.11.0-1~) ...
Job for xen.service failed because the control process exited with error code.
See "systemctl status xen.service" and "journalctl -xe" for details.
invoke-rc.d: initscript xen, action "start" failed.
● xen.service - LSB: Xen daemons
   Loaded: loaded (]8;;file://gamma/etc/init.d/xen/etc/init.d/xen]8;;; generated)
   Active: failed (Result: exit-code) since Sat 2018-07-28 22:24:29 CEST; 16ms ago
     Docs: ]8;;man:systemd-sysv-generator(8)man:systemd-sysv-generator(8)]8;;
  Process: 7670 ExecStart=/etc/init.d/xen start (code=exited, status=1/FAILURE)
    Tasks: 4 (limit: 4674)
   Memory: 3.0M
   CGroup: /system.slice/xen.service
           └─1157 /usr/lib/xen-4.10/bin/xenstored --pid-file=/var/run/xenstore.pid

Jul 28 22:24:29 gamma systemd[1]: Starting LSB: Xen daemons...
Jul 28 22:24:29 gamma xen[7670]: Starting Xen daemons: xenstored xenconsoled/usr/lib/xen-4.10/bin/xenconsoled: error while loading shared libraries: libxentoolcore-4.10.so.1: cannot open shared object file: No such file or directory
Jul 28 22:24:29 gamma xen[7670]:  failed!
Jul 28 22:24:29 gamma systemd[1]: xen.service: Control process exited, code=exited status=1
Jul 28 22:24:29 gamma systemd[1]: xen.service: Failed with result 'exit-code'.
Jul 28 22:24:29 gamma systemd[1]: Failed to start LSB: Xen daemons.
dpkg: error processing package xen-utils-common (--configure):
 installed xen-utils-common package post-installation script subprocess returned error exit status 1

It has to go somewhere else, probably again another separate package?