On Thu, May 3, 2018 at 6:10 AM Daniel P. Berrangé <berrange@xxxxxxxxxx> wrote: > 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 < 4.3.0" > 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. -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
