A patch for all these copy-editing issues. Mostly I've just assumed
that the appropriate solution is to snip out the troublesome bits.
JBR - and today's single word in West Greenlandic is:
"Silly me, I went and spoke out of turn as usual!"
diff -ru release-notes.pristine//en/issues.dbk release-notes/en/issues.dbk
--- release-notes.pristine//en/issues.dbk 2011-02-01 17:35:20.496916343 +0000
+++ release-notes/en/issues.dbk 2011-02-01 17:56:42.841258893 +0000
@@ -75,9 +75,9 @@
Versions of <systemitem role="package">grub-pc</systemitem> older than
1.98+20100720-1 will not be able to boot directly off
a <acronym>RAID</acronym> with the 1.x metadata formats (the new default is
-1.2). To ensure a bootable system, please make sure to use <systemitem
-1.98+20100720-1 or later, which is provided by Debian &releasename;. An
+1.2). To ensure a bootable system, please make sure that the new
+version of <systemitem role="package">grub-pc</systemitem> provided by Debian
+&releasename; has installed its bootloader code to the disk. An
unbootable system may be rescued with <ulink
url="http://www.supergrubdisk.org/super-grub2-disk/">Super Grub2 Disk</ulink>
or <ulink url="http://grml.org">grml</ulink>.
@@ -87,7 +87,8 @@
<title>pam_userdb.so breakage with newer libdb</title>
-Some Berkeley Database version 7 files created with libdb3 cannot be read by
+If you authenticate users against a Berkeley DB database, you should
+be aware that some db version 7 files created with libdb3 cannot be read by
newer libdb versions (see bug <ulink url="&url-bts;521860">#521860</ulink>).
As a workaround, the files can be recreated with <command>db4.8_load</command>,
from the <systemitem role="package">db4.8-util</systemitem> package.
@@ -444,10 +445,9 @@
url="http://www.iana.org/assignments/port-numbers">the IANA registry</ulink>.
-Starting with the version 4.38 of the Debian <systemitem
-role="package">netbase</systemitem> package, the <literal>sieve</literal>
-service will be moved from port 2000 to port 4190 in the
+In the version of <systemitem role="package">netbase</systemitem> in
+&releasename, the <literal>sieve</literal> service has been moved from port
+2000 to port 4190 in the <filename>/etc/services</filename> file.
Any installs which used the <literal>sieve</literal> service name instead of a
@@ -639,8 +639,7 @@
granted automatically to the user currently logged on physically to the
system: video and audio devices, network roaming, power management,
device mounting. The cdrom, floppy, audio, video, plugdev and powerdev
-groups are no longer useful. See the <systemitem
-role="package">consolekit</systemitem> documentation for more information.
+groups are no longer useful.
Most graphical programs requiring root permissions now rely on <ulink
@@ -721,11 +720,11 @@
- <title>Kernel mode setting</title>
+ <title>Kernel mode-setting</title>
Kernel drivers for Intel (starting from i830), ATI/AMD (from the
original Radeon to the Radeon HD 5xxx <quote>Evergreen</quote> series)
- and for NVIDIA graphics chipsets now support native mode setting.
+ and for NVIDIA graphics chipsets now support native video mode setting.
Support for old-style userspace mode setting is discontinued in the
diff -ru release-notes.pristine//en/upgrading.dbk release-notes/en/upgrading.dbk
--- release-notes.pristine//en/upgrading.dbk 2011-02-01 17:35:20.493027527 +0000
+++ release-notes/en/upgrading.dbk 2011-02-01 17:45:33.093263258 +0000
@@ -293,7 +293,7 @@
-To perform this review, launch <command>aptitude</command> in <quote>visual mode</quote> and
+To perform this review, launch <command>aptitude</command> in full-screen mode and
press <keycap>g</keycap> (<quote>Go</quote>). If it shows any actions, you should review them and either fix
them or implement the suggested actions. If no actions are suggested you will
be presented with a message saying <quote>No packages are scheduled to be installed,
@@ -1251,8 +1251,7 @@
you can also use the kernel sources, provided in the <systemitem
role="package">linux-source-2.6</systemitem> package. You can make use of the
<literal>deb-pkg</literal> target available in the sources' makefile for
-building a binary package. There are some differences in these two approaches,
-please consult the respective package's documentation.
+building a binary package.
If possible, it is to your advantage to upgrade the kernel package separately
@@ -1921,28 +1920,13 @@
<command>apt-get</command> to manually install packages in &oldreleasename;
it will have kept track of those packages you manually installed and will be
able to mark as obsolete those packages pulled in by dependencies alone which
-are no longer needed if a package has been removed.
-<command>aptitude</command> and <systemitem role="package">apt</systemitem>,
-unlike <command>deborphan</command>, will not mark for removal packages that
-you manually installed, as opposed to those that were automatically
-installed through dependencies. To remove automatically installed packages
-that are no longer used, run:
+are no longer needed if a package has been removed. To remove
+automatically installed packages that are no longer used, run:
# apt-get autoremove
-There are additional tools you can use to find obsolete packages such as
-<command>deborphan</command>, <command>debfoster</command> or
-<command>cruft</command>. <command>deborphan</command> is highly recommended,
-although it will (in default mode) only report obsolete libraries: packages in
-the <quote><literal>libs</literal></quote> or <quote><literal>oldlibs</literal></quote> sections that are not used by any other packages. Do not
-blindly remove the packages these tools present, especially if you are using
-aggressive non-default options that are prone to produce false positives. It
-is highly recommended that you manually review the packages suggested for
-removal (i.e. their contents, size and description) before you remove them.
The <ulink url="&url-bts;">Debian Bug Tracking System</ulink>
often provides additional information on why the package was removed. You
should review both the archived bug reports for the package itself and the
@@ -2017,13 +2001,11 @@
<systemitem role="package">apt-proxy</systemitem> is no longer
- provided, alternatives to this tool include
+ provided; although no automatic upgrade path exists, users can
+ switch to alternatives such as
- <systemitem role="package">apt-cacher</systemitem> and
- <systemitem role="package">approx</systemitem>. Although no
- automatic upgrade path exists, user of <systemitem
- role="package">apt-proxy</systemitem> can switch to these alternatives
- by manually installing any of these packages.
+ <systemitem role="package">apt-cacher</systemitem>, or
+ <systemitem role="package">approx</systemitem>.
diff -ru release-notes.pristine//en/whats-new.dbk release-notes/en/whats-new.dbk
--- release-notes.pristine//en/whats-new.dbk 2011-02-01 17:35:20.496916343 +0000
+++ release-notes/en/whats-new.dbk 2011-02-01 17:39:11.828925631 +0000
@@ -386,25 +386,15 @@
-The preferred program for interactive package management from a terminal is
-<command>aptitude</command>. For a non-interactive command line interface
-for package management, it is recommended to use <command>apt-get</command>.
-<command>apt-get</command> is also the preferred tool for upgrades
-between major releases.
-If you are still using <command>dselect</command>, you should switch to
+For users familiar with <command>aptitude</command>'s full-screen mode, this
+is the preferred interface for normal package management. However, the
+recommended command line tool for the &oldreleasename; to &releasename;
+upgrade is <command>apt-get</command>. If you are still using
+<command>dselect</command>, you should switch to
<systemitem role="package">aptitude</systemitem> as the official front-end
for package management.
-For &releasename; APT automatically installs recommended packages by default<footnote><para>This change implies that disk requirements for tasks selected through the debian installer have increased too. For more information please
-see the <quote>Disk Space Needed for Tasks</quote> chapter in the
-<ulink url="&url-install-manual;">Installation Guide</ulink>.</para></footnote>.
-This can be changed by adding the following line in
TODO: Do we have to mention dpkg triggers here or elsewhere?