1 |
On 14/03/2015 11:10, Meino.Cramer@×××.de wrote: |
2 |
> Alan McKinnon <alan.mckinnon@×××××.com> [15-03-14 09:48]: |
3 |
>> On 14/03/2015 09:36, Meino.Cramer@×××.de wrote: |
4 |
>>> Hi, |
5 |
>>> |
6 |
>>> emerge hits me: |
7 |
>>> |
8 |
>>> Whiletrying to reolve a lot of blockers, emerge @preserved-rebuild |
9 |
>>> gives me this: |
10 |
>>> |
11 |
>>> emerge: there are no ebuilds to satisfy "kde-base/solid:4". |
12 |
>>> (dependency required by "@preserved-rebuild" [argument]) |
13 |
>>> |
14 |
>>> emerge itself can be called without that error. |
15 |
>>> How can an argument to a command haves a dependency? |
16 |
>>> |
17 |
>>> How can I get out of this? |
18 |
>> |
19 |
>> |
20 |
>> It's portage's insanely obtuse output that is getting you confused, but |
21 |
>> the error is with an ebuild, not portage. |
22 |
>> |
23 |
>> First, there is not such package as "solid" with SLOT=4: |
24 |
>> |
25 |
>> # eix -e solid |
26 |
>> * kde-frameworks/solid |
27 |
>> Available versions: (5) (~)5.7.0(5/5.7) |
28 |
>> {debug doc nls test} |
29 |
>> Homepage: http://www.kde.org/ |
30 |
>> Description: Framework providing platform independent |
31 |
>> hardware discovery, abstraction, and management |
32 |
>> |
33 |
>> |
34 |
>> Then, all that "dependency required by..." output from portage is an |
35 |
>> effort to show you what is pulling a package in, and it starts at the |
36 |
>> beginning. Portage knows it's dealing with whatever is in the |
37 |
>> @preserved-rebuild set, and that set has packages in it. Each of those |
38 |
>> packages may have other deps, and so on. |
39 |
>> |
40 |
>> In your case, it seems to be solid-actions-kcm that's causing it |
41 |
>> |
42 |
>> # grep -r "kde-base/solid:4" /var/portage/ |
43 |
>> /var/portage/kde-base/solid-actions-kcm/solid-actions-kcm-4.11.14.ebuild: |
44 |
>> !kde-base/solid:4 |
45 |
>> |
46 |
>> |
47 |
>> |
48 |
>> I have no idea if this will work, but here's what I'd do: |
49 |
>> |
50 |
>> skip @preserved-rebuild for now, and run |
51 |
>> revdep-rebuild |
52 |
>> emerge -a --depclean |
53 |
>> |
54 |
>> So if that changes things. Also make sure neither solid nor |
55 |
>> solid-actions-kcm are in world, they should be deps pulled in automatically. |
56 |
>> |
57 |
>> Also move /var/lib/portage/preserved_libs_registry out of the way if it |
58 |
>> has junk in it and let revdep-rebuild fix things. |
59 |
>> |
60 |
>> Finally, you did sync ran emerge world recently, right? |
61 |
|
62 |
|
63 |
> |
64 |
> Hi Alan, |
65 |
> |
66 |
> thanks for your reply ! :) |
67 |
|
68 |
|
69 |
No problem. |
70 |
|
71 |
Huge amounts of portage output snipped below, but I think you are trying |
72 |
to have stable Qt4 and unstable Qt5 on the same system. That doesn't |
73 |
work currently, I'll walk through my reasoning so you can see what's |
74 |
going on: |
75 |
|
76 |
> |
77 |
> ...interesting...one needs to use grep to resolve a problem of |
78 |
> portage ;) |
79 |
|
80 |
Hah yes, that's quite funny. |
81 |
I wanted to see what the ebuilds actually say, not what portage tools |
82 |
think they say :-) |
83 |
|
84 |
|
85 |
> |
86 |
> |
87 |
> Things are going even more worst (correct English???...uh, sound like |
88 |
> german English...;;;))): |
89 |
> |
90 |
> revdep-rebuild runs fine and found nothing to rebuild. |
91 |
> depclean stops its work and said: |
92 |
> |
93 |
> Calculating dependencies... done! |
94 |
> * Dependencies could not be completely resolved due to |
95 |
> * the following required packages not being installed: |
96 |
> * |
97 |
> * >=dev-qt/qtgui-4.8.5:4[accessibility,dbus(+)] pulled in by: |
98 |
> * kde-base/kglobalaccel-4.14.3 |
99 |
|
100 |
[... huge snip] |
101 |
|
102 |
Basically, of this part really means that you need Qt:4 |
103 |
It *can* co-exist with Qt5, I have them both installed here. |
104 |
|
105 |
> Since packages are missing I tried: |
106 |
> emerge --update --newuse --deep --with-bdeps=y @world --tree --keep-going -v |
107 |
> |
108 |
> |
109 |
> which prints: |
110 |
> These are the packages that would be merged, in reverse order: |
111 |
> |
112 |
> Calculating dependencies... done! |
113 |
|
114 |
[...snip...] |
115 |
|
116 |
> [blocks B ] <dev-qt/qtgui-4.8.6:4 ("<dev-qt/qtgui-4.8.6:4" is blocking dev-qt/qtchooser-0_p20150102) |
117 |
> [blocks B ] <dev-qt/qtsql-4.8.6:4 ("<dev-qt/qtsql-4.8.6:4" is blocking dev-qt/qtchooser-0_p20150102) |
118 |
> [blocks B ] <dev-qt/qtcore-4.8.6:4 ("<dev-qt/qtcore-4.8.6:4" is blocking dev-qt/qtchooser-0_p20150102) |
119 |
> [blocks B ] <dev-qt/qthelp-4.8.6:4 ("<dev-qt/qthelp-4.8.6:4" is blocking dev-qt/qtchooser-0_p20150102) |
120 |
> [blocks B ] <dev-qt/qtopengl-4.8.6:4 ("<dev-qt/qtopengl-4.8.6:4" is blocking dev-qt/qtchooser-0_p20150102) |
121 |
> [blocks B ] <dev-qt/qt3support-4.8.6:4 ("<dev-qt/qt3support-4.8.6:4" is blocking dev-qt/qtchooser-0_p20150102) |
122 |
> [blocks B ] <dev-qt/qtsvg-4.8.6:4 ("<dev-qt/qtsvg-4.8.6:4" is blocking dev-qt/qtchooser-0_p20150102) |
123 |
> [blocks B ] <dev-qt/qtmultimedia-4.8.6:4 ("<dev-qt/qtmultimedia-4.8.6:4" is blocking dev-qt/qtchooser-0_p20150102) |
124 |
> [blocks B ] <dev-qt/qtdeclarative-4.8.6:4 ("<dev-qt/qtdeclarative-4.8.6:4" is blocking dev-qt/qtchooser-0_p20150102) |
125 |
> [blocks B ] <dev-qt/designer-4.8.6:4 ("<dev-qt/designer-4.8.6:4" is blocking dev-qt/qtchooser-0_p20150102) |
126 |
> [blocks B ] <dev-qt/qttest-4.8.6:4 ("<dev-qt/qttest-4.8.6:4" is blocking dev-qt/qtchooser-0_p20150102) |
127 |
> [blocks B ] <dev-qt/qtxmlpatterns-4.8.6:4 ("<dev-qt/qtxmlpatterns-4.8.6:4" is blocking dev-qt/qtchooser-0_p20150102) |
128 |
> [blocks B ] <dev-qt/qtwebkit-4.8.6:4 ("<dev-qt/qtwebkit-4.8.6:4" is blocking dev-qt/qtchooser-0_p20150102) |
129 |
> [blocks B ] <dev-qt/qtdbus-4.8.6:4 ("<dev-qt/qtdbus-4.8.6:4" is blocking dev-qt/qtchooser-0_p20150102) |
130 |
> [blocks B ] <dev-qt/qtscript-4.8.6:4 ("<dev-qt/qtscript-4.8.6:4" is blocking dev-qt/qtchooser-0_p20150102) |
131 |
|
132 |
[... snip big list of what wants Qt stuff] |
133 |
|
134 |
dev-qt/qtchooser seems to be the main culprit here. In that ebuild: |
135 |
|
136 |
RDEPEND=" |
137 |
... |
138 |
!<dev-qt/qtgui-4.8.6:4 |
139 |
... |
140 |
|
141 |
And so on and so on |
142 |
|
143 |
This eix shows what I think might be your main problem: |
144 |
|
145 |
# eix -e qtgui |
146 |
[I] dev-qt/qtgui |
147 |
Available versions: |
148 |
(4) 4.8.5-r3 (~)4.8.6-r1 |
149 |
(5) (~)5.4.1^t |
150 |
|
151 |
Looks like you are running a stable system, but you keyworded Qt5. Is |
152 |
that correct? The above ebuild shows that unstable Qt5 blocks stable |
153 |
Qt4, so you will have to fix that first. |
154 |
|
155 |
1. Find and uninstall what apps you have that need Qt5, or |
156 |
2. Keyword Qt4 unstable and let portage figure out how to resolve the |
157 |
blockers |
158 |
|
159 |
|
160 |
|
161 |
|
162 |
|
163 |
> Uuuuh..,thats much. |
164 |
> |
165 |
> Should I buy a new harddisk and start right from the beginning? |
166 |
|
167 |
No :-) |
168 |
About 30 lines in package.accept_keywords should be enough :-) |
169 |
|
170 |
|
171 |
-- |
172 |
Alan McKinnon |
173 |
alan.mckinnon@×××××.com |