I just did not quite understand - is this a bug (so I can wait and no d-u until this dependency goes away)?
Or, I *must* install systemd-shim now, to be able to d-u for the future without converting to systemd-sysv?

thanks,

manul

yossarian

Post subject:Posted: 07.05.2014, 00:15

Joined: 2010-09-11
Posts: 35

Status: Offline

It's not a bug.
If you don't want systemd-sysv just install systemd-shim instead.

P.S. Is there any way so I can get from apt, such sort of information:
"new package xxx is going to be installed because it is dependency of package yyy"; without manually traversing all the list of recursive dependencies of all possible packages involved, one by one?

@titan, when manul posted his apt output, his machine wasn't removing sysvinit-core, so is your case different? If sysvinit-core really is to be removed (and replaced by systemd-sysv) then you may face serious issues like I did last week - see my thread linked above if you didn't already. And do what yossarian suggested and install systemd-shim before DU.

manul

Post subject:Posted: 07.05.2014, 16:46

Joined: 2010-09-13
Posts: 111

Status: Offline

towo wrote:

Quote:

Systemd still wants to be installed...

And?
installed != used
Or do you see sysvinit to be removed?

If it is not going to be "used" at all, why should then it be "installed" at all?

I have some fedora boxes with systemd, but (for various reasons) do not feel comfortable for using it with my aptosid machines (unless it is absolutely unavoidable).

I do not want to argue for anything; I just want to know better what is going on (and what Debian's systemd policy will effectively turn out to be in reality).

I was under impression (could be wrong) that while systemd gets default init with Debian, Debian should still officially support alternate init systems as well - well at least for some time (without systemd binary being used either as PID 1, or any other way)?

spock, yossarian and others:
Right now, policykit-1 dependency of systemd (via libpam-systemd) should be satisfied by alternative systemd-shim; and all I ask is how do I find which exactly package still "pulls" systemd as a dependency.
No one answered this yet btw, and this is a generic question (I was wondering about it before as well, for other packages).

Thanks,
manul

mheyes

Post subject:Posted: 07.05.2014, 19:32

Joined: 2011-02-10
Posts: 42

Status: Offline

I just did a d-u, systemd installed, nothing removed. Then, apt-get purge systemd, and systemd was removed but nothing else. Ridiculous.