when I do emerge -puD world, I get (beside some other lines) the following output: [ebuild N ] x11-themes/gtk-engines-2.2.0 [ebuild N ] x11-themes/gtk-engines-thinice-2.0.2-r1 [ebuild N ] x11-themes/gnome-themes-2.4.0 There is no ebuild, that could cause this on my system, besides the gtk-engines-mist-0.10.ebuild, which includes the blocking dependency "!x11-themes/gnome-themes". used portage version is 2.0.49-r15 Reproducible: Always Steps to Reproduce: 1. 2. 3.
btw. gnome-themes is missing "!>=x11-themes/gtk-engines-mist-0.10"
$ emerge -p gtk-engines-mist These are the packages that I would merge, in order: Calculating dependencies ...done! [blocks B ] x11-themes/gnome-themes (from pkg x11-themes/gtk-engines-mist-0.10) [ebuild N ] x11-themes/gtk-engines-mist-0.10
oh, and the other one would be a bug for the gnome team, please file a new bug for that.
to verify this, you have to unmerge x11-themes/gnome-themes and all ebuilds that depend on it, merge gtk-engines-mist-0.10 and wonder, why portage wants to force you to install x11-themes/gnome-themes and the other two gtk ebuilds, it depends on. that merging gtk-engines-mist is blocked by gnome-themes is obvious, but not my point.
$ emerge -ep gtk-engines-mist | grep theme [blocks B ] x11-themes/gnome-themes (from pkg x11-themes/gtk-engines-mist-0.10) [ebuild N ] x11-themes/gtk-engines-mist-0.10 $ USE="-*" emerge -ep gtk-engines-mist | grep theme [blocks B ] x11-themes/gnome-themes (from pkg x11-themes/gtk-engines-mist-0.10) [ebuild N ] x11-themes/gtk-engines-mist-0.10 will try with unmerging and merging later, but I don't think that the result will be different.
*** This bug has been marked as a duplicate of 36344 ***
