Hide Forgot
vios-proxy is a new package in 6.2. No other packages depend on it, so it will need to be added to comps.xml in order to be pulled into the compose.
This also looks like it should be a dependency of a virtualization tool.
@notting: It's not a strict dependency, that's the issue. We need vios-proxy for using AMQP over virtio-serial between hosts and KVM guests. But not all matahari usage will be on virt environments, so we can't put a Requires: vios-proxy on matahari packages. Any suggestions for how this should be handled?
Wouldn't it then be a dependency of either libvirt, or the qemu tools?
No, it's not
OK, so looks like it would be added as an optional package in both the client-mgmt-tools group, and the virtualization group.
comps.xml updated
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2011-1743.html