1 |
On Tuesday 21 July 2009 17:11:33 Alex Schuster wrote: |
2 |
> Hi there! |
3 |
> |
4 |
> My @world update shows this problem: |
5 |
> |
6 |
> !!! Multiple package instances within a single package slot have been |
7 |
> pulled !!! into the dependency graph, resulting in a slot conflict: |
8 |
> |
9 |
> dev-python/PyQt4:0 |
10 |
> |
11 |
> ('ebuild', '/', 'dev-python/PyQt4-4.4.4-r5', 'merge') pulled in by |
12 |
> |
13 |
> >=dev-python/PyQt4-4.4.0[X] required by ('installed', '/', 'kde- |
14 |
> |
15 |
> base/plasma-workspace-4.2.4', 'nomerge') |
16 |
> dev-python/PyQt4[X] required by ('installed', '/', 'media- |
17 |
> sound/picard-0.11', 'nomerge') |
18 |
> |
19 |
> >=dev-python/PyQt4-4.4 required by ('ebuild', '/', 'dev- |
20 |
> |
21 |
> python/qscintilla-python-2.3.2-r2', 'merge') |
22 |
> (and 1 more) |
23 |
> |
24 |
> ('ebuild', '/', 'dev-python/PyQt4-4.4.4-r2', 'merge') pulled in by |
25 |
> |
26 |
> >=dev-python/PyQt4-4.4.4-r1[dbus,qt3support,svg,webkit,X] required by |
27 |
> |
28 |
> ('ebuild', '/', 'kde-base/pykde4-4.2.4', 'merge') |
29 |
> (and 4 more) |
30 |
> |
31 |
> I would like to understand where the problem is. The bottom says that |
32 |
> pykde4-4.2.4 needs at least PyQt4-4.4.4-r2. This is fine, I can see the |
33 |
> corresponding DEPEND line in the pykde4-4.2.4 ebuild. |
34 |
> |
35 |
> The top list tells that: |
36 |
> plasma-workspace-4.2.4 needs PyQt4-4.4.0, |
37 |
> picard-0.11 needs PyQt4 and |
38 |
> qscintilla-python-2.3.2-r2 needs PyQt4-4.4 |
39 |
> |
40 |
> Why then is PyQt4-4.4.4-r5 needed? -r2 should satisfy these needs, too, |
41 |
> doesn't it? Or is the problem the 'and 1 more' line? How would I find out |
42 |
> which other package would need -r5 then? And why would the other line be |
43 |
> listed then? I don't get this. |
44 |
> |
45 |
> I grepped for PyQt4-4.4.4-r5 through all ebuilds, it appeared only in the |
46 |
> PyQt4-4.4.4-r5.ebuild itself. |
47 |
> |
48 |
> This is not an important problem - I think I can unmask some stuff and it |
49 |
> will work. But wanted to cut the amount of masking down a little, and I'm |
50 |
> just curious why this happens. |
51 |
> |
52 |
> So, thanks for any insights, if want to practice your portage-fu, but don't |
53 |
> bother if you have more important things to do, I'm fine :) |
54 |
|
55 |
There was issues with pykde4 recently resulting in these blockers. Easiest way |
56 |
out is to remove all local masks you might have for PyQt and pykde4, unmerge |
57 |
both and emerge -uND world. Let portage sort it out. |
58 |
|
59 |
IIRC you can get by by just unmerging one of them and it works. But, I'm too |
60 |
lazy now to figure out which way round it goes, and memory ain't what it used |
61 |
to be. |
62 |
|
63 |
-- |
64 |
alan dot mckinnon at gmail dot com |