Merge ~paelzer/uvtool:fix-libvirt-dependency into uvtool:ubuntu/devel
Status: | Merged |
---|---|
Merged at revision: | 7996f7f8ccc0afad4010e9e5b8eaecfe8f1b55ef |
Proposed branch: | ~paelzer/uvtool:fix-libvirt-dependency |
Merge into: | uvtool:ubuntu/devel |
Diff against target: |
35 lines (+9/-2) 2 files modified
debian/changelog (+6/-0) debian/control (+3/-2) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Robie Basak | Pending | ||
Review via email: mp+324779@code.launchpad.net |
Description of the change
Hi,
part of working on bug 1694159 is to drop the libvirt-bin dependency of uvtool-libvirt.
I don't know if you have any issues with it considering your backport-from-git strategy, but we can discuss that if needed.
TL;DR libvirt-bin is only a transitional package since Yakkety, we want to complete the drop of dependencies towards 18.04 so that we can remove the package in 18.10.
But fixing as much as possible ahead of time - e..g in artful now, makes the small transition later easier. Therefore a merge request for uvtools artful packaging mapping the new package names.
I made sure the commit message explains the details why which replacement dependencies where chosen, that way people can find it without knowing the MP to read the reasoning.
Note: since we need daemon-system AND clients anyway as outlined int he commit.
And in recent Ubuntu releases libvirt-bin looks like this:
Package: libvirt-bin cloud0 daemon- system (>= 2.5.0-3ubuntu5~ cloud0) , libvirt-clients (>= 2.5.0-3ubuntu5~ cloud0)
Source: libvirt
Version: 2.5.0-3ubuntu5~
Depends: libvirt-
The change is actually a no-op (there are other cases where we only replace with one of the new packages). But for this the change should have no impact other than dropping the outdated libvirt-bin dependency.