Merged and to-be merged blockers are not considered properly in all cases. A partial fix was implemented, but problem still exist. (should be remedied in the dep rewrite) Reproducible: Always Steps to Reproduce:
*** Bug 34296 has been marked as a duplicate of this bug. ***
I fixed it in CVS
supposed to be fixed in 2.0.50 which is stable now. If this bug is not fixed please reopen.
This problem is not fixed. [ebuild N ] x11-themes/gnome-themes-2.4.1 qpkg -q: x11-themes/gnome-themes-2.4.1 DEPENDED ON BY: x11-themes/gtk-engines-mist-0.10 dependency of the mist ebuild: DEPEND="!x11-themes/gnome-themes"
dont use qpkg to determine if the problem still exists use portage (ala emerge)
SpanKY: The "[ebuild N..." line is ripped from emerge -puD world. And if I was not blind when reading the man page, emerge does not have functionality like qpkg -q in portage 2.0.50.
Hmpf, gnome-themes is a PDEPEND of libgnomeui, so that must be the reason, why portage wants to install it again and again. I did "find /var/db/pkg/ iname * -exec grep -H gnome-themes '{}' ';'" to find this out. There is no information about PDEPENDencies available and neither qpkg nor etcat can handle these as it seems. According to Bug 27234 (if I had seen this one a bit sooner...) gtk-engines-mist is included in >=gnome-themes-2.2. Conclusion: 1) x11-themes/gnome-themes should block ~gtk-engines-mist-0.10 2) please fix qpkg,etcat 3) please update the ebuild/eclass howto Thx for your work and patience.
I don't think this is portage problem. Could you post as new bug?
