Broken dependencies on gutsy amd64
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xenman (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: xenman
The xenman package depends on packages xen-utils-3.0.3-1 or xen-utils, however neither of these exist in my gutsy amd64 repositories. Instead I have xen-utils-3.1 and xen-utils-3.0
Details:
apt-cache show xenman
Depends: python, yelp, python-rpm, python-vte, python-paramiko, python-gtk2, python-glade2, xen-utils-3.0.3-1 | xen-utils
apt-cache policy xen-utils-3.0.3-1
xen-utils-3.0.3-1:
Installed: (none)
Candidate: (none)
Version table:
apt-cache policy xen-utils
xen-utils:
Installed: (none)
Candidate: (none)
Version table:
apt-cache search xen-utils
xen-utils-3.1 - XEN administrative tools
xen-utils-common - XEN administrative tools - common files
xen-utils-3.0 - XEN administrative tools
Thank you for taking the time to report this bug and helping to make Ubuntu better.
Package xen-utils is a virtual package, which is provided by xen-utils-3.1 on Gutsy amd64. See the Provides line below:
$ apt-cache show xen-utils-3.1
Package: xen-utils-3.1
Priority: extra
Section: universe/misc
Installed-Size: 1172
Maintainer: Chuck Short <>
Architecture: amd64
Source: xen-3.1
Version: 3.1.0-0ubuntu18
Replaces: xen-utils-3.0
Provides: xen-utils
From the debian-policy (http:// www.debian. org/doc/ debian- policy/ ch-relationship s.html) chapter 7.4:
A virtual package is one which appears in the Provides control file field of another package. The effect is as if the package(s) which provide a particular virtual package name had been listed by name everywhere the virtual package name appears.
So the dependency on xen-utils is fulfilled by xen-utils-3.1
As this doesn't seem to be a "real" bug, I will close it. Please feel free to re-open if you do have real dependency problems with xenman.