On 14/03/2015 11:10, [email protected] wrote:
> Alan McKinnon <[email protected]> [15-03-14 09:48]:
>> On 14/03/2015 09:36, [email protected] wrote:
>>> Hi,
>>>
>>> emerge hits me:
>>>
>>> Whiletrying to reolve a lot of blockers, emerge @preserved-rebuild
>>> gives me this:
>>>
>>> emerge: there are no ebuilds to satisfy "kde-base/solid:4".
>>> (dependency required by "@preserved-rebuild" [argument])
>>>
>>> emerge itself can be called without that error.
>>> How can an argument to a command haves a dependency?
>>>
>>> How can I get out of this?
>>
>>
>> It's portage's insanely obtuse output that is getting you confused, but
>> the error is with an ebuild, not portage.
>>
>> First, there is not such package as "solid" with SLOT=4:
>>
>> # eix -e solid
>> * kde-frameworks/solid
>> Available versions: (5) (~)5.7.0(5/5.7)
>> {debug doc nls test}
>> Homepage: http://www.kde.org/
>> Description: Framework providing platform independent
>> hardware discovery, abstraction, and management
>>
>>
>> Then, all that "dependency required by..." output from portage is an
>> effort to show you what is pulling a package in, and it starts at the
>> beginning. Portage knows it's dealing with whatever is in the
>> @preserved-rebuild set, and that set has packages in it. Each of those
>> packages may have other deps, and so on.
>>
>> In your case, it seems to be solid-actions-kcm that's causing it
>>
>> # grep -r "kde-base/solid:4" /var/portage/
>> /var/portage/kde-base/solid-actions-kcm/solid-actions-kcm-4.11.14.ebuild:
>> !kde-base/solid:4
>>
>>
>>
>> I have no idea if this will work, but here's what I'd do:
>>
>> skip @preserved-rebuild for now, and run
>> revdep-rebuild
>> emerge -a --depclean
>>
>> So if that changes things. Also make sure neither solid nor
>> solid-actions-kcm are in world, they should be deps pulled in automatically.
>>
>> Also move /var/lib/portage/preserved_libs_registry out of the way if it
>> has junk in it and let revdep-rebuild fix things.
>>
>> Finally, you did sync ran emerge world recently, right?
>
> Hi Alan,
>
> thanks for your reply ! :)
No problem.
Huge amounts of portage output snipped below, but I think you are trying
to have stable Qt4 and unstable Qt5 on the same system. That doesn't
work currently, I'll walk through my reasoning so you can see what's
going on:
>
> ...interesting...one needs to use grep to resolve a problem of
> portage ;)
Hah yes, that's quite funny.
I wanted to see what the ebuilds actually say, not what portage tools
think they say :-)
>
>
> Things are going even more worst (correct English???...uh, sound like
> german English...;;;))):
>
> revdep-rebuild runs fine and found nothing to rebuild.
> depclean stops its work and said:
>
> Calculating dependencies... done!
> * Dependencies could not be completely resolved due to
> * the following required packages not being installed:
> *
> * >=dev-qt/qtgui-4.8.5:4[accessibility,dbus(+)] pulled in by:
> * kde-base/kglobalaccel-4.14.3
[... huge snip]
Basically, of this part really means that you need Qt:4
It *can* co-exist with Qt5, I have them both installed here.
> Since packages are missing I tried:
> emerge --update --newuse --deep --with-bdeps=y @world --tree --keep-going -v
>
>
> which prints:
> These are the packages that would be merged, in reverse order:
>
> Calculating dependencies... done!
[...snip...]
> [blocks B ] <dev-qt/qtgui-4.8.6:4 ("<dev-qt/qtgui-4.8.6:4" is blocking
> dev-qt/qtchooser-0_p20150102)
> [blocks B ] <dev-qt/qtsql-4.8.6:4 ("<dev-qt/qtsql-4.8.6:4" is blocking
> dev-qt/qtchooser-0_p20150102)
> [blocks B ] <dev-qt/qtcore-4.8.6:4 ("<dev-qt/qtcore-4.8.6:4" is blocking
> dev-qt/qtchooser-0_p20150102)
> [blocks B ] <dev-qt/qthelp-4.8.6:4 ("<dev-qt/qthelp-4.8.6:4" is blocking
> dev-qt/qtchooser-0_p20150102)
> [blocks B ] <dev-qt/qtopengl-4.8.6:4 ("<dev-qt/qtopengl-4.8.6:4" is
> blocking dev-qt/qtchooser-0_p20150102)
> [blocks B ] <dev-qt/qt3support-4.8.6:4 ("<dev-qt/qt3support-4.8.6:4" is
> blocking dev-qt/qtchooser-0_p20150102)
> [blocks B ] <dev-qt/qtsvg-4.8.6:4 ("<dev-qt/qtsvg-4.8.6:4" is blocking
> dev-qt/qtchooser-0_p20150102)
> [blocks B ] <dev-qt/qtmultimedia-4.8.6:4 ("<dev-qt/qtmultimedia-4.8.6:4"
> is blocking dev-qt/qtchooser-0_p20150102)
> [blocks B ] <dev-qt/qtdeclarative-4.8.6:4
> ("<dev-qt/qtdeclarative-4.8.6:4" is blocking dev-qt/qtchooser-0_p20150102)
> [blocks B ] <dev-qt/designer-4.8.6:4 ("<dev-qt/designer-4.8.6:4" is
> blocking dev-qt/qtchooser-0_p20150102)
> [blocks B ] <dev-qt/qttest-4.8.6:4 ("<dev-qt/qttest-4.8.6:4" is blocking
> dev-qt/qtchooser-0_p20150102)
> [blocks B ] <dev-qt/qtxmlpatterns-4.8.6:4
> ("<dev-qt/qtxmlpatterns-4.8.6:4" is blocking dev-qt/qtchooser-0_p20150102)
> [blocks B ] <dev-qt/qtwebkit-4.8.6:4 ("<dev-qt/qtwebkit-4.8.6:4" is
> blocking dev-qt/qtchooser-0_p20150102)
> [blocks B ] <dev-qt/qtdbus-4.8.6:4 ("<dev-qt/qtdbus-4.8.6:4" is blocking
> dev-qt/qtchooser-0_p20150102)
> [blocks B ] <dev-qt/qtscript-4.8.6:4 ("<dev-qt/qtscript-4.8.6:4" is
> blocking dev-qt/qtchooser-0_p20150102)
[... snip big list of what wants Qt stuff]
dev-qt/qtchooser seems to be the main culprit here. In that ebuild:
RDEPEND="
...
!<dev-qt/qtgui-4.8.6:4
...
And so on and so on
This eix shows what I think might be your main problem:
# eix -e qtgui
[I] dev-qt/qtgui
Available versions:
(4) 4.8.5-r3 (~)4.8.6-r1
(5) (~)5.4.1^t
Looks like you are running a stable system, but you keyworded Qt5. Is
that correct? The above ebuild shows that unstable Qt5 blocks stable
Qt4, so you will have to fix that first.
1. Find and uninstall what apps you have that need Qt5, or
2. Keyword Qt4 unstable and let portage figure out how to resolve the
blockers
> Uuuuh..,thats much.
>
> Should I buy a new harddisk and start right from the beginning?
No :-)
About 30 lines in package.accept_keywords should be enough :-)
--
Alan McKinnon
[email protected]
