Howdy. Seems like a recent change to net-im/znc causes a conflict on systems where znc and virtualbox are installed. 08 May 2014; Alex Alexander <wired@gentoo.org> znc-1.2-r1.ebuild, znc-9999.ebuild: added REQUIRED_USE for python, bug #509640 Now, on my amd64 system, results in: homeserver-02 ~ # upg These are the packages that would be merged, in order: Calculating dependencies - !!! Problem resolving dependencies for sys-libs/tevent from @selected ... done! !!! The ebuild selected to satisfy "sys-libs/tevent" has unmet requirements. - sys-libs/tevent-0.9.19::gentoo USE="" PYTHON_SINGLE_TARGET="-python2_6 -python2_7" PYTHON_TARGETS="python2_7 -python2_6" The following REQUIRED_USE flag constraints are unsatisfied: exactly-one-of ( python_single_target_python2_6 python_single_target_python2_7 ) The above constraints are a subset of the following complete expression: python_single_target_python2_6? ( python_targets_python2_6 ) python_single_target_python2_7? ( python_targets_python2_7 ) exactly-one-of ( python_single_target_python2_6 python_single_target_python2_7 ) (dependency required by "@selected" [set]) (dependency required by "@world" [argument]) --- ('upg' is a script that does: emerge -uDNv --with-bdeps y system world --keep-going ) Virtualbox needs Python 2.7, and ZNC needs Python 3.X and above. What should I do to resolve the conflict? Thanks.
You know you can do something like echo "net-irc/znc python_single_target_python3_3" >> /etc/portage/package.use to get around this problem? Same is possible for virtualbox as well.
It's net-irc/znc but I don't see any problem there that's related to what you are seeing. In fact, the net-irc/znc ebuilds require _different_ python versions than emerge is complaining about (they use not 2_6/2_7 but 3_2/3_3). It's perfectly fine to have different packages requiring different a PYTHON_SINGLE_TARGET, even if it's a bit cumbersome at times (but that happens to be the implementation we use now). As noted in comment #1, the output clearly sets out what steps you need to take to fix this issue locally.
Wow, sorry for the noise. Thanks for your time.
