boon ~ # emerge -uav dev-lang/v8 These are the packages that would be merged, in order: Calculating dependencies... done! Total: 0 packages, Size of downloads: 0 kB WARNING: One or more updates have been skipped due to a dependency conflict: dev-lang/v8:0 (dev-lang/v8-3.18.5.9::gentoo, ebuild scheduled for merge) conflicts with =dev-lang/v8-3.17* required by (www-client/chromium-27.0.1453.110::gentoo, ebuild scheduled for merge)
Created attachment 353124 [details] package.mask
Created attachment 353126 [details] package.use
Created attachment 353128 [details] package.accept_keywords
Created attachment 353130 [details] make.conf
boon ~ # eselect profile list Available profile symlink targets: [1] default/linux/amd64/13.0 [2] default/linux/amd64/13.0/selinux [3] default/linux/amd64/13.0/desktop [4] default/linux/amd64/13.0/desktop/gnome * [5] default/linux/amd64/13.0/desktop/kde [6] default/linux/amd64/13.0/developer [7] default/linux/amd64/13.0/no-multilib [8] default/linux/amd64/13.0/x32 [9] hardened/linux/amd64 [10] hardened/linux/amd64/selinux [11] hardened/linux/amd64/no-multilib [12] hardened/linux/amd64/no-multilib/selinux [13] hardened/linux/amd64/x32 [14] hardened/linux/uclibc/amd64 boon ~ # uname -a Linux boon 3.8.13-gentoo #1 SMP Sun Jun 30 12:10:27 SGT 2013 x86_64 Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz GenuineIntel GNU/Linux
Yes, it sets a dependency on =dev-lang/v8-3.17*. What is wrong with that? The "latest" www-client/chromium in the tree would be 29.0.1547.15 so it's a good thing I changed the Summary, I guess.
I am actually not sure if this is a real bug or just that the latest chromium doesn't work with the latest v8. I was just following the guide from http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1 saying the below. :) It is also possible that two packages that are yet to be installed are blocking each other. In this rare case, you should find out why you need to install both. In most cases you can do with one of the packages alone. If not, please file a bug on Gentoo's bugtracking system.
(In reply to Boon Hian Tek from comment #7) > I am actually not sure if this is a real bug or just that the latest > chromium doesn't work with the latest v8. Again, what you are calling the "latest chromium (27.0.1453.110) clearly isn't the latest. In the stable branch, it's 28.0.1500.71. In the unstable branch, it's 28.0.1500.89. Then there is an even higher masked branch populated by 29.0.1547.0 and 29.0.1547.15. If that's not good enough, there is a by now quite wobbly branch of ebuilds that could fall over any second, which is both masked and de-keyworded, populated by a very brave 9999-r1 ebuild. Doubtlessly, with all that in place, there must have been some kind of mistake in setting v8 dependencies.
You'll have to upgrade to chromium-28 if you want that version of v8.