ConsoleKit is for all practical purposes unmaintained, and all of the packages you mentioned it support systemd just fine. Emerge systemd, and purge CK from your system; I did that almost a year ago.
Regards. On Mon, Jul 22, 2013 at 2:03 AM, Helmut Jarausch <jarau...@igpm.rwth-aachen.de> wrote: > Hi, > > gnome-base/gnome-settings-daemon-3.8.4 requires systemd > > sys-auth/consolekit-0.4.6 cannot coexist with systemd > > but many packages depend on sys-auth/consolekit : > > emerge -vpc sys-auth/consolekit gives > > sys-auth/consolekit-0.4.5_p20120320-r2 pulled in by: > gnome-base/gnome-session-3.8.2.1-r1 requires sys-auth/consolekit > gnome-base/gnome-shell-3.8.3-r1 requires sys-auth/consolekit > kde-base/kdm-4.10.5 requires sys-auth/consolekit > net-misc/networkmanager-0.9.8.2-r2 requires sys-auth/consolekit > net-wireless/bluez-4.101-r5 requires sys-auth/consolekit > sys-apps/accountsservice-0.6.34 requires sys-auth/consolekit > sys-auth/pambase-20120417-r2 requires >>=sys-auth/consolekit-0.4.5_p2012[pam] > sys-auth/polkit-0.111 requires sys-auth/consolekit[policykit] > x11-apps/xdm-1.1.11-r3 requires sys-auth/consolekit > x11-misc/slim-1.3.5-r2 requires sys-auth/consolekit > > > So, what to do? Obviously, I don't want an unbootable system. > > How did you resolve this conflict? > > Many thanks for a hint, > Helmut -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
