As per Summary. pinkbyte@oas1 ~ $ cat /var/lib/portage/world_sets @kdebase pinkbyte@oas1 ~ $ cat /var/lib/layman/kde/sets/kdebase # Autogenerated by regenerate-files, DO NOT EDIT. kde-base/kdebase-meta:4 @kde-baseapps @kdebase-runtime @kdebase-workspace-4.11 pinkbyte@oas1 ~ $ cat /var/lib/layman/kde/sets/kdebase-workspace-4.11 | grep kgreeter <kde-base/libkgreeter-4.11.50 pinkbyte@oas1 ~ $ emerge -uDN world -pv (output omitted) [blocks B ] <kde-base/kdm-4.11.17-r1 ("<kde-base/kdm-4.11.17-r1" is blocking kde-base/libkgreeter-4.11.17) * Error: The above package list contains packages which cannot be * installed at the same time on the same system. (kde-base/libkgreeter-4.11.17:4/4.11::gentoo, ebuild scheduled for merge) pulled in by kde-base/libkgreeter:4 required by @kdebase-workspace (kde-base/kdm-4.11.14:4/4.11::gentoo, installed) pulled in by kde-base/kdm:4 required by @kdebase-workspace >=kde-base/kdm-4.11:4[aqua=] (>=kde-base/kdm-4.11:4[-aqua]) required by (kde-base/kdebase-meta-4.14.3:4/4::gentoo, installed) >=kde-base/kdm-4.11.14:4[aqua=] (>=kde-base/kdm-4.11.14:4[-aqua]) required by (kde-base/ksmserver-4.11.14:4/4.11::gentoo, installed)
Sets have no mechanism to distinguish between stable or not.
(In reply to Michael Palimaka (kensington) from comment #1) > Sets have no mechanism to distinguish between stable or not. I know that. And i do not require such mechanism. Just do it one way or another - either drop libkgreeter from kdebase-workspace or stabilize it and new kdm. It can be non-trivial, if new KDM can not be stabilized without stabilizing all of the new KDE ebuilds... As i can see, libkgreeter is pulled by new KDM. I am not sure, but what side effects will pop up if we just drop it from set?
It'll be stabilised in due course, I'm not there's much else we can do though.
Stabilization is in preparation. In the meanwhile we keeping the sets untouched as we need them to do the bumps.
