On Sunday 29 March 2009 08:26:45 John P. Burkett wrote:
> Working on a amd64 machine, I did
> emerge -D -uav world
> and got the following response:
>
> !!! Multiple package instances within a single package slot have been
> pulled !!! into the dependency graph, resulting in a slot conflict:
>
> dev-lang/python:2.5
>
> ('installed', '/', 'dev-lang/python-2.5.2-r7', 'nomerge') pulled in by
> dev-lang/python required by ('installed', '/',
> 'dev-libs/libxslt-1.1.24-r1', 'nomerge')
>
> >=dev-lang/python-2.2 required by ('installed', '/',
>
> 'app-pda/libopensync-0.22', 'nomerge')
> dev-lang/python required by world
> (and 19 more)
>
> ('ebuild', '/', 'dev-lang/python-2.5.2-r7', 'merge') pulled in by
>
> >=dev-lang/python-2.3[-build,xml] required by ('ebuild', '/',
>
> 'app-text/iso-codes-3.6', 'merge')
> dev-lang/python required by world
I'm not sure why portage is telling you this; two packages (at least) want to
merge python-2.5.2-r7
Try emerge python on it's own then emerge world, portage's confusion should
then not be present
[snip]
> emerge: there are no ebuilds built with USE flags to satisfy
> ">=app-text/poppler-bindings-0.8[gtk,cairo]".
> !!! One of the following packages is required to complete your request:
> - app-text/poppler-bindings-0.10.4 (Change USE: +cairo)
> (dependency required by "app-text/evince-2.24.2" [ebuild])
> (dependency required by "world" [argument])
Put 'cairo' in your USE and run emerge world again.
Portage is bitching that poppler-bindings does not have cairo support while
evince requires this. Portage will not automatically change your USE flags in
this case as it assumes you have a very good reason for setting them that way.
>
> I would be grateful for suggestions as to (1) which package if any
> should be masked, and (2) what to do about app-text/poppler-bindings.
>
> John
--
alan dot mckinnon at gmail dot com
