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

Christian Ehrhardt  2048529 at bugs.launchpad.net
Tue Jan 9 12:24:12 UTC 2024


Here from /var/log/dpkg.log on the system that got it removed by do-
release-upgrade:

2024-01-09 12:09:13 status installed libvirt-bin:amd64 4.0.0-1ubuntu8.21
2024-01-09 12:09:13 remove libvirt-bin:amd64 4.0.0-1ubuntu8.21 <none>
2024-01-09 12:09:13 status half-configured libvirt-bin:amd64 4.0.0-1ubuntu8.21
2024-01-09 12:09:13 status half-installed libvirt-bin:amd64 4.0.0-1ubuntu8.21
2024-01-09 12:09:14 status config-files libvirt-bin:amd64 4.0.0-1ubuntu8.21
...
2024-01-09 12:09:28 purge libvirt-bin:amd64 4.0.0-1ubuntu8.21 <none>
2024-01-09 12:09:28 status config-files libvirt-bin:amd64 4.0.0-1ubuntu8.21
2024-01-09 12:09:28 status triggers-pending systemd:amd64 245.4-4ubuntu3.22
2024-01-09 12:09:28 status not-installed libvirt-bin:amd64 <none>

I can only assume that it removed packages no more in the new repository?
Maybe under some condition like being in oldlibs or any such?

** Also affects: ubuntu-release-upgrader (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: libvirt (Ubuntu)
       Status: New => Incomplete

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

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




More information about the foundations-bugs mailing list