Debian is moving to systemd now. Unstable and testing are getting dependencies on systemd from various packages. Now is a good time to transition, it's been working well for me for over a year. -- Sent from my Samsung Galaxy Note 2 with K-9 Mail.

Jason White <jason@jasonjgw.net> writes:

When I run an aptitude full-upgrade, I am prompted to remove sysvinit-core and replace it with systemd-sysv.

does this mean that Debian Sid is making the transition now, or is it the result of the specific combination of packages that I happen to have installed?

To be clear, I want to make the change to Systemd, while minimizing the risk of an unbootable system in the transition, and I'm considering whether now is the time to go ahead with it or not.

FWIW jessie hasn't forced me to install systemd-sysv yet. I *did* have to install these systemd components: udev was pulled in by initramfs-tools & Xorg. libsystemd-id128-0 was pulled in by festival. libsystemd-journal0 and libsystemd-login0 were pulled in by dbus. At a glance, it looks like KDE and the various display managers (e.g. gdm3) force you to install systemd-sysv right now, and the XFCE and GNOME session managers Recommend it (i.e. opt out). Also a few other bits like upower, udisks2 and gnome-bluetooth. There is "aptitude why", or from within the aptitude UI you can tap "i" a couple of times until the bottom pane shows similar output, e.g. for gnome-bluetooth I see: i twb-desktop Recommends xinit i A xinit Recommends xterm | x-session-manager | x-window-manager | x-terminal-emulator p cinnamon Provides x-window-manager p cinnamon Recommends cinnamon-bluetooth p cinnamon-bluetooth Depends gnome-bluetooth