Hi Svante, Brian: thanks for your comments; I tend to agree.
I've just checked; the patch applies: joostvb@nusku:~/svn/release-notes% patch -p0 < /tmp/en_issues.dbk.patch patching file en/issues.dbk Hunk #1 succeeded at 206 (offset 28 lines). Hunk #2 succeeded at 224 (offset 28 lines). Hunk #3 succeeded at 235 (offset 28 lines). . Some more comments/issues with the patch: Chapter 5. Issues to be aware of for jessie is about "Sometimes, changes introduced in a new release have side-effects we cannot reasonably avoid, or they expose bugs somewhere else. This section documents issues we are aware of." I feel tips on how to override the new default init system do not belong here. Another place would likely be more suitable. Why do you use an <itemizedlist>? I feel just putting the <listitem>s in normal paragraphs is better. On Mon, Dec 15, 2014 at 06:10:08PM +0000, Brian Potkin wrote: > 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? "grub will get a new menu entry to boot with init=/lib/sysvinit/init if something goes wrong with the switch to systemd-sysv. If you are using some other bootloader, e.g. LILO you are on your own." Perhaps something like: If you don't use grub as bootloader, but e.g. LILO, changing to grub before upgrading to Jessie makes the upgrade more robust. During the migration from SysV init to systemd, grub will have an entry init=/lib/sysvinit/init, in order to keep the system bootable with the old SysV. . > A few other things should be considered for removal too. <snip> > > + </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. So just remove "by e.g. autoclean". > > + <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. I suggest something like: "The package <systemitem role="package">systemd-shim</systemitem> implements interfaces needed by desktop environment helpers expecting systemd-like functionality. The packagemanagement system will install this package if you use such a desktop environment without running systemd as init system." Bye, Joost -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
