Translation status
| 607 | Strings | 51% | Translate |
|---|---|---|---|
| 15,006 | Words | 44% |
Other components
| Component | Translated | Untranslated | Untranslated words | Checks | Suggestions | Comments | |
|---|---|---|---|---|---|---|---|
70_conclusion
GPL-2.0
|
0% | 24 | 723 | ||||
|
|
|||||||
|
15_debian-packaging
GPL-2.0
|
6% | 176 | 6,243 | 5 | |||
|
|
|||||||
|
00a_preface
GPL-2.0
|
33% | 6 | 283 | ||||
|
|
|||||||
|
13_workstation
GPL-2.0
|
55% | 142 | 3,894 | 92 | |||
|
|
|||||||
|
11_network-services
GPL-2.0
|
58% | 388 | 7,337 | 267 | |||
|
|
|||||||
|
Book_Info
GPL-2.0
|
60% | 6 | 118 | ||||
|
|
|||||||
|
90_derivative-distributions
GPL-2.0
|
62% | 28 | 1,162 | 10 | |||
|
|
|||||||
|
05_packaging-system
GPL-2.0
|
67% | 115 | 4,516 | 79 | |||
|
|
|||||||
|
07_solving-problems
GPL-2.0
|
67% | 52 | 1,454 | 40 | |||
|
|
|||||||
|
99_backcover
GPL-2.0
|
75% | 2 | 102 | ||||
|
|
|||||||
Translation Information
| Project website | debian-handbook.info |
|---|---|
| Instructions for translators | https://debian-handbook.info/contribute/ Mailing list for translators: <<debian-handbook-translators@lists.alioth.debian.org> |
| Project maintainers |
 rhertzog
 pere
|
| Translation process |
|
| Translation license | GNU General Public License v2.0 or later |
| Source code repository |
https://salsa.debian.org/hertzog/debian-handbook.git
|
| Repository branch | buster/master |
| Last remote commit |
fr-FR: Translated using Weblate.
109bba20
pere authored 2 weeks ago |
| Weblate repository |
https://hosted.weblate.org/git/debian-handbook/12_advanced-administration/
|
| Filemask | */06_apt.po |
| Translation file |
fa-IR/06_apt.po
|
None
When this option is enabled, the daily script will execute <command>unattended-upgrade</command> (from the <emphasis role="pkg">unattended-upgrades</emphasis> package) which — as its name suggest — can automatize the upgrade process for some packages (by default it only takes care of security updates, but this can be customized in <filename>/etc/apt/apt.conf.d/50unattended-upgrades</filename>). Note that this option can be set with the help of debconf by running <command>dpkg-reconfigure -plow unattended-upgrades</command>. If <emphasis role="pkg">apt-listbugs</emphasis> is installed, it will prevent an automatic upgrade of packages which are affected by an already reported serious or grave bug.
You might sometimes find that the new version of a software doesn't work at all. This generally happens if the application isn't particularly popular and hasn't been tested enough; a last-minute update can also introduce regressions which are only found after the stable release. In both cases, the first thing to do is to have a look at the bug tracking system at <ulink url="https://bugs.debian.org"><literal>https://bugs.debian.org/<replaceable>package</replaceable></literal></ulink>, and check whether the problem has already been reported. If this is case, it will be also listed before the upgrade begins, if you have <emphasis role="pkg">apt-listbugs</emphasis> installed. If it hasn't, you should report it yourself with <command>reportbug</command>. If it is already known, the bug report and the associated messages are usually an excellent source of information related to the bug:
The seal works with a chain of cryptographical hashes and a signature. T and is explained in detail in <citerefentry><refentrytitle>apt-secure</refentrytitle><manvolnum>8</manvolnum></citerefentry>. Starting with Debian 10 <emphasis role="distribution">Buster</emphasis> the signed file is the <filename>InRelease</filename> file, provided by the Debian mirrors. ItThere is also a legacy file called <filename>Release</filename>. Both contains a list of the <filename>Packages</filename> files (including their compressed forms, <filename>Packages.gz</filename> and <filename>Packages.xz</filename>, and the incremental versions), along with their MD5, SHA1 and SHA256 hashes, which ensures that the files haven't been tampered with. These <filename>Packages</filename> files contain a list of the Debian packages available on the mirror, along with their hashes, which ensures in turn that the contents of the packages themselves haven't been altered either. The difference between <filename>InRelease</filename> and <filename>Release</filename> is that the former is cryptographically signed in-line, whereas the latter provides a detached signature in the form of the file <filename>Release.gpg</filename>.
This section does not cover the finer details of using <command>aptitude</command>, i. It rather focuses on giving you a survival kit to use it. <command>aptitude</command> is ratherBut it is well documented and we advise you to use its complete manual available in the <emphasis role="pkg">aptitude-doc-en</emphasis> package (see <filename>/usr/share/doc/aptitude/html/en/index.html</filename>) or at <ulink url="https://www.debian.org/doc/manuals/aptitude/" />.
There are numerous non-official sources of Debian packages set up by advanced users who have recompiled some software (— Ubuntu made this popular with their Personal Package Archive (<acronym>PPA</acronym>) service), — by programmers who make their creation available to all, and even by Debian developers who offer pre-versions of their package online.
The syntax of the last field depends on the structure of the repository. In the simplest cases, you can simply indicate a subdirectory (with a required trailing slash) of the desired source (t. This is often a simple “<filename>./</filename>” which refers to the absence of a subdirectory — t. The packages are then directly at the specified URL). But in the most common case, the repositories will be structured like a Debian mirror, with multiple distributions, each having multiple components. In those cases, name the chosen distribution (by its “codename” — see the list in sidebar <xref linkend="sidebar.bruce-perens" /> — or by the corresponding “suites” —(<literal>oldstable</literal>, <literal>stable</literal>, <literal>testing</literal>, <literal>unstable</literal>), and then the components (or sections) to enable (chosen betweento enable. A typical Debian mirror provides the components <literal>main</literal>, <literal>contrib</literal>, and <literal>non-free</literal> in a typical Debian mirror).
The second field gives the base URL of the source (c. Combined with the filenames presentlisted in the <filename>Packages.gxz</filename> files, it must give a full and valid URL): t. This can consist in a Debian mirror or in any other package archive set up by a third party. The URL can start with <literal>file://</literal> to indicate a local source installed in the system's file hierarchy, with <literal>http://</literal> or <literal>https://</literal> to indicate a source accessible from a web server, or with <literal>ftp://</literal> or <literal>ftps://</literal> for a source available on an FTP server. The URL can also start with <literal>cdrom:</literal> for CD-ROM/DVD-ROM/Blu-ray disc based installations, although this is less frequent, since network-based installation methods are more andeventually more common.
Statistics
| Percent | Strings | Words | Chars | ||
|---|---|---|---|---|---|
| Total | 607 | 15,006 | 132,692 | ||
| Translated | 51% | 313 | 6,659 | 55,714 | |
| Needs editing | 37% | 225 | 6,284 | 58,642 | |
| Failing checks | 29% | 177 | 4,877 | 46,308 |
Last activity
| Last change | July 26, 2016, 8:31 a.m. | |||
|---|---|---|---|---|
| Last author | Ole-Erik Yrvin | |||