Excuse the top-posting; if I try inter-post between all those blockers
you'll never find what I reply :-)

First I recommend to sync your tree again, just in case you got yours
between two Qt commits and things are not consistent anymore.

You seem to have at least two things happening:

python-exec
qt

To deal with the first, try remove python-exec and re-merge it (but
quickpkg a backup first)

quickpkg python-exec && emerge -avC python-exec && emerge -av1 python-exec

This is untested so I don't know if it will bork. If it does, you have a
quickpkg that you can untar and get things back.

Onto Qt:

I've had similar things over the years and it always made little sense.
Eventually I removed all references to Qt from world, sets in use and
USE then let portage figure out what to do. Rationale: Qt is a basic
toolkit that stuff uses, so stuff should decide what it needs and not
me. I want the stuff and if that requires Qt then just let portage give
me what is required.

This will show all references to Qt to consider:

grep -ir /qt /etc/portage/ /var/lib/portage/world*


In your case, I see portage wants to downgrade several Qt packages due
to fsrunner, but there's nothing in that ebuild or the kde4-base eclass
it inherits, which leads me to believe you might have a config setting
somewhere that wants to exclude latest Qt somehow. Portage and the tree
by itself isn't doing it, here's my output:

$ emerge -pvt fsrunner

These are the packages that would be merged, in reverse order:

Calculating dependencies... done!
[ebuild  N     ] kde-misc/fsrunner-0.7.5:4  USE="(-aqua) -debug" 18 kB

Total: 1 package (1 new), Size of downloads: 18 kB




On 03/11/2013 00:02, 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:
> 
> Calculating dependencies... done!
>  * Invalid resume list:
>  * 
>  *   (u'ebuild', u'/', u'sys-apps/lshw-02.17b', u'merge')
>  *   (u'ebuild', u'/', u'net-print/foomatic-filters-4.0.17-r1', u'merge')
> [snipping some dozen lines]
>  *   (u'ebuild', u'/', u'media-video/kmplayer-0.11.3d-r1', u'merge')
>  *   (u'ebuild', u'/', u'media-libs/phonon-vlc-0.6.2', u'merge')
>  * 
>  * One or more packages are either masked or have missing dependencies:
>  * 
>  *   
> dev-lang/python-exec:=[python_targets_python2_7(-),python_targets_python3_2(-),-python_single_target_python2_6(-),-python_single_target_python2_7(-),-python_single_target_python3_2(-),-python_single_target_python3_3(-)]
>  pulled in by:
>  *     (dev-java/java-config-2.2.0::gentoo, installed)
> [snipping LOTS of similar output again]
>  *
>  *   
> dev-lang/python-exec:=[python_targets_python2_7(-),python_targets_python3_2(-),-python_single_target_python2_6(-),-python_single_target_python2_7(-),-python_single_target_python3_2(-),-python_single_target_python3_3(-)]
>  pulled in by:
>  *     (dev-libs/libpeas-1.8.1::gentoo, installed)
>  * 
>  *   
> dev-lang/python-exec:=[python_targets_python2_7(-),python_targets_python3_2(-),-python_single_target_python2_6(-),-python_single_target_python2_7(-),-python_single_target_python3_2(-),-python_single_target_python3_3(-)]
>  pulled in by:
>  *     (dev-python/pygobject-3.8.3::gentoo, installed)
>  * 
>  *   >=dev-libs/icu-3.8.1-r1:0/51.1= pulled in by:
>  *     (net-libs/webkit-gtk-1.10.2-r300::gentoo, installed)
>  * 
>  *   ~app-emulation/emul-linux-x86-medialibs-20130224 pulled in by:
>  *     (app-emulation/emul-linux-x86-qtlibs-20130224::gentoo, installed)
>  * 
>  * The resume list contains packages that are either masked or have
>  * unsatisfied dependencies. Please restart/continue the operation
>  * manually, or use --skipfirst to skip the first package in the list and
>  * any other packages that may be masked or have missing dependencies.
> 
> Wow, I don't even... anyway, I thought emerge -DuN @world might work now, but
> it does not, again due to Qt problems. And those I do not understand:
> 
> Total: 178 packages (148 upgrades, 9 downgrades, 12 new, 1 in new slot, 8 
> reinstalls, 4 uninstalls), Size of downloads: 349,914 kB
> Fetch Restriction: 1 package
> Conflict: 18 blocks
> 
> !!! 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)
> 
> dev-qt/qtcore:4
> 
>   (dev-qt/qtcore-4.8.4-r5::gentoo, ebuild scheduled for merge) pulled in by
>     ~dev-qt/qtcore-4.8.4[aqua=,debug=] required by 
> (dev-qt/qtscript-4.8.4::gentoo, ebuild scheduled for merge)
>     (and 4 more with the same problem)
> 
>   (dev-qt/qtcore-4.8.5::gentoo, installed) pulled in by
>     ~dev-qt/qtcore-4.8.5[aqua=,debug=,qt3support=] required by 
> (dev-qt/qtopengl-4.8.5::gentoo, installed)
>     >=dev-qt/qtcore-4.8.5:4 required by 
> (app-office/akonadi-server-1.10.3::gentoo, installed)
>     (and 12 more with the same problems)
> 
> dev-qt/qtscript:4
> 
>   (dev-qt/qtscript-4.8.5::gentoo, installed) pulled in by
>     ~dev-qt/qtscript-4.8.5[aqua=,debug=] required by 
> (dev-qt/designer-4.8.5::gentoo, installed)
>     (and 2 more with the same problem)
> 
>   (dev-qt/qtscript-4.8.4::gentoo, ebuild scheduled for merge) pulled in by
>     ~dev-qt/qtscript-4.8.4[aqua=,debug=] required by 
> (dev-qt/qtgui-4.8.4-r1::gentoo, ebuild scheduled for merge)
> 
> dev-qt/qtdbus:4
> 
>   (dev-qt/qtdbus-4.8.4::gentoo, ebuild scheduled for merge) pulled in by
>     ~dev-qt/qtdbus-4.8.4[aqua=,debug=] required by 
> (dev-qt/qtgui-4.8.4-r1::gentoo, ebuild scheduled for merge)
> 
>   (dev-qt/qtdbus-4.8.5::gentoo, installed) pulled in by
>     >=dev-qt/qtdbus-4.8.5:4 required by 
> (app-office/akonadi-server-1.10.3::gentoo, installed)
> 
> dev-qt/qt3support:4
> 
>   (dev-qt/qt3support-4.8.4::gentoo, ebuild scheduled for merge) pulled in by
>     ~dev-qt/qt3support-4.8.4[aqua=,debug=] required by
>     (dev-qt/qtgui-4.8.4-r1::gentoo, ebuild scheduled for merge)
> 
>   (dev-qt/qt3support-4.8.5::gentoo, installed) pulled in by
>     ~dev-qt/qt3support-4.8.5[aqua=,debug=] required by 
> (dev-qt/qtgui-4.8.5-r1::gentoo, installed)
>     (and 2 more with the same problem)
> 
> dev-qt/qtsql:4
> 
>   (dev-qt/qtsql-4.8.4::gentoo, ebuild scheduled for merge) pulled in by
>     ~dev-qt/qtsql-4.8.4[aqua=,debug=,qt3support] required by 
> (dev-qt/qt3support-4.8.4::gentoo, ebuild scheduled for merge)
> 
>   (dev-qt/qtsql-4.8.5::gentoo, installed) pulled in by
>     ~dev-qt/qtsql-4.8.5[aqua=,debug=,qt3support] required by 
> (dev-qt/qt3support-4.8.5::gentoo, installed)
>     >=dev-qt/qtsql-4.8.5:4[mysql?,postgres?] required by 
> (app-office/akonadi-server-1.10.3::gentoo, installed)
>     (and 1 more with the same problems)
> 
> So, 4.8.4 and 4.8.5 are somehow both needed. Let's start at the top: fsrunner
> and kdid3 need >=dev-qt/qtgui-4.7.4, which 4.8.5 also would satisfy, but one
> needs ~dev-qt/qtgui-4.8.4, and that is dev-qt/qt3support-4.8.4. What needs 
> that?
> 
> The 2nd entry from the bottom states that ~dev-qt/qt3support-4.8.4 is required
> by dev-qt/qtgui-4.8.4-r1.
> 
> The output also says 'and 1 more with the same problems' - might this be the
> real reason? How would I find out what package this is? The --tree output only
> shows fsrunner pulling in qtgui-4.8.4:
> 
> [nomerge       ] kde-misc/fsrunner-0.7.5:4::kde  USE="(-aqua) -debug" 
> [nomerge       ]  dev-qt/qtgui-4.8.4-r1:4 [4.8.5-r1:4] USE="accessibility 
> cups dbus%* exceptions gif%* glib gtkstyle mng nas pch qt3support tiff 
> xinerama xv (-aqua) -c++0x% -debug -egl -nis -trace" 
> [ebuild     UD ]   dev-qt/qt3support-4.8.4:4 [4.8.5:4] USE="accessibility 
> exceptions pch (-aqua) -c++0x% -debug" 0 kB
> [ebuild     UD ]    dev-qt/qtgui-4.8.4-r1:4 [4.8.5-r1:4] USE="accessibility 
> cups dbus%* exceptions gif%* glib gtkstyle mng nas pch qt3support tiff 
> xinerama xv (-aqua) -c++0x% -debug -egl -nis -trace" 0 kB
> [ebuild     UD ]     dev-qt/qtdbus-4.8.4:4 [4.8.5:4] USE="exceptions pch
> (-aqua) -c++0x% -debug" 0 kB
> 
> The ebuilds for fsrunner and kdid3 only have the 'interit kde4-base' line, no
> special dependencies.
> 
> 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.
> 
>       Alex
> 


-- 
Alan McKinnon
alan.mckin...@gmail.com


Reply via email to