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

[Christian Ehrhardt ]

Sadly the do-release-upgrade is in a screen session not directly seen in the logs.
But I'll run a "all default enter only" test whenever I come by this virtual workspace.

Until then I'm already extending that bug to do-release-upgrade for expertise on what to expect.
(Hence setting to incomplete there too)

I'm not saying do-release-upgrade does something wrong, but rather the
opposite "What would be expected to be done by a package to not be
removed by accident?"

Or is everything actually all right?


Furthermore, while this seems totally reproducible - this particular example is in the field since almost 4 years and comes up now. And it should affect more than just libvirt, I'd assume any transitional would be handled this way? Hence for now priority low until we know more.

** Changed in: ubuntu-release-upgrader (Ubuntu)
       Status: New => Incomplete

** Changed in: libvirt (Ubuntu)
   Importance: Undecided => Medium

** Changed in: libvirt (Ubuntu)
   Importance: Medium => Low

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Importance: Undecided => Low

-- 
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