See http://forums.gentoo.org/viewtopic-p-7318442.html#7318442 for some discussion of this issue. After having xen-tools installed for quite some time with hvm and qemu use flags, portage is suddenly claiming that the qemu use flag is masked and hence hvm cannot be enabled due to xen-tools requiring qemu when hvm is enabled. !!! The ebuild selected to satisfy "xen-tools" has unmet requirements. - app-emulation/xen-tools-4.2.1-r3::gentoo USE="hvm screen -api -custom-cflags -debug -doc -flask -ocaml -pygrub (-qemu) -static-libs -xend" PYTHON_SINGLE_TARGET="python2_7 -python2_6" PYTHON_TARGETS="python2_7 -python2_6" The following REQUIRED_USE flag constraints are unsatisfied: hvm? ( qemu ) Additionally, qemu is listed in parenthesis, which apparently means that qemu is masked by the active profile but I have been unable to track down exactly where this is. I consider this a blocker as it breaks world updates if xen-tools is currently installed.
looks like # Agostino Sarubbo <ago@gentoo.org> (23 May 2013) # Temporary mask because it needs texinfo-5 >=app-emulation/xen-tools-4.2.1-r3 qemu from gentoo-x86/profiles/base/package.use.mask
I admin that I am not an ebuild hacker but wouldn't it just be better to keep the same keywords on xen-tools as on texinfo-5 so as not to cause breakage like this? xen-tools-4.2.1-r3 is listed as stable but if you have the qemu flag, portage just barfs on this and it's still not obvious what the proper resolution is. If texinfo-5 is still being tested and hence is unstable (~amd64 keyword) then shouldn't anything that depends on it be listed as unstable? What is the suggested workaround for this issue? Manually mask this version of xen-tools?
*** This bug has been marked as a duplicate of bug 470048 ***
*** This bug has been marked as a duplicate of bug 471122 ***
Odd, I didn't find those when I searched.
