On Mon 15 Dec 2014 at 17:00:32 +0100, Svante Signell wrote: > Hi I trimmed the patch, less text now. However, the LILO comment is > still there. Do you want me to remove that one too?
A few other things should be considered for removal too. > + It is also a good idea to install > + <systemitem role="package"> sysvinit-core, sysvint and sysvinit-utils > + </systemitem> as the first packages when upgrading. I have explained in another post why this is bad idea for Wheezy users of upstart who do not want to change. It isn't even a good idea when the user wants to keep sysvinit. It is unnecessary advice and should be omitted. > + </para> </listitem> > + <listitem> <para> apt-get upgrade from Wheezy to Jessie can boot > + with init=/lib/sysvinit/init until the old sysvinit package > + is removed by e.g. autoclean. 'autoclean' will not remove an installed package from the system. > + <listitem> <para> > + If you have a desktop environment installed, it is also > + recommended to install <systemitem > + role="package">systemd-shim</systemitem> to > </para> > + <itemizedlist> > + <listitem> <para> > + assist apt and/or aptitude with the upgrade, Why do apt/aptitude require assistance? They have the pinning file and the dependencies of libpam-systemd to go on. If either of them get it wrong it is a bug and to be reported. This advice is superfluous. > + </para> </listitem> > + <listitem> <para> avoid getting <systemitem > + role="package">systemd-sysv</systemitem> installed by mistake, > + e.g. if you have forgotten to create the pinning file. </para> Apt's resolver not working would be a bug. A user error would not be a bug. The presence or absence of systemd-shim has no bearing on whether systemd-sysv is installed. This advice is technically incorrect and also superfluous. Regards, Brian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org