I haven't updated my system for a while. I'm trying to emerge @world and I get this strange conflict. Does anyone know how to resolve it? Is portage supposed to raise a conflict for the same version of a package? !!! Multiple versions within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict: dev-db/sqlite:3 ('ebuild', '/', 'dev-db/sqlite-3.5.9', 'merge') pulled in by @world ('ebuild', '/', 'media-sound/amarok-1.90-r1', 'merge') ('installed', '/', 'dev-db/sqlite-3.5.9', 'nomerge') pulled in by @world ('installed', '/', 'dev-ruby/sqlite3-ruby-1.2.4', 'nomerge') ('ebuild', '/', 'dev-libs/nspr-4.7.3', 'merge') (and 8 more)
Created attachment 172191 [details] emerge --info
As a work around, it is sufficient to modify amarok-1.90-r1.ebuild as follows. It really looks like a part of portage isn't fully aware of the newer syntax. --- /usr/portage/media-sound/amarok/amarok-1.90-r1.ebuild 2008-11-01 15:36:20.000000000 +0100 +++ amarok-1.90-r1.ebuild 2008-11-18 13:28:05.000000000 +0100 @@ -20,7 +20,7 @@ DEPEND=" >=app-misc/strigi-0.5.7 - dev-db/sqlite:3[threadsafe] + dev-db/sqlite:3 kde-base/kdelibs:${SLOT} kde-base/libplasma:${SLOT} >=media-libs/taglib-1.5
Created attachment 172271 [details, diff] show unsatisfied USE dependency output when a slot conflict occurs due to USE dependencies If this patch is saved as /tmp/use-conflict.patch, then it can be applied as follows: patch /usr/lib/portage/pym/_emerge/__init__.py /tmp/use-conflict.patch This patch will hopefully make the output a little easier to understand. Rather than modify the dependencies of the ebuild, you should be modifying your USE settings in /etc/make.conf or /etc/portage/package.use.
This is fixed in 2.2_rc15.
This output is improved some more now (bug #249185).