[l10n-russian CVS] release-notes/sgml release-notes.en.sgml, 1.9,
1.10
Yuri Kozlov
yuray-guest at alioth.debian.org
Tue Mar 27 19:14:10 CET 2007
Update of /cvsroot/l10n-russian/release-notes/sgml
In directory alioth:/tmp/cvs-serv1082/sgml
Modified Files:
release-notes.en.sgml
Log Message:
Index: release-notes.en.sgml
===================================================================
RCS file: /cvsroot/l10n-russian/release-notes/sgml/release-notes.en.sgml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -d -r1.9 -r1.10
--- release-notes.en.sgml 26 Mar 2007 17:47:19 -0000 1.9
+++ release-notes.en.sgml 27 Mar 2007 18:14:08 -0000 1.10
@@ -24,25 +24,79 @@
<chapt id="about"><heading>Introduction</heading>
<p>The primary goals of these Release Notes are to inform users
- of major changes in this release of the Debian distribution, to
+ of major changes in this release of the &debian; distribution, to
provide information on how to upgrade safely from the previous
- to the this release and finally to inform users of known potential
+ release to the current release and finally to inform users of known potential
issues users could encounter when upgrading to or using the
- release.</p>
+ &releasename; release.</p>
<p>Note that it is impossible to list every known issue and that
therefore a selection has been made based on a combination of the
expected prevalence and impact of issues.</p>
- <p>The most recent version of this document is always available at
- <url id="&url-release-notes;">. If your version is more than a month
- old, you might wish to download the latest version.</p>
+ <p>The most recent version of this document is always available at <url
+ id="&url-release-notes;">. If the version you are reading is more than a
+ month old<footnote>On front page's of the PDF version and in the footer
+ of the online, HTML, version</footnote>, you might wish to obtain the
+ latest version.</p>
<p>Please note that we only support
and document upgrading from the previous release of Debian (in this case,
the upgrade from &oldreleasename;). If you need to upgrade from older
- releases, we suggest you read previous editions of the release notes.</p>
+ releases, we suggest you read previous editions of the release notes and
+ upgrade to &oldreleasename; first.</p>
+
+ <sect id="bug_reports"><heading>Reporting bugs on this document</heading>
+
+ <p>We have attempted to test all the different upgrade steps
+ described in this document and we have also tried to anticipate all
+ the possible issues our users might encounter.</p>
+
+ <p>Nevertheless, If you think you have found any bug in this
+ documentation (incorrect information or information that is missing),
+ please file a bug in the <url id="&url-bts;" name="bug tracking
+ system"> against the <package>release-notes</package> package.</p>
+
+ </sect>
+
+ <sect id="upgrade_reports"><heading>Contributing upgrade reports</heading>
+ <p>We welcome any information from users related to upgrades from
+ &oldreleasename; to &releasename;. If you are willing to share information
+ please file a bug in the <url id="&url-bts;" name="bug tracking system">
+ against the <package>upgrade-reports</package> package with your results.</p>
+ <p>Please provide the following information when submitting your upgrade report:
+
+ <list>
+
+<!-- TODO: any more things to add here? -->
+ <item><p>Session logs using <package>script</package>, as described in
+ <ref id="record_session">.</p></item>
+
+ <item><p>The status of your package database before and after the
+ upgrade, using the backup procedure described at <ref
+ id="backup">.
+
+ <item><p>Your aptitude logs, available at <file>/var/log/aptitude</file>.</p></item>
+
+ </list></p>
+
+ <p>Note: you should take some time to review and remove any sensitive and/or confidential
+ information from the logs before including them in a bug report as the information
+ will be published in a public database.
+
+ </sect>
+
+ <sect id="sources"><heading>Sources for this document</heading>
+ <p>This document uses <package>debiandocsgml</package>. Its sources
+ are available in the <em>Debian Documentation Project</em>'s CVS.
+ You can use the <url id="&url-cvs-release-notes;" name="web
+ interface"> to access its files individually through the web and see
+ their changes. For more information on how to access the CVS please
+ consult the <url id="&url-ddp-cvs-info;" name="Debian Documentation Project CVS pages">.
+ </p>
+
+ </sect>
<!--
<sect id="changes"><heading>Changes in the Release Notes</heading>
@@ -116,16 +170,20 @@
<sect id="newdistro"><heading>What's new in the distribution?</heading>
+<!-- TODO (jfs): numbers could be entities so that updating them was easier, like
+ in the FAQ -->
<!-- TODO: Numbers need to be reviewed, these values have been obtained
using the changes-release script -->
<p>This new release of Debian again comes with a lot more software
than its predecessor &oldreleasename;; the distribution includes
- over 6200 new packages. Most of the software in the distribution
- has been updated: over 10500 software packages (this is 67% of
- all packages in &oldreleasename;). Also, a significant number
- of packages (over 3400, 22% of the packages in &oldreleasename;) have for various reasons been removed from the distribution.
- You will not see any updates for these packages and they will be
- marked as 'obsolete' in package management front-ends.</p>
+ over 6,200 new packages, for a total of over 18,000 packages. Most
+ of the software in the distribution has been updated: over 10,500
+ software packages (this is 67% of all packages in &oldreleasename;).
+ Also, a significant number of packages (over 3400, 22% of the
+ packages in &oldreleasename;) have for various reasons been removed
+ from the distribution. You will not see any updates for these
+ packages and they will be marked as 'obsolete' in package management
+ front-ends.</p>
<p>With this release &debian; switches from XFree86 to the 7.1
release of X.Org, which includes support for a greater range of
@@ -350,6 +408,15 @@
will have to reconfigure the mail system after
installation.</p></item>
+ <tag>Desktop selection</tag>
+ <item><p>The installation system will install
+ a GNOME desktop as the default desktop if the user asks for one.
+ However, users wishing to install alternate desktop environments
+ can easily do so by adding boot parameters:
+ <tt>tasks="standard, kde-desktop"</tt> for KDE and
+ <tt>tasks="standard, xfce-desktop"</tt> for Xfce. ISO images for
+ alternate desktop environments will also be available.</p></item>
+
<![ %not-s390 [
<tag>New languages</tag>
<item><p>Thanks to the huge efforts of translators, Debian can
@@ -383,6 +450,17 @@
language selected, or will provide a limited selection
if it cannot. Users can still introduce obscure
combinations if need be.</p></item>
+
+ <tag>Improved system-wide localization</tag>
+ <item><p>Most of the internationalization and localization tasks that
+ were previously handled by the <package>localization-config</package> tool are now
+ included in the stock &debian; installer or in packages themselves. This
+ means that selection of a language will automatically install packages
+ necessar for that language (dictionaries, documentation, fonts...) both
+ in standard and desktop enviroments. Configuration that is no longer
+ handled automatically include the papersize configuration and some
+ advanced keyboard settings on Xorg for some languages.</p></item>
+
]]> <!-- not-s390 -->
</taglist></p>
@@ -411,7 +489,6 @@
</chapt>
-<!-- TODO: Mention default usage of UTF-8 for new installs -->
<chapt id="installing"><heading>New installations</heading>
<p>The Debian Installer is the official installation system for Debian.
@@ -429,7 +506,7 @@
</example></p>
<p>You may also want to check the <url id="&url-installer;index#errata"
- name="errata"> for debian-installer.</p>
+ name="errata"> for debian-installer for a list of knonw issues.</p>
<![ %alpha [
<!-- TODO: Still true? -->
@@ -459,40 +536,66 @@
<sect id="improves_in_etch"><heading>System improvements</heading>
- <p>TODO: Document improvements which users installing etch will see but
- not those upgrading from sarge. For more information see <url
- id="http://wiki.debian.org/Sarge2EtchUpgrade" name="the wiki
- pages">.</p>
+ <p>Users installing &releasename; will benefit from some improvements
+ in the &debian; operating system. Most of these improvements
+ will be carried over to upgrades from &oldreleasename; but there
+ are some changes that will only affect new installs:
+ </p>
<p><list>
- <item>inetd: new default is OpenBSD's</item>
+<!-- Bug 301138, fixed in etch -->
+ <item>Development packages are now of <em>Optional</em> priority.
+ This includes the standard C/C++-compiler, <package>gcc</package>, as well
+ as some other software (<package>dpkg-dev</package>,
+ <package>flex</package>, or <package>make</package>) and development
+ headers (<package>libc6-dev</package>,
+ <package>linux-kernel-headers</package>).
+<!-- TODO: Point to the bug report for the full list of packages in case
+ users want to remove them ? -->
+ This reduces the disk space needed for a standard installation.
+ </item>
- <item>vi: the variant installed by default is a compact version of
- <prgn/vim/ (<package/vim-tiny/) instead of <package/nvi/
+<!-- TODO: Recommend users to remove unused desktop environments ? -->
+ <item>There are three different tasks for Desktop environments users can
+ choose from: GNOME, KDE or Xfce. An installation of the Desktop task in
+ &oldreleasename; would install both GNOME or KDE.</item>
- <item>mail server setup for local delivery per default (sarge users retain their config)</item>
+ <item>The default inet superdaemon is <package>openbsd-inetd</package>
+ instead of <package>netkit-inetd</package>. It will not be started if no
+ services are configured, which is the default.</item>
- <item>development packages now priority optional, will not get installed (#301138), sarge users need to manually remove gcc, binutils et al</item>
+ <item>The variant installed for <prgn/vi/ by default is a compact version of
+ <prgn/vim/ (<package/vim-tiny/) instead of <package/nvi/.
- <item>new standard task in tasksel installs all packages of priority
- standard and higher</item>
+ <item>The &releasename; installer sets up ext2 and ext3 filesystems so
+ that they have "directory indexes", a feature which speeds operations on
+ directories with many files. It does this by turning on the
+ <em/dir_index/ and <em/filetype/ flags when the filesystem is created.
+ Users upgrading from &oldreleasename; need to set this flags manually
+ with <prgn/tune2fs/.</item>
- <item>filesystem improvements, see wiki</item>
+<!-- TODO: Add for lenny, link to utf8-migration-tool, which is right now not
+ available for etch -->
+ <item>The &debian; installer will setup all localized environments using
+ UTF-8 as the default encoding instead of language-specific encoding.
+ Users upgrading to &releasename; will have to switch to this encoding
+ by configuring their environment and locale definitions.</item>
- <item>packages pulled in for laptops</item>
</list></p>
- <sect id="regressions_in_etch"><heading>Regressions</heading>
-
- <p>TODO: Things that are worst in etch than in sarge
-
- <list>
- <item>localization-config NOT installed by d-i, actually not available in etch (#402566). Some i18n/l10n steps need to be done manually (such as installing some packages based on locale).</item>
-
- </list></p>
+<!-- TODO: make it conditional based on arquitecture ? -->
+ <p>Additional packages are pulled in based on the system being installed on or on the user
+ configuration. Users running the installer in a laptop system will
+ automatically get a set of packages specific for laptops, and so will
+ users configuring a localized environment. Even though these packages are
+ not pulled in when upgrading from &oldreleasename; to &releasename; they
+ are still available for users through <em>tasks</em>. Users wishing to
+ install these tasks just need to run <prgn/aptitude/ interactively and select the
+ appropiate tasks from the <em>Tasks</em> item presented in the user interface.</p>
- </sect>
+ <p>For more information please see the <url id="http://wiki.debian.org/Sarge2EtchUpgrade"
+ name="wiki pages"> that describe the upgrade from &oldreleasename; to &releasename;.</p>
<sect id="popcon"><heading>Popularity contest</heading>
@@ -513,8 +616,6 @@
</sect>
-<!-- TODO: Mention localization config? -->
-
</chapt>
@@ -566,16 +667,33 @@
planning, although users accessing your system via an <prgn/ssh/
connection should notice little during the upgrade, and should be
able to continue working. If you wish to take extra precautions, back up or
- unmount users' partitions (<file>/home</file>) before upgrading. A
- reboot will not normally be necessary, unless you also plan to
- upgrade your kernel.</p>
+ unmount users' partitions (<file>/home</file>) before upgrading.</p>
+<!-- JFS: Not true in etch
+ <p>A reboot will not normally be necessary, unless you also plan to
+ upgrade your kernel.</p>
+-->
+ <p>You will probably have to do a kernel upgrade when upgrading to
+ &releasename;, so a reboot will normally be necessary. Typically, this
+ will be done after the upgrade is finished.</p>
+
<!-- TODO: Is not necessary to change the kernel? e.g. udev ? -->
<p>Distribution upgrade should be done either locally from a
textmode virtual console (or a directly connected serial
terminal), or remotely via an <prgn/ssh/ link.</p>
+<!-- JFS: probably can be removed for lenny -->
+ <p>If you are upgrading remotely via an <prgn/ssh/ link it is highly
+ recommended that you take the necessary precautions to be able to
+ access the server through a remote serial terminal. There are chances
+ that, after upgrading the kernel and rebooting, some devices will
+ be renamed (as described in <ref id="device-reorder">) and you will
+ have to fix the system configuration through a local console. Also,
+ if the system is rebooted accidentally in the middle of an upgrade
+ there are chances you will need to recover using a local console.</p>
+<!-- END - remove for lenny -->
+
<p><strong/Important!/ You should <em/not/ upgrade using <prgn/telnet/,
<prgn/rlogin/, <prgn/rsh/, or from an X session managed by <prgn/xdm/,
<prgn/gdm/ or <prgn/kdm/ etc on the machine you are upgrading. That is
@@ -777,6 +895,32 @@
</sect1>
</sect>
+
+<!-- JFS: This section should be probably removed for lenny -->
+ <sect id="handle-conflict"><heading>Manually unmarking packages</heading>
+
+ <p>To prevent <prgn/aptitude/ from removing some packages that were pulled
+ in through dependencies, you need to manually unmark them as <em/auto/
+ packages. This includes OpenOffice and Vim for desktop installs:
+<!-- This is a no-op if none of them are installed -->
+<example>
+# aptitude unmarkauto openoffice.org vim
+</example></p>
+
+<!-- JFS: This cannot be in the same line as above since it produces an ugly output if
+ you just have 2.4 kernels installed -->
+ <p>And 2.6 kernel images if you have installed them using a kernel metapackage:
+
+<example>
+# aptitude unmarkauto $(dpkg-query -W 'kernel-image-2.6*' | cut -f1)
+</example></p>
+
+ <p>Note: You can review which packages are marked as <em/auto/ in aptitude running:
+
+<example>
+# aptitude search 'i~M <package name>'
+</example></p>
+ </sect>
<sect id="upgrade-process"><heading>Preparing sources for APT</heading>
@@ -946,6 +1090,8 @@
lines for a CD-ROM will often refer to "<tt/unstable/";
although this may be confusing, you should <em/not/ change it.</p>
+ <sect1 id="record_session"><heading>Recording the session</heading>
+
<p>It is strongly recommended that you use the
<prgn>/usr/bin/script</prgn> program to record a transcript of the
upgrade session. Then if a problem occurs, you will have a log of
@@ -980,26 +1126,63 @@
</example>
</p>
+ </sect1>
<sect1 id="updating_lists"><heading>Updating the package list</heading>
<p>First the list of available packages for the new release needs to
- be fetched. This is done by executing<footnote>We use <prgn/apt-get/
- for this because the &oldreleasename; version <prgn/aptitude/ may fail
- when new sources have been added to <file/sources.list/.</footnote>:</p>
+ be fetched. This is done by executing:</p>
<p><example>
-# apt-get update
+# aptitude update
</example></p>
+<!-- JFS: Hopefully this will be fixed in lenny -->
+ <p>Running this the first time new sources are updated will print out
+ some warnings related to the availability of the sources. These
+ warnings are harmless and will not appear if you rerun the command again.
+ </p>
+
</sect1>
+ <sect1 id="minimal_upgrade"><heading>Minimal system upgrade</heading>
+
+ <p>TBD</p>
+
+ <p>Server system with no X, do a minimal upgrade with:
+
+ <example>
+# aptitude install initrd-tools
+ </example></p>
+
+ <p>Server system with some X, (xfree86-common) do a minimal upgrade with:
+
+ <example>
+# aptitude install initrd-tools x11-common
+ </example></p>
+
+ <p>Desktop system, use this instead:
+
+ <example>
+# aptitude install initrd-tools libfam0 xlibmesa-glu
+ </example></p>
+
+ <p>Note: Once this minimal upgrade has been done might want to consider
+ upgrading the kernel before upgrading the full system.
+ (either in 2.4 or 2.6). This reduces the window of exposure of not having
+ a bootable systems. If using lilo, it could be upgraded (and run) afterwards
+ for similar reasons. However, installing coreutils + udev might force
+ the removal of large parts of the system if in a desktop.</p>
+
+ </sect1>
<!-- FJP: This next section can probably be dropped for etch -->
<!-- JFS: Actually, this caused issues if done, as documented in 396331, such as
removing the current *running* kernel does this still apply with the
latest aptitude 0.4.4-1 -->
<sect1 id="upgrading_aptitude"><heading>Upgrading aptitude</heading>
+
+ <p>TODO: This is no longer true and will be removed. TESTS pending.
<p>Upgrade tests have shown that &releasename;'s version of
<prgn/aptitude/ is better at solving the complex dependencies during
@@ -1028,6 +1211,7 @@
<sect1 id="upgrading_other"><heading>Upgrading the rest of the system</heading>
+<!-- FIXME: we have not tested with the with-recommends option -->
<p>You are now ready to continue with the main part of the
upgrade. Execute:</p>
<p><example>
@@ -1250,7 +1434,7 @@
</sect1>
]]>
- <sect1><heading>Device enumeration reordering</heading>
+ <sect1 id="device-reorder"><heading>Device enumeration reordering</heading>
<p>&releasename; features a more robust mechanism for hardware discovery
than previous releases. However, this may cause changes in the
order devices are discovered on your system affecting the order
@@ -1912,8 +2096,11 @@
<file>/usr/share/doc/php5</file>).</p>
</sect>
+<!-- JFS: Bug #400311 -->
<sect id="mozilla-security"> <heading>Security status of Mozilla products</heading>
- <p>The Mozilla programs are important tools for many users.
+ <p>The Mozilla programs <package>firefox</package> and <package>thunderbird</package>
+ (rebranded in Debian to <package>iceweasel</package> and <package>icedove</package>, respectively),
+ are important tools for many users.
Unfortunately the upstream security policy is to urge users to update to
new upstream versions, which conflicts with Debian's policy not to ship
large functional changes in security updates.
More information about the l10n-russian-cvs-commits
mailing list