On 14/03/2015 09:36, meino.cra...@gmx.de 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?
--
Alan McKinnon
alan.mckin...@gmail.com
