[l10n-russian CVS] release-notes Makefile,NONE,1.1 release-notes.en.sgml,1.4,1.5 release-notes.ru.sgml,1.2,1.3
Nikolai Prokoschenko
debian-l10n-russian@lists.debian.org
Tue, 24 May 2005 23:04:29 +0000
Update of /cvsroot/l10n-russian/release-notes
In directory haydn:/tmp/cvs-serv23969
Modified Files:
release-notes.en.sgml release-notes.ru.sgml
Added Files:
Makefile
Log Message:
* Update sgml files
* Include a Makefile for easy updates (no automatical updates yet). This Makefile was
written by Denis Barbier for the French team
Index: release-notes.ru.sgml
===================================================================
RCS file: /cvsroot/l10n-russian/release-notes/release-notes.ru.sgml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- release-notes.ru.sgml 24 May 2005 09:59:38 -0000 1.2
+++ release-notes.ru.sgml 24 May 2005 23:04:27 -0000 1.3
@@ -120,13 +120,6 @@
they will be marked as 'obsolete' in package management
front-ends.</p>
- <p>На смену устаревающему, хотя и до
- сих пор популярному <package>dselect</package>
- было разработано несколько более
- удачных интерфейсов к apt. Рекомендуем
- обратить внимание на пакеты
- <package>aptitude</package> и <package>synaptic</package>.</p>
-
<p>Этот выпуск &debian; содержит
значительно улучшенную версию XFree86
4.3, включающую поддержку широкого
@@ -143,6 +136,14 @@
are the Evolution groupware software and GAIM instant messaging
client.</p>
+ <p>The &releasename; version of <prgn>aptitude</prgn> is the
+ preferred program for package management from console. It has proven
+ to be better at dependency resolution than <prgn>apt-get</prgn>.
+ <prgn>aptitude</prgn> supports most command line operations of
+ <prgn>apt-get</prgn>. If you are still using <prgn>dselect</prgn>,
+ you should also give <package>aptitude</package> a try as frontend
+ for package management.</p>
+
<p>The official &debian; distribution now ships on thirteen to
fifteen binary CDs (depending on the architecture) and a similar
number of source CDs. A DVD version of the distribution is now also
@@ -312,8 +313,27 @@
параметром "debian-installer/framebuffer=true".</p>
</sect>
-]]></chapt>
+]]>
+ <sect id="popcon"><heading>Popularity contest</heading>
+
+ <p>For technical reasons the <package>popcon</package> is no longer
+ installed by default for new &releasename; installations. This will
+ probably be corrected in future releases.</p>
+
+ <p><package>popcon</package> provides the Debian project with valuable
+ information on which packages in the distribution are actually used.
+ This information is used mainly to decide the order in which packages
+ are included on installation CD-ROMs, but is also often consulted by
+ Debian developers in deciding whether or not to adopt a package that no
+ longer has a maintainer.</p>
+
+ <p>Information from <package>popcon</package> is processed anonymously.
+ We would appreciate it if you install the package and allow it to
+ participate in the official survey; you will thereby help improve
+ Debian.</p>
+</sect></chapt>
+
@@ -839,7 +859,7 @@
время обновления, вы сможете найти в
файле транскрипта.</p>
</sect1>
- <sect1 id="nownownow"><heading>Things to do before rebooting</heading>
+ <sect1 id="nownownow"><heading>Перед перезагрузкой</heading>
<p>Когда команда <tt>aptitude dist-upgrade</tt>
закончила работу, <em>формально</em>
@@ -887,25 +907,115 @@
this new kernel is installed you should reboot at the next available
opportunity to get the benefit.</p>
- <p>Please note that the installation system of &oldreleasename; (and
- previous releases) did <em>not</em> install the kernel as a package in
- your system. This has changed in &releasename; and you can install
- virtual packages to keep track of kernel changes. These packages are
- named kernel-image-<tt>VERSION</tt>-<tt>ARCH</tt>, with
- <tt>VERSION</tt> corresponding to the kernel version number (2.4 or
- 2.6) and <tt>ARCH</tt> corresponding to any of the supported
- architectures. If you want to have security support for the kernel
- integrated in package management please install the kernel package
- most suitable for your hardware after the upgrade.</p>
+ <p>Следует заметить, что сиcтема
+ установки &oldreleasename; и более старых
+ выпусков <em>не устанавливала</em> ядро в
+ качестве пакета в вашу систему. В
+ &releasename; ситуация изменилась, теперь вы
+ можете устанавливать псевдопакеты
+ чтобы отслеживать смену ядер. Эти
+ пакеты будут иметь имена вида
+ kernel-image-<tt>ВЕРСИЯ</tt>-<tt>АРХИТЕКТУРА</tt>,
+ где <tt>ВЕРСИЯ</tt> - номер версии ядра (2.4
+ или 2.6), а <tt>АРХИТЕКТУРА</tt> - любая из
+ поддерживаемых архитектур.</p>
- <p>Более рисковые пользователи могут
- скомпилировать собственное ядро.
- Установите пакет <package>kernel-package</package> и
- прочитайте документацию в каталоге
+ <p>Если вы не боитесь трудностей, то
+ можете скомпилировать собственное
+ ядро из исходного кода. Установите
+ пакет <package>kernel-package</package> и прочитайте
+ документацию в каталоге
<file>/usr/share/doc/kernel-package</file>.</p>
-</sect2></sect1></sect></chapt>
+</sect2></sect1></sect>
+
+
+ <sect id="obsolete"><heading>Obsolete packages</heading>
+
+<!-- JFS: Providing a full listing might be useful, especially if we can
+point to the Bug that was opened when the bug was removed. This list should
+be moved to an appendix, instead of adding it inline as we did in the
+potato to woody RN -->
+
+ <p>Introducing several thousand new packages, &releasename; also
+ retires and omits more than two thousand old packages that were in
+ &oldreleasename;. It provides no upgrade path for these obsolete
+ packages. While nothing prevents you from continuing to use an
+ obsolete package where desired, the Debian project will usually
+ discontinue security support for it a year after &releasename;'s
+ release<footnote><p>Or for as long as there is not another release in
+ that time frame. Typically only two stable releases are supported at
+ any given time.</p></footnote>, and will not normally provide other
+ support in the meantime. Replacing them with available alternatives,
+ if any, is recommended.</p>
+
+ <p>There are many reasons why packages might have been removed from
+ the distribution: they are no longer maintained upstream, there is no
+ longer a Debian Developer interested in maintaining the packages; the
+ functionality they provide has been superseded by different software
+ (or a new version); or they are no longer considered suitable for
+ &releasename; due to bugs in them. In the later case, packages might
+ still be present in the "unstable" distribution.</p>
+
+ <p>Detecting which packages in an updated system are "obsolete" is
+ easy since the package management front-ends will mark them as such.
+ If you are using <prgn>aptitude</prgn>, you will see a listing of
+ these packages in the "Obsolete and Locally Created Packages" entry.
+ <prgn>dselect</prgn> provides a similar section but the listing it
+ presents might differ. Also, if you have used <prgn>aptitude</prgn> 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. Also,
+ <prgn>aptitude</prgn>, unlike <prgn>deborphan</prgn> will not mark as
+ obsolete packages that you manually installed, as opposed to those
+ that were automaticaly installed through dependancies.</p>
+
+ <p>There are additional tools you can use to find obsolete packages
+ such as <prgn>deborphan</prgn>, <prgn>debfoster</prgn> or
+ <prgn>cruft</prgn>. <prgn>deborphan</prgn> is highly recommended,
+ although it will (in default mode) only report obsolete libraries:
+ packages in the "libs" or "oldlibs" 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.</p>
+
+<!-- JFS: Should we recommend purging old packages? This might be
+dangerous since the maintainer scripts might try to remove stuff that
+didn't belong to them... -->
+
+ <p>The <url id="&url-bts;" name="Debian Bug Tracking System"> often
+ provides additional information on why the package was removed. You
+ should review both the archived bug reports for the package itself and
+ the archived bug reports for the <url
+ id="&url-bts;/cgi-bin/pkgreport.cgi?pkg=ftp.debian.org&archive=yes"
+ name="ftp.debian.org pseudo-package">.</p>
+
+ <sect1 id="dummy"><heading>Dummy packages</heading>
+
+<!-- JFS: If the appendix is kept this section should point there and the packages described here should be moved to that section -->
+
+ <p>Some packages from &oldreleasename; have been split into several
+ packages in &releasename;, often to improve system maintainability. To
+ ease the upgrade path in such cases, &releasename; often provides
+ "dummy" packages: empty packages that have the same name as the old
+ package in &oldreleasename; with dependencies that cause the new
+ packages to be installed. These "dummy" packages are considered
+ obsolete packages after the upgrade and can be safely removed.</p>
+
+ <p>Most (but not all) dummy packages' descriptions indicate their
+ purpose. Package descriptions for dummy packages are not uniform,
+ however, so you might also find <prgn>deborphan</prgn> with the
+ <tt>--guess</tt> options useful to detect them in your system. Note
+ that some dummy packages are not intended to be removed after an
+ upgrade but are, instead, used to keep track of the current available
+ version of a program over time.</p>
+</sect1></sect></chapt>
+
+
<!-- FJP: Add more info here on dealing with obsolete packages?
@@ -913,7 +1023,7 @@
(use "limit" command in aptitude and search for ~c) -->
<chapt id="information">
- <heading>Issues to be aware of for &releasename;</heading>
+ <heading>Что надо знать о &releasename;</heading>
<!-- Controversial, disabled for now, please translate though
<sect id="german-quotes"><heading>Problems with German Quotes</heading>
@@ -943,14 +1053,16 @@
-->
-<sect id="pythonchanges"><heading>Changes to Python packages</heading>
- <p>None of the python2.X packages that are included with &releasename;
- include the standard modules 'profile' and 'pstats', because they are
- licensed under a license that does not conform to the DFSG (see bug #293932
- for details). These two modules can be found in the python-profiler and
- python2.X-profiler packages that are included in the non-free section of the
- Debian archive.</p>
+<sect id="pythonchanges"><heading>Изменения в пакетах Python</heading>
+
+ <p>Ни один пакет python2.X из поставки &releasename;
+ не содержит стандартных модулей "profile" и
+ "pstats", так как их лицензия не соответсвует
+ DFSG (ошибка #293932 содержит более подробное
+ описание). Эти модули можно получить,
+ установив пакеты python-profiler и python2.X-profiler из
+ секции non-free архива Debian.</p>
</sect>
<![ %available-2.6 [
@@ -960,40 +1072,67 @@
<p>The 2.6 kernel series contains major changes from the 2.4 series.
Modules have been renamed and a lot of drivers have been partially or
sometimes almost completely rewritten. Upgrading to a 2.6 kernel from
- an earlier version is therefore not a process to be taken lightly.
- This section aims to make you aware of some of the issues you may
- face.</p>
+ an earlier version is therefore not a process to be undertaken
+ lightly. This section aims to make you aware of some of the issues
+ you may face.</p>
- <p>You are therefore strongly advised not to upgrade to a 2.6 kernel
- as part of the upgrade from &oldreleasename; to &releasename;.
- Instead, you should first make sure your system works correctly with
- either the old kernel or with a 2.4 kernel from &releasename; and do
- the upgrade to a 2.6 kernel later as a separate project.</p>
+ <p>Для начала, мы настоятельно не
+ рекомендуем вам менять ядро
+ одновременно с обновлением всей
+ системы &oldreleasename; на &releasename;. Сначала
+ убедитесь, что система нормально
+ работает с вашим старым ядром (или с
+ ядром 2.4 из &releasename;), а затем отдельно
+ обновить ядро до 2.6.</p>
- <p>If you compile your own kernel from source, make sure you install
- <package>module-init-tools</package> before you reboot with the 2.6
- kernel. This package replaces <package>modutils</package> for 2.6
- kernels. If you install one of the Debian
- <package>kernel-image</package> packages, this package will be
- installed automatically because of dependencies.</p>
+ <p>Если вы планируете скомпилировать
+ собственное ядро, то перед загрузкой
+ ядра 2.6 убедитесь, что вы установили
+ пакет <package>module-init-tools</package>. Этот пакет
+ выполняет функции <package>modutils</package> для
+ ядер серии 2.6. При установке любого из
+ пакетов <package>kernel-image</package>
+ <package>module-init-tools</package> будет установлен
+ автоматически, так как
+ <package>kernel-image</package> от него зависят.</p>
- <p>If you use <em>LVM</em>, you should also install
- <package>lvm2</package> before you reboot as the 2.6 kernel does not
- directly support LVM1. To access LVM1 volumes, the compatibility
- layer of <package>lvm2</package> (the dm-mod module) is used. You can
- leave <package>lvm10</package> installed; the init scripts will
- detect which kernel is used and execute the appropriate version.</p>
+ <p>Если вы используете <em>LVM</em>, то до
+ перезагрузки вам также надо будет
+ установить пакет <package>lvm2</package>, так
+ как ялро 2.6 само по себе не
+ поддерживает LVM1. Для доступа к
+ разделам LVM1 применяется модуль
+ совместимости dm-mod пакета
+ <package>lvm2</package>. Пакет <package>lvm10</package>
+ можно не удалять, сценарии первичной
+ загрузки определят версию
+ используемого ядра и загрузят
+ подходящую версию пакета LVM.</p>
+
+ <p>If you have entries in the <file>/etc/modules</file> file (the
+ list of modules to be loaded during system boot), be aware that some
+ module names may have changed. If this happens you will have to
+ update this file with the new module names.</p>
<![ %i386 [
<p>For some SATA disk controllers, the device assigned to a drive and
its partitions may change from <file>/dev/hdX</file> to
<file>/dev/sdX</file>. If this happens, you will have to modify your
- <file>/etc/fstab</file> and bootloader configuration accordingly.</p>
+ <file>/etc/fstab</file> and bootloader configuration accordingly.
+ Unless these changes are made correctly, your system may not boot
+ correctly.</p>
]]>
+ <p>Once you have installed your 2.6 kernel, but before you reboot,
+ make sure you have a recovery method. First, make sure that the
+ bootloader configuration has entries for both the new kernel and the
+ old, working 2.4 kernel. You should also ensure you have a "rescue"
+ floppy or cdrom to hand, in case misconfiguration of the bootloader
+ prevents you booting the old kernel.</p>
+
<![ %not-s390 [
<sect1 id="2.6-keyboard">
- <heading>Keyboard configuration</heading>
+ <heading>Настройка клавиатуры</heading>
<p>The most invasive change in the 2.6 kernels is a fundamental
change of the input layer. This change makes all keyboards look like
@@ -1032,7 +1171,7 @@
reconfigure the X Window System and <package>gpm</package> if your
mouse is not working after upgrading to a 2.6 kernel. The most likely
cause is that the device which gets the data from the mouse has
- changed.</p>
+ changed. You may also need to load different modules.</p>
<![ %sparc [
<p>If you currently have X configured for <file>/dev/sunmouse</file>,
@@ -1040,6 +1179,20 @@
]]></sect1>
+
+ <sect1 id="2.6-sound">
+ <heading>Sound configuration</heading>
+
+ <p>For the 2.6 kernel series the ALSA sound drivers are preferred
+ over the OSS sound drivers. If you install
+ <package>alsa-base</package>, ALSA modules for your soundcard should
+ be loaded automatically; this will also automatically blacklist OSS
+ modules for <package>discover</package> and
+ <package>hotplug</package> to prevent them from loading. If you have
+ OSS modules listed in <file>/etc/modules</file>, you should remove
+ them.</p>
+</sect1>
+
]]> <!-- %not-s390 -->
<sect1 id="2.6-udev">
@@ -1072,7 +1225,20 @@
<![ %i386 [
- <sect id="x_and_transmeta">
+ <sect id="x-mouse">
+ <heading>X Windows Systems fails to load</heading>
+
+ <p>If after booting your machine, X Windows fails to load and you see
+ an error "missing core pointer" in
+ <file>/var/log/XFree86.0.log</file>, the problem could be that the
+ mouse driver is not loaded fast enough by <prgn>hotplug</prgn> (bug
+ <url id="http://bugs.debian.org/255744" name="#255744">). The
+ solution is to add the driver module for your mouse (e.g. psmouse) in
+ <file>/etc/modules</file>.</p>
+</sect>
+
+
+ <sect id="x-transmeta">
<heading>X Window System on Transmeta Crusoe systems</heading>
<p>The X server shipping in &releasename; contains optimized code
Index: release-notes.en.sgml
===================================================================
RCS file: /cvsroot/l10n-russian/release-notes/release-notes.en.sgml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- NEW FILE: Makefile ---
DOC = release-notes
lang = ru
POT = $(DOC).pot
PO = $(DOC).$(lang).po
SGML_ORIG = $(DOC).en.sgml
SGML_L10N = $(DOC).$(lang).sgml
update:
wget -O $(SGML_ORIG) "http://cvs.debian.org/*checkout*/ddp/manuals.sgml/release-notes/en/release-notes.en.sgml?cvsroot=debian-doc"
debiandoc2pot $(SGML_ORIG) > $(POT)
msgmerge -U $(PO) $(POT)
po2debiandoc $(SGML_ORIG) $(PO) > $(SGML_L10N)
update-po:
debiandoc2pot $(SGML_ORIG) > $(POT)
msgmerge -U $(PO) $(POT)
stats:
msgfmt -v -o /dev/null $(PO)
$(POT): $(SGML_ORIG)
debiandoc2pot $? > $@
$(SGML_L10N): $(SGML_ORIG) $(PO)
po2debiandoc $(SGML_ORIG) $(PO) > $@
.PHONY: update update-po stats