On Sat, Nov 02, 2013 at 11:02:27PM +0100, Alex Schuster wrote:
> Hi there!
> 
> My @world update did not go well. It was much worse some while ago, so I
> just did an emerge -e @world, after manually removing stuff
> from /var/lib/portage/world until I got no complaints any more. I had to
> remove kde-misc/publictransport and kde-misc/plasma-emergelog for that.
> 
> After most was done, it stopped after one package failed to build, and
> was unable to resume due to blockers. emerge --resume gives this:
> 
> weird portage # emerge -aj --resume
> 
> These are the packages that would be merged, in order:
> [...]
> !!! Multiple package instances within a single package slot have been pulled
> !!! into the dependency graph, resulting in a slot conflict:
> 
> dev-qt/qtgui:4
> 
>   (dev-qt/qtgui-4.8.5-r1::gentoo, installed) pulled in by
>     >=dev-qt/qtgui-4.8.5:4[accessibility,dbus(+)] required by 
> (kde-base/libkworkspace-4.11.2::gentoo, installed)
>     ~dev-qt/qtgui-4.8.5[aqua=,debug=,egl=,qt3support=] required by 
> (dev-qt/qtopengl-4.8.5::gentoo, installed)
>     (and 283 more with the same problems)
> 
>   (dev-qt/qtgui-4.8.4-r1::gentoo, ebuild scheduled for merge) pulled in by
>     >=dev-qt/qtgui-4.7.4:4[accessibility,dbus] required by
>   (kde-misc/fsrunner-0.7.5::kde, installed)
>   >=dev-qt/qtgui-4.7.4:4[accessibility,dbus] required by
>   (media-sound/kid3-2.2.1::kde, installed)
>   ~dev-qt/qtgui-4.8.4[accessibility=,aqua=,debug=,qt3support] required by
>   (dev-qt/qt3support-4.8.4::gentoo, ebuild scheduled for merge) (and 1
>   more with the same problems)
> [...]
> Any enlightenment would be very much appreciated. I just don't know how to get
> my system back working. ATM, KDE is mostly at version 4.11.2-r1, but some KDE
> packages still need to be updated. So, it does not work right now, unknown
> protocol file and such errors.

I, too, had been having qt blocking qt, and I had no idea what was
causing it. I guess I caused it myself because I updated qt with
--nodeps (long story, kde 4.11.2 needs akonadi-server 1.10.3 which
needed the then keyworded qt 4.8.5).

Both 4.8.4 and 4.8.5 were stable by the end, but still something caused
to pull in both, just as in your output. Yesterday I wanted to clean up
emerge output so I can ask about it here. So I updated everything except
qt (without --nodeps). And now world update is clean again.
-- 
Gruß | Greetings | Qapla’
Please do not share anything from, with or about me with any Facebook service.

Yesterday we stood at the abyss.  Today we are one step further.

Attachment: signature.asc
Description: Digital signature

Reply via email to