On Thu 31 Jul 2014 at 20:12:56 +0100, Mark Carroll wrote: > Perhaps coincidentally, just rather recently I've noticed a change, with > stable pinned at 600 and testing at 50:
I don't use pinning so don't appreciate the significance of this. > root:/# apt-get upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > root:/# apt-get dist-upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > The following NEW packages will be installed: > init sysvinit-core > 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. > Need to get 134 kB of archives. > After this operation, 283 kB of additional disk space will be used. > Do you want to continue [Y/n]? init is a new metapackage. It depends on one of sysvinit-core, systemd-sysv or upstart. It ensures there is one of these available on the system at all times. At the present time sysvinit-core is the default. > I wonder what changed, if anything would break if I went ahead. Do you or do you not want an init system? If your preference is for systemd-sysv install it before upgrading. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/31072014230932.22cbcbbb4...@desktop.copernicus.demon.co.uk
