On Sun, May 06, 2018 at 11:00:00AM +0000, Neal Gompa wrote:
On Thu, May 3, 2018 at 6:10 AM Daniel P. Berrangé
> In libvirt we recently deleted a driver for the legacy Xen toolstack.
> This was shipped in a libvirt-daemon-driver-xen RPM.
> I am able to add an "Obsoletes: libvirt-daemon-driver-xen < 4.3.0"
> line to the libvirt-daemon-driver-libxl RPM, which gives clean
> upgrade path for users.
> If they have the libvirt-daemon-driver-xen-debuginfo RPM installed
> though that still breaks the upgrade.
> How can I get the auto-generated libvirt-daemon-driver-libxl-debuginfo
> RPM to have an "Obsoletes: libvirt-daemon-driver-xen-debuginfo <
> statement ? It seems impossible, meaning users with debuginfo have a
> broken upgrade path. An unfortunate consequence of switching to seprate
> -debuginfo per sub-RPM.
How is this creating upgrade problems? debuginfo packages do not require
the main packages at all.
I have the debuginfo RPMs installed locally and the upgrade process wants
to install the new debuginfo RPMs to replace them. Whether they have a
dep on the main non-debuginfo packages is tangential to that.