On 02/12/2015 08:15 AM, Gevisz wrote: > # emerge --ask chromium > ... >> The following USE changes are necessary to proceed: >> (see "package.use" in the portage(5) man page for more details) >> # required by www-client/chromium-40.0.2214.111 >> # required by chromium (argument) >>> =dev-libs/libxml2-2.9.2 icu > Ok, done. > > # emerge --ask chromium > ... >> !!! Multiple package instances within a single package slot have been pulled >> !!! into the dependency graph, resulting in a slot conflict: >> >> dev-libs/libxml2:2 >> >> (dev-libs/libxml2-2.9.2:2/2::gentoo, ebuild scheduled for merge) pulled in >> by >> dev-libs/libxml2:=[icu] required by >> (www-client/chromium-40.0.2214.111:0/0::gentoo, ebuild scheduled for merge) >> ^^^ >> > >> >> (dev-libs/libxml2-2.9.2:2/2::gentoo, installed) pulled in by >> dev-libs/libxml2:2[!icu?] required by (dev-qt/qtwebkit-4.8.5:4/4::gentoo, >> installed) >> ^^^^^ >> > >> It may be possible to solve this problem by using package.mask to >> prevent one of those packages from being selected. However, it is also >> possible that conflicting dependencies exist such that they are >> impossible to satisfy simultaneously. If such a conflict exists in >> the dependencies of two different packages, then those packages can >> not be installed simultaneously. You may want to try a larger value of >> the --backtrack option, such as --backtrack=30, in order to see if >> that will solve this conflict automatically.
I think (emphasis on the think) that qtwebkit needs libxml2 with -icu, and chromium needs libxml2 with +icu. As far as I can tell from reading a couple bug reports, it looks like you can rebuild qtwebkit with -gstreamer (since that's what causes the !icu? blocker) and then you should be able to install chromium. Apparently icu is pretty annoying. Alternatively, you could just uninstall qtwebkit if you're not using it for anything. Alec
