[Bug 2048529] Re: Do we need to keep libvirt-bin forever?

[Christian Ehrhardt ]

I can now show that the behavior with just apt dist-upgrade behaves as I'd have expected.
libvirt-bin no more being in focal stays on 4.0.0-1ubuntu8.21 of bionic and keeps pulling things in

But indeed as reported when upgrading with do-release-upgrade the
transitional package goes away and any following auto-remove would
eliminate it.

In fact further upgrading to jammy in the test above does just that.
After another do-release-upgrade to in jammy it is gone.

ubuntu at x-lvb:~$ apt-cache policy libvirt-bin libvirt-clients; dpkg -S virsh; virsh -v
libvirt-bin:
  Installed: (none)
  Candidate: (none)
  Version table:
libvirt-clients:
  Installed: (none)
  Candidate: 8.0.0-1ubuntu7.7
  Version table:
     8.0.0-1ubuntu7.7 500
        500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
     8.0.0-1ubuntu7.5 500
        500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
     8.0.0-1ubuntu7 500
        500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
sosreport: /usr/lib/python3/dist-packages/sos/report/plugins/virsh.py
Command 'virsh' not found, but can be installed with:
sudo apt install libvirt-clients


But also, I looked through logs how things happened and I think it is
not that weird.

It is like:

Remove (was auto installed)
<list>
[yN]


And to be clear, that only happened because I wanted the "yes to all experience".
I said I'm ok for it to remove those, so it is my fault I guess?


I'll need to do a run with just "enter enter enter" to make sure and see how it would behave there.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-release-upgrader in
Ubuntu.
https://bugs.launchpad.net/bugs/2048529

Title:
  Do we need to keep libvirt-bin forever?

Status in libvirt package in Ubuntu:
  Incomplete
Status in ubuntu-release-upgrader package in Ubuntu:
  Incomplete

Bug description:
  # History

  In debian/1.2.10-1 7ca6a8a libvirt-bin was changed to be a
  transitional.

  This will need to be retained until an LTS change happens so for Ubuntu this was kept and up until Xenial libvirt-bin was a package with content.
  Then it followed Debian

  Later in yakkety yak and later it got changed to be a transitional in 1.3.1-2
  Since we'd need to wait for an Ubuntu LTS 1.3.3-2ubuntu1 kept libvirt-bin (the transitional) around this stayed another while.

  Then post Bionic we dropped even that and libvirt-bin was no more (no
  package, no transitional, no nothing).

  # Problem

  This is kind of how transitions work, but now we've got a report that
  if people installed e.g. on Xenial and just `apt install libvirt-bin`
  to get virsh and other things back then. And upgrade through to e.g.
  focal or even later - they got the replacement packages like `libvirt-
  clients` removed (presumably as nothing depended on it anymore).

  TODO:

  This history is a bit convoluted as the timing was so different due to waiting until after LTSes.
  But we need to:
  1. Install xenial, install libvirt-bin, do-release-upgrade through to Jammy, check if libvirt-clients is still around or not.
  2. if not, then this is a bug and we need to find how to avoid.

  Potentially this is needed in all >Bionic and need to retain the
  libvirt-bin transitional forever? This feels so worng, with a deeper
  look I hope we can find what is actually going on and find a better
  solution.

  P.S. original reporter is Mmike on #ubuntu-server in IRC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2048529/+subscriptions