1 |
On Wednesday 22 October 2008 11:15:34 Peter Humphrey wrote: |
2 |
> On Tuesday 21 October 2008 19:46:33 Daniel Pielmeier wrote: |
3 |
> > One thing I would give a try is to give portage a hand and emerge some of |
4 |
> > the qt split ebuilds with the oneshot option. In your case the qt split |
5 |
> > ebuilds which are blocked: |
6 |
> > |
7 |
> > x11-libs/qt-script-4.4.2, x11-libs/qt-dbus-4.4.2, |
8 |
> > x11-libs/qt-qt3support-4.4.2, x11-libs/qt-sql-4.4.2, |
9 |
> > x11-libs/qt-gui-4.4.2, x11-libs/qt-svg-4.4.2, |
10 |
> > x11-libs/qt-test-4.4.2, x11-libs/qt-core-4.4.2, |
11 |
> > x11-libs/qt-webkit-4.4.2, x11-libs/qt-opengl-4.4.2 |
12 |
> > |
13 |
> > and then see if portage will be able to continue with the world update. |
14 |
> |
15 |
> That was a good idea, one that I ought to have thought of but didn't. |
16 |
> Unfortunately, it's made no difference at all. Emerge -upDvN world still |
17 |
> gives the same block: |
18 |
> |
19 |
> [blocks B ] x11-libs/qt-core ("x11-libs/qt-core" is blocking |
20 |
> x11-libs/qt-4.3.3) |
21 |
> [blocks B ] <=x11-libs/qt-4.4.0_alpha:4 ("<=x11-libs/qt-4.4.0_alpha:4" |
22 |
> is blocking x11-libs/qt-script-4.4.2, x11-libs/qt-dbus-4.4.2, |
23 |
> x11-libs/qt-qt3support-4.4.2, x11-libs/qt-sql-4.4.2, x11-libs/qt-gui-4.4.2, |
24 |
> x11-libs/qt-svg-4.4.2, x11-libs/qt-test-4.4.2, x11-libs/qt-core-4.4.2, |
25 |
> x11-libs/qt-webkit-4.4.2, x11-libs/qt-opengl-4.4.2) |
26 |
> |
27 |
> Total: 160 packages (3 upgrades, 78 new, 65 in new slots, 14 reinstalls), |
28 |
> Size of downloads: 209,150 kB |
29 |
> Conflict: 2 blocks (2 unsatisfied) |
30 |
> |
31 |
> To recap, the only version of qt installed is qt-3.3.8-r4, and equery d |
32 |
> =x11-libs/qt-3.3.8-r4 returns 160 packages, all wanting =x11-libs/qt-3*. |
33 |
> Emerge seems to think I have a version4.* of qt installed, but I haven't |
34 |
> apart from the split e-builds I've just installed as above. |
35 |
|
36 |
No, that is incorrect and your reading of the output is wrong. |
37 |
|
38 |
Emerge detects blockers by looking at what is currently on the machine or what |
39 |
it wants to install and seeing if that will block with what is on the machine |
40 |
or what will be installed. |
41 |
|
42 |
You do not have to have a package installed to create a block - it can be |
43 |
caused by something that is due to be emerged (and hence will only be |
44 |
installed in the future). |
45 |
|
46 |
Look at the second blocker line. It says: |
47 |
|
48 |
<=x11-libs/qt-4.4.0_alpha:4 |
49 |
|
50 |
That means: |
51 |
- a version in SLOT 4 |
52 |
- the version number is less than 4.4.0_alpha is blocking/blocked by qt-4.4.2 |
53 |
|
54 |
You do not have such a package installed. That's cool. |
55 |
|
56 |
You need to find out why portage thinks it must install such a thing. That's |
57 |
why I asked you for emerge -t earlier. Find an entry for |
58 |
<=x11-libs/qt-4.4.0_alpha:4 in that list and look above it to see what pulled |
59 |
it in. Fix that thing and portage will stop trying to pull in an old version |
60 |
of qt and your problem will go away. |
61 |
|
62 |
I earnestly recommend you do not go through a full reinstall. That will teach |
63 |
you nothing. You need to go through this at least once to learn how to deal |
64 |
with it, it's a necessary gentoo skill |
65 |
|
66 |
-- |
67 |
alan dot mckinnon at gmail dot com |