Neil Bothwick writes:
> On Wed, 22 Oct 2008 10:15:34 +0100, Peter Humphrey wrote:
> > That was a good idea, one that I ought to have thought of but didn't.
> > Unfortunately, it's made no difference at all. Emerge -upDvN world
> > still gives the same block:
[...]
> > To recap, the only version of qt installed is qt-3.3.8-r4,
>
> Something you are trying to emerge as part of the world update depends
> on qt-4.3*, so it is trying to install 4.3 and 4.4, that's the cause of
> the block. Blocks aren't always the result of installed packages, only
> those that would be installed at the end of the emerge.
>
> > I could try removing qt-3.3.8-r4, but first I'd have to back up the
> > whole system against the probability of being unable to recover from
> > the resultant smashing of KDE 3.5.
>
> qt3 seems to be unrelated to this, but a full backup is unnecessary.
> quickpkg qt3 before unmerging it. If the system goes TU you can emerge
> -k it.
I think I have the same conflict. I just solved it by putting this into
package.keywords:
~dev-python/PyQt4-4.4.3
~dev-python/sip-4.7.7
So I upgraded to PyQt4-4.4.3, and this depends on the splitted Qt ebuilds,
while PyQt4 up to version 4.4-r1 wants the old monolithic Qt.
weird ~ # grep x11-libs/qt /usr/portage/dev-python/PyQt4/*.ebuild
/usr/portage/dev-python/PyQt4/PyQt4-4.3.3.ebuild:RDEPEND="=x11-libs/qt-4.3*
/usr/portage/dev-python/PyQt4/PyQt4-4.4-r1.ebuild:RDEPEND="=x11-libs/qt-4*
/usr/portage/dev-python/PyQt4/PyQt4-4.4.2.ebuild:
>=x11-libs/qt-core-4.4.0:4
/usr/portage/dev-python/PyQt4/PyQt4-4.4.3.ebuild:
>=x11-libs/qt-core-4.4.0:4
[...]
Wonko
