I tried to build a fresh ~amd64 gentoo with kde4 and on that way I got the problem, that qt-gui-4.5.2-r1 wanted to be emerged, but at the same time also qt-gui-4.5.1-r2 was pulled in. After some checks I realized that qt-gui-4.5.1-r2 was pulled in because it has automatically the dbus use flag enabled, but qt-4.5.2-r1 was pulled in because it is the most recent ~amd64 version. After compiling qt-4.5.2-r1 with the dbus use flag enabled, the problem was gone and I was able to emerge kde4 without any further problem. The problem is, that qt-4.5.1 and qt-4.5.2 cannot be installed at the same time... Reproducible: Always Steps to Reproduce: 1. Start with a fresh stage3 and fresh portage tree 2. Do NOT set the dbus useflag for qt-gui 3. emerge -a kdebase-startkde Actual Results: Blocking packages Expected Results: No blocking packages :P
This was posted by a Gentoo dev on planet.gentoo.org: http://www.linuxized.com/2009/07/gentoo-testing-clean-install-qt-kde-4-blockers-help/ It clearly describes your problem. @qt herd: Still assigning this to you, I'm sure you have a duplicate bug somewhere but I'm not seeing it.
Not a qt bug IMHO. We (the qt herd) have decided to drop IUSE defaults for flags which are already enabled by the desktop or base profiles, and we are not going to change that again. As wired explained in his blog post: "Portage first checks qt-gui-4.5.2, which doesn’t have dbus enabled by default. No go. But wait, qt-gui-4.5.1 has it enabled and portage falls back to it. So now portage tries to mix all the other qt-*-4.5.2 packages with qt-gui-4.5.1 (and its 4.5.1 dependencies) [...]" => blockers! So IMHO this should be considered a portage bug (or rather, a limitation of its dep resolver), if anything.
*** Bug 278701 has been marked as a duplicate of this bug. ***
If you are on the desktop profile, dbus is enabled by default. If you are not, then we now respect your choice and you get to enable dbus yourself if you need it anyway. Most Qt users will want the desktop profile and should not have any problem. For the non-desktop profile users I'm sorry that this transition is bumpy, but we do end up with a clearer situation in the end, which is why we decided to do this.
