[Pkg-xen-devel] Bug#852545: Config file in xen-hypervisor package likely causes problems on upgrade

[Ian Jackson]

Control: tags -1 stretch-ignore

Ian Jackson writes ("Bug#852545: Config file in xen-hypervisor package likely causes problems on upgrade"):
> Control: tags -1 confirmed
> 
> I have generated some emergency holographic Xen 4.9 packages and
> indeed
> 
> dpkg: error processing archive
> i/xen-hypervisor-4.9-amd64_4.9.0~~not-1iwj_amd64.deb (--install):
>  trying to overwrite '/etc/default/grub.d/xen.cfg', which is also in
>  package xen-hypervisor-4.8-amd64 4.8.1~pre.2017.01.23-1

I made some experimental packages which have the grub default file in
this new package:

 Package: xen-hypervisor-common
 Source: xen
 Version: 4.9.0~~not-1iwj
 Architecture: all
 Maintainer: Debian Xen Team <pkg-xen-devel at lists.alioth.debian.org>
 Installed-Size: 44
 Replaces: xen-hypervisor-4.8-amd64, xen-hypervisor-4.8-arm64, xen-hypervisor-4.8-armhf
 Section: kernel
 Priority: optional
 Description: Xen Hypervisor - common files
  The configuration which arranges for an installed hypervisor to be booted
  as default, with the right command line arguments passed to both
  hypervisor and host (Domain 0) kernel.
  .
  This package is only required on the host system (Domain 0) and not on the
  virtual guest systems (Domain U).

I was able to coinstall this with xen-hypervisor-4.8-amd64 and even
got the right conffile prompt (which I induced by editing the file
both on the test system and in the package).

So I think this problem can be postponed for now.  It will need to be
addressed when anyone packages Xen 4.9 for Debian.

The things I had to do to the packaging to make it generate my test
packages are too horrible (and useless) to share.  I thought I would
quote the generated control file instead.

Ian.