http://nopaste.info/b948879045.html relevant part should be: (line 69) [nomerge ] media-video/totem-3.8.2-r1 USE="introspection lirc nautilus nsplugin python -debug -flash -grilo {-test} -zeitgeist" PYTHON_SINGLE_TARGET="python2_7 -python2_6" PYTHON_TARGETS="python2_7 -python2_6" [ebuild N ] dev-libs/totem-pl-parser-2.32.6-r3 USE="introspection quvi -archive" 0 kB [ebuild N ~] net-libs/libsoup-gnome-2.40.3:2.4 USE="introspection -debug" 0 kB [ebuild UD~] net-libs/libsoup-2.40.3:2.4 [2.42.2:2.4] USE="introspection samba ssl -debug {-test}" 0 kB ... !!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict: net-libs/libsoup:2.4 (net-libs/libsoup-2.42.2::gentoo, installed) pulled in by >=net-libs/libsoup-2.42.1:2.4 required by (www-client/epiphany-3.8.2::gentoo, ebuild scheduled for merge) (and 11 more with the same problem) (net-libs/libsoup-2.40.3::gentoo, ebuild scheduled for merge) pulled in by ~net-libs/libsoup-2.40.3[introspection?] required by (net-libs/libsoup-gnome-2.40.3::gentoo, ebuild scheduled for merge) I found help in #gentoo.de, thanks again, thomasg :) He told me to add a keyword for dev-libs/totem-pl-parser and to file a bug. I guess totem needs to rdepend on a more recent version of totem-pl-parser so it won't pull net-libs/libsoup-gnome?
You need to: emerge -C libsoup-gnome And, if you are getting it still pulled in, it's because you need to also update other package (as you would be mixing stable and testing). You can find the culprit running "equery d libsoup-gnome" and, then, see if keywording its latest version works
This isn't INVALID per se, as it's a significant issue in upgrade path, but we know that and hopefully take action to make it better soon. But we have separate tracking for that than here (hopefully adding libsoup-gnome split back until it completely disappears from usage in tree). Meanwhile you can do what Pacho said, the easing is mostly targeted at stable users before gnome3 goes stable.
It's the same issue as appears when a package blocks others, I even think handbook explained that sometimes "emerge -C" is needed. Cases like this were even more noticeable in the past when portage wasn't able to resolve blocks automatically. This remembers me that portage will resolve the blockers automatically if you don't have libsoup-gnome in your world file (and you shouldn't) and, of course, don't mix packages from stable pulling it with testing.
