Peter Humphrey schrieb am 21.10.2008 11:07: > On Monday 20 October 2008 13:08:30 Daniel Pielmeier wrote: >> Unmerge x11-libs/qt-4.3.3 and try again. If you want to be on the safe >> side do a quickpkg =x11-libs/qt-4.3.3 before. The new qt-4.4.x split >> ebuilds can not live alongside the non split ebuild. > > I ran quickpkg and emerge -C on qt-4.3.3, then emerge -upDvN world again. > The block is still there, exactly the same as before.
Let me quote Alan here: > I main underlying reason seems to be that Qt now comes as split-ebuilds and > Peter has some monolithic ones installed. It's similar to migrating KDE to > split-ebuilds, but on a much smaller scale. Unfortunately there's no easy way > to automate this in an ebuild, that would require several new unrelated > packages replacing one big one, portage doesn't support that kind of thing. > So one has to do it manually, and deal with the resulting recdep-rebuild > issues as well .... The problem is that portage is probably not smart enough to do the upgrade from the non-split to the split ebuilds, so the world update will always run into this blocker even when qt-4.3.3 is not installed. Maybe some ebuild depends on >=qt-4.3.3 so it is pulled in and another one depends on >=qt-4.4.x which also gets pulled in and thus the blockers. This should be no problem in the normal case as the highest needed version would be installed. But the new split ebuilds have no relation to the old monolithic which is probably causing the problems in this case. The highest available version for monolithic is qt-4.3.3 and so it is pulled in alongside the new split ebuilds which are also needed because of a >=4.4.x dependency of other programs. I remember such problems to when migrating to qt split ebuilds and simply running emerge world was not enough but I do not remember the exact procedure which solved this. There were some issues with PyQt4 but I am not sure if this was related. One thing I would give a try is to give portage a hand and emerge some of the qt split ebuilds with the oneshot option. In your case the qt split ebuilds which are blocked: 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 and then see if portage will be able to continue with the world update. > I've started building a new system from scratch on another disk, and I'm now > about ready to start installing KDE on it. Maybe a clean start is what I > need. > I think this could be solved without a reinstall but it is up to you. Regards, Daniel
