On Tue, 2010-05-18 at 19:43 -0400, Philip Webb wrote:
> 100518 Lindsay Haisley wrote:
> > what I have to do to resolve it?
> >> !!! Multiple package instances within a single package slot have been
> >> pulled
> >> !!! into the dependency graph, resulting in a slot conflict:
> >> dev-python/gnome-vfs-python:2
> >> ('installed', '/', 'dev-python/gnome-vfs-python-2.26.1', 'nomerge')
> >> pulled in by
> >> >=dev-python/gnome-vfs-python-2.26.1 required by ('installed', '/',
> >> 'dev-python/libgnome-python-2.26.1', 'nomerge')
> >> (and 2 more)
> >> ('ebuild', '/', 'dev-python/gnome-vfs-python-2.22.3', 'merge') pulled in
> >> by
> >> ~dev-python/gnome-vfs-python-2.22.3 required by ('installed', '/',
> >> 'dev-python/gnome-python-2.22.3', 'nomerge')
> >> (and 2 more)
>
> A quick suggestion by someone who doesn't use any of these is
> that you have incompatible versions of Libgnome-python & Gnome-python:
> the latter is a meta-pkg & an earlier version, so try unmerging it.
I'll take a look at this, but I'm looking for a broader understanding of
this kind of message since I'm getting a number of them (this is only
one set). What's the difference between "required by" and "pulled in
by"? Are these message documented and explained somewhere?
--
Lindsay Haisley | "Real programmers use butterflies"
FMP Computer Services | - xkcd
512-259-1190 |
http://www.fmp.com |
