On 7/21/09, Alan McKinnon <alan.mckin...@gmail.com> wrote:
> On Tuesday 21 July 2009 17:11:33 Alex Schuster wrote:
>> Hi there!
>>
>> My @world update shows this problem:
>>
>> !!! Multiple package instances within a single package slot have been
>> pulled !!! into the dependency graph, resulting in a slot conflict:
>>
>> dev-python/PyQt4:0
>>
>> ('ebuild', '/', 'dev-python/PyQt4-4.4.4-r5', 'merge') pulled in by
>>
>> >=dev-python/PyQt4-4.4.0[X] required by ('installed', '/', 'kde-
>>
>> base/plasma-workspace-4.2.4', 'nomerge')
>> dev-python/PyQt4[X] required by ('installed', '/', 'media-
>> sound/picard-0.11', 'nomerge')
>>
>> >=dev-python/PyQt4-4.4 required by ('ebuild', '/', 'dev-
>>
>> python/qscintilla-python-2.3.2-r2', 'merge')
>> (and 1 more)
>>
>> ('ebuild', '/', 'dev-python/PyQt4-4.4.4-r2', 'merge') pulled in by
>>
>> >=dev-python/PyQt4-4.4.4-r1[dbus,qt3support,svg,webkit,X] required by
>>
>> ('ebuild', '/', 'kde-base/pykde4-4.2.4', 'merge')
>> (and 4 more)
>>
>> I would like to understand where the problem is. The bottom says that
>> pykde4-4.2.4 needs at least PyQt4-4.4.4-r2. This is fine, I can see the
>> corresponding DEPEND line in the pykde4-4.2.4 ebuild.
>>
>> The top list tells that:
>> plasma-workspace-4.2.4 needs PyQt4-4.4.0,
>> picard-0.11 needs PyQt4 and
>> qscintilla-python-2.3.2-r2 needs PyQt4-4.4
>>
>> Why then is PyQt4-4.4.4-r5 needed? -r2 should satisfy these needs, too,
>> doesn't it? Or is the problem the 'and 1 more' line? How would I find out
>> which other package would need -r5 then? And why would the other line be
>> listed then? I don't get this.
>>
>> I grepped for PyQt4-4.4.4-r5 through all ebuilds, it appeared only in the
>> PyQt4-4.4.4-r5.ebuild itself.
>>
>> This is not an important problem - I think I can unmask some stuff and it
>> will work. But wanted to cut the amount of masking down a little, and I'm
>> just curious why this happens.
>>
>> So, thanks for any insights, if want to practice your portage-fu, but
>> don't
>> bother if you have more important things to do, I'm fine :)
>
> There was issues with pykde4 recently resulting in these blockers. Easiest
> way
> out is to remove all local masks you might have for PyQt and pykde4, unmerge
> both and emerge -uND world. Let portage sort it out.
>
> IIRC you can get by by just unmerging one of them and it works. But, I'm too
> lazy now to figure out which way round it goes, and memory ain't what it
> used
> to be.
PyQt4-4.5.1 ebuild was removed from the portage tree over the weekend.
I had only that specific version unmasked (IIRC kde4 dependencies?),
and ran into a similar(?) situation yesterday. Maybe you hit the same?
(Similar situation == portage surprises and wants to downgrade PyQt4
to 4.4.4-something.)
No worries, IIRC I just unmasked 4.5.2 and everything has been smiles
and sunshine again afterward.
--
Arttu V.
