1 |
2008/10/22 Alex Schuster <wonko@×××××××××.org>: |
2 |
> |
3 |
> I think I have the same conflict. I just solved it by putting this into |
4 |
> package.keywords: |
5 |
> ~dev-python/PyQt4-4.4.3 |
6 |
> ~dev-python/sip-4.7.7 |
7 |
> |
8 |
> So I upgraded to PyQt4-4.4.3, and this depends on the splitted Qt ebuilds, |
9 |
> while PyQt4 up to version 4.4-r1 wants the old monolithic Qt. |
10 |
> |
11 |
> weird ~ # grep x11-libs/qt /usr/portage/dev-python/PyQt4/*.ebuild |
12 |
> /usr/portage/dev-python/PyQt4/PyQt4-4.3.3.ebuild:RDEPEND="=x11-libs/qt-4.3* |
13 |
> /usr/portage/dev-python/PyQt4/PyQt4-4.4-r1.ebuild:RDEPEND="=x11-libs/qt-4* |
14 |
> /usr/portage/dev-python/PyQt4/PyQt4-4.4.2.ebuild: |
15 |
>>=x11-libs/qt-core-4.4.0:4 |
16 |
> /usr/portage/dev-python/PyQt4/PyQt4-4.4.3.ebuild: |
17 |
>>=x11-libs/qt-core-4.4.0:4 |
18 |
> [...] |
19 |
|
20 |
This is maybe the PyQt issue I did not remember. So I think it is |
21 |
worth a try. If this is the case portage tries to pull qt-4.4.3 |
22 |
because it is needed by PyQt-4.4 plus the qt split ebuilds which are |
23 |
needed by some other packages. So putting versions of PyQt and sip in |
24 |
package.keywords which depemd on qt split ebuilds should solve it. If |
25 |
I remember right I have this entries in my package.keywords too. |
26 |
Probably you need oneshot for PyQt and sip too. |
27 |
|
28 |
-- |
29 |
Regards, |
30 |
Daniel |