The Wanderer <wande...@fastmail.fm> writes: > There is a considerable difference, however, between automatically > installing the new version of a program (even if in a different package > for whatever reason) and automatically installing a completely different > program from the original, simply because both programs are intended for > the same role.
> You could argue that it's appropriate to do anyway - e.g. that it would > be appropriate to automatically switch existing systems from gcc to > clang if the default compiler referenced by build-essential got changed. > It still shouldn't be treated as the same thing as a simple version > upgrade, however. I think we need some sort of critical debconf prompt here for the jessie release, similar to how we handled the change of /bin/sh to dash and how we handled the switch to startpar. Probably in systemd-sysv, which is the package that forces the conversion. It's quite surprising to, for example, install network-manager (which is an application that ca be used with non-GNOME window managers) and end up with a new init system. As for the original question, systemd-sysv was probably installed as a dependency of either gdm3 or network-manager by way of libpam-systemd (which provides cgroup setup). -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/8738giyla6....@windlord.stanford.edu
