1 |
Hi folks, |
2 |
|
3 |
I think this is FUBAR in the most serious terms here. What I did to |
4 |
screw this up. I read somewhere that when you install KDE4 and remove |
5 |
KDE3, you can get rid of the qt3support USE flag. Well, I had forgot |
6 |
about getting rid of that until I just happened to be looking at the USE |
7 |
line in make.conf for something else and saw it still there. Well, I |
8 |
removed it and did a emerge -uvDNa world and let portage go for it. It |
9 |
rebuilt quite a few packages then stopped with a failure. That was a |
10 |
couple days ago. I don't have that error anymore. Well, after that |
11 |
went belly up I just added the flag back thinking I'll get back to where |
12 |
I was and figure it out later. Let's just say portage doesn't like that |
13 |
either. |
14 |
|
15 |
Where I am now. I'm wanting to upgrade to KDE 4.5.1 and was sort of |
16 |
doing all the above and this at once. Right now, I'm getting a WHOLE |
17 |
LOT of these sort of errors: |
18 |
|
19 |
Calculating dependencies... done! |
20 |
|
21 |
!!! Multiple package instances within a single package slot have been pulled |
22 |
!!! into the dependency graph, resulting in a slot conflict: |
23 |
|
24 |
x11-libs/qt-script:4 |
25 |
|
26 |
(x11-libs/qt-script-4.6.3, installed) pulled in by |
27 |
~x11-libs/qt-script-4.6.3aqua=,debug=] required by |
28 |
(x11-libs/qt-gui-4.6.3, installed) |
29 |
>=x11-libs/qt-script-4.6.3:4 required by |
30 |
(kde-base/plasma-workspace-4.5.1, ebuild scheduled for merge) |
31 |
(and 13 more with the same problems) |
32 |
|
33 |
(x11-libs/qt-script-4.6.2, ebuild scheduled for merge) pulled in by |
34 |
~x11-libs/qt-script-4.6.2aqua=,debug=] required by |
35 |
(x11-libs/qt-gui-4.6.2, ebuild scheduled for merge) |
36 |
|
37 |
x11-libs/qt-svg:4 |
38 |
|
39 |
(x11-libs/qt-svg-4.6.2, ebuild scheduled for merge) pulled in by |
40 |
(no parents that aren't satisfied by other packages in this slot) |
41 |
|
42 |
(x11-libs/qt-svg-4.6.3, installed) pulled in by |
43 |
>=x11-libs/qt-svg-4.6.34 required by (kde-base/mplayerthumbs-4.5.1, |
44 |
ebuild scheduled for merge) |
45 |
(and 13 more with the same problem) |
46 |
|
47 |
x11-libs/qt-xmlpatterns:4 |
48 |
|
49 |
(x11-libs/qt-xmlpatterns-4.6.2, ebuild scheduled for merge) pulled in by |
50 |
~x11-libs/qt-xmlpatterns-4.6.2aqua=,debug=] required by |
51 |
(x11-libs/qt-webkit-4.6.2-r1, ebuild scheduled for merge) |
52 |
|
53 |
(x11-libs/qt-xmlpatterns-4.6.3, installed) pulled in by |
54 |
~x11-libs/qt-xmlpatterns-4.6.3aqua=,debug=] required by |
55 |
(x11-libs/qt-webkit-4.6.3-r1, installed) |
56 |
|
57 |
|
58 |
I only posted here a SMALL portion of this. Can someone explain, in a |
59 |
way that I can understand, how to get past these? I have never been |
60 |
able to make much sense of these things. They seem to always be bass |
61 |
ackwards of what makes sense to me. Just pick one and explain what |
62 |
portage is trying to tell me so I can fix the others one by one, |
63 |
hopefully anyway. |
64 |
|
65 |
I get that I need to unmerge something so that it can emerge a new |
66 |
version. I just can't figure out what is what. |
67 |
|
68 |
Thanks in advance for anyone that can help me have a light bulb |
69 |
moment. O_O |
70 |
|
71 |
Dale |
72 |
|
73 |
:-) :-) |