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