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