I think I had the similar blocks while upgrading my kde from 3.5.x to 4.1.2, I just unmerged x11-libs/qt-core then everything seemed to be fine.

-Weifeng

On Sun, Oct 19, 2008 at 9:54 PM, Peter Humphrey <peter@humphrey.ukfsn.org> wrote:
Having been inspired by messages here extolling the virtues of KDE-4, I
tried installing it. I did as Neil B said and autounmasked kde-meta-4.1.2,
but I still have a couple of show-stoppers.

After running autounmask, I had 81 new entries in package.keywords, but I
had to add another 82 myself after that many attempts to emerge -uaDvN
world.

Even so, I now have five blockers. Three of them I can clear by unmerging
old package versions, but that leaves me with these two:

[blocks B     ] <=x11-libs/qt-4.4.0_alpha:4 ("<=x11-libs/qt-4.4.0_alpha:4"
is blocking x11-libs/qt-script-4.4.2, x11-libs/qt-dbus-4.4.2,
x11-libs/qt-qt3support-4.4.2, x11-libs/qt-sql-4.4.2, x11-libs/qt-gui-4.4.2,
x11-libs/qt-svg-4.4.2, x11-libs/qt-test-4.4.2, x11-libs/qt-core-4.4.2,
x11-libs/qt-webkit-4.4.2, x11-libs/qt-opengl-4.4.2)
[blocks B     ] x11-libs/qt-core ("x11-libs/qt-core" is blocking
x11-libs/qt-4.3.3)

The first of these implies that I have to unmerge qt-3.*, which I assume
would smash the system into tiny pieces, while the second just looks
nonsensical to me.

Can anyone see anything obvious here that I can fix?

--
Rgds
Peter