Re: Things to check in release notes
issues.dbk, which has some slightly non-native-English that I've tried
to fix up without affecting the meaning, and some stylistic
inconsistencies ("suid" vs "setuid", "squeeze" vs "Squeeze", varying
kinds of dashes, and "behaviour" in an otherwise en_US file).
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
Index: issues.dbk
===================================================================
--- issues.dbk (revision 9832)
+++ issues.dbk (working copy)
@@ -44,17 +44,17 @@
<acronym>LDAP</acronym> and attempt to change their effective
privileges to fail when connecting to an <acronym>LDAP</acronym>
server using <acronym>TLS</acronym> or <acronym>SSL</acronym>.
- This can cause problems for suid programs on systems using
+ This can cause problems for setuid programs on systems using
<systemitem role="package">libnss-ldap</systemitem> like
<command>sudo</command>, <command>su</command> or
- <command>schroot</command> and for suid programs that perform LDAP
+ <command>schroot</command> and for setuid programs that perform LDAP
searches like <systemitem role ="package">sudo-ldap</systemitem>.
</para>
<para>
It is recommended to replace the
<systemitem role="package">libnss-ldap</systemitem> package with
<systemitem role="package">libnss-ldapd</systemitem>, a newer library
- which uses separate daemon (<command>nslcd</command>) for all
+ which uses a separate daemon (<command>nslcd</command>) for all
<acronym>LDAP</acronym> lookups. The replacement for
<systemitem role="package">libpam-ldap</systemitem> is
<systemitem role="package">libpam-ldapd</systemitem>.
@@ -82,7 +82,7 @@
and partial lack of upstream support in the form of long term branches make it
very difficult to support these browsers with backported security fixes.
Additionally, library interdependencies make it impossible to update to newer
-upstream releases. As such, browsers built upon the webkit, qtwebkit and khtml
+upstream releases. Therefore, browsers built upon the webkit, qtwebkit and khtml
engines are included in &Releasename;, but not covered by security support.
These browsers should not be used against untrusted websites.
</para>
@@ -92,8 +92,8 @@
</para>
<para>
Xulrunner has had a history of good backportability for older releases over
-the previous release cycles. Chromium —while built upon the Webkit
-codebase— is a leaf package, which will be kept up-to-date by rebuilding
+the previous release cycles. Chromium - while built upon the Webkit
+codebase - is a leaf package, which will be kept up-to-date by rebuilding
the current Chromium releases for stable.
</para>
</section>
@@ -108,8 +108,8 @@
<title>GNOME desktop changes and support</title>
<para>
By default, some accessibility tools are not enabled in the GNOME display
- manager (gdm3). In order to enable zooming or a visual keyboard, the
- simplest way is to enable the <quote>shell</quote> greeter.
+ manager (gdm3). The simplest way to enable zooming or a visual keyboard
+ is to activate the <quote>shell</quote> greeter.
</para>
<para>
To do that, edit the <filename>/etc/gdm3/greeter.gsettings</filename> file,
@@ -127,10 +127,10 @@
<para>
<command>NetworkManager</command> can detect if a network
interface is managed by <command>ifupdown</command> in order to avoid
- conflicts, but is not able to do so with other networking management
+ conflicts, but is not able to do so with other network management
programs such as <command>wicd-daemon</command>. Problems and
unexpected behavior can result if two such daemons are managing the
- same interface when attempting to make a networking connection.
+ same interface when attempting to make a network connection.
</para>
<para>
For instance, if <command>wicd-daemon</command> and
@@ -142,9 +142,9 @@
likewise fail with the message:
<screen>NetworkManager is not running. Please start it.</screen>
It is recommended that users of GNOME consider
- installing and trying <command>NetworkManager</command> but, if
- desired, the <command>NetworkManager</command> daemon may be
- permanently disabled using the following command:
+ installing and trying <command>NetworkManager</command>, but
+ the <command>NetworkManager</command> daemon may be
+ permanently disabled if desired using the following command:
<screen># update-rc.d network-manager disable</screen>
After disabling the daemon, it is recommended to examine the contents
of <filename>/etc/resolv.conf</filename>. This file is used to
@@ -164,7 +164,7 @@
<para><command>suidperl</command> was removed upstream with 5.12, so the
<systemitem role="package">perl-suid</systemitem> package which used to be
distributed in Debian has been removed too. Possible alternatives include
-using a simple setuid C wrapper to execute a perl script from a hard-coded
+using a simple setuid C wrapper to execute a Perl script from a hard-coded
location, or using a more general tool like <command>sudo</command>.
</para>
@@ -190,7 +190,7 @@
</para>
<para>
- The same advice applies if you still have <systemitem
+ The same advice applies if you have <systemitem
role="package">request-tracker3.6</systemitem> or older packages from
previous Debian releases still in use; if this is the case it is
recommended to upgrade step by step, following the appropriate
@@ -304,7 +304,7 @@
special compatibility options to provide a <command>pdksh</command> binary
symlink. This compatibility binary behaves more like the traditional
Public Domain Korn Shell than the current <command>mksh</command>. However
- as it contains behaviour-changing bugfixes it is not a pure drop-in
+ as it contains behavior-changing bugfixes it is not a pure drop-in
replacement. So, you're advised to change your
<programlisting>#!/bin/pdksh</programlisting> scripts to
<programlisting>#!/bin/mksh</programlisting> and test them. If the test
@@ -319,10 +319,10 @@
The compatibility binary is not suitable for interactive
use, so as system administrator, adjust the login shell of your Korn Shell
users. For minimal service interruption, do this before the upgrade of
- the O.S: manually install the <systemitem role="package">mksh</systemitem>
+ the O.S.: manually install the <systemitem role="package">mksh</systemitem>
package and change the login and/or interactive shells of users that use
<command>pdksh</command> to <command>mksh</command>. Furthermore, you're
- suggested to copy <filename>/etc/skel/.mkshrc</filename> into their home
+ encouraged to copy <filename>/etc/skel/.mkshrc</filename> into their home
directories: this provides some shell functions like <command>pushd</command>,
<command>popd</command> and <command>dirs</command> and a nice
<programlisting>PS1</programlisting> (shell prompt).
@@ -333,10 +333,10 @@
<section id="puppet">
<title>Puppet 2.6 / 2.7 compatibility</title>
<para>
-When upgrading a Puppet managed system from Squeeze to Wheezy, you
+When upgrading a Puppet managed system from squeeze to wheezy, you
must ensure that the corresponding puppetmaster runs at least Puppet
-version 2.7. If the master is running Squeeze's <systemitem
-role="package">puppetmaster</systemitem>, the managed Wheezy system
+version 2.7. If the master is running squeeze's <systemitem
+role="package">puppetmaster</systemitem>, the managed wheezy system
will not be able to connect to it.
</para>
<para>
Reply to: