2008/10/22 Alex Schuster <[EMAIL PROTECTED]>: > > 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 > [...]
This is maybe the PyQt issue I did not remember. So I think it is worth a try. If this is the case portage tries to pull qt-4.4.3 because it is needed by PyQt-4.4 plus the qt split ebuilds which are needed by some other packages. So putting versions of PyQt and sip in package.keywords which depemd on qt split ebuilds should solve it. If I remember right I have this entries in my package.keywords too. Probably you need oneshot for PyQt and sip too. -- Regards, Daniel
