diff options
| author | Hideki Yamane <henrich@debian.org> | 2018-08-02 11:58:17 +0800 |
|---|---|---|
| committer | Sean Whitton <spwhitton@spwhitton.name> | 2018-08-03 15:17:31 +0800 |
| commit | 6ea335c7eed462055b01a14921fc358ebca809d1 (patch) | |
| tree | 7af8f6aebebb7d9a6f3a23a3cac2e5af8faff6d0 /locales | |
| parent | 686dbb933c9fcd4972c8a0cbe09be4580e043bc6 (diff) | |
Just updated po files...
Diffstat (limited to 'locales')
24 files changed, 17021 insertions, 0 deletions
diff --git a/locales/ja/LC_MESSAGES/ap-flowcharts.po b/locales/ja/LC_MESSAGES/ap-flowcharts.po new file mode 100644 index 0000000..00ce5d8 --- /dev/null +++ b/locales/ja/LC_MESSAGES/ap-flowcharts.po @@ -0,0 +1,73 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1996, 1997, 1998 Ian Jackson, Christian Schwarz, 1998-2017, +# The Debian Policy Mailing List +# This file is distributed under the same license as the Debian Policy +# Manual package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2018. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Debian Policy Manual 4.1.6.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-08-02 11:56+0800\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language-Team: LANGUAGE <LL@li.org>\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.4.0\n" + +#: ../../ap-flowcharts.rst:2 +msgid "Maintainer script flowcharts" +msgstr "" + +#: ../../ap-flowcharts.rst:4 +msgid "" +"The flowcharts [#]_ included in this appendix use the following " +"conventions:" +msgstr "" + +#: ../../ap-flowcharts.rst:7 +msgid "maintainer scripts and their arguments are within boxes;" +msgstr "" + +#: ../../ap-flowcharts.rst:9 +msgid "actions carried out external to the scripts are in italics; and" +msgstr "" + +#: ../../ap-flowcharts.rst:11 +msgid "the ``dpkg`` status of the package at the end of the run are in bold type." +msgstr "" + +#: ../../ap-flowcharts.rst:17 +msgid "Installing a package that was not previously installed" +msgstr "" + +#: ../../ap-flowcharts.rst:22 +msgid "Installing a package that was previously removed, but not purged" +msgstr "" + +#: ../../ap-flowcharts.rst:27 +msgid "Upgrading a package" +msgstr "" + +#: ../../ap-flowcharts.rst:32 +msgid "Removing a package" +msgstr "" + +#: ../../ap-flowcharts.rst:37 +msgid "Purging a package previously removed" +msgstr "" + +#: ../../ap-flowcharts.rst:42 +msgid "Removing and purging a package" +msgstr "" + +#: ../../ap-flowcharts.rst:45 +msgid "" +"These flowcharts were originally created by Margarita Manterola for the " +"Debian Women project wiki." +msgstr "" + diff --git a/locales/ja/LC_MESSAGES/ap-license.po b/locales/ja/LC_MESSAGES/ap-license.po new file mode 100644 index 0000000..4f31f67 --- /dev/null +++ b/locales/ja/LC_MESSAGES/ap-license.po @@ -0,0 +1,59 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1996, 1997, 1998 Ian Jackson, Christian Schwarz, 1998-2017, +# The Debian Policy Mailing List +# This file is distributed under the same license as the Debian Policy +# Manual package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2018. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Debian Policy Manual 4.1.6.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-08-02 11:56+0800\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language-Team: LANGUAGE <LL@li.org>\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.4.0\n" + +#: ../../ap-license.rst:2 +msgid "License" +msgstr "" + +#: ../../ap-license.rst:4 +msgid "Copyright © 1996, 1997, 1998 Ian Jackson and Christian Schwarz" +msgstr "" + +#: ../../ap-license.rst:6 +msgid "" +"These are the copyright dates of the original Policy manual. Since then," +" this manual has been updated by many others. No comprehensive " +"collection of copyright notices for subsequent work exists." +msgstr "" + +#: ../../ap-license.rst:10 +msgid "" +"This manual is free software; you may redistribute it and/or modify it " +"under the terms of the GNU General Public License as published by the " +"Free Software Foundation; either version 2 of the License, or (at your " +"option) any later version." +msgstr "" + +#: ../../ap-license.rst:15 +msgid "" +"This is distributed in the hope that it will be useful, but WITHOUT ANY " +"WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS" +" FOR A PARTICULAR PURPOSE. See the GNU General Public License for more " +"details." +msgstr "" + +#: ../../ap-license.rst:20 +msgid "" +"A copy of the GNU General Public License is available as ``/usr/share" +"/common-licenses/GPL`` in the Debian distribution or on the World Wide " +"Web at `<https://www.gnu.org/licenses/>`_." +msgstr "" + diff --git a/locales/ja/LC_MESSAGES/ap-pkg-alternatives.po b/locales/ja/LC_MESSAGES/ap-pkg-alternatives.po new file mode 100644 index 0000000..66a608a --- /dev/null +++ b/locales/ja/LC_MESSAGES/ap-pkg-alternatives.po @@ -0,0 +1,66 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1996, 1997, 1998 Ian Jackson, Christian Schwarz, 1998-2017, +# The Debian Policy Mailing List +# This file is distributed under the same license as the Debian Policy +# Manual package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2018. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Debian Policy Manual 4.1.6.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-08-02 11:56+0800\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language-Team: LANGUAGE <LL@li.org>\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.4.0\n" + +#: ../../ap-pkg-alternatives.rst:2 +msgid "" +"Alternative versions of an interface - ``update-alternatives`` (from old " +"Packaging Manual)" +msgstr "" + +#: ../../ap-pkg-alternatives.rst:4 +msgid "" +"When several packages all provide different versions of the same program " +"or file it is useful to have the system select a default, but to allow " +"the system administrator to change it and have their decisions respected." +msgstr "" + +#: ../../ap-pkg-alternatives.rst:9 +msgid "" +"For example, there are several versions of the ``vi`` editor, and there " +"is no reason to prevent all of them from being installed at once, each " +"under their own name (``nvi``, ``vim`` or whatever). Nevertheless it is " +"desirable to have the name ``vi`` refer to something, at least by " +"default." +msgstr "" + +#: ../../ap-pkg-alternatives.rst:15 +msgid "" +"If all the packages involved cooperate, this can be done with ``update-" +"alternatives``." +msgstr "" + +#: ../../ap-pkg-alternatives.rst:18 +msgid "" +"Each package provides its own version under its own name, and calls " +"``update-alternatives`` in its postinst to register its version (and " +"again in its prerm to deregister it)." +msgstr "" + +#: ../../ap-pkg-alternatives.rst:22 +msgid "See the update-alternatives(8) man page for details." +msgstr "" + +#: ../../ap-pkg-alternatives.rst:24 +msgid "" +"If ``update-alternatives`` does not seem appropriate you may wish to " +"consider using diversions instead." +msgstr "" + diff --git a/locales/ja/LC_MESSAGES/ap-pkg-binarypkg.po b/locales/ja/LC_MESSAGES/ap-pkg-binarypkg.po new file mode 100644 index 0000000..bf1d8af --- /dev/null +++ b/locales/ja/LC_MESSAGES/ap-pkg-binarypkg.po @@ -0,0 +1,238 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1996, 1997, 1998 Ian Jackson, Christian Schwarz, 1998-2017, +# The Debian Policy Mailing List +# This file is distributed under the same license as the Debian Policy +# Manual package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2018. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Debian Policy Manual 4.1.6.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-08-02 11:56+0800\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language-Team: LANGUAGE <LL@li.org>\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.4.0\n" + +#: ../../ap-pkg-binarypkg.rst:2 +msgid "Binary packages (from old Packaging Manual)" +msgstr "" + +#: ../../ap-pkg-binarypkg.rst:4 +msgid "See deb(5) and :ref:`s-pkg-controlarea`." +msgstr "" + +#: ../../ap-pkg-binarypkg.rst:9 +msgid "Creating package files - ``dpkg-deb``" +msgstr "" + +#: ../../ap-pkg-binarypkg.rst:11 +msgid "" +"All manipulation of binary package files is done by ``dpkg-deb``; it's " +"the only program that has knowledge of the format. (``dpkg-deb`` may be " +"invoked by calling ``dpkg``, as ``dpkg`` will spot that the options " +"requested are appropriate to ``dpkg-deb`` and invoke that instead with " +"the same arguments.)" +msgstr "" + +#: ../../ap-pkg-binarypkg.rst:17 +msgid "" +"In order to create a binary package, you must make a directory tree which" +" contains all the files and directories you want to have in the file " +"system data part of the package. In Debian-format source packages, this " +"directory is usually either ``debian/tmp`` or ``debian/pkg``, relative to" +" the top of the package's source tree." +msgstr "" + +#: ../../ap-pkg-binarypkg.rst:23 +msgid "" +"They should have the locations (relative to the root of the directory " +"tree you're constructing) ownerships and permissions which you want them " +"to have on the system when they are installed." +msgstr "" + +#: ../../ap-pkg-binarypkg.rst:27 +msgid "" +"With current versions of ``dpkg`` the uid/username and gid/groupname " +"mappings for the users and groups being used should be the same on the " +"system where the package is built and the one where it is installed." +msgstr "" + +#: ../../ap-pkg-binarypkg.rst:31 +msgid "" +"You need to add one special directory to the root of the miniature file " +"system tree you're creating: ``DEBIAN``. It should contain the control " +"information files, notably the binary package control file (see :ref:`s" +"-pkg-controlfile`)." +msgstr "" + +#: ../../ap-pkg-binarypkg.rst:36 +msgid "" +"The ``DEBIAN`` directory will not appear in the file system archive of " +"the package, and so won't be installed by ``dpkg`` when the package is " +"unpacked." +msgstr "" + +#: ../../ap-pkg-binarypkg.rst:40 +msgid "When you've prepared the package, you should invoke:" +msgstr "" + +#: ../../ap-pkg-binarypkg.rst:46 +msgid "" +"This will build the package in ``directory.deb``. (``dpkg`` knows that " +"``--build`` is a ``dpkg-deb`` option, so it invokes ``dpkg-deb`` with the" +" same arguments to build the package.)" +msgstr "" + +#: ../../ap-pkg-binarypkg.rst:50 +msgid "" +"See the dpkg-deb(8) man page for details of how to examine the contents " +"of this newly-created file. You may find the output of following commands" +" enlightening:" +msgstr "" + +#: ../../ap-pkg-binarypkg.rst:60 +msgid "To view the copyright file for a package you could use this command:" +msgstr "" + +#: ../../ap-pkg-binarypkg.rst:69 +msgid "Package control information files" +msgstr "" + +#: ../../ap-pkg-binarypkg.rst:71 +msgid "" +"The control information portion of a binary package is a collection of " +"files with names known to ``dpkg``. It will treat the contents of these " +"files specially - some of them contain information used by ``dpkg`` when " +"installing or removing the package; others are scripts which the package " +"maintainer wants ``dpkg`` to run." +msgstr "" + +#: ../../ap-pkg-binarypkg.rst:77 +msgid "" +"It is possible to put other files in the package control information file" +" area, but this is not generally a good idea (though they will largely be" +" ignored)." +msgstr "" + +#: ../../ap-pkg-binarypkg.rst:81 +msgid "" +"Here is a brief list of the control information files supported by " +"``dpkg`` and a summary of what they're used for." +msgstr "" + +#: ../../ap-pkg-binarypkg.rst:93 +msgid "``control``" +msgstr "" + +#: ../../ap-pkg-binarypkg.rst:85 +msgid "" +"This is the key description file used by ``dpkg``. It specifies the " +"package's name and version, gives its description for the user, states " +"its relationships with other packages, and so forth. See " +":ref:`s-sourcecontrolfiles` and :ref:`s-binarycontrolfiles`." +msgstr "" + +#: ../../ap-pkg-binarypkg.rst:91 +msgid "" +"It is usually generated automatically from information in the source " +"package by the ``dpkg-gencontrol`` program, and with assistance from " +"``dpkg-shlibdeps``. See :doc:`ap-pkg-sourcepkg`." +msgstr "" + +#: ../../ap-pkg-binarypkg.rst:108 +msgid "``postinst``, ``preinst``, ``postrm``, ``prerm``" +msgstr "" + +#: ../../ap-pkg-binarypkg.rst:96 +msgid "" +"These are executable files (usually scripts) which ``dpkg`` runs during " +"installation, upgrade and removal of packages. They allow the package to " +"deal with matters which are particular to that package or require more " +"complicated processing than that provided by ``dpkg``. Details of when " +"and how they are called are in :doc:`Package maintainer scripts and " +"installation procedure <ch-maintainerscripts>`." +msgstr "" + +#: ../../ap-pkg-binarypkg.rst:103 +msgid "" +"It is very important to make these scripts idempotent. See " +":ref:`s-idempotency`." +msgstr "" + +#: ../../ap-pkg-binarypkg.rst:106 +msgid "" +"The maintainer scripts are not guaranteed to run with a controlling " +"terminal and may not be able to interact with the user. See " +":ref:`s-controllingterminal`." +msgstr "" + +#: ../../ap-pkg-binarypkg.rst:113 +msgid "``conffiles`` This file contains a list of configuration files which" +msgstr "" + +#: ../../ap-pkg-binarypkg.rst:111 +msgid "" +"are to be handled automatically by ``dpkg`` (see :doc:`ap-pkg-" +"conffiles`). Note that not necessarily every configuration file should be" +" listed here." +msgstr "" + +#: ../../ap-pkg-binarypkg.rst:120 +msgid "``shlibs``" +msgstr "" + +#: ../../ap-pkg-binarypkg.rst:116 +msgid "" +"This file contains a list of the shared libraries supplied by the " +"package, with dependency details for each. This is used by ``dpkg-" +"shlibdeps`` when it determines what dependencies are required in a " +"package control file. The ``shlibs`` file format is described on " +":ref:`s-shlibs`." +msgstr "" + +#: ../../ap-pkg-binarypkg.rst:125 +msgid "The main control information file: ``control``" +msgstr "" + +#: ../../ap-pkg-binarypkg.rst:127 +msgid "" +"The most important control information file used by ``dpkg`` when it " +"installs a package is ``control``. It contains all the package's \"vital " +"statistics\"." +msgstr "" + +#: ../../ap-pkg-binarypkg.rst:131 +msgid "" +"The binary package control files of packages built from Debian sources " +"are made by a special tool, ``dpkg-gencontrol``, which reads " +"``debian/control`` and ``debian/changelog`` to find the information it " +"needs. See :doc:`ap-pkg-sourcepkg` for more details." +msgstr "" + +#: ../../ap-pkg-binarypkg.rst:136 +msgid "" +"The fields in binary package control files are listed in " +":ref:`s-binarycontrolfiles`." +msgstr "" + +#: ../../ap-pkg-binarypkg.rst:139 +msgid "" +"A description of the syntax of control files and the purpose of the " +"fields is available in :doc:`Control files and their fields <ch-" +"controlfields>`." +msgstr "" + +#: ../../ap-pkg-binarypkg.rst:146 +msgid "Time Stamps" +msgstr "" + +#: ../../ap-pkg-binarypkg.rst:148 +msgid "See :ref:`s-timestamps`." +msgstr "" + diff --git a/locales/ja/LC_MESSAGES/ap-pkg-conffiles.po b/locales/ja/LC_MESSAGES/ap-pkg-conffiles.po new file mode 100644 index 0000000..59ded7f --- /dev/null +++ b/locales/ja/LC_MESSAGES/ap-pkg-conffiles.po @@ -0,0 +1,176 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1996, 1997, 1998 Ian Jackson, Christian Schwarz, 1998-2017, +# The Debian Policy Mailing List +# This file is distributed under the same license as the Debian Policy +# Manual package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2018. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Debian Policy Manual 4.1.6.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-08-02 11:56+0800\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language-Team: LANGUAGE <LL@li.org>\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.4.0\n" + +#: ../../ap-pkg-conffiles.rst:2 +msgid "Configuration file handling (from old Packaging Manual)" +msgstr "" + +#: ../../ap-pkg-conffiles.rst:4 +msgid "" +"``dpkg`` can do a certain amount of automatic handling of package " +"configuration files." +msgstr "" + +#: ../../ap-pkg-conffiles.rst:7 +msgid "" +"Whether this mechanism is appropriate depends on a number of factors, but" +" basically there are two approaches to any particular configuration file." +msgstr "" + +#: ../../ap-pkg-conffiles.rst:11 +msgid "" +"The easy method is to ship a best-effort configuration in the package, " +"and use ``dpkg``'s conffile mechanism to handle updates. If the user is " +"unlikely to want to edit the file, but you need them to be able to " +"without losing their changes, and a new package with a changed version of" +" the file is only released infrequently, this is a good approach." +msgstr "" + +#: ../../ap-pkg-conffiles.rst:17 +msgid "" +"The hard method is to build the configuration file from scratch in the " +"``postinst`` script, and to take the responsibility for fixing any " +"mistakes made in earlier versions of the package automatically. This will" +" be appropriate if the file is likely to need to be different on each " +"system." +msgstr "" + +#: ../../ap-pkg-conffiles.rst:26 +msgid "Automatic handling of configuration files by ``dpkg``" +msgstr "" + +#: ../../ap-pkg-conffiles.rst:28 +msgid "" +"A package may contain a control information file called ``conffiles``. " +"This file should be a list of filenames of configuration files needing " +"automatic handling, separated by newlines. The filenames should be " +"absolute pathnames, and the files referred to should actually exist in " +"the package." +msgstr "" + +#: ../../ap-pkg-conffiles.rst:34 +msgid "" +"When a package is upgraded ``dpkg`` will process the configuration files " +"during the configuration stage, shortly before it runs the package's " +"``postinst`` script," +msgstr "" + +#: ../../ap-pkg-conffiles.rst:38 +msgid "" +"For each file it checks to see whether the version of the file included " +"in the package is the same as the one that was included in the last " +"version of the package (the one that is being upgraded from); it also " +"compares the version currently installed on the system with the one " +"shipped with the last version." +msgstr "" + +#: ../../ap-pkg-conffiles.rst:44 +msgid "" +"If neither the user nor the package maintainer has changed the file, it " +"is left alone. If one or the other has changed their version, then the " +"changed version is preferred - i.e., if the user edits their file, but " +"the package maintainer doesn't ship a different version, the user's " +"changes will stay, silently, but if the maintainer ships a new version " +"and the user hasn't edited it the new version will be installed (with an " +"informative message). If both have changed their version the user is " +"prompted about the problem and must resolve the differences themselves." +msgstr "" + +#: ../../ap-pkg-conffiles.rst:53 +msgid "" +"The comparisons are done by calculating the MD5 message digests of the " +"files, and storing the MD5 of the file as it was included in the most " +"recent version of the package." +msgstr "" + +#: ../../ap-pkg-conffiles.rst:57 +msgid "" +"When a package is installed for the first time ``dpkg`` will install the " +"file that comes with it, unless that would mean overwriting a file " +"already on the file system." +msgstr "" + +#: ../../ap-pkg-conffiles.rst:61 +msgid "" +"However, note that ``dpkg`` will *not* replace a conffile that was " +"removed by the user (or by a script). This is necessary because with some" +" programs a missing file produces an effect hard or impossible to achieve" +" in another way, so that a missing file needs to be kept that way if the " +"user did it." +msgstr "" + +#: ../../ap-pkg-conffiles.rst:67 +msgid "" +"Note that a package should *not* modify a ``dpkg``-handled conffile in " +"its maintainer scripts. Doing this will lead to ``dpkg`` giving the user " +"confusing and possibly dangerous options for conffile update when the " +"package is upgraded." +msgstr "" + +#: ../../ap-pkg-conffiles.rst:75 +msgid "Fully-featured maintainer script configuration handling" +msgstr "" + +#: ../../ap-pkg-conffiles.rst:77 +msgid "" +"For files which contain site-specific information such as the hostname " +"and networking details and so forth, it is better to create the file in " +"the package's ``postinst`` script." +msgstr "" + +#: ../../ap-pkg-conffiles.rst:81 +msgid "" +"This will typically involve examining the state of the rest of the system" +" to determine values and other information, and may involve prompting the" +" user for some information which can't be obtained some other way." +msgstr "" + +#: ../../ap-pkg-conffiles.rst:86 +msgid "" +"When using this method there are a couple of important issues which " +"should be considered:" +msgstr "" + +#: ../../ap-pkg-conffiles.rst:89 +msgid "" +"If you discover a bug in the program which generates the configuration " +"file, or if the format of the file changes from one version to the next, " +"you will have to arrange for the postinst script to do something sensible" +" - usually this will mean editing the installed configuration file to " +"remove the problem or change the syntax. You will have to do this very " +"carefully, since the user may have changed the file, perhaps to fix the " +"very problem that your script is trying to deal with - you will have to " +"detect these situations and deal with them correctly." +msgstr "" + +#: ../../ap-pkg-conffiles.rst:98 +msgid "" +"If you do go down this route it's probably a good idea to make the " +"program that generates the configuration file(s) a separate program in " +"``/usr/sbin``, by convention called ``packageconfig`` and then run that " +"if appropriate from the post-installation script. The ``packageconfig`` " +"program should not unquestioningly overwrite an existing configuration - " +"if its mode of operation is geared towards setting up a package for the " +"first time (rather than any arbitrary reconfiguration later) you should " +"have it check whether the configuration already exists, and require a " +"``--force`` flag to overwrite it." +msgstr "" + diff --git a/locales/ja/LC_MESSAGES/ap-pkg-controlfields.po b/locales/ja/LC_MESSAGES/ap-pkg-controlfields.po new file mode 100644 index 0000000..85c4f62 --- /dev/null +++ b/locales/ja/LC_MESSAGES/ap-pkg-controlfields.po @@ -0,0 +1,165 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1996, 1997, 1998 Ian Jackson, Christian Schwarz, 1998-2017, +# The Debian Policy Mailing List +# This file is distributed under the same license as the Debian Policy +# Manual package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2018. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Debian Policy Manual 4.1.6.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-08-02 11:56+0800\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language-Team: LANGUAGE <LL@li.org>\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.4.0\n" + +#: ../../ap-pkg-controlfields.rst:2 +msgid "Control files and their fields (from old Packaging Manual)" +msgstr "" + +#: ../../ap-pkg-controlfields.rst:4 +msgid "" +"Many of the tools in the ``dpkg`` suite manipulate data in a common " +"format, known as control files. Binary and source packages have control " +"data as do the ``.changes`` files which control the installation of " +"uploaded files, and ``dpkg``'s internal databases are in a similar " +"format." +msgstr "" + +#: ../../ap-pkg-controlfields.rst:13 +msgid "Syntax of control files" +msgstr "" + +#: ../../ap-pkg-controlfields.rst:15 +msgid "See :ref:`s-controlsyntax`." +msgstr "" + +#: ../../ap-pkg-controlfields.rst:17 +msgid "" +"It is important to note that there are several fields which are optional " +"as far as ``dpkg`` and the related tools are concerned, but which must " +"appear in every Debian package, or whose omission may cause problems." +msgstr "" + +#: ../../ap-pkg-controlfields.rst:24 +msgid "List of fields" +msgstr "" + +#: ../../ap-pkg-controlfields.rst:26 +msgid "See :ref:`s-controlfieldslist`." +msgstr "" + +#: ../../ap-pkg-controlfields.rst:28 +msgid "" +"This section now contains only the fields that didn't belong to the " +"Policy manual." +msgstr "" + +#: ../../ap-pkg-controlfields.rst:34 +msgid "``Filename`` and ``MSDOS-Filename``" +msgstr "" + +#: ../../ap-pkg-controlfields.rst:36 +msgid "" +"These fields in ``Packages`` files give the filename(s) of (the parts of)" +" a package in the distribution directories, relative to the root of the " +"Debian hierarchy. If the package has been split into several parts the " +"parts are all listed in order, separated by spaces." +msgstr "" + +#: ../../ap-pkg-controlfields.rst:44 +msgid "``Size`` and ``MD5sum``" +msgstr "" + +#: ../../ap-pkg-controlfields.rst:46 +msgid "" +"These fields in ``Packages`` files give the size (in bytes, expressed in " +"decimal) and MD5 checksum of the file(s) which make(s) up a binary " +"package in the distribution. If the package is split into several parts " +"the values for the parts are listed in order, separated by spaces." +msgstr "" + +#: ../../ap-pkg-controlfields.rst:54 +msgid "``Status``" +msgstr "" + +#: ../../ap-pkg-controlfields.rst:56 +msgid "" +"This field in ``dpkg``'s status file records whether the user wants a " +"package installed, removed or left alone, whether it is broken (requiring" +" re-installation) or not and what its current state on the system is. " +"Each of these pieces of information is a single word." +msgstr "" + +#: ../../ap-pkg-controlfields.rst:64 +msgid "``Config-Version``" +msgstr "" + +#: ../../ap-pkg-controlfields.rst:66 +msgid "" +"If a package is not installed or not configured, this field in ``dpkg``'s" +" status file records the last version of the package which was " +"successfully configured." +msgstr "" + +#: ../../ap-pkg-controlfields.rst:73 +msgid "``Conffiles``" +msgstr "" + +#: ../../ap-pkg-controlfields.rst:75 +msgid "" +"This field in ``dpkg``'s status file contains information about the " +"automatically-managed configuration files held by a package. This field " +"should *not* appear anywhere in a package!" +msgstr "" + +#: ../../ap-pkg-controlfields.rst:82 +msgid "Obsolete fields" +msgstr "" + +#: ../../ap-pkg-controlfields.rst:84 +msgid "" +"These are still recognized by ``dpkg`` but should not appear anywhere any" +" more." +msgstr "" + +#: ../../ap-pkg-controlfields.rst:89 +msgid "``Revision``; \\ ``Package-Revision``; \\ ``Package_Revision``" +msgstr "" + +#: ../../ap-pkg-controlfields.rst:88 +msgid "" +"The Debian revision part of the package version was at one point in a " +"separate control field. This field went through several names." +msgstr "" + +#: ../../ap-pkg-controlfields.rst:92 +msgid "``Recommended``" +msgstr "" + +#: ../../ap-pkg-controlfields.rst:92 +msgid "Old name for ``Recommends``." +msgstr "" + +#: ../../ap-pkg-controlfields.rst:95 +msgid "``Optional``" +msgstr "" + +#: ../../ap-pkg-controlfields.rst:95 +msgid "Old name for ``Suggests``." +msgstr "" + +#: ../../ap-pkg-controlfields.rst:98 +msgid "``Class``" +msgstr "" + +#: ../../ap-pkg-controlfields.rst:98 +msgid "Old name for ``Priority``." +msgstr "" + diff --git a/locales/ja/LC_MESSAGES/ap-pkg-diversions.po b/locales/ja/LC_MESSAGES/ap-pkg-diversions.po new file mode 100644 index 0000000..efd6dc3 --- /dev/null +++ b/locales/ja/LC_MESSAGES/ap-pkg-diversions.po @@ -0,0 +1,112 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1996, 1997, 1998 Ian Jackson, Christian Schwarz, 1998-2017, +# The Debian Policy Mailing List +# This file is distributed under the same license as the Debian Policy +# Manual package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2018. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Debian Policy Manual 4.1.6.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-08-02 11:56+0800\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language-Team: LANGUAGE <LL@li.org>\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.4.0\n" + +#: ../../ap-pkg-diversions.rst:2 +msgid "" +"Diversions - overriding a package's version of a file (from old Packaging" +" Manual)" +msgstr "" + +#: ../../ap-pkg-diversions.rst:4 +msgid "" +"It is possible to have ``dpkg`` not overwrite a file when it reinstalls " +"the package it belongs to, and to have it put the file from the package " +"somewhere else instead." +msgstr "" + +#: ../../ap-pkg-diversions.rst:8 +msgid "" +"This can be used locally to override a package's version of a file, or by" +" one package to override another's version (or provide a wrapper for it)." +msgstr "" + +#: ../../ap-pkg-diversions.rst:12 +msgid "" +"Before deciding to use a diversion, read :doc:`ap-pkg-alternatives` to " +"see if you really want a diversion rather than several alternative " +"versions of a program." +msgstr "" + +#: ../../ap-pkg-diversions.rst:16 +msgid "" +"There is a diversion list, which is read by ``dpkg``, and updated by a " +"special program ``dpkg-divert``. Please see dpkg-divert(8) for full " +"details of its operation." +msgstr "" + +#: ../../ap-pkg-diversions.rst:20 +msgid "" +"When a package wishes to divert a file from another, it should call " +"``dpkg-divert`` in its preinst to add the diversion and rename the " +"existing file. For example, supposing that a ``smailwrapper`` package " +"wishes to install a wrapper around ``/usr/sbin/smail``:" +msgstr "" + +#: ../../ap-pkg-diversions.rst:30 +msgid "" +"The ``--package smailwrapper`` ensures that ``smailwrapper``'s copy of " +"``/usr/sbin/smail`` can bypass the diversion and get installed as the " +"true version. It's safe to add the diversion unconditionally on upgrades " +"since it will be left unchanged if it already exists, but ``dpkg-divert``" +" will display a message. To suppress that message, make the command " +"conditional on the version from which the package is being upgraded:" +msgstr "" + +#: ../../ap-pkg-diversions.rst:45 +msgid "" +"where ``1.0-2`` is the version at which the diversion was first added to " +"the package. Running the command during abort-upgrade is pointless but " +"harmless." +msgstr "" + +#: ../../ap-pkg-diversions.rst:49 +msgid "The postrm has to do the reverse:" +msgstr "" + +#: ../../ap-pkg-diversions.rst:58 +msgid "" +"If the diversion was added at a particular version, the postrm should " +"also handle the failure case of upgrading from an older version (unless " +"the older version is so old that direct upgrades are no longer " +"supported):" +msgstr "" + +#: ../../ap-pkg-diversions.rst:70 +msgid "" +"where ``1.0-2`` is the version at which the diversion was first added to " +"the package. The postrm should not remove the diversion on upgrades both " +"because there's no reason to remove the diversion only to immediately re-" +"add it and since the postrm of the old package is run after unpacking so " +"the removal of the diversion will fail." +msgstr "" + +#: ../../ap-pkg-diversions.rst:76 +msgid "" +"Do not attempt to divert a file which is vitally important for the " +"system's operation - when using ``dpkg-divert`` there is a time, after it" +" has been diverted but before ``dpkg`` has installed the new version, " +"when the file does not exist." +msgstr "" + +#: ../../ap-pkg-diversions.rst:81 +msgid "Do not attempt to divert a conffile, as ``dpkg`` does not handle it well." +msgstr "" + diff --git a/locales/ja/LC_MESSAGES/ap-pkg-scope.po b/locales/ja/LC_MESSAGES/ap-pkg-scope.po new file mode 100644 index 0000000..bd17eb3 --- /dev/null +++ b/locales/ja/LC_MESSAGES/ap-pkg-scope.po @@ -0,0 +1,112 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1996, 1997, 1998 Ian Jackson, Christian Schwarz, 1998-2017, +# The Debian Policy Mailing List +# This file is distributed under the same license as the Debian Policy +# Manual package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2018. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Debian Policy Manual 4.1.6.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-08-02 11:56+0800\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language-Team: LANGUAGE <LL@li.org>\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.4.0\n" + +#: ../../ap-pkg-scope.rst:2 +msgid "Introduction and scope of these appendices" +msgstr "" + +#: ../../ap-pkg-scope.rst:4 +msgid "" +"These appendices, except the final three, are taken essentially verbatim " +"from the now-deprecated Packaging Manual, version 3.2.1.0. They are the " +"chapters which are likely to be of use to package maintainers and which " +"have not already been included in the policy document itself. Most of " +"these sections are very likely not relevant to policy; they should be " +"treated as documentation for the packaging system. Please note that these" +" appendices are included for convenience, and for historical reasons: " +"they used to be part of policy package, and they have not yet been " +"incorporated into dpkg documentation. However, they still have value, and" +" hence they are presented here." +msgstr "" + +#: ../../ap-pkg-scope.rst:15 +msgid "" +"They have not yet been checked to ensure that they are compatible with " +"the contents of policy, and if there are any contradictions, the version " +"in the main policy document takes precedence. The remaining chapters of " +"the old Packaging Manual have also not been read in detail to ensure that" +" there are not parts which have been left out. Both of these will be done" +" in due course." +msgstr "" + +#: ../../ap-pkg-scope.rst:22 +msgid "" +"Certain parts of the Packaging manual were integrated into the Policy " +"Manual proper, and removed from the appendices. Links have been placed " +"from the old locations to the new ones." +msgstr "" + +#: ../../ap-pkg-scope.rst:26 +msgid "" +"``dpkg`` is a suite of programs for creating binary package files and " +"installing and removing them on Unix systems. [#]_" +msgstr "" + +#: ../../ap-pkg-scope.rst:29 +msgid "" +"The binary packages are designed for the management of installed " +"executable programs (usually compiled binaries) and their associated " +"data, though source code examples and documentation are provided as part " +"of some packages." +msgstr "" + +#: ../../ap-pkg-scope.rst:34 +msgid "" +"This manual describes the technical aspects of creating Debian binary " +"packages (``.deb`` files). It documents the behavior of the package " +"management programs ``dpkg``, ``dselect`` et al. and the way they " +"interact with packages." +msgstr "" + +#: ../../ap-pkg-scope.rst:39 +msgid "" +"This manual does not go into detail about the options and usage of the " +"package building and installation tools. It should therefore be read in " +"conjunction with those programs' man pages." +msgstr "" + +#: ../../ap-pkg-scope.rst:43 +msgid "" +"The utility programs which are provided with ``dpkg`` not described in " +"detail here, are documented in their man pages." +msgstr "" + +#: ../../ap-pkg-scope.rst:46 +msgid "" +"It is assumed that the reader is reasonably familiar with the ``dpkg`` " +"System Administrators' manual. Unfortunately this manual does not yet " +"exist." +msgstr "" + +#: ../../ap-pkg-scope.rst:50 +msgid "" +"The Debian version of the FSF's GNU hello program is provided as an " +"example for people wishing to create Debian packages. However, while the " +"examples are helpful, they do not replace the need to read and follow the" +" Policy and Programmer's Manual." +msgstr "" + +#: ../../ap-pkg-scope.rst:56 +msgid "" +"``dpkg`` is targeted primarily at Debian, but may work on or be ported to" +" other systems." +msgstr "" + diff --git a/locales/ja/LC_MESSAGES/ap-pkg-sourcepkg.po b/locales/ja/LC_MESSAGES/ap-pkg-sourcepkg.po new file mode 100644 index 0000000..fdb3c48 --- /dev/null +++ b/locales/ja/LC_MESSAGES/ap-pkg-sourcepkg.po @@ -0,0 +1,514 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1996, 1997, 1998 Ian Jackson, Christian Schwarz, 1998-2017, +# The Debian Policy Mailing List +# This file is distributed under the same license as the Debian Policy +# Manual package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2018. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Debian Policy Manual 4.1.6.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-08-02 11:56+0800\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language-Team: LANGUAGE <LL@li.org>\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.4.0\n" + +#: ../../ap-pkg-sourcepkg.rst:2 +msgid "Source packages (from old Packaging Manual)" +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:4 +msgid "" +"The Debian binary packages in the distribution are generated from Debian " +"sources, which are in a special format to assist the easy and automatic " +"building of binaries." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:11 +msgid "Tools for processing source packages" +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:13 +msgid "" +"Various tools are provided for manipulating source packages; they pack " +"and unpack sources and help build of binary packages and help manage the " +"distribution of new versions." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:17 +msgid "" +"They are introduced and typical uses described here; see dpkg-source(1) " +"for full documentation about their arguments and operation." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:20 +msgid "" +"For examples of how to construct a Debian source package, and how to use " +"those utilities that are used by Debian source packages, please see the " +"``hello`` example package." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:27 +msgid "``dpkg-source`` - packs and unpacks Debian source packages" +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:29 +msgid "" +"This program is frequently used by hand, and is also called from package-" +"independent automated building scripts such as ``dpkg-buildpackage``." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:33 +msgid "To unpack a package it is typically invoked with" +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:39 +msgid "" +"with the ``filename.tar.gz`` and ``filename.diff.gz`` (if applicable) in " +"the same directory. It unpacks into ``package-version``, and if " +"applicable ``package-version.orig``, in the current directory." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:43 +msgid "To create a packed source archive it is typically invoked:" +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:49 +msgid "" +"This will create the ``.dsc``, ``.tar.gz`` and ``.diff.gz`` (if " +"appropriate) in the current directory. ``dpkg-source`` does not clean the" +" source tree first - this must be done separately if it is required." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:53 +msgid "See also :ref:`s-pkg-sourcearchives`." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:58 +msgid "``dpkg-buildpackage`` - overall package-building control script" +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:60 +msgid "See ``dpkg-buildpackage(1)``." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:65 +msgid "``dpkg-gencontrol`` - generates binary package control files" +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:67 +msgid "" +"This program is usually called from ``debian/rules`` (see " +"`section\\_title <#s-pkg-sourcetree>`__) in the top level of the source " +"tree." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:71 +msgid "" +"This is usually done just before the files and directories in the " +"temporary directory tree where the package is being built have their " +"permissions and ownerships set and the package is constructed using " +"``dpkg-deb/``. [#]_" +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:76 +msgid "" +"``dpkg-gencontrol`` must be called after all the files which are to go " +"into the package have been placed in the temporary build directory, so " +"that its calculation of the installed size of a package is correct." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:80 +msgid "" +"It is also necessary for ``dpkg-gencontrol`` to be run after ``dpkg-" +"shlibdeps`` so that the variable substitutions created by ``dpkg-" +"shlibdeps`` in ``debian/substvars`` are available." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:84 +msgid "" +"For a package which generates only one binary package, and which builds " +"it in ``debian/tmp`` relative to the top of the source package, it is " +"usually sufficient to call ``dpkg-gencontrol``." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:88 +msgid "Sources which build several binaries will typically need something like:" +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:94 +msgid "" +"The ``-P`` tells ``dpkg-gencontrol`` that the package is being built in a" +" non-default directory, and the ``-p`` tells it which package's control " +"file should be generated." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:98 +msgid "" +"``dpkg-gencontrol`` also adds information to the list of files in " +"``debian/files``, for the benefit of (for example) a future invocation of" +" ``dpkg-genchanges``." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:105 +msgid "``dpkg-shlibdeps`` - calculates shared library dependencies" +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:107 +msgid "See ``dpkg-shlibdeps(1)``." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:112 +msgid "``dpkg-distaddfile`` - adds a file to ``debian/files``" +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:114 +msgid "" +"Some packages' uploads need to include files other than the source and " +"binary package files." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:117 +msgid "" +"``dpkg-distaddfile`` adds a file to the ``debian/files`` file so that it " +"will be included in the ``.changes`` file when ``dpkg-genchanges`` is " +"run." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:121 +msgid "It is usually invoked from the ``binary`` target of ``debian/rules``:" +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:127 +msgid "" +"The filename is relative to the directory where ``dpkg-genchanges`` will " +"expect to find it - this is usually the directory above the top level of " +"the source tree. The ``debian/rules`` target should put the file there " +"just before or just after calling ``dpkg-distaddfile``." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:132 +msgid "" +"The section and priority are passed unchanged into the resulting " +"``.changes`` file." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:138 +msgid "``dpkg-genchanges`` - generates a ``.changes`` upload control file" +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:140 +msgid "See ``dpkg-genchanges(1)``." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:145 +msgid "``dpkg-parsechangelog`` - produces parsed representation of a changelog" +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:147 +msgid "See ``dpkg-parsechangelog(1)``." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:152 +msgid "``dpkg-architecture`` - information about the build and host system" +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:154 +msgid "See ``dpkg-architecture(1)``." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:159 +msgid "The Debian package source tree" +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:161 +msgid "" +"The source archive scheme described later is intended to allow a Debian " +"package source tree with some associated control information to be " +"reproduced and transported easily. The Debian package source tree is a " +"version of the original program with certain files added for the benefit " +"of the packaging process, and with any other changes required made to the" +" rest of the source code and installation scripts." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:168 +msgid "" +"The extra files created for Debian are in the subdirectory ``debian`` of " +"the top level of the Debian package source tree. They are described " +"below." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:175 +msgid "``debian/rules`` - the main building script" +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:177 +msgid "See :ref:`s-debianrules`." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:182 +msgid "``debian/substvars`` and variable substitutions" +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:184 +msgid "See :ref:`s-substvars`." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:189 +msgid "``debian/files``" +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:191 +msgid "See :ref:`s-debianfiles`." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:196 +msgid "``debian/tmp``" +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:198 +msgid "" +"This is the default temporary location for the construction of binary " +"packages by the ``binary`` target. The directory ``tmp`` serves as the " +"root of the file system tree as it is being constructed (for example, by " +"using the package's upstream makefiles install targets and redirecting " +"the output there), and it also contains the ``DEBIAN`` subdirectory. See " +":ref:`s-pkg-bincreating`." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:205 +msgid "" +"This is only a default and can be easily overridden. Most packaging tools" +" no longer use ``debian/tmp``, instead preferring ``debian/pkg`` for the " +"common case of a source package building only one binary package. Such " +"tools usually only use ``debian/tmp`` as a temporary staging area for " +"built files and do not construct packages from it." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:211 +msgid "" +"If several binary packages are generated from the same source tree, it is" +" usual to use a separate ``debian/pkg`` directory for each binary package" +" as the temporary construction locations." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:215 +msgid "" +"Whatever temporary directories are created and used by the ``binary`` " +"target must of course be removed by the ``clean`` target." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:221 +msgid "Source packages as archives" +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:223 +msgid "" +"As it exists on the FTP site, a Debian source package consists of three " +"related files. You must have the right versions of all three to be able " +"to use them." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:230 +msgid "Debian source control file - ``.dsc``" +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:228 +msgid "" +"This file is a control file used by ``dpkg-source`` to extract a source " +"package. See :ref:`s-debiansourcecontrolfiles`." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:234 +msgid "Original source archive - ``package_upstream-version.orig.tar.gz``" +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:233 +msgid "" +"This is a compressed (with ``gzip -9``) ``tar`` file containing the " +"source code from the upstream authors of the program." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:249 +msgid "Debian package diff - ``package_upstream_version-revision.diff.gz``" +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:237 +msgid "" +"This is a unified context diff (``diff -u``) giving the changes which are" +" required to turn the original source into the Debian source. These " +"changes may only include editing and creating plain files. The " +"permissions of files, the targets of symbolic links and the " +"characteristics of special files or pipes may not be changed and no files" +" may be removed or renamed." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:244 +msgid "" +"All the directories in the diff must exist, except the ``debian`` " +"subdirectory of the top of the source tree, which will be created by " +"``dpkg-source`` if necessary when unpacking." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:248 +msgid "" +"The ``dpkg-source`` program will automatically make the ``debian/rules`` " +"file executable (see below)." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:251 +msgid "" +"If there is no original source code - for example, if the package is " +"specially prepared for Debian or the Debian maintainer is the same as the" +" upstream maintainer - the format is slightly different: then there is no" +" diff, and the tarfile is named ``package_version.tar.gz``, and " +"preferably contains a directory named ``package-version``." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:260 +msgid "Unpacking a Debian source package without ``dpkg-source``" +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:262 +msgid "" +"``dpkg-source -x`` is the recommended way to unpack a Debian source " +"package. However, if it is not available it is possible to unpack a " +"Debian source archive as follows:" +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:266 +msgid "Untar the tarfile, which will create a ``.orig`` directory." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:268 +msgid "Rename the ``.orig`` directory to ``package-version``." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:270 +msgid "Create the subdirectory ``debian`` at the top of the source tree." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:272 +msgid "Apply the diff using ``patch -p0``." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:274 +msgid "" +"Untar the tarfile again if you want a copy of the original source code " +"alongside the Debian version." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:277 +msgid "" +"It is not possible to generate a valid Debian source archive without " +"using ``dpkg-source``. In particular, attempting to use ``diff`` directly" +" to generate the ``.diff.gz`` file will not work." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:284 +msgid "Restrictions on objects in source packages" +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:286 +msgid "" +"The source package may not contain any hard links, [#]_ [#]_ device " +"special files, sockets or setuid or setgid files. [#]_" +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:289 +msgid "" +"The source packaging tools manage the changes between the original and " +"Debian source using ``diff`` and ``patch``. Turning the original source " +"tree as included in the ``.orig.tar.gz`` into the Debian package source " +"must not involve any changes which cannot be handled by these tools. " +"Problematic changes which cause ``dpkg-source`` to halt with an error " +"when building the source package are:" +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:296 +msgid "Adding or removing symbolic links, sockets or pipes." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:298 +msgid "Changing the targets of symbolic links." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:300 +msgid "Creating directories, other than ``debian``." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:302 +msgid "Changes to the contents of binary files." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:304 +msgid "" +"Changes which cause ``dpkg-source`` to print a warning but continue " +"anyway are:" +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:307 +msgid "Removing files, directories or symlinks. [#]_" +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:309 +msgid "" +"Changed text files which are missing the usual final newline (either in " +"the original or the modified source tree)." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:312 +msgid "" +"Changes which are not represented, but which are not detected by ``dpkg-" +"source``, are:" +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:315 +msgid "" +"Changing the permissions of files (other than ``debian/rules``) and " +"directories." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:318 +msgid "" +"The ``debian`` directory and ``debian/rules`` are handled specially by " +"``dpkg-source`` - before applying the changes it will create the " +"``debian`` directory, and afterwards it will make ``debian/rules`` world-" +"executable." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:324 +msgid "" +"This is so that the control file which is produced has the right " +"permissions" +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:328 +msgid "" +"This is not currently detected when building source packages, but only " +"when extracting them." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:332 +msgid "" +"Hard links may be permitted at some point in the future, but would " +"require a fair amount of work." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:336 +msgid "Setgid directories are allowed." +msgstr "" + +#: ../../ap-pkg-sourcepkg.rst:339 +msgid "" +"Renaming a file is not treated specially - it is seen as the removal of " +"the old file (which generates a warning, but is otherwise ignored), and " +"the creation of the new one." +msgstr "" + diff --git a/locales/ja/LC_MESSAGES/ap-process.po b/locales/ja/LC_MESSAGES/ap-process.po new file mode 100644 index 0000000..347a802 --- /dev/null +++ b/locales/ja/LC_MESSAGES/ap-process.po @@ -0,0 +1,417 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1996, 1997, 1998 Ian Jackson, Christian Schwarz, 1998-2017, +# The Debian Policy Mailing List +# This file is distributed under the same license as the Debian Policy +# Manual package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2018. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Debian Policy Manual 4.1.6.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-08-02 11:56+0800\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language-Team: LANGUAGE <LL@li.org>\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.4.0\n" + +#: ../../ap-process.rst:2 +msgid "Debian Policy changes process" +msgstr "" + +#: ../../ap-process.rst:7 +msgid "Introduction" +msgstr "" + +#: ../../ap-process.rst:9 +msgid "" +"To introduce a change in the current Debian Policy, the change proposal " +"has to go through a certain process. [#]_" +msgstr "" + +#: ../../ap-process.rst:15 +msgid "Change Goals" +msgstr "" + +#: ../../ap-process.rst:17 +msgid "" +"The change should be technically correct, and consistent with the rest of" +" the policy document. This means no legislating the value of π. This also" +" means that the proposed solution be known to work; iterative design " +"processes do not belong in policy." +msgstr "" + +#: ../../ap-process.rst:22 +msgid "" +"The change should not be too disruptive; if very many packages become " +"instantly buggy, then instead there should be a transition plan. " +"Exceptions should be rare (only if the current state is really " +"untenable), and probably blessed by the TC." +msgstr "" + +#: ../../ap-process.rst:27 +msgid "" +"The change has to be reviewed in depth, in the open, where any one may " +"contribute; a publicly accessible, archived, open mailing list." +msgstr "" + +#: ../../ap-process.rst:30 +msgid "Proposal should be addressed in a timely fashion." +msgstr "" + +#: ../../ap-process.rst:32 +msgid "" +"Any domain experts should be consulted, since not every policy mailing " +"list subscriber is an expert on everything, including policy maintainers." +msgstr "" + +#: ../../ap-process.rst:36 +msgid "" +"The goal is rough consensus on the change, which should not be hard if " +"the matter is technical. Technical issues where there is no agreement " +"should be referred to the TC; non-technical issues should be referred to " +"the whole developer body, and perhaps general resolutions lie down that " +"path." +msgstr "" + +#: ../../ap-process.rst:42 +msgid "" +"Package maintainers whose packages may be impacted should have access to " +"policy change proposals, even if they do not subscribe to policy mailing " +"lists (policy gazette?)." +msgstr "" + +#: ../../ap-process.rst:49 +msgid "Current Process" +msgstr "" + +#: ../../ap-process.rst:51 +msgid "" +"Each suggested change goes through different states. These states are " +"denoted through either usertags of the debian-policy@packages.debian.org " +"user or, for ``moreinfo``, ``patch``, ``pending``, and ``wontfix``, " +"regular tags." +msgstr "" + +#: ../../ap-process.rst:56 +msgid "" +"`Current list of bugs <https://bugs.debian.org/cgi-bin/pkgreport.cgi?src" +"=debian-policy&pend-exc=done>`_" +msgstr "" + +#: ../../ap-process.rst:59 +msgid "" +"The Policy delegates are responsible for managing the tags on bugs and " +"will update tags as new bugs are submitted or as activity happens on " +"bugs. All Debian Developers should feel free to add the seconded tag as " +"described below. Other tags should be changed with the coordination of " +"the Policy Team." +msgstr "" + +#: ../../ap-process.rst:68 +msgid "State A: More information required" +msgstr "" + +#: ../../ap-process.rst:70 +msgid "" +"The Policy delegates are unable to determine whether the bug is really a " +"Policy matter, or judge that there are missing details that would prevent" +" a fruitful discussion (and may result in a confused and unhelpful " +"discussion)." +msgstr "" + +#: ../../ap-process.rst:75 +msgid "" +"Policy delegates ask the original submitter to provide the missing " +"details. Others are asked to refrain from discussing whatever they take " +"the issue to be, limiting their postings to attempts to supply the " +"missing details." +msgstr "" + +#: ../../ap-process.rst:80 +msgid "" +"`TAG: moreinfo <https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=debian-" +"policy&pend-exc=done&tag=moreinfo>`_" +msgstr "" + +#: ../../ap-process.rst:82 +msgid "" +"What needs to happen next: Submitter (or someone else) provides the " +"requested information within 30 days, or the bug is closed." +msgstr "" + +#: ../../ap-process.rst:85 +msgid "The majority of bugs will skip this stage." +msgstr "" + +#: ../../ap-process.rst:90 +msgid "State B: Discussion" +msgstr "" + +#: ../../ap-process.rst:92 +msgid "" +"Discuss remedy. Alternate proposals. Discussion guided by delegates. " +"There should be a clear time limit to this stage, but as yet we have not " +"set one." +msgstr "" + +#: ../../ap-process.rst:96 +msgid "" +"`TAG: discussion <https://bugs.debian.org/cgi-bin/pkgreport.cgi?src" +"=debian-policy&pend-exc=done&tag=discussion>`_" +msgstr "" + +#: ../../ap-process.rst:99 +msgid "" +"What needs to happen next: Reach a conclusion and consensus in the " +"discussion and make a final proposal for what should be changed (if " +"anything), moving to the proposal tag." +msgstr "" + +#: ../../ap-process.rst:106 +msgid "State C: Proposal" +msgstr "" + +#: ../../ap-process.rst:108 +msgid "" +"A final proposal has emerged from the discussion, and there is a rough " +"consensus on how to proceed to resolve the issue." +msgstr "" + +#: ../../ap-process.rst:111 +msgid "" +"`TAG: proposal <https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=debian-" +"policy&pend-exc=done&tag=proposal>`_" +msgstr "" + +#: ../../ap-process.rst:114 +msgid "" +"What needs to happen next: Provided that the rough consensus persists, " +"develop a patch against the current Policy document with specific wording" +" of the change. Often this is done in conjunction with the proposal, in " +"which case one may skip this step and move directly to patch tag." +msgstr "" + +#: ../../ap-process.rst:123 +msgid "State D: Wording proposed" +msgstr "" + +#: ../../ap-process.rst:125 +msgid "" +"A patch against the Policy document reflecting the consensus has been " +"created and is waiting for formal seconds. The standard patch tag is used" +" for this state, since it's essentially equivalent to the standard " +"meaning of that tag." +msgstr "" + +#: ../../ap-process.rst:130 +msgid "" +"`TAG: patch <https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=debian-" +"policy&pend-exc=done&tag=patch>`_" +msgstr "" + +#: ../../ap-process.rst:133 +msgid "" +"What needs to happen next: The proposal needs to be reviewed and " +"seconded. Any Debian developer who agrees with the change and the " +"conclusion of rough consensus from the discussion should say so in the " +"bug log by seconding the proposal." +msgstr "" + +#: ../../ap-process.rst:141 +msgid "State E: Seconded" +msgstr "" + +#: ../../ap-process.rst:143 +msgid "" +"The proposal is signed off on by N Debian Developers. To start with, " +"we're going with N=3, meaning that if three Debian Developers agree, not " +"just with the proposal but with the conclusion that it reflects consensus" +" and addresses the original issue -- it is considered eligible for " +"inclusion in the next version of Policy. Since Policy is partly a " +"technical project governance method, one must be a Debian Developer to " +"formally second, although review and discussion is welcome from anyone. " +"Once this tag has been applied, the bug is waiting for a Policy team " +"member to apply the patch to the package repository." +msgstr "" + +#: ../../ap-process.rst:153 +msgid "" +"`TAG: seconded <https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=debian-" +"policy&pend-exc=done&tag=seconded>`_" +msgstr "" + +#: ../../ap-process.rst:156 +msgid "" +"What needs to happen next: A Policy maintainer does the final review and " +"confirmation, and then applies the patch for the next Policy release." +msgstr "" + +#: ../../ap-process.rst:159 +msgid "" +"This tag is not used very much because normally a Policy maintainer " +"applies the patch and moves the proposal to the next state once enough " +"seconds are reached." +msgstr "" + +#: ../../ap-process.rst:166 +msgid "State F: Accepted" +msgstr "" + +#: ../../ap-process.rst:168 +msgid "" +"Change accepted, will be in next upload. The standard pending tag is used" +" for this state since it matches the regular meaning of pending." +msgstr "" + +#: ../../ap-process.rst:171 +msgid "" +"`TAG: pending <https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=debian-" +"policy&pend-exc=done&tag=pending>`_" +msgstr "" + +#: ../../ap-process.rst:174 +msgid "" +"What needs to happen next: The bug is now in the waiting queue for the " +"next Policy release, and there's nothing left to do except for upload a " +"new version of Policy." +msgstr "" + +#: ../../ap-process.rst:181 +msgid "State G: Reject" +msgstr "" + +#: ../../ap-process.rst:183 +msgid "" +"Rejected proposals. The standard wontfix is used for this state. " +"Normally, bugs in this state will not remain open; instead, a Policy team" +" member will close them with an explanation. The submitter may then " +"appeal to the tech-ctte if they so desire. Alternately, issues appealed " +"to the tech-ctte may remain open with this tag while that appeal " +"proceeds." +msgstr "" + +#: ../../ap-process.rst:190 +msgid "" +"`TAG: wontfix <https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=debian-" +"policy&pend-exc=done&tag=rejected>`_" +msgstr "" + +#: ../../ap-process.rst:193 +msgid "" +"We may use one of the following tags here, but to date we have only used " +"dubious and ctte. It's not clear whether we need more tags for this " +"stage." +msgstr "" + +#: ../../ap-process.rst:198 +msgid "**dubious**" +msgstr "" + +#: ../../ap-process.rst:198 +msgid "Not a policy matter" +msgstr "" + +#: ../../ap-process.rst:201 +msgid "**ctte**" +msgstr "" + +#: ../../ap-process.rst:201 +msgid "Referred to the Technical Committee (tech-ctte)" +msgstr "" + +#: ../../ap-process.rst:204 +msgid "**devel**" +msgstr "" + +#: ../../ap-process.rst:204 +msgid "Referred to the developer body" +msgstr "" + +#: ../../ap-process.rst:207 +msgid "**delegate**" +msgstr "" + +#: ../../ap-process.rst:207 +msgid "Rejected by a Policy delegate" +msgstr "" + +#: ../../ap-process.rst:210 +msgid "**obsolete**" +msgstr "" + +#: ../../ap-process.rst:210 +msgid "The proposal timed out without a conclusion" +msgstr "" + +#: ../../ap-process.rst:212 +msgid "" +"What needs to happen next: The bug should be closed once a final " +"resolution is reached, or retagged to an appropriate state if that final " +"resolution reverses the decision to reject the proposal." +msgstr "" + +#: ../../ap-process.rst:219 +msgid "Other Tags" +msgstr "" + +#: ../../ap-process.rst:221 +msgid "All Policy bugs are additionally categorized by class of bug." +msgstr "" + +#: ../../ap-process.rst:223 +msgid "" +"The normative tag is used for bugs that make normative changes to Policy," +" meaning that the dictates of Policy will change in some fashion as part " +"of the resolution of the bug if the proposal is accepted. The full " +"process is followed for such bugs." +msgstr "" + +#: ../../ap-process.rst:228 +msgid "" +"`TAG: normative <https://bugs.debian.org/cgi-bin/pkgreport.cgi?src" +"=debian-policy&pend-exc=done&tag=normative>`_" +msgstr "" + +#: ../../ap-process.rst:231 +msgid "" +"The informative tag is used for bugs about wording issues, typos, " +"informative footnotes, or other changes that do not affect the formal " +"dictates of Policy, just the presentation. The same tags are used for " +"these bugs for convenience, but the Policy maintainers may make " +"informative changes without following the full process. Informative bugs " +"fall under their discretion." +msgstr "" + +#: ../../ap-process.rst:238 +msgid "" +"`TAG: informative <https://bugs.debian.org/cgi-bin/pkgreport.cgi?src" +"=debian-policy&pend-exc=done&tag=informative>`_" +msgstr "" + +#: ../../ap-process.rst:241 +msgid "" +"The packaging tag is used for bugs about the packaging and build process " +"of the debian-policy Debian package. These bugs do not follow the normal " +"process and will not have the other tags except for pending and wontfix " +"(used with their normal meanings)." +msgstr "" + +#: ../../ap-process.rst:246 +msgid "" +"`TAG: packaging <https://bugs.debian.org/cgi-bin/pkgreport.cgi?src" +"=debian-policy&pend-exc=done&tag=packaging>`_" +msgstr "" + +#: ../../ap-process.rst:250 +msgid "" +"This process was originally developed by Margarita Manterola, Clint " +"Adams, Russ Allbery and Manoj Srivastava. In 2017, Sean Whitton " +"deprecated the 'issue' usertag and added use of the 'moreinfo' tag, after" +" discussions at DebConf17." +msgstr "" + diff --git a/locales/ja/LC_MESSAGES/ch-archive.po b/locales/ja/LC_MESSAGES/ch-archive.po new file mode 100644 index 0000000..fbd135b --- /dev/null +++ b/locales/ja/LC_MESSAGES/ch-archive.po @@ -0,0 +1,589 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1996, 1997, 1998 Ian Jackson, Christian Schwarz, 1998-2017, +# The Debian Policy Mailing List +# This file is distributed under the same license as the Debian Policy +# Manual package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2018. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Debian Policy Manual 4.1.6.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-08-02 11:56+0800\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language-Team: LANGUAGE <LL@li.org>\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.4.0\n" + +#: ../../ch-archive.rst:2 +msgid "The Debian Archive" +msgstr "" + +#: ../../ch-archive.rst:4 +msgid "" +"The Debian system is maintained and distributed as a collection of " +"*packages*. Since there are so many of them (currently well over 15000), " +"they are split into *sections* and given *priorities* to simplify the " +"handling of them." +msgstr "" + +#: ../../ch-archive.rst:9 +msgid "" +"The effort of the Debian project is to build a free operating system, but" +" not every package we want to make accessible is *free* in our sense (see" +" the Debian Free Software Guidelines, below), or may be imported/exported" +" without restrictions. Thus, the archive is split into areas [#]_ based " +"on their licenses and other restrictions." +msgstr "" + +#: ../../ch-archive.rst:15 +msgid "The aims of this are:" +msgstr "" + +#: ../../ch-archive.rst:17 +msgid "to allow us to make as much software available as we can" +msgstr "" + +#: ../../ch-archive.rst:19 +msgid "to allow us to encourage everyone to write free software, and" +msgstr "" + +#: ../../ch-archive.rst:21 +msgid "" +"to allow us to make it easy for people to produce CD-ROMs of our system " +"without violating any licenses, import/export restrictions, or any other " +"laws." +msgstr "" + +#: ../../ch-archive.rst:25 +msgid "The *main* archive area forms the *Debian distribution*." +msgstr "" + +#: ../../ch-archive.rst:27 +msgid "" +"Packages in the other archive areas (``contrib``, ``non-free``) are not " +"considered to be part of the Debian distribution, although we support " +"their use and provide infrastructure for them (such as our bug-tracking " +"system and mailing lists). This Debian Policy Manual applies to these " +"packages as well." +msgstr "" + +#: ../../ch-archive.rst:36 +msgid "The Debian Free Software Guidelines" +msgstr "" + +#: ../../ch-archive.rst:38 +msgid "" +"The Debian Free Software Guidelines (DFSG) form our definition of \"free " +"software\". These are:" +msgstr "" + +#: ../../ch-archive.rst:46 +msgid "Free Redistribution" +msgstr "" + +#: ../../ch-archive.rst:42 +msgid "" +"The license of a Debian component may not restrict any party from selling" +" or giving away the software as a component of an aggregate software " +"distribution containing programs from several different sources. The " +"license may not require a royalty or other fee for such sale." +msgstr "" + +#: ../../ch-archive.rst:50 +msgid "Source Code" +msgstr "" + +#: ../../ch-archive.rst:49 +msgid "" +"The program must include source code, and must allow distribution in " +"source code as well as compiled form." +msgstr "" + +#: ../../ch-archive.rst:55 +msgid "Derived Works" +msgstr "" + +#: ../../ch-archive.rst:53 +msgid "" +"The license must allow modifications and derived works, and must allow " +"them to be distributed under the same terms as the license of the " +"original software." +msgstr "" + +#: ../../ch-archive.rst:66 +msgid "Integrity of The Author's Source Code" +msgstr "" + +#: ../../ch-archive.rst:58 +msgid "" +"The license may restrict source-code from being distributed in modified " +"form *only* if the license allows the distribution of \"patch files\" " +"with the source code for the purpose of modifying the program at build " +"time. The license must explicitly permit distribution of software built " +"from modified source code. The license may require derived works to carry" +" a different name or version number from the original software. (This is " +"a compromise. The Debian Project encourages all authors to not restrict " +"any files, source or binary, from being modified.)" +msgstr "" + +#: ../../ch-archive.rst:70 +msgid "No Discrimination Against Persons or Groups" +msgstr "" + +#: ../../ch-archive.rst:69 +msgid "The license must not discriminate against any person or group of persons." +msgstr "" + +#: ../../ch-archive.rst:76 +msgid "No Discrimination Against Fields of Endeavor" +msgstr "" + +#: ../../ch-archive.rst:73 +msgid "" +"The license must not restrict anyone from making use of the program in a " +"specific field of endeavor. For example, it may not restrict the program " +"from being used in a business, or from being used for genetic research." +msgstr "" + +#: ../../ch-archive.rst:81 +msgid "Distribution of License" +msgstr "" + +#: ../../ch-archive.rst:79 +msgid "" +"The rights attached to the program must apply to all to whom the program " +"is redistributed without the need for execution of an additional license " +"by those parties." +msgstr "" + +#: ../../ch-archive.rst:89 +msgid "License Must Not Be Specific to Debian" +msgstr "" + +#: ../../ch-archive.rst:84 +msgid "" +"The rights attached to the program must not depend on the program's being" +" part of a Debian system. If the program is extracted from Debian and " +"used or distributed without Debian but otherwise within the terms of the " +"program's license, all parties to whom the program is redistributed must " +"have the same rights as those that are granted in conjunction with the " +"Debian system." +msgstr "" + +#: ../../ch-archive.rst:95 +msgid "License Must Not Contaminate Other Software" +msgstr "" + +#: ../../ch-archive.rst:92 +msgid "" +"The license must not place restrictions on other software that is " +"distributed along with the licensed software. For example, the license " +"must not insist that all other programs distributed on the same medium " +"must be free software." +msgstr "" + +#: ../../ch-archive.rst:97 +msgid "" +"Example Licenses The \"GPL,\" \"BSD,\" and \"Artistic\" licenses are " +"examples of licenses that we consider *free*." +msgstr "" + +#: ../../ch-archive.rst:104 +msgid "Archive areas" +msgstr "" + +#: ../../ch-archive.rst:109 +msgid "The main archive area" +msgstr "" + +#: ../../ch-archive.rst:111 +msgid "" +"The *main* archive area comprises the Debian distribution. Only the " +"packages in this area are considered part of the distribution. None of " +"the packages in the *main* archive area require software outside of that " +"area to function. Anyone may use, share, modify and redistribute the " +"packages in this archive area freely [#]_." +msgstr "" + +#: ../../ch-archive.rst:117 +msgid "" +"Every package in *main* must comply with the DFSG (Debian Free Software " +"Guidelines). [#]_" +msgstr "" + +#: ../../ch-archive.rst:120 +msgid "In addition, the packages in *main*" +msgstr "" + +#: ../../ch-archive.rst:122 +msgid "" +"must not require or recommend a package outside of *main* for compilation" +" or execution (thus, the package must not declare a ``Pre-Depends``, " +"``Depends``, ``Recommends``, ``Build-Depends``, ``Build-Depends-Indep``, " +"or ``Build-Depends-Arch`` relationship on a non-*main* package unless " +"that package is only listed as a non-default alternative for a package in" +" *main*)," +msgstr "" + +#: ../../ch-archive.rst:129 ../../ch-archive.rst:146 ../../ch-archive.rst:176 +msgid "must not be so buggy that we refuse to support them, and" +msgstr "" + +#: ../../ch-archive.rst:131 ../../ch-archive.rst:148 +msgid "must meet all policy requirements presented in this manual." +msgstr "" + +#: ../../ch-archive.rst:136 +msgid "The contrib archive area" +msgstr "" + +#: ../../ch-archive.rst:138 +msgid "" +"The *contrib* archive area contains supplemental packages intended to " +"work with the Debian distribution, but which require software outside of " +"the distribution to either build or function." +msgstr "" + +#: ../../ch-archive.rst:142 +msgid "Every package in *contrib* must comply with the DFSG." +msgstr "" + +#: ../../ch-archive.rst:144 +msgid "In addition, the packages in *contrib*" +msgstr "" + +#: ../../ch-archive.rst:150 +msgid "Examples of packages which would be included in *contrib* are:" +msgstr "" + +#: ../../ch-archive.rst:152 +msgid "" +"free packages which require *contrib*, *non-free* packages or packages " +"which are not in our archive at all for compilation or execution, and" +msgstr "" + +#: ../../ch-archive.rst:156 +msgid "wrapper packages or other sorts of free accessories for non-free programs." +msgstr "" + +#: ../../ch-archive.rst:162 +msgid "The non-free archive area" +msgstr "" + +#: ../../ch-archive.rst:164 +msgid "" +"The *non-free* archive area contains supplemental packages intended to " +"work with the Debian distribution that do not comply with the DFSG or " +"have other problems that make their distribution problematic. They may " +"not comply with all of the policy requirements in this manual due to " +"restrictions on modifications or other limitations." +msgstr "" + +#: ../../ch-archive.rst:170 +msgid "" +"Packages must be placed in *non-free* if they are not compliant with the " +"DFSG or are encumbered by patents or other legal issues that make their " +"distribution problematic." +msgstr "" + +#: ../../ch-archive.rst:174 +msgid "In addition, the packages in *non-free*" +msgstr "" + +#: ../../ch-archive.rst:178 +msgid "" +"must meet all policy requirements presented in this manual that it is " +"possible for them to meet. [#]_" +msgstr "" + +#: ../../ch-archive.rst:184 +msgid "Copyright considerations" +msgstr "" + +#: ../../ch-archive.rst:186 +msgid "" +"Every package must be accompanied by a verbatim copy of its copyright " +"information and distribution license in the file " +"``/usr/share/doc/package/copyright`` (see :ref:`s-copyrightfile` for " +"further details)." +msgstr "" + +#: ../../ch-archive.rst:191 +msgid "" +"We reserve the right to restrict files from being included anywhere in " +"our archives if" +msgstr "" + +#: ../../ch-archive.rst:194 +msgid "their use or distribution would break a law," +msgstr "" + +#: ../../ch-archive.rst:196 +msgid "there is an ethical conflict in their distribution or use," +msgstr "" + +#: ../../ch-archive.rst:198 +msgid "we would have to sign a license for them, or" +msgstr "" + +#: ../../ch-archive.rst:200 +msgid "their distribution would conflict with other project policies." +msgstr "" + +#: ../../ch-archive.rst:202 +msgid "" +"Programs whose authors encourage the user to make donations are fine for " +"the main distribution, provided that the authors do not claim that not " +"donating is immoral, unethical, illegal or something similar; in such a " +"case they must go in *non-free*." +msgstr "" + +#: ../../ch-archive.rst:207 +msgid "" +"Packages whose copyright permission notices (or patent problems) do not " +"even allow redistribution of binaries only, and where no special " +"permission has been obtained, must not be placed on the Debian FTP site " +"and its mirrors at all." +msgstr "" + +#: ../../ch-archive.rst:212 +msgid "" +"Note that under international copyright law (this applies in the United " +"States, too), *no* distribution or modification of a work is allowed " +"without an explicit notice saying so. Therefore a program without a " +"copyright notice *is* copyrighted and you may not do anything to it " +"without risking being sued! Likewise if a program has a copyright notice " +"but no statement saying what is permitted then nothing is permitted." +msgstr "" + +#: ../../ch-archive.rst:219 +msgid "" +"Many authors are unaware of the problems that restrictive copyrights (or " +"lack of copyright notices) can cause for the users of their supposedly-" +"free software. It is often worthwhile contacting such authors " +"diplomatically to ask them to modify their license terms. However, this " +"can be a politically difficult thing to do and you should ask for advice " +"on the ``debian-legal`` mailing list first, as explained below." +msgstr "" + +#: ../../ch-archive.rst:226 +msgid "" +"When in doubt about a copyright, send mail to debian-" +"legal@lists.debian.org. Be prepared to provide us with the copyright " +"statement. Software covered by the GPL, public domain software and BSD-" +"like copyrights are safe; be wary of the phrases \"commercial use " +"prohibited\" and \"distribution restricted\"." +msgstr "" + +#: ../../ch-archive.rst:235 +msgid "Sections" +msgstr "" + +#: ../../ch-archive.rst:237 +msgid "" +"The packages in the archive areas *main*, *contrib* and *non-free* are " +"grouped further into *sections* to simplify handling." +msgstr "" + +#: ../../ch-archive.rst:240 +msgid "" +"The archive area and section for each package should be specified in the " +"package's ``Section`` control record (see :ref:`s-f-Section`). However, " +"the maintainer of the Debian archive may override this selection to " +"ensure the consistency of the Debian distribution. The ``Section`` field " +"should be of the form:" +msgstr "" + +#: ../../ch-archive.rst:246 +msgid "*section* if the package is in the *main* archive area," +msgstr "" + +#: ../../ch-archive.rst:248 +msgid "" +"*area/section* if the package is in the *contrib* or *non-free* archive " +"areas." +msgstr "" + +#: ../../ch-archive.rst:251 +msgid "" +"The Debian archive maintainers provide the authoritative list of " +"sections. At present, they are: admin, cli-mono, comm, database, debug, " +"devel, doc, editors, education, electronics, embedded, fonts, games, " +"gnome, gnu-r, gnustep, graphics, hamradio, haskell, httpd, interpreters, " +"introspection, java, javascript, kde, kernel, libdevel, libs, lisp, " +"localization, mail, math, metapackages, misc, net, news, ocaml, oldlibs, " +"otherosfs, perl, php, python, ruby, rust, science, shells, sound, tasks, " +"tex, text, utils, vcs, video, web, x11, xfce, zope. The additional " +"section *debian-installer* contains special packages used by the " +"installer and is not used for normal Debian packages." +msgstr "" + +#: ../../ch-archive.rst:262 +msgid "" +"For more information about the sections and their definitions, see the " +"`list of sections in unstable <https://packages.debian.org/unstable/>`_." +msgstr "" + +#: ../../ch-archive.rst:269 +msgid "Priorities" +msgstr "" + +#: ../../ch-archive.rst:271 +msgid "" +"Each package must have a *priority* value, which is set in the metadata " +"for the Debian archive and is also included in the package's control " +"files (see :ref:`s-f-Priority`). This information is used to control " +"which packages are included in standard or minimal Debian installations." +msgstr "" + +#: ../../ch-archive.rst:277 +msgid "" +"Most Debian packages will have a priority of ``optional``. Priority " +"levels other than ``optional`` are only used for packages that should be " +"included by default in a standard installation of Debian." +msgstr "" + +#: ../../ch-archive.rst:281 +msgid "" +"The priority of a package is determined solely by the functionality it " +"provides directly to the user. The priority of a package should not be " +"increased merely because another higher-priority package depends on it; " +"instead, the tools used to construct Debian installations will correctly " +"handle package dependencies. In particular, this means that C-like " +"libraries will almost never have a priority above ``optional``, since " +"they do not provide functionality directly to users. However, as an " +"exception, the maintainers of Debian installers may request an increase " +"of the priority of a package to resolve installation issues and ensure " +"that the correct set of packages is included in a standard or minimal " +"install." +msgstr "" + +#: ../../ch-archive.rst:293 +msgid "" +"The following *priority levels* are recognized by the Debian package " +"management tools." +msgstr "" + +#: ../../ch-archive.rst:305 +msgid "``required``" +msgstr "" + +#: ../../ch-archive.rst:297 +msgid "" +"Packages which are necessary for the proper functioning of the system " +"(usually, this means that dpkg functionality depends on these packages). " +"Removing a ``required`` package may cause your system to become totally " +"broken and you may not even be able to use ``dpkg`` to put things back, " +"so only do so if you know what you are doing." +msgstr "" + +#: ../../ch-archive.rst:303 +msgid "" +"Systems with only the ``required`` packages installed have at least " +"enough functionality for the sysadmin to boot the system and install more" +" software." +msgstr "" + +#: ../../ch-archive.rst:316 +msgid "``important``" +msgstr "" + +#: ../../ch-archive.rst:308 +msgid "" +"Important programs, including those which one would expect to find on any" +" Unix-like system. If the expectation is that an experienced Unix person " +"who found it missing would say \"What on earth is going on, where is " +"``foo``?\", it must be an ``important`` package. [#]_ Other packages " +"without which the system will not run well or be usable must also have " +"priority ``important``. This does *not* include Emacs, the X Window " +"System, TeX or any other large applications. The ``important`` packages " +"are just a bare minimum of commonly-expected and necessary tools." +msgstr "" + +#: ../../ch-archive.rst:325 +msgid "``standard``" +msgstr "" + +#: ../../ch-archive.rst:319 +msgid "" +"These packages provide a reasonably small but not too limited character-" +"mode system. This is what will be installed by default if the user " +"doesn't select anything else. It doesn't include many large applications." +msgstr "" + +#: ../../ch-archive.rst:324 +msgid "" +"No two packages that both have a priority of ``standard`` or higher may " +"conflict with each other." +msgstr "" + +#: ../../ch-archive.rst:331 +msgid "``optional``" +msgstr "" + +#: ../../ch-archive.rst:328 +msgid "" +"This is the default priority for the majority of the archive. Unless a " +"package should be installed by default on standard Debian systems, it " +"should have a priority of ``optional``. Packages with a priority of " +"``optional`` may conflict with each other." +msgstr "" + +#: ../../ch-archive.rst:342 +msgid "``extra``" +msgstr "" + +#: ../../ch-archive.rst:334 +msgid "" +"*This priority is deprecated.* Use the ``optional`` priority instead. " +"This priority should be treated as equivalent to ``optional``." +msgstr "" + +#: ../../ch-archive.rst:338 +msgid "" +"The ``extra`` priority was previously used for packages that conflicted " +"with other packages and packages that were only likely to be useful to " +"people with specialized requirements. However, this distinction was " +"somewhat arbitrary, not consistently followed, and not useful enough to " +"warrant the maintenance effort." +msgstr "" + +#: ../../ch-archive.rst:345 +msgid "" +"The Debian archive software uses the term \"component\" internally and in" +" the Release file format to refer to the division of an archive. The " +"Debian Social Contract simply refers to \"areas.\" This document uses " +"terminology similar to the Social Contract." +msgstr "" + +#: ../../ch-archive.rst:351 +msgid "" +"See `What Does Free Mean? <https://www.debian.org/intro/free>`_ for more " +"about what we mean by free software." +msgstr "" + +#: ../../ch-archive.rst:355 +msgid "" +"Debian's FTP Masters publish a `REJECT-FAQ <https://ftp-master.debian.org" +"/REJECT-FAQ.html>`_ which details the project's current working " +"interpretation of the DFSG." +msgstr "" + +#: ../../ch-archive.rst:360 +msgid "" +"It is possible that there are policy requirements which the package is " +"unable to meet, for example, if the source is unavailable. These " +"situations will need to be handled on a case-by-case basis." +msgstr "" + +#: ../../ch-archive.rst:365 +msgid "" +"This is an important criterion because we are trying to produce, amongst " +"other things, a free Unix." +msgstr "" + diff --git a/locales/ja/LC_MESSAGES/ch-binary.po b/locales/ja/LC_MESSAGES/ch-binary.po new file mode 100644 index 0000000..311eb96 --- /dev/null +++ b/locales/ja/LC_MESSAGES/ch-binary.po @@ -0,0 +1,675 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1996, 1997, 1998 Ian Jackson, Christian Schwarz, 1998-2017, +# The Debian Policy Mailing List +# This file is distributed under the same license as the Debian Policy +# Manual package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2018. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Debian Policy Manual 4.1.6.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-08-02 11:56+0800\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language-Team: LANGUAGE <LL@li.org>\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.4.0\n" + +#: ../../ch-binary.rst:2 +msgid "Binary packages" +msgstr "" + +#: ../../ch-binary.rst:4 +msgid "" +"The Debian distribution is based on the Debian package management system," +" called ``dpkg``. Thus, all packages in the Debian distribution must be " +"provided in the ``.deb`` file format." +msgstr "" + +#: ../../ch-binary.rst:8 +msgid "" +"A ``.deb`` package contains two sets of files: a set of files to install " +"on the system when the package is installed, and a set of files that " +"provide additional metadata about the package or which are executed when " +"the package is installed or removed. This second set of files is called " +"*control information files*. Among those files are the package maintainer" +" scripts and ``control``, the :ref:`binary package control file " +"<s-binarycontrolfiles>` that contains the control fields for the package." +" Other control information files include :ref:`symbols <s-sharedlibs-" +"symbols>` or :ref:`shlibs <s-sharedlibs-shlibdeps>` used to store shared " +"library dependency information and the ``conffiles`` file that lists the " +"package's configuration files (described in :ref:`s-config-files`)." +msgstr "" + +#: ../../ch-binary.rst:21 +msgid "" +"There is unfortunately a collision of terminology here between control " +"information files and files in the Debian control file format. Throughout" +" this document, a *control file* refers to a file in the Debian control " +"file format. These files are documented in :doc:`Control files and their " +"fields <ch-controlfields>`. Only files referred to specifically as " +"*control information files* are the files included in the control " +"information file member of the ``.deb`` file format used by binary " +"packages. Most control information files are not in the Debian control " +"file format." +msgstr "" + +#: ../../ch-binary.rst:34 +msgid "The package name" +msgstr "" + +#: ../../ch-binary.rst:36 +msgid "Every package must have a name that's unique within the Debian archive." +msgstr "" + +#: ../../ch-binary.rst:38 +msgid "" +"The package name is included in the control field ``Package``, the format" +" of which is described in :ref:`s-f-Package`. The package name is also " +"included as a part of the file name of the ``.deb`` file." +msgstr "" + +#: ../../ch-binary.rst:46 +msgid "Packages with potentially offensive content" +msgstr "" + +#: ../../ch-binary.rst:48 +msgid "" +"As a maintainer you should make a judgement about whether the contents of" +" a package is appropriate to include, whether it needs any kind of " +"content warning, and whether some parts should be split out into a " +"separate package (so that users who want to avoid certain parts can do " +"so). In making these decisions you should take into account the " +"project's views as expressed in our Diversity Statement." +msgstr "" + +#: ../../ch-binary.rst:55 +msgid "" +"If you split out (potentially) offensive or disturbing material into a " +"separate package, you should usually mark this in the package name by " +"adding ``-offensive``. For example, ``cowsay`` vs ``cowsay-offensive``." +" In this situation the ``-offensive`` package can be Suggested by the " +"core package(s), but should not be Recommended or Depended on." +msgstr "" + +#: ../../ch-binary.rst:65 +msgid "The version of a package" +msgstr "" + +#: ../../ch-binary.rst:67 +msgid "" +"Every package has a version number recorded in its ``Version`` control " +"file field, described in :ref:`s-f-Version`." +msgstr "" + +#: ../../ch-binary.rst:70 +msgid "" +"The package management system imposes an ordering on version numbers, so " +"that it can tell whether packages are being up- or downgraded and so that" +" package system front end applications can tell whether a package it " +"finds available is newer than the one installed on the system. The " +"version number format has the most significant parts (as far as " +"comparison is concerned) at the beginning." +msgstr "" + +#: ../../ch-binary.rst:77 +msgid "" +"If an upstream package has problematic version numbers they should be " +"converted to a sane form for use in the ``Version`` field." +msgstr "" + +#: ../../ch-binary.rst:83 +msgid "Version numbers based on dates" +msgstr "" + +#: ../../ch-binary.rst:85 +msgid "" +"In general, Debian packages should use the same version numbers as the " +"upstream sources. However, upstream version numbers based on some date " +"formats (sometimes used for development or \"snapshot\" releases) will " +"not be ordered correctly by the package management software. For example," +" ``dpkg`` will consider \"96May01\" to be greater than \"96Dec24\"." +msgstr "" + +#: ../../ch-binary.rst:91 +msgid "" +"To prevent having to use epochs for every new upstream version, the date-" +"based portion of any upstream version number should be given in a way " +"that sorts correctly: four-digit year first, followed by a two-digit " +"numeric month, followed by a two-digit numeric date, possibly with " +"punctuation between the components." +msgstr "" + +#: ../../ch-binary.rst:97 +msgid "" +"Native Debian packages (i.e., packages which have been written especially" +" for Debian) whose version numbers include dates should also follow these" +" rules. If punctuation is desired between the date components, remember " +"that hyphen (``-``) cannot be used in native package versions. Period " +"(``.``) is normally a good choice." +msgstr "" + +#: ../../ch-binary.rst:106 +msgid "Uniqueness of version numbers" +msgstr "" + +#: ../../ch-binary.rst:108 +msgid "" +"The part of the version number after the epoch must not be reused for a " +"version of the package with different contents once the package has been " +"accepted into the archive, even if the version of the package previously " +"using that part of the version number is no longer present in any archive" +" suites." +msgstr "" + +#: ../../ch-binary.rst:114 +msgid "" +"This uniqueness requirement applies to the version numbers of source " +"packages and of binary packages, even if the source package producing a " +"given binary package changes. Thus the version numbers which a binary " +"package must not reuse includes the version numbers of any versions of " +"the binary package ever accepted into the archive, under any source " +"package." +msgstr "" + +#: ../../ch-binary.rst:121 +msgid "" +"Additionally, for non-native packages, the upstream version must not be " +"reused for different upstream source code, so that for each source " +"package name and upstream version number there exists exactly one " +"original source archive contents (see :ref:`s-f-Files`)." +msgstr "" + +#: ../../ch-binary.rst:126 +msgid "" +"The reason for these restrictions is as follows. Epochs are not included" +" in the names of the files that compose source packages, or in the " +"filenames of binary packages, so reusing a version number, even if the " +"epoch differs, results in identically named files with different " +"contents. This can cause various problems." +msgstr "" + +#: ../../ch-binary.rst:132 +msgid "" +"If you find yourself wanting to reuse the part of a version number after " +"the epoch, you can just increment the Debian revision, which doesn't need" +" to start at 1 or be consecutive." +msgstr "" + +#: ../../ch-binary.rst:139 +msgid "The maintainer of a package" +msgstr "" + +#: ../../ch-binary.rst:141 +msgid "" +"Every package must have a maintainer, except for orphaned packages as " +"described below. The maintainer may be one person or a group of people " +"reachable from a common email address, such as a mailing list. The " +"maintainer is responsible for maintaining the Debian packaging files, " +"evaluating and responding appropriately to reported bugs, uploading new " +"versions of the package (either directly or through a sponsor), ensuring " +"that the package is placed in the appropriate archive area and included " +"in Debian releases as appropriate for the stability and utility of the " +"package, and requesting removal of the package from the Debian " +"distribution if it is no longer useful or maintainable." +msgstr "" + +#: ../../ch-binary.rst:152 +msgid "" +"The maintainer must be specified in the ``Maintainer`` control field with" +" their correct name and a working email address. The email address given " +"in the ``Maintainer`` control field must accept mail from those role " +"accounts in Debian used to send automated mails regarding the package. " +"This includes non-spam mail from the bug-tracking system, all mail from " +"the Debian archive maintenance software, and other role accounts or " +"automated processes that are commonly agreed on by the project. [#]_ If " +"one person or team maintains several packages, they should use the same " +"form of their name and email address in the ``Maintainer`` fields of " +"those packages." +msgstr "" + +#: ../../ch-binary.rst:163 +msgid "" +"The format of the ``Maintainer`` control field is described in " +":ref:`s-f-Maintainer`." +msgstr "" + +#: ../../ch-binary.rst:166 +msgid "" +"If the maintainer of the package is a team of people with a shared email " +"address, the ``Uploaders`` control field must be present and must contain" +" at least one human with their personal email address. See " +":ref:`s-f-Uploaders` for the syntax of that field." +msgstr "" + +#: ../../ch-binary.rst:171 +msgid "" +"An orphaned package is one with no current maintainer. Orphaned packages " +"should have their ``Maintainer`` control field set to ``Debian QA Group " +"<packages@qa.debian.org>``. These packages are considered maintained by " +"the Debian project as a whole until someone else volunteers to take over " +"maintenance. [#]_" +msgstr "" + +#: ../../ch-binary.rst:179 +msgid "The description of a package" +msgstr "" + +#: ../../ch-binary.rst:181 +msgid "" +"Every Debian package must have a ``Description`` control field which " +"contains a synopsis and extended description of the package. Technical " +"information about the format of the ``Description`` field is in " +":ref:`s-f-Description`." +msgstr "" + +#: ../../ch-binary.rst:186 +msgid "" +"The description should describe the package (the program) to a user " +"(system administrator) who has never met it before so that they have " +"enough information to decide whether they want to install it. This " +"description should not just be copied verbatim from the program's " +"documentation." +msgstr "" + +#: ../../ch-binary.rst:192 +msgid "" +"Put important information first, both in the synopsis and extended " +"description. Sometimes only the first part of the synopsis or of the " +"description will be displayed. You can assume that there will usually be " +"a way to see the whole extended description." +msgstr "" + +#: ../../ch-binary.rst:197 +msgid "" +"The description should also give information about the significant " +"dependencies and conflicts between this package and others, so that the " +"user knows why these dependencies and conflicts have been declared." +msgstr "" + +#: ../../ch-binary.rst:201 +msgid "" +"Instructions for configuring or using the package should not be included " +"(that is what installation scripts, manual pages, info files, etc., are " +"for). Copyright statements and other administrivia should not be included" +" either (that is what the copyright file is for)." +msgstr "" + +#: ../../ch-binary.rst:209 +msgid "The single line synopsis" +msgstr "" + +#: ../../ch-binary.rst:211 +msgid "" +"The single line synopsis should be kept brief---certainly under 80 " +"characters." +msgstr "" + +#: ../../ch-binary.rst:214 +msgid "" +"Do not include the package name in the synopsis line. The display " +"software knows how to display this already, and you do not need to state " +"it. Remember that in many situations the user may only see the synopsis " +"line - make it as informative as you can." +msgstr "" + +#: ../../ch-binary.rst:222 +msgid "The extended description" +msgstr "" + +#: ../../ch-binary.rst:224 +msgid "" +"Do not try to continue the single line synopsis into the extended " +"description. This will not work correctly when the full description is " +"displayed, and makes no sense where only the summary (the single line " +"synopsis) is available." +msgstr "" + +#: ../../ch-binary.rst:229 +msgid "" +"The extended description should describe what the package does and how it" +" relates to the rest of the system (in terms of, for example, which " +"subsystem it is which part of)." +msgstr "" + +#: ../../ch-binary.rst:233 +msgid "" +"The description field needs to make sense to anyone, even people who have" +" no idea about any of the things the package deals with. [#]_" +msgstr "" + +#: ../../ch-binary.rst:239 +msgid "Dependencies" +msgstr "" + +#: ../../ch-binary.rst:241 +msgid "" +"Every package must specify the dependency information about other " +"packages that are required for the first to work correctly." +msgstr "" + +#: ../../ch-binary.rst:244 +msgid "" +"For example, a dependency entry must be provided for any shared libraries" +" required by a dynamically-linked executable binary in a package." +msgstr "" + +#: ../../ch-binary.rst:248 +msgid "" +"Packages are not required to declare any dependencies they have on other " +"packages which are marked ``Essential`` (see below), and should not do so" +" unless they depend on a particular version of that package. [#]_" +msgstr "" + +#: ../../ch-binary.rst:252 +msgid "" +"Sometimes, unpacking one package requires that another package be first " +"unpacked *and* configured. In this case, the depending package must " +"specify this dependency in the ``Pre-Depends`` control field." +msgstr "" + +#: ../../ch-binary.rst:256 +msgid "" +"You should not specify a ``Pre-Depends`` entry for a package before this " +"has been discussed on the ``debian-devel`` mailing list and a consensus " +"about doing that has been reached." +msgstr "" + +#: ../../ch-binary.rst:260 +msgid "" +"The format of the package interrelationship control fields is described " +"in :doc:`Declaring relationships between packages <ch-relationships>`." +msgstr "" + +#: ../../ch-binary.rst:266 +msgid "Virtual packages" +msgstr "" + +#: ../../ch-binary.rst:268 +msgid "" +"Sometimes, there are several packages which offer more-or-less the same " +"functionality. In this case, it's useful to define a *virtual package* " +"whose name describes that common functionality. (The virtual packages " +"only exist logically, not physically; that's why they are called " +"*virtual*.) The packages with this particular function will then " +"*provide* the virtual package. Thus, any other package requiring that " +"function can simply depend on the virtual package without having to " +"specify all possible packages individually." +msgstr "" + +#: ../../ch-binary.rst:277 +msgid "" +"All packages should use virtual package names where appropriate, and " +"arrange to create new ones if necessary. They should not use virtual " +"package names (except privately, amongst a cooperating group of packages)" +" unless they have been agreed upon and appear in the list of virtual " +"package names. (See also :ref:`s-virtual`)" +msgstr "" + +#: ../../ch-binary.rst:283 +msgid "" +"The latest version of the authoritative list of virtual package names can" +" be found in the ``debian-policy`` package. It is also available from the" +" Debian web mirrors at https://www.debian.org/doc/packaging-manuals" +"/virtual-package-names-list.txt." +msgstr "" + +#: ../../ch-binary.rst:288 +msgid "" +"The procedure for updating the list is described in the preface to the " +"list." +msgstr "" + +#: ../../ch-binary.rst:294 +msgid "Base system" +msgstr "" + +#: ../../ch-binary.rst:296 +msgid "" +"The ``base system`` is a minimum subset of the Debian system that is " +"installed before everything else on a new system. Only very few packages " +"are allowed to form part of the base system, in order to keep the " +"required disk usage very small." +msgstr "" + +#: ../../ch-binary.rst:301 +msgid "" +"The base system consists of all those packages with priority ``required``" +" or ``important``. Many of them will be tagged ``essential`` (see below)." +msgstr "" + +#: ../../ch-binary.rst:308 +msgid "Essential packages" +msgstr "" + +#: ../../ch-binary.rst:310 +msgid "" +"Essential is defined as the minimal set of functionality that must be " +"available and usable on the system at all times, even when packages are " +"in the \"Unpacked\" state. Packages are tagged ``essential`` for a system" +" using the ``Essential`` control field. The format of the ``Essential`` " +"control field is described in :ref:`s-f-Essential`." +msgstr "" + +#: ../../ch-binary.rst:316 +msgid "" +"Since these packages cannot be easily removed (one has to specify an " +"extra *force option* to ``dpkg`` to do so), this flag must not be used " +"unless absolutely necessary. A shared library package must not be tagged " +"``essential``; dependencies will prevent its premature removal, and we " +"need to be able to remove it when it has been superseded." +msgstr "" + +#: ../../ch-binary.rst:322 +msgid "" +"Since dpkg will not prevent upgrading of other packages while an " +"``essential`` package is in an unconfigured state, all ``essential`` " +"packages must supply all of their core functionality even when " +"unconfigured. If the package cannot satisfy this requirement it must not " +"be tagged as essential, and any packages depending on this package must " +"instead have explicit dependency fields as appropriate." +msgstr "" + +#: ../../ch-binary.rst:329 +msgid "" +"Maintainers should take great care in adding any programs, interfaces, or" +" functionality to ``essential`` packages. Packages may assume that " +"functionality provided by ``essential`` packages is always available " +"without declaring explicit dependencies, which means that removing " +"functionality from the Essential set is very difficult and is almost " +"never done. Any capability added to an ``essential`` package therefore " +"creates an obligation to support that capability as part of the Essential" +" set in perpetuity." +msgstr "" + +#: ../../ch-binary.rst:338 +msgid "" +"You must not tag any packages ``essential`` before this has been " +"discussed on the ``debian-devel`` mailing list and a consensus about " +"doing that has been reached." +msgstr "" + +#: ../../ch-binary.rst:345 +msgid "Maintainer Scripts" +msgstr "" + +#: ../../ch-binary.rst:347 +msgid "" +"The package installation scripts should avoid producing output which is " +"unnecessary for the user to see and should rely on ``dpkg`` to stave off " +"boredom on the part of a user installing many packages. This means, " +"amongst other things, not passing the ``--verbose`` option to ``update-" +"alternatives``." +msgstr "" + +#: ../../ch-binary.rst:353 +msgid "" +"Errors which occur during the execution of an installation script must be" +" checked and the installation must not continue after an error." +msgstr "" + +#: ../../ch-binary.rst:356 +msgid "" +"Note that in general :ref:`s-scripts` applies to package maintainer " +"scripts, too." +msgstr "" + +#: ../../ch-binary.rst:359 +msgid "" +"You should not use ``dpkg-divert`` on a file belonging to another package" +" without consulting the maintainer of that package first. When adding or " +"removing diversions, package maintainer scripts must provide the " +"``--package`` flag to ``dpkg-divert`` and must not use ``--local``." +msgstr "" + +#: ../../ch-binary.rst:364 +msgid "" +"All packages which supply an instance of a common command name (or, in " +"general, filename) should generally use ``update-alternatives``, so that " +"they may be installed together. If ``update-alternatives`` is not used, " +"then each package must use ``Conflicts`` to ensure that other packages " +"are removed. (In this case, it may be appropriate to specify a conflict " +"against earlier versions of something that previously did not use " +"``update-alternatives``; this is an exception to the usual rule that " +"versioned conflicts should be avoided.)" +msgstr "" + +#: ../../ch-binary.rst:376 +msgid "Prompting in maintainer scripts" +msgstr "" + +#: ../../ch-binary.rst:378 +msgid "" +"Package maintainer scripts may prompt the user if necessary. Prompting " +"must be done by communicating through a program, such as ``debconf``, " +"which conforms to the Debian Configuration Management Specification, " +"version 2 or higher." +msgstr "" + +#: ../../ch-binary.rst:383 +msgid "" +"Packages which are essential, or which are dependencies of essential " +"packages, may fall back on another prompting method if no such interface " +"is available when they are executed." +msgstr "" + +#: ../../ch-binary.rst:387 +msgid "" +"The Debian Configuration Management Specification is included in the " +"``debconf_specification`` files in the debian-policy package. It is also " +"available from the Debian web mirrors at https://www.debian.org/doc" +"/packaging-manuals/debconf_specification.html." +msgstr "" + +#: ../../ch-binary.rst:392 +msgid "" +"Packages which use the Debian Configuration Management Specification may " +"contain the additional control information files ``config`` and " +"``templates``. ``config`` is an additional maintainer script used for " +"package configuration, and ``templates`` contains templates used for user" +" prompting. The ``config`` script might be run before the ``preinst`` " +"script and before the package is unpacked or any of its dependencies or " +"pre-dependencies are satisfied. Therefore it must work using only the " +"tools present in *essential* packages. [#]_" +msgstr "" + +#: ../../ch-binary.rst:401 +msgid "" +"Packages which use the Debian Configuration Management Specification must" +" allow for translation of their user-visible messages by using a gettext-" +"based system such as the one provided by the po-debconf package." +msgstr "" + +#: ../../ch-binary.rst:405 +msgid "" +"Packages should try to minimize the amount of prompting they need to do, " +"and they should ensure that the user will only ever be asked each " +"question once. This means that packages should try to use appropriate " +"shared configuration files (such as ``/etc/papersize`` and " +"``/etc/news/server``), and shared debconf variables rather than each " +"prompting for their own list of required pieces of information." +msgstr "" + +#: ../../ch-binary.rst:412 +msgid "" +"It also means that an upgrade should not ask the same questions again, " +"unless the user has used ``dpkg --purge`` to remove the package's " +"configuration. The answers to configuration questions should be stored in" +" an appropriate place in ``/etc`` so that the user can modify them, and " +"how this has been done should be documented." +msgstr "" + +#: ../../ch-binary.rst:418 +msgid "" +"If a package has a vitally important piece of information to pass to the " +"user (such as \"don't run me as I am, you must edit the following " +"configuration files first or you risk your system emitting badly-" +"formatted messages\"), it should display this in the ``config`` or " +"``postinst`` script and prompt the user to hit return to acknowledge the " +"message. Copyright messages do not count as vitally important (they " +"belong in ``/usr/share/doc/package/copyright``); neither do instructions " +"on how to use a program (these should be in on-line documentation, where " +"all the users can see them)." +msgstr "" + +#: ../../ch-binary.rst:428 +msgid "" +"Any necessary prompting should almost always be confined to the " +"``config`` or ``postinst`` script. If it is done in the ``postinst``, it " +"should be protected with a conditional so that unnecessary prompting " +"doesn't happen if a package's installation fails and the ``postinst`` is " +"called with ``abort-upgrade``, ``abort-remove`` or ``abort-deconfigure``." +msgstr "" + +#: ../../ch-binary.rst:436 +msgid "" +"A sample implementation of such a whitelist written for the Mailman " +"mailing list management software is used for mailing lists hosted by " +"https://alioth-lists.debian.net/." +msgstr "" + +#: ../../ch-binary.rst:441 +msgid "" +"The detailed procedure for gracefully orphaning a package can be found in" +" the Debian Developer's Reference (see :ref:`s-related`)." +msgstr "" + +#: ../../ch-binary.rst:446 +msgid "" +"The blurb that comes with a program in its announcements and/or " +"``README`` files is rarely suitable for use in a description. It is " +"usually aimed at people who are already in the community where the " +"package is used." +msgstr "" + +#: ../../ch-binary.rst:452 +msgid "" +"Essential is needed in part to avoid unresolvable dependency loops on " +"upgrade. If packages add unnecessary dependencies on packages in this " +"set, the chances that there **will** be an unresolvable dependency loop " +"caused by forcing these Essential packages to be configured first before " +"they need to be is greatly increased. It also increases the chances that " +"frontends will be unable to **calculate** an upgrade path, even if one " +"exists." +msgstr "" + +#: ../../ch-binary.rst:460 +msgid "" +"Also, functionality is rarely ever removed from the Essential set, but " +"*packages* have been removed from the Essential set when the " +"functionality moved to a different package. So depending on these " +"packages *just in case* they stop being essential does way more harm than" +" good." +msgstr "" + +#: ../../ch-binary.rst:467 +msgid "" +"Debconf or another tool that implements the Debian Configuration " +"Management Specification will also be installed, and any versioned " +"dependencies on it will be satisfied before preconfiguration begins." +msgstr "" + diff --git a/locales/ja/LC_MESSAGES/ch-controlfields.po b/locales/ja/LC_MESSAGES/ch-controlfields.po new file mode 100644 index 0000000..6ed5444 --- /dev/null +++ b/locales/ja/LC_MESSAGES/ch-controlfields.po @@ -0,0 +1,1777 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1996, 1997, 1998 Ian Jackson, Christian Schwarz, 1998-2017, +# The Debian Policy Mailing List +# This file is distributed under the same license as the Debian Policy +# Manual package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2018. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Debian Policy Manual 4.1.6.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-08-02 11:56+0800\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language-Team: LANGUAGE <LL@li.org>\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.4.0\n" + +#: ../../ch-controlfields.rst:2 +msgid "Control files and their fields" +msgstr "" + +#: ../../ch-controlfields.rst:4 +msgid "" +"The package management system manipulates data represented in a common " +"format, known as *control data*, stored in *control files*. Control files" +" are used for source packages, binary packages and the ``.changes`` files" +" which control the installation of uploaded files. [#]_" +msgstr "" + +#: ../../ch-controlfields.rst:12 +msgid "Syntax of control files" +msgstr "" + +#: ../../ch-controlfields.rst:14 +msgid "" +"A control file consists of one or more paragraphs of fields. [#]_ The " +"paragraphs are separated by empty lines. Parsers may accept lines " +"consisting solely of spaces and tabs as paragraph separators, but control" +" files should use empty lines. Some control files allow only one " +"paragraph; others allow several, in which case each paragraph usually " +"refers to a different package. (For example, in source packages, the " +"first paragraph refers to the source package, and later paragraphs refer " +"to binary packages generated from the source.) The ordering of the " +"paragraphs in control files is significant." +msgstr "" + +#: ../../ch-controlfields.rst:24 +msgid "" +"Each paragraph consists of a series of data fields. Each field consists " +"of the field name followed by a colon and then the data/value associated " +"with that field. The field name is composed of US-ASCII characters " +"excluding control characters, space, and colon (i.e., characters in the " +"ranges U+0021 (``!``) through U+0039 (``9``), and U+003B (``;``) through " +"U+007E (``~``), inclusive). Field names must not begin with the comment " +"character (U+0023 ``#``), nor with the hyphen character (U+002D ``-``)." +msgstr "" + +#: ../../ch-controlfields.rst:32 +msgid "" +"The field ends at the end of the line or at the end of the last " +"continuation line (see below). Horizontal whitespace (spaces and tabs) " +"may occur immediately before or after the value and is ignored there; it " +"is conventional to put a single space after the colon. For example, a " +"field might be:" +msgstr "" + +#: ../../ch-controlfields.rst:42 +msgid "the field name is ``Package`` and the field value ``libc6``." +msgstr "" + +#: ../../ch-controlfields.rst:44 +msgid "" +"Empty field values are only permitted in source package control files " +"(``debian/control``). Such fields are ignored." +msgstr "" + +#: ../../ch-controlfields.rst:47 +msgid "" +"A paragraph must not contain more than one instance of a particular field" +" name." +msgstr "" + +#: ../../ch-controlfields.rst:50 +msgid "There are three types of fields:" +msgstr "" + +#: ../../ch-controlfields.rst:55 +msgid "simple" +msgstr "" + +#: ../../ch-controlfields.rst:53 +msgid "" +"The field, including its value, must be a single line. Folding of the " +"field is not permitted. This is the default field type if the definition " +"of the field does not specify a different type." +msgstr "" + +#: ../../ch-controlfields.rst:61 +msgid "folded" +msgstr "" + +#: ../../ch-controlfields.rst:58 +msgid "" +"The value of a folded field is a logical line that may span several " +"lines. The lines after the first are called continuation lines and must " +"start with a space or a tab. Whitespace, including any newlines, is not " +"significant in the field values of folded fields. [#]_" +msgstr "" + +#: ../../ch-controlfields.rst:69 +msgid "multiline" +msgstr "" + +#: ../../ch-controlfields.rst:64 +msgid "" +"The value of a multiline field may comprise multiple continuation lines. " +"The first line of the value, the part on the same line as the field name," +" often has special significance or may have to be empty. Other lines are " +"added following the same syntax as the continuation lines of the folded " +"fields. Whitespace, including newlines, is significant in the values of " +"multiline fields." +msgstr "" + +#: ../../ch-controlfields.rst:71 +msgid "" +"Whitespace must not appear inside names (of packages, architectures, " +"files or anything else) or version numbers, or between the characters of " +"multi-character version relationships." +msgstr "" + +#: ../../ch-controlfields.rst:75 +msgid "" +"The presence and purpose of a field, and the syntax of its value may " +"differ between types of control files." +msgstr "" + +#: ../../ch-controlfields.rst:78 +msgid "" +"Field names are not case-sensitive, but it is usual to capitalize the " +"field names using mixed case as shown below. Field values are case-" +"sensitive unless the description of the field says otherwise." +msgstr "" + +#: ../../ch-controlfields.rst:82 +msgid "" +"Paragraph separators (empty lines), and lines consisting only of U+0020 " +"SPACE and U+0009 TAB, are not allowed within field values or between " +"fields. Empty lines in field values are usually escaped by representing " +"them by a U+0020 SPACE followed by a U+002E (``.``)." +msgstr "" + +#: ../../ch-controlfields.rst:87 +msgid "" +"Lines starting with U+0023 (``#``), without any preceding whitespace, are" +" comment lines that are only permitted in source package control files " +"(``debian/control``). These comment lines are ignored, even between two " +"continuation lines. They do not end logical lines." +msgstr "" + +#: ../../ch-controlfields.rst:92 +msgid "All control files must be encoded in UTF-8." +msgstr "" + +#: ../../ch-controlfields.rst:97 +msgid "Source package control files -- ``debian/control``" +msgstr "" + +#: ../../ch-controlfields.rst:99 +msgid "" +"The ``debian/control`` file contains the most vital (and version-" +"independent) information about the source package and about the binary " +"packages it creates." +msgstr "" + +#: ../../ch-controlfields.rst:103 +msgid "" +"The first paragraph of the control file contains information about the " +"source package in general. The subsequent paragraphs each describe a " +"binary package that the source tree builds. Each binary package built " +"from this source package has a corresponding paragraph, except for any " +"automatically-generated debug packages that do not require one." +msgstr "" + +#: ../../ch-controlfields.rst:109 +msgid "" +"The fields in the general paragraph (the first one, for the source " +"package) are:" +msgstr "" + +#: ../../ch-controlfields.rst:112 ../../ch-controlfields.rst:221 +#: ../../ch-controlfields.rst:279 +msgid ":ref:`Source <s-f-Source>` (mandatory)" +msgstr "" + +#: ../../ch-controlfields.rst:114 ../../ch-controlfields.rst:202 +#: ../../ch-controlfields.rst:229 ../../ch-controlfields.rst:291 +msgid ":ref:`Maintainer <s-f-Maintainer>` (mandatory)" +msgstr "" + +#: ../../ch-controlfields.rst:116 ../../ch-controlfields.rst:231 +msgid ":ref:`Uploaders <s-f-Uploaders>`" +msgstr "" + +#: ../../ch-controlfields.rst:118 ../../ch-controlfields.rst:140 +#: ../../ch-controlfields.rst:190 +msgid ":ref:`Section <s-f-Section>` (recommended)" +msgstr "" + +#: ../../ch-controlfields.rst:120 ../../ch-controlfields.rst:142 +#: ../../ch-controlfields.rst:192 +msgid ":ref:`Priority <s-f-Priority>` (recommended)" +msgstr "" + +#: ../../ch-controlfields.rst:122 ../../ch-controlfields.rst:243 +msgid ":ref:`Build-Depends et al <s-sourcebinarydeps>`" +msgstr "" + +#: ../../ch-controlfields.rst:124 ../../ch-controlfields.rst:241 +msgid ":ref:`Standards-Version <s-f-Standards-Version>` (mandatory)" +msgstr "" + +#: ../../ch-controlfields.rst:126 ../../ch-controlfields.rst:150 +#: ../../ch-controlfields.rst:206 ../../ch-controlfields.rst:233 +msgid ":ref:`Homepage <s-f-Homepage>`" +msgstr "" + +#: ../../ch-controlfields.rst:128 ../../ch-controlfields.rst:235 +msgid ":ref:`Version Control System (VCS) fields <s-f-VCS-fields>`" +msgstr "" + +#: ../../ch-controlfields.rst:130 ../../ch-controlfields.rst:237 +msgid ":ref:`Testsuite <s-f-Testsuite>`" +msgstr "" + +#: ../../ch-controlfields.rst:132 +msgid ":ref:`Rules-Requires-Root <s-f-Rules-Requires-Root>`" +msgstr "" + +#: ../../ch-controlfields.rst:134 +msgid "The fields in the binary package paragraphs are:" +msgstr "" + +#: ../../ch-controlfields.rst:136 ../../ch-controlfields.rst:184 +msgid ":ref:`Package <s-f-Package>` (mandatory)" +msgstr "" + +#: ../../ch-controlfields.rst:138 ../../ch-controlfields.rst:194 +#: ../../ch-controlfields.rst:283 +msgid ":ref:`Architecture <s-f-Architecture>` (mandatory)" +msgstr "" + +#: ../../ch-controlfields.rst:144 ../../ch-controlfields.rst:196 +msgid ":ref:`Essential <s-f-Essential>`" +msgstr "" + +#: ../../ch-controlfields.rst:146 ../../ch-controlfields.rst:198 +msgid ":ref:`Depends et al <s-binarydeps>`" +msgstr "" + +#: ../../ch-controlfields.rst:148 ../../ch-controlfields.rst:204 +#: ../../ch-controlfields.rst:295 +msgid ":ref:`Description <s-f-Description>` (mandatory)" +msgstr "" + +#: ../../ch-controlfields.rst:152 ../../ch-controlfields.rst:208 +msgid ":ref:`Built-Using <s-built-using>`" +msgstr "" + +#: ../../ch-controlfields.rst:154 +msgid ":ref:`Package-Type <s-f-Package-Type>`" +msgstr "" + +#: ../../ch-controlfields.rst:156 +msgid "The syntax and semantics of the fields are described below." +msgstr "" + +#: ../../ch-controlfields.rst:158 +msgid "" +"These fields are used by ``dpkg-gencontrol`` to generate control files " +"for binary packages (see below), by ``dpkg-genchanges`` to generate the " +"``.changes`` file to accompany the upload, and by ``dpkg-source`` when it" +" creates the ``.dsc`` source control file as part of a source archive. " +"Some fields are folded in ``debian/control``, but not in any other " +"control file. These tools are responsible for removing the line breaks " +"from such fields when using fields from ``debian/control`` to generate " +"other control files. They are also responsible for discarding empty " +"fields." +msgstr "" + +#: ../../ch-controlfields.rst:168 +msgid "" +"The fields here may contain variable references - their values will be " +"substituted by ``dpkg-gencontrol``, ``dpkg-genchanges`` or ``dpkg-" +"source`` when they generate output control files. See :ref:`s-substvars` " +"for details." +msgstr "" + +#: ../../ch-controlfields.rst:176 +msgid "Binary package control files -- ``DEBIAN/control``" +msgstr "" + +#: ../../ch-controlfields.rst:178 +msgid "" +"The ``DEBIAN/control`` file contains the most vital (and version-" +"dependent) information about a binary package. It consists of a single " +"paragraph." +msgstr "" + +#: ../../ch-controlfields.rst:182 ../../ch-controlfields.rst:273 +msgid "The fields in this file are:" +msgstr "" + +#: ../../ch-controlfields.rst:186 +msgid ":ref:`Source <s-f-Source>`" +msgstr "" + +#: ../../ch-controlfields.rst:188 ../../ch-controlfields.rst:227 +#: ../../ch-controlfields.rst:285 +msgid ":ref:`Version <s-f-Version>` (mandatory)" +msgstr "" + +#: ../../ch-controlfields.rst:200 +msgid ":ref:`Installed-Size <s-f-Installed-Size>`" +msgstr "" + +#: ../../ch-controlfields.rst:213 +msgid "Debian source control files -- ``.dsc``" +msgstr "" + +#: ../../ch-controlfields.rst:215 +msgid "" +"This file consists of a single paragraph, possibly surrounded by a PGP " +"signature. The fields of that paragraph are listed below. Their syntax is" +" described above, in :ref:`s-controlsyntax`." +msgstr "" + +#: ../../ch-controlfields.rst:219 ../../ch-controlfields.rst:275 +msgid ":ref:`Format <s-f-Format>` (mandatory)" +msgstr "" + +#: ../../ch-controlfields.rst:223 +msgid ":ref:`Binary <s-f-Binary>`" +msgstr "" + +#: ../../ch-controlfields.rst:225 +msgid ":ref:`Architecture <s-f-Architecture>`" +msgstr "" + +#: ../../ch-controlfields.rst:239 +msgid ":ref:`Dgit <s-f-Dgit>`" +msgstr "" + +#: ../../ch-controlfields.rst:245 +msgid ":ref:`Package-List <s-f-Package-List>` (recommended)" +msgstr "" + +#: ../../ch-controlfields.rst:247 ../../ch-controlfields.rst:301 +msgid ":ref:`Checksums-Sha1 and Checksums-Sha256 <s-f-Checksums>` (mandatory)" +msgstr "" + +#: ../../ch-controlfields.rst:250 ../../ch-controlfields.rst:304 +msgid ":ref:`Files <s-f-Files>` (mandatory)" +msgstr "" + +#: ../../ch-controlfields.rst:252 +msgid "" +"The Debian source control file is generated by ``dpkg-source`` when it " +"builds the source archive, from other files in the source package, " +"described above. When unpacking, it is checked against the files and " +"directories in the other parts of the source package." +msgstr "" + +#: ../../ch-controlfields.rst:260 +msgid "Debian changes files -- ``.changes``" +msgstr "" + +#: ../../ch-controlfields.rst:262 +msgid "" +"The ``.changes`` files are used by the Debian archive maintenance " +"software to process updates to packages. They consist of a single " +"paragraph, possibly surrounded by a PGP signature. That paragraph " +"contains information from the ``debian/control`` file and other data " +"about the source package gathered via ``debian/changelog`` and " +"``debian/rules``." +msgstr "" + +#: ../../ch-controlfields.rst:269 +msgid "" +"``.changes`` files have a format version that is incremented whenever the" +" documented fields or their meaning change. This document describes " +"format 1.8." +msgstr "" + +#: ../../ch-controlfields.rst:277 +msgid ":ref:`Date <s-f-Date>` (mandatory)" +msgstr "" + +#: ../../ch-controlfields.rst:281 +msgid ":ref:`Binary <s-f-Binary>` (mandatory)" +msgstr "" + +#: ../../ch-controlfields.rst:287 +msgid ":ref:`Distribution <s-f-Distribution>` (mandatory)" +msgstr "" + +#: ../../ch-controlfields.rst:289 +msgid ":ref:`Urgency <s-f-Urgency>` (recommended)" +msgstr "" + +#: ../../ch-controlfields.rst:293 +msgid ":ref:`Changed-By <s-f-Changed-By>`" +msgstr "" + +#: ../../ch-controlfields.rst:297 +msgid ":ref:`Closes <s-f-Closes>`" +msgstr "" + +#: ../../ch-controlfields.rst:299 +msgid ":ref:`Changes <s-f-Changes>` (mandatory)" +msgstr "" + +#: ../../ch-controlfields.rst:309 +msgid "List of fields" +msgstr "" + +#: ../../ch-controlfields.rst:314 +msgid "``Source``" +msgstr "" + +#: ../../ch-controlfields.rst:316 +msgid "This field identifies the source package name." +msgstr "" + +#: ../../ch-controlfields.rst:318 +msgid "" +"In ``debian/control`` or a ``.dsc`` file, this field must contain only " +"the name of the source package." +msgstr "" + +#: ../../ch-controlfields.rst:321 +msgid "" +"In a binary package control file or a ``.changes`` file, the source " +"package name may be followed by a version number in parentheses. [#]_ " +"This version number may be omitted (and is, by ``dpkg-gencontrol``) if it" +" has the same value as the ``Version`` field of the binary package in " +"question. The field itself may be omitted from a binary package control " +"file when the source package has the same name and version as the binary " +"package." +msgstr "" + +#: ../../ch-controlfields.rst:329 +msgid "" +"Package names (both source and binary, see :ref:`s-f-Package`) must " +"consist only of lower case letters (``a-z``), digits (``0-9``), plus " +"(``+``) and minus (``-``) signs, and periods (``.``). They must be at " +"least two characters long and must start with an alphanumeric character." +msgstr "" + +#: ../../ch-controlfields.rst:338 +msgid "``Maintainer``" +msgstr "" + +#: ../../ch-controlfields.rst:340 +msgid "" +"The package maintainer's name and email address. The name must come " +"first, then the email address inside angle brackets ``<>`` (in RFC822 " +"format)." +msgstr "" + +#: ../../ch-controlfields.rst:344 +msgid "" +"If the maintainer's name contains a full stop then the whole field will " +"not work directly as an email address due to a misfeature in the syntax " +"specified in RFC822; a program using this field as an address must check " +"for this and correct the problem if necessary (for example by putting the" +" name in round brackets and moving it to the end, and bringing the email " +"address forward)." +msgstr "" + +#: ../../ch-controlfields.rst:351 +msgid "" +"See :ref:`s-maintainer` for additional requirements and information about" +" package maintainers." +msgstr "" + +#: ../../ch-controlfields.rst:357 +msgid "``Uploaders``" +msgstr "" + +#: ../../ch-controlfields.rst:359 +msgid "" +"List of the names and email addresses of co-maintainers of the package, " +"if any. If the package has other maintainers besides the one named in the" +" :ref:`Maintainer field <s-f-Maintainer>`, their names and email " +"addresses should be listed here. The format of each entry is the same as " +"that of the Maintainer field, and multiple entries must be comma " +"separated." +msgstr "" + +#: ../../ch-controlfields.rst:366 +msgid "" +"This is normally an optional field, but if the ``Maintainer`` control " +"field names a group of people and a shared email address, the " +"``Uploaders`` field must be present and must contain at least one human " +"with their personal email address." +msgstr "" + +#: ../../ch-controlfields.rst:371 +msgid "The Uploaders field in ``debian/control`` can be folded." +msgstr "" + +#: ../../ch-controlfields.rst:376 +msgid "``Changed-By``" +msgstr "" + +#: ../../ch-controlfields.rst:378 +msgid "" +"The name and email address of the person who prepared this version of the" +" package, usually a maintainer. The syntax is the same as for the " +":ref:`Maintainer field <s-f-Maintainer>`." +msgstr "" + +#: ../../ch-controlfields.rst:385 +msgid "``Section``" +msgstr "" + +#: ../../ch-controlfields.rst:387 +msgid "" +"This field specifies an application area into which the package has been " +"classified. See :ref:`s-subsections`." +msgstr "" + +#: ../../ch-controlfields.rst:390 ../../ch-controlfields.rst:403 +msgid "" +"When it appears in the ``debian/control`` file, it gives the value for " +"the subfield of the same name in the ``Files`` field of the ``.changes`` " +"file. It also gives the default for the same field in the binary " +"packages." +msgstr "" + +#: ../../ch-controlfields.rst:398 +msgid "``Priority``" +msgstr "" + +#: ../../ch-controlfields.rst:400 +msgid "" +"This field represents how important it is that the user have the package " +"installed. See :ref:`s-priorities`." +msgstr "" + +#: ../../ch-controlfields.rst:411 +msgid "``Package``" +msgstr "" + +#: ../../ch-controlfields.rst:413 +msgid "The name of the binary package." +msgstr "" + +#: ../../ch-controlfields.rst:415 +msgid "" +"Binary package names must follow the same syntax and restrictions as " +"source package names. See :ref:`s-f-Source` for the details." +msgstr "" + +#: ../../ch-controlfields.rst:422 +msgid "``Architecture``" +msgstr "" + +#: ../../ch-controlfields.rst:424 +msgid "" +"Depending on context and the control file used, the ``Architecture`` " +"field can include the following sets of values:" +msgstr "" + +#: ../../ch-controlfields.rst:427 +msgid "" +"A unique single word identifying a Debian machine architecture as " +"described in :ref:`s-arch-spec`." +msgstr "" + +#: ../../ch-controlfields.rst:430 +msgid "" +"An architecture wildcard identifying a set of Debian machine " +"architectures, see :ref:`s-arch-wildcard-spec`. ``any`` matches all " +"Debian machine architectures and is the most frequently used." +msgstr "" + +#: ../../ch-controlfields.rst:435 +msgid "``all``, which indicates an architecture-independent package." +msgstr "" + +#: ../../ch-controlfields.rst:437 +msgid "``source``, which indicates a source package." +msgstr "" + +#: ../../ch-controlfields.rst:439 +msgid "" +"In the main ``debian/control`` file in the source package, this field may" +" contain the special value ``all``, the special architecture wildcard " +"``any``, or a list of specific and wildcard architectures separated by " +"spaces. If ``all`` or ``any`` appears, that value must be the entire " +"contents of the field. Most packages will use either ``all`` or ``any``." +msgstr "" + +#: ../../ch-controlfields.rst:445 +msgid "" +"Specifying a specific list of architectures indicates that the source " +"will build an architecture-dependent package only on architectures " +"included in the list. Specifying a list of architecture wildcards " +"indicates that the source will build an architecture-dependent package on" +" only those architectures that match any of the specified architecture " +"wildcards. Specifying a list of architectures or architecture wildcards " +"other than ``any`` is for the minority of cases where a program is not " +"portable or is not useful on some architectures. Where possible, the " +"program should be made portable instead." +msgstr "" + +#: ../../ch-controlfields.rst:455 +msgid "" +"In the Debian source control file ``.dsc``, this field contains a list of" +" architectures and architecture wildcards separated by spaces. When the " +"list contains the architecture wildcard ``any``, the only other value " +"allowed in the list is ``all``." +msgstr "" + +#: ../../ch-controlfields.rst:460 +msgid "" +"The list may include (or consist solely of) the special value ``all``. In" +" other words, in ``.dsc`` files unlike the ``debian/control``, ``all`` " +"may occur in combination with specific architectures. The " +"``Architecture`` field in the Debian source control file ``.dsc`` is " +"generally constructed from the ``Architecture`` fields in the " +"``debian/control`` in the source package." +msgstr "" + +#: ../../ch-controlfields.rst:467 +msgid "" +"Specifying only ``any`` indicates that the source package isn't dependent" +" on any particular architecture and should compile fine on any one. The " +"produced binary package(s) will be specific to whatever the current build" +" architecture is." +msgstr "" + +#: ../../ch-controlfields.rst:472 +msgid "" +"Specifying only ``all`` indicates that the source package will only build" +" architecture-independent packages." +msgstr "" + +#: ../../ch-controlfields.rst:475 +msgid "" +"Specifying ``any all`` indicates that the source package isn't dependent " +"on any particular architecture. The set of produced binary packages will " +"include at least one architecture-dependent package and one architecture-" +"independent package." +msgstr "" + +#: ../../ch-controlfields.rst:480 +msgid "" +"Specifying a list of architectures or architecture wildcards indicates " +"that the source will build an architecture-dependent package, and will " +"only work correctly on the listed or matching architectures. If the " +"source package also builds at least one architecture-independent package," +" ``all`` will also be included in the list." +msgstr "" + +#: ../../ch-controlfields.rst:486 +msgid "" +"In a ``.changes`` file, the ``Architecture`` field lists the " +"architecture(s) of the package(s) currently being uploaded. This will be " +"a list; if the source for the package is also being uploaded, the special" +" entry ``source`` is also present. ``all`` will be present if any " +"architecture-independent packages are being uploaded. Architecture " +"wildcards such as ``any`` must never occur in the ``Architecture`` field " +"in the ``.changes`` file." +msgstr "" + +#: ../../ch-controlfields.rst:494 +msgid "" +"See :ref:`s-debianrules` for information on how to get the architecture " +"for the build process." +msgstr "" + +#: ../../ch-controlfields.rst:500 +msgid "``Essential``" +msgstr "" + +#: ../../ch-controlfields.rst:502 +msgid "" +"This is a boolean field which may occur only in the control file of a " +"binary package or in a per-package fields paragraph of a source package " +"control file." +msgstr "" + +#: ../../ch-controlfields.rst:506 +msgid "" +"If set to ``yes`` then the package management system will refuse to " +"remove the package (upgrading and replacing it is still possible). The " +"other possible value is ``no``, which is the same as not having the field" +" at all." +msgstr "" + +#: ../../ch-controlfields.rst:514 +msgid "" +"Package interrelationship fields: ``Depends``, ``Pre-Depends``, " +"``Recommends``, ``Suggests``, ``Breaks``, ``Conflicts``, ``Provides``, " +"``Replaces``, ``Enhances``" +msgstr "" + +#: ../../ch-controlfields.rst:516 +msgid "" +"These fields describe the package's relationships with other packages. " +"Their syntax and semantics are described in :doc:`Declaring relationships" +" between packages <ch-relationships>`." +msgstr "" + +#: ../../ch-controlfields.rst:523 +msgid "``Standards-Version``" +msgstr "" + +#: ../../ch-controlfields.rst:525 +msgid "" +"The most recent version of the standards (the policy manual and " +"associated texts) with which the package complies. See " +":ref:`s-standardsversion`." +msgstr "" + +#: ../../ch-controlfields.rst:529 +msgid "" +"The version number has four components: major and minor version number " +"and major and minor patch level. When the standards change in a way that " +"requires every package to change the major number will be changed. " +"Significant changes that will require work in many packages will be " +"signaled by a change to the minor number. The major patch level will be " +"changed for any change to the meaning of the standards, however small; " +"the minor patch level will be changed when only cosmetic, typographical " +"or other edits are made which neither change the meaning of the document " +"nor affect the contents of packages." +msgstr "" + +#: ../../ch-controlfields.rst:539 +msgid "" +"Thus only the first three components of the policy version are " +"significant in the *Standards-Version* control field, and so either these" +" three components or all four components may be specified. [#]_" +msgstr "" + +#: ../../ch-controlfields.rst:546 +msgid "``Version``" +msgstr "" + +#: ../../ch-controlfields.rst:548 +msgid "" +"The version number of a package. The format is: " +"``[epoch:]upstream_version[-debian_revision]``." +msgstr "" + +#: ../../ch-controlfields.rst:551 +msgid "The three components here are:" +msgstr "" + +#: ../../ch-controlfields.rst:561 +msgid "``epoch``" +msgstr "" + +#: ../../ch-controlfields.rst:554 +msgid "" +"This is a single (generally small) unsigned integer. It may be omitted, " +"in which case zero is assumed. If it is omitted then the " +"``upstream_version`` may not contain any colons." +msgstr "" + +#: ../../ch-controlfields.rst:558 +msgid "" +"Epochs can help when the upstream version numbering scheme changes, but " +"they must be used with care. You should not change the epoch, even in " +"experimental, without getting consensus on debian-devel first." +msgstr "" + +#: ../../ch-controlfields.rst:578 +msgid "``upstream_version``" +msgstr "" + +#: ../../ch-controlfields.rst:564 +msgid "" +"This is the main part of the version number. It is usually the version " +"number of the original (\"upstream\") package from which the ``.deb`` " +"file has been made, if this is applicable. Usually this will be in the " +"same format as that specified by the upstream author(s); however, it may " +"need to be reformatted to fit into the package management system's format" +" and comparison scheme." +msgstr "" + +#: ../../ch-controlfields.rst:571 +msgid "" +"The comparison behavior of the package management system with respect to " +"the ``upstream_version`` is described below. The ``upstream_version`` " +"portion of the version number is mandatory." +msgstr "" + +#: ../../ch-controlfields.rst:575 +msgid "" +"The ``upstream_version`` may contain only alphanumerics [#]_ and the " +"characters ``.`` ``+`` ``-`` ``~`` (full stop, plus, hyphen, tilde) and " +"should start with a digit. If there is no ``debian_revision`` then " +"hyphens are not allowed." +msgstr "" + +#: ../../ch-controlfields.rst:599 +msgid "``debian_revision`` This part of the version number specifies the" +msgstr "" + +#: ../../ch-controlfields.rst:581 +msgid "" +"version of the Debian package based on the upstream version. It may " +"contain only alphanumerics and the characters ``+`` ``.`` ``~`` (plus, " +"full stop, tilde) and is compared in the same way as the " +"``upstream_version`` is." +msgstr "" + +#: ../../ch-controlfields.rst:586 +msgid "" +"It is optional; if it isn't present then the ``upstream_version`` may not" +" contain a hyphen. This format represents the case where a piece of " +"software was written specifically to be a Debian package, where the " +"Debian package source must always be identical to the pristine source and" +" therefore no revision indication is required." +msgstr "" + +#: ../../ch-controlfields.rst:592 +msgid "" +"It is conventional to restart the ``debian_revision`` at ``1`` each time " +"the ``upstream_version`` is increased." +msgstr "" + +#: ../../ch-controlfields.rst:595 +msgid "" +"The package management system will break the version number apart at the " +"last hyphen in the string (if there is one) to determine the " +"``upstream_version`` and ``debian_revision``. The absence of a " +"``debian_revision`` is equivalent to a ``debian_revision`` of ``0``." +msgstr "" + +#: ../../ch-controlfields.rst:601 +msgid "" +"When comparing two version numbers, first the epoch of each are compared," +" then the ``upstream_version`` if epoch is equal, and then " +"``debian_revision`` if ``upstream_version`` is also equal. epoch is " +"compared numerically. The ``upstream_version`` and ``debian_revision`` " +"parts are compared by the package management system using the following " +"algorithm:" +msgstr "" + +#: ../../ch-controlfields.rst:607 +msgid "The strings are compared from left to right." +msgstr "" + +#: ../../ch-controlfields.rst:609 +msgid "" +"First the initial part of each string consisting entirely of non-digit " +"characters is determined. These two parts (one of which may be empty) are" +" compared lexically. If a difference is found it is returned. The lexical" +" comparison is a comparison of ASCII values modified so that all the " +"letters sort earlier than all the non-letters and so that a tilde sorts " +"before anything, even the end of a part. For example, the following parts" +" are in sorted order from earliest to latest: ``~~``, ``~~a``, ``~``, the" +" empty part, ``a``. [#]_" +msgstr "" + +#: ../../ch-controlfields.rst:618 +msgid "" +"Then the initial part of the remainder of each string which consists " +"entirely of digit characters is determined. The numerical values of these" +" two parts are compared, and any difference found is returned as the " +"result of the comparison. For these purposes an empty string (which can " +"only occur at the end of one or both version strings being compared) " +"counts as zero." +msgstr "" + +#: ../../ch-controlfields.rst:625 +msgid "" +"These two steps (comparing and removing initial non-digit strings and " +"initial digit strings) are repeated until a difference is found or both " +"strings are exhausted." +msgstr "" + +#: ../../ch-controlfields.rst:630 +msgid "Epochs should be used sparingly" +msgstr "" + +#: ../../ch-controlfields.rst:632 +msgid "" +"Note that the purpose of epochs is to cope with situations where the " +"upstream version numbering scheme changes and to allow us to leave behind" +" serious mistakes. If you think that increasing the epoch is the right " +"solution, you should consult debian-devel and get consensus before doing " +"so (even in experimental)." +msgstr "" + +#: ../../ch-controlfields.rst:639 +msgid "" +"Epochs should not be used when a package needs to be rolled back. In that" +" case, use the ``+really`` convention: for example, if you uploaded " +"``2.3-3`` and now you need to go backwards to upstream 2.2, call your " +"reverting upload something like ``2.3+really2.2-1``. Eventually, when we " +"upload upstream 2.4, the +really part can go away." +msgstr "" + +#: ../../ch-controlfields.rst:645 +msgid "" +"Epochs are also not intended to cope with version numbers containing " +"strings of letters which the package management system cannot interpret " +"(such as ``ALPHA`` or ``pre-``), or with silly orderings. [#]_" +msgstr "" + +#: ../../ch-controlfields.rst:653 +msgid "``Description``" +msgstr "" + +#: ../../ch-controlfields.rst:655 +msgid "" +"In a source or binary control file, the ``Description`` field contains a " +"description of the binary package, consisting of two parts, the synopsis " +"or the short description, and the long description. It is a multiline " +"field with the following format:" +msgstr "" + +#: ../../ch-controlfields.rst:665 +msgid "The lines in the extended description can have these formats:" +msgstr "" + +#: ../../ch-controlfields.rst:667 +msgid "" +"Those starting with a single space are part of a paragraph. Successive " +"lines of this form will be word-wrapped when displayed. The leading space" +" will usually be stripped off. The line must contain at least one non-" +"whitespace character." +msgstr "" + +#: ../../ch-controlfields.rst:672 +msgid "" +"Those starting with two or more spaces. These will be displayed verbatim." +" If the display cannot be panned horizontally, the displaying program " +"will line wrap them \"hard\" (i.e., without taking account of word " +"breaks). If it can they will be allowed to trail off to the right. None, " +"one or two initial spaces may be deleted, but the number of spaces " +"deleted from each line will be the same (so that you can have indenting " +"work correctly, for example). The line must contain at least one non-" +"whitespace character." +msgstr "" + +#: ../../ch-controlfields.rst:681 +msgid "" +"Those containing a single space followed by a single full stop character." +" These are rendered as blank lines. This is the *only* way to get a blank" +" line. [#]_" +msgstr "" + +#: ../../ch-controlfields.rst:685 +msgid "" +"Those containing a space, a full stop and some more characters. These are" +" for future expansion. Do not use them." +msgstr "" + +#: ../../ch-controlfields.rst:688 +msgid "Do not use tab characters. Their effect is not predictable." +msgstr "" + +#: ../../ch-controlfields.rst:690 +msgid "See :ref:`s-descriptions` for further information on this." +msgstr "" + +#: ../../ch-controlfields.rst:693 +msgid "" +"In a ``.changes`` file, the ``Description`` field contains a summary of " +"the descriptions for the packages being uploaded. For this case, the " +"first line of the field value (the part on the same line as " +"``Description:``) is always empty. It is a multiline field, with one line" +" per package. Each line is indented by one space and contains the name of" +" a binary package, a space, a hyphen (``-``), a space, and the short " +"description line from that package." +msgstr "" + +#: ../../ch-controlfields.rst:704 +msgid "``Distribution``" +msgstr "" + +#: ../../ch-controlfields.rst:706 +msgid "" +"In a ``.changes`` file or parsed changelog output this contains the " +"(space-separated) name(s) of the distribution(s) where this version of " +"the package should be installed. Valid distributions are determined by " +"the archive maintainers. [#]_ The Debian archive software only supports " +"listing a single distribution. Migration of packages to other " +"distributions is handled outside of the upload process." +msgstr "" + +#: ../../ch-controlfields.rst:716 +msgid "``Date``" +msgstr "" + +#: ../../ch-controlfields.rst:718 +msgid "" +"This field includes the date the package was built or last edited. It " +"must be in the same format as the date in a ``debian/changelog`` entry." +msgstr "" + +#: ../../ch-controlfields.rst:721 +msgid "" +"The value of this field is usually extracted from the " +"``debian/changelog`` file - see :ref:`s-dpkgchangelog`)." +msgstr "" + +#: ../../ch-controlfields.rst:727 +msgid "``Format``" +msgstr "" + +#: ../../ch-controlfields.rst:729 +msgid "" +"In |changes link|_ files, this field declares the format version of that " +"file. The syntax of the field value is the same as that of a " +":ref:`package version number <s-f-Version>` except that no epoch or " +"Debian revision is allowed. The format described in this document is 1.8." +msgstr "" + +#: ../../ch-controlfields.rst:735 +msgid "" +"In |dsc link|_ files, this field declares the format of the source " +"package. The field value is used by programs acting on a source package " +"to interpret the list of files in the source package and determine how to" +" unpack it. The syntax of the field value is a numeric major revision, a " +"period, a numeric minor revision, and then an optional subtype after " +"whitespace, which if specified is an alphanumeric word in parentheses. " +"The subtype is optional in the syntax but may be mandatory for particular" +" source format revisions. [#]_" +msgstr "" + +#: ../../ch-controlfields.rst:753 +msgid "``Urgency``" +msgstr "" + +#: ../../ch-controlfields.rst:755 +msgid "" +"This is a description of how important it is to upgrade to this version " +"from previous ones. It consists of a single keyword taking one of the " +"values ``low``, ``medium``, ``high``, ``emergency``, or ``critical`` [#]_" +" (not case-sensitive) followed by an optional commentary (separated by a " +"space) which is usually in parentheses. For example:" +msgstr "" + +#: ../../ch-controlfields.rst:765 ../../ch-controlfields.rst:782 +msgid "" +"The value of this field is usually extracted from the " +"``debian/changelog`` file - see :ref:`s-dpkgchangelog`." +msgstr "" + +#: ../../ch-controlfields.rst:771 +msgid "``Changes``" +msgstr "" + +#: ../../ch-controlfields.rst:773 +msgid "" +"This multiline field contains the human-readable changes data, describing" +" the differences between the last version and the current one." +msgstr "" + +#: ../../ch-controlfields.rst:776 +msgid "" +"The first line of the field value (the part on the same line as " +"``Changes:``) is always empty. The content of the field is expressed as " +"continuation lines, with each line indented by at least one space. Blank " +"lines must be represented by a line consisting only of a space and a full" +" stop (``.``)." +msgstr "" + +#: ../../ch-controlfields.rst:785 +msgid "" +"Each version's change information should be preceded by a \"title\" line " +"giving at least the version, distribution(s) and urgency, in a human-" +"readable way." +msgstr "" + +#: ../../ch-controlfields.rst:789 +msgid "" +"If data from several versions is being returned the entry for the most " +"recent version should be returned first, and entries should be separated " +"by the representation of a blank line (the \"title\" line may also be " +"followed by the representation of a blank line)." +msgstr "" + +#: ../../ch-controlfields.rst:797 +msgid "``Binary``" +msgstr "" + +#: ../../ch-controlfields.rst:799 +msgid "" +"This folded field is a list of binary packages. Its syntax and meaning " +"varies depending on the control file in which it appears." +msgstr "" + +#: ../../ch-controlfields.rst:802 +msgid "" +"When it appears in the ``.dsc`` file, it lists binary packages which a " +"source package can produce, separated by commas [#]_. The source package " +"does not necessarily produce all of these binary packages for every " +"architecture. The source control file doesn't contain details of which " +"architectures are appropriate for which of the binary packages." +msgstr "" + +#: ../../ch-controlfields.rst:808 +msgid "" +"When it appears in a ``.changes`` file, it lists the names of the binary " +"packages being uploaded, separated by whitespace (not commas)." +msgstr "" + +#: ../../ch-controlfields.rst:814 +msgid "``Installed-Size``" +msgstr "" + +#: ../../ch-controlfields.rst:816 +msgid "" +"This field appears in the control files of binary packages, and in the " +"``Packages`` files. It gives an estimate of the total amount of disk " +"space required to install the named package. Actual installed size may " +"vary based on block size, file system properties, or actions taken by " +"package maintainer scripts." +msgstr "" + +#: ../../ch-controlfields.rst:822 +msgid "" +"The disk space is given as the integer value of the estimated installed " +"size in bytes, divided by 1024 and rounded up." +msgstr "" + +#: ../../ch-controlfields.rst:828 +msgid "``Files``" +msgstr "" + +#: ../../ch-controlfields.rst:830 +msgid "" +"This field contains a list of files with information about each one. The " +"exact information and syntax varies with the context." +msgstr "" + +#: ../../ch-controlfields.rst:833 +msgid "" +"In all cases, Files is a multiline field. The first line of the field " +"value (the part on the same line as ``Files:``) is always empty. The " +"content of the field is expressed as continuation lines, one line per " +"file. Each line must be indented by one space and contain a number of " +"sub-fields, separated by spaces, as described below." +msgstr "" + +#: ../../ch-controlfields.rst:839 +msgid "" +"In the ``.dsc`` file, each line contains the MD5 checksum, size and " +"filename of the tar file and (if applicable) diff file which make up the " +"remainder of the source package. [#]_ For example:" +msgstr "" + +#: ../../ch-controlfields.rst:849 +msgid "" +"The exact forms of the filenames are described in :ref:`s-pkg-" +"sourcearchives`." +msgstr "" + +#: ../../ch-controlfields.rst:852 +msgid "" +"In the ``.changes`` file this contains one line per file being uploaded. " +"Each line contains the MD5 checksum, size, section and priority and the " +"filename. For example:" +msgstr "" + +#: ../../ch-controlfields.rst:864 +msgid "" +"The :ref:`section <s-f-Section>` and :ref:`priority <s-f-Priority>` are " +"the values of the corresponding fields in the main source control file. " +"If no section or priority is specified then ``-`` should be used, though " +"section and priority values must be specified for new packages to be " +"installed properly." +msgstr "" + +#: ../../ch-controlfields.rst:870 +msgid "" +"The special value ``byhand`` for the section in a ``.changes`` file " +"indicates that the file in question is not an ordinary package file and " +"must be installed by hand by the distribution maintainers. If the section" +" is ``byhand`` the priority should be ``-``." +msgstr "" + +#: ../../ch-controlfields.rst:875 +msgid "" +"If a new Debian revision of a package is being shipped and no new " +"original source archive is being distributed the ``.dsc`` must still " +"contain the ``Files`` field entry for the original source archive " +"``package_upstream-version.orig.tar.gz``, but the ``.changes`` file " +"should leave it out. In this case the original source archive on the " +"distribution site must match exactly, byte-for-byte, the original source " +"archive which was used to generate the ``.dsc`` file and diff which are " +"being uploaded." +msgstr "" + +#: ../../ch-controlfields.rst:887 +msgid "``Closes``" +msgstr "" + +#: ../../ch-controlfields.rst:889 +msgid "" +"A space-separated list of bug report numbers that the upload governed by " +"the .changes file closes." +msgstr "" + +#: ../../ch-controlfields.rst:895 +msgid "``Homepage``" +msgstr "" + +#: ../../ch-controlfields.rst:897 +msgid "" +"The URL of the web site for this package, preferably (when applicable) " +"the site from which the original source can be obtained and any " +"additional upstream documentation or information may be found. The " +"content of this field is a simple URL without any surrounding characters " +"such as ``<>``." +msgstr "" + +#: ../../ch-controlfields.rst:906 +msgid "``Checksums-Sha1`` and ``Checksums-Sha256``" +msgstr "" + +#: ../../ch-controlfields.rst:908 +msgid "" +"These multiline fields contain a list of files with a checksum and size " +"for each one. Both ``Checksums-Sha1`` and ``Checksums-Sha256`` have the " +"same syntax and differ only in the checksum algorithm used: SHA-1 for " +"``Checksums-Sha1`` and SHA-256 for ``Checksums-Sha256``." +msgstr "" + +#: ../../ch-controlfields.rst:913 +msgid "" +"``Checksums-Sha1`` and ``Checksums-Sha256`` are multiline fields. The " +"first line of the field value (the part on the same line as ``Checksums-" +"Sha1:`` or ``Checksums-Sha256:``) is always empty. The content of the " +"field is expressed as continuation lines, one line per file. Each line " +"consists of the checksum, a space, the file size, a space, and the file " +"name. For example (from a ``.changes`` file):" +msgstr "" + +#: ../../ch-controlfields.rst:933 +msgid "" +"In the ``.dsc`` file, these fields list all files that make up the source" +" package. In the ``.changes`` file, these fields list all files being " +"uploaded. The list of files in these fields must match the list of files " +"in the ``Files`` field." +msgstr "" + +#: ../../ch-controlfields.rst:941 ../../ch-controlfields.rst:1197 +msgid "``DM-Upload-Allowed``" +msgstr "" + +#: ../../ch-controlfields.rst:943 +msgid "Obsolete, see :ref:`below <s-f-DM-Upload-Allowed>`." +msgstr "" + +#: ../../ch-controlfields.rst:948 +msgid "Version Control System (VCS) fields" +msgstr "" + +#: ../../ch-controlfields.rst:950 +msgid "" +"Debian source packages are increasingly developed using VCSs. The purpose" +" of the following fields is to indicate a publicly accessible repository " +"where the Debian source package is developed." +msgstr "" + +#: ../../ch-controlfields.rst:955 +msgid "``Vcs-Browser``" +msgstr "" + +#: ../../ch-controlfields.rst:955 +msgid "URL of a web interface for browsing the repository." +msgstr "" + +#: ../../ch-controlfields.rst:981 +msgid "``Vcs-<type>``" +msgstr "" + +#: ../../ch-controlfields.rst:958 +msgid "" +"The field name identifies the VCS. The field's value uses the version " +"control system's conventional syntax for describing repository locations " +"and should be sufficient to locate the repository used for packaging. " +"Ideally, it also locates the branch used for development of new versions " +"of the Debian package." +msgstr "" + +#: ../../ch-controlfields.rst:964 +msgid "" +"The following values for <type> are supported, with the corresponding VCS" +" indicated in parentheses if it isn't obvious:" +msgstr "" + +#: ../../ch-controlfields.rst:967 +msgid "Arch" +msgstr "" + +#: ../../ch-controlfields.rst:968 +msgid "Bzr (Bazaar)" +msgstr "" + +#: ../../ch-controlfields.rst:969 +msgid "Cvs (CVS)" +msgstr "" + +#: ../../ch-controlfields.rst:970 +msgid "Darcs" +msgstr "" + +#: ../../ch-controlfields.rst:971 +msgid "Git" +msgstr "" + +#: ../../ch-controlfields.rst:972 +msgid "Hg (Mercurial)" +msgstr "" + +#: ../../ch-controlfields.rst:973 +msgid "Mtn (Monotone)" +msgstr "" + +#: ../../ch-controlfields.rst:974 +msgid "Svn (Subversion)" +msgstr "" + +#: ../../ch-controlfields.rst:976 +msgid "" +"In the case of Git, the value consists of a URL, optionally followed by " +"the word ``-b`` and the name of a branch in the indicated repository, " +"following the syntax of the ``git clone`` command. If no branch is " +"specified, the packaging should be on the default branch." +msgstr "" + +#: ../../ch-controlfields.rst:981 +msgid "More than one different VCS may be specified for the same package." +msgstr "" + +#: ../../ch-controlfields.rst:983 +msgid "" +"For both fields, any URLs given should use a scheme that provides " +"confidentiality (``https``, for example, rather than ``http`` or ``git``)" +" if the VCS repository supports it." +msgstr "" + +#: ../../ch-controlfields.rst:990 +msgid "``Package-List``" +msgstr "" + +#: ../../ch-controlfields.rst:992 +msgid "" +"Multiline field listing all the packages that can be built from the " +"source package, considering every architecture. The first line of the " +"field value is empty. Each one of the next lines describes one binary " +"package, by listing its name, type, section and priority separated by " +"spaces. Fifth and subsequent space-separated items may be present and " +"parsers must allow them. See the :ref:`Package-Type <s-f-Package-Type>` " +"field for a list of package types." +msgstr "" + +#: ../../ch-controlfields.rst:1003 +msgid "``Package-Type``" +msgstr "" + +#: ../../ch-controlfields.rst:1005 +msgid "" +"Simple field containing a word indicating the type of package: ``deb`` " +"for binary packages and ``udeb`` for micro binary packages. Other types " +"not defined here may be indicated. In source package control files, the " +"``Package-Type`` field should be omitted instead of giving it a value of " +"``deb``, as this value is assumed for paragraphs lacking this field." +msgstr "" + +#: ../../ch-controlfields.rst:1014 +msgid "``Dgit``" +msgstr "" + +#: ../../ch-controlfields.rst:1016 +msgid "" +"Folded field containing a single git commit hash, presented in full, " +"followed optionally by whitespace and other data to be defined in future " +"extensions." +msgstr "" + +#: ../../ch-controlfields.rst:1020 +msgid "" +"Declares that the source package corresponds exactly to a referenced " +"commit in a Git repository available at the canonical location called " +"*dgit-repos*, used by ``dgit``, a bidirectional gateway between the " +"Debian archive and Git. The commit is reachable from at least one " +"reference whose name matches ``refs/dgit/*``. See the manual page of " +"``dgit`` for further details." +msgstr "" + +#: ../../ch-controlfields.rst:1030 +msgid "``Testsuite``" +msgstr "" + +#: ../../ch-controlfields.rst:1032 +msgid "" +"Simple field containing a comma-separated list of values allowing test " +"execution environments to discover packages which provide tests." +msgstr "" + +#: ../../ch-controlfields.rst:1035 +msgid "" +"This field is automatically added to Debian source control files " +"(``.dsc``) by ``dpkg``, with the value ``autopkgtest``, when a " +"``debian/tests/control`` file is present in the source package. This " +"field may also be used in source package control files " +"(``debian/control``) if needed in other situations." +msgstr "" + +#: ../../ch-controlfields.rst:1044 +msgid "``Rules-Requires-Root``" +msgstr "" + +#: ../../ch-controlfields.rst:1046 +msgid "" +"Simple field that defines if the source package requires access to root " +"(or fakeroot) during selected targets in the :ref:`Main building script: " +"debian/rules <s-debianrules>`." +msgstr "" + +#: ../../ch-controlfields.rst:1050 +msgid "The field can consist of exactly one of the following three items:" +msgstr "" + +#: ../../ch-controlfields.rst:1052 +msgid "" +"``no``: Declares that neither root nor fakeroot is required. Package " +"builders (e.g. dpkg-buildpackage) may choose to invoke any target in " +"``debian/rules`` with an unprivileged user." +msgstr "" + +#: ../../ch-controlfields.rst:1056 +msgid "" +"``binary-targets`` (default): Declares that the package will need the " +"root (or fakeroot) when either of the ``binary``, ``binary-arch`` or " +"``binary-indep`` targets are called. This is how every tool behaved " +"before this field was defined." +msgstr "" + +#: ../../ch-controlfields.rst:1061 +msgid "" +"A space separated list of keywords described below. These keywords must " +"always contain a forward slash, which sets them apart from the other " +"possible values of ``Rules-Requires-Root``. When this list is provided, " +"the builder must provide a `gain root command` (as defined in " +":ref:`debian/rules and Rules-Requires-Root <s-debianrules-gainrootapi>`) " +"*or* pretend that the value was set to ``binary-targets``, and both the " +"builder and the package's ``debian/rules`` script must downgrade " +"accordingly (see below)." +msgstr "" + +#: ../../ch-controlfields.rst:1070 +msgid "" +"If the package builder supports the ``Rules-Requires-Root`` field and " +"wants to enable the feature, then it must set the environment variable " +"``DEB_RULES_REQUIRES_ROOT`` when invoking the package building script " +"``debian/rules``. The value of ``DEB_RULES_REQUIRES_ROOT`` should be one" +" of:" +msgstr "" + +#: ../../ch-controlfields.rst:1076 +msgid "" +"The value of ``Rules-Requires-Root`` if the builder can support that " +"value. The builder may trim unnecessary whitespace used to format the " +"field for readability." +msgstr "" + +#: ../../ch-controlfields.rst:1080 +msgid "" +"The value ``binary-targets`` if it cannot support the value of ``Rules-" +"Requires-Root``." +msgstr "" + +#: ../../ch-controlfields.rst:1083 +msgid "" +"A compliant builder may also leave ``DEB_RULES_REQUIRES_ROOT`` unset or " +"set it to ``binary-targets`` if it has been requested to test whether the" +" package it builds correctly implements the fall-back for legacy " +"builders." +msgstr "" + +#: ../../ch-controlfields.rst:1089 +msgid "Remarks" +msgstr "" + +#: ../../ch-controlfields.rst:1091 +msgid "" +"All packages and builders must support ``binary-targets`` as this was the" +" historical behaviour prior to the introduction of this field." +msgstr "" + +#: ../../ch-controlfields.rst:1094 +msgid "" +"Any tool (particularly older versions of them) may be unaware of this " +"field and behave like the field was set to ``binary-targets``. The " +"package build must gracefully cope with this and produce a semantically " +"equivalent result." +msgstr "" + +#: ../../ch-controlfields.rst:1099 +msgid "" +"This field intentionally does not enable a package to request a true root" +" over fakeroot." +msgstr "" + +#: ../../ch-controlfields.rst:1103 +msgid "Definition of the keywords" +msgstr "" + +#: ../../ch-controlfields.rst:1105 +msgid "The keywords have the format ``<namespace>/<case>``, where:" +msgstr "" + +#: ../../ch-controlfields.rst:1107 +msgid "" +"``<namespace>`` must consist entirely of printable ASCII characters " +"except for any whitespace and the forward slash (``/``). It must consist" +" of at least 2 characters." +msgstr "" + +#: ../../ch-controlfields.rst:1111 +msgid "" +"``/`` (between ``<namespace>`` and ``<case>``) is a single ASCII forward " +"slash." +msgstr "" + +#: ../../ch-controlfields.rst:1114 +msgid "" +"``<case>`` must consist entirely of printable ASCII characters except for" +" any whitespace. It must consist of at least 2 characters." +msgstr "" + +#: ../../ch-controlfields.rst:1118 +msgid "" +"These keywords define where the package build script ``debian/rules``, or" +" the tools called by that script, will need access to root or fakeroot." +msgstr "" + +#: ../../ch-controlfields.rst:1122 +msgid "" +"In addition to the keywords defined in the next section, each tool or " +"package may define keywords within a namespace named after that tool or " +"package. The package or tool is considered to own that namespace." +msgstr "" + +#: ../../ch-controlfields.rst:1126 +msgid "" +"A tool may use the `gain root command` to do something under (fake)root " +"if and only if the tool defines an appropriate keyword in its namespace, " +"and the package lists that keyword in ``Rules-Requires-Root``." +msgstr "" + +#: ../../ch-controlfields.rst:1131 +msgid "" +"All tools must ignore keywords under namespaces they do not know or own." +" A tool may emit a warning, or abort with an error, if it finds unknown " +"keywords in namespaces it owns, but it is not required to do this for all" +" keywords in the namespace." +msgstr "" + +#: ../../ch-controlfields.rst:1137 +msgid "Provided keywords" +msgstr "" + +#: ../../ch-controlfields.rst:1139 +msgid "The following keywords are defined:" +msgstr "" + +#: ../../ch-controlfields.rst:1141 +msgid "" +"``dpkg/target-subcommand``: declares that there exists a command that the" +" ``debian/rules`` file must run under (fake)root" +msgstr "" + +#: ../../ch-controlfields.rst:1144 +msgid "" +"``dpkg/target/foo``: declares that the additional, package-specific " +"target ``foo`` (that is, not one of the targets specified in :ref:`Main " +"building script: debian/rules <s-debianrules>`) must be run under " +"(fake)root" +msgstr "" + +#: ../../ch-controlfields.rst:1149 +msgid "" +"This list is intentionally incomplete. You should consult the " +"documentation of the tool or package in question for which keywords it " +"defines and when they are needed." +msgstr "" + +#: ../../ch-controlfields.rst:1156 +msgid "User-defined fields" +msgstr "" + +#: ../../ch-controlfields.rst:1158 +msgid "" +"Additional user-defined fields may be added to the source package control" +" file. Such fields will be ignored, and not copied to (for example) " +"binary or Debian source control files or upload control files." +msgstr "" + +#: ../../ch-controlfields.rst:1162 +msgid "" +"If you wish to add additional unsupported fields to these output files " +"you should use the mechanism described here." +msgstr "" + +#: ../../ch-controlfields.rst:1165 +msgid "" +"Fields in the main source control information file with names starting " +"``X``, followed by one or more of the letters ``BCS`` and a hyphen ``-``," +" will be copied to the output files. Only the part of the field name " +"after the hyphen will be used in the output file. Where the letter ``B`` " +"is used the field will appear in binary package control files, where the " +"letter ``S`` is used in Debian source control files and where ``C`` is " +"used in upload control (``.changes``) files." +msgstr "" + +#: ../../ch-controlfields.rst:1173 +msgid "" +"For example, if the main source information control file contains the " +"field" +msgstr "" + +#: ../../ch-controlfields.rst:1180 +msgid "then the binary and Debian source control files will contain the field" +msgstr "" + +#: ../../ch-controlfields.rst:1189 +msgid "Obsolete fields" +msgstr "" + +#: ../../ch-controlfields.rst:1191 +msgid "" +"The following fields have been obsoleted and may be found in packages " +"conforming with previous versions of the Policy." +msgstr "" + +#: ../../ch-controlfields.rst:1199 +msgid "" +"Indicates that Debian Maintainers may upload this package to the Debian " +"archive. The only valid value is ``yes``. This field was used to regulate" +" uploads by Debian Maintainers, See the General Resolution `Endorse the " +"concept of Debian Maintainers " +"<https://www.debian.org/vote/2007/vote_003>`_ for more details." +msgstr "" + +#: ../../ch-controlfields.rst:1207 +msgid "``dpkg``'s internal databases are in a similar format." +msgstr "" + +#: ../../ch-controlfields.rst:1210 +msgid "The paragraphs are also sometimes referred to as stanzas." +msgstr "" + +#: ../../ch-controlfields.rst:1213 +msgid "" +"This folding method is similar to RFC 5322, allowing control files that " +"contain only one paragraph and no multiline fields to be read by parsers " +"written for RFC 5322." +msgstr "" + +#: ../../ch-controlfields.rst:1218 +msgid "" +"It is customary to leave a space after the package name if a version " +"number is specified." +msgstr "" + +#: ../../ch-controlfields.rst:1222 +msgid "" +"In the past, people specified the full version number in the Standards-" +"Version field, for example \"2.3.0.0\". Since minor patch-level changes " +"don't introduce new policy, it was thought it would be better to relax " +"policy and only require the first 3 components to be specified, in this " +"example \"2.3.0\". All four components may still be used if someone " +"wishes to do so." +msgstr "" + +#: ../../ch-controlfields.rst:1230 +msgid "Alphanumerics are ``A-Za-z0-9`` only." +msgstr "" + +#: ../../ch-controlfields.rst:1233 +msgid "" +"One common use of ``~`` is for upstream pre-releases. For example, " +"``1.0~beta1~svn1245`` sorts earlier than ``1.0~beta1``, which sorts " +"earlier than ``1.0``." +msgstr "" + +#: ../../ch-controlfields.rst:1238 +msgid "" +"The author of this manual has heard of a package whose versions went " +"``1.1``, ``1.2``, ``1.3``, ``1``, ``2.1``, ``2.2``, ``2`` and so forth." +msgstr "" + +#: ../../ch-controlfields.rst:1243 +msgid "" +"Completely empty lines will not be rendered as blank lines. Instead, they" +" will cause the parser to think you're starting a whole new record in the" +" control file, and will therefore likely abort with an error." +msgstr "" + +#: ../../ch-controlfields.rst:1249 +msgid "" +"Example distribution names in the Debian archive used in ``.changes`` " +"files are:" +msgstr "" + +#: ../../ch-controlfields.rst:1256 +msgid "*unstable*" +msgstr "" + +#: ../../ch-controlfields.rst:1253 +msgid "" +"This distribution value refers to the *developmental* part of the Debian " +"distribution tree. Most new packages, new upstream versions of packages " +"and bug fixes go into the *unstable* directory tree." +msgstr "" + +#: ../../ch-controlfields.rst:1263 +msgid "*experimental*" +msgstr "" + +#: ../../ch-controlfields.rst:1259 +msgid "" +"The packages with this distribution value are deemed by their maintainers" +" to be high risk. Oftentimes they represent early beta or developmental " +"packages from various sources that the maintainers want people to try, " +"but are not ready to be a part of the other parts of the Debian " +"distribution tree." +msgstr "" + +#: ../../ch-controlfields.rst:1265 +msgid "" +"Others are used for updating stable releases or for security uploads. " +"More information is available in the Debian Developer's Reference, " +"section \"The Debian archive\"." +msgstr "" + +#: ../../ch-controlfields.rst:1270 +msgid "" +"The source formats currently supported by the Debian archive software are" +" ``1.0``, ``3.0 (native)``, and ``3.0 (quilt)``." +msgstr "" + +#: ../../ch-controlfields.rst:1274 +msgid "" +"Other urgency values are supported with configuration changes in the " +"archive software but are not used in Debian. The urgency affects how " +"quickly a package will be considered for inclusion into the ``testing`` " +"distribution and gives an indication of the importance of any fixes " +"included in the upload. ``Emergency`` and ``critical`` are treated as " +"synonymous." +msgstr "" + +#: ../../ch-controlfields.rst:1282 +msgid "A space after each comma is conventional." +msgstr "" + +#: ../../ch-controlfields.rst:1285 +msgid "That is, the parts which are not the ``.dsc``." +msgstr "" + diff --git a/locales/ja/LC_MESSAGES/ch-customized-programs.po b/locales/ja/LC_MESSAGES/ch-customized-programs.po new file mode 100644 index 0000000..5d318f0 --- /dev/null +++ b/locales/ja/LC_MESSAGES/ch-customized-programs.po @@ -0,0 +1,871 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1996, 1997, 1998 Ian Jackson, Christian Schwarz, 1998-2017, +# The Debian Policy Mailing List +# This file is distributed under the same license as the Debian Policy +# Manual package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2018. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Debian Policy Manual 4.1.6.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-08-02 11:56+0800\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language-Team: LANGUAGE <LL@li.org>\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.4.0\n" + +#: ../../ch-customized-programs.rst:2 +msgid "Customized programs" +msgstr "" + +#: ../../ch-customized-programs.rst:7 +msgid "Architecture specification strings" +msgstr "" + +#: ../../ch-customized-programs.rst:9 +msgid "" +"If a program needs to specify an *architecture specification string* in " +"some place, it should select one of the strings provided by ``dpkg-" +"architecture -L``. The strings are in the format ``os-arch``, though the " +"OS part is sometimes elided, as when the OS is Linux." +msgstr "" + +#: ../../ch-customized-programs.rst:14 +msgid "" +"Note that we don't want to use ``arch-debian-linux`` to apply to the rule" +" ``architecture-vendor-os`` since this would make our programs " +"incompatible with other Linux distributions. We also don't use something " +"like ``arch-unknown-linux``, since the ``unknown`` does not look very " +"good." +msgstr "" + +#: ../../ch-customized-programs.rst:23 +msgid "Architecture wildcards" +msgstr "" + +#: ../../ch-customized-programs.rst:25 +msgid "" +"A package may specify an architecture wildcard. Architecture wildcards " +"are in the format ``any`` (which matches every architecture), ``os``-any," +" or any-\\ ``cpu``. [#]_" +msgstr "" + +#: ../../ch-customized-programs.rst:32 +msgid "Daemons" +msgstr "" + +#: ../../ch-customized-programs.rst:34 +msgid "" +"The configuration files ``/etc/services``, ``/etc/protocols``, and " +"``/etc/rpc`` are managed by the ``netbase`` package and must not be " +"modified by other packages." +msgstr "" + +#: ../../ch-customized-programs.rst:38 +msgid "" +"If a package requires a new entry in one of these files, the maintainer " +"should get in contact with the ``netbase`` maintainer, who will add the " +"entries and release a new version of the ``netbase`` package." +msgstr "" + +#: ../../ch-customized-programs.rst:42 +msgid "" +"The configuration file ``/etc/inetd.conf`` must not be modified by the " +"package's scripts except via the ``update-inetd`` script or the " +"``DebianNet.pm`` Perl module. See their documentation for details on how " +"to add entries." +msgstr "" + +#: ../../ch-customized-programs.rst:47 +msgid "" +"If a package wants to install an example entry into ``/etc/inetd.conf``, " +"the entry must be preceded with exactly one hash character (``#``). Such " +"lines are treated as \"commented out by user\" by the ``update-inetd`` " +"script and are not changed or activated during package updates." +msgstr "" + +#: ../../ch-customized-programs.rst:55 +msgid "Using pseudo-ttys and modifying wtmp, utmp and lastlog" +msgstr "" + +#: ../../ch-customized-programs.rst:57 +msgid "" +"Some programs need to create pseudo-ttys. This should be done using " +"Unix98 ptys if the C library supports it. The resulting program must not " +"be installed setuid root, unless that is required for other " +"functionality." +msgstr "" + +#: ../../ch-customized-programs.rst:62 +msgid "" +"The files ``/var/run/utmp``, ``/var/log/wtmp`` and ``/var/log/lastlog`` " +"must be installed writable by group ``utmp``. Programs which need to " +"modify those files must be installed setgid ``utmp``." +msgstr "" + +#: ../../ch-customized-programs.rst:69 +msgid "Editors and pagers" +msgstr "" + +#: ../../ch-customized-programs.rst:71 +msgid "" +"Some programs have the ability to launch an editor or pager program to " +"edit or display a text document. Since there are lots of different " +"editors and pagers available in the Debian distribution, the system " +"administrator and each user should have the possibility to choose their " +"preferred editor and pager." +msgstr "" + +#: ../../ch-customized-programs.rst:77 +msgid "" +"In addition, every program should choose a good default editor/pager if " +"none is selected by the user or system administrator." +msgstr "" + +#: ../../ch-customized-programs.rst:80 +msgid "" +"Thus, every program that launches an editor or pager must use the EDITOR " +"or PAGER environment variable to determine the editor or pager the user " +"wishes to use. If these variables are not set, the programs " +"``/usr/bin/editor`` and ``/usr/bin/pager`` should be used, respectively. " +"These commands may be invoked explicitly (e.g., as ``/usr/bin/editor``) " +"or via a PATH search (e.g., as ``editor``)." +msgstr "" + +#: ../../ch-customized-programs.rst:87 +msgid "" +"These two files are managed through the ``dpkg`` \"alternatives\" " +"mechanism. Every package providing an editor or pager must call the " +"``update-alternatives`` script to register as an alternative for " +"``/usr/bin/editor`` or ``/usr/bin/pager`` as appropriate. The alternative" +" should have a slave alternative for ``/usr/share/man/man1/editor.1.gz`` " +"or ``/usr/share/man/man1/pager.1.gz`` pointing to the corresponding " +"manual page." +msgstr "" + +#: ../../ch-customized-programs.rst:96 +msgid "" +"If it is very hard to adapt a program to make use of the EDITOR or PAGER " +"variables, that program may be configured to use ``/usr/bin/sensible-" +"editor`` and ``/usr/bin/sensible-pager`` as the editor or pager program " +"respectively. These are two scripts provided in the sensible-utils " +"package that check the EDITOR and PAGER variables and launch the " +"appropriate program, and fall back to ``/usr/bin/editor`` and " +"``/usr/bin/pager`` if the variable is not set." +msgstr "" + +#: ../../ch-customized-programs.rst:104 +msgid "" +"A program may also use the VISUAL environment variable to determine the " +"user's choice of editor. If it exists, it should take precedence over " +"EDITOR. This is in fact what ``/usr/bin/sensible-editor`` does." +msgstr "" + +#: ../../ch-customized-programs.rst:108 +msgid "" +"It is not required for a package to depend on ``editor`` and ``pager``, " +"nor is it required for a package to provide such virtual packages. [#]_" +msgstr "" + +#: ../../ch-customized-programs.rst:115 +msgid "Web servers and applications" +msgstr "" + +#: ../../ch-customized-programs.rst:117 +msgid "" +"This section describes the locations and URLs that should be used by all " +"web servers and web applications in the Debian system." +msgstr "" + +#: ../../ch-customized-programs.rst:120 +msgid "Cgi-bin executable files are installed in the directory" +msgstr "" + +#: ../../ch-customized-programs.rst:126 +msgid "or a subdirectory of that directory, and the script" +msgstr "" + +#: ../../ch-customized-programs.rst:132 +msgid "should be referred to as" +msgstr "" + +#: ../../ch-customized-programs.rst:138 +msgid "(Deleted)" +msgstr "" + +#: ../../ch-customized-programs.rst:140 +msgid "Access to images" +msgstr "" + +#: ../../ch-customized-programs.rst:142 +msgid "" +"It is recommended that images for a package be stored in " +"``/usr/share/images/package`` and may be referred to through an alias " +"``/images/`` as" +msgstr "" + +#: ../../ch-customized-programs.rst:150 +msgid "Web Document Root" +msgstr "" + +#: ../../ch-customized-programs.rst:152 +msgid "" +"Web Applications should try to avoid storing files in the Web Document " +"Root. Instead they should use the /usr/share/doc/package directory for " +"documents and register the Web Application via the doc-base package. If " +"access to the web document root is unavoidable then use" +msgstr "" + +#: ../../ch-customized-programs.rst:162 +msgid "" +"as the Document Root. This might be just a symbolic link to the location " +"where the system administrator has put the real document root." +msgstr "" + +#: ../../ch-customized-programs.rst:166 +msgid "Providing httpd and/or httpd-cgi" +msgstr "" + +#: ../../ch-customized-programs.rst:168 +msgid "" +"All web servers should provide the virtual package ``httpd``. If a web " +"server has CGI support it should provide ``httpd-cgi`` additionally." +msgstr "" + +#: ../../ch-customized-programs.rst:172 +msgid "" +"All web applications which do not contain CGI scripts should depend on " +"``httpd``, all those web applications which ``do`` contain CGI scripts, " +"should depend on ``httpd-cgi``." +msgstr "" + +#: ../../ch-customized-programs.rst:179 +msgid "Mail transport, delivery and user agents" +msgstr "" + +#: ../../ch-customized-programs.rst:181 +msgid "" +"Debian packages which process electronic mail, whether mail user agents " +"(MUAs) or mail transport agents (MTAs), must ensure that they are " +"compatible with the configuration decisions below. Failure to do this may" +" result in lost mail, broken ``From:`` lines, and other serious brain " +"damage!" +msgstr "" + +#: ../../ch-customized-programs.rst:187 +msgid "" +"The mail spool is ``/var/mail`` and the interface to send a mail message " +"is ``/usr/sbin/sendmail`` (as per the FHS). On older systems, the mail " +"spool may be physically located in ``/var/spool/mail``, but all access to" +" the mail spool should be via the ``/var/mail`` symlink. The mail spool " +"is part of the base system and not part of the MTA package." +msgstr "" + +#: ../../ch-customized-programs.rst:193 +msgid "" +"All Debian MUAs, MTAs, MDAs and other mailbox accessing programs (such as" +" IMAP daemons) must lock the mailbox in an NFS-safe way. This means that " +"``fcntl()`` locking must be combined with dot locking. To avoid " +"deadlocks, a program should use ``fcntl()`` first and dot locking after " +"this, or alternatively implement the two locking methods in a non " +"blocking way. [#]_ Using the functions ``maillock`` and ``mailunlock`` " +"provided by the ``liblockfile*`` packages is the recommended way to " +"accomplish this." +msgstr "" + +#: ../../ch-customized-programs.rst:202 +msgid "" +"Mailboxes are generally either mode 600 and owned by user or mode 660 and" +" owned by ``user:mail``. [#]_ The local system administrator may choose " +"a different permission scheme; packages should not make assumptions about" +" the permission and ownership of mailboxes unless required (such as when " +"creating a new mailbox). A MUA may remove a mailbox (unless it has " +"nonstandard permissions) in which case the MTA or another MUA must " +"recreate it if needed." +msgstr "" + +#: ../../ch-customized-programs.rst:210 +msgid "" +"The mail spool is 2775 ``root:mail``, and MUAs should be setgid mail to " +"do the locking mentioned above (and must obviously avoid accessing other " +"users' mailboxes using this privilege)." +msgstr "" + +#: ../../ch-customized-programs.rst:214 +msgid "" +"``/etc/aliases`` is the source file for the system mail aliases (e.g., " +"postmaster, usenet, etc.), it is the one which the sysadmin and " +"``postinst`` scripts may edit. After ``/etc/aliases`` is edited the " +"program or human editing it must call ``newaliases``. All MTA packages " +"must come with a ``newaliases`` program, even if it does nothing, but " +"older MTA packages did not do this so programs should not fail if " +"``newaliases`` cannot be found. Note that because of this, all MTA " +"packages must have ``Provides``, ``Conflicts`` and ``Replaces: mail-" +"transport-agent`` control fields." +msgstr "" + +#: ../../ch-customized-programs.rst:224 +msgid "" +"The convention of writing ``forward to address`` in the mailbox itself is" +" not supported. Use a ``.forward`` file instead." +msgstr "" + +#: ../../ch-customized-programs.rst:227 +msgid "" +"The ``rmail`` program used by UUCP for incoming mail should be " +"``/usr/sbin/rmail``. Likewise, ``rsmtp``, for receiving batch-SMTP-over-" +"UUCP, should be ``/usr/sbin/rsmtp`` if it is supported." +msgstr "" + +#: ../../ch-customized-programs.rst:231 +msgid "" +"If your package needs to know what hostname to use on (for example) " +"outgoing news and mail messages which are generated locally, you should " +"use the file ``/etc/mailname``. It will contain the portion after the " +"username and ``@`` (at) sign for email addresses of users on the machine " +"(followed by a newline)." +msgstr "" + +#: ../../ch-customized-programs.rst:237 +msgid "" +"Such a package should check for the existence of this file when it is " +"being configured. If it exists, it should be used without comment, " +"although an MTA's configuration script may wish to prompt the user even " +"if it finds that this file exists. If the file does not exist, the " +"package should prompt the user for the value (preferably using " +"``debconf``) and store it in ``/etc/mailname`` as well as using it in the" +" package's configuration. The prompt should make it clear that the name " +"will not just be used by that package. For example, in this situation the" +" ``inn`` package could say something like:" +msgstr "" + +#: ../../ch-customized-programs.rst:255 +msgid "where syshostname is the output of ``hostname --fqdn``." +msgstr "" + +#: ../../ch-customized-programs.rst:260 +msgid "News system configuration" +msgstr "" + +#: ../../ch-customized-programs.rst:262 +msgid "" +"All the configuration files related to the NNTP (news) servers and " +"clients should be located under ``/etc/news``." +msgstr "" + +#: ../../ch-customized-programs.rst:265 +msgid "" +"There are some configuration issues that apply to a number of news " +"clients and server packages on the machine. These are:" +msgstr "" + +#: ../../ch-customized-programs.rst:270 +msgid "``/etc/news/organization``" +msgstr "" + +#: ../../ch-customized-programs.rst:269 +msgid "" +"A string which should appear as the organization header for all messages " +"posted by NNTP clients on the machine" +msgstr "" + +#: ../../ch-customized-programs.rst:274 +msgid "``/etc/news/server``" +msgstr "" + +#: ../../ch-customized-programs.rst:273 +msgid "" +"Contains the FQDN of the upstream NNTP server, or localhost if the local " +"machine is an NNTP server." +msgstr "" + +#: ../../ch-customized-programs.rst:276 +msgid "" +"Other global files may be added as required for cross-package news " +"configuration." +msgstr "" + +#: ../../ch-customized-programs.rst:282 +msgid "Programs for the X Window System" +msgstr "" + +#: ../../ch-customized-programs.rst:287 +msgid "Providing X support and package priorities" +msgstr "" + +#: ../../ch-customized-programs.rst:289 +msgid "" +"Programs that can be configured with support for the X Window System must" +" be configured to do so and must declare any package dependencies " +"necessary to satisfy their runtime requirements when using the X Window " +"System. If such a package is of higher priority than the X packages on " +"which it depends, it is required that either the X-specific components be" +" split into a separate package, or that an alternative version of the " +"package, which includes X support, be provided, or that the package's " +"priority be lowered." +msgstr "" + +#: ../../ch-customized-programs.rst:301 +msgid "Packages providing an X server" +msgstr "" + +#: ../../ch-customized-programs.rst:303 +msgid "" +"Packages that provide an X server that, directly or indirectly, " +"communicates with real input and display hardware should declare in their" +" ``Provides`` control field that they provide the virtual package " +"``xserver``. [#]_" +msgstr "" + +#: ../../ch-customized-programs.rst:311 +msgid "Packages providing a terminal emulator" +msgstr "" + +#: ../../ch-customized-programs.rst:313 +msgid "" +"Packages that provide a terminal emulator for the X Window System which " +"meet the criteria listed below should declare in their ``Provides`` " +"control field that they provide the virtual package ``x-terminal-" +"emulator``. They should also register themselves as an alternative for " +"``/usr/bin/x-terminal-emulator``, with a priority of 20. That alternative" +" should have a slave alternative for ``/usr/share/man/man1/x-terminal-" +"emulator.1.gz`` pointing to the corresponding manual page." +msgstr "" + +#: ../../ch-customized-programs.rst:322 +msgid "To be an ``x-terminal-emulator``, a program must:" +msgstr "" + +#: ../../ch-customized-programs.rst:324 +msgid "Be able to emulate a DEC VT100 terminal, or a compatible terminal." +msgstr "" + +#: ../../ch-customized-programs.rst:326 +msgid "" +"Support the command-line option ``-e command``, which creates a new " +"terminal window [#]_ and runs the specified command. <command> may be " +"multiple arguments, which form the argument list to the executed program." +" In other words, the behavior is as though the arguments were passed " +"directly to ``execvp``, bypassing the shell. (``xterm``'s behavior of " +"falling back on using the shell if ``-e`` had a single argument and exec " +"failed is permissible but not required.)" +msgstr "" + +#: ../../ch-customized-programs.rst:335 +msgid "" +"Support the command-line option ``-T title``, which creates a new " +"terminal window with the window title title." +msgstr "" + +#: ../../ch-customized-programs.rst:341 +msgid "Packages providing a window manager" +msgstr "" + +#: ../../ch-customized-programs.rst:343 +msgid "" +"Packages that provide a window manager should declare in their " +"``Provides`` control field that they provide the virtual package ``x" +"-window-manager``. They should also register themselves as an alternative" +" for ``/usr/bin/x-window-manager``, with a priority calculated as " +"follows:" +msgstr "" + +#: ../../ch-customized-programs.rst:349 +msgid "Start with a priority of 20." +msgstr "" + +#: ../../ch-customized-programs.rst:351 +msgid "" +"If the window manager supports the Debian menu system, add 20 points if " +"this support is available in the package's default configuration (i.e., " +"no configuration files belonging to the system or user have to be edited " +"to activate the feature); if configuration files must be modified, add " +"only 10 points." +msgstr "" + +#: ../../ch-customized-programs.rst:357 +msgid "" +"If the window manager complies with `The Window Manager Specification " +"Project <https://www.freedesktop.org/wiki/Specifications/wm-spec>`_, " +"written by the `Free Desktop Group <https://www.freedesktop.org/wiki/>`_," +" add 40 points." +msgstr "" + +#: ../../ch-customized-programs.rst:362 +msgid "" +"If the window manager permits the X session to be restarted using a " +"*different* window manager (without killing the X server) in its default " +"configuration, add 10 points; otherwise add none." +msgstr "" + +#: ../../ch-customized-programs.rst:366 +msgid "" +"That alternative should have a slave alternative for " +"``/usr/share/man/man1/x-window-manager.1.gz`` pointing to the " +"corresponding manual page." +msgstr "" + +#: ../../ch-customized-programs.rst:373 +msgid "Packages providing fonts" +msgstr "" + +#: ../../ch-customized-programs.rst:375 +msgid "" +"Packages that provide fonts for the X Window System [#]_ must do a " +"number of things to ensure that they are both available without " +"modification of the X or font server configuration, and that they do not " +"corrupt files used by other font packages to register information about " +"themselves." +msgstr "" + +#: ../../ch-customized-programs.rst:381 +msgid "" +"Fonts of any type supported by the X Window System must be in a separate " +"binary package from any executables, libraries, or documentation (except " +"that specific to the fonts shipped, such as their license information). " +"If one or more of the fonts so packaged are necessary for proper " +"operation of the package with which they are associated the font package " +"may be Recommended; if the fonts merely provide an enhancement, a " +"Suggests relationship may be used. Packages must not Depend on font " +"packages. [#]_" +msgstr "" + +#: ../../ch-customized-programs.rst:390 +msgid "" +"BDF fonts must be converted to PCF fonts with the ``bdftopcf`` utility " +"(available in the ``xfonts-utils`` package, ``gzip``\\ ped, and placed in" +" a directory that corresponds to their resolution:" +msgstr "" + +#: ../../ch-customized-programs.rst:394 +msgid "100 dpi fonts must be placed in ``/usr/share/fonts/X11/100dpi/``." +msgstr "" + +#: ../../ch-customized-programs.rst:396 +msgid "75 dpi fonts must be placed in ``/usr/share/fonts/X11/75dpi/``." +msgstr "" + +#: ../../ch-customized-programs.rst:398 +msgid "" +"Character-cell fonts, cursor fonts, and other low-resolution fonts must " +"be placed in ``/usr/share/fonts/X11/misc/``." +msgstr "" + +#: ../../ch-customized-programs.rst:401 +msgid "" +"Type 1 fonts must be placed in ``/usr/share/fonts/X11/Type1/``. If font " +"metric files are available, they must be placed here as well." +msgstr "" + +#: ../../ch-customized-programs.rst:404 +msgid "" +"Subdirectories of ``/usr/share/fonts/X11/`` other than those listed above" +" must be neither created nor used. (The ``PEX``, ``CID``, ``Speedo``, and" +" ``cyrillic`` directories are excepted for historical reasons, but " +"installation of files into these directories remains discouraged.)" +msgstr "" + +#: ../../ch-customized-programs.rst:410 +msgid "" +"Font packages may, instead of placing files directly in the X font " +"directories listed above, provide symbolic links in that font directory " +"pointing to the files' actual location in the filesystem. Such a location" +" must comply with the FHS." +msgstr "" + +#: ../../ch-customized-programs.rst:415 +msgid "" +"Font packages should not contain both 75dpi and 100dpi versions of a " +"font. If both are available, they should be provided in separate binary " +"packages with ``-75dpi`` or ``-100dpi`` appended to the names of the " +"packages containing the corresponding fonts." +msgstr "" + +#: ../../ch-customized-programs.rst:420 +msgid "" +"Fonts destined for the ``misc`` subdirectory should not be included in " +"the same package as 75dpi or 100dpi fonts; instead, they should be " +"provided in a separate package with ``-misc`` appended to its name." +msgstr "" + +#: ../../ch-customized-programs.rst:425 +msgid "" +"Font packages must not provide the files ``fonts.dir``, ``fonts.alias``, " +"or ``fonts.scale`` in a font directory:" +msgstr "" + +#: ../../ch-customized-programs.rst:428 +msgid "``fonts.dir`` files must not be provided at all." +msgstr "" + +#: ../../ch-customized-programs.rst:430 +msgid "" +"``fonts.alias`` and ``fonts.scale`` files, if needed, should be provided " +"in the directory ``/etc/X11/fonts/fontdir/package.extension``, where " +"fontdir is the name of the subdirectory of ``/usr/share/fonts/X11/`` " +"where the package's corresponding fonts are stored (e.g., ``75dpi`` or " +"``misc``), package is the name of the package that provides these fonts, " +"and extension is either ``scale`` or ``alias``, whichever corresponds to " +"the file contents." +msgstr "" + +#: ../../ch-customized-programs.rst:439 +msgid "" +"Font packages must declare a dependency on ``xfonts-utils`` in their " +"``Depends`` or ``Pre-Depends`` control field." +msgstr "" + +#: ../../ch-customized-programs.rst:442 +msgid "" +"Font packages that provide one or more ``fonts.scale`` files as described" +" above must invoke ``update-fonts-scale`` on each directory into which " +"they installed fonts *before* invoking ``update-fonts-dir`` on that " +"directory. This invocation must occur in both the ``postinst`` (for all " +"arguments) and ``postrm`` (for all arguments except ``upgrade``) scripts." +msgstr "" + +#: ../../ch-customized-programs.rst:449 +msgid "" +"Font packages that provide one or more ``fonts.alias`` files as described" +" above must invoke ``update-fonts-alias`` on each directory into which " +"they installed fonts. This invocation must occur in both the ``postinst``" +" (for all arguments) and ``postrm`` (for all arguments except " +"``upgrade``) scripts." +msgstr "" + +#: ../../ch-customized-programs.rst:455 +msgid "" +"Font packages must invoke ``update-fonts-dir`` on each directory into " +"which they installed fonts. This invocation must occur in both the " +"``postinst`` (for all arguments) and ``postrm`` (for all arguments except" +" ``upgrade``) scripts." +msgstr "" + +#: ../../ch-customized-programs.rst:460 +msgid "" +"Font packages must not provide alias names for the fonts they include " +"which collide with alias names already in use by fonts already packaged." +msgstr "" + +#: ../../ch-customized-programs.rst:464 +msgid "" +"Font packages must not provide fonts with the same XLFD registry name as " +"another font already packaged." +msgstr "" + +#: ../../ch-customized-programs.rst:470 +msgid "Application defaults files" +msgstr "" + +#: ../../ch-customized-programs.rst:472 +msgid "" +"Application defaults files must be installed in the directory ``/etc/X11" +"/app-defaults/`` (use of a localized subdirectory of ``/etc/X11/`` as " +"described in the *X Toolkit Intrinsics - C Language Interface* manual is " +"also permitted). They must be registered as ``conffile``\\ s or handled " +"as configuration files." +msgstr "" + +#: ../../ch-customized-programs.rst:478 +msgid "" +"Customization of programs' X resources may also be supported with the " +"provision of a file with the same name as that of the package placed in " +"the ``/etc/X11/Xresources/`` directory, which must be registered as a " +"``conffile`` or handled as a configuration file. [#]_" +msgstr "" + +#: ../../ch-customized-programs.rst:486 +msgid "Installation directory issues" +msgstr "" + +#: ../../ch-customized-programs.rst:488 +msgid "" +"Historically, packages using the X Window System used a separate set of " +"installation directories from other packages. This practice has been " +"discontinued and packages using the X Window System should now generally " +"be installed in the same directories as any other package. Specifically, " +"packages must not install files under the ``/usr/X11R6/`` directory and " +"the ``/usr/X11R6/`` directory hierarchy should be regarded as obsolete." +msgstr "" + +#: ../../ch-customized-programs.rst:495 +msgid "" +"Include files previously installed under ``/usr/X11R6/include/X11/`` " +"should be installed into ``/usr/include/X11/``. For files previously " +"installed into subdirectories of ``/usr/X11R6/lib/X11/``, package " +"maintainers should determine if subdirectories of ``/usr/lib/`` and " +"``/usr/share/`` can be used. If not, a subdirectory of ``/usr/lib/X11/`` " +"should be used." +msgstr "" + +#: ../../ch-customized-programs.rst:502 +msgid "" +"Configuration files for window, display, or session managers or other " +"applications that are tightly integrated with the X Window System may be " +"placed in a subdirectory of ``/etc/X11/`` corresponding to the package " +"name. Other X Window System applications should use the ``/etc/`` " +"directory unless otherwise mandated by policy (such as for " +":ref:`s-appdefaults`)." +msgstr "" + +#: ../../ch-customized-programs.rst:512 +msgid "Perl programs and modules" +msgstr "" + +#: ../../ch-customized-programs.rst:514 +msgid "Perl programs and modules should follow the current Perl policy." +msgstr "" + +#: ../../ch-customized-programs.rst:516 +msgid "" +"The Perl policy can be found in the ``perl-policy`` files in the " +"``debian-policy`` package. It is also available from the Debian web " +"mirrors at https://www.debian.org/doc/packaging-manuals/perl-policy/." +msgstr "" + +#: ../../ch-customized-programs.rst:523 +msgid "Emacs lisp programs" +msgstr "" + +#: ../../ch-customized-programs.rst:525 +msgid "" +"Please refer to the \"Debian Emacs Policy\" for details of how to package" +" emacs lisp programs." +msgstr "" + +#: ../../ch-customized-programs.rst:528 +msgid "" +"The Emacs policy is available in ``debian-emacs-policy.gz`` of the " +"emacsen-common package. It is also available from the Debian web mirrors " +"at https://www.debian.org/doc/packaging-manuals/debian-emacs-policy." +msgstr "" + +#: ../../ch-customized-programs.rst:535 +msgid "Games" +msgstr "" + +#: ../../ch-customized-programs.rst:537 +msgid "" +"The permissions on ``/var/games`` are mode 755, owner ``root`` and group " +"``root``." +msgstr "" + +#: ../../ch-customized-programs.rst:540 +msgid "Each game decides on its own security policy." +msgstr "" + +#: ../../ch-customized-programs.rst:542 +msgid "" +"Games which require protected, privileged access to high-score files, " +"saved games, etc., may be made set-\\ *group*-id (mode 2755) and owned by" +" ``root:games``, and use files and directories with appropriate " +"permissions (770 ``root:games``, for example). They must not be made " +"set-\\ *user*-id, as this causes security problems. (If an attacker can " +"subvert any set-user-id game they can overwrite the executable of any " +"other, causing other players of these games to run a Trojan horse " +"program. With a set-group-id game the attacker only gets access to less " +"important game data, and if they can get at the other players' accounts " +"at all it will take considerably more effort.)" +msgstr "" + +#: ../../ch-customized-programs.rst:553 +msgid "" +"Some packages, for example some fortune cookie programs, are configured " +"by the upstream authors to install with their data files or other static " +"information made unreadable so that they can only be accessed through " +"set-id programs provided. You should not do this in a Debian package: " +"anyone can download the ``.deb`` file and read the data from it, so there" +" is no point making the files unreadable. Not making the files unreadable" +" also means that you don't have to make so many programs set-id, which " +"reduces the risk of a security hole." +msgstr "" + +#: ../../ch-customized-programs.rst:562 +msgid "" +"As described in the FHS, binaries of games should be installed in the " +"directory ``/usr/games``. This also applies to games that use the X " +"Window System. Manual pages for games (X and non-X games) should be " +"installed in ``/usr/share/man/man6``." +msgstr "" + +#: ../../ch-customized-programs.rst:568 +msgid "" +"Internally, the package system normalizes the GNU triplets and the Debian" +" arches into Debian arch triplets (which are kind of inverted GNU " +"triplets), with the first component of the triplet representing the libc " +"and ABI in use, and then does matching against those triplets. However, " +"such triplets are an internal implementation detail that should not be " +"used by packages directly. The libc and ABI portion is handled internally" +" by the package system based on the os and cpu." +msgstr "" + +#: ../../ch-customized-programs.rst:578 +msgid "The Debian base system already provides an editor and a pager program." +msgstr "" + +#: ../../ch-customized-programs.rst:582 +msgid "" +"If it is not possible to establish both locks, the system shouldn't wait " +"for the second lock to be established, but remove the first lock, wait a " +"(random) time, and start over locking again." +msgstr "" + +#: ../../ch-customized-programs.rst:587 +msgid "" +"There are two traditional permission schemes for mail spools: mode 600 " +"with all mail delivery done by processes running as the destination user," +" or mode 660 and owned by group mail with mail delivery done by a process" +" running as a system user in group mail. Historically, Debian required " +"mode 660 mail spools to enable the latter model, but that model has " +"become increasingly uncommon and the principle of least privilege " +"indicates that mail systems that use the first model should use " +"permissions of 600. If delivery to programs is permitted, it's easier to " +"keep the mail system secure if the delivery agent runs as the destination" +" user. Debian Policy therefore permits either scheme." +msgstr "" + +#: ../../ch-customized-programs.rst:600 +msgid "" +"This implements current practice, and provides an actual policy for usage" +" of the ``xserver`` virtual package which appears in the virtual packages" +" list. In a nutshell, X servers that interface directly with the display " +"and input hardware or via another subsystem (e.g., GGI) should provide " +"``xserver``. Things like ``Xvfb``, ``Xnest``, and ``Xprt`` should not." +msgstr "" + +#: ../../ch-customized-programs.rst:608 +msgid "" +"\"New terminal window\" does not necessarily mean a new top-level X " +"window directly parented by the window manager; it could, if the terminal" +" emulator application were so coded, be a new \"view\" in a multiple-" +"document interface (MDI)." +msgstr "" + +#: ../../ch-customized-programs.rst:614 +msgid "" +"For the purposes of Debian Policy, a \"font for the X Window System\" is " +"one which is accessed via X protocol requests. Fonts for the Linux " +"console, for PostScript renderer, or any other purpose, do not fit this " +"definition. Any tool which makes such fonts available to the X Window " +"System, however, must abide by this font policy." +msgstr "" + +#: ../../ch-customized-programs.rst:621 +msgid "" +"This is because the X server may retrieve fonts from the local file " +"system or over the network from an X font server; the Debian package " +"system is empowered to deal only with the local file system." +msgstr "" + +#: ../../ch-customized-programs.rst:626 +msgid "" +"Note that this mechanism is not the same as using app-defaults; app-" +"defaults are tied to the client binary on the local file system, whereas " +"X resources are stored in the X server and affect all connecting clients." +msgstr "" + diff --git a/locales/ja/LC_MESSAGES/ch-docs.po b/locales/ja/LC_MESSAGES/ch-docs.po new file mode 100644 index 0000000..f368ea8 --- /dev/null +++ b/locales/ja/LC_MESSAGES/ch-docs.po @@ -0,0 +1,503 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1996, 1997, 1998 Ian Jackson, Christian Schwarz, 1998-2017, +# The Debian Policy Mailing List +# This file is distributed under the same license as the Debian Policy +# Manual package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2018. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Debian Policy Manual 4.1.6.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-08-02 11:56+0800\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language-Team: LANGUAGE <LL@li.org>\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.4.0\n" + +#: ../../ch-docs.rst:2 +msgid "Documentation" +msgstr "" + +#: ../../ch-docs.rst:7 +msgid "Manual pages" +msgstr "" + +#: ../../ch-docs.rst:9 +msgid "" +"You should install manual pages in ``nroff`` source form, in appropriate " +"places under ``/usr/share/man``. You should only use sections 1 to 9 (see" +" the FHS for more details). You must not install a pre-formatted \"cat " +"page\"." +msgstr "" + +#: ../../ch-docs.rst:14 +msgid "" +"Each program, utility, and function should have an associated manual page" +" included in the same package. It is suggested that all configuration " +"files also have a manual page included as well. Manual pages for " +"protocols and other auxiliary things are optional." +msgstr "" + +#: ../../ch-docs.rst:19 +msgid "" +"If no manual page is available, this is considered as a bug and should be" +" reported to the Debian Bug Tracking System (the maintainer of the " +"package is allowed to write this bug report themselves, if they so " +"desire). Do not close the bug report until a proper man page is " +"available. [#]_" +msgstr "" + +#: ../../ch-docs.rst:25 +msgid "" +"You may forward a complaint about a missing man page to the upstream " +"authors, and mark the bug as forwarded in the Debian bug tracking system." +" Even though the GNU Project do not in general consider the lack of a man" +" page to be a bug, we do; if they tell you that they don't consider it a " +"bug you should leave the bug in our bug tracking system open anyway." +msgstr "" + +#: ../../ch-docs.rst:32 +msgid "Manual pages should be installed compressed using ``gzip -9``." +msgstr "" + +#: ../../ch-docs.rst:34 +msgid "" +"If one man page needs to be accessible via several names it is better to " +"use a symbolic link than the ``.so`` feature, but there is no need to " +"fiddle with the relevant parts of the upstream source to change from " +"``.so`` to symlinks: don't do it unless it's easy. You should not create " +"hard links in the manual page directories, nor put absolute filenames in " +"``.so`` directives. The filename in a ``.so`` in a man page should be " +"relative to the base of the man page tree (usually ``/usr/share/man``). " +"If you do not create any links (whether symlinks, hard links, or ``.so`` " +"directives) in the file system to the alternate names of the man page, " +"then you should not rely on ``man`` finding your man page under those " +"names based solely on the information in the man page's header. [#]_" +msgstr "" + +#: ../../ch-docs.rst:46 +msgid "" +"Manual pages in locale-specific subdirectories of ``/usr/share/man`` " +"should use either UTF-8 or the usual legacy encoding for that language " +"(normally the one corresponding to the shortest relevant locale name in " +"``/usr/share/i18n/SUPPORTED``). For example, pages under " +"``/usr/share/man/fr`` should use either UTF-8 or ISO-8859-1. [#]_" +msgstr "" + +#: ../../ch-docs.rst:52 +msgid "" +"A country name (the ``DE`` in ``de_DE``) should not be included in the " +"subdirectory name unless it indicates a significant difference in the " +"language, as this excludes speakers of the language in other countries. " +"[#]_" +msgstr "" + +#: ../../ch-docs.rst:57 +msgid "" +"If a localized version of a manual page is provided, it should either be " +"up-to-date or it should be obvious to the reader that it is outdated and " +"the original manual page should be used instead. This can be done either " +"by a note at the beginning of the manual page or by showing the missing " +"or changed portions in the original language instead of the target " +"language." +msgstr "" + +#: ../../ch-docs.rst:67 +msgid "Info documents" +msgstr "" + +#: ../../ch-docs.rst:69 +msgid "" +"Info documents should be installed in ``/usr/share/info``. They should be" +" compressed with ``gzip -9``." +msgstr "" + +#: ../../ch-docs.rst:72 +msgid "" +"The ``install-info`` program maintains a directory of installed info " +"documents in ``/usr/share/info/dir`` for the use of info readers. This " +"file must not be included in packages other than install-info." +msgstr "" + +#: ../../ch-docs.rst:76 +msgid "" +"``install-info`` is automatically invoked when appropriate using dpkg " +"triggers. Packages other than install-info *should not* invoke ``install-" +"info`` directly and *should not* depend on, recommend, or suggest " +"install-info for this purpose." +msgstr "" + +#: ../../ch-docs.rst:81 +msgid "" +"Info readers requiring the ``/usr/share/info/dir`` file should depend on " +"install-info." +msgstr "" + +#: ../../ch-docs.rst:84 +msgid "" +"Info documents should contain section and directory entry information in " +"the document for the use of ``install-info``. The section should be " +"specified via a line starting with ``INFO-DIR-SECTION`` followed by a " +"space and the section of this info page. The directory entry or entries " +"should be included between a ``START-INFO-DIR-ENTRY`` line and an ``END-" +"INFO-DIR-ENTRY`` line. For example:" +msgstr "" + +#: ../../ch-docs.rst:98 +msgid "" +"To determine which section to use, you should look at " +"``/usr/share/info/dir`` on your system and choose the most relevant (or " +"create a new section if none of the current sections are relevant). [#]_" +msgstr "" + +#: ../../ch-docs.rst:106 +msgid "Additional documentation" +msgstr "" + +#: ../../ch-docs.rst:108 +msgid "" +"Any additional documentation that comes with the package may be installed" +" at the discretion of the package maintainer. It is often a good idea to " +"include text information files (``README``\\ s, FAQs, and so forth) that " +"come with the source package in the binary package. However, you don't " +"need to install the instructions for building and installing the package," +" of course!" +msgstr "" + +#: ../../ch-docs.rst:115 +msgid "" +"Plain text documentation should be compressed with ``gzip -9`` unless it " +"is small." +msgstr "" + +#: ../../ch-docs.rst:117 +msgid "" +"If a package comes with large amounts of documentation that many users of" +" the package will not require, you should create a separate binary " +"package to contain it so that it does not take up disk space on the " +"machines of users who do not need or want it installed. As a special case" +" of this rule, shared library documentation of any appreciable size " +"should always be packaged with the library development package (:ref:`s" +"-sharedlibs-dev`) or in a separate documentation package, since shared " +"libraries are frequently installed as dependencies of other packages by " +"users who have little interest in documentation of the library itself. " +"The documentation package for the package package is conventionally named" +" package-doc (or package-doc-language-code if there are separate " +"documentation packages for multiple languages)." +msgstr "" + +#: ../../ch-docs.rst:130 +msgid "" +"If package is a build tool, development tool, command-line tool, or " +"library development package, package (or package-dev in the case of a " +"library development package) already provides documentation in man, info," +" or plain text format, and package-doc provides HTML or other formats, " +"package should declare at most a ``Suggests`` on package-doc. Otherwise, " +"package should declare at most a ``Recommends`` on package-doc." +msgstr "" + +#: ../../ch-docs.rst:138 +msgid "" +"Additional documentation included in the package should be installed " +"under ``/usr/share/doc/package``. If the documentation is packaged " +"separately, as package-doc for example, it may be installed under either " +"that path or into the documentation directory for the separate " +"documentation package (``/usr/share/doc/package-doc`` in this example). " +"However, installing the documentation into the documentation directory of" +" the main package is preferred since it is independent of the packaging " +"method and will be easier for users to find." +msgstr "" + +#: ../../ch-docs.rst:147 +msgid "" +"Any separate package providing documentation must still install standard " +"documentation files in its own ``/usr/share/doc`` directory as specified " +"in the rest of this policy. See, for example, :ref:`s-copyrightfile` and " +":ref:`s-changelogs`." +msgstr "" + +#: ../../ch-docs.rst:153 +msgid "" +"Packages must not require the existence of any files in " +"``/usr/share/doc/`` in order to function. [#]_ Any files that are used " +"or read by programs but are also useful as stand alone documentation " +"should be installed elsewhere, such as under ``/usr/share/package/``, and" +" then included via symbolic links in ``/usr/share/doc/package``." +msgstr "" + +#: ../../ch-docs.rst:160 +msgid "" +"``/usr/share/doc/package`` may be a symbolic link to another directory in" +" ``/usr/share/doc`` only if the two packages both come from the same " +"source and the first package Depends on the second. [#]_" +msgstr "" + +#: ../../ch-docs.rst:167 +msgid "Preferred documentation formats" +msgstr "" + +#: ../../ch-docs.rst:169 +msgid "The unification of Debian documentation is being carried out via HTML." +msgstr "" + +#: ../../ch-docs.rst:171 +msgid "" +"If the package comes with extensive documentation in a markup format that" +" can be converted to various other formats you should if possible ship " +"HTML versions in a binary package. [#]_ The documentation must be " +"installed as specified in :ref:`s-docs-additional`." +msgstr "" + +#: ../../ch-docs.rst:176 +msgid "" +"Other formats such as PostScript may be provided at the package " +"maintainer's discretion." +msgstr "" + +#: ../../ch-docs.rst:182 +msgid "Copyright information" +msgstr "" + +#: ../../ch-docs.rst:184 +msgid "" +"Every package must be accompanied by a verbatim copy of its copyright " +"information and distribution license in the file " +"``/usr/share/doc/package/copyright``. This file must neither be " +"compressed nor be a symbolic link." +msgstr "" + +#: ../../ch-docs.rst:189 +msgid "" +"In addition, the copyright file must say where the upstream sources (if " +"any) were obtained, and should include a name or contact address for the " +"upstream authors. This can be the name of an individual or an " +"organization, an email address, a web forum or bugtracker, or any other " +"means to unambiguously identify who to contact to participate in the " +"development of the upstream source code." +msgstr "" + +#: ../../ch-docs.rst:196 +msgid "" +"Packages in the *contrib* or *non-free* archive areas should state in the" +" copyright file that the package is not part of the Debian distribution " +"and briefly explain why." +msgstr "" + +#: ../../ch-docs.rst:200 +msgid "" +"A copy of the file which will be installed in " +"``/usr/share/doc/package/copyright`` should be in ``debian/copyright`` in" +" the source package." +msgstr "" + +#: ../../ch-docs.rst:204 +msgid "" +"``/usr/share/doc/package`` may be a symbolic link to another directory in" +" ``/usr/share/doc`` only if the two packages both come from the same " +"source and the first package Depends on the second. These rules are " +"important because ``copyright`` files must be extractable by mechanical " +"means." +msgstr "" + +#: ../../ch-docs.rst:210 +msgid "" +"Packages distributed under the Apache license (version 2.0), the Artistic" +" license, the Creative Commons CC0-1.0 license, the GNU GPL (versions 1, " +"2, or 3), the GNU LGPL (versions 2, 2.1, or 3), the GNU FDL (versions 1.2" +" or 1.3), and the Mozilla Public License (version 1.1 or 2.0) should " +"refer to the corresponding files under ``/usr/share/common-licenses``, " +"[#]_ rather than quoting them in the copyright file." +msgstr "" + +#: ../../ch-docs.rst:218 +msgid "" +"You should not use the copyright file as a general ``README`` file. If " +"your package has such a file it should be installed in " +"``/usr/share/doc/package/README`` or ``README.Debian`` or some other " +"appropriate place." +msgstr "" + +#: ../../ch-docs.rst:223 +msgid "All copyright files must be encoded in UTF-8." +msgstr "" + +#: ../../ch-docs.rst:228 +msgid "Machine-readable copyright information" +msgstr "" + +#: ../../ch-docs.rst:230 +msgid "" +"A specification for a standard, machine-readable format for " +"``debian/copyright`` files is maintained as part of the debian-policy " +"package. This document may be found in the ``copyright-format`` files in " +"the debian-policy package. It is also available from the Debian web " +"mirrors at https://www.debian.org/doc/packaging-manuals/copyright-" +"format/1.0/." +msgstr "" + +#: ../../ch-docs.rst:237 +msgid "Use of this format is optional." +msgstr "" + +#: ../../ch-docs.rst:242 +msgid "Examples" +msgstr "" + +#: ../../ch-docs.rst:244 +msgid "" +"Any examples (configurations, source files, whatever), should be " +"installed in a directory ``/usr/share/doc/package/examples``. These files" +" should not be referenced by any program: they're there for the benefit " +"of the system administrator and users as documentation only. " +"Architecture-specific example files should be installed in a directory " +"``/usr/lib/package/examples`` with symbolic links to them from " +"``/usr/share/doc/package/examples``, or the latter directory itself may " +"be a symbolic link to the former." +msgstr "" + +#: ../../ch-docs.rst:253 +msgid "" +"If the purpose of a package is to provide examples, then the example " +"files may be installed into ``/usr/share/doc/package``." +msgstr "" + +#: ../../ch-docs.rst:259 +msgid "Changelog files" +msgstr "" + +#: ../../ch-docs.rst:261 +msgid "" +"Packages that are not Debian-native must contain a compressed copy of the" +" ``debian/changelog`` file from the Debian source tree in " +"``/usr/share/doc/package`` with the name ``changelog.Debian.gz``." +msgstr "" + +#: ../../ch-docs.rst:265 +msgid "" +"If an upstream changelog is available, it should be accessible as " +"``/usr/share/doc/package/changelog.gz`` in plain text. If the upstream " +"changelog is distributed in HTML, it should be made available in that " +"form as ``/usr/share/doc/package/changelog.html.gz`` and a plain text " +"``changelog.gz`` should be generated from it using, for example, ``lynx " +"-dump -nolist``. If the upstream changelog files do not already conform " +"to this naming convention, then this may be achieved either by renaming " +"the files, or by adding a symbolic link, at the maintainer's discretion." +" [#]_" +msgstr "" + +#: ../../ch-docs.rst:275 +msgid "" +"All of these files should be installed compressed using ``gzip -9``, as " +"they will become large with time even if they start out small." +msgstr "" + +#: ../../ch-docs.rst:278 +msgid "" +"If the package has only one changelog which is used both as the Debian " +"changelog and the upstream one because there is no separate upstream " +"maintainer then that changelog should usually be installed as " +"``/usr/share/doc/package/changelog.gz``; if there is a separate upstream " +"maintainer, but no upstream changelog, then the Debian changelog should " +"still be called ``changelog.Debian.gz``." +msgstr "" + +#: ../../ch-docs.rst:285 +msgid "" +"For details about the format and contents of the Debian changelog file, " +"please see :ref:`s-dpkgchangelog`." +msgstr "" + +#: ../../ch-docs.rst:289 +msgid "" +"It is not very hard to write a man page. See the `Man-Page-HOWTO " +"<http://www.schweikhardt.net/man_page_howto.html>`_, man(7), the examples" +" created by ``dh_make``, the helper program ``help2man``, or the " +"directory ``/usr/share/doc/man-db/examples``." +msgstr "" + +#: ../../ch-docs.rst:295 +msgid "" +"Supporting this in ``man`` often requires unreasonable processing time to" +" find a manual page or to report that none exists, and moves knowledge " +"into man's database that would be better left in the file system. This " +"support is therefore deprecated and will cease to be present in the " +"future." +msgstr "" + +#: ../../ch-docs.rst:302 +msgid "" +"``man`` will automatically detect whether UTF-8 is in use. In future, all" +" manual pages will be required to use UTF-8." +msgstr "" + +#: ../../ch-docs.rst:306 +msgid "" +"At the time of writing, Chinese and Portuguese are the main languages " +"with such differences, so ``pt_BR``, ``zh_CN``, and ``zh_TW`` are all " +"allowed." +msgstr "" + +#: ../../ch-docs.rst:311 +msgid "" +"Normally, info documents are generated from Texinfo source. To include " +"this information in the generated info document, if it is absent, add " +"commands like:" +msgstr "" + +#: ../../ch-docs.rst:322 +msgid "" +"to the Texinfo source of the document and ensure that the info documents " +"are rebuilt from source during the package build." +msgstr "" + +#: ../../ch-docs.rst:326 +msgid "" +"The system administrator should be able to delete files in " +"``/usr/share/doc/`` without causing any programs to break." +msgstr "" + +#: ../../ch-docs.rst:330 +msgid "" +"Please note that this does not override the section on changelog files " +"below, so the file ``/usr/share/doc/package/changelog.Debian.gz`` must " +"refer to the changelog for the current version of package in question. In" +" practice, this means that the sources of the target and the destination " +"of the symlink must be the same (same source package and version)." +msgstr "" + +#: ../../ch-docs.rst:339 +msgid "" +"Rationale: The important thing here is that HTML documentation should be " +"available from *some* binary package." +msgstr "" + +#: ../../ch-docs.rst:343 +msgid "" +"In particular, ``/usr/share/common-licenses/Apache-2.0``, ``/usr/share" +"/common-licenses/Artistic``, ``/usr/share/common-licenses/CC0-1.0``, " +"``/usr/share/common-licenses/GPL-1``, ``/usr/share/common-" +"licenses/GPL-2``, ``/usr/share/common-licenses/GPL-3``, ``/usr/share" +"/common-licenses/LGPL-2``, ``/usr/share/common-licenses/LGPL-2.1``, " +"``/usr/share/common-licenses/LGPL-3``, ``/usr/share/common-" +"licenses/GFDL-1.2``, ``/usr/share/common-licenses/GFDL-1.3``, " +"``/usr/share/common-licenses/MPL-1.1``, and ``/usr/share/common-" +"licenses/MPL-2.0`` respectively. The University of California BSD license" +" is also included in base-files as ``/usr/share/common-licenses/BSD``, " +"but given the brevity of this license, its specificity to code whose " +"copyright is held by the Regents of the University of California, and the" +" frequency of minor wording changes, its text should be included in the " +"copyright file rather than referencing this file." +msgstr "" + +#: ../../ch-docs.rst:364 +msgid "" +"Rationale: People should not have to look in places for upstream " +"changelogs merely because they are given different names or are " +"distributed in HTML format." +msgstr "" + diff --git a/locales/ja/LC_MESSAGES/ch-files.po b/locales/ja/LC_MESSAGES/ch-files.po new file mode 100644 index 0000000..655c840 --- /dev/null +++ b/locales/ja/LC_MESSAGES/ch-files.po @@ -0,0 +1,1100 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1996, 1997, 1998 Ian Jackson, Christian Schwarz, 1998-2017, +# The Debian Policy Mailing List +# This file is distributed under the same license as the Debian Policy +# Manual package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2018. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Debian Policy Manual 4.1.6.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-08-02 11:56+0800\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language-Team: LANGUAGE <LL@li.org>\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.4.0\n" + +#: ../../ch-files.rst:2 +msgid "Files" +msgstr "" + +#: ../../ch-files.rst:7 +msgid "Binaries" +msgstr "" + +#: ../../ch-files.rst:9 +msgid "" +"Two different packages must not install programs with different " +"functionality but with the same filenames. (The case of two programs " +"having the same functionality but different implementations is handled " +"via \"alternatives\" or the \"Conflicts\" mechanism. See " +":ref:`s-maintscripts` and :ref:`s-conflicts` respectively.) If this case " +"happens, one of the programs must be renamed. The maintainers should " +"report this to the ``debian-devel`` mailing list and try to find a " +"consensus about which program will have to be renamed. If a consensus " +"cannot be reached, *both* programs must be renamed." +msgstr "" + +#: ../../ch-files.rst:20 +msgid "" +"To support merged-\\ ``/usr`` systems, packages must not install files in" +" both ``/path`` and ``/usr/path``. For example, a package may not install" +" both ``/bin/example`` and ``/usr/bin/example``." +msgstr "" + +#: ../../ch-files.rst:24 +msgid "" +"If a file is moved between ``/path`` and ``/usr/path`` in revisions of a " +"Debian package, and a compatibility symlink at the old path is needed, " +"the symlink must be managed in a way that will not break when ``/path`` " +"and ``/usr/path`` are the same underlying directory due to symlinks or " +"other mechanisms." +msgstr "" + +#: ../../ch-files.rst:30 +msgid "" +"Binary executables must not be statically linked with the GNU C library, " +"since this prevents the binary from benefiting from fixes and " +"improvements to the C library without being rebuilt and complicates " +"security updates. This requirement may be relaxed for binary executables " +"whose intended purpose is to diagnose and fix the system in situations " +"where the GNU C library may not be usable (such as system recovery shells" +" or utilities like ldconfig) or for binary executables where the security" +" benefits of static linking outweigh the drawbacks." +msgstr "" + +#: ../../ch-files.rst:39 +msgid "" +"By default, when a package is being built, any binaries created should " +"include debugging information, as well as being compiled with " +"optimization. You should also turn on as many reasonable compilation " +"warnings as possible; this makes life easier for porters, who can then " +"look at build logs for possible problems. For the C programming language," +" this means the following compilation parameters should be used:" +msgstr "" + +#: ../../ch-files.rst:54 +msgid "" +"Note that by default all installed binaries should be stripped, either by" +" using the ``-s`` flag to ``install``, or by calling ``strip`` on the " +"binaries after they have been copied into ``debian/tmp`` but before the " +"tree is made into a package." +msgstr "" + +#: ../../ch-files.rst:59 +msgid "" +"Although binaries in the build tree should be compiled with debugging " +"information by default, it can often be difficult to debug programs if " +"they are also subjected to compiler optimization. For this reason, it is " +"recommended to support the standardized environment variable " +"``DEB_BUILD_OPTIONS`` (see :ref:`s-debianrules-options`). This variable " +"can contain several flags to change how a package is compiled and built." +msgstr "" + +#: ../../ch-files.rst:67 +msgid "" +"It is up to the package maintainer to decide what compilation options are" +" best for the package. Certain binaries (such as computationally-" +"intensive programs) will function better with certain flags (``-O3``, for" +" example); feel free to use them. Please use good judgment here. Don't " +"use flags for the sake of it; only use them if there is good reason to do" +" so. Feel free to override the upstream author's ideas about which " +"compilation options are best: they are often inappropriate for our " +"environment." +msgstr "" + +#: ../../ch-files.rst:79 +msgid "Libraries" +msgstr "" + +#: ../../ch-files.rst:81 +msgid "" +"If the package is **architecture: any**, then the shared library " +"compilation and linking flags must have ``-fPIC``, or the package shall " +"not build on some of the supported architectures. [#]_ Any exception to " +"this rule must be discussed on the mailing list *debian-" +"devel@lists.debian.org*, and a rough consensus obtained. The reasons for " +"not compiling with ``-fPIC`` flag must be recorded in the file " +"``README.Debian``, and care must be taken to either restrict the " +"architecture or arrange for ``-fPIC`` to be used on architectures where " +"it is required. [#]_" +msgstr "" + +#: ../../ch-files.rst:91 +msgid "" +"As to the static libraries, the common case is not to have relocatable " +"code, since there is no benefit, unless in specific cases; therefore the " +"static version must not be compiled with the ``-fPIC`` flag. Any " +"exception to this rule should be discussed on the mailing list *debian-" +"devel@lists.debian.org*, and the reasons for compiling with the ``-fPIC``" +" flag must be recorded in the file ``README.Debian``. [#]_" +msgstr "" + +#: ../../ch-files.rst:98 +msgid "" +"In other words, if both a shared and a static library is being built, " +"each source unit (``*.c``, for example, for C files) will need to be " +"compiled twice, for the normal case." +msgstr "" + +#: ../../ch-files.rst:102 +msgid "" +"Libraries should be built with threading support and to be thread-safe if" +" the library supports this." +msgstr "" + +#: ../../ch-files.rst:105 +msgid "" +"Although not enforced by the build tools, shared libraries must be linked" +" against all libraries that they use symbols from in the same way that " +"binaries are. This ensures the correct functioning of the :ref:`symbols " +"<s-sharedlibs-symbols>` and :ref:`shlibs <s-sharedlibs-shlibdeps>` " +"systems and guarantees that all libraries can be safely opened with " +"``dlopen()``. Packagers may wish to use the gcc option ``-Wl,-z,defs`` " +"when building a shared library. Since this option enforces symbol " +"resolution at build time, a missing library reference will be caught " +"early as a fatal build error." +msgstr "" + +#: ../../ch-files.rst:114 +msgid "All installed shared libraries should be stripped with" +msgstr "" + +#: ../../ch-files.rst:120 +msgid "" +"(The option ``--strip-unneeded`` makes ``strip`` remove only the symbols " +"which aren't needed for relocation processing.) Shared libraries can " +"function perfectly well when stripped, since the symbols for dynamic " +"linking are in a separate part of the ELF object file. [#]_" +msgstr "" + +#: ../../ch-files.rst:125 +msgid "" +"Note that under some circumstances it may be useful to install a shared " +"library unstripped, for example when building a separate package to " +"support debugging." +msgstr "" + +#: ../../ch-files.rst:129 +msgid "" +"Shared object files (often ``.so`` files) that are not public libraries, " +"that is, they are not meant to be linked to by third party executables " +"(binaries of other packages), should be installed in subdirectories of " +"the ``/usr/lib`` or ``/usr/lib/triplet`` directories (see the FHS for a " +"definition). Such files are exempt from the rules that govern ordinary " +"shared libraries, except that they must not be installed executable and " +"should be stripped. [#]_" +msgstr "" + +#: ../../ch-files.rst:137 +msgid "" +"Packages that use ``libtool`` to create and install their shared " +"libraries install a file containing additional metadata (ending in " +"``.la``) alongside the library. For public libraries intended for use by " +"other packages, these files normally should not be included in the Debian" +" package, since the information they include is not necessary to link " +"with the shared library on Debian and can add unnecessary additional " +"dependencies to other programs or libraries. [#]_ If the ``.la`` file is" +" required for that library (if, for instance, it's loaded via ``libltdl``" +" in a way that requires that meta-information), the ``dependency_libs`` " +"setting in the ``.la`` file should normally be set to the empty string. " +"If the shared library development package has historically included the " +"``.la``, it must be retained in the development package (with " +"``dependency_libs`` emptied) until all libraries that depend on it have " +"removed or emptied ``dependency_libs`` in their ``.la`` files to prevent " +"linking with those other libraries using ``libtool`` from failing." +msgstr "" + +#: ../../ch-files.rst:154 +msgid "" +"If the ``.la`` must be included, it should be included in the development" +" (``-dev``) package, unless the library will be loaded by ``libtool``'s " +"``libltdl`` library. If it is intended for use with ``libltdl``, the " +"``.la`` files must go in the run-time library package." +msgstr "" + +#: ../../ch-files.rst:159 +msgid "" +"These requirements for handling of ``.la`` files do not apply to loadable" +" modules or libraries not installed in directories searched by default by" +" the dynamic linker. Packages installing loadable modules will frequently" +" need to install the ``.la`` files alongside the modules so that they can" +" be loaded by ``libltdl``. ``dependency_libs`` does not need to be " +"modified for libraries or modules that are not installed in directories " +"searched by the dynamic linker by default and not intended for use by " +"other packages." +msgstr "" + +#: ../../ch-files.rst:168 +msgid "" +"You must make sure that you use only released versions of shared " +"libraries to build your packages; otherwise other users will not be able " +"to run your binaries properly. Producing source packages that depend on " +"unreleased compilers is also usually a bad idea." +msgstr "" + +#: ../../ch-files.rst:176 +msgid "Shared libraries" +msgstr "" + +#: ../../ch-files.rst:178 +msgid "This section has moved to :doc:`Shared libraries <ch-sharedlibs>`." +msgstr "" + +#: ../../ch-files.rst:183 +msgid "Scripts" +msgstr "" + +#: ../../ch-files.rst:185 +msgid "" +"All command scripts, including the package maintainer scripts inside the " +"package and used by ``dpkg``, should have a ``#!`` line naming the shell " +"to be used to interpret them." +msgstr "" + +#: ../../ch-files.rst:189 +msgid "In the case of Perl scripts this must be ``#!/usr/bin/perl``." +msgstr "" + +#: ../../ch-files.rst:191 +msgid "" +"When scripts are installed into a directory in the system PATH, the " +"script name should not include an extension such as ``.sh`` or ``.pl`` " +"that denotes the scripting language currently used to implement it." +msgstr "" + +#: ../../ch-files.rst:195 +msgid "" +"Shell scripts (``sh`` and ``bash``) other than ``init.d`` scripts should " +"almost certainly start with ``set -e`` so that errors are detected. " +"``init.d`` scripts are something of a special case, due to how frequently" +" they need to call commands that are allowed to fail, and it may instead " +"be easier to check the exit status of commands directly. See :ref:`s" +"-writing-init` for more information about writing ``init.d`` scripts." +msgstr "" + +#: ../../ch-files.rst:203 +msgid "" +"Every script should use ``set -e`` or check the exit status of *every* " +"command." +msgstr "" + +#: ../../ch-files.rst:206 +msgid "" +"Scripts may assume that ``/bin/sh`` implements the POSIX.1-2017 Shell " +"Command Language [#]_ plus the following additional features not " +"mandated by POSIX.1-2017.. [#]_" +msgstr "" + +#: ../../ch-files.rst:210 +msgid "" +"``echo -n``, if implemented as a shell built-in, must not generate a " +"newline." +msgstr "" + +#: ../../ch-files.rst:213 +msgid "" +"``test``, if implemented as a shell built-in, must support ``-a`` and " +"``-o`` as binary logical operators." +msgstr "" + +#: ../../ch-files.rst:216 +msgid "" +"``local`` to create a scoped variable must be supported, including " +"listing multiple variables in a single local command and assigning a " +"value to a variable at the same time as localizing it. ``local`` may or " +"may not preserve the variable value from an outer scope if no assignment " +"is present. Uses such as:" +msgstr "" + +#: ../../ch-files.rst:229 +msgid "must be supported and must set the value of ``c`` to ``delta``." +msgstr "" + +#: ../../ch-files.rst:231 +msgid "" +"The XSI extension to ``kill`` allowing ``kill -signal``, where signal is " +"either the name of a signal or one of the numeric signals listed in the " +"XSI extension (0, 1, 2, 3, 6, 9, 14, and 15), must be supported if " +"``kill`` is implemented as a shell built-in." +msgstr "" + +#: ../../ch-files.rst:236 +msgid "" +"The XSI extension to ``trap`` allowing numeric signals must be supported." +" In addition to the signal numbers listed in the extension, which are the" +" same as for ``kill`` above, 13 (SIGPIPE) must be allowed." +msgstr "" + +#: ../../ch-files.rst:241 +msgid "" +"If a shell script requires non-POSIX.1-2017 features from the shell " +"interpreter other than those listed above, the appropriate shell must be " +"specified in the first line of the script (e.g., ``#!/bin/bash``) and the" +" package must depend on the package providing the shell (unless the shell" +" package is marked \"Essential\", as in the case of ``bash``)." +msgstr "" + +#: ../../ch-files.rst:247 +msgid "" +"You may wish to restrict your script to POSIX.1-2017 features plus the " +"above set when possible so that it may use ``/bin/sh`` as its " +"interpreter. Checking your script with ``checkbashisms`` from the " +"devscripts package or running your script with an alternate shell such as" +" ``posh`` may help uncover violations of the above requirements. If in " +"doubt whether a script complies with these requirements, use " +"``/bin/bash``." +msgstr "" + +#: ../../ch-files.rst:254 +msgid "" +"Perl scripts should check for errors when making any system calls, " +"including ``open``, ``print``, ``close``, ``rename`` and ``system``." +msgstr "" + +#: ../../ch-files.rst:257 +msgid "" +"``csh`` and ``tcsh`` should be avoided as scripting languages. See *Csh " +"Programming Considered Harmful*, one of the ``comp.unix.*`` FAQs, which " +"can be found at http://www.faqs.org/faqs/unix-faq/shell/csh-whynot/. If " +"an upstream package comes with ``csh`` scripts then you must make sure " +"that they start with ``#!/bin/csh`` and make your package depend on the " +"``c-shell`` virtual package." +msgstr "" + +#: ../../ch-files.rst:264 +msgid "" +"Any scripts which create files in world-writeable directories (e.g., in " +"``/tmp``) must use a mechanism which will fail atomically if a file with " +"the same name already exists." +msgstr "" + +#: ../../ch-files.rst:268 +msgid "" +"The Debian base system provides the ``tempfile`` and ``mktemp`` utilities" +" for use by scripts for this purpose." +msgstr "" + +#: ../../ch-files.rst:274 +msgid "Symbolic links" +msgstr "" + +#: ../../ch-files.rst:276 +msgid "" +"In general, symbolic links within a top-level directory should be " +"relative, and symbolic links pointing from one top-level directory to or " +"into another should be absolute. (A top-level directory is a sub-" +"directory of the root directory ``/``.) For example, a symbolic link from" +" ``/usr/lib/foo`` to ``/usr/share/bar`` should be relative " +"(``../share/bar``), but a symbolic link from ``/var/run`` to ``/run`` " +"should be absolute. [#]_ Symbolic links must not traverse above the root" +" directory." +msgstr "" + +#: ../../ch-files.rst:285 +msgid "" +"In addition, symbolic links should be specified as short as possible, " +"i.e., link targets like ``foo/../bar`` are deprecated." +msgstr "" + +#: ../../ch-files.rst:288 +msgid "" +"Note that when creating a relative link using ``ln`` it is not necessary " +"for the target of the link to exist relative to the working directory " +"you're running ``ln`` from, nor is it necessary to change directory to " +"the directory where the link is to be made. Simply include the string " +"that should appear as the target of the link (this will be a pathname " +"relative to the directory in which the link resides) as the first " +"argument to ``ln``." +msgstr "" + +#: ../../ch-files.rst:296 +msgid "" +"For example, in your ``Makefile`` or ``debian/rules``, you can do things " +"like:" +msgstr "" + +#: ../../ch-files.rst:306 +msgid "" +"A symbolic link pointing to a compressed file (in the sense that it is " +"meant to be uncompressed with ``unzip`` or ``zless`` etc.) should always " +"have the same file extension as the referenced file. (For example, if a " +"file ``foo.gz`` is referenced by a symbolic link, the filename of the " +"link has to end with \"``.gz``\" too, as in ``bar.gz``.)" +msgstr "" + +#: ../../ch-files.rst:315 +msgid "Device files" +msgstr "" + +#: ../../ch-files.rst:317 +msgid "" +"Packages must not include device files or named pipes in the package file" +" tree." +msgstr "" + +#: ../../ch-files.rst:320 +msgid "" +"Debian packages should assume that device files in ``/dev`` are " +"dynamically managed by the kernel or some other system facility and do " +"not have to be explicitly created or managed by the package. Debian " +"packages other than those whose purpose is to manage the ``/dev`` device " +"file tree must not attempt to create or remove device files in ``/dev`` " +"when a dynamic device management facility is in use." +msgstr "" + +#: ../../ch-files.rst:327 +msgid "" +"If named pipes or device files outside of ``/dev`` are required by a " +"package, they should normally be created when necessary by the programs " +"in the package, by init scripts or systemd unit files, or by similar on-" +"demand mechanisms. If such files need to be created during package " +"installation, they must be created in the ``postinst`` maintainer script " +"[#]_ and removed in either the ``prerm`` or the ``postrm`` maintainer " +"script." +msgstr "" + +#: ../../ch-files.rst:338 +msgid "Configuration files" +msgstr "" + +#: ../../ch-files.rst:343 +msgid "Definitions" +msgstr "" + +#: ../../ch-files.rst:350 +msgid "configuration file" +msgstr "" + +#: ../../ch-files.rst:346 +msgid "" +"A file that affects the operation of a program, or provides site- or " +"host-specific information, or otherwise customizes the behavior of a " +"program. Typically, configuration files are intended to be modified by " +"the system administrator (if needed or desired) to conform to local " +"policy or to provide more useful site-specific behavior." +msgstr "" + +#: ../../ch-files.rst:354 +msgid "``conffile``" +msgstr "" + +#: ../../ch-files.rst:353 +msgid "" +"A file listed in a package's ``conffiles`` file, and is treated specially" +" by ``dpkg`` (see :ref:`s-configdetails`)." +msgstr "" + +#: ../../ch-files.rst:356 +msgid "" +"The distinction between these two is important; they are not " +"interchangeable concepts. Almost all ``conffile``\\ s are configuration " +"files, but many configuration files are not ``conffiles``." +msgstr "" + +#: ../../ch-files.rst:360 +msgid "" +"As noted elsewhere, ``/etc/init.d`` scripts, ``/etc/default`` files, " +"scripts installed in ``/etc/cron.{hourly,daily,weekly,monthly}``, and " +"cron configuration installed in ``/etc/cron.d`` must be treated as " +"configuration files. In general, any script that embeds configuration " +"information is de-facto a configuration file and should be treated as " +"such." +msgstr "" + +#: ../../ch-files.rst:370 +msgid "Location" +msgstr "" + +#: ../../ch-files.rst:372 +msgid "" +"Any configuration files created or used by your package must reside in " +"``/etc``. If there are several, consider creating a subdirectory of " +"``/etc`` named after your package." +msgstr "" + +#: ../../ch-files.rst:376 +msgid "" +"If your package creates or uses configuration files outside of ``/etc``, " +"and it is not feasible to modify the package to use ``/etc`` directly, " +"put the files in ``/etc`` and create symbolic links to those files from " +"the location that the package requires." +msgstr "" + +#: ../../ch-files.rst:384 +msgid "Behavior" +msgstr "" + +#: ../../ch-files.rst:386 +msgid "Configuration file handling must conform to the following behavior:" +msgstr "" + +#: ../../ch-files.rst:388 +msgid "local changes must be preserved during a package upgrade, and" +msgstr "" + +#: ../../ch-files.rst:390 +msgid "" +"configuration files must be preserved when the package is removed, and " +"only deleted when the package is purged." +msgstr "" + +#: ../../ch-files.rst:393 +msgid "" +"Obsolete configuration files without local changes should be removed by " +"the package during upgrade. [#]_" +msgstr "" + +#: ../../ch-files.rst:396 +msgid "" +"The easy way to achieve this behavior is to make the configuration file a" +" ``conffile``. This is appropriate only if it is possible to distribute a" +" default version that will work for most installations, although some " +"system administrators may choose to modify it. This implies that the " +"default version will be part of the package distribution, and must not be" +" modified by the maintainer scripts during installation (or at any other " +"time)." +msgstr "" + +#: ../../ch-files.rst:404 +msgid "" +"In order to ensure that local changes are preserved correctly, no package" +" may contain or make hard links to conffiles. [#]_" +msgstr "" + +#: ../../ch-files.rst:407 +msgid "" +"The other way to do it is via the maintainer scripts. In this case, the " +"configuration file must not be listed as a ``conffile`` and must not be " +"part of the package distribution. If the existence of a file is required " +"for the package to be sensibly configured it is the responsibility of the" +" package maintainer to provide maintainer scripts which correctly create," +" update and maintain the file and remove it on purge. (See :doc:`Package " +"maintainer scripts and installation procedure <ch-maintainerscripts>` for" +" more information.) These scripts must be idempotent (i.e., must work " +"correctly if ``dpkg`` needs to re-run them due to errors during " +"installation or removal), must cope with all the variety of ways ``dpkg``" +" can call maintainer scripts, must not overwrite or otherwise mangle the " +"user's configuration without asking, must not ask unnecessary questions " +"(particularly during upgrades), and must otherwise be good citizens." +msgstr "" + +#: ../../ch-files.rst:422 +msgid "" +"The scripts are not required to configure every possible option for the " +"package, but only those necessary to get the package running on a given " +"system. Ideally the sysadmin should not have to do any configuration " +"other than that done (semi-)automatically by the ``postinst`` script." +msgstr "" + +#: ../../ch-files.rst:427 +msgid "" +"A common practice is to create a script called ``package-configure`` and " +"have the package's ``postinst`` call it if and only if the configuration " +"file does not already exist. In certain cases it is useful for there to " +"be an example or template file which the maintainer scripts use. Such " +"files should be in ``/usr/share/package`` or ``/usr/lib/package`` " +"(depending on whether they are architecture-independent or not). There " +"should be symbolic links to them from ``/usr/share/doc/package/examples``" +" if they are examples, and should be perfectly ordinary ``dpkg``-handled " +"files (*not* configuration files)." +msgstr "" + +#: ../../ch-files.rst:437 +msgid "" +"These two styles of configuration file handling must not be mixed, for " +"that way lies madness: ``dpkg`` will ask about overwriting the file every" +" time the package is upgraded." +msgstr "" + +#: ../../ch-files.rst:444 +msgid "Sharing configuration files" +msgstr "" + +#: ../../ch-files.rst:446 +msgid "" +"If two or more packages use the same configuration file and it is " +"reasonable for both to be installed at the same time, one of these " +"packages must be defined as *owner* of the configuration file, i.e., it " +"will be the package which handles that file as a configuration file. " +"Other packages that use the configuration file must depend on the owning " +"package if they require the configuration file to operate. If the other " +"package will use the configuration file if present, but is capable of " +"operating without it, no dependency need be declared." +msgstr "" + +#: ../../ch-files.rst:455 +msgid "" +"If it is desirable for two or more related packages to share a " +"configuration file *and* for all of the related packages to be able to " +"modify that configuration file, then the following should be done:" +msgstr "" + +#: ../../ch-files.rst:459 +msgid "" +"One of the related packages (the \"owning\" package) will manage the " +"configuration file with maintainer scripts as described in the previous " +"section." +msgstr "" + +#: ../../ch-files.rst:463 +msgid "" +"The owning package should also provide a program that the other packages " +"may use to modify the configuration file." +msgstr "" + +#: ../../ch-files.rst:466 +msgid "" +"The related packages must use the provided program to make any desired " +"modifications to the configuration file. They should either depend on the" +" core package to guarantee that the configuration modifier program is " +"available or accept gracefully that they cannot modify the configuration " +"file if it is not. (This is in addition to the fact that the " +"configuration file may not even be present in the latter scenario.)" +msgstr "" + +#: ../../ch-files.rst:474 +msgid "" +"Sometimes it's appropriate to create a new package which provides the " +"basic infrastructure for the other packages and which manages the shared " +"configuration files. (The ``sgml-base`` package is a good example.)" +msgstr "" + +#: ../../ch-files.rst:478 +msgid "" +"If the configuration file cannot be shared as described above, the " +"packages must be marked as conflicting with each other. Two packages that" +" specify the same file as a ``conffile`` must conflict. This is an " +"instance of the general rule about not sharing files. Neither " +"alternatives nor diversions are likely to be appropriate in this case; in" +" particular, ``dpkg`` does not handle diverted ``conffile``\\ s well." +msgstr "" + +#: ../../ch-files.rst:485 +msgid "" +"When two packages both declare the same ``conffile``, they may see left-" +"over configuration files from each other even though they conflict with " +"each other. If a user removes (without purging) one of the packages and " +"installs the other, the new package will take over the ``conffile`` from " +"the old package. If the file was modified by the user, it will be treated" +" the same as any other locally modified ``conffile`` during an upgrade." +msgstr "" + +#: ../../ch-files.rst:493 +msgid "" +"The maintainer scripts must not alter a ``conffile`` of *any* package, " +"including the one the scripts belong to." +msgstr "" + +#: ../../ch-files.rst:499 +msgid "User configuration files (\"dotfiles\")" +msgstr "" + +#: ../../ch-files.rst:501 +msgid "" +"The files in ``/etc/skel`` will automatically be copied into new user " +"accounts by ``adduser``. No other program should reference the files in " +"``/etc/skel``." +msgstr "" + +#: ../../ch-files.rst:505 +msgid "" +"Therefore, if a program needs a dotfile to exist in advance in ``$HOME`` " +"to work sensibly, that dotfile should be installed in ``/etc/skel`` and " +"treated as a configuration file." +msgstr "" + +#: ../../ch-files.rst:509 +msgid "" +"However, programs that require dotfiles in order to operate sensibly are " +"a bad thing, unless they do create the dotfiles themselves automatically." +msgstr "" + +#: ../../ch-files.rst:513 +msgid "" +"Furthermore, programs should be configured by the Debian default " +"installation to behave as closely to the upstream default behavior as " +"possible." +msgstr "" + +#: ../../ch-files.rst:517 +msgid "" +"Therefore, if a program in a Debian package needs to be configured in " +"some way in order to operate sensibly, that should be done using a site-" +"wide configuration file placed in ``/etc``. Only if the program doesn't " +"support a site-wide default configuration and the package maintainer " +"doesn't have time to add it may a default per-user file be placed in " +"``/etc/skel``." +msgstr "" + +#: ../../ch-files.rst:524 +msgid "" +"``/etc/skel`` should be as empty as we can make it. This is particularly " +"true because there is no easy (or necessarily desirable) mechanism for " +"ensuring that the appropriate dotfiles are copied into the accounts of " +"existing users when a package is installed." +msgstr "" + +#: ../../ch-files.rst:532 +msgid "Log files" +msgstr "" + +#: ../../ch-files.rst:534 +msgid "" +"Log files should usually be named ``/var/log/package.log``. If you have " +"many log files, or need a separate directory for permission reasons " +"(``/var/log`` is writable only by ``root``), you should usually create a " +"directory named ``/var/log/package`` and place your log files there." +msgstr "" + +#: ../../ch-files.rst:539 +msgid "" +"Log files must be rotated occasionally so that they don't grow " +"indefinitely. The best way to do this is to install a log rotation " +"configuration file in the directory ``/etc/logrotate.d``, normally named " +"``/etc/logrotate.d/package``, and use the facilities provided by " +"``logrotate``. [#]_ Here is a good example for a logrotate config file " +"(for more information see logrotate(8)):" +msgstr "" + +#: ../../ch-files.rst:558 +msgid "" +"This rotates all files under ``/var/log/foo``, saves 12 compressed " +"generations, and tells the daemon to reopen its log files after the log " +"rotation. It skips this log rotation (via ``missingok``) if no such log " +"file is present, which avoids errors if the package is removed but not " +"purged." +msgstr "" + +#: ../../ch-files.rst:564 +msgid "" +"Log files should be removed when the package is purged (but not when it " +"is only removed). This should be done by the ``postrm`` script when it is" +" called with the argument ``purge`` (see :ref:`s-removedetails`)." +msgstr "" + +#: ../../ch-files.rst:572 +msgid "Permissions and owners" +msgstr "" + +#: ../../ch-files.rst:574 +msgid "" +"The rules in this section are guidelines for general use. If necessary " +"you may deviate from the details below. However, if you do so you must " +"make sure that what is done is secure and you should try to be as " +"consistent as possible with the rest of the system. You should probably " +"also discuss it on ``debian-devel`` first." +msgstr "" + +#: ../../ch-files.rst:580 +msgid "" +"Files should be owned by ``root:root``, and made writable only by the " +"owner and universally readable (and executable, if appropriate), that is " +"mode 644 or 755." +msgstr "" + +#: ../../ch-files.rst:584 +msgid "" +"Directories should be mode 755 or (for group-writability) mode 2775. The " +"ownership of the directory should be consistent with its mode: if a " +"directory is mode 2775, it should be owned by the group that needs write " +"access to it. [#]_" +msgstr "" + +#: ../../ch-files.rst:589 +msgid "" +"Control information files should be owned by ``root:root`` and either " +"mode 644 (for most files) or mode 755 (for executables such as " +":ref:`maintainer scripts <s-maintscripts>`)." +msgstr "" + +#: ../../ch-files.rst:593 +msgid "" +"Setuid and setgid executables should be mode 4755 or 2755 respectively, " +"and owned by the appropriate user or group. They should not be made " +"unreadable (modes like 4711 or 2711 or even 4111); doing so achieves no " +"extra security, because anyone can find the binary in the freely " +"available Debian package; it is merely inconvenient. For the same reason " +"you should not restrict read or execute permissions on non-set-id " +"executables." +msgstr "" + +#: ../../ch-files.rst:601 +msgid "" +"Some setuid programs need to be restricted to particular sets of users, " +"using file permissions. In this case they should be owned by the uid to " +"which they are set-id, and by the group which should be allowed to " +"execute them. They should have mode 4754; again there is no point in " +"making them unreadable to those users who must not be allowed to execute " +"them." +msgstr "" + +#: ../../ch-files.rst:608 +msgid "" +"It is possible to arrange that the system administrator can reconfigure " +"the package to correspond to their local security policy by changing the " +"permissions on a binary: they can do this by using ``dpkg-statoverride``," +" as described below. [#]_ Another method you should consider is to " +"create a group for people allowed to use the program(s) and make any " +"setuid executables executable only by that group." +msgstr "" + +#: ../../ch-files.rst:616 +msgid "" +"If you need to create a new user or group for your package there are two " +"possibilities. Firstly, you may need to make some files in the binary " +"package be owned by this user or group, or you may need to compile the " +"user or group id (rather than just the name) into the binary (though this" +" latter should be avoided if possible, as in this case you need a " +"statically allocated id)." +msgstr "" + +#: ../../ch-files.rst:623 +msgid "" +"If you need a statically allocated id, you must ask for a user or group " +"id from the ``base-passwd`` maintainer, and must not release the package " +"until you have been allocated one. Once you have been allocated one you " +"must either make the package depend on a version of the ``base-passwd`` " +"package with the id present in ``/etc/passwd`` or ``/etc/group``, or " +"arrange for your package to create the user or group itself with the " +"correct id (using ``adduser``) in its ``preinst`` or ``postinst``. (Doing" +" it in the ``postinst`` is to be preferred if it is possible, otherwise a" +" pre-dependency will be needed on the ``adduser`` package.)" +msgstr "" + +#: ../../ch-files.rst:633 +msgid "" +"On the other hand, the program might be able to determine the uid or gid " +"from the user or group name at runtime, so that a dynamically allocated " +"id can be used. In this case you should choose an appropriate user or " +"group name, discussing this on ``debian-devel`` and checking that it is " +"unique. When this has been checked you must arrange for your package to " +"create the user or group if necessary using ``adduser`` in the " +"``preinst`` or ``postinst`` script (again, the latter is to be preferred " +"if it is possible)." +msgstr "" + +#: ../../ch-files.rst:642 +msgid "" +"Note that changing the numeric value of an id associated with a name is " +"very difficult, and involves searching the file system for all " +"appropriate files. You need to think carefully whether a static or " +"dynamic id is required, since changing your mind later will cause " +"problems." +msgstr "" + +#: ../../ch-files.rst:651 +msgid "The use of ``dpkg-statoverride``" +msgstr "" + +#: ../../ch-files.rst:653 +msgid "" +"This section is not intended as policy, but as a description of the use " +"of ``dpkg-statoverride``." +msgstr "" + +#: ../../ch-files.rst:656 +msgid "" +"If a system administrator wishes to have a file (or directory or other " +"such thing) installed with owner and permissions different from those in " +"the distributed Debian package, they can use the ``dpkg-statoverride`` " +"program to instruct ``dpkg`` to use the different settings every time the" +" file is installed. Thus the package maintainer should distribute the " +"files with their normal permissions, and leave it for the system " +"administrator to make any desired changes. For example, a daemon which is" +" normally required to be setuid root, but in certain situations could be " +"used without being setuid, should be installed setuid in the ``.deb``. " +"Then the local system administrator can change this if they wish. If " +"there are two standard ways of doing it, the package maintainer can use " +"``debconf`` to find out the preference, and call ``dpkg-statoverride`` in" +" the maintainer script if necessary to accommodate the system " +"administrator's choice. Care must be taken during upgrades to not " +"override an existing setting." +msgstr "" + +#: ../../ch-files.rst:672 +msgid "" +"Given the above, ``dpkg-statoverride`` is essentially a tool for system " +"administrators and would not normally be needed in the maintainer " +"scripts. There is one type of situation, though, where calls to ``dpkg-" +"statoverride`` would be needed in the maintainer scripts, and that " +"involves packages which use dynamically allocated user or group ids. In " +"such a situation, something like the following idiom can be very helpful " +"in the package's ``postinst``, where ``sysuser`` is a dynamically " +"allocated id:" +msgstr "" + +#: ../../ch-files.rst:693 +msgid "" +"The corresponding code to remove the override when the package is purged " +"would be:" +msgstr "" + +#: ../../ch-files.rst:707 +msgid "File names" +msgstr "" + +#: ../../ch-files.rst:709 +msgid "" +"The name of the files installed by binary packages in the system PATH " +"(namely ``/bin``, ``/sbin``, ``/usr/bin``, ``/usr/sbin`` and " +"``/usr/games``) must be encoded in ASCII." +msgstr "" + +#: ../../ch-files.rst:713 +msgid "" +"The name of the files and directories installed by binary packages " +"outside the system PATH must be encoded in UTF-8 and should be restricted" +" to ASCII when it is possible to do so." +msgstr "" + +#: ../../ch-files.rst:718 +msgid "" +"If you are using GCC, ``-fPIC`` produces code with relocatable position " +"independent code, which is required for most architectures to create a " +"shared library, with i386 and perhaps some others where non position " +"independent code is permitted in a shared library." +msgstr "" + +#: ../../ch-files.rst:723 +msgid "" +"Position independent code may have a performance penalty, especially on " +"``i386``. However, in most cases the speed penalty must be measured " +"against the memory wasted on the few architectures where non position " +"independent code is even possible." +msgstr "" + +#: ../../ch-files.rst:729 +msgid "" +"Some of the reasons why this might be required is if the library contains" +" hand crafted assembly code that is not relocatable, the speed penalty is" +" excessive for compute intensive libs, and similar reasons." +msgstr "" + +#: ../../ch-files.rst:735 +msgid "" +"Some of the reasons for linking static libraries with the ``-fPIC`` flag " +"are if, for example, one needs a Perl API for a library that is under " +"rapid development, and has an unstable API, so shared libraries are " +"pointless at this phase of the library's development. In that case, since" +" Perl needs a library with relocatable code, it may make sense to create " +"a static library with relocatable code. Another reason cited is if you " +"are distilling various libraries into a common shared library, like " +"``mklibs`` does in the Debian installer project." +msgstr "" + +#: ../../ch-files.rst:745 +msgid "" +"You might also want to use the options ``--remove-section=.comment`` and " +"``--remove-section=.note`` on both shared libraries and executables, and " +"``--strip-debug`` on static libraries." +msgstr "" + +#: ../../ch-files.rst:750 +msgid "" +"A common example are the so-called \"plug-ins\", internal shared objects " +"that are dynamically loaded by programs using dlopen(3)." +msgstr "" + +#: ../../ch-files.rst:754 +msgid "" +"These files store, among other things, all libraries on which that shared" +" library depends. Unfortunately, if the ``.la`` file is present and " +"contains that dependency information, using ``libtool`` when linking " +"against that library will cause the resulting program or library to be " +"linked against those dependencies as well, even if this is unnecessary. " +"This can create unneeded dependencies on shared library packages that " +"would otherwise be hidden behind the library ABI, and can make library " +"transitions to new SONAMEs unnecessarily complicated and difficult to " +"manage." +msgstr "" + +#: ../../ch-files.rst:765 +msgid "" +"The Open Group Base Specifications Issue 7, 2018 Edition, which is also " +"known as POSIX.1-2017 and as IEEE Std 1003.1-2017 and is available on the" +" World Wide Web from `The Open Group " +"<http://pubs.opengroup.org/onlinepubs/9699919799/download/>`_." +msgstr "" + +#: ../../ch-files.rst:771 +msgid "" +"These features are in widespread use in the Linux community and are " +"implemented in all of bash, dash, and ksh, the most common shells users " +"may wish to use as ``/bin/sh``." +msgstr "" + +#: ../../ch-files.rst:776 +msgid "" +"This is necessary to allow top-level directories to be symlinks. If " +"linking ``/var/run`` to ``/run`` were done with the relative symbolic " +"link ``../run``, but ``/var`` were a symbolic link to ``/srv/disk1``, the" +" symbolic link would point to ``/srv/run`` rather than the intended " +"target." +msgstr "" + +#: ../../ch-files.rst:783 +msgid "" +"It's better to use ``mkfifo`` rather than ``mknod`` to create named pipes" +" to avoid false positives from automated checks for packages incorrectly " +"creating device files." +msgstr "" + +#: ../../ch-files.rst:788 +msgid "" +"The ``dpkg-maintscript-helper`` tool, available from the dpkg package, " +"can help for this task." +msgstr "" + +#: ../../ch-files.rst:792 +msgid "" +"Rationale: There are two problems with hard links. The first is that some" +" editors break the link while editing one of the files, so that the two " +"files may unwittingly become unlinked and different. The second is that " +"``dpkg`` might break the hard link while upgrading ``conffile``\\ s." +msgstr "" + +#: ../../ch-files.rst:799 +msgid "" +"The traditional approach to log files has been to set up *ad hoc* log " +"rotation schemes using simple shell scripts and cron. While this approach" +" is highly customizable, it requires quite a lot of sysadmin work. Even " +"though the original Debian system helped a little by automatically " +"installing a system which can be used as a template, this was deemed not " +"enough." +msgstr "" + +#: ../../ch-files.rst:806 +msgid "" +"The use of ``logrotate``, a program developed by Red Hat, is better, as " +"it centralizes log management. It has both a configuration file " +"(``/etc/logrotate.conf``) and a directory where packages can drop their " +"individual log rotation configurations (``/etc/logrotate.d``)." +msgstr "" + +#: ../../ch-files.rst:812 +msgid "" +"When a package is upgraded, and the owner or permissions of a file " +"included in the package has changed, dpkg arranges for the ownership and " +"permissions to be correctly set upon installation. However, this does not" +" extend to directories; the permissions and ownership of directories " +"already on the system does not change on install or upgrade of packages. " +"This makes sense, since otherwise common directories like ``/usr`` would " +"always be in flux. To correctly change permissions of a directory the " +"package owns, explicit action is required, usually in the ``postinst`` " +"script. Care must be taken to handle downgrades as well, in that case." +msgstr "" + +#: ../../ch-files.rst:824 +msgid "" +"Ordinary files installed by ``dpkg`` (as opposed to ``conffile``\\ s and " +"other similar objects) normally have their permissions reset to the " +"distributed permissions when the package is reinstalled. However, the use" +" of ``dpkg-statoverride`` overrides this default behavior." +msgstr "" + diff --git a/locales/ja/LC_MESSAGES/ch-maintainerscripts.po b/locales/ja/LC_MESSAGES/ch-maintainerscripts.po new file mode 100644 index 0000000..26d7c4c --- /dev/null +++ b/locales/ja/LC_MESSAGES/ch-maintainerscripts.po @@ -0,0 +1,751 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1996, 1997, 1998 Ian Jackson, Christian Schwarz, 1998-2017, +# The Debian Policy Mailing List +# This file is distributed under the same license as the Debian Policy +# Manual package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2018. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Debian Policy Manual 4.1.6.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-08-02 11:56+0800\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language-Team: LANGUAGE <LL@li.org>\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.4.0\n" + +#: ../../ch-maintainerscripts.rst:2 +msgid "Package maintainer scripts and installation procedure" +msgstr "" + +#: ../../ch-maintainerscripts.rst:7 +msgid "Introduction to package maintainer scripts" +msgstr "" + +#: ../../ch-maintainerscripts.rst:9 +msgid "" +"It is possible to supply scripts as part of a package which the package " +"management system will run for you when your package is installed, " +"upgraded or removed." +msgstr "" + +#: ../../ch-maintainerscripts.rst:13 +msgid "" +"These scripts are the control information files ``preinst``, " +"``postinst``, ``prerm`` and ``postrm``. They must be proper executable " +"files; if they are scripts (which is recommended), they must start with " +"the usual ``#!`` convention. They should be readable and executable by " +"anyone, and must not be world-writable." +msgstr "" + +#: ../../ch-maintainerscripts.rst:19 +msgid "" +"The package management system looks at the exit status from these " +"scripts. It is important that they exit with a non-zero status if there " +"is an error, so that the package management system can stop its " +"processing. For shell scripts this means that you *almost always* need to" +" use ``set -e`` (this is usually true when writing shell scripts, in " +"fact). It is also important, of course, that they exit with a zero status" +" if everything went well." +msgstr "" + +#: ../../ch-maintainerscripts.rst:27 +msgid "" +"Additionally, packages interacting with users using ``debconf`` in the " +"``postinst`` script should install a ``config`` script as a control " +"information file. See :ref:`s-maintscriptprompt` for details." +msgstr "" + +#: ../../ch-maintainerscripts.rst:32 +msgid "" +"When a package is upgraded a combination of the scripts from the old and " +"new packages is called during the upgrade procedure. If your scripts are " +"going to be at all complicated you need to be aware of this, and may need" +" to check the arguments to your scripts." +msgstr "" + +#: ../../ch-maintainerscripts.rst:37 +msgid "" +"Broadly speaking the ``preinst`` is called before (a particular version " +"of) a package is unpacked, and the ``postinst`` afterwards; the ``prerm``" +" before (a version of) a package is removed and the ``postrm`` " +"afterwards." +msgstr "" + +#: ../../ch-maintainerscripts.rst:42 +msgid "" +"Programs called from maintainer scripts should not normally have a path " +"prepended to them. Before installation is started, the package management" +" system checks to see if the programs ``ldconfig``, ``start-stop-" +"daemon``, and ``update-rc.d`` can be found via the ``PATH`` environment " +"variable. Those programs, and any other program that one would expect to " +"be in the ``PATH``, should thus be invoked without an absolute pathname. " +"Maintainer scripts should also not reset the ``PATH``, though they might " +"choose to modify it by prepending or appending package-specific " +"directories. These considerations really apply to all shell scripts." +msgstr "" + +#: ../../ch-maintainerscripts.rst:56 +msgid "Maintainer scripts idempotency" +msgstr "" + +#: ../../ch-maintainerscripts.rst:58 +msgid "" +"It is necessary for the error recovery procedures that the scripts be " +"idempotent. This means that if it is run successfully, and then it is " +"called again, it doesn't bomb out or cause any harm, but just ensures " +"that everything is the way it ought to be. If the first call failed, or " +"aborted half way through for some reason, the second call should merely " +"do the things that were left undone the first time, if any, and exit with" +" a success status if everything is OK. [#]_" +msgstr "" + +#: ../../ch-maintainerscripts.rst:69 +msgid "Controlling terminal for maintainer scripts" +msgstr "" + +#: ../../ch-maintainerscripts.rst:71 +msgid "" +"Maintainer scripts are not guaranteed to run with a controlling terminal " +"and may not be able to interact with the user. They must be able to fall " +"back to noninteractive behavior if no controlling terminal is available. " +"Maintainer scripts that prompt via a program conforming to the Debian " +"Configuration Management Specification (see :ref:`s-maintscriptprompt`) " +"may assume that program will handle falling back to noninteractive " +"behavior." +msgstr "" + +#: ../../ch-maintainerscripts.rst:79 +msgid "" +"For high-priority prompts without a reasonable default answer, maintainer" +" scripts may abort if there is no controlling terminal. However, this " +"situation should be avoided if at all possible, since it prevents " +"automated or unattended installs. In most cases, users will consider this" +" to be a bug in the package." +msgstr "" + +#: ../../ch-maintainerscripts.rst:88 +msgid "Exit status" +msgstr "" + +#: ../../ch-maintainerscripts.rst:90 +msgid "" +"Each script must return a zero exit status for success, or a nonzero one " +"for failure, since the package management system looks for the exit " +"status of these scripts and determines what action to take next based on " +"that datum." +msgstr "" + +#: ../../ch-maintainerscripts.rst:98 +msgid "Summary of ways maintainer scripts are called" +msgstr "" + +#: ../../ch-maintainerscripts.rst:100 +msgid "" +"What follows is a summary of all the ways in which maintainer scripts may" +" be called along with what facilities those scripts may rely on being " +"available at that time. Script names preceded by new- are the scripts " +"from the new version of a package being installed, upgraded to, or " +"downgraded to. Script names preceded by old- are the scripts from the old" +" version of a package that is being upgraded from or downgraded from." +msgstr "" + +#: ../../ch-maintainerscripts.rst:107 +msgid "The ``preinst`` script may be called in the following ways:" +msgstr "" + +#: ../../ch-maintainerscripts.rst:109 +msgid "``new-preinst`` install" +msgstr "" + +#: ../../ch-maintainerscripts.rst:110 +msgid "``new-preinst`` install *old-version*" +msgstr "" + +#: ../../ch-maintainerscripts.rst:111 +msgid "``new-preinst`` upgrade *old-version*" +msgstr "" + +#: ../../ch-maintainerscripts.rst:113 +msgid "" +"The package will not yet be unpacked, so the ``preinst`` script cannot " +"rely on any files included in its package. Only essential packages and " +"pre-dependencies (``Pre-Depends``) may be assumed to be available. Pre-" +"dependencies will have been configured at least once, but at the time the" +" ``preinst`` is called they may only be in an \"Unpacked\" or \"Half-" +"Configured\" state if a previous version of the pre-dependency was " +"completely configured and has not been removed since then." +msgstr "" + +#: ../../ch-maintainerscripts.rst:129 +msgid "``old-preinst`` abort-upgrade *new-version*" +msgstr "" + +#: ../../ch-maintainerscripts.rst:123 +msgid "" +"Called during error handling of an upgrade that failed after unpacking " +"the new package because the ``postrm upgrade`` action failed. The " +"unpacked files may be partly from the new version or partly missing, so " +"the script cannot rely on files included in the package. Package " +"dependencies may not be available. Pre-dependencies will be at least " +"\"Unpacked\" following the same rules as above, except they may be only " +"\"Half-Installed\" if an upgrade of the pre-dependency failed. [#]_" +msgstr "" + +#: ../../ch-maintainerscripts.rst:131 +msgid "The ``postinst`` script may be called in the following ways:" +msgstr "" + +#: ../../ch-maintainerscripts.rst:138 +msgid "``postinst`` configure *most-recently-configured-version*" +msgstr "" + +#: ../../ch-maintainerscripts.rst:134 +msgid "" +"The files contained in the package will be unpacked. All package " +"dependencies will at least be \"Unpacked\". If there are no circular " +"dependencies involved, all package dependencies will be configured. For " +"behavior in the case of circular dependencies, see the discussion in " +":ref:`s-binarydeps`." +msgstr "" + +#: ../../ch-maintainerscripts.rst:140 +msgid "``old-postinst`` abort-upgrade *new-version*" +msgstr "" + +#: ../../ch-maintainerscripts.rst:141 +msgid "``conflictor's-postinst`` abort-remove in-favour *package* *new-version*" +msgstr "" + +#: ../../ch-maintainerscripts.rst:142 +msgid "``postinst`` abort-remove" +msgstr "" + +#: ../../ch-maintainerscripts.rst:143 +msgid "" +"``deconfigured's-postinst`` abort-deconfigure in-favour *failed-install-" +"package* *version* [ removing conflicting-package version ]" +msgstr "" + +#: ../../ch-maintainerscripts.rst:145 +msgid "" +"The files contained in the package will be unpacked. All package " +"dependencies will at least be \"Half-Installed\" and will have previously" +" been configured and not removed. However, dependencies may not be " +"configured or even fully unpacked in some error situations. [#]_ The " +"``postinst`` should still attempt any actions for which its dependencies " +"are required, since they will normally be available, but consider the " +"correct error handling approach if those actions fail. Aborting the " +"``postinst`` action if commands or facilities from the package " +"dependencies are not available is often the best approach." +msgstr "" + +#: ../../ch-maintainerscripts.rst:156 +msgid "The ``prerm`` script may be called in the following ways:" +msgstr "" + +#: ../../ch-maintainerscripts.rst:158 +msgid "``prerm`` remove" +msgstr "" + +#: ../../ch-maintainerscripts.rst:159 +msgid "``old-prerm`` upgrade *new-version*" +msgstr "" + +#: ../../ch-maintainerscripts.rst:160 +msgid "``conflictor's-prerm`` remove in-favour package *new-version*" +msgstr "" + +#: ../../ch-maintainerscripts.rst:161 +msgid "" +"``deconfigured's-prerm`` deconfigure in-favour *package-being-installed* " +"*version* [removing conflicting-package version]" +msgstr "" + +#: ../../ch-maintainerscripts.rst:163 +msgid "" +"The package whose ``prerm`` is being called will be at least \"Half-" +"Installed\". All package dependencies will at least be \"Half-Installed\"" +" and will have previously been configured and not removed. If there was " +"no error, all dependencies will at least be \"Unpacked\", but these " +"actions may be called in various error states where dependencies are only" +" \"Half-Installed\" due to a partial upgrade." +msgstr "" + +#: ../../ch-maintainerscripts.rst:174 +msgid "``new-prerm`` failed-upgrade *old-version*" +msgstr "" + +#: ../../ch-maintainerscripts.rst:172 +msgid "" +"Called during error handling when ``prerm upgrade`` fails. The new " +"package will not yet be unpacked, and all the same constraints as for " +"``preinst upgrade`` apply." +msgstr "" + +#: ../../ch-maintainerscripts.rst:176 +msgid "The ``postrm`` script may be called in the following ways:" +msgstr "" + +#: ../../ch-maintainerscripts.rst:178 +msgid "``postrm`` remove" +msgstr "" + +#: ../../ch-maintainerscripts.rst:179 +msgid "``postrm`` purge" +msgstr "" + +#: ../../ch-maintainerscripts.rst:180 +msgid "``old-postrm`` upgrade *new-version*" +msgstr "" + +#: ../../ch-maintainerscripts.rst:181 +msgid "``disappearer's-postrm`` disappear overwriter *overwriter-version*" +msgstr "" + +#: ../../ch-maintainerscripts.rst:183 +msgid "" +"The ``postrm`` script is called after the package's files have been " +"removed or replaced. The package whose ``postrm`` is being called may " +"have previously been deconfigured and only be \"Unpacked\", at which " +"point subsequent package changes do not consider its dependencies. " +"Therefore, all ``postrm`` actions may only rely on essential packages and" +" must gracefully skip any actions that require the package's dependencies" +" if those dependencies are unavailable. [#]_" +msgstr "" + +#: ../../ch-maintainerscripts.rst:197 +msgid "``new-postrm`` failed-upgrade *old-version*" +msgstr "" + +#: ../../ch-maintainerscripts.rst:193 +msgid "" +"Called when the old ``postrm upgrade`` action fails. The new package will" +" be unpacked, but only essential packages and pre-dependencies can be " +"relied on. Pre-dependencies will either be configured or will be " +"\"Unpacked\" or \"Half-Configured\" but previously had been configured " +"and was never removed." +msgstr "" + +#: ../../ch-maintainerscripts.rst:199 +msgid "``new-postrm`` abort-install" +msgstr "" + +#: ../../ch-maintainerscripts.rst:200 +msgid "``new-postrm`` abort-install *old-version*" +msgstr "" + +#: ../../ch-maintainerscripts.rst:201 +msgid "``new-postrm`` abort-upgrade *old-version*" +msgstr "" + +#: ../../ch-maintainerscripts.rst:203 +msgid "" +"Called before unpacking the new package as part of the error handling of " +"``preinst`` failures. May assume the same state as ``preinst`` can " +"assume." +msgstr "" + +#: ../../ch-maintainerscripts.rst:210 +msgid "Details of unpack phase of installation or upgrade" +msgstr "" + +#: ../../ch-maintainerscripts.rst:212 +msgid "" +"The procedure on installation/upgrade/overwrite/disappear (i.e., when " +"running ``dpkg --unpack``, or the unpack stage of ``dpkg --install``) is " +"as follows. [#]_ In each case, if a major error occurs (unless listed " +"below) the actions are, in general, run backwards - this means that the " +"maintainer scripts are run with different arguments in reverse order. " +"These are the \"error unwind\" calls listed below." +msgstr "" + +#: ../../ch-maintainerscripts.rst:219 +msgid "Notify the currently installed package:" +msgstr "" + +#: ../../ch-maintainerscripts.rst:221 +msgid "If a version of the package is already \"Installed\", call" +msgstr "" + +#: ../../ch-maintainerscripts.rst:227 +msgid "" +"If the script runs but exits with a non-zero exit status, ``dpkg`` will " +"attempt:" +msgstr "" + +#: ../../ch-maintainerscripts.rst:234 +msgid "" +"If this works, the upgrade continues. If this does not work, the error " +"unwind:" +msgstr "" + +#: ../../ch-maintainerscripts.rst:241 +msgid "" +"If this works, then the *old-version* is \"Installed\", if not, the old " +"version is in a \"Half-Configured\" state." +msgstr "" + +#: ../../ch-maintainerscripts.rst:244 +msgid "" +"If a \"conflicting\" package is being removed at the same time, or if any" +" package will be broken (due to ``Breaks``):" +msgstr "" + +#: ../../ch-maintainerscripts.rst:247 +msgid "" +"If ``--auto-deconfigure`` is specified, call, for each package to be " +"deconfigured due to ``Breaks``:" +msgstr "" + +#: ../../ch-maintainerscripts.rst:255 ../../ch-maintainerscripts.rst:276 +#: ../../ch-maintainerscripts.rst:295 ../../ch-maintainerscripts.rst:336 +#: ../../ch-maintainerscripts.rst:352 +msgid "Error unwind:" +msgstr "" + +#: ../../ch-maintainerscripts.rst:262 ../../ch-maintainerscripts.rst:284 +msgid "" +"The deconfigured packages are marked as requiring configuration, so that " +"if ``--install`` is used they will be configured again if possible." +msgstr "" + +#: ../../ch-maintainerscripts.rst:266 +msgid "" +"If any packages depended on a conflicting package being removed and " +"``--auto-deconfigure`` is specified, call, for each such package:" +msgstr "" + +#: ../../ch-maintainerscripts.rst:288 +msgid "To prepare for removal of each conflicting package, call:" +msgstr "" + +#: ../../ch-maintainerscripts.rst:302 +msgid "Run the ``preinst`` of the new package:" +msgstr "" + +#: ../../ch-maintainerscripts.rst:304 +msgid "If the package is being upgraded, call:" +msgstr "" + +#: ../../ch-maintainerscripts.rst:310 +msgid "If this fails, we call:" +msgstr "" + +#: ../../ch-maintainerscripts.rst:316 +msgid "If that works, then" +msgstr "" + +#: ../../ch-maintainerscripts.rst:322 +msgid "" +"is called. If this works, then the old version is in an \"Installed\" " +"state, or else it is left in an \"Unpacked\" state." +msgstr "" + +#: ../../ch-maintainerscripts.rst:325 +msgid "If it fails, then the old version is left in an \"Half-Installed\" state." +msgstr "" + +#: ../../ch-maintainerscripts.rst:328 +msgid "" +"Otherwise, if the package had some configuration files from a previous " +"version installed (i.e., it is in the \"Config-Files\" state):" +msgstr "" + +#: ../../ch-maintainerscripts.rst:342 +msgid "" +"If this fails, the package is left in a \"Half-Installed\" state, which " +"requires a reinstall. If it works, the packages is left in a \"Config-" +"Files\" state." +msgstr "" + +#: ../../ch-maintainerscripts.rst:346 +msgid "Otherwise (i.e., the package was completely purged):" +msgstr "" + +#: ../../ch-maintainerscripts.rst:358 +msgid "" +"If the error-unwind fails, the package is in a \"Half-Installed\" phase, " +"and requires a reinstall. If the error unwind works, the package is in " +"the \"Not-Installed\" state." +msgstr "" + +#: ../../ch-maintainerscripts.rst:362 +msgid "" +"The new package's files are unpacked, overwriting any that may be on the " +"system already, for example any from the old version of the same package " +"or from another package. Backups of the old files are kept temporarily, " +"and if anything goes wrong the package management system will attempt to " +"put them back as part of the error unwind." +msgstr "" + +#: ../../ch-maintainerscripts.rst:368 +msgid "" +"It is an error for a package to contain files which are on the system in " +"another package, unless ``Replaces`` is used (see :ref:`s-replaces`)." +msgstr "" + +#: ../../ch-maintainerscripts.rst:372 +msgid "" +"It is a more serious error for a package to contain a plain file or other" +" kind of non-directory where another package has a directory (again, " +"unless ``Replaces`` is used). This error can be overridden if desired " +"using ``--force-overwrite-dir``, but this is not advisable." +msgstr "" + +#: ../../ch-maintainerscripts.rst:378 +msgid "" +"Packages which overwrite each other's files produce behavior which, " +"though deterministic, is hard for the system administrator to understand." +" It can easily lead to \"missing\" programs if, for example, a package is" +" unpacked which overwrites a file from another package, and is then " +"removed again. [#]_" +msgstr "" + +#: ../../ch-maintainerscripts.rst:384 +msgid "" +"A directory will never be replaced by a symbolic link to a directory or " +"vice versa; instead, the existing state (symlink or not) will be left " +"alone and ``dpkg`` will follow the symlink if there is one." +msgstr "" + +#: ../../ch-maintainerscripts.rst:388 +msgid "If the package is being upgraded:" +msgstr "" + +#: ../../ch-maintainerscripts.rst:390 +msgid "Call:" +msgstr "" + +#: ../../ch-maintainerscripts.rst:396 +msgid "If this fails, ``dpkg`` will attempt:" +msgstr "" + +#: ../../ch-maintainerscripts.rst:402 +msgid "If this works, installation continues. If not, Error unwind:" +msgstr "" + +#: ../../ch-maintainerscripts.rst:408 ../../ch-maintainerscripts.rst:415 +msgid "" +"If this fails, the old version is left in a \"Half-Installed\" state. If " +"it works, dpkg now calls:" +msgstr "" + +#: ../../ch-maintainerscripts.rst:422 +msgid "If this fails, the old version is in an \"Unpacked\" state." +msgstr "" + +#: ../../ch-maintainerscripts.rst:424 +msgid "" +"This is the point of no return. If ``dpkg`` gets this far, it won't back " +"off past this point if an error occurs. This will leave the package in a " +"fairly bad state, which will require a successful re-installation to " +"clear up, but it's when ``dpkg`` starts doing things that are " +"irreversible." +msgstr "" + +#: ../../ch-maintainerscripts.rst:430 +msgid "" +"Any files which were in the old version of the package but not in the new" +" are removed." +msgstr "" + +#: ../../ch-maintainerscripts.rst:433 +msgid "The new file list replaces the old." +msgstr "" + +#: ../../ch-maintainerscripts.rst:435 +msgid "The new maintainer scripts replace the old." +msgstr "" + +#: ../../ch-maintainerscripts.rst:437 +msgid "" +"Any packages all of whose files have been overwritten during the " +"installation, and which aren't required for dependencies, are considered " +"to have been removed. For each such package" +msgstr "" + +#: ../../ch-maintainerscripts.rst:441 +msgid "``dpkg`` calls:" +msgstr "" + +#: ../../ch-maintainerscripts.rst:448 +msgid "The package's maintainer scripts are removed." +msgstr "" + +#: ../../ch-maintainerscripts.rst:450 +msgid "" +"It is noted in the status database as being in a sane state, namely " +"\"Not-Installed\" (any conffiles it may have are ignored, rather than " +"being removed by ``dpkg``). Note that disappearing packages do not have " +"their prerm called, because ``dpkg`` doesn't know in advance that the " +"package is going to vanish." +msgstr "" + +#: ../../ch-maintainerscripts.rst:456 +msgid "" +"Any files in the package we're unpacking that are also listed in the file" +" lists of other packages are removed from those lists. (This will " +"lobotomize the file list of the \"conflicting\" package if there is one.)" +msgstr "" + +#: ../../ch-maintainerscripts.rst:461 +msgid "The backup files made during installation, above, are deleted." +msgstr "" + +#: ../../ch-maintainerscripts.rst:463 +msgid "The new package's status is now sane, and recorded as \"Unpacked\"." +msgstr "" + +#: ../../ch-maintainerscripts.rst:465 +msgid "" +"Here is another point of no return: if the conflicting package's removal " +"fails we do not unwind the rest of the installation. The conflicting " +"package is left in a half-removed limbo." +msgstr "" + +#: ../../ch-maintainerscripts.rst:469 +msgid "" +"If there was a conflicting package we go and do the removal actions " +"(described below), starting with the removal of the conflicting package's" +" files (any that are also in the package being unpacked have already been" +" removed from the conflicting package's file list, and so do not get " +"removed now)." +msgstr "" + +#: ../../ch-maintainerscripts.rst:478 +msgid "Details of configuration" +msgstr "" + +#: ../../ch-maintainerscripts.rst:480 +msgid "" +"When we configure a package (this happens with ``dpkg --install`` and " +"``dpkg --configure``), we first update any ``conffile``\\ s and then " +"call:" +msgstr "" + +#: ../../ch-maintainerscripts.rst:487 +msgid "" +"No attempt is made to unwind after errors during configuration. If the " +"configuration fails, the package is in a \"Half-Configured\" state, and " +"an error message is generated." +msgstr "" + +#: ../../ch-maintainerscripts.rst:491 +msgid "" +"If there is no most recently configured version ``dpkg`` will pass a null" +" argument. [#]_" +msgstr "" + +#: ../../ch-maintainerscripts.rst:497 +msgid "Details of removal and/or configuration purging" +msgstr "" + +#: ../../ch-maintainerscripts.rst:503 +msgid "If prerm fails during replacement due to conflict" +msgstr "" + +#: ../../ch-maintainerscripts.rst:510 +msgid "Or else we call:" +msgstr "" + +#: ../../ch-maintainerscripts.rst:516 +msgid "" +"If this fails, the package is in a \"Half-Configured\" state, or else it " +"remains \"Installed\"." +msgstr "" + +#: ../../ch-maintainerscripts.rst:519 +msgid "The package's files are removed (except ``conffile``\\ s)." +msgstr "" + +#: ../../ch-maintainerscripts.rst:525 +msgid "" +"If it fails, there's no error unwind, and the package is in an \"Half-" +"Installed\" state." +msgstr "" + +#: ../../ch-maintainerscripts.rst:528 +msgid "All the maintainer scripts except the ``postrm`` are removed." +msgstr "" + +#: ../../ch-maintainerscripts.rst:530 +msgid "" +"If we aren't purging the package we stop here. Note that packages which " +"have no ``postrm`` and no ``conffile``\\ s are automatically purged when " +"removed, as there is no difference except for the ``dpkg`` status." +msgstr "" + +#: ../../ch-maintainerscripts.rst:535 +msgid "" +"The ``conffile``\\ s and any backup files (``~``-files, ``#*#`` files, " +"``%``-files, ``.dpkg-{old,new,tmp}``, etc.) are removed." +msgstr "" + +#: ../../ch-maintainerscripts.rst:542 +msgid "If this fails, the package remains in a \"Config-Files\" state." +msgstr "" + +#: ../../ch-maintainerscripts.rst:544 +msgid "The package's file list is removed." +msgstr "" + +#: ../../ch-maintainerscripts.rst:547 +msgid "" +"This is so that if an error occurs, the user interrupts ``dpkg`` or some " +"other unforeseen circumstance happens you don't leave the user with a " +"badly-broken package when ``dpkg`` attempts to repeat the action." +msgstr "" + +#: ../../ch-maintainerscripts.rst:553 +msgid "" +"This can happen if the new version of the package no longer pre-depends " +"on a package that had been partially upgraded." +msgstr "" + +#: ../../ch-maintainerscripts.rst:557 +msgid "" +"For example, suppose packages foo and bar are \"Installed\" with foo " +"depending on bar. If an upgrade of bar were started and then aborted, and" +" then an attempt to remove foo failed because its ``prerm`` script " +"failed, foo's ``postinst abort-remove`` would be called with bar only " +"\"Half-Installed\"." +msgstr "" + +#: ../../ch-maintainerscripts.rst:564 +msgid "" +"This is often done by checking whether the command or facility the " +"``postrm`` intends to call is available before calling it. For example:" +msgstr "" + +#: ../../ch-maintainerscripts.rst:574 +msgid "" +"in ``postrm`` purges the ``debconf`` configuration for the package if " +"debconf is installed." +msgstr "" + +#: ../../ch-maintainerscripts.rst:578 +msgid "" +"See :doc:`ap-flowcharts` for flowcharts illustrating the processes " +"described here." +msgstr "" + +#: ../../ch-maintainerscripts.rst:582 +msgid "Part of the problem is due to what is arguably a bug in ``dpkg``." +msgstr "" + +#: ../../ch-maintainerscripts.rst:585 +msgid "" +"Historical note: Truly ancient (pre-1997) versions of ``dpkg`` passed " +"``<unknown>`` (including the angle brackets) in this case. Even older " +"ones did not pass a second argument at all, under any circumstance. Note " +"that upgrades using such an old dpkg version are unlikely to work for " +"other reasons, even if this old argument behavior is handled by your " +"postinst script." +msgstr "" + diff --git a/locales/ja/LC_MESSAGES/ch-opersys.po b/locales/ja/LC_MESSAGES/ch-opersys.po new file mode 100644 index 0000000..ab1ff44 --- /dev/null +++ b/locales/ja/LC_MESSAGES/ch-opersys.po @@ -0,0 +1,1503 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1996, 1997, 1998 Ian Jackson, Christian Schwarz, 1998-2017, +# The Debian Policy Mailing List +# This file is distributed under the same license as the Debian Policy +# Manual package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2018. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Debian Policy Manual 4.1.6.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-08-02 11:56+0800\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language-Team: LANGUAGE <LL@li.org>\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.4.0\n" + +#: ../../ch-opersys.rst:2 +msgid "The Operating System" +msgstr "" + +#: ../../ch-opersys.rst:7 +msgid "File system hierarchy" +msgstr "" + +#: ../../ch-opersys.rst:12 +msgid "File System Structure" +msgstr "" + +#: ../../ch-opersys.rst:14 +msgid "" +"The location of all files and directories must comply with the Filesystem" +" Hierarchy Standard (FHS), version 3.0, with the exceptions noted below, " +"and except where doing so would violate other terms of Debian Policy. The" +" following exceptions to the FHS apply:" +msgstr "" + +#: ../../ch-opersys.rst:19 +msgid "" +"The FHS requirement that architecture-independent application-specific " +"static files be located in ``/usr/share`` is relaxed to a suggestion. In " +"particular, a subdirectory of ``/usr/lib`` may be used by a package (or a" +" collection of packages) to hold a mixture of architecture-independent " +"and architecture-dependent files. However, when a directory is entirely " +"composed of architecture-independent files, it should be located in " +"``/usr/share``." +msgstr "" + +#: ../../ch-opersys.rst:28 +msgid "" +"The optional rules related to user specific configuration files for " +"applications are stored in the user's home directory are relaxed. It is " +"recommended that such files start with the '``.``' character (a \"dot " +"file\"), and if an application needs to create more than one dot file " +"then the preferred placement is in a subdirectory with a name starting " +"with a '.' character, (a \"dot directory\"). In this case it is " +"recommended the configuration files not start with the '.' character." +msgstr "" + +#: ../../ch-opersys.rst:37 +msgid "" +"Only the dynamic linker and libc are allowed to install files in " +"``/lib64``." +msgstr "" + +#: ../../ch-opersys.rst:40 +msgid "" +"The requirement for object files, internal binaries, and libraries, " +"including ``libc.so.*``, to be located directly under ``/lib{,32}`` and " +"``/usr/lib{,32}`` is amended, permitting files to instead be installed to" +" ``/lib/triplet`` and ``/usr/lib/triplet``, where ``triplet`` is the " +"value returned by ``dpkg-architecture -qDEB_HOST_MULTIARCH`` for the " +"architecture of the package. Packages may *not* install files to any " +"triplet path other than the one matching the architecture of that " +"package; for instance, an ``Architecture: amd64`` package containing " +"32-bit x86 libraries may not install these libraries to ``/usr/lib/i386" +"-linux-gnu``. [#]_" +msgstr "" + +#: ../../ch-opersys.rst:51 +msgid "" +"No package for a 64 bit architecture may install files in ``/usr/lib64/``" +" or in a subdirectory of it." +msgstr "" + +#: ../../ch-opersys.rst:54 +msgid "" +"The requirement for C and C++ headers files to be accessible through the " +"search path ``/usr/include/`` is amended, permitting files to be " +"accessible through the search path ``/usr/include/triplet`` where " +"``triplet`` is as above. [#]_" +msgstr "" + +#: ../../ch-opersys.rst:59 +msgid "" +"Applications may also use a single subdirectory under " +"``/usr/lib/triplet``." +msgstr "" + +#: ../../ch-opersys.rst:62 +msgid "" +"The execution time linker/loader, ld\\*, must still be made available in " +"the existing location under /lib or /lib64 since this is part of the ELF " +"ABI for the architecture." +msgstr "" + +#: ../../ch-opersys.rst:66 +msgid "" +"The requirement that ``/usr/local/share/man`` be \"synonymous\" with " +"``/usr/local/man`` is relaxed to a recommendation" +msgstr "" + +#: ../../ch-opersys.rst:69 +msgid "" +"The requirement that window managers with a single configuration file " +"call it ``system.*wmrc`` is removed, as is the restriction that the " +"window manager subdirectory be named identically to the window manager " +"name itself." +msgstr "" + +#: ../../ch-opersys.rst:74 +msgid "" +"The requirement that boot manager configuration files live in ``/etc``, " +"or at least are symlinked there, is relaxed to a recommendation." +msgstr "" + +#: ../../ch-opersys.rst:78 +msgid "" +"``/var/run`` is required to be a symbolic link to ``/run``, and " +"``/var/lock`` is required to be a symbolic link to ``/run/lock``." +msgstr "" + +#: ../../ch-opersys.rst:81 +msgid "The ``/var/www`` directory is additionally allowed." +msgstr "" + +#: ../../ch-opersys.rst:83 +msgid "" +"The requirement for ``/usr/local/share/color`` to exist if " +"``/usr/share/color`` exists is relaxed to a recommendation." +msgstr "" + +#: ../../ch-opersys.rst:86 +msgid "" +"The requirement for ``/usr/local/libqual`` to exist if ``/libqual`` or " +"``/usr/libqual`` exists (where ``libqual`` is a variant of ``lib`` such " +"as ``lib32`` or ``lib64``) is removed." +msgstr "" + +#: ../../ch-opersys.rst:90 +msgid "" +"On GNU/Hurd systems, the following additional directories are allowed in " +"the root filesystem: ``/hurd`` and ``/servers``. [#]_" +msgstr "" + +#: ../../ch-opersys.rst:93 +msgid "" +"As an exception to the requirement for there to be no subdirectories in " +"``/usr/bin``, the ``mh`` mail-handling suite may create ``/usr/bin/mh/``," +" as was allowed in FHS version 2.3. Other subdirectories are not allowed." +msgstr "" + +#: ../../ch-opersys.rst:98 +msgid "" +"The version of this document referred here can be found in the ``debian-" +"policy`` package or on `FHS (Debian copy) <https://www.debian.org/doc" +"/packaging-manuals/fhs/>`_ alongside this manual (or, if you have the " +"debian-policy installed, you can try `FHS (local copy) " +"<file:///usr/share/doc/debian-policy/fhs/>`_). The latest version, which " +"may be a more recent version, may be found on `FHS (upstream) " +"<http://refspecs.linuxfoundation.org/fhs.shtml>`_. Specific questions " +"about following the standard may be asked on the ``debian-devel`` mailing" +" list, or referred to the FHS mailing list (see the `FHS web site " +"<http://refspecs.linuxfoundation.org/fhs.shtml>`_ for more information)." +msgstr "" + +#: ../../ch-opersys.rst:113 +msgid "Site-specific programs" +msgstr "" + +#: ../../ch-opersys.rst:115 +msgid "" +"As mandated by the FHS, packages must not place any files in " +"``/usr/local``, either by putting them in the file system archive to be " +"unpacked by ``dpkg`` or by manipulating them in their maintainer scripts." +msgstr "" + +#: ../../ch-opersys.rst:120 +msgid "" +"However, the package may create empty directories below ``/usr/local`` so" +" that the system administrator knows where to place site-specific files. " +"These are not directories *in* ``/usr/local``, but are children of " +"directories in ``/usr/local``. These directories (``/usr/local/*/dir/``) " +"should be removed on package removal if they are empty." +msgstr "" + +#: ../../ch-opersys.rst:127 +msgid "" +"Note that this applies only to directories *below* ``/usr/local``, not " +"*in* ``/usr/local``. Packages must not create sub-directories in the " +"directory ``/usr/local`` itself, except those listed in FHS, section 4.5." +" However, you may create directories below them as you wish. You must not" +" remove any of the directories listed in 4.5, even if you created them." +msgstr "" + +#: ../../ch-opersys.rst:134 +msgid "" +"If ``/etc/staff-group-for-usr-local`` does not exist, ``/usr/local`` and " +"all subdirectories created by packages should have permissions 0755 and " +"be owned by ``root:root``. If ``/etc/staff-group-for-usr-local`` exists," +" ``/usr/local`` and subdirectories should have permissions 2775 (group-" +"writable and set-group-id) and be owned by ``root:staff``." +msgstr "" + +#: ../../ch-opersys.rst:141 +msgid "" +"Since ``/usr/local`` can be mounted read-only from a remote server, " +"``/usr/local/*/dir/`` directories must be created and removed by the " +"``postinst`` and ``prerm`` maintainer scripts and not be included in the " +"``.deb`` archive. These scripts must not fail if either of these " +"operations fail." +msgstr "" + +#: ../../ch-opersys.rst:147 +msgid "For example, the ``emacsen-common`` package could contain something like" +msgstr "" + +#: ../../ch-opersys.rst:163 +msgid "in its ``postinst`` script, and" +msgstr "" + +#: ../../ch-opersys.rst:170 +msgid "" +"in the ``prerm`` script. (Note that this form is used to ensure that if " +"the script is interrupted, the directory ``/usr/local/share/emacs`` will " +"still be removed.)" +msgstr "" + +#: ../../ch-opersys.rst:174 +msgid "" +"If you do create a directory in ``/usr/local`` for local additions to a " +"package, you should ensure that settings in ``/usr/local`` take " +"precedence over the equivalents in ``/usr``." +msgstr "" + +#: ../../ch-opersys.rst:178 +msgid "" +"However, because ``/usr/local`` and its contents are for exclusive use of" +" the local administrator, a package must not rely on the presence or " +"absence of files or directories in ``/usr/local`` for normal operation." +msgstr "" + +#: ../../ch-opersys.rst:185 +msgid "The system-wide mail directory" +msgstr "" + +#: ../../ch-opersys.rst:187 +msgid "" +"The system-wide mail directory is ``/var/mail``. This directory is part " +"of the base system and should not be owned by any particular mail agents." +" The use of the old location ``/var/spool/mail`` is deprecated, even " +"though the spool may still be physically located there." +msgstr "" + +#: ../../ch-opersys.rst:195 +msgid "``/run`` and ``/run/lock``" +msgstr "" + +#: ../../ch-opersys.rst:197 +msgid "" +"The directory ``/run`` is cleared at boot, normally by being a mount " +"point for a temporary file system. Packages therefore must not assume " +"that any files or directories under ``/run`` other than ``/run/lock`` " +"exist unless the package has arranged to create those files or " +"directories since the last reboot. Normally, this is done by the package " +"via an init script. See :ref:`s-writing-init` for more information." +msgstr "" + +#: ../../ch-opersys.rst:205 +msgid "" +"Packages must not include files or directories under ``/run``, or under " +"the older ``/var/run`` and ``/var/lock`` paths. The latter paths will " +"normally be symlinks or other redirections to ``/run`` for backwards " +"compatibility." +msgstr "" + +#: ../../ch-opersys.rst:213 +msgid "Users and groups" +msgstr "" + +#: ../../ch-opersys.rst:218 ../../ch-opersys.rst:326 +msgid "Introduction" +msgstr "" + +#: ../../ch-opersys.rst:220 +msgid "" +"The Debian system can be configured to use either plain or shadow " +"passwords." +msgstr "" + +#: ../../ch-opersys.rst:223 +msgid "" +"Some user ids (UIDs) and group ids (GIDs) are reserved globally for use " +"by certain packages. Because some packages need to include files which " +"are owned by these users or groups, or need the ids compiled into " +"binaries, these ids must be used on any Debian system only for the " +"purpose for which they are allocated. This is a serious restriction, and " +"we should avoid getting in the way of local administration policies. In " +"particular, many sites allocate users and/or local system groups starting" +" at 100." +msgstr "" + +#: ../../ch-opersys.rst:232 +msgid "" +"Apart from this we should have dynamically allocated ids, which should by" +" default be arranged in some sensible order, but the behavior should be " +"configurable." +msgstr "" + +#: ../../ch-opersys.rst:236 +msgid "" +"Packages other than ``base-passwd`` must not modify ``/etc/passwd``, " +"``/etc/shadow``, ``/etc/group`` or ``/etc/gshadow``." +msgstr "" + +#: ../../ch-opersys.rst:242 +msgid "UID and GID classes" +msgstr "" + +#: ../../ch-opersys.rst:244 +msgid "The UID and GID numbers are divided into classes as follows:" +msgstr "" + +#: ../../ch-opersys.rst:254 +msgid "0-99:" +msgstr "" + +#: ../../ch-opersys.rst:247 +msgid "" +"Globally allocated by the Debian project, the same on every Debian " +"system. These ids will appear in the ``passwd`` and ``group`` files of " +"all Debian systems, new ids in this range being added automatically as " +"the ``base-passwd`` package is updated." +msgstr "" + +#: ../../ch-opersys.rst:252 +msgid "" +"Packages which need a single statically allocated uid or gid should use " +"one of these; their maintainers should ask the ``base-passwd`` maintainer" +" for ids." +msgstr "" + +#: ../../ch-opersys.rst:262 +msgid "100-999:" +msgstr "" + +#: ../../ch-opersys.rst:257 +msgid "" +"Dynamically allocated system users and groups. Packages which need a user" +" or group, but can have this user or group allocated dynamically and " +"differently on each system, should use ``adduser --system`` to create the" +" group and/or user. ``adduser`` will check for the existence of the user " +"or group, and if necessary choose an unused id based on the ranges " +"specified in ``adduser.conf``." +msgstr "" + +#: ../../ch-opersys.rst:267 +msgid "1000-59999:" +msgstr "" + +#: ../../ch-opersys.rst:265 +msgid "" +"Dynamically allocated user accounts. By default ``adduser`` will choose " +"UIDs and GIDs for user accounts in this range, though ``adduser.conf`` " +"may be used to modify this behavior." +msgstr "" + +#: ../../ch-opersys.rst:279 +msgid "60000-64999:" +msgstr "" + +#: ../../ch-opersys.rst:270 +msgid "" +"Globally allocated by the Debian project, but only created on demand. The" +" ids are allocated centrally and statically, but the actual accounts are " +"only created on users' systems on demand." +msgstr "" + +#: ../../ch-opersys.rst:274 +msgid "" +"These ids are for packages which are obscure or which require many " +"statically-allocated ids. These packages should check for and create the " +"accounts in ``/etc/passwd`` or ``/etc/group`` (using ``adduser`` if it " +"has this facility) if necessary. Packages which are likely to require " +"further allocations should have a \"hole\" left after them in the " +"allocation, to give them room to grow." +msgstr "" + +#: ../../ch-opersys.rst:282 +msgid "65000-65533:" +msgstr "" + +#: ../../ch-opersys.rst:282 +msgid "Reserved." +msgstr "" + +#: ../../ch-opersys.rst:286 +msgid "65534:" +msgstr "" + +#: ../../ch-opersys.rst:285 +msgid "User ``nobody``. The corresponding gid refers to the group ``nogroup``." +msgstr "" + +#: ../../ch-opersys.rst:290 +msgid "65535:" +msgstr "" + +#: ../../ch-opersys.rst:289 +msgid "" +"This value *must not* be used, because it was the error return sentinel " +"value when ``uid_t`` was 16 bits." +msgstr "" + +#: ../../ch-opersys.rst:295 +msgid "65536-4294967293:" +msgstr "" + +#: ../../ch-opersys.rst:293 +msgid "" +"Dynamically allocated user accounts. By default ``adduser`` will not " +"allocate UIDs and GIDs in this range, to ease compatibility with legacy " +"systems where ``uid_t`` is still 16 bits." +msgstr "" + +#: ../../ch-opersys.rst:300 +msgid "4294967294:" +msgstr "" + +#: ../../ch-opersys.rst:298 +msgid "" +"``(uid_t)(-2) == (gid_t)(-2)`` *must not* be used, because it is used as " +"the anonymous, unauthenticated user by some NFS implementations." +msgstr "" + +#: ../../ch-opersys.rst:304 +msgid "4294967295:" +msgstr "" + +#: ../../ch-opersys.rst:303 +msgid "" +"``(uid_t)(-1) == (gid_t)(-1)`` *must not* be used, because it is the " +"error return sentinel value." +msgstr "" + +#: ../../ch-opersys.rst:309 +msgid "Non-existent home directories" +msgstr "" + +#: ../../ch-opersys.rst:311 +msgid "" +"The canonical non-existent home directory is ``/nonexistent``. Users who" +" should not have a home directory should have their home directory set to" +" this value." +msgstr "" + +#: ../../ch-opersys.rst:315 +msgid "" +"The Debian autobuilders set HOME to ``/nonexistent`` so that packages " +"which try to write to a home directory will fail to build." +msgstr "" + +#: ../../ch-opersys.rst:321 +msgid "System run levels and ``init.d`` scripts" +msgstr "" + +#: ../../ch-opersys.rst:328 +msgid "" +"The ``/etc/init.d`` directory contains the scripts executed by ``init`` " +"at boot time and when the init state (or \"runlevel\") is changed (see " +"``init(8)``)." +msgstr "" + +#: ../../ch-opersys.rst:332 +msgid "" +"There are at least two different, yet functionally equivalent, ways of " +"handling these scripts. For the sake of simplicity, this document " +"describes only the symbolic link method. However, it must not be assumed " +"by maintainer scripts that this method is being used, and any automated " +"manipulation of the various runlevel behaviors by maintainer scripts must" +" be performed using ``update-rc.d`` as described below and not by " +"manually installing or removing symlinks. For information on the " +"implementation details of the other method, implemented in the ``file-" +"rc`` package, please refer to the documentation of that package." +msgstr "" + +#: ../../ch-opersys.rst:342 +msgid "" +"These scripts are referenced by symbolic links in the ``/etc/rcn.d`` " +"directories. When changing runlevels, ``init`` looks in the directory " +"``/etc/rcn.d`` for the scripts it should execute, where ``n`` is the " +"runlevel that is being changed to, or ``S`` for the boot-up scripts." +msgstr "" + +#: ../../ch-opersys.rst:347 +msgid "" +"The names of the links all have the form ``Smmscript`` or ``Kmmscript`` " +"where mm is a two-digit number and script is the name of the script (this" +" should be the same as the name of the actual script in ``/etc/init.d``)." +msgstr "" + +#: ../../ch-opersys.rst:352 +msgid "" +"When ``init`` changes runlevel first the targets of the links whose names" +" start with a ``K`` are executed, each with the single argument ``stop``," +" followed by the scripts prefixed with an ``S``, each with the single " +"argument ``start``. (The links are those in the ``/etc/rcn.d`` directory " +"corresponding to the new runlevel.) The ``K`` links are responsible for " +"killing services and the ``S`` link for starting services upon entering " +"the runlevel." +msgstr "" + +#: ../../ch-opersys.rst:360 +msgid "" +"For example, if we are changing from runlevel 2 to runlevel 3, init will " +"first execute all of the ``K`` prefixed scripts it finds in " +"``/etc/rc3.d``, and then all of the ``S`` prefixed scripts in that " +"directory. The links starting with ``K`` will cause the referred-to file " +"to be executed with an argument of ``stop``, and the ``S`` links with an " +"argument of ``start``." +msgstr "" + +#: ../../ch-opersys.rst:367 +msgid "" +"The two-digit number mm is used to determine the order in which to run " +"the scripts: low-numbered links have their scripts run first. For " +"example, the ``K20`` scripts will be executed before the ``K30`` scripts." +" This is used when a certain service must be started before another. For " +"example, the name server ``bind`` might need to be started before the " +"news server ``inn`` so that ``inn`` can set up its access lists. In this " +"case, the script that starts ``bind`` would have a lower number than the " +"script that starts ``inn`` so that it runs first:" +msgstr "" + +#: ../../ch-opersys.rst:381 +msgid "" +"The two runlevels 0 (halt) and 6 (reboot) are slightly different. In " +"these runlevels, the links with an ``S`` prefix are still called after " +"those with a ``K`` prefix, but they too are called with the single " +"argument ``stop``." +msgstr "" + +#: ../../ch-opersys.rst:389 +msgid "Writing the scripts" +msgstr "" + +#: ../../ch-opersys.rst:391 +msgid "" +"Packages that include daemons for system services should place scripts in" +" ``/etc/init.d`` to start or stop services at boot time or during a " +"change of runlevel. These scripts should be named " +"``/etc/init.d/package``, and they should accept one argument, saying what" +" to do:" +msgstr "" + +#: ../../ch-opersys.rst:398 +msgid "``start``" +msgstr "" + +#: ../../ch-opersys.rst:398 +msgid "start the service," +msgstr "" + +#: ../../ch-opersys.rst:401 +msgid "``stop``" +msgstr "" + +#: ../../ch-opersys.rst:401 +msgid "stop the service," +msgstr "" + +#: ../../ch-opersys.rst:405 +msgid "``restart``" +msgstr "" + +#: ../../ch-opersys.rst:404 +msgid "" +"stop and restart the service if it's already running, otherwise start the" +" service" +msgstr "" + +#: ../../ch-opersys.rst:409 +msgid "``try-restart``" +msgstr "" + +#: ../../ch-opersys.rst:408 +msgid "" +"restart the service if it's already running, otherwise just report " +"success." +msgstr "" + +#: ../../ch-opersys.rst:413 +msgid "``reload``" +msgstr "" + +#: ../../ch-opersys.rst:412 +msgid "" +"cause the configuration of the service to be reloaded without actually " +"stopping and restarting the service," +msgstr "" + +#: ../../ch-opersys.rst:417 +msgid "``force-reload``" +msgstr "" + +#: ../../ch-opersys.rst:416 +msgid "" +"cause the configuration to be reloaded if the service supports this, " +"otherwise restart the service." +msgstr "" + +#: ../../ch-opersys.rst:420 +msgid "``status``" +msgstr "" + +#: ../../ch-opersys.rst:420 +msgid "report the current status of the service" +msgstr "" + +#: ../../ch-opersys.rst:422 +msgid "" +"The ``start``, ``stop``, ``restart``, and ``force-reload`` options should" +" be supported by all scripts in ``/etc/init.d``. Supporting ``status`` is" +" recommended but not required. The ``reload`` and ``try-restart`` options" +" are optional." +msgstr "" + +#: ../../ch-opersys.rst:427 +msgid "" +"The ``init.d`` scripts must ensure that they will behave sensibly (i.e., " +"returning success and not starting multiple copies of a service) if " +"invoked with ``start`` when the service is already running, or with " +"``stop`` when it isn't, and that they don't kill unfortunately-named user" +" processes. The best way to achieve this is usually to use ``start-stop-" +"daemon`` with the ``--oknodo`` option." +msgstr "" + +#: ../../ch-opersys.rst:434 +msgid "" +"Be careful of using ``set -e`` in ``init.d`` scripts. Writing correct " +"``init.d`` scripts requires accepting various error exit statuses when " +"daemons are already running or already stopped without aborting the " +"``init.d`` script, and common ``init.d`` function libraries are not safe " +"to call with ``set -e`` in effect. [#]_ For ``init.d`` scripts, it's " +"often easier to not use ``set -e`` and instead check the result of each " +"command separately." +msgstr "" + +#: ../../ch-opersys.rst:442 +msgid "" +"If a service reloads its configuration automatically (as in the case of " +"``cron``, for example), the ``reload`` option of the ``init.d`` script " +"should behave as if the configuration has been reloaded successfully." +msgstr "" + +#: ../../ch-opersys.rst:446 +msgid "" +"The ``/etc/init.d`` scripts must be treated as configuration files, " +"either (if they are present in the package, that is, in the .deb file) by" +" marking them as ``conffile``\\ s, or, (if they do not exist in the .deb)" +" by managing them correctly in the maintainer scripts (see :ref:`s" +"-config-files`). This is important since we want to give the local system" +" administrator the chance to adapt the scripts to the local system, e.g.," +" to disable a service without de-installing the package, or to specify " +"some special command line options when starting a service, while making " +"sure their changes aren't lost during the next package upgrade." +msgstr "" + +#: ../../ch-opersys.rst:457 +msgid "" +"These scripts should not fail obscurely when the configuration files " +"remain but the package has been removed, as configuration files remain on" +" the system after the package has been removed. Only when ``dpkg`` is " +"executed with the ``--purge`` option will configuration files be removed." +" In particular, as the ``/etc/init.d/package`` script itself is usually a" +" ``conffile``, it will remain on the system if the package is removed but" +" not purged. Therefore, you should include a ``test`` statement at the " +"top of the script, like this:" +msgstr "" + +#: ../../ch-opersys.rst:470 +msgid "" +"Often there are some variables in the ``init.d`` scripts whose values " +"control the behavior of the scripts, and which a system administrator is " +"likely to want to change. As the scripts themselves are frequently " +"``conffile``\\ s, modifying them requires that the administrator merge in" +" their changes each time the package is upgraded and the ``conffile`` " +"changes. To ease the burden on the system administrator, such " +"configurable values should not be placed directly in the script. Instead," +" they should be placed in a file in ``/etc/default``, which typically " +"will have the same base name as the ``init.d`` script. This extra file " +"should be sourced by the script when the script runs. It must contain " +"only variable settings and comments in POSIX.1-2017 ``sh`` format. It may" +" either be a ``conffile`` or a configuration file maintained by the " +"package maintainer scripts. See :ref:`s-config-files` for more details." +msgstr "" + +#: ../../ch-opersys.rst:485 +msgid "" +"To ensure that vital configurable values are always available, the " +"``init.d`` script should set default values for each of the shell " +"variables it uses, either before sourcing the ``/etc/default/`` file or " +"afterwards using something like the ``: ${VAR:=default}`` syntax. Also, " +"the ``init.d`` script must behave sensibly and not fail if the " +"``/etc/default`` file is deleted." +msgstr "" + +#: ../../ch-opersys.rst:492 +msgid "" +"Files and directories under ``/run``, including ones referred to via the " +"compatibility paths ``/var/run`` and ``/var/lock``, are normally stored " +"on a temporary filesystem and are normally not persistent across a " +"reboot. The ``init.d`` scripts must handle this correctly. This will " +"typically mean creating any required subdirectories dynamically when the " +"``init.d`` script is run. See :ref:`s-fhs-run` for more information." +msgstr "" + +#: ../../ch-opersys.rst:503 +msgid "Interfacing with init systems" +msgstr "" + +#: ../../ch-opersys.rst:505 +msgid "" +"Maintainers should use the abstraction layer provided by the ``update-" +"rc.d`` and ``invoke-rc.d`` programs to deal with initscripts in their " +"packages' scripts such as ``postinst``, ``prerm`` and ``postrm``." +msgstr "" + +#: ../../ch-opersys.rst:509 +msgid "" +"Directly managing the /etc/rc?.d links and directly invoking the " +"``/etc/init.d/`` initscripts should be done only by packages providing " +"the initscript subsystem (such as ``sysv-rc`` and ``file-rc``)." +msgstr "" + +#: ../../ch-opersys.rst:516 +msgid "Managing the links" +msgstr "" + +#: ../../ch-opersys.rst:518 +msgid "" +"The program ``update-rc.d`` is provided for package maintainers to " +"arrange for the proper creation and removal of ``/etc/rcn.d`` symbolic " +"links, or their functional equivalent if another method is being used. " +"This may be used by maintainers in their packages' ``postinst`` and " +"``postrm`` scripts." +msgstr "" + +#: ../../ch-opersys.rst:524 +msgid "" +"You must not include any ``/etc/rcn.d`` symbolic links in the actual " +"archive or manually create or remove the symbolic links in maintainer " +"scripts; you must use the ``update-rc.d`` program instead. (The former " +"will fail if an alternative method of maintaining runlevel information is" +" being used.) You must not include the ``/etc/rcn.d`` directories " +"themselves in the archive either. (Only the ``sysvinit`` package may do " +"so.)" +msgstr "" + +#: ../../ch-opersys.rst:532 +msgid "" +"To get the default behavior for your package, put in your ``postinst`` " +"script::" +msgstr "" + +#: ../../ch-opersys.rst:537 +msgid "and in your ``postrm``::" +msgstr "" + +#: ../../ch-opersys.rst:543 +msgid "" +"The default behaviour is to enable autostarting your package's daemon. " +"The local administrator can override this using the command ``update-rc.d" +" package disable``. If, however, the daemon should not be autostarted " +"unless the local administrator has explicitly requested this, instead add" +" to your ``postinst`` script::" +msgstr "" + +#: ../../ch-opersys.rst:551 +msgid "" +"and add a dependency on ``init-system-helpers (>= 1.50)``, which " +"introduced the ``defaults-disabled`` option. Then the local " +"administrator can enable autostarting the daemon using the command " +"``update-rc.d package enable``." +msgstr "" + +#: ../../ch-opersys.rst:556 +msgid "" +"An older practice, which should not be used, was to include a line like " +"``DISABLED=yes`` in the package's ``/etc/default`` file. The package's " +"init script would not start the service until the local system " +"administrator changed this to ``DISABLED=no``, or similar. The problem " +"with this approach was that it hides from the init system whether or not " +"the daemon should actually be started, which leads to inconsistent and " +"confusing behavior: ``service <package> start`` may return success but " +"not start the service; services with a dependency on this service will be" +" started even though the service isn't running; and init system status " +"commands may incorrectly claim that the service was started." +msgstr "" + +#: ../../ch-opersys.rst:568 +msgid "" +"Note that if your package changes runlevels or priority, you may have to " +"remove and recreate the links, since otherwise the old links may persist." +" Refer to the documentation of ``update-rc.d``." +msgstr "" + +#: ../../ch-opersys.rst:572 +msgid "" +"For more information about using ``update-rc.d``, please consult its man " +"page, update-rc.d(8)." +msgstr "" + +#: ../../ch-opersys.rst:575 +msgid "" +"It is easiest for packages not to call ``update-rc.d`` directly, but " +"instead use debhelper programs that add the required ``update-rc.d`` " +"calls automatically. See ``dh_installinit``, ``dh_installsystemd``, etc." +msgstr "" + +#: ../../ch-opersys.rst:582 +msgid "Running initscripts" +msgstr "" + +#: ../../ch-opersys.rst:584 +msgid "" +"The program ``invoke-rc.d`` is provided to make it easier for package " +"maintainers to properly invoke an initscript, obeying runlevel and other " +"locally-defined constraints that might limit a package's right to start, " +"stop and otherwise manage services. This program may be used by " +"maintainers in their packages' scripts." +msgstr "" + +#: ../../ch-opersys.rst:590 +msgid "" +"The package maintainer scripts must use ``invoke-rc.d`` to invoke the " +"``/etc/init.d/*`` initscripts or equivalent, instead of calling them " +"directly." +msgstr "" + +#: ../../ch-opersys.rst:594 +msgid "" +"By default, ``invoke-rc.d`` will pass any action requests (start, stop, " +"reload, restart...) to the ``/etc/init.d`` script, filtering out requests" +" to start or restart a service out of its intended runlevels." +msgstr "" + +#: ../../ch-opersys.rst:598 +msgid "Most packages will simply use:" +msgstr "" + +#: ../../ch-opersys.rst:604 +msgid "in their ``postinst`` and ``prerm`` scripts." +msgstr "" + +#: ../../ch-opersys.rst:606 +msgid "" +"A package should register its initscript services using ``update-rc.d`` " +"before it tries to invoke them using ``invoke-rc.d``. Invocation of " +"unregistered services may fail." +msgstr "" + +#: ../../ch-opersys.rst:610 +msgid "" +"For more information about using ``invoke-rc.d``, please consult its man " +"page, invoke-rc.d(8)." +msgstr "" + +#: ../../ch-opersys.rst:613 +msgid "" +"It is easiest for packages not to call ``invoke-rc.d`` directly, but " +"instead use debhelper programs that add the required ``invoke-rc.d`` " +"calls automatically. See ``dh_installinit``, ``dh_installsystemd``, etc." +msgstr "" + +#: ../../ch-opersys.rst:620 +msgid "Boot-time initialization" +msgstr "" + +#: ../../ch-opersys.rst:622 ../../ch-opersys.rst:638 +msgid "This section has been deleted." +msgstr "" + +#: ../../ch-opersys.rst:627 +msgid "Example" +msgstr "" + +#: ../../ch-opersys.rst:629 +msgid "" +"Examples on which you can base your systemd integration on is available " +"in the man page systemd.unit(8). An example on which you can base your " +"``/etc/init.d`` scripts is found in ``/etc/init.d/skeleton``." +msgstr "" + +#: ../../ch-opersys.rst:636 +msgid "Console messages from ``init.d`` scripts" +msgstr "" + +#: ../../ch-opersys.rst:643 +msgid "Cron jobs" +msgstr "" + +#: ../../ch-opersys.rst:645 +msgid "" +"Packages must not modify the configuration file ``/etc/crontab``, and " +"they must not modify the files in ``/var/spool/cron/crontabs``." +msgstr "" + +#: ../../ch-opersys.rst:648 +msgid "" +"If a package wants to install a job that has to be executed via cron, it " +"should place a file named as specified in :ref:`s-cron-files` into one or" +" more of the following directories:" +msgstr "" + +#: ../../ch-opersys.rst:653 +msgid "``/etc/cron.hourly``" +msgstr "" + +#: ../../ch-opersys.rst:655 +msgid "``/etc/cron.daily``" +msgstr "" + +#: ../../ch-opersys.rst:657 +msgid "``/etc/cron.weekly``" +msgstr "" + +#: ../../ch-opersys.rst:659 +msgid "``/etc/cron.monthly``" +msgstr "" + +#: ../../ch-opersys.rst:661 +msgid "" +"As these directory names imply, the files within them are executed on an " +"hourly, daily, weekly, or monthly basis, respectively. The exact times " +"are listed in ``/etc/crontab``." +msgstr "" + +#: ../../ch-opersys.rst:665 +msgid "" +"All files installed in any of these directories must be scripts (e.g., " +"shell scripts or Perl scripts) so that they can easily be modified by the" +" local system administrator. In addition, they must be treated as " +"configuration files." +msgstr "" + +#: ../../ch-opersys.rst:670 +msgid "" +"If a certain job has to be executed at some other frequency or at a " +"specific time, the package should install a file in ``/etc/cron.d`` with " +"a name as specified in :ref:`s-cron-files`. This file uses the same " +"syntax as ``/etc/crontab`` and is processed by ``cron`` automatically. " +"The file must also be treated as a configuration file. (Note that entries" +" in the ``/etc/cron.d`` directory are not handled by ``anacron``. Thus, " +"you should only use this directory for jobs which may be skipped if the " +"system is not running.)" +msgstr "" + +#: ../../ch-opersys.rst:679 +msgid "" +"Unlike ``crontab`` files described in the IEEE Std 1003.1-2008 (POSIX.1) " +"available from `The Open Group " +"<https://www.opengroup.org/onlinepubs/9699919799/>`_, the files in " +"``/etc/cron.d`` and the file ``/etc/crontab`` have seven fields; namely:" +msgstr "" + +#: ../../ch-opersys.rst:685 +msgid "Minute [0,59]" +msgstr "" + +#: ../../ch-opersys.rst:687 +msgid "Hour [0,23]" +msgstr "" + +#: ../../ch-opersys.rst:689 +msgid "Day of the month [1,31]" +msgstr "" + +#: ../../ch-opersys.rst:691 +msgid "Month of the year [1,12]" +msgstr "" + +#: ../../ch-opersys.rst:693 +msgid "Day of the week ([0,6] with 0=Sunday)" +msgstr "" + +#: ../../ch-opersys.rst:695 +msgid "Username" +msgstr "" + +#: ../../ch-opersys.rst:697 +msgid "Command to be run" +msgstr "" + +#: ../../ch-opersys.rst:699 +msgid "" +"Ranges of numbers are allowed. Ranges are two numbers separated with a " +"hyphen. The specified range is inclusive. Lists are allowed. A list is a " +"set of numbers (or ranges) separated by commas. Step values can be used " +"in conjunction with ranges." +msgstr "" + +#: ../../ch-opersys.rst:704 +msgid "" +"The scripts or ``crontab`` entries in these directories should check if " +"all necessary programs are installed before they try to execute them. " +"Otherwise, problems will arise when a package was removed but not purged " +"since configuration files are kept on the system in this situation." +msgstr "" + +#: ../../ch-opersys.rst:709 +msgid "" +"Any ``cron`` daemon must provide ``/usr/bin/crontab`` and support normal " +"``crontab`` entries as specified in POSIX. The daemon must also support " +"names for days and months, ranges, and step values. It has to support " +"``/etc/crontab``, and correctly execute the scripts in ``/etc/cron.d``. " +"The daemon must also correctly execute scripts in " +"``/etc/cron.{hourly,daily,weekly,monthly}``." +msgstr "" + +#: ../../ch-opersys.rst:719 +msgid "Cron job file names" +msgstr "" + +#: ../../ch-opersys.rst:721 +msgid "" +"The file name of a cron job file should normally match the name of the " +"package from which it comes." +msgstr "" + +#: ../../ch-opersys.rst:724 +msgid "" +"If a package supplies multiple cron job files files in the same " +"directory, the file names should all start with the name of the package " +"(possibly modified as described below) followed by a hyphen (``-``) and a" +" suitable suffix." +msgstr "" + +#: ../../ch-opersys.rst:729 +msgid "" +"A cron job file name must not include any period or plus characters " +"(``.`` or ``+``) characters as this will cause cron to ignore the file. " +"Underscores (``_``) should be used instead of ``.`` and ``+`` characters." +msgstr "" + +#: ../../ch-opersys.rst:737 +msgid "Menus" +msgstr "" + +#: ../../ch-opersys.rst:739 +msgid "" +"Packages shipping applications that comply with minimal requirements " +"described below for integration with desktop environments should register" +" these applications in the desktop menu, following the *FreeDesktop* " +"standard, using text files called *desktop entries*. Their format is " +"described in the *Desktop Entry Specification* at " +"https://standards.freedesktop.org/desktop-entry-spec/latest/ and " +"complementary information can be found in the *Desktop Menu " +"Specification* at https://standards.freedesktop.org/menu-spec/latest/." +msgstr "" + +#: ../../ch-opersys.rst:748 +msgid "" +"The desktop entry files are installed by the packages in the directory " +"``/usr/share/applications`` and the FreeDesktop menus are refreshed using" +" *dpkg triggers*. It is therefore not necessary to depend on packages " +"providing FreeDesktop menu systems." +msgstr "" + +#: ../../ch-opersys.rst:753 +msgid "" +"Entries displayed in the FreeDesktop menu should conform to the following" +" minima for relevance and visual integration." +msgstr "" + +#: ../../ch-opersys.rst:756 +msgid "" +"Unless hidden by default, the desktop entry must point to a PNG or SVG " +"icon with a transparent background, providing at least the 22×22 size, " +"and preferably up to 64×64. The icon should be neutral enough to " +"integrate well with the default icon themes. It is encouraged to ship the" +" icon in the default *hicolor* icon theme directories, or to use an " +"existing icon from the *hicolor* theme." +msgstr "" + +#: ../../ch-opersys.rst:763 +msgid "" +"If the menu entry is not useful in the general case as a standalone " +"application, the desktop entry should set the ``NoDisplay`` key to true, " +"so that it can be configured to be displayed only by those who need it." +msgstr "" + +#: ../../ch-opersys.rst:768 +msgid "" +"In doubt, the package maintainer should coordinate with the maintainers " +"of menu implementations through the *debian-desktop* mailing list in " +"order to avoid problems with categories or bad interactions with other " +"icons. Especially for packages which are part of installation tasks, the " +"contents of the ``NotShowIn``/``OnlyShowIn`` keys should be validated by " +"the maintainers of the relevant environments." +msgstr "" + +#: ../../ch-opersys.rst:776 +msgid "" +"Since the FreeDesktop menu is a cross-distribution standard, the desktop " +"entries written for Debian should be forwarded upstream, where they will " +"benefit to other users and are more likely to receive extra contributions" +" such as translations." +msgstr "" + +#: ../../ch-opersys.rst:781 +msgid "" +"If a package installs a FreeDesktop desktop entry, it must not also " +"install a Debian menu entry." +msgstr "" + +#: ../../ch-opersys.rst:787 +msgid "Multimedia handlers" +msgstr "" + +#: ../../ch-opersys.rst:789 +msgid "" +"Media types (formerly known as MIME types, Multipurpose Internet Mail " +"Extensions, RFCs 2045-2049) is a mechanism for encoding files and data " +"streams and providing meta-information about them, in particular their " +"type and format (e.g. ``image/png``, ``text/html``, ``audio/ogg``)." +msgstr "" + +#: ../../ch-opersys.rst:794 +msgid "" +"Registration of media type handlers allows programs like mail user agents" +" and web browsers to invoke these handlers to view, edit or display media" +" types they don't support directly." +msgstr "" + +#: ../../ch-opersys.rst:798 +msgid "" +"There are two overlapping systems to associate media types to programs " +"which can handle them. The *mailcap* system is found on a large number of" +" Unix systems. The *FreeDesktop* system is aimed at Desktop environments." +" In Debian, FreeDesktop entries are automatically translated in mailcap " +"entries, therefore packages already using desktop entries should not use " +"the mailcap system directly." +msgstr "" + +#: ../../ch-opersys.rst:808 +msgid "Registration of media type handlers with desktop entries" +msgstr "" + +#: ../../ch-opersys.rst:810 +msgid "" +"Packages shipping an application able to view, edit or point to files of " +"a given media type, or open links with a given URI scheme, should list it" +" in the ``MimeType`` key of the application's `desktop entry " +"<#s-menus>`_. For URI schemes, the relevant MIME types are ``x-scheme-" +"handler/*`` (e.g. ``x-scheme-handler/https``)." +msgstr "" + +#: ../../ch-opersys.rst:819 +msgid "Registration of media type handlers with mailcap entries" +msgstr "" + +#: ../../ch-opersys.rst:821 +msgid "" +"Packages that are not using desktop entries for registration should " +"install a file in mailcap(5) format (RFC 1524) in the directory " +"``/usr/lib/mime/packages/``. The file name should be the binary package's" +" name." +msgstr "" + +#: ../../ch-opersys.rst:826 +msgid "" +"The mime-support package provides the ``update-mime`` program, which " +"integrates these registrations in the ``/etc/mailcap`` file, using dpkg " +"triggers. [#]_" +msgstr "" + +#: ../../ch-opersys.rst:830 +msgid "" +"Packages installing desktop entries should not install mailcap entries " +"for the same program, because the mime-support package already reads " +"desktop entries." +msgstr "" + +#: ../../ch-opersys.rst:834 +msgid "" +"Packages using these facilities *should not* depend on, recommend, or " +"suggest ``mime-support``." +msgstr "" + +#: ../../ch-opersys.rst:840 +msgid "Providing media types to files" +msgstr "" + +#: ../../ch-opersys.rst:842 +msgid "" +"The media type of a file is discovered by inspecting the file's extension" +" or its magic(5) pattern, and interrogating a database associating them " +"with media types." +msgstr "" + +#: ../../ch-opersys.rst:846 +msgid "" +"To support new associations between media types and files, their " +"characteristic file extensions and magic patterns should be registered to" +" the IANA (Internet Assigned Numbers Authority). See " +"https://www.iana.org/assignments/media-types and RFC 6838 for details. " +"This information will then propagate to the systems discovering file " +"media types in Debian, provided by the shared-mime-info, mime-support and" +" file packages. If registration and propagation can not be waited for, " +"support can be asked to the maintainers of the packages mentioned above." +msgstr "" + +#: ../../ch-opersys.rst:856 +msgid "" +"For files that are produced and read by a single application, it is also " +"possible to declare this association to the *Shared MIME Info* system by " +"installing in the directory ``/usr/share/mime/packages`` a file in the " +"XML format specified at https://standards.freedesktop.org/shared-mime-" +"info-spec/latest/." +msgstr "" + +#: ../../ch-opersys.rst:865 +msgid "Keyboard configuration" +msgstr "" + +#: ../../ch-opersys.rst:867 +msgid "" +"To achieve a consistent keyboard configuration so that all applications " +"interpret a keyboard event the same way, all programs in the Debian " +"distribution must be configured to comply with the following guidelines." +msgstr "" + +#: ../../ch-opersys.rst:871 +msgid "The following keys must have the specified interpretations:" +msgstr "" + +#: ../../ch-opersys.rst:874 +msgid "``<--``" +msgstr "" + +#: ../../ch-opersys.rst:874 +msgid "delete the character to the left of the cursor" +msgstr "" + +#: ../../ch-opersys.rst:877 +msgid "``Delete``" +msgstr "" + +#: ../../ch-opersys.rst:877 +msgid "delete the character to the right of the cursor" +msgstr "" + +#: ../../ch-opersys.rst:880 +msgid "``Control+H``" +msgstr "" + +#: ../../ch-opersys.rst:880 +msgid "emacs: the help prefix" +msgstr "" + +#: ../../ch-opersys.rst:882 +msgid "" +"The interpretation of any keyboard events should be independent of the " +"terminal that is used, be it a virtual console, an X terminal emulator, " +"an rlogin/telnet session, etc." +msgstr "" + +#: ../../ch-opersys.rst:886 +msgid "" +"The following list explains how the different programs should be set up " +"to achieve this:" +msgstr "" + +#: ../../ch-opersys.rst:889 +msgid "``<--`` generates ``KB_BackSpace`` in X." +msgstr "" + +#: ../../ch-opersys.rst:891 +msgid "``Delete`` generates ``KB_Delete`` in X." +msgstr "" + +#: ../../ch-opersys.rst:893 +msgid "" +"X translations are set up to make ``KB_Backspace`` generate ASCII DEL, " +"and to make ``KB_Delete`` generate ``ESC [ 3 ~`` (this is the vt220 " +"escape code for the \"delete character\" key). This must be done by " +"loading the X resources using ``xrdb`` on all local X displays, not using" +" the application defaults, so that the translation resources used " +"correspond to the ``xmodmap`` settings." +msgstr "" + +#: ../../ch-opersys.rst:900 +msgid "" +"The Linux console is configured to make ``<--`` generate DEL, and " +"``Delete`` generate ``ESC [ 3 ~``." +msgstr "" + +#: ../../ch-opersys.rst:903 +msgid "" +"X applications are configured so that ``<`` deletes left, and ``Delete`` " +"deletes right. Motif applications already work like this." +msgstr "" + +#: ../../ch-opersys.rst:906 +msgid "Terminals should have ``stty erase ^?`` ." +msgstr "" + +#: ../../ch-opersys.rst:908 +msgid "" +"The ``xterm`` terminfo entry should have ``ESC [ 3 ~`` for ``kdch1``, " +"just as for ``TERM=linux`` and ``TERM=vt220``." +msgstr "" + +#: ../../ch-opersys.rst:911 +msgid "" +"Emacs is programmed to map ``KB_Backspace`` or the ``stty erase`` " +"character to ``delete-backward-char``, and ``KB_Delete`` or ``kdch1`` to " +"``delete-forward-char``, and ``^H`` to ``help`` as always." +msgstr "" + +#: ../../ch-opersys.rst:915 +msgid "" +"Other applications use the ``stty erase`` character and ``kdch1`` for the" +" two delete keys, with ASCII DEL being \"delete previous character\" and " +"``kdch1`` being \"delete character under cursor\"." +msgstr "" + +#: ../../ch-opersys.rst:919 +msgid "This will solve the problem except for the following cases:" +msgstr "" + +#: ../../ch-opersys.rst:921 +msgid "" +"Some terminals have a ``<--`` key that cannot be made to produce anything" +" except ``^H``. On these terminals Emacs help will be unavailable on " +"``^H`` (assuming that the ``stty erase`` character takes precedence in " +"Emacs, and has been set correctly). ``M-x help`` or ``F1`` (if available)" +" can be used instead." +msgstr "" + +#: ../../ch-opersys.rst:926 +msgid "" +"Some operating systems use ``^H`` for ``stty erase``. However, modern " +"telnet versions and all rlogin versions propagate ``stty`` settings, and " +"almost all UNIX versions honour ``stty erase``. Where the ``stty`` " +"settings are not propagated correctly, things can be made to work by " +"using ``stty`` manually." +msgstr "" + +#: ../../ch-opersys.rst:932 +msgid "" +"Some systems (including previous Debian versions) use ``xmodmap`` to " +"arrange for both ``<--`` and ``Delete`` to generate ``KB_Delete``. We can" +" change the behavior of their X clients using the same X resources that " +"we use to do it for our own clients, or configure our clients using their" +" resources when things are the other way around. On displays configured " +"like this ``Delete`` will not work, but ``<--`` will." +msgstr "" + +#: ../../ch-opersys.rst:940 +msgid "" +"Some operating systems have different ``kdch1`` settings in their " +"``terminfo`` database for ``xterm`` and others. On these systems the " +"``Delete`` key will not work correctly when you log in from a system " +"conforming to our policy, but ``<--`` will." +msgstr "" + +#: ../../ch-opersys.rst:948 +msgid "Environment variables" +msgstr "" + +#: ../../ch-opersys.rst:950 +msgid "" +"Programs installed on the system PATH (``/bin``, ``/usr/bin``, ``/sbin``," +" ``/usr/sbin``, or similar directories) must not depend on custom " +"environment variable settings to get reasonable defaults. This is because" +" such environment variables would have to be set in a system-wide " +"configuration file such as a file in ``/etc/profile.d``, which is not " +"supported by all shells." +msgstr "" + +#: ../../ch-opersys.rst:957 +msgid "" +"If a program usually depends on environment variables for its " +"configuration, the program should be changed to fall back to a reasonable" +" default configuration if these environment variables are not present. If" +" this cannot be done easily (e.g., if the source code of a non-free " +"program is not available), the program must be replaced by a small " +"\"wrapper\" shell script that sets the environment variables if they are " +"not already defined, and calls the original program." +msgstr "" + +#: ../../ch-opersys.rst:965 +msgid "Here is an example of a wrapper script for this purpose:" +msgstr "" + +#: ../../ch-opersys.rst:977 +msgid "Registering Documents using doc-base" +msgstr "" + +#: ../../ch-opersys.rst:979 +msgid "" +"The doc-base package implements a flexible mechanism for handling and " +"presenting documentation. The recommended practice is for every Debian " +"package that provides online documentation (other than just manual pages)" +" to register these documents with doc-base by installing a doc-base " +"control file in ``/usr/share/doc-base/``." +msgstr "" + +#: ../../ch-opersys.rst:985 +msgid "" +"Please refer to the documentation that comes with the doc-base package " +"for information and details." +msgstr "" + +#: ../../ch-opersys.rst:991 +msgid "Alternate init systems" +msgstr "" + +#: ../../ch-opersys.rst:993 +msgid "" +"A number of other init systems are available now in Debian that can be " +"used in place of sysvinit. Alternative init implementations must support " +"running SysV init scripts as described at :ref:`s-sysvinit` for " +"compatibility." +msgstr "" + +#: ../../ch-opersys.rst:998 +msgid "" +"Packages may integrate with these replacement init systems by providing " +"implementation-specific configuration information about how and when to " +"start a service or in what order to run certain tasks at boot time. " +"However, any package integrating with other init systems must also be " +"backwards-compatible with sysvinit by providing a SysV-style init script " +"with the same name as and equivalent functionality to any init-specific " +"job, as this is the only start-up configuration method guaranteed to be " +"supported by all init implementations. An exception to this rule is " +"scripts or jobs provided by the init implementation itself; such jobs may" +" be required for an implementation-specific equivalent of the " +"``/etc/rcS.d/`` scripts and may not have a one-to-one correspondence with" +" the init scripts." +msgstr "" + +#: ../../ch-opersys.rst:1014 +msgid "Event-based boot with upstart" +msgstr "" + +#: ../../ch-opersys.rst:1016 +msgid "" +"The ``upstart`` event-based boot system is no longer maintained in " +"Debian, so this section has been removed." +msgstr "" + +#: ../../ch-opersys.rst:1020 +msgid "" +"This is necessary in order to reserve the directories for use in cross-" +"installation of library packages from other architectures, as part of " +"``multiarch``." +msgstr "" + +#: ../../ch-opersys.rst:1025 +msgid "" +"This is necessary for architecture-dependent headers file to coexist in a" +" ``multiarch`` setup." +msgstr "" + +#: ../../ch-opersys.rst:1029 +msgid "" +"These directories are used to store translators and as a set of standard " +"names for mount points, respectively." +msgstr "" + +#: ../../ch-opersys.rst:1033 +msgid "" +"``/lib/lsb/init-functions``, which assists in writing LSB-compliant init " +"scripts, may fail if ``set -e`` is in effect and echoing status " +"messages to the console fails, for example." +msgstr "" + +#: ../../ch-opersys.rst:1038 +msgid "" +"Creating, modifying or removing a file in ``/usr/lib/mime/packages/`` " +"using maintainer scripts will not activate the trigger. In that case, it " +"can be done by calling ``dpkg-trigger --no-await /usr/lib/mime/packages``" +" from the maintainer script after creating, modifying, or removing the " +"file." +msgstr "" + diff --git a/locales/ja/LC_MESSAGES/ch-relationships.po b/locales/ja/LC_MESSAGES/ch-relationships.po new file mode 100644 index 0000000..fcd015a --- /dev/null +++ b/locales/ja/LC_MESSAGES/ch-relationships.po @@ -0,0 +1,944 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1996, 1997, 1998 Ian Jackson, Christian Schwarz, 1998-2017, +# The Debian Policy Mailing List +# This file is distributed under the same license as the Debian Policy +# Manual package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2018. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Debian Policy Manual 4.1.6.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-08-02 11:56+0800\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language-Team: LANGUAGE <LL@li.org>\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.4.0\n" + +#: ../../ch-relationships.rst:2 +msgid "Declaring relationships between packages" +msgstr "" + +#: ../../ch-relationships.rst:7 +msgid "Syntax of relationship fields" +msgstr "" + +#: ../../ch-relationships.rst:9 +msgid "" +"These fields all have a uniform syntax. They are a list of package names " +"separated by commas." +msgstr "" + +#: ../../ch-relationships.rst:12 +msgid "" +"In the ``Depends``, ``Recommends``, ``Suggests``, ``Pre-Depends``, " +"``Build-Depends``, ``Build-Depends-Indep`` and ``Build-Depends-Arch`` " +"control fields of the package, which declare dependencies on other " +"packages, the package names listed may also include lists of alternative " +"package names, separated by vertical bar (pipe) symbols ``|``. In such a " +"case, that part of the dependency can be satisfied by any one of the " +"alternative packages. [#]_" +msgstr "" + +#: ../../ch-relationships.rst:20 +msgid "" +"All of the fields except for ``Provides`` may restrict their " +"applicability to particular versions of each named package. This is done " +"in parentheses after each individual package name; the parentheses should" +" contain a relation from the list below followed by a version number, in " +"the format described in :ref:`s-f-Version`." +msgstr "" + +#: ../../ch-relationships.rst:26 +msgid "" +"The relations allowed are ``<<``, ``<=``, ``=``, ``>=`` and ``>>`` for " +"strictly earlier, earlier or equal, exactly equal, later or equal and " +"strictly later, respectively. [#]_" +msgstr "" + +#: ../../ch-relationships.rst:30 +msgid "" +"Whitespace may appear at any point in the version specification subject " +"to the rules in :ref:`s-controlsyntax`, and must appear where it's " +"necessary to disambiguate; it is not otherwise significant. All of the " +"relationship fields can only be folded in source package control files. " +"For consistency and in case of future changes to ``dpkg`` it is " +"recommended that a single space be used after a version relationship and " +"before a version number; it is also conventional to put a single space " +"after each comma, on either side of each vertical bar, and before each " +"open parenthesis. When opening a continuation line in a relationship " +"field, it is conventional to do so after a comma and before the space " +"following that comma." +msgstr "" + +#: ../../ch-relationships.rst:42 +msgid "For example, a list of dependencies might appear as:" +msgstr "" + +#: ../../ch-relationships.rst:50 +msgid "" +"Relationships may be restricted to a certain set of architectures. This " +"is indicated in brackets after each individual package name and the " +"optional version specification. The brackets enclose a non-empty list of " +"Debian architecture names in the format described in :ref:`s-arch-spec`, " +"separated by whitespace. Exclamation marks may be prepended to each of " +"the names. (It is not permitted for some names to be prepended with " +"exclamation marks while others aren't.)" +msgstr "" + +#: ../../ch-relationships.rst:58 +msgid "" +"For build relationship fields (``Build-Depends``, ``Build-Depends-" +"Indep``, ``Build-Depends-Arch``, ``Build-Conflicts``, ``Build-Conflicts-" +"Indep`` and ``Build-Conflicts-Arch``), if the current Debian host " +"architecture is not in this list and there are no exclamation marks in " +"the list, or it is in the list with a prepended exclamation mark, the " +"package name and the associated version specification are ignored " +"completely for the purposes of defining the relationships." +msgstr "" + +#: ../../ch-relationships.rst:67 ../../ch-relationships.rst:96 +msgid "For example:" +msgstr "" + +#: ../../ch-relationships.rst:76 +msgid "" +"requires ``kernel-headers-2.2.10`` on all architectures other than " +"hurd-i386 and requires ``hurd-dev`` and ``gnumach-dev`` only on " +"hurd-i386. Here is another example showing multiple architectures " +"separated by spaces:" +msgstr "" + +#: ../../ch-relationships.rst:87 +msgid "" +"For binary relationship fields and the ``Built-Using`` field, the " +"architecture restriction syntax is only supported in the source package " +"control file ``debian/control``. When the corresponding binary package " +"control file is generated, the relationship will either be omitted or " +"included without the architecture restriction based on the architecture " +"of the binary package. This means that architecture restrictions must not" +" be used in binary relationship fields for architecture-independent " +"packages (``Architecture: all``)." +msgstr "" + +#: ../../ch-relationships.rst:102 +msgid "" +"becomes ``Depends: foo`` when the package is built on the ``i386`` " +"architecture, ``Depends: bar`` when the package is built on the ``amd64``" +" architecture, and omitted entirely in binary packages built on all other" +" architectures." +msgstr "" + +#: ../../ch-relationships.rst:107 +msgid "" +"If the architecture-restricted dependency is part of a set of " +"alternatives using ``|``, that alternative is ignored completely on " +"architectures that do not match the restriction. For example:" +msgstr "" + +#: ../../ch-relationships.rst:115 +msgid "" +"is equivalent to ``bar`` on the ``i386`` architecture, to ``foo`` on the " +"``amd64`` architecture, and to ``foo | bar`` on all other architectures." +msgstr "" + +#: ../../ch-relationships.rst:119 +msgid "" +"Relationships may also be restricted to a certain set of architectures " +"using architecture wildcards in the format described in :ref:`s-arch-" +"wildcard-spec`. The syntax for declaring such restrictions is the same as" +" declaring restrictions using a certain set of architectures without " +"architecture wildcards. For example:" +msgstr "" + +#: ../../ch-relationships.rst:129 +msgid "" +"is equivalent to ``foo`` on architectures using the Linux kernel and any " +"cpu, ``bar`` on architectures using any kernel and an i386 cpu, and " +"``baz`` on any architecture using a kernel other than Linux." +msgstr "" + +#: ../../ch-relationships.rst:133 +msgid "" +"Note that the binary package relationship fields such as ``Depends`` " +"appear in one of the binary package sections of the control file, whereas" +" the build-time relationships such as ``Build-Depends`` appear in the " +"source package section of the control file (which is the first section)." +msgstr "" + +#: ../../ch-relationships.rst:142 +msgid "" +"Binary Dependencies - ``Depends``, ``Recommends``, ``Suggests``, " +"``Enhances``, ``Pre-Depends``" +msgstr "" + +#: ../../ch-relationships.rst:144 +msgid "" +"Packages can declare in their control file that they have certain " +"relationships to other packages - for example, that they may not be " +"installed at the same time as certain other packages, and/or that they " +"depend on the presence of others." +msgstr "" + +#: ../../ch-relationships.rst:149 +msgid "" +"This is done using the ``Depends``, ``Pre-Depends``, ``Recommends``, " +"``Suggests``, ``Enhances``, ``Breaks`` and ``Conflicts`` control fields. " +"``Breaks`` is described in :ref:`s-breaks`, and ``Conflicts`` is " +"described in :ref:`s-conflicts`. The rest are described below." +msgstr "" + +#: ../../ch-relationships.rst:155 +msgid "" +"These seven fields are used to declare a dependency relationship by one " +"package on another. Except for ``Enhances`` and ``Breaks``, they appear " +"in the depending (binary) package's control file. (``Enhances`` appears " +"in the recommending package's control file, and ``Breaks`` appears in the" +" version of depended-on package which causes the named package to break)." +msgstr "" + +#: ../../ch-relationships.rst:162 +msgid "" +"A ``Depends`` field takes effect *only* when a package is to be " +"configured. It does not prevent a package being on the system in an " +"unconfigured state while its dependencies are unsatisfied, and it is " +"possible to replace a package whose dependencies are satisfied and which " +"is properly installed with a different version whose dependencies are not" +" and cannot be satisfied; when this is done the depending package will be" +" left unconfigured (since attempts to configure it will give errors) and " +"will not function properly. If it is necessary, a ``Pre-Depends`` field " +"can be used, which has a partial effect even when a package is being " +"unpacked, as explained in detail below. (The other three dependency " +"fields, ``Recommends``, ``Suggests`` and ``Enhances``, are only used by " +"the various front-ends to ``dpkg`` such as ``apt-get``, ``aptitude``, and" +" ``dselect``.)" +msgstr "" + +#: ../../ch-relationships.rst:176 +msgid "" +"Since ``Depends`` only places requirements on the order in which packages" +" are configured, packages in an installation run are usually all unpacked" +" first and all configured later. [#]_" +msgstr "" + +#: ../../ch-relationships.rst:180 +msgid "" +"If there is a circular dependency among packages being installed or " +"removed, installation or removal order honoring the dependency order is " +"impossible, requiring the dependency loop be broken at some point and the" +" dependency requirements violated for at least one package. Packages " +"involved in circular dependencies may not be able to rely on their " +"dependencies being configured before they themselves are configured, " +"depending on which side of the break of the circular dependency loop they" +" happen to be on. If one of the packages in the loop has no ``postinst`` " +"script, then the cycle will be broken at that package; this ensures that " +"all ``postinst`` scripts are run with their dependencies properly " +"configured if this is possible. Otherwise the breaking point is " +"arbitrary. Packages should therefore avoid circular dependencies where " +"possible, particularly if they have ``postinst`` scripts." +msgstr "" + +#: ../../ch-relationships.rst:194 +msgid "The meaning of the five dependency fields is as follows:" +msgstr "" + +#: ../../ch-relationships.rst:223 +msgid "``Depends``" +msgstr "" + +#: ../../ch-relationships.rst:197 +msgid "" +"This declares an absolute dependency. A package will not be configured " +"unless all of the packages listed in its ``Depends`` field have been " +"correctly configured (unless there is a circular dependency as described " +"above)." +msgstr "" + +#: ../../ch-relationships.rst:202 +msgid "" +"The ``Depends`` field should be used if the depended-on package is " +"required for the depending package to provide a significant amount of " +"functionality." +msgstr "" + +#: ../../ch-relationships.rst:206 +msgid "" +"The ``Depends`` field should also be used if the ``postinst`` or " +"``prerm`` scripts require the depended-on package to be unpacked or " +"configured in order to run. In the case of ``postinst configure``, the " +"depended-on packages will be unpacked and configured first. (If both " +"packages are involved in a dependency loop, this might not work as " +"expected; see the explanation a few paragraphs back.) In the case of " +"``prerm`` or other ``postinst`` actions, the package dependencies will " +"normally be at least unpacked, but they may be only \"Half-Installed\" if" +" a previous upgrade of the dependency failed." +msgstr "" + +#: ../../ch-relationships.rst:216 +msgid "" +"Finally, the ``Depends`` field should be used if the depended-on package " +"is needed by the ``postrm`` script to fully clean up after the package " +"removal. There is no guarantee that package dependencies will be " +"available when ``postrm`` is run, but the depended-on package is more " +"likely to be available if the package declares a dependency (particularly" +" in the case of ``postrm remove``). The ``postrm`` script must gracefully" +" skip actions that require a dependency if that dependency isn't " +"available." +msgstr "" + +#: ../../ch-relationships.rst:229 +msgid "``Recommends``" +msgstr "" + +#: ../../ch-relationships.rst:226 +msgid "This declares a strong, but not absolute, dependency." +msgstr "" + +#: ../../ch-relationships.rst:228 +msgid "" +"The ``Recommends`` field should list packages that would be found " +"together with this one in all but unusual installations." +msgstr "" + +#: ../../ch-relationships.rst:236 +msgid "``Suggests``" +msgstr "" + +#: ../../ch-relationships.rst:232 +msgid "" +"This is used to declare that one package may be more useful with one or " +"more others. Using this field tells the packaging system and the user " +"that the listed packages are related to this one and can perhaps enhance " +"its usefulness, but that installing this one without them is perfectly " +"reasonable." +msgstr "" + +#: ../../ch-relationships.rst:241 +msgid "``Enhances``" +msgstr "" + +#: ../../ch-relationships.rst:239 +msgid "" +"This field is similar to Suggests but works in the opposite direction. It" +" is used to declare that a package can enhance the functionality of " +"another package." +msgstr "" + +#: ../../ch-relationships.rst:280 +msgid "``Pre-Depends``" +msgstr "" + +#: ../../ch-relationships.rst:244 +msgid "" +"This field is like ``Depends``, except that it also forces ``dpkg`` to " +"complete installation of the packages named before even starting the " +"installation of the package which declares the pre-dependency, as " +"follows:" +msgstr "" + +#: ../../ch-relationships.rst:249 +msgid "" +"When a package declaring a pre-dependency is about to be *unpacked* the " +"pre-dependency can be satisfied if the depended-on package is either " +"fully configured, *or even if* the depended-on package(s) are only in the" +" \"Unpacked\" or the \"Half-Configured\" state, provided that they have " +"been configured correctly at some point in the past (and not removed or " +"partially removed since). In this case, both the previously-configured " +"and currently \"Unpacked\" or \"Half-Configured\" versions must satisfy " +"any version clause in the ``Pre-Depends`` field." +msgstr "" + +#: ../../ch-relationships.rst:259 +msgid "" +"When the package declaring a pre-dependency is about to be *configured*, " +"the pre-dependency will be treated as a normal ``Depends``. It will be " +"considered satisfied only if the depended-on package has been correctly " +"configured. However, unlike with ``Depends``, ``Pre-Depends`` does not " +"permit circular dependencies to be broken. If a circular dependency is " +"encountered while attempting to honor ``Pre-Depends``, the installation " +"will be aborted." +msgstr "" + +#: ../../ch-relationships.rst:268 +msgid "" +"``Pre-Depends`` are also required if the ``preinst`` script depends on " +"the named package. It is best to avoid this situation if possible." +msgstr "" + +#: ../../ch-relationships.rst:272 +msgid "" +"``Pre-Depends`` should be used sparingly, preferably only by packages " +"whose premature upgrade or installation would hamper the ability of the " +"system to continue with any upgrade that might be in progress." +msgstr "" + +#: ../../ch-relationships.rst:277 +msgid "" +"You should not specify a ``Pre-Depends`` entry for a package before this " +"has been discussed on the ``debian-devel`` mailing list and a consensus " +"about doing that has been reached. See :ref:`s-dependencies`." +msgstr "" + +#: ../../ch-relationships.rst:282 +msgid "" +"When selecting which level of dependency to use you should consider how " +"important the depended-on package is to the functionality of the one " +"declaring the dependency. Some packages are composed of components of " +"varying degrees of importance. Such a package should list using " +"``Depends`` the package(s) which are required by the more important " +"components. The other components' requirements may be mentioned as " +"Suggestions or Recommendations, as appropriate to the components' " +"relative importance." +msgstr "" + +#: ../../ch-relationships.rst:294 +msgid "Packages which break other packages - ``Breaks``" +msgstr "" + +#: ../../ch-relationships.rst:296 +msgid "" +"When one binary package declares that it breaks another, ``dpkg`` will " +"refuse to allow the package which declares ``Breaks`` to be unpacked " +"unless the broken package is deconfigured first, and it will refuse to " +"allow the broken package to be reconfigured." +msgstr "" + +#: ../../ch-relationships.rst:301 +msgid "" +"A package will not be regarded as causing breakage merely because its " +"configuration files are still installed; it must be at least \"Half-" +"Installed\"." +msgstr "" + +#: ../../ch-relationships.rst:305 +msgid "" +"A special exception is made for packages which declare that they break " +"their own package name or a virtual package which they provide (see " +"below): this does not count as a real breakage." +msgstr "" + +#: ../../ch-relationships.rst:309 +msgid "" +"Normally a ``Breaks`` entry will have an \"earlier than\" version clause;" +" such a ``Breaks`` is introduced in the version of an (implicit or " +"explicit) dependency which violates an assumption or reveals a bug in " +"earlier versions of the broken package, or which takes over a file from " +"earlier versions of the package named in ``Breaks``. This use of " +"``Breaks`` will inform higher-level package management tools that the " +"broken package must be upgraded before the new one." +msgstr "" + +#: ../../ch-relationships.rst:317 +msgid "" +"If the breaking package also overwrites some files from the older " +"package, it should use ``Replaces`` to ensure this goes smoothly. See " +":ref:`s-replaces` for a full discussion of taking over files from other " +"packages, including how to use ``Breaks`` in those cases." +msgstr "" + +#: ../../ch-relationships.rst:323 +msgid "" +"Many of the cases where ``Breaks`` should be used were previously handled" +" with ``Conflicts`` because ``Breaks`` did not yet exist. Many " +"``Conflicts`` fields should now be ``Breaks``. See :ref:`s-conflicts` for" +" more information about the differences." +msgstr "" + +#: ../../ch-relationships.rst:332 +msgid "Conflicting binary packages - ``Conflicts``" +msgstr "" + +#: ../../ch-relationships.rst:334 +msgid "" +"When one binary package declares a conflict with another using a " +"``Conflicts`` field, ``dpkg`` will refuse to allow them to be unpacked on" +" the system at the same time. This is a stronger restriction than " +"``Breaks``, which prevents the broken package from being configured while" +" the breaking package is in the \"Unpacked\" state but allows both " +"packages to be unpacked at the same time." +msgstr "" + +#: ../../ch-relationships.rst:341 +msgid "" +"If one package is to be unpacked, the other must be removed first. If the" +" package being unpacked is marked as replacing (see :ref:`s-replaces`, " +"but note that ``Breaks`` should normally be used in this case) the one on" +" the system, or the one on the system is marked as deselected, or both " +"packages are marked ``Essential``, then ``dpkg`` will automatically " +"remove the package which is causing the conflict. Otherwise, it will halt" +" the installation of the new package with an error. This mechanism is " +"specifically designed to produce an error when the installed package is " +"``Essential``, but the new package is not." +msgstr "" + +#: ../../ch-relationships.rst:352 +msgid "" +"A package will not cause a conflict merely because its configuration " +"files are still installed; it must be at least \"Half-Installed\"." +msgstr "" + +#: ../../ch-relationships.rst:355 +msgid "" +"A special exception is made for packages which declare a conflict with " +"their own package name, or with a virtual package which they provide (see" +" below): this does not prevent their installation, and allows a package " +"to conflict with others providing a replacement for it. You use this " +"feature when you want the package in question to be the only package " +"providing some feature." +msgstr "" + +#: ../../ch-relationships.rst:362 +msgid "" +"Normally, ``Breaks`` should be used instead of ``Conflicts`` since " +"``Conflicts`` imposes a stronger restriction on the ordering of package " +"installation or upgrade and can make it more difficult for the package " +"manager to find a correct solution to an upgrade or installation problem." +" ``Breaks`` should be used" +msgstr "" + +#: ../../ch-relationships.rst:368 +msgid "when moving a file from one package to another (see :ref:`s-replaces`)," +msgstr "" + +#: ../../ch-relationships.rst:371 +msgid "when splitting a package (a special case of the previous one), or" +msgstr "" + +#: ../../ch-relationships.rst:373 +msgid "" +"when the breaking package exposes a bug in or interacts badly with " +"particular versions of the broken package." +msgstr "" + +#: ../../ch-relationships.rst:376 +msgid "``Conflicts`` should be used" +msgstr "" + +#: ../../ch-relationships.rst:378 +msgid "when two packages provide the same file and will continue to do so," +msgstr "" + +#: ../../ch-relationships.rst:380 +msgid "" +"in conjunction with ``Provides`` when only one package providing a given " +"virtual facility may be unpacked at a time (see :ref:`s-virtual`)," +msgstr "" + +#: ../../ch-relationships.rst:384 +msgid "" +"in other cases where one must prevent simultaneous installation of two " +"packages for reasons that are ongoing (not fixed in a later version of " +"one of the packages) or that must prevent both packages from being " +"unpacked at the same time, not just configured." +msgstr "" + +#: ../../ch-relationships.rst:389 +msgid "" +"Be aware that adding ``Conflicts`` is normally not the best solution when" +" two packages provide the same files. Depending on the reason for that " +"conflict, using alternatives or renaming the files is often a better " +"approach. See, for example, :ref:`s-binaries`." +msgstr "" + +#: ../../ch-relationships.rst:394 +msgid "" +"Neither ``Breaks`` nor ``Conflicts`` should be used unless two packages " +"cannot be installed at the same time or installing them both causes one " +"of them to be broken or unusable. Having similar functionality or " +"performing the same tasks as another package is not sufficient reason to " +"declare ``Breaks`` or ``Conflicts`` with that package." +msgstr "" + +#: ../../ch-relationships.rst:400 +msgid "" +"A ``Conflicts`` entry may have an \"earlier than\" version clause if the " +"reason for the conflict is corrected in a later version of one of the " +"packages. However, normally the presence of an \"earlier than\" version " +"clause is a sign that ``Breaks`` should have been used instead. An " +"\"earlier than\" version clause in ``Conflicts`` prevents ``dpkg`` from " +"upgrading or installing the package which declares such a conflict until " +"the upgrade or removal of the conflicted-with package has been completed," +" which is a strong restriction." +msgstr "" + +#: ../../ch-relationships.rst:412 +msgid "Virtual packages - ``Provides``" +msgstr "" + +#: ../../ch-relationships.rst:414 +msgid "" +"As well as the names of actual (\"concrete\") packages, the package " +"relationship fields ``Depends``, ``Recommends``, ``Suggests``, " +"``Enhances``, ``Pre-Depends``, ``Breaks``, ``Conflicts``, ``Build-" +"Depends``, ``Build-Depends-Indep``, ``Build-Depends-Arch``, ``Build-" +"Conflicts``, ``Build-Conflicts-Indep`` and ``Build-Conflicts-Arch`` may " +"mention \"virtual packages\"." +msgstr "" + +#: ../../ch-relationships.rst:421 +msgid "" +"A *virtual package* is one which appears in the ``Provides`` control " +"field of another package. The effect is as if the package(s) which " +"provide a particular virtual package name had been listed by name " +"everywhere the virtual package name appears. (See also :ref:`s-virtual-" +"pkg`)" +msgstr "" + +#: ../../ch-relationships.rst:427 +msgid "" +"If there are both concrete and virtual packages of the same name, then " +"the dependency may be satisfied (or the conflict caused) by either the " +"concrete package with the name in question or any other concrete package " +"which provides the virtual package with the name in question. This is so " +"that, for example, supposing we have" +msgstr "" + +#: ../../ch-relationships.rst:438 +msgid "" +"and someone else releases an enhanced version of the ``bar`` package they" +" can say:" +msgstr "" + +#: ../../ch-relationships.rst:446 +msgid "" +"and the ``bar-plus`` package will now also satisfy the dependency for the" +" ``foo`` package." +msgstr "" + +#: ../../ch-relationships.rst:449 +msgid "" +"If a relationship field has a version number attached, only real packages" +" will be considered to see whether the relationship is satisfied (or the " +"prohibition violated, for a conflict or breakage). In other words, if a " +"version number is specified, this is a request to ignore all ``Provides``" +" for that package name and consider only real packages. The package " +"manager will assume that a package providing that virtual package is not " +"of the \"right\" version. A ``Provides`` field may not contain version " +"numbers, and the version number of the concrete package which provides a " +"particular virtual package will not be considered when considering a " +"dependency on or conflict with the virtual package name. [#]_" +msgstr "" + +#: ../../ch-relationships.rst:461 +msgid "" +"To specify which of a set of real packages should be the default to " +"satisfy a particular dependency on a virtual package, list the real " +"package as an alternative before the virtual one." +msgstr "" + +#: ../../ch-relationships.rst:465 +msgid "" +"If the virtual package represents a facility that can only be provided by" +" one real package at a time, such as the mail-transport-agent virtual " +"package that requires installation of a binary that would conflict with " +"all other providers of that virtual package (see :ref:`s-mail-transport-" +"agents`), all packages providing that virtual package should also declare" +" a conflict with it using ``Conflicts``. This will ensure that at most " +"one provider of that virtual package is unpacked or installed at a time." +msgstr "" + +#: ../../ch-relationships.rst:477 +msgid "Overwriting files and replacing packages - ``Replaces``" +msgstr "" + +#: ../../ch-relationships.rst:479 +msgid "" +"Packages can declare in their control file that they should overwrite " +"files in certain other packages, or completely replace other packages. " +"The ``Replaces`` control field has these two distinct purposes." +msgstr "" + +#: ../../ch-relationships.rst:486 +msgid "Overwriting files in other packages" +msgstr "" + +#: ../../ch-relationships.rst:488 +msgid "" +"It is usually an error for a package to contain files which are on the " +"system in another package. However, if the overwriting package declares " +"that it ``Replaces`` the one containing the file being overwritten, then " +"``dpkg`` will replace the file from the old package with that from the " +"new. The file will no longer be listed as \"owned\" by the old package " +"and will be taken over by the new package. Normally, ``Breaks`` should be" +" used in conjunction with ``Replaces``. [#]_" +msgstr "" + +#: ../../ch-relationships.rst:496 +msgid "" +"For example, if a package foo is split into foo and foo-data starting at " +"version 1.2-3, foo-data would have the fields" +msgstr "" + +#: ../../ch-relationships.rst:504 +msgid "" +"in its control file. The new version of the package foo would normally " +"have the field" +msgstr "" + +#: ../../ch-relationships.rst:511 +msgid "" +"(or possibly ``Recommends`` or even ``Suggests`` if the files moved into " +"foo-data are not required for normal operation)." +msgstr "" + +#: ../../ch-relationships.rst:514 +msgid "" +"If a package is completely replaced in this way, so that ``dpkg`` does " +"not know of any files it still contains, it is considered to have " +"\"disappeared\". It will be marked as not wanted on the system (selected " +"for removal) and \"Not-Installed\". Any ``conffile``\\ s details noted " +"for the package will be ignored, as they will have been taken over by the" +" overwriting package. The package's ``postrm`` script will be run with a " +"special argument to allow the package to do any final cleanup required. " +"See :ref:`s-mscriptsinstact`. [#]_" +msgstr "" + +#: ../../ch-relationships.rst:523 +msgid "" +"For this usage of ``Replaces``, virtual packages (see :ref:`s-virtual`) " +"are not considered when looking at a ``Replaces`` field. The packages " +"declared as being replaced must be mentioned by their real names." +msgstr "" + +#: ../../ch-relationships.rst:528 +msgid "" +"This usage of ``Replaces`` only takes effect when both packages are at " +"least partially on the system at once. It is not relevant if the packages" +" conflict unless the conflict has been overridden." +msgstr "" + +#: ../../ch-relationships.rst:535 +msgid "Replacing whole packages, forcing their removal" +msgstr "" + +#: ../../ch-relationships.rst:537 +msgid "" +"Second, ``Replaces`` allows the packaging system to resolve which package" +" should be removed when there is a conflict (see :ref:`s-conflicts`). " +"This usage only takes effect when the two packages *do* conflict, so that" +" the two usages of this field do not interfere with each other." +msgstr "" + +#: ../../ch-relationships.rst:543 +msgid "" +"In this situation, the package declared as being replaced can be a " +"virtual package, so for example, all mail transport agents (MTAs) would " +"have the following fields in their control files:" +msgstr "" + +#: ../../ch-relationships.rst:553 +msgid "" +"ensuring that only one MTA can be unpacked at any one time. See " +":ref:`s-virtual` for more information about this example." +msgstr "" + +#: ../../ch-relationships.rst:559 +msgid "" +"Relationships between source and binary packages - ``Build-Depends``, " +"``Build-Depends-Indep``, ``Build-Depends-Arch``, ``Build-Conflicts``, " +"``Build-Conflicts-Indep``, ``Build-Conflicts-Arch``" +msgstr "" + +#: ../../ch-relationships.rst:561 +msgid "" +"Source packages that require certain binary packages to be installed or " +"absent at the time of building the package can declare relationships to " +"those binary packages." +msgstr "" + +#: ../../ch-relationships.rst:565 +msgid "" +"This is done using the ``Build-Depends``, ``Build-Depends-Indep``, " +"``Build-Depends-Arch``, ``Build-Conflicts``, ``Build-Conflicts-Indep`` " +"and ``Build-Conflicts-Arch`` control fields." +msgstr "" + +#: ../../ch-relationships.rst:569 +msgid "" +"Build-dependencies on \"build-essential\" binary packages can be omitted." +" Please see :ref:`s-pkg-relations` for more information." +msgstr "" + +#: ../../ch-relationships.rst:572 +msgid "" +"The dependencies and conflicts they define must be satisfied (as defined " +"earlier for binary packages) in order to invoke the targets in " +"``debian/rules``, as follows:" +msgstr "" + +#: ../../ch-relationships.rst:578 +msgid "``clean``" +msgstr "" + +#: ../../ch-relationships.rst:577 +msgid "" +"Only the ``Build-Depends`` and ``Build-Conflicts`` fields must be " +"satisfied when this target is invoked." +msgstr "" + +#: ../../ch-relationships.rst:583 +msgid "``build-arch``, and ``binary-arch``" +msgstr "" + +#: ../../ch-relationships.rst:581 +msgid "" +"The ``Build-Depends``, ``Build-Conflicts``, ``Build-Depends-Arch``, and " +"``Build-Conflicts-Arch`` fields must be satisfied when these targets are " +"invoked." +msgstr "" + +#: ../../ch-relationships.rst:588 +msgid "``build-indep``, and ``binary-indep``" +msgstr "" + +#: ../../ch-relationships.rst:586 +msgid "" +"The ``Build-Depends``, ``Build-Conflicts``, ``Build-Depends-Indep``, and " +"``Build-Conflicts-Indep`` fields must be satisfied when these targets are" +" invoked." +msgstr "" + +#: ../../ch-relationships.rst:594 +msgid "``build`` and ``binary``" +msgstr "" + +#: ../../ch-relationships.rst:591 +msgid "" +"The ``Build-Depends``, ``Build-Conflicts``, ``Build-Depends-Indep``, " +"``Build-Conflicts-Indep``, ``Build-Depends-Arch``, and ``Build-Conflicts-" +"Arch`` fields must be satisfied when these targets are invoked." +msgstr "" + +#: ../../ch-relationships.rst:599 +msgid "Additional source packages used to build the binary - ``Built-Using``" +msgstr "" + +#: ../../ch-relationships.rst:601 +msgid "" +"Some binary packages incorporate parts of other packages when built but " +"do not have to depend on those packages. Examples include linking with " +"static libraries or incorporating source code from another package during" +" the build. In this case, the source packages of those other packages are" +" part of the complete source (the binary package is not reproducible " +"without them)." +msgstr "" + +#: ../../ch-relationships.rst:608 +msgid "" +"When the license of either the incorporated parts or the incorporating " +"binary package requires that the full source code of the incorporating " +"binary package be made available, the ``Built-Using`` field must list the" +" corresponding source package for any affected binary package " +"incorporated during the build, [#]_ including an \"exactly equal\" " +"(\"=\") version relation on the version that was used to build that " +"version of the incorporating binary package. [#]_" +msgstr "" + +#: ../../ch-relationships.rst:616 +msgid "" +"This causes the Debian archive to retain the versions of the source " +"packages that were actually incorporated. In particular, if the versions" +" of the incorporated parts are updated but the incorporating binary " +"package is not rebuilt, the older versions of the incorporated parts will" +" remain in the archive in order to satisfy the license." +msgstr "" + +#: ../../ch-relationships.rst:622 +msgid "" +"A package using the source code from the gcc-4.6-source binary package " +"built from the gcc-4.6 source package would have this field in its " +"control file:" +msgstr "" + +#: ../../ch-relationships.rst:630 +msgid "" +"A package including binaries from grub2 and loadlin would have this field" +" in its control file:" +msgstr "" + +#: ../../ch-relationships.rst:637 +msgid "" +"This field should not be added solely for purposes other than satisfying " +"license or DFSG requirements to provide full source code. In particular, " +"it should not be added solely to enable finding packages that should be " +"rebuilt against newer versions of their build dependencies." +msgstr "" + +#: ../../ch-relationships.rst:644 +msgid "" +"While ``Build-Depends``, ``Build-Depends-Indep`` and ``Build-Depends-" +"Arch`` permit the use of alternative dependencies, these are not normally" +" used by the Debian autobuilders. To avoid inconsistency between " +"repeated builds of a package, the autobuilders will default to selecting " +"the first alternative, after reducing any architecture-specific " +"restrictions for the build architecture in question. While this may " +"limit the usefulness of alternatives in a single release, they can still " +"be used to provide flexibility in building the same package across " +"multiple distributions or releases, where a particular dependency is met " +"by differently named packages." +msgstr "" + +#: ../../ch-relationships.rst:657 +msgid "" +"The relations ``<`` and ``>`` were previously allowed, but they were " +"confusingly defined to mean earlier/later or equal rather than strictly " +"earlier/later. ``dpkg`` still supports them with a warning, but they are " +"no longer allowed by Debian Policy." +msgstr "" + +#: ../../ch-relationships.rst:663 +msgid "" +"This approach makes dependency resolution easier. If two packages A and B" +" are being upgraded, the installed package A depends on exactly the " +"installed package B, and the new package A depends on exactly the new " +"package B (a common situation when upgrading shared libraries and their " +"corresponding development packages), satisfying the dependencies at every" +" stage of the upgrade would be impossible. This relaxed restriction means" +" that both new packages can be unpacked together and then configured in " +"their dependency order." +msgstr "" + +#: ../../ch-relationships.rst:673 +msgid "" +"It is possible that a future release of ``dpkg`` may add the ability to " +"specify a version number for each virtual package it provides. This " +"feature is not yet present, however, and is expected to be used only " +"infrequently." +msgstr "" + +#: ../../ch-relationships.rst:679 +msgid "" +"To see why ``Breaks`` is normally needed in addition to ``Replaces``, " +"consider the case of a file in the package foo being taken over by the " +"package foo-data. ``Replaces`` will allow foo-data to be installed and " +"take over that file. However, without ``Breaks``, nothing requires foo to" +" be upgraded to a newer version that knows it does not include that file " +"and instead depends on foo-data. Nothing would prevent the new foo-data " +"package from being installed and then removed, removing the file that it " +"took over from foo. After that operation, the package manager would think" +" the system was in a consistent state, but the foo package would be " +"missing one of its files." +msgstr "" + +#: ../../ch-relationships.rst:692 +msgid "" +"Replaces is a one way relationship. You have to install the replacing " +"package after the replaced package." +msgstr "" + +#: ../../ch-relationships.rst:696 +msgid "" +"``Build-Depends`` in the source package is not adequate since it " +"(rightfully) does not document the exact version used in the build." +msgstr "" + +#: ../../ch-relationships.rst:700 +msgid "" +"The archive software might reject packages that refer to non-existent " +"sources." +msgstr "" + diff --git a/locales/ja/LC_MESSAGES/ch-scope.po b/locales/ja/LC_MESSAGES/ch-scope.po new file mode 100644 index 0000000..d62d0f8 --- /dev/null +++ b/locales/ja/LC_MESSAGES/ch-scope.po @@ -0,0 +1,342 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1996, 1997, 1998 Ian Jackson, Christian Schwarz, 1998-2017, +# The Debian Policy Mailing List +# This file is distributed under the same license as the Debian Policy +# Manual package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2018. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Debian Policy Manual 4.1.6.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-08-02 11:56+0800\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language-Team: LANGUAGE <LL@li.org>\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.4.0\n" + +#: ../../ch-scope.rst:2 +msgid "About this manual" +msgstr "" + +#: ../../ch-scope.rst:7 +msgid "Scope" +msgstr "" + +#: ../../ch-scope.rst:9 +msgid "" +"This manual describes the policy requirements for the Debian " +"distribution. This includes the structure and contents of the Debian " +"archive and several design issues of the operating system, as well as " +"technical requirements that each package must satisfy to be included in " +"the distribution." +msgstr "" + +#: ../../ch-scope.rst:15 +msgid "" +"This manual also describes Debian policy as it relates to creating Debian" +" packages. It is not a tutorial on how to build packages, nor is it " +"exhaustive where it comes to describing the behavior of the packaging " +"system. Instead, this manual attempts to define the interface to the " +"package management system with which the developers must be conversant. " +"[#]_" +msgstr "" + +#: ../../ch-scope.rst:22 +msgid "" +"The footnotes present in this manual are merely informative, and are not " +"part of Debian policy itself." +msgstr "" + +#: ../../ch-scope.rst:25 +msgid "" +"The appendices to this manual are not necessarily normative, either. " +"Please see :doc:`ap-pkg-scope` for more information." +msgstr "" + +#: ../../ch-scope.rst:28 +msgid "" +"In the normative part of this manual, the words *must*, *should* and " +"*may*, and the adjectives *required*, *recommended* and *optional*, are " +"used to distinguish the significance of the various guidelines in this " +"policy document. Packages that do not conform to the guidelines denoted " +"by *must* (or *required*) will generally not be considered acceptable for" +" the Debian distribution. Non-conformance with guidelines denoted by " +"*should* (or *recommended*) will generally be considered a bug, but will " +"not necessarily render a package unsuitable for distribution. Guidelines " +"denoted by *may* (or *optional*) are truly optional and adherence is left" +" to the maintainer's discretion." +msgstr "" + +#: ../../ch-scope.rst:39 +msgid "" +"These classifications are roughly equivalent to the bug severities " +"*serious* (for *must* or *required* directive violations), *minor*, " +"*normal* or *important* (for *should* or *recommended* directive " +"violations) and *wishlist* (for *optional* items). [#]_" +msgstr "" + +#: ../../ch-scope.rst:44 +msgid "" +"Much of the information presented in this manual will be useful even when" +" building a package which is to be distributed in some other way or is " +"intended for local use only." +msgstr "" + +#: ../../ch-scope.rst:48 +msgid "" +"udebs (stripped-down binary packages used by the Debian Installer) do not" +" comply with all of the requirements discussed here. See the `Debian " +"Installer internals manual " +"<https://d-i.alioth.debian.org/doc/internals/ch03.html>`_ for more " +"information about them." +msgstr "" + +#: ../../ch-scope.rst:57 +msgid "New versions of this document" +msgstr "" + +#: ../../ch-scope.rst:59 +msgid "" +"This manual is distributed via the Debian package `debian-policy " +"<https://packages.debian.org/debian-policy>`_." +msgstr "" + +#: ../../ch-scope.rst:62 +msgid "" +"The current version of this document is also available from the Debian " +"web mirrors at https://www.debian.org/doc/debian-policy/. Also available " +"from the same directory are several other formats: `policy.epub " +"<https://www.debian.org/doc/debian-policy/policy.epub>`_, `policy.txt " +"<https://www.debian.org/doc/debian-policy/policy.txt>`_ and `policy.pdf " +"<https://www.debian.org/doc/debian-policy/policy.pdf>`_. Included in both" +" the same directory and in the debian-policy package is a standalone copy" +" of :doc:`upgrading-checklist`, which indicates policy changes between " +"versions of this document." +msgstr "" + +#: ../../ch-scope.rst:78 +msgid "Authors and Maintainers" +msgstr "" + +#: ../../ch-scope.rst:81 +msgid "Early history" +msgstr "" + +#: ../../ch-scope.rst:83 +msgid "" +"Originally called \"Debian GNU/Linux Policy Manual\", this manual was " +"initially written in 1996 by Ian Jackson. It was revised on November " +"27th, 1996 by David A. Morris. Christian Schwarz added new sections on " +"March 15th, 1997, and reworked/restructured it in April-July 1997. " +"Christoph Lameter contributed the \"Web Standard\". Julian Gilbey largely" +" restructured it in 2001. Since September 1998, changes to the contents " +"of this document have been co-ordinated by means of the `debian-policy " +"mailing list <mailto:debian-policy@lists.debian.org>`_" +msgstr "" + +#: ../../ch-scope.rst:93 +msgid "Current process" +msgstr "" + +#: ../../ch-scope.rst:95 +msgid "" +"The Policy Editors are DPL delegates with responsibility for the contents" +" of this document (see the Debian Constitution for the meaning of \"DPL " +"delegate\"). However, the Policy Editors further delegate their " +"editorial power to a process of establishing project member consensus on " +"the debian-policy mailing list, as described in :doc:`ap-process`. The " +"current Policy Editors are:" +msgstr "" + +#: ../../ch-scope.rst:102 +msgid "Russ Allbery" +msgstr "" + +#: ../../ch-scope.rst:104 +msgid "Bill Allombert" +msgstr "" + +#: ../../ch-scope.rst:106 +msgid "Andreas Barth" +msgstr "" + +#: ../../ch-scope.rst:108 +msgid "Sean Whitton" +msgstr "" + +#: ../../ch-scope.rst:111 +msgid "Improvements" +msgstr "" + +#: ../../ch-scope.rst:113 +msgid "" +"While the authors of this document have tried hard to avoid typos and " +"other errors, these do still occur. If you discover an error in this " +"manual or if you want to give any comments, suggestions, or criticisms " +"please send an email to the Debian Policy Mailing List, debian-" +"policy@lists.debian.org, or submit a bug report against the ``debian-" +"policy`` package." +msgstr "" + +#: ../../ch-scope.rst:120 +msgid "" +"Please do not try to reach the individual authors or maintainers of the " +"Policy Manual regarding changes to the Policy." +msgstr "" + +#: ../../ch-scope.rst:123 +msgid "" +"New techniques and functionality are generally implemented in the Debian " +"archive (long) before they are detailed in this document. This is not " +"considered to be a problem: there is a consensus in the Debian Project " +"that the task of keeping this document up-to-date should never block " +"making improvements to Debian. Nevertheless, it is better to submit " +"patches to this document sooner rather than later. This reduces the " +"amount of work that is needed on the part of others to get themselves up-" +"to-speed on new best practices." +msgstr "" + +#: ../../ch-scope.rst:135 +msgid "Related documents" +msgstr "" + +#: ../../ch-scope.rst:137 +msgid "" +"There are several other documents other than this Policy Manual that are " +"necessary to fully understand some Debian policies and procedures." +msgstr "" + +#: ../../ch-scope.rst:140 +msgid "The external \"sub-policy\" documents are referred to in:" +msgstr "" + +#: ../../ch-scope.rst:142 +msgid ":ref:`s-fhs`" +msgstr "" + +#: ../../ch-scope.rst:144 +msgid ":ref:`s-virtual-pkg`" +msgstr "" + +#: ../../ch-scope.rst:146 +msgid ":ref:`s-menus`" +msgstr "" + +#: ../../ch-scope.rst:148 +msgid ":ref:`s-perl`" +msgstr "" + +#: ../../ch-scope.rst:150 +msgid ":ref:`s-maintscriptprompt`" +msgstr "" + +#: ../../ch-scope.rst:152 +msgid ":ref:`s-emacs`" +msgstr "" + +#: ../../ch-scope.rst:154 +msgid "" +"In addition to those, which carry the weight of policy, there is the " +"Debian Developer's Reference. This document describes procedures and " +"resources for Debian developers, but it is *not* normative; rather, it " +"includes things that don't belong in the Policy, such as best practices " +"for developers." +msgstr "" + +#: ../../ch-scope.rst:160 +msgid "" +"The Developer's Reference is available in the developers-reference " +"package. It's also available from the Debian web mirrors at " +"https://www.debian.org/doc/developers-reference/." +msgstr "" + +#: ../../ch-scope.rst:164 +msgid "" +"Finally, a :ref:`specification for machine-readable copyright files " +"<s-copyrightformat>` is maintained as part of the debian-policy package " +"using the same procedure as the other policy documents. Use of this " +"format is optional." +msgstr "" + +#: ../../ch-scope.rst:172 +msgid "Definitions" +msgstr "" + +#: ../../ch-scope.rst:174 +msgid "The following terms are used in this Policy Manual:" +msgstr "" + +#: ../../ch-scope.rst:181 +msgid "ASCII" +msgstr "" + +#: ../../ch-scope.rst:177 +msgid "" +"The character encoding specified by ANSI X3.4-1986 and its predecessor " +"standards, referred to in MIME as US-ASCII, and corresponding to an " +"encoding in eight bits per character of the first 128 `Unicode " +"<http://www.unicode.org/>`_ characters, with the eighth bit always zero." +msgstr "" + +#: ../../ch-scope.rst:188 +msgid "UTF-8" +msgstr "" + +#: ../../ch-scope.rst:184 +msgid "" +"The transformation format (sometimes called encoding) of `Unicode " +"<http://www.unicode.org/>`_ defined by `RFC 3629 <https://www.rfc-" +"editor.org/rfc/rfc3629.txt>`__. UTF-8 has the useful property of having " +"ASCII as a subset, so any text encoded in ASCII is trivially also valid " +"UTF-8." +msgstr "" + +#: ../../ch-scope.rst:191 +msgid "" +"Informally, the criteria used for inclusion is that the material meet one" +" of the following requirements:" +msgstr "" + +#: ../../ch-scope.rst:201 +msgid "Standard interfaces" +msgstr "" + +#: ../../ch-scope.rst:195 +msgid "" +"The material presented represents an interface to the packaging system " +"that is mandated for use, and is used by, a significant number of " +"packages, and therefore should not be changed without peer review. " +"Package maintainers can then rely on this interface not changing, and the" +" package management software authors need to ensure compatibility with " +"this interface definition. (Control file and changelog file formats are " +"examples.)" +msgstr "" + +#: ../../ch-scope.rst:206 +msgid "Chosen Convention" +msgstr "" + +#: ../../ch-scope.rst:204 +msgid "" +"If there are a number of technically viable choices that can be made, but" +" one needs to select one of these options for inter-operability. The " +"version number format is one example." +msgstr "" + +#: ../../ch-scope.rst:208 +msgid "" +"Please note that these are not mutually exclusive; selected conventions " +"often become parts of standard interfaces." +msgstr "" + +#: ../../ch-scope.rst:212 +msgid "" +"Compare RFC 2119. Note, however, that these words are used in a different" +" way in this document." +msgstr "" + diff --git a/locales/ja/LC_MESSAGES/ch-sharedlibs.po b/locales/ja/LC_MESSAGES/ch-sharedlibs.po new file mode 100644 index 0000000..af7e79c --- /dev/null +++ b/locales/ja/LC_MESSAGES/ch-sharedlibs.po @@ -0,0 +1,1180 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1996, 1997, 1998 Ian Jackson, Christian Schwarz, 1998-2017, +# The Debian Policy Mailing List +# This file is distributed under the same license as the Debian Policy +# Manual package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2018. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Debian Policy Manual 4.1.6.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-08-02 11:56+0800\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language-Team: LANGUAGE <LL@li.org>\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.4.0\n" + +#: ../../ch-sharedlibs.rst:2 +msgid "Shared libraries" +msgstr "" + +#: ../../ch-sharedlibs.rst:4 +msgid "" +"Packages containing shared libraries must be constructed with a little " +"care to make sure that the shared library is always available. This is " +"especially important for packages whose shared libraries are vitally " +"important, such as the C library (currently ``libc6``)." +msgstr "" + +#: ../../ch-sharedlibs.rst:9 +msgid "" +"This section deals only with public shared libraries: shared libraries " +"that are placed in directories searched by the dynamic linker by default " +"or which are intended to be linked against normally and possibly used by " +"other, independent packages. Shared libraries that are internal to a " +"particular package or that are only loaded as dynamic modules are not " +"covered by this section and are not subject to its requirements." +msgstr "" + +#: ../../ch-sharedlibs.rst:16 +msgid "" +"A shared library is identified by the ``SONAME`` attribute stored in its " +"dynamic section. When a binary is linked against a shared library, the " +"``SONAME`` of the shared library is recorded in the binary's ``NEEDED`` " +"section so that the dynamic linker knows that library must be loaded at " +"runtime. The shared library file's full name (which usually contains " +"additional version information not needed in the ``SONAME``) is therefore" +" normally not referenced directly. Instead, the shared library is loaded " +"by its ``SONAME``, which exists on the file system as a symlink pointing " +"to the full name of the shared library. This symlink must be provided by " +"the package. :ref:`s-sharedlibs-runtime` describes how to do this. [#]_" +msgstr "" + +#: ../../ch-sharedlibs.rst:27 +msgid "" +"When linking a binary or another shared library against a shared library," +" the ``SONAME`` for that shared library is not yet known. Instead, the " +"shared library is found by looking for a file matching the library name " +"with ``.so`` appended. This file exists on the file system as a symlink " +"pointing to the shared library." +msgstr "" + +#: ../../ch-sharedlibs.rst:33 +msgid "" +"Shared libraries are normally split into several binary packages. The " +"``SONAME`` symlink is installed by the runtime shared library package, " +"and the bare ``.so`` symlink is installed in the development package " +"since it's only used when linking binaries or shared libraries. However, " +"there are some exceptions for unusual shared libraries or for shared " +"libraries that are also loaded as dynamic modules by other programs." +msgstr "" + +#: ../../ch-sharedlibs.rst:40 +msgid "" +"This section is primarily concerned with how the separation of shared " +"libraries into multiple packages should be done and how dependencies on " +"and between shared library binary packages are managed in Debian. " +":ref:`s-libraries` should be read in conjunction with this section and " +"contains additional rules for the files contained in the shared library " +"packages." +msgstr "" + +#: ../../ch-sharedlibs.rst:47 +msgid "" +"This is a convention of shared library versioning, but not a requirement." +" Some libraries use the ``SONAME`` as the full library file name instead " +"and therefore do not need a symlink. Most, however, encode additional " +"information about backwards-compatible revisions as a minor version " +"number in the file name. The ``SONAME`` itself only changes when binaries" +" linked with the earlier version of the shared library may no longer " +"work, but the filename may change with each release of the library. See " +":ref:`s-sharedlibs-runtime` for more information." +msgstr "" + +#: ../../ch-sharedlibs.rst:60 +msgid "Run-time shared libraries" +msgstr "" + +#: ../../ch-sharedlibs.rst:62 +msgid "" +"The run-time shared library must be placed in a package whose name " +"changes whenever the ``SONAME`` of the shared library changes. This " +"allows several versions of the shared library to be installed at the same" +" time, allowing installation of the new version of the shared library " +"without immediately breaking binaries that depend on the old version. " +"Normally, the run-time shared library and its ``SONAME`` symlink should " +"be placed in a package named libraryname\\ *soversion*, where *soversion*" +" is the version number in the ``SONAME`` of the shared library. " +"Alternatively, if it would be confusing to directly append *soversion* to" +" libraryname (if, for example, libraryname itself ends in a number), you " +"should use libraryname-\\ *soversion* instead. [#]_" +msgstr "" + +#: ../../ch-sharedlibs.rst:74 +msgid "" +"To determine the *soversion*, look at the ``SONAME`` of the library, " +"stored in the ELF ``SONAME`` attribute. It is usually of the form " +"``name.so.major-version`` (for example, ``libz.so.1``). The version part " +"is the part which comes after ``.so.``, so in that example it is ``1``. " +"The soname may instead be of the form ``name-major-version.so``, such as " +"``libdb-5.1.so``, in which case the name would be ``libdb`` and the " +"version would be ``5.1``." +msgstr "" + +#: ../../ch-sharedlibs.rst:82 +msgid "" +"If you have several shared libraries built from the same source tree, you" +" may lump them all together into a single shared library package provided" +" that all of their ``SONAME``\\ s will always change together. Be aware " +"that this is not normally the case, and if the ``SONAME``\\ s do not " +"change together, upgrading such a merged shared library package will be " +"unnecessarily difficult because of file conflicts with the old version of" +" the package. When in doubt, always split shared library packages so that" +" each binary package installs a single shared library." +msgstr "" + +#: ../../ch-sharedlibs.rst:91 +msgid "" +"Every time the shared library ABI changes in a way that may break " +"binaries linked against older versions of the shared library, the " +"``SONAME`` of the library and the corresponding name for the binary " +"package containing the runtime shared library should change. Normally, " +"this means the ``SONAME`` should change any time an interface is removed " +"from the shared library or the signature of an interface (the number of " +"parameters or the types of parameters that it takes, for example) is " +"changed. This practice is vital to allowing clean upgrades from older " +"versions of the package and clean transitions between the old ABI and new" +" ABI without having to upgrade every affected package simultaneously." +msgstr "" + +#: ../../ch-sharedlibs.rst:102 +msgid "" +"The ``SONAME`` and binary package name need not, and indeed normally " +"should not, change if new interfaces are added but none are removed or " +"changed, since this will not break binaries linked against the old shared" +" library. Correct versioning of dependencies on the newer shared library " +"by binaries that use the new interfaces is handled via the ``symbols`` or" +" ``shlibs`` system (see :ref:`s-sharedlibs-depends`)." +msgstr "" + +#: ../../ch-sharedlibs.rst:109 +msgid "" +"The package should install the shared libraries under their normal names." +" For example, the libgdbm3 package should install ``libgdbm.so.3.0.0`` as" +" ``/usr/lib/libgdbm.so.3.0.0``. The files should not be renamed or re-" +"linked by any ``prerm`` or ``postrm`` scripts; ``dpkg`` will take care of" +" renaming things safely without affecting running programs, and attempts " +"to interfere with this are likely to lead to problems." +msgstr "" + +#: ../../ch-sharedlibs.rst:117 +msgid "" +"Shared libraries should not be installed executable, since the dynamic " +"linker does not require this and trying to execute a shared library " +"usually results in a core dump." +msgstr "" + +#: ../../ch-sharedlibs.rst:121 +msgid "" +"The run-time library package should include the symbolic link for the " +"``SONAME`` that ``ldconfig`` would create for the shared libraries. For " +"example, the libgdbm3 package should include a symbolic link from " +"``/usr/lib/libgdbm.so.3`` to ``libgdbm.so.3.0.0``. This is needed so that" +" the dynamic linker (for example ``ld.so`` or ``ld-linux.so.*``) can find" +" the library between the time that ``dpkg`` installs it and the time that" +" ``ldconfig`` is run in the ``postinst`` script. [#]_" +msgstr "" + +#: ../../ch-sharedlibs.rst:129 +msgid "" +"The following command, when run on a shared library, will output the name" +" to be used for the Debian package containing that shared library::" +msgstr "" + +#: ../../ch-sharedlibs.rst:137 +msgid "" +"The package management system requires the library to be placed before " +"the symbolic link pointing to it in the ``.deb`` file. This is so that " +"when ``dpkg`` comes to install the symlink (overwriting the previous " +"symlink pointing at an older version of the library), the new shared " +"library is already in place. In the past, this was achieved by creating " +"the library in the temporary packaging directory before creating the " +"symlink. Unfortunately, this was not always effective, since the building" +" of the tar file in the ``.deb`` depended on the behavior of the " +"underlying file system. Some file systems (such as reiserfs) reorder the " +"files so that the order of creation is forgotten. Since version 1.7.0, " +"``dpkg`` reorders the files itself as necessary when building a package. " +"Thus it is no longer important to concern oneself with the order of file " +"creation." +msgstr "" + +#: ../../ch-sharedlibs.rst:155 +msgid "``ldconfig``" +msgstr "" + +#: ../../ch-sharedlibs.rst:157 +msgid "" +"Any package installing shared libraries in one of the default library " +"directories of the dynamic linker (which are currently ``/usr/lib`` and " +"``/lib``) or a directory that is listed in ``/etc/ld.so.conf`` [#]_ must " +"use ``ldconfig`` to update the shared library system." +msgstr "" + +#: ../../ch-sharedlibs.rst:162 +msgid "" +"Any such package must have the line ``activate-noawait ldconfig`` in its " +"``triggers`` control file (i.e. ``DEBIAN/triggers``)." +msgstr "" + +#: ../../ch-sharedlibs.rst:165 +msgid "" +"These are currently ``/usr/local/lib`` plus directories under ``/lib`` " +"and ``/usr/lib`` matching the multiarch triplet for the system " +"architecture." +msgstr "" + +#: ../../ch-sharedlibs.rst:172 +msgid "Shared library support files" +msgstr "" + +#: ../../ch-sharedlibs.rst:174 +msgid "" +"If your package contains files whose names do not change with each change" +" in the library shared object version, you must not put them in the " +"shared library package. Otherwise, several versions of the shared library" +" cannot be installed at the same time without filename clashes, making " +"upgrades and transitions unnecessarily difficult." +msgstr "" + +#: ../../ch-sharedlibs.rst:180 +msgid "" +"It is recommended that supporting files and run-time support programs " +"that do not need to be invoked manually by users, but are nevertheless " +"required for the package to function, be placed (if they are binary) in a" +" subdirectory of ``/usr/lib``, preferably under ``/usr/lib/``\\ package-" +"name. If the program or file is architecture independent, the " +"recommendation is for it to be placed in a subdirectory of ``/usr/share``" +" instead, preferably under ``/usr/share/``\\ package-name. Following the " +"package-name naming convention ensures that the file names change when " +"the shared object version changes." +msgstr "" + +#: ../../ch-sharedlibs.rst:191 +msgid "" +"Run-time support programs that use the shared library but are not " +"required for the library to function or files used by the shared library " +"that can be used by any version of the shared library package should " +"instead be put in a separate package. This package might typically be " +"named libraryname-tools; note the absence of the soversion in the package" +" name." +msgstr "" + +#: ../../ch-sharedlibs.rst:198 +msgid "" +"Files and support programs only useful when compiling software against " +"the library should be included in the development package for the " +"library. [#]_" +msgstr "" + +#: ../../ch-sharedlibs.rst:202 +msgid "" +"For example, a ``package-name-config`` script or pkg-config configuration" +" files." +msgstr "" + +#: ../../ch-sharedlibs.rst:208 +msgid "Static libraries" +msgstr "" + +#: ../../ch-sharedlibs.rst:210 +msgid "" +"The static library (``libraryname.a``) is usually provided in addition to" +" the shared version. It is placed into the development package (see " +"below)." +msgstr "" + +#: ../../ch-sharedlibs.rst:214 +msgid "" +"In some cases, it is acceptable for a library to be available in static " +"form only; these cases include:" +msgstr "" + +#: ../../ch-sharedlibs.rst:217 +msgid "" +"libraries for languages whose shared library support is immature or " +"unstable" +msgstr "" + +#: ../../ch-sharedlibs.rst:220 +msgid "" +"libraries whose interfaces are in flux or under development (commonly the" +" case when the library's major version number is zero, or where the ABI " +"breaks across patchlevels)" +msgstr "" + +#: ../../ch-sharedlibs.rst:224 +msgid "" +"libraries which are explicitly intended to be available only in static " +"form by their upstream author(s)" +msgstr "" + +#: ../../ch-sharedlibs.rst:230 +msgid "Development files" +msgstr "" + +#: ../../ch-sharedlibs.rst:232 +msgid "" +"If there are development files associated with a shared library, the " +"source package needs to generate a binary development package named " +"libraryname-dev, or if you need to support multiple development versions " +"at a time, librarynameapiversion-dev. Installing the development package " +"must result in installation of all the development files necessary for " +"compiling programs against that shared library. [#]_" +msgstr "" + +#: ../../ch-sharedlibs.rst:239 +msgid "" +"In case several development versions of a library exist, you may need to " +"use ``dpkg``'s Conflicts mechanism (see :ref:`s-conflicts`) to ensure " +"that the user only installs one development version at a time (as " +"different development versions are likely to have the same header files " +"in them, which would cause a filename clash if both were unpacked)." +msgstr "" + +#: ../../ch-sharedlibs.rst:245 +msgid "" +"The development package should contain a symlink for the associated " +"shared library without a version number. For example, the libgdbm-dev " +"package should include a symlink from ``/usr/lib/libgdbm.so`` to " +"``libgdbm.so.3.0.0``. This symlink is needed by the linker (``ld``) when " +"compiling packages, as it will only look for ``libgdbm.so`` when " +"compiling dynamically." +msgstr "" + +#: ../../ch-sharedlibs.rst:252 +msgid "" +"If the package provides Ada Library Information (``*.ali``) files for use" +" with GNAT, these files must be installed read-only (mode 0444) so that " +"GNAT will not attempt to recompile them. This overrides the normal file " +"mode requirements given in :ref:`s-permissions-owners`." +msgstr "" + +#: ../../ch-sharedlibs.rst:257 +msgid "" +"This wording allows the development files to be split into several " +"packages, such as a separate architecture-independent libraryname-" +"headers, provided that the development package depends on all the " +"required additional packages." +msgstr "" + +#: ../../ch-sharedlibs.rst:265 +msgid "Dependencies between the packages of the same library" +msgstr "" + +#: ../../ch-sharedlibs.rst:267 +msgid "" +"Typically the development version should have an exact version dependency" +" on the runtime library, to make sure that compilation and linking " +"happens correctly. The ``${binary:Version}`` substitution variable can be" +" useful for this purpose. [#]_" +msgstr "" + +#: ../../ch-sharedlibs.rst:272 +msgid "" +"Previously, ``${Source-Version}`` was used, but its name was confusing " +"and it has been deprecated since dpkg 1.13.19." +msgstr "" + +#: ../../ch-sharedlibs.rst:278 +msgid "Dependencies between the library and other packages" +msgstr "" + +#: ../../ch-sharedlibs.rst:280 +msgid "" +"If a package contains a binary or library which links to a shared " +"library, we must ensure that, when the package is installed on the " +"system, all of the libraries needed are also installed. These " +"dependencies must be added to the binary package when it is built, since " +"they may change based on which version of a shared library the binary or " +"library was linked with even if there are no changes to the source of the" +" binary (for example, symbol versions change, macros become functions or " +"vice versa, or the binary package may determine at compile-time whether " +"new library interfaces are available and can be called). To allow these " +"dependencies to be constructed, shared libraries must provide either a " +"``symbols`` file or a ``shlibs`` file. These provide information on the " +"package dependencies required to ensure the presence of interfaces " +"provided by this library. Any package with binaries or libraries linking " +"to a shared library must use these files to determine the required " +"dependencies when it is built. Other packages which use a shared library " +"(for example using ``dlopen()``) should compute appropriate dependencies " +"using these files at build time as well." +msgstr "" + +#: ../../ch-sharedlibs.rst:298 +msgid "" +"The two mechanisms differ in the degree of detail that they provide. A " +"``symbols`` file documents, for each symbol exported by a library, the " +"minimal version of the package any binary using this symbol will need. " +"This is typically the version of the package in which the symbol was " +"introduced. This information permits detailed analysis of the symbols " +"used by a particular package and construction of an accurate dependency, " +"but it requires the package maintainer to track more information about " +"the shared library." +msgstr "" + +#: ../../ch-sharedlibs.rst:307 +msgid "" +"A ``shlibs`` file, in contrast, only documents the last time the library " +"ABI changed in any way. It only provides information about the library as" +" a whole, not individual symbols. When a package is built using a shared " +"library with only a ``shlibs`` file, the generated dependency will " +"require a version of the shared library equal to or newer than the " +"version of the last ABI change. This generates unnecessarily restrictive " +"dependencies compared to ``symbols`` files if none of the symbols used by" +" the package have changed. This, in turn, may make upgrades needlessly " +"complex and unnecessarily restrict use of the package on systems with " +"older versions of the shared libraries." +msgstr "" + +#: ../../ch-sharedlibs.rst:318 +msgid "" +"``shlibs`` files also only support a limited range of library SONAMEs, " +"making it difficult to use ``shlibs`` files in some unusual corner cases." +" [#]_" +msgstr "" + +#: ../../ch-sharedlibs.rst:322 +msgid "" +"``symbols`` files are therefore recommended for most shared library " +"packages since they provide more accurate dependencies. For most C " +"libraries, the additional detail required by ``symbols`` files is not too" +" difficult to maintain. However, maintaining exhaustive symbols " +"information for a C++ library can be quite onerous, so ``shlibs`` files " +"may be more appropriate for most C++ libraries. Libraries with a " +"corresponding udeb must also provide a ``shlibs`` file, since the udeb " +"infrastructure does not use ``symbols`` files." +msgstr "" + +#: ../../ch-sharedlibs.rst:331 +msgid "" +"A ``shlibs`` file represents an SONAME as a library name and version " +"number, such as ``libfoo VERSION``, instead of recording the actual " +"SONAME. If the SONAME doesn't match one of the two expected formats " +"(``libfoo-VERSION.so`` or ``libfoo.so.VERSION``), it cannot be " +"represented." +msgstr "" + +#: ../../ch-sharedlibs.rst:340 +msgid "Generating dependencies on shared libraries" +msgstr "" + +#: ../../ch-sharedlibs.rst:342 +msgid "" +"When a package that contains any shared libraries or compiled binaries is" +" built, it must run ``dpkg-shlibdeps`` on each shared library and " +"compiled binary to determine the libraries used and hence the " +"dependencies needed by the package. [#]_ To do this, put a call to " +"``dpkg-shlibdeps`` into your ``debian/rules`` file in the source package." +" List all of the compiled binaries, libraries, or loadable modules in " +"your package. [#]_ ``dpkg-shlibdeps`` will use the ``symbols`` or " +"``shlibs`` files installed by the shared libraries to generate dependency" +" information. The package must then provide a substitution variable into " +"which the discovered dependency information can be placed." +msgstr "" + +#: ../../ch-sharedlibs.rst:353 +msgid "" +"If you are creating a udeb for use in the Debian Installer, you will need" +" to specify that ``dpkg-shlibdeps`` should use the dependency line of " +"type ``udeb`` by adding the ``-tudeb`` option. [#]_ If there is no " +"dependency line of type ``udeb`` in the ``shlibs`` file, ``dpkg-" +"shlibdeps`` will fall back to the regular dependency line." +msgstr "" + +#: ../../ch-sharedlibs.rst:359 +msgid "" +"``dpkg-shlibdeps`` puts the dependency information into the " +"``debian/substvars`` file by default, which is then used by ``dpkg-" +"gencontrol``. You will need to place a ``${shlibs:Depends}`` variable in " +"the ``Depends`` field in the control file of every binary package built " +"by this source package that contains compiled binaries, libraries, or " +"loadable modules. If you have multiple binary packages, you will need to " +"call ``dpkg-shlibdeps`` on each one which contains compiled libraries or " +"binaries. For example, you could use the ``-T`` option to the ``dpkg`` " +"utilities to specify a different ``substvars`` file for each binary " +"package. [#]_" +msgstr "" + +#: ../../ch-sharedlibs.rst:370 +msgid "For more details on ``dpkg-shlibdeps``, see its manual page." +msgstr "" + +#: ../../ch-sharedlibs.rst:372 +msgid "" +"We say that a binary ``foo`` *directly* uses a library ``libbar`` if it " +"is explicitly linked with that library (that is, the library is listed in" +" the ELF ``NEEDED`` attribute, caused by adding ``-lbar`` to the link " +"line when the binary is created). Other libraries that are needed by " +"``libbar`` are linked *indirectly* to ``foo``, and the dynamic linker " +"will load them automatically when it loads ``libbar``. A package should " +"depend on the libraries it directly uses, but not the libraries it only " +"uses indirectly. The dependencies for the libraries used directly will " +"automatically pull in the indirectly-used libraries. ``dpkg-shlibdeps`` " +"will handle this logic automatically, but package maintainers need to be " +"aware of this distinction between directly and indirectly using a library" +" if they have to override its results for some reason. [#]_" +msgstr "" + +#: ../../ch-sharedlibs.rst:385 +msgid "" +"``dpkg-shlibdeps`` will use a program like ``objdump`` or ``readelf`` to " +"find the libraries and the symbols in those libraries directly needed by " +"the binaries or shared libraries in the package." +msgstr "" + +#: ../../ch-sharedlibs.rst:390 +msgid "" +"The easiest way to call ``dpkg-shlibdeps`` correctly is to use a package " +"helper framework such as debhelper. If you are using debhelper, the " +"``dh_shlibdeps`` program will do this work for you. It will also " +"correctly handle multi-binary packages." +msgstr "" + +#: ../../ch-sharedlibs.rst:395 +msgid "" +"``dh_shlibdeps`` from the ``debhelper`` suite will automatically add this" +" option if it knows it is processing a udeb." +msgstr "" + +#: ../../ch-sharedlibs.rst:398 +msgid "" +"Again, ``dh_shlibdeps`` and ``dh_gencontrol`` will handle everything " +"except the addition of the variable to the control file for you if you're" +" using debhelper, including generating separate ``substvars`` files for " +"each binary package and calling ``dpkg-gencontrol`` with the appropriate " +"flags." +msgstr "" + +#: ../../ch-sharedlibs.rst:404 +msgid "" +"A good example of where this helps is the following: We could update " +"``libimlib`` with a new version that supports a new revision of a " +"graphics format called dgf (but retaining the same major version number) " +"and depends on a new library package libdgf4 instead of the older " +"libdgf3. If we used ``ldd`` to add dependencies for every library " +"directly or indirectly linked with a binary, every package that uses " +"``libimlib`` would need to be recompiled so it would also depend on " +"libdgf4 in order to retire the older libdgf3 package. Since dependencies " +"are only added based on ELF ``NEEDED`` attribute, packages using " +"``libimlib`` can rely on ``libimlib`` itself having the dependency on an " +"appropriate version of ``libdgf`` and do not need rebuilding." +msgstr "" + +#: ../../ch-sharedlibs.rst:420 +msgid "Shared library ABI changes" +msgstr "" + +#: ../../ch-sharedlibs.rst:422 +msgid "" +"Maintaining a shared library package using either ``symbols`` or " +"``shlibs`` files requires being aware of the exposed ABI of the shared " +"library and any changes to it. Both ``symbols`` and ``shlibs`` files " +"record every change to the ABI of the shared library; ``symbols`` files " +"do so per public symbol, whereas ``shlibs`` files record only the last " +"change for the entire library." +msgstr "" + +#: ../../ch-sharedlibs.rst:429 +msgid "" +"There are two types of ABI changes: ones that are backward-compatible and" +" ones that are not. An ABI change is backward-compatible if any " +"reasonable program or library that was linked with the previous version " +"of the shared library will still work correctly with the new version of " +"the shared library. [#]_ Adding new symbols to the shared library is a " +"backward-compatible change. Removing symbols from the shared library is " +"not. Changing the behavior of a symbol may or may not be backward-" +"compatible depending on the change; for example, changing a function to " +"accept a new enum constant not previously used by the library is " +"generally backward-compatible, but changing the members of a struct that " +"is passed into library functions is generally not unless the library " +"takes special precautions to accept old versions of the data structure." +msgstr "" + +#: ../../ch-sharedlibs.rst:443 +msgid "" +"ABI changes that are not backward-compatible normally require changing " +"the ``SONAME`` of the library and therefore the shared library package " +"name, which forces rebuilding all packages using that shared library to " +"update their dependencies and allow them to use the new version of the " +"shared library. For more information, see :ref:`s-sharedlibs-runtime`. " +"The remainder of this section will deal with backward-compatible changes." +msgstr "" + +#: ../../ch-sharedlibs.rst:450 +msgid "" +"Backward-compatible changes require either updating or recording the " +"minimal-version for that symbol in ``symbols`` files or updating the " +"version in the dependencies in ``shlibs`` files. For more information on " +"how to do this in the two formats, see :ref:`s-symbols` and " +":ref:`s-shlibs`. Below are general rules that apply to both files." +msgstr "" + +#: ../../ch-sharedlibs.rst:456 +msgid "" +"The easy case is when a public symbol is added. Simply add the version at" +" which the symbol was introduced (for ``symbols`` files) or update the " +"dependency version (for ``shlibs``) files. But special care should be " +"taken to update dependency versions when the behavior of a public symbol " +"changes. This is easy to neglect, since there is no automated method of " +"determining such changes, but failing to update versions in this case may" +" result in binary packages with too-weak dependencies that will fail at " +"runtime, possibly in ways that can cause security vulnerabilities. If the" +" package maintainer believes that a symbol behavior change may have " +"occurred but isn't sure, it's safer to update the version rather than " +"leave it unmodified. This may result in unnecessarily strict " +"dependencies, but it ensures that packages whose dependencies are " +"satisfied will work properly." +msgstr "" + +#: ../../ch-sharedlibs.rst:470 +msgid "" +"A common example of when a change to the dependency version is required " +"is a function that takes an enum or struct argument that controls what " +"the function does. For example::" +msgstr "" + +#: ../../ch-sharedlibs.rst:477 +msgid "" +"If a new operation, ``OP_BAZ``, is added, the minimal-version of " +"``library_do_operation`` (for ``symbols`` files) or the version in the " +"dependency for the shared library (for ``shlibs`` files) must be " +"increased to the version at which ``OP_BAZ`` was introduced. Otherwise, a" +" binary built against the new version of the library (having detected at " +"compile-time that the library supports ``OP_BAZ``) may be installed with " +"a shared library that doesn't support ``OP_BAZ`` and will fail at runtime" +" when it tries to pass ``OP_BAZ`` into this function." +msgstr "" + +#: ../../ch-sharedlibs.rst:486 +msgid "" +"Dependency versions in either ``symbols`` or ``shlibs`` files normally " +"should not contain the Debian revision of the package, since the library " +"behavior is normally fixed for a particular upstream version and any " +"Debian packaging of that upstream version will have the same behavior. In" +" the rare case that the library behavior was changed in a particular " +"Debian revision, appending ``~`` to the end of the version that includes " +"the Debian revision is recommended, since this allows backports of the " +"shared library package using the normal backport versioning convention to" +" satisfy the dependency." +msgstr "" + +#: ../../ch-sharedlibs.rst:496 +msgid "" +"An example of an \"unreasonable\" program is one that uses library " +"interfaces that are documented as internal and unsupported. If the only " +"programs or libraries affected by a change are \"unreasonable\" ones, " +"other techniques, such as declaring ``Breaks`` relationships with " +"affected packages or treating their usage of the library as bugs in those" +" packages, may be appropriate instead of changing the SONAME. However, " +"the default approach is to change the SONAME for any change to the ABI " +"that could break a program." +msgstr "" + +#: ../../ch-sharedlibs.rst:508 +msgid "The ``symbols`` system" +msgstr "" + +#: ../../ch-sharedlibs.rst:510 +msgid "" +"In the following sections, we will first describe where the various " +"``symbols`` files are to be found, then the ``symbols`` file format, and " +"finally how to create ``symbols`` files if your package contains a shared" +" library." +msgstr "" + +#: ../../ch-sharedlibs.rst:518 +msgid "The ``symbols`` files present on the system" +msgstr "" + +#: ../../ch-sharedlibs.rst:520 +msgid "" +"``symbols`` files for a shared library are normally provided by the " +"shared library package as a control file, but there are several override " +"paths that are checked first in case that information is wrong or " +"missing. The following list gives them in the order in which they are " +"read by ``dpkg-shlibdeps``. The first one that contains the required " +"information is used." +msgstr "" + +#: ../../ch-sharedlibs.rst:539 +msgid "``debian/*/DEBIAN/symbols``" +msgstr "" + +#: ../../ch-sharedlibs.rst:528 +msgid "" +"During the package build, if the package itself contains shared libraries" +" with ``symbols`` files, they will be generated in these staging " +"directories by ``dpkg-gensymbols`` (see `Providing a symbols file <#s" +"-providing-symbols>`__). ``symbols`` files found in the build tree take " +"precedence over ``symbols`` files from other binary packages." +msgstr "" + +#: ../../ch-sharedlibs.rst:535 +msgid "" +"These files must exist before ``dpkg-shlibdeps`` is run or the " +"dependencies of binaries and libraries from a source package on other " +"libraries from that same source package will not be correct. In practice," +" this means that ``dpkg-gensymbols`` must be run before ``dpkg-" +"shlibdeps`` during the package build. [#]_" +msgstr "" + +#: ../../ch-sharedlibs.rst:544 +msgid "" +"``/etc/dpkg/symbols/package.symbols.arch`` and " +"``/etc/dpkg/symbols/package.symbols``" +msgstr "" + +#: ../../ch-sharedlibs.rst:542 +msgid "" +"Per-system overrides of shared library dependencies. These files normally" +" do not exist. They are maintained by the local system administrator and " +"must not be created by any Debian package." +msgstr "" + +#: ../../ch-sharedlibs.rst:550 +msgid "``symbols`` control files for packages installed on the system" +msgstr "" + +#: ../../ch-sharedlibs.rst:547 +msgid "" +"The ``symbols`` control files for all the packages currently installed on" +" the system are searched last. This will be the most common source of " +"shared library dependency information. These files can be read with " +"``dpkg-query --control-show package symbols``." +msgstr "" + +#: ../../ch-sharedlibs.rst:552 +msgid "" +"Be aware that if a ``debian/shlibs.local`` exists in the source package, " +"it will override any ``symbols`` files. This is the only case where a " +"``shlibs`` is used despite ``symbols`` files being present. See :ref:`s" +"-shlibs-paths` and :ref:`s-sharedlibs-shlibdeps` for more information." +msgstr "" + +#: ../../ch-sharedlibs.rst:558 +msgid "" +"An example may clarify. Suppose the source package ``foo`` generates two " +"binary packages, ``libfoo2`` and ``foo-runtime``. When building the " +"binary packages, the contents of the packages are staged in the " +"directories ``debian/libfoo2`` and ``debian/foo-runtime`` respectively. " +"(``debian/tmp`` could be used instead of one of these.) Since " +"``libfoo2`` provides the ``libfoo`` shared library, it will contain a " +"``symbols`` file, which will be installed in " +"``debian/libfoo2/DEBIAN/symbols``, eventually to be included as a control" +" file in that package. When ``dpkg-shlibdeps`` is run on the executable " +"``debian/foo-runtime/usr/bin/foo-prog``, it will examine the " +"``debian/libfoo2/DEBIAN/symbols`` file to determine whether ``foo-" +"prog``'s library dependencies are satisfied by any of the libraries " +"provided by ``libfoo2``. Since those binaries were linked against the " +"just-built shared library as part of the build process, the ``symbols`` " +"file for the newly-built ``libfoo2`` must take precedence over a " +"``symbols`` file for any other ``libfoo2`` package already installed on " +"the system." +msgstr "" + +#: ../../ch-sharedlibs.rst:580 +msgid "The ``symbols`` File Format" +msgstr "" + +#: ../../ch-sharedlibs.rst:582 +msgid "" +"The following documents the format of the ``symbols`` control file as " +"included in binary packages. These files are built from template " +"``symbols`` files in the source package by ``dpkg-gensymbols``. The " +"template files support a richer syntax that allows ``dpkg-gensymbols`` to" +" do some of the tedious work involved in maintaining ``symbols`` files, " +"such as handling C++ symbols or optional symbols that may not exist on " +"particular architectures. When writing ``symbols`` files for a shared " +"library package, refer to dpkg-gensymbols(1) for the richer syntax." +msgstr "" + +#: ../../ch-sharedlibs.rst:591 +msgid "" +"A ``symbols`` may contain one or more entries, one for each shared " +"library contained in the package corresponding to that ``symbols``. Each " +"entry has the following format::" +msgstr "" + +#: ../../ch-sharedlibs.rst:602 +msgid "" +"To explain this format, we'll use the ``zlib1g`` package as an example, " +"which (at the time of writing) installs the shared library " +"``/usr/lib/libz.so.1.2.3.4``. Mandatory lines will be described first, " +"followed by optional lines." +msgstr "" + +#: ../../ch-sharedlibs.rst:607 +msgid "" +"``library-soname`` must contain exactly the value of the ELF ``SONAME`` " +"attribute of the shared library. In our example, this is ``libz.so.1``. " +"[#]_" +msgstr "" + +#: ../../ch-sharedlibs.rst:611 +msgid "" +"``main-dependency-template`` has the same syntax as a dependency field in" +" a binary package control file, except that the string ``#MINVER#`` is " +"replaced by a version restriction like ``(>= version)`` or by nothing if " +"an unversioned dependency is deemed sufficient. The version restriction " +"will be based on which symbols from the shared library are referenced and" +" the version at which they were introduced (see below). In nearly all " +"cases, ``main-dependency-template`` will be ``package #MINVER#``, where " +"package is the name of the binary package containing the shared library. " +"This adds a simple, possibly-versioned dependency on the shared library " +"package. In some rare cases, such as when multiple packages provide the " +"same shared library ABI, the dependency template may need to be more " +"complex." +msgstr "" + +#: ../../ch-sharedlibs.rst:624 +msgid "" +"In our example, the first line of the ``zlib1g`` ``symbols`` file would " +"be::" +msgstr "" + +#: ../../ch-sharedlibs.rst:629 +msgid "" +"Each public symbol exported by the shared library must have a " +"corresponding symbol line, indented by one space. symbol is the exported " +"symbol (which, for C++, means the mangled symbol) followed by ``@`` and " +"the symbol version, or the string ``Base`` if there is no symbol version." +" ``minimal-version`` is the most recent version of the shared library " +"that changed the behavior of that symbol, whether by adding it, changing " +"its function signature (the parameters, their types, or the return type)," +" or changing its behavior in a way that is visible to a caller. ``id-of-" +"dependency-template`` is an optional field that references an " +"``alternative-dependency-template``; see below for a full description." +msgstr "" + +#: ../../ch-sharedlibs.rst:641 +msgid "" +"For example, ``libz.so.1`` contains the symbols ``compress`` and " +"``compressBound``. ``compress`` has no symbol version and last changed " +"its behavior in upstream version ``1:1.1.4``. ``compressBound`` has the " +"symbol version ``ZLIB_1.2.0``, was introduced in upstream version " +"``1:1.2.0``, and has not changed its behavior. Its ``symbols`` file " +"therefore contains the lines::" +msgstr "" + +#: ../../ch-sharedlibs.rst:651 +msgid "" +"Packages using only ``compress`` would then get a dependency on ``zlib1g " +"(>= 1:1.1.4)``, but packages using ``compressBound`` would get a " +"dependency on ``zlib1g (>= 1:1.2.0)``." +msgstr "" + +#: ../../ch-sharedlibs.rst:655 +msgid "" +"One or more ``alternative-dependency-template`` lines may be provided. " +"These are used in cases where some symbols in the shared library should " +"use one dependency template while others should use a different template." +" The alternative dependency templates are used only if a symbol line " +"contains the ``id-of-dependency-template`` field. The first alternative " +"dependency template is numbered 1, the second 2, and so forth. [#]_" +msgstr "" + +#: ../../ch-sharedlibs.rst:663 +msgid "" +"Finally, the entry for the library may contain one or more metadata " +"fields. Currently, the only supported field-name is ``Build-Depends-" +"Package``, whose value lists the `library development package <#s" +"-sharedlibs-dev>`_ on which packages using this shared library declare a " +"build dependency. If this field is present, ``dpkg-shlibdeps`` uses it to" +" ensure that the resulting binary package dependency on the shared " +"library is at least as strict as the source package dependency on the " +"shared library development package. [#]_ For our example, the ``zlib1g``" +" ``symbols`` file would contain::" +msgstr "" + +#: ../../ch-sharedlibs.rst:675 +msgid "Also see ``deb-symbols(5)``." +msgstr "" + +#: ../../ch-sharedlibs.rst:677 +msgid "This can be determined by using the command" +msgstr "" + +#: ../../ch-sharedlibs.rst:683 +msgid "" +"An example of where this may be needed is with a library that implements " +"the libGL interface. All GL implementations provide the same set of base " +"interfaces, and then may provide some additional interfaces only used by " +"programs that require that specific GL implementation. So, for example, " +"libgl1-mesa-glx may use the following ``symbols`` file::" +msgstr "" + +#: ../../ch-sharedlibs.rst:696 +msgid "" +"Binaries or shared libraries using only ``publicGlSymbol`` would depend " +"only on ``libgl1`` (which may be provided by multiple packages), but ones" +" using ``implementationSpecificSymbol`` would get a dependency on " +"``libgl1-mesa-glx (>= 6.5.2-7)``." +msgstr "" + +#: ../../ch-sharedlibs.rst:701 +msgid "" +"This field should normally not be necessary, since if the behavior of any" +" symbol has changed, the corresponding symbol minimal-version should have" +" been increased. But including it makes the ``symbols`` system more " +"robust by tightening the dependency in cases where the package using the " +"shared library specifically requires at least a particular version of the" +" shared library development package for some reason." +msgstr "" + +#: ../../ch-sharedlibs.rst:712 +msgid "Providing a ``symbols`` file" +msgstr "" + +#: ../../ch-sharedlibs.rst:714 +msgid "" +"If your package provides a shared library, you should arrange to include " +"a ``symbols`` control file following the format described above in that " +"package. You must include either a ``symbols`` control file or a " +"``shlibs`` control file." +msgstr "" + +#: ../../ch-sharedlibs.rst:719 +msgid "" +"Normally, this is done by creating a ``symbols`` in the source package " +"named ``debian/package.symbols`` or ``debian/symbols``, possibly with " +"``.arch`` appended if the symbols information varies by architecture. " +"This file may use the extended syntax documented in dpkg-gensymbols(1). " +"Then, call ``dpkg-gensymbols`` as part of the package build process. It " +"will create ``symbols`` files in the package staging area based on the " +"binaries and libraries in the package staging area and the ``symbols`` " +"files in the source package. [#]_" +msgstr "" + +#: ../../ch-sharedlibs.rst:728 +msgid "" +"Packages that provide ``symbols`` files must keep them up-to-date to " +"ensure correct dependencies in packages that use the shared libraries. " +"This means updating the ``symbols`` file whenever a new public symbol is " +"added, changing the minimal-version field whenever a symbol changes " +"behavior or signature in a backward-compatible way (see :ref:`s" +"-sharedlibs-updates`), and changing the library-soname and main-" +"dependency-template, and probably all of the minimal-version fields, when" +" the library changes ``SONAME``. Removing a public symbol from the " +"``symbols`` file because it's no longer provided by the library normally " +"requires changing the ``SONAME`` of the library. See :ref:`s-sharedlibs-" +"runtime` for more information on ``SONAME``\\ s." +msgstr "" + +#: ../../ch-sharedlibs.rst:740 +msgid "" +"If you are using ``debhelper``, ``dh_makeshlibs`` will take care of " +"calling either ``dpkg-gensymbols`` or generating a ``shlibs`` file as " +"appropriate." +msgstr "" + +#: ../../ch-sharedlibs.rst:747 +msgid "The ``shlibs`` system" +msgstr "" + +#: ../../ch-sharedlibs.rst:749 +msgid "" +"The ``shlibs`` system is a simpler alternative to the ``symbols`` system " +"for declaring dependencies for shared libraries. It may be more " +"appropriate for C++ libraries and other cases where tracking individual " +"symbols is too difficult. It predated the ``symbols`` system and is " +"therefore frequently seen in older packages. It is also required for " +"udebs, which do not support ``symbols``." +msgstr "" + +#: ../../ch-sharedlibs.rst:756 +msgid "" +"In the following sections, we will first describe where the various " +"``shlibs`` files are to be found, then how to use ``dpkg-shlibdeps``, and" +" finally the ``shlibs`` file format and how to create them." +msgstr "" + +#: ../../ch-sharedlibs.rst:763 +msgid "The ``shlibs`` files present on the system" +msgstr "" + +#: ../../ch-sharedlibs.rst:765 +msgid "" +"There are several places where ``shlibs`` files are found. The following " +"list gives them in the order in which they are read by ``dpkg-" +"shlibdeps``. (The first one which gives the required information is " +"used.)" +msgstr "" + +#: ../../ch-sharedlibs.rst:776 +msgid "``debian/shlibs.local``" +msgstr "" + +#: ../../ch-sharedlibs.rst:771 +msgid "" +"This lists overrides for this package. This file should normally not be " +"used, but may be needed temporarily in unusual situations to work around " +"bugs in other packages, or in unusual cases where the normally declared " +"dependency information in the installed ``shlibs`` file for a library " +"cannot be used. This file overrides information obtained from any other " +"source." +msgstr "" + +#: ../../ch-sharedlibs.rst:780 +msgid "``/etc/dpkg/shlibs.override``" +msgstr "" + +#: ../../ch-sharedlibs.rst:779 +msgid "" +"This lists global overrides. This list is normally empty. It is " +"maintained by the local system administrator." +msgstr "" + +#: ../../ch-sharedlibs.rst:786 +msgid "``DEBIAN/shlibs`` files in the \"build directory\"" +msgstr "" + +#: ../../ch-sharedlibs.rst:783 +msgid "" +"These files are generated as part of the package build process and staged" +" for inclusion as control files in the binary packages being built. They " +"provide details of any shared libraries included in the same package." +msgstr "" + +#: ../../ch-sharedlibs.rst:791 +msgid "``shlibs`` control files for packages installed on the system" +msgstr "" + +#: ../../ch-sharedlibs.rst:789 +msgid "" +"The ``shlibs`` control files for all the packages currently installed on " +"the system. These files can be read using ``dpkg-query --control-show " +"package shlibs``." +msgstr "" + +#: ../../ch-sharedlibs.rst:797 +msgid "``/etc/dpkg/shlibs.default``" +msgstr "" + +#: ../../ch-sharedlibs.rst:794 +msgid "" +"This file lists any shared libraries whose packages have failed to " +"provide correct ``shlibs`` files. It was used when the ``shlibs`` setup " +"was first introduced, but it is now normally empty. It is maintained by " +"the ``dpkg`` maintainer." +msgstr "" + +#: ../../ch-sharedlibs.rst:799 +msgid "" +"If a ``symbols`` file for a shared library package is available, ``dpkg-" +"shlibdeps`` will always use it in preference to a ``shlibs``, with the " +"exception of ``debian/shlibs.local``. The latter overrides any other " +"``shlibs`` or ``symbols`` files." +msgstr "" + +#: ../../ch-sharedlibs.rst:807 +msgid "The ``shlibs`` File Format" +msgstr "" + +#: ../../ch-sharedlibs.rst:809 +msgid "" +"Each ``shlibs`` file has the same format. Lines beginning with ``#`` are " +"considered to be comments and are ignored. Each line is of the form::" +msgstr "" + +#: ../../ch-sharedlibs.rst:814 +msgid "" +"We will explain this by reference to the example of the ``zlib1g`` " +"package, which (at the time of writing) installs the shared library " +"``/usr/lib/libz.so.1.2.3.4``." +msgstr "" + +#: ../../ch-sharedlibs.rst:818 +msgid "" +"``type`` is an optional element that indicates the type of package for " +"which the line is valid. The only type currently in use is ``udeb``. The " +"colon and space after the type are required." +msgstr "" + +#: ../../ch-sharedlibs.rst:822 +msgid "" +"``library-name`` is the name of the shared library, in this case " +"``libz``. (This must match the name part of the soname, see below.)" +msgstr "" + +#: ../../ch-sharedlibs.rst:825 +msgid "" +"``soname-version`` is the version part of the ELF ``SONAME`` attribute of" +" the library, determined the same way that the soversion component of the" +" recommended shared library package name is determined. See :ref:`s" +"-sharedlibs-runtime` for the details." +msgstr "" + +#: ../../ch-sharedlibs.rst:830 +msgid "" +"``dependencies`` has the same syntax as a dependency field in a binary " +"package control file. It should give details of which packages are " +"required to satisfy a binary built against the version of the library " +"contained in the package. See :ref:`s-depsyntax` for details on the " +"syntax, and :ref:`s-sharedlibs-updates` for details on how to maintain " +"the dependency version constraint." +msgstr "" + +#: ../../ch-sharedlibs.rst:837 +msgid "" +"In our example, if the last change to the ``zlib1g`` package that could " +"change behavior for a client of that library was in version " +"``1:1.2.3.3.dfsg-1``, then the ``shlibs`` entry for this library could " +"say::" +msgstr "" + +#: ../../ch-sharedlibs.rst:844 +msgid "" +"This version restriction must be new enough that any binary built against" +" the current version of the library will work with any version of the " +"shared library that satisfies that dependency." +msgstr "" + +#: ../../ch-sharedlibs.rst:848 +msgid "" +"As zlib1g also provides a udeb containing the shared library, there would" +" also be a second line::" +msgstr "" + +#: ../../ch-sharedlibs.rst:856 +msgid "Providing a ``shlibs`` file" +msgstr "" + +#: ../../ch-sharedlibs.rst:858 +msgid "" +"To provide a ``shlibs`` file for a shared library binary package, create " +"a ``shlibs`` file following the format described above and place it in " +"the ``DEBIAN`` directory for that package during the build. It will then " +"be included as a control file for that package. [#]_" +msgstr "" + +#: ../../ch-sharedlibs.rst:863 +msgid "" +"Since ``dpkg-shlibdeps`` reads the ``DEBIAN/shlibs`` files in all of the " +"binary packages being built from this source package, all of the " +"``DEBIAN/shlibs`` files should be installed before ``dpkg-shlibdeps`` is " +"called on any of the binary packages." +msgstr "" + +#: ../../ch-sharedlibs.rst:868 +msgid "" +"This is what ``dh_makeshlibs`` in the debhelper suite does. If your " +"package also has a udeb that provides a shared library, ``dh_makeshlibs``" +" can automatically generate the ``udeb:`` lines if you specify the name " +"of the udeb with the ``--add-udeb`` option." +msgstr "" + diff --git a/locales/ja/LC_MESSAGES/ch-source.po b/locales/ja/LC_MESSAGES/ch-source.po new file mode 100644 index 0000000..4cc3fa3 --- /dev/null +++ b/locales/ja/LC_MESSAGES/ch-source.po @@ -0,0 +1,1267 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1996, 1997, 1998 Ian Jackson, Christian Schwarz, 1998-2017, +# The Debian Policy Mailing List +# This file is distributed under the same license as the Debian Policy +# Manual package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2018. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Debian Policy Manual 4.1.6.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-08-02 11:56+0800\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language-Team: LANGUAGE <LL@li.org>\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.4.0\n" + +#: ../../ch-source.rst:2 +msgid "Source packages" +msgstr "" + +#: ../../ch-source.rst:7 +msgid "Standards conformance" +msgstr "" + +#: ../../ch-source.rst:9 +msgid "" +"Source packages should specify the most recent version number of this " +"policy document with which your package complied when it was last " +"updated." +msgstr "" + +#: ../../ch-source.rst:13 +msgid "" +"The version is specified in the ``Standards-Version`` control field. The " +"format of the ``Standards-Version`` field is described in :ref:`s-f" +"-Standards-Version`." +msgstr "" + +#: ../../ch-source.rst:17 +msgid "" +"For a package to have an old Standards-Version value is not *itself* a " +"bug, however. It just means that no-one has yet reviewed the package " +"with changes to the standards in mind." +msgstr "" + +#: ../../ch-source.rst:21 +msgid "" +"When updating existing packaging, the Standards-Version must not be " +"updated except after reviewing the changes between the old and the new " +"versions of the standards and updating your package if necessary (the " +":doc:`upgrading-checklist` can help with this task)." +msgstr "" + +#: ../../ch-source.rst:26 +msgid "" +"A very old Standards-Version can mean that infelicities in the package " +"are likely. It is recommended that each package be reviewed at least " +"once per Debian release, so a Standards-Version older than the previous " +"Debian release is indicative of work (if only review work) that needs " +"doing." +msgstr "" + +#: ../../ch-source.rst:35 +msgid "Package relationships" +msgstr "" + +#: ../../ch-source.rst:37 +msgid "" +"Source packages should specify which binary packages they require to be " +"installed or not to be installed in order to build correctly. For " +"example, if building a package requires a certain compiler, then the " +"compiler should be specified as a build-time dependency." +msgstr "" + +#: ../../ch-source.rst:42 +msgid "" +"It is not necessary to explicitly specify build-time relationships on a " +"minimal set of packages that are always needed to compile, link and put " +"in a Debian package a standard \"Hello World!\" program written in C or " +"C++. The required packages are called *build-essential*, and an " +"informational list can be found in ``/usr/share/doc/build-" +"essential/list`` (which is contained in the ``build-essential`` package)." +" [#]_" +msgstr "" + +#: ../../ch-source.rst:50 +msgid "" +"When specifying the set of build-time dependencies, one should list only " +"those packages explicitly required by the build. It is not necessary to " +"list packages which are required merely because some other package in the" +" list of build-time dependencies depends on them. [#]_" +msgstr "" + +#: ../../ch-source.rst:55 +msgid "" +"If build-time dependencies are specified, it must be possible to build " +"the package and produce working binaries on a system with only essential " +"and build-essential packages installed and also those required to satisfy" +" the build-time relationships (including any implied relationships). In " +"particular, this means that version clauses should be used rigorously in " +"build-time relationships so that one cannot produce bad or inconsistently" +" configured packages when the relationships are properly satisfied." +msgstr "" + +#: ../../ch-source.rst:64 +msgid "" +":doc:`Declaring relationships between packages <ch-relationships>` " +"explains the technical details." +msgstr "" + +#: ../../ch-source.rst:70 +msgid "Changes to the upstream sources" +msgstr "" + +#: ../../ch-source.rst:72 +msgid "" +"If changes to the source code are made that are not specific to the needs" +" of the Debian system, they should be sent to the upstream authors in " +"whatever form they prefer so as to be included in the upstream version of" +" the package." +msgstr "" + +#: ../../ch-source.rst:77 +msgid "" +"If you need to configure the package differently for Debian or for Linux," +" and the upstream source doesn't provide a way to do so, you should add " +"such configuration facilities (for example, a new ``autoconf`` test or " +"``#define``) and send the patch to the upstream authors, with the default" +" set to the way they originally had it. You can then easily override the " +"default in your ``debian/rules`` or wherever is appropriate." +msgstr "" + +#: ../../ch-source.rst:85 +msgid "" +"You should make sure that the ``configure`` utility detects the correct " +"architecture specification string (refer to :ref:`s-arch-spec` for " +"details)." +msgstr "" + +#: ../../ch-source.rst:89 +msgid "" +"If your package includes the scripts ``config.sub`` and ``config.guess``," +" you should arrange for the versions provided by the package autotools-" +"dev be used instead (see autotools-dev documentation for details how to " +"achieve that). This ensures that these files can be updated distribution-" +"wide at build time when introducing new architectures." +msgstr "" + +#: ../../ch-source.rst:96 +msgid "" +"If you need to edit a ``Makefile`` where GNU-style ``configure`` scripts " +"are used, you should edit the ``.in`` files rather than editing the " +"``Makefile`` directly. This allows the user to reconfigure the package if" +" necessary. You should *not* configure the package and edit the generated" +" ``Makefile``! This makes it impossible for someone else to later " +"reconfigure the package without losing the changes you made." +msgstr "" + +#: ../../ch-source.rst:106 +msgid "Debian changelog: ``debian/changelog``" +msgstr "" + +#: ../../ch-source.rst:108 +msgid "" +"Every source package must include the Debian changelog file, " +"``debian/changelog``. Changes in the Debian version of the package " +"should be briefly explained in this file. [#]_ This includes " +"modifications made in the Debian package compared to the upstream one as " +"well as other changes and updates to the package. [#]_" +msgstr "" + +#: ../../ch-source.rst:114 +msgid "" +"The format of the ``debian/changelog`` allows the package building tools " +"to discover which version of the package is being built and find out " +"other release-specific information." +msgstr "" + +#: ../../ch-source.rst:118 +msgid "That format is a series of entries like this:" +msgstr "" + +#: ../../ch-source.rst:131 +msgid "" +"``package`` and ``version`` are the source package name and version " +"number." +msgstr "" + +#: ../../ch-source.rst:134 +msgid "" +"``distribution(s)`` lists the distributions where this version should be " +"installed when it is uploaded - it is copied to the ``Distribution`` " +"field in the ``.changes`` file. See :ref:`s-f-Distribution`." +msgstr "" + +#: ../../ch-source.rst:139 +msgid "" +"``urgency`` is the value for the ``Urgency`` field in the ``.changes`` " +"file for the upload (see :ref:`s-f-Urgency`). It is not possible to " +"specify an urgency containing commas; commas are used to separate " +"``keyword=value`` settings in the ``dpkg`` changelog format (though there" +" is currently only one useful keyword, ``urgency``)." +msgstr "" + +#: ../../ch-source.rst:145 +msgid "" +"The change details may in fact be any series of lines starting with at " +"least two spaces, but conventionally each change starts with an asterisk " +"and a separating space and continuation lines are indented so as to bring" +" them in line with the start of the text above. Blank lines may be used " +"here to separate groups of changes, if desired." +msgstr "" + +#: ../../ch-source.rst:151 +msgid "" +"If this upload resolves bugs recorded in the Bug Tracking System (BTS), " +"they may be automatically closed on the inclusion of this package into " +"the Debian archive by including the string: ``closes: Bug#nnnnn`` in the" +" change details. [#]_ This information is conveyed via the ``Closes`` " +"field in the ``.changes`` file (see :ref:`s-f-Closes`)." +msgstr "" + +#: ../../ch-source.rst:158 +msgid "" +"The maintainer name and email address used in the changelog should be the" +" details of the person who prepared this release of the package. They are" +" *not* necessarily those of the uploader or usual package maintainer. " +"[#]_ The information here will be copied to the ``Changed-By`` field in " +"the ``.changes`` file (see :ref:`s-f-Changed-By`), and then later used to" +" send an acknowledgement when the upload has been installed." +msgstr "" + +#: ../../ch-source.rst:166 +msgid "" +"The date has the following format [#]_ (compatible and with the same " +"semantics of RFC 2822 and RFC 5322):" +msgstr "" + +#: ../../ch-source.rst:173 +msgid "where:" +msgstr "" + +#: ../../ch-source.rst:175 +msgid "``day-of week`` is one of: Mon, Tue, Wed, Thu, Fri, Sat, Sun" +msgstr "" + +#: ../../ch-source.rst:177 +msgid "``dd`` is a one- or two-digit day of the month (01-31)" +msgstr "" + +#: ../../ch-source.rst:179 +msgid "" +"``month`` is one of: Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, " +"Nov, Dec" +msgstr "" + +#: ../../ch-source.rst:182 +msgid "``yyyy`` is the four-digit year (e.g. 2010)" +msgstr "" + +#: ../../ch-source.rst:184 +msgid "``hh`` is the two-digit hour (00-23)" +msgstr "" + +#: ../../ch-source.rst:186 +msgid "``mm`` is the two-digit minutes (00-59)" +msgstr "" + +#: ../../ch-source.rst:188 +msgid "``ss`` is the two-digit seconds (00-60)" +msgstr "" + +#: ../../ch-source.rst:196 +msgid "``+zzzz`` or ``-zzzz`` is the time zone offset from Coordinated" +msgstr "" + +#: ../../ch-source.rst:191 +msgid "" +"Universal Time (UTC). \"+\" indicates that the time is ahead of (i.e., " +"east of) UTC and \"-\" indicates that the time is behind (i.e., west of) " +"UTC. The first two digits indicate the hour difference from UTC and the " +"last two digits indicate the number of additional minutes difference from" +" UTC. The last two digits must be in the range 00-59." +msgstr "" + +#: ../../ch-source.rst:198 +msgid "" +"The first \"title\" line with the package name must start at the left " +"hand margin. The \"trailer\" line with the maintainer and date details " +"must be preceded by exactly one space. The maintainer details and the " +"date must be separated by exactly two spaces." +msgstr "" + +#: ../../ch-source.rst:203 +msgid "The entire changelog must be encoded in UTF-8." +msgstr "" + +#: ../../ch-source.rst:205 +msgid "" +"For more information on placement of the changelog files within binary " +"packages, please see :ref:`s-changelogs`." +msgstr "" + +#: ../../ch-source.rst:211 +msgid "Copyright: ``debian/copyright``" +msgstr "" + +#: ../../ch-source.rst:213 +msgid "" +"Every package must be accompanied by a verbatim copy of its copyright " +"information and distribution license in the file " +"``/usr/share/doc/package/copyright`` (see :ref:`s-copyrightfile` for " +"further details). Also see :ref:`s-pkgcopyright` for further " +"considerations related to copyrights for packages." +msgstr "" + +#: ../../ch-source.rst:223 +msgid "Error trapping in makefiles" +msgstr "" + +#: ../../ch-source.rst:225 +msgid "" +"When ``make`` invokes a command in a makefile (including your package's " +"upstream makefiles and ``debian/rules``), it does so using ``sh``. This " +"means that ``sh``'s usual bad error handling properties apply: if you " +"include a miniature script as one of the commands in your makefile you'll" +" find that if you don't do anything about it then errors are not detected" +" and ``make`` will blithely continue after problems." +msgstr "" + +#: ../../ch-source.rst:232 +msgid "" +"Every time you put more than one shell command (this includes using a " +"loop) in a makefile command you must make sure that errors are trapped. " +"For simple compound commands, such as changing directory and then running" +" a program, using ``&&`` rather than semicolon as a command separator is " +"sufficient. For more complex commands including most loops and " +"conditionals you should include a separate ``set -e`` command at the " +"start of every makefile command that's actually one of these miniature " +"shell scripts." +msgstr "" + +#: ../../ch-source.rst:243 +msgid "Time Stamps" +msgstr "" + +#: ../../ch-source.rst:245 +msgid "" +"Maintainers should preserve the modification times of the upstream source" +" files in a package, as far as is reasonably possible. [#]_" +msgstr "" + +#: ../../ch-source.rst:251 +msgid "Restrictions on objects in source packages" +msgstr "" + +#: ../../ch-source.rst:253 +msgid "" +"The source package may not contain any hard links, [#]_ device special " +"files, sockets or setuid or setgid files.. [#]_" +msgstr "" + +#: ../../ch-source.rst:259 +msgid "Main building script: ``debian/rules``" +msgstr "" + +#: ../../ch-source.rst:261 +msgid "" +"This file must be an executable makefile, and contains the package-" +"specific recipes for compiling the package and building binary package(s)" +" from the source." +msgstr "" + +#: ../../ch-source.rst:265 +msgid "" +"It must start with the line ``#!/usr/bin/make -f``, so that it can be " +"invoked by saying its name rather than invoking ``make`` explicitly. That" +" is, invoking either of ``make -f debian/rules args...`` or " +"``./debian/rules args...`` must result in identical behavior." +msgstr "" + +#: ../../ch-source.rst:269 +msgid "" +"The following targets are required and must be implemented by " +"``debian/rules``: ``clean``, ``binary``, ``binary-arch``, ``binary-" +"indep``, ``build``, ``build-arch`` and ``build-indep``. These are the " +"targets called by ``dpkg-buildpackage``." +msgstr "" + +#: ../../ch-source.rst:274 +msgid "" +"Since an interactive ``debian/rules`` script makes it impossible to auto-" +"compile that package and also makes it hard for other people to reproduce" +" the same binary package, all required targets must be non-interactive. " +"It also follows that any target that these targets depend on must also be" +" non-interactive." +msgstr "" + +#: ../../ch-source.rst:280 +msgid "" +"The package build should be as verbose as reasonably possible, except " +"where the ``terse`` tag is included in ``DEB_BUILD_OPTIONS`` (see :ref:`s" +"-debianrules-options`:). This means that ``debian/rules`` should pass to" +" the commands it invokes options that cause them to produce maximally " +"verbose output. For example, the build target should pass ``--disable-" +"silent-rules`` to any configure scripts." +msgstr "" + +#: ../../ch-source.rst:287 +msgid "" +"For packages in the main archive, no required targets may attempt network" +" access, except, via the loopback interface, to services on the build " +"host that have been started by the build." +msgstr "" + +#: ../../ch-source.rst:291 +msgid "The targets are as follows:" +msgstr "" + +#: ../../ch-source.rst:323 +msgid "``build`` (required)" +msgstr "" + +#: ../../ch-source.rst:294 +msgid "" +"The ``build`` target should perform all the configuration and compilation" +" of the package. If a package has an interactive pre-build configuration " +"routine, the Debian source package must either be built after this has " +"taken place (so that the binary package can be built without rerunning " +"the configuration) or the configuration routine modified to become non-" +"interactive. (The latter is preferable if there are architecture-specific" +" features detected by the configuration routine.)" +msgstr "" + +#: ../../ch-source.rst:303 +msgid "" +"For some packages, notably ones where the same source tree is compiled in" +" different ways to produce two binary packages, the ``build`` target does" +" not make much sense. For these packages it is good enough to provide two" +" (or more) targets (``build-a`` and ``build-b`` or whatever) for each of " +"the ways of building the package, and a ``build`` target that does " +"nothing. The ``binary`` target will have to build the package in each of " +"the possible ways and make the binary package out of each." +msgstr "" + +#: ../../ch-source.rst:312 +msgid "" +"The ``build`` target must not do anything that might require root " +"privilege." +msgstr "" + +#: ../../ch-source.rst:315 +msgid "" +"The ``build`` target may need to run the ``clean`` target first - see " +"below." +msgstr "" + +#: ../../ch-source.rst:318 +msgid "" +"When a package has a configuration and build routine which takes a long " +"time, or when the makefiles are poorly designed, or when ``build`` needs " +"to run ``clean`` first, it is a good idea to ``touch build`` when the " +"build process is complete. This will ensure that if ``debian/rules " +"build`` is run again it will not rebuild the whole program. [#]_" +msgstr "" + +#: ../../ch-source.rst:338 +msgid "``build-arch`` (required), ``build-indep`` (required)" +msgstr "" + +#: ../../ch-source.rst:326 +msgid "" +"The ``build-arch`` target must perform all the configuration and " +"compilation required for producing all architecture-dependent binary " +"packages (those packages for which the body of the ``Architecture`` field" +" in ``debian/control`` is not ``all``). Similarly, the ``build-indep`` " +"target must perform all the configuration and compilation required for " +"producing all architecture-independent binary packages (those packages " +"for which the body of the ``Architecture`` field in ``debian/control`` is" +" ``all``). The ``build`` target should either depend on those targets or " +"take the same actions as invoking those targets would perform. [#]_" +msgstr "" + +#: ../../ch-source.rst:337 +msgid "" +"The ``build-arch`` and ``build-indep`` targets must not do anything that " +"might require root privilege." +msgstr "" + +#: ../../ch-source.rst:365 +msgid "" +"``binary`` (required), ``binary-arch`` (required), ``binary-indep`` " +"(required)" +msgstr "" + +#: ../../ch-source.rst:341 +msgid "" +"The ``binary`` target must be all that is necessary for the user to build" +" the binary package(s) produced from this source package. It is split " +"into two parts: ``binary-arch`` builds the binary packages which are " +"specific to a particular architecture, and ``binary-indep`` builds those " +"which are not." +msgstr "" + +#: ../../ch-source.rst:347 +msgid "" +"``binary`` may be (and commonly is) a target with no commands which " +"simply depends on ``binary-arch`` and ``binary-indep``." +msgstr "" + +#: ../../ch-source.rst:350 +msgid "" +"Both ``binary-*`` targets should depend on the ``build`` target, or on " +"the appropriate ``build-arch`` or ``build-indep`` target, so that the " +"package is built if it has not been already. It should then create the " +"relevant binary package(s), using ``dpkg-gencontrol`` to make their " +"control files and ``dpkg-deb`` to build them and place them in the parent" +" of the top level directory." +msgstr "" + +#: ../../ch-source.rst:357 +msgid "" +"Both the ``binary-arch`` and ``binary-indep`` targets *must* exist. If " +"one of them has nothing to do (which will always be the case if the " +"source generates only a single binary package, whether architecture-" +"dependent or not), it must still exist and must always succeed." +msgstr "" + +#: ../../ch-source.rst:363 +msgid "" +"The ``binary`` targets may need to be invoked as root depending on the " +"value of the :ref:`Rules-Requires-Root <s-f-Rules-Requires-Root>` field." +" [#]_" +msgstr "" + +#: ../../ch-source.rst:388 +msgid "``clean`` (required)" +msgstr "" + +#: ../../ch-source.rst:368 +msgid "" +"This must undo any effects that the ``build`` and ``binary`` targets may " +"have had, except that it should leave alone any output files created in " +"the parent directory by a run of a ``binary`` target." +msgstr "" + +#: ../../ch-source.rst:373 +msgid "" +"If a ``build`` file is touched at the end of the ``build`` target, as " +"suggested above, it should be removed as the first action that ``clean`` " +"performs, so that running ``build`` again after an interrupted ``clean`` " +"doesn't think that everything is already done." +msgstr "" + +#: ../../ch-source.rst:378 +msgid "" +"The ``clean`` target may need to be invoked as root if ``binary`` has " +"been invoked since the last ``clean``, or if ``build`` has been invoked " +"as root (since ``build`` may create directories, for example)." +msgstr "" + +#: ../../ch-source.rst:383 +msgid "" +"The ``clean`` target cannot be used to remove files in the source tree " +"that are not compatible with the DFSG. This is because the files would " +"remain in the upstream tarball, and thus in the source package, so the " +"source package would continue to violate DFSG. Instead, the upstream " +"source should be repacked to remove those files." +msgstr "" + +#: ../../ch-source.rst:396 +msgid "``patch`` (optional)" +msgstr "" + +#: ../../ch-source.rst:391 +msgid "" +"This target performs whatever additional actions are required to make the" +" source ready for editing (unpacking additional upstream archives, " +"applying patches, etc.). It is recommended to be implemented for any " +"package where ``dpkg-source -x`` does not result in source ready for " +"additional modification. See :ref:`s-readmesource`." +msgstr "" + +#: ../../ch-source.rst:398 +msgid "" +"The ``build``, ``binary`` and ``clean`` targets must be invoked with the " +"current directory being the package's top-level directory." +msgstr "" + +#: ../../ch-source.rst:401 +msgid "" +"Additional targets may exist in ``debian/rules``, either as published or " +"undocumented interfaces or for the package's internal use." +msgstr "" + +#: ../../ch-source.rst:404 +msgid "" +"The architectures we build on and build for are determined by ``make`` " +"variables using the utility ``dpkg-architecture``. You can determine the " +"Debian architecture and the GNU style architecture specification string " +"for the build architecture as well as for the host architecture. The " +"build architecture is the architecture on which ``debian/rules`` is run " +"and the package build is performed. The host architecture is the " +"architecture on which the resulting package will be installed and run. " +"The target architecture is the architecture of the packages that the " +"compiler currently being built will generate. These are normally the " +"same, but may be different in the case of cross-compilation (building " +"packages for one architecture on machines of a different architecture), " +"building a cross-compiler (a compiler package that will generate objects " +"for one architecture, built on a machine of a different architecture) or " +"a Canadian cross-compiler (a compiler that will generate objects for one " +"architecture, built on a machine of a different architecture, that will " +"run on yet a different architecture)." +msgstr "" + +#: ../../ch-source.rst:421 +msgid "Here is a list of supported ``make`` variables:" +msgstr "" + +#: ../../ch-source.rst:423 +msgid "``DEB_*_ARCH`` (the Debian architecture)" +msgstr "" + +#: ../../ch-source.rst:425 +msgid "``DEB_*_ARCH_CPU`` (the Debian CPU name)" +msgstr "" + +#: ../../ch-source.rst:427 +msgid "``DEB_*_ARCH_BITS`` (the Debian CPU pointer size in bits)" +msgstr "" + +#: ../../ch-source.rst:429 +msgid "``DEB_*_ARCH_ENDIAN`` (the Debian CPU endianness)" +msgstr "" + +#: ../../ch-source.rst:431 +msgid "``DEB_*_ARCH_OS`` (the Debian System name)" +msgstr "" + +#: ../../ch-source.rst:433 +msgid "``DEB_*_GNU_TYPE`` (the GNU style architecture specification string)" +msgstr "" + +#: ../../ch-source.rst:435 +msgid "``DEB_*_GNU_CPU`` (the CPU part of ``DEB_*_GNU_TYPE``)" +msgstr "" + +#: ../../ch-source.rst:437 +msgid "``DEB_*_GNU_SYSTEM`` (the System part of ``DEB_*_GNU_TYPE``)" +msgstr "" + +#: ../../ch-source.rst:439 +msgid "" +"where ``*`` is either ``BUILD`` for specification of the build " +"architecture, ``HOST`` for specification of the host architecture or " +"``TARGET`` for specification of the target architecture." +msgstr "" + +#: ../../ch-source.rst:443 +msgid "" +"Backward compatibility can be provided in the rules file by setting the " +"needed variables to suitable default values; please refer to the " +"documentation of ``dpkg-architecture`` for details." +msgstr "" + +#: ../../ch-source.rst:447 +msgid "" +"It is important to understand that the ``DEB_*_ARCH`` string only " +"determines which Debian architecture we are building on or for. It should" +" not be used to get the CPU or system information; the ``DEB_*_ARCH_CPU``" +" and ``DEB_*_ARCH_OS`` variables should be used for that. GNU style " +"variables should generally only be used with upstream build systems." +msgstr "" + +#: ../../ch-source.rst:454 +msgid "" +"The builder may set ``DEB_RULES_REQUIRES_ROOT`` environment variable when" +" calling any of the mandatory targets as defined in :ref:`Rules-Requires-" +"Root <s-f-Rules-Requires-Root>`. If the variable is not set, the package" +" must behave as if it was set to ``binary-targets``." +msgstr "" + +#: ../../ch-source.rst:463 +msgid "``debian/rules`` and ``DEB_BUILD_OPTIONS``" +msgstr "" + +#: ../../ch-source.rst:465 +msgid "" +"Supporting the standardized environment variable ``DEB_BUILD_OPTIONS`` is" +" recommended. This variable can contain several flags to change how a " +"package is compiled and built. Each flag must be in the form flag or " +"flag=options. If multiple flags are given, they must be separated by " +"whitespace. [#]_ flag must start with a lowercase letter (``a-z``) and " +"consist only of lowercase letters, numbers (``0-9``), and the characters " +"``-`` and ``_`` (hyphen and underscore). options must not contain " +"whitespace. The same tag should not be given multiple times with " +"conflicting values. Package maintainers may assume that " +"``DEB_BUILD_OPTIONS`` will not contain conflicting tags." +msgstr "" + +#: ../../ch-source.rst:476 +msgid "The meaning of the following tags has been standardized:" +msgstr "" + +#: ../../ch-source.rst:480 +msgid "``nocheck``" +msgstr "" + +#: ../../ch-source.rst:479 +msgid "" +"This tag says to not run any build-time test suite provided by the " +"package." +msgstr "" + +#: ../../ch-source.rst:491 +msgid "``nodoc``" +msgstr "" + +#: ../../ch-source.rst:483 +msgid "" +"This tag says to skip any build steps that only generate package " +"documentation. Files required by other sections of Debian Policy, such as" +" copyright and changelog files, must still be generated and put in the " +"package, but other generated documentation such as help2man-generated " +"pages, Doxygen-generated API documentation, or info pages generated from " +"Texinfo sources should be skipped if possible. This option does not " +"change the set of binary packages generated by the source package, but " +"documentation-only binary packages may be nearly empty when built with " +"this option." +msgstr "" + +#: ../../ch-source.rst:498 +msgid "``noopt``" +msgstr "" + +#: ../../ch-source.rst:494 +msgid "" +"The presence of this tag means that the package should be compiled with a" +" minimum of optimization. For C programs, it is best to add ``-O0`` to " +"``CFLAGS`` (although this is usually the default). Some programs might " +"fail to build or run at this level of optimization; it may be necessary " +"to use ``-O1``, for example." +msgstr "" + +#: ../../ch-source.rst:503 +msgid "``nostrip``" +msgstr "" + +#: ../../ch-source.rst:501 +msgid "" +"This tag means that the debugging symbols should not be stripped from the" +" binary during installation, so that debugging information may be " +"included in the package." +msgstr "" + +#: ../../ch-source.rst:514 +msgid "``parallel=n``" +msgstr "" + +#: ../../ch-source.rst:506 +msgid "" +"This tag means that the package should be built using up to ``n`` " +"parallel processes if the package build system supports this. [#]_ If " +"the package build system does not support parallel builds, this string " +"must be ignored. If the package build system only supports a lower level " +"of concurrency than n, the package should be built using as many parallel" +" processes as the package build system supports. It is up to the package " +"maintainer to decide whether the package build times are long enough and " +"the package build system is robust enough to make supporting parallel " +"builds worthwhile." +msgstr "" + +#: ../../ch-source.rst:520 +msgid "``terse``" +msgstr "" + +#: ../../ch-source.rst:517 +msgid "" +"This tag means that the package build will be less verbose than default." +" For example, ``debian/rules`` might pass options to the package's " +"configure script that cause the compiler to produce less output." +msgstr "" + +#: ../../ch-source.rst:522 +msgid "Unknown flags must be ignored by ``debian/rules``." +msgstr "" + +#: ../../ch-source.rst:524 +msgid "" +"The following makefile snippet is an example of how one may implement the" +" build options; you will probably have to massage this example in order " +"to make it work for your package." +msgstr "" + +#: ../../ch-source.rst:560 +msgid "``debian/rules`` and ``Rules-Requires-Root``" +msgstr "" + +#: ../../ch-source.rst:562 +msgid "" +"Depending on the value of the :ref:`Rules-Requires-Root <s-f-Rules-" +"Requires-Root>` field, the package builder (e.g. dpkg-buildpackage) may " +"run the ``debian/rules`` target as an unprivileged user and provide a " +"`gain root command`. This command allows the ``debian/rules`` target to " +"run particular subcommands under (fake)root." +msgstr "" + +#: ../../ch-source.rst:569 +msgid "" +"The `gain root command` is passed to the build script via the " +"``DEB_GAIN_ROOT_CMD`` environment variable. The contents of this " +"variable is a space separated list, the first entry of which is the " +"command, and the proceeding entries of which are arguments to the " +"command. The `gain root command` must be available via PATH. The `gain " +"root command` must not rely on shell features because it will not " +"necessarily be invoked via a shell." +msgstr "" + +#: ../../ch-source.rst:577 +msgid "" +"The `gain root command` must not run interactively, including prompting " +"for any user input. It must be possible to prepend the `gain root " +"command` to an existing command and its arguments, without needing to " +"alter or quote the existing command and its arguments. Furthermore, the " +"`gain root command` must preserve all environment variables without the " +"caller having to explicitly request any preservation." +msgstr "" + +#: ../../ch-source.rst:585 +msgid "" +"The following are examples of valid gain root commands (in syntax of sh)," +" assuming the tools used are available and properly configured::" +msgstr "" + +#: ../../ch-source.rst:593 +msgid "Examples of valid use of the `gain root command`::" +msgstr "" + +#: ../../ch-source.rst:606 +msgid "Variable substitutions: ``debian/substvars``" +msgstr "" + +#: ../../ch-source.rst:608 +msgid "" +"When ``dpkg-gencontrol`` generates :ref:`binary package control files " +"<s-binarycontrolfiles>` (``DEBIAN/control``), it performs variable " +"substitutions on its output just before writing it. Variable " +"substitutions have the form ``${variable}``. The optional file " +"``debian/substvars`` contains variable substitutions to be used; " +"variables can also be set directly from ``debian/rules`` using the ``-V``" +" option to the source packaging commands, and certain predefined " +"variables are also available." +msgstr "" + +#: ../../ch-source.rst:617 +msgid "" +"The ``debian/substvars`` file is usually generated and modified " +"dynamically by ``debian/rules`` targets, in which case it must be removed" +" by the ``clean`` target." +msgstr "" + +#: ../../ch-source.rst:621 +msgid "" +"See deb-substvars(5) for full details about source variable " +"substitutions, including the format of ``debian/substvars``." +msgstr "" + +#: ../../ch-source.rst:627 +msgid "Optional upstream source location: ``debian/watch``" +msgstr "" + +#: ../../ch-source.rst:629 +msgid "" +"This is an optional, recommended configuration file for the ``uscan`` " +"utility which defines how to automatically scan ftp or http sites for " +"newly available updates of the package. This is also used by some Debian " +"QA tools to help with quality control and maintenance of the distribution" +" as a whole." +msgstr "" + +#: ../../ch-source.rst:635 +msgid "" +"If the upstream maintainer of the software provides OpenPGP signatures " +"for new releases, including the information required for ``uscan`` to " +"verify signatures for new upstream releases is also recommended. To do " +"this, use the ``pgpsigurlmangle`` option in ``debian/watch`` to specify " +"the location of the upstream signature, and include the key or keys used " +"to sign upstream releases in the Debian source package as " +"``debian/upstream/signing-key.asc``." +msgstr "" + +#: ../../ch-source.rst:643 +msgid "" +"For more information about ``uscan`` and these options, including how to " +"generate the file containing upstream signing keys, see uscan(1)." +msgstr "" + +#: ../../ch-source.rst:649 +msgid "Generated files list: ``debian/files``" +msgstr "" + +#: ../../ch-source.rst:651 +msgid "" +"This file is not a permanent part of the source tree; it is used while " +"building packages to record which files are being generated. ``dpkg-" +"genchanges`` uses it when it generates a ``.changes`` file." +msgstr "" + +#: ../../ch-source.rst:655 +msgid "" +"It should not exist in a shipped source package, and so it (and any " +"backup files or temporary files such as ``files.new``) [#]_ should be " +"removed by the ``clean`` target. It may also be wise to ensure a fresh " +"start by emptying or removing it at the start of the ``binary`` target." +msgstr "" + +#: ../../ch-source.rst:660 +msgid "" +"When ``dpkg-gencontrol`` is run for a binary package, it adds an entry to" +" ``debian/files`` for the ``.deb`` file that will be created when ``dpkg-" +"deb --build`` is run for that binary package. So for most packages all " +"that needs to be done with this file is to delete it in the ``clean`` " +"target." +msgstr "" + +#: ../../ch-source.rst:666 +msgid "" +"If a package upload includes files besides the source package and any " +"binary packages whose control files were made with ``dpkg-gencontrol`` " +"then they should be placed in the parent of the package's top-level " +"directory and ``dpkg-distaddfile`` should be called to add the file to " +"the list in ``debian/files``." +msgstr "" + +#: ../../ch-source.rst:675 +msgid "Convenience copies of code" +msgstr "" + +#: ../../ch-source.rst:677 +msgid "" +"Some software packages include in their distribution convenience copies " +"of code from other software packages, generally so that users compiling " +"from source don't have to download multiple packages. Debian packages " +"should not make use of these convenience copies unless the included " +"package is explicitly intended to be used in this way. [#]_ If the " +"included code is already in the Debian archive in the form of a library, " +"the Debian packaging should ensure that binary packages reference the " +"libraries already in Debian and the convenience copy is not used. If the " +"included code is not already in Debian, it should be packaged separately " +"as a prerequisite if possible. [#]_" +msgstr "" + +#: ../../ch-source.rst:691 +msgid "Source package handling: ``debian/README.source``" +msgstr "" + +#: ../../ch-source.rst:693 +msgid "" +"If running ``dpkg-source -x`` on a source package doesn't produce the " +"source of the package, ready for editing, and allow one to make changes " +"and run ``dpkg-buildpackage`` to produce a modified package without " +"taking any additional steps, creating a ``debian/README.source`` " +"documentation file is recommended. This file should explain how to do all" +" of the following:" +msgstr "" + +#: ../../ch-source.rst:700 +msgid "" +"Generate the fully patched source, in a form ready for editing, that " +"would be built to create Debian packages. Doing this with a ``patch`` " +"target in ``debian/rules`` is recommended; see `Main building script: " +"debian/rules <#s-debianrules>`__." +msgstr "" + +#: ../../ch-source.rst:705 +msgid "" +"Modify the source and save those modifications so that they will be " +"applied when building the package." +msgstr "" + +#: ../../ch-source.rst:708 +msgid "" +"Remove source modifications that are currently being applied when " +"building the package." +msgstr "" + +#: ../../ch-source.rst:711 +msgid "" +"Optionally, document what steps are necessary to upgrade the Debian " +"source package to a new upstream version, if applicable." +msgstr "" + +#: ../../ch-source.rst:714 +msgid "" +"This explanation should include specific commands and mention any " +"additional required Debian packages. It should not assume familiarity " +"with any specific Debian packaging system or patch management tools." +msgstr "" + +#: ../../ch-source.rst:718 +msgid "" +"This explanation may refer to a documentation file installed by one of " +"the package's build dependencies provided that the referenced " +"documentation clearly explains these tasks and is not a general reference" +" manual." +msgstr "" + +#: ../../ch-source.rst:723 +msgid "" +"``debian/README.source`` may also include any other information that " +"would be helpful to someone modifying the source package. Even if the " +"package doesn't fit the above description, maintainers are encouraged to " +"document in a ``debian/README.source`` file any source package with a " +"particularly complex or unintuitive source layout or build system (for " +"example, a package that builds the same source multiple times to generate" +" different binary packages)." +msgstr "" + +#: ../../ch-source.rst:732 +msgid "Reproducibility" +msgstr "" + +#: ../../ch-source.rst:734 +msgid "" +"Packages should build reproducibly, which for the purposes of this " +"document [#]_ means that given" +msgstr "" + +#: ../../ch-source.rst:737 +msgid "a version of a source package unpacked at a given path;" +msgstr "" + +#: ../../ch-source.rst:738 +msgid "a set of versions of installed build dependencies;" +msgstr "" + +#: ../../ch-source.rst:739 +msgid "a set of environment variable values;" +msgstr "" + +#: ../../ch-source.rst:740 +msgid "a build architecture; and" +msgstr "" + +#: ../../ch-source.rst:741 +msgid "a host architecture," +msgstr "" + +#: ../../ch-source.rst:743 +msgid "" +"repeatedly building the source package for the build architecture on any " +"machine of the host architecture with those versions of the build " +"dependencies installed and exactly those environment variable values set " +"will produce bit-for-bit identical binary packages." +msgstr "" + +#: ../../ch-source.rst:748 +msgid "" +"It is recommended that packages produce bit-for-bit identical binaries " +"even if most environment variables and build paths are varied. It is " +"intended for this stricter standard to replace the above when it is " +"easier for packages to meet it." +msgstr "" + +#: ../../ch-source.rst:754 +msgid "Missing sources: ``debian/missing-sources``" +msgstr "" + +#: ../../ch-source.rst:756 +msgid "" +"Sometimes upstream does not include the source code for some files in the" +" upstream tarball. In order to satisfy the DFSG for packages in ``main``" +" or ``contrib``, you should either:" +msgstr "" + +#: ../../ch-source.rst:760 +msgid "repack the upstream tarball to include those sources; or" +msgstr "" + +#: ../../ch-source.rst:761 +msgid "include a copy of the sources in the ``debian/missing-sources`` directory." +msgstr "" + +#: ../../ch-source.rst:764 +msgid "" +"There is an optional convention to organise the contents of ``debian" +"/missing-sources`` in the following way. For a sourceless file ``foo`` " +"in the subdirectory ``bar`` of the upstream tarball, where the source of " +"``foo`` has extension ``baz``, the source is to be located at ``debian" +"/missing-sources/bar/foo.baz``. For example, according to this " +"convention, the C source code of an executable ``checksum/util`` is to be" +" located at ``debian/missing-sources/checksum/util.c``." +msgstr "" + +#: ../../ch-source.rst:774 +msgid "Rationale:" +msgstr "" + +#: ../../ch-source.rst:776 +msgid "" +"This allows maintaining the list separately from the policy documents " +"(the list does not need the kind of control that the policy documents " +"do)." +msgstr "" + +#: ../../ch-source.rst:780 +msgid "" +"Having a separate package allows one to install the build-essential " +"packages on a machine, as well as allowing other packages such as tasks " +"to require installation of the build-essential packages using the depends" +" relation." +msgstr "" + +#: ../../ch-source.rst:785 +msgid "" +"The separate package allows bug reports against the list to be " +"categorized separately from the policy management process in the BTS." +msgstr "" + +#: ../../ch-source.rst:790 +msgid "" +"The reason for this is that dependencies change, and you should list all " +"those packages, and *only* those packages that *you* need directly. What " +"others need is their business. For example, if you only link against " +"``libimlib``, you will need to build-depend on libimlib2-dev but not " +"against any ``libjpeg*`` packages, even though ``libimlib2-dev`` " +"currently depends on them: installation of libimlib2-dev will " +"automatically ensure that all of its run-time dependencies are satisfied." +msgstr "" + +#: ../../ch-source.rst:800 +msgid "" +"Mistakes in changelogs are usually best rectified by making a new " +"changelog entry rather than \"rewriting history\" by editing old " +"changelog entries." +msgstr "" + +#: ../../ch-source.rst:805 +msgid "" +"Although there is nothing stopping an author who is also the Debian " +"maintainer from using this changelog for all their changes, it will have " +"to be renamed if the Debian and upstream maintainers become different " +"people. In such a case, however, it might be better to maintain the " +"package as a non-native package." +msgstr "" + +#: ../../ch-source.rst:812 +msgid "" +"To be precise, the string should match the following Perl regular " +"expression:" +msgstr "" + +#: ../../ch-source.rst:819 +msgid "" +"Then all of the bug numbers listed will be closed by the archive " +"maintenance software (``dak``) using the version of the changelog entry." +msgstr "" + +#: ../../ch-source.rst:824 +msgid "" +"In the case of a sponsored upload, the uploader signs the files, but the " +"changelog maintainer name and address are those of the person who " +"prepared this release. If the preparer of the release is not one of the " +"usual maintainers of the package (as listed in the :ref:```Maintainer`` " +"<#s-f-Maintainer` or ```Uploaders`` <s-f-Uploaders>` control fields of " +"the package), the first line of the changelog is conventionally used to " +"explain why a non-maintainer is uploading the package. The Debian " +"Developer's Reference (see :ref:`s-related`) documents the conventions " +"used." +msgstr "" + +#: ../../ch-source.rst:835 +msgid "This is the same as the format generated by ``date -R``." +msgstr "" + +#: ../../ch-source.rst:839 +msgid "" +"The rationale is that there is some information conveyed by knowing the " +"age of the file, for example, you could recognize that some documentation" +" is very old by looking at the modification time, so it would be nice if " +"the modification time of the upstream source would be preserved." +msgstr "" + +#: ../../ch-source.rst:846 +msgid "" +"This is not currently detected when building source packages, but only " +"when extracting them." +msgstr "" + +#: ../../ch-source.rst:849 +msgid "" +"Hard links may be permitted at some point in the future, but would " +"require a fair amount of work." +msgstr "" + +#: ../../ch-source.rst:853 +msgid "Setgid directories are allowed." +msgstr "" + +#: ../../ch-source.rst:856 +msgid "" +"Another common way to do this is for ``build`` to depend on ``build-" +"stamp`` and to do nothing else, and for the ``build-stamp`` target to do " +"the building and to ``touch build-stamp`` on completion. This is " +"especially useful if the build routine creates a file or directory called" +" ``build``; in such a case, ``build`` will need to be listed as a phony " +"target (i.e., as a dependency of the ``.PHONY`` target). See the " +"documentation of ``make`` for more information on phony targets." +msgstr "" + +#: ../../ch-source.rst:866 +msgid "" +"This split allows binary-only builds to not install the dependencies " +"required for the ``build-indep`` target and skip any resource-intensive " +"build tasks that are only required when building architecture-independent" +" binary packages." +msgstr "" + +#: ../../ch-source.rst:872 +msgid "" +"The ``fakeroot`` package often allows one to build a package correctly " +"even without being root." +msgstr "" + +#: ../../ch-source.rst:876 +msgid "" +"Some packages support any delimiter, but whitespace is the easiest to " +"parse inside a makefile and avoids ambiguity with flag values that " +"contain commas." +msgstr "" + +#: ../../ch-source.rst:881 +msgid "" +"Packages built with ``make`` can often implement this by passing the " +"``-j``\\ n option to ``make``." +msgstr "" + +#: ../../ch-source.rst:885 +msgid "" +"``files.new`` is used as a temporary file by ``dpkg-gencontrol`` and " +"``dpkg-distaddfile`` - they write a new version of ``files`` here before " +"renaming it, to avoid leaving a corrupted copy if an error occurs." +msgstr "" + +#: ../../ch-source.rst:891 +msgid "For example, parts of the GNU build system work like this." +msgstr "" + +#: ../../ch-source.rst:894 +msgid "" +"Having multiple copies of the same code in Debian is inefficient, often " +"creates either static linking or shared library conflicts, and, most " +"importantly, increases the difficulty of handling security " +"vulnerabilities in the duplicated code." +msgstr "" + +#: ../../ch-source.rst:900 +msgid "" +"This is Debian's precisification of the `reproducible-builds.org " +"definition <https://reproducible-builds.org/docs/definition/>`_." +msgstr "" + diff --git a/locales/ja/LC_MESSAGES/index.po b/locales/ja/LC_MESSAGES/index.po new file mode 100644 index 0000000..bd68692 --- /dev/null +++ b/locales/ja/LC_MESSAGES/index.po @@ -0,0 +1,42 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1996, 1997, 1998 Ian Jackson, Christian Schwarz, 1998-2017, +# The Debian Policy Mailing List +# This file is distributed under the same license as the Debian Policy +# Manual package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2018. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Debian Policy Manual 4.1.6.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-08-02 11:56+0800\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language-Team: LANGUAGE <LL@li.org>\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.4.0\n" + +#: ../../index.rst:3 +msgid "Debian Policy Manual" +msgstr "" + +#: ../../index.rst:5 +msgid "" +"This manual describes the policy requirements for the Debian " +"distribution. This includes the structure and contents of the Debian " +"archive and several design issues of the operating system, as well as " +"technical requirements that each package must satisfy to be included in " +"the distribution." +msgstr "" + +#: ../../index.rst:10 +msgid "This is Debian Policy version 4.1.6.0, released on 2018-07-11." +msgstr "" + +#: ../../index.rst:29 +msgid "Appendices" +msgstr "" + diff --git a/locales/ja/LC_MESSAGES/upgrading-checklist.po b/locales/ja/LC_MESSAGES/upgrading-checklist.po new file mode 100644 index 0000000..ecd5748 --- /dev/null +++ b/locales/ja/LC_MESSAGES/upgrading-checklist.po @@ -0,0 +1,3545 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1996, 1997, 1998 Ian Jackson, Christian Schwarz, 1998-2017, +# The Debian Policy Mailing List +# This file is distributed under the same license as the Debian Policy +# Manual package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2018. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Debian Policy Manual 4.1.6.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-08-02 11:56+0800\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language-Team: LANGUAGE <LL@li.org>\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.4.0\n" + +#: ../../upgrading-checklist.rst:2 +msgid "Upgrading checklist" +msgstr "" + +#: ../../upgrading-checklist.rst:5 +msgid "About the checklist" +msgstr "" + +#: ../../upgrading-checklist.rst:7 +msgid "" +"The checklist below has been created to simplify the upgrading process of" +" old packages. This list is not official or normative. It only provides " +"an indication of what has changed and whether you are likely to need to " +"make changes to your package in light of this. If you have doubts about a" +" certain topic, if you need more details, or if you think some other " +"package does not comply with policy, please refer to the Policy Manual " +"itself." +msgstr "" + +#: ../../upgrading-checklist.rst:15 +msgid "" +"All of the changes from version 3.0.0 onwards indicate which section of " +"the Policy Manual discusses the issue. The section numbering should still" +" be accurate for changes back to the 2.5.0 release. Before that point, " +"the sections listed here probably no longer correspond to sections in the" +" modern Policy Manual." +msgstr "" + +#: ../../upgrading-checklist.rst:21 +msgid "" +"Here is how the check list works: Check which policy version your package" +" was checked against last (indicated in the ``Standards-Version`` field " +"of the source package). Then move upwards until the top and check which " +"of the items on the list might concern your package. Note which sections " +"of policy discuss this, and then check out the Policy Manual for details." +" Once you've made all necessary changes to match the current rules, " +"update the value of ``Standards-Version`` to the current Policy Manual " +"version." +msgstr "" + +#: ../../upgrading-checklist.rst:30 +msgid "" +"If an item in the list is followed by the name of a Lintian tag in square" +" brackets, it indicates that the policy requirement is covered by that " +"Lintian tag. The lack of such an annotation does not mean that no " +"Lintian tag exists to cover the requirement. Our coverage of these " +"annotations is quite incomplete, and patches to this checklist are very " +"welcome." +msgstr "" + +#: ../../upgrading-checklist.rst:37 +msgid "" +"The sections in this checklist match the values for the ``Standards-" +"Version`` control field in omitting the minor patch version, except in " +"the two anomalous historical cases where normative requirements were " +"changed in a minor patch release." +msgstr "" + +#: ../../upgrading-checklist.rst:43 +msgid "Version 4.1.6" +msgstr "" + +#: ../../upgrading-checklist.rst:45 +msgid "Unreleased." +msgstr "" + +#: ../../upgrading-checklist.rst:51 ../../upgrading-checklist.rst:56 +#: ../../upgrading-checklist.rst:114 ../../upgrading-checklist.rst:300 +#: ../../upgrading-checklist.rst:431 ../../upgrading-checklist.rst:555 +#: ../../upgrading-checklist.rst:939 ../../upgrading-checklist.rst:1089 +msgid "4.9" +msgstr "" + +#: ../../upgrading-checklist.rst:48 +msgid "" +"The package build should be as verbose as reasonably possible. This means" +" that ``debian/rules`` should pass to the commands it invokes options " +"that cause them to produce maximally verbose output." +msgstr "" + +#: ../../upgrading-checklist.rst:54 +msgid "" +"Required targets may attempt network access, via the loopback interface, " +"to services on the build host that have been started by the build." +msgstr "" + +#: ../../upgrading-checklist.rst:60 ../../upgrading-checklist.rst:305 +#: ../../upgrading-checklist.rst:1044 ../../upgrading-checklist.rst:1100 +msgid "4.9.1" +msgstr "" + +#: ../../upgrading-checklist.rst:59 +msgid "" +"New ``terse`` tag that can appear in ``DEB_BUILD_OPTIONS`` to make a " +"package build less verbose." +msgstr "" + +#: ../../upgrading-checklist.rst:64 +msgid "5.2 & 5.4" +msgstr "" + +#: ../../upgrading-checklist.rst:63 +msgid "The Standards-Version field is now mandatory, not just recommended." +msgstr "" + +#: ../../upgrading-checklist.rst:67 +msgid "Version 4.1.5" +msgstr "" + +#: ../../upgrading-checklist.rst:69 +msgid "Released July, 2018." +msgstr "" + +#: ../../upgrading-checklist.rst:73 +msgid "4.9.2" +msgstr "" + +#: ../../upgrading-checklist.rst:72 +msgid "" +"Document how ``debian/rules`` and the ``Rules-Requires-Root`` field " +"interact." +msgstr "" + +#: ../../upgrading-checklist.rst:77 ../../upgrading-checklist.rst:313 +#: ../../upgrading-checklist.rst:1120 ../../upgrading-checklist.rst:1173 +msgid "5.6.12" +msgstr "" + +#: ../../upgrading-checklist.rst:76 +msgid "" +"You should not change a package's epoch, even in experimental, without " +"getting consensus on debian-devel first." +msgstr "" + +#: ../../upgrading-checklist.rst:81 +msgid "5.6.12.1" +msgstr "" + +#: ../../upgrading-checklist.rst:80 +msgid "" +"Epochs should not be used for the purpose of rolling back the version of " +"a package. Use the +really convention." +msgstr "" + +#: ../../upgrading-checklist.rst:84 +msgid "5.6.31" +msgstr "" + +#: ../../upgrading-checklist.rst:84 +msgid "Document the ``Rules-Requires-Root`` field." +msgstr "" + +#: ../../upgrading-checklist.rst:89 ../../upgrading-checklist.rst:140 +#: ../../upgrading-checklist.rst:223 ../../upgrading-checklist.rst:327 +#: ../../upgrading-checklist.rst:582 ../../upgrading-checklist.rst:619 +#: ../../upgrading-checklist.rst:719 ../../upgrading-checklist.rst:726 +#: ../../upgrading-checklist.rst:921 ../../upgrading-checklist.rst:929 +#: ../../upgrading-checklist.rst:1268 ../../upgrading-checklist.rst:1713 +msgid "9.1.1" +msgstr "" + +#: ../../upgrading-checklist.rst:87 +msgid "" +"Update Debian's version of the Filesystem Hierarchy Standard from 2.3 to " +"3.0, and update the list of exceptions. Only a tiny minority of " +"packages, if any, should be made buggy by this change." +msgstr "" + +#: ../../upgrading-checklist.rst:93 +msgid "9.3.2 & 10.4" +msgstr "" + +#: ../../upgrading-checklist.rst:92 +msgid "" +"Update version of POSIX standard for shell scripts from SUSv3 to " +"POSIX.1-2017 (also known as SUSv4 in some contexts)." +msgstr "" + +#: ../../upgrading-checklist.rst:96 +msgid "Version 4.1.4" +msgstr "" + +#: ../../upgrading-checklist.rst:98 +msgid "Released April, 2018." +msgstr "" + +#: ../../upgrading-checklist.rst:104 ../../upgrading-checklist.rst:110 +msgid "3.2.2" +msgstr "" + +#: ../../upgrading-checklist.rst:101 +msgid "" +"The part of the version number after the epoch must not be reused for a " +"version of the package with different contents, even after the version of" +" the package previously using that part of the version number is no " +"longer present in any archive suites." +msgstr "" + +#: ../../upgrading-checklist.rst:107 +msgid "" +"For non-native packages, the upstream version must not be reused for " +"different upstream source code, so that for each source package name and " +"upstream version number there exists exactly one original source archive " +"contents." +msgstr "" + +#: ../../upgrading-checklist.rst:113 +msgid "" +"The ``get-orig-source`` rules target has been removed. Packages should " +"transition to ``debian/watch`` and use uscan where possible." +msgstr "" + +#: ../../upgrading-checklist.rst:121 +msgid "9.1.2" +msgstr "" + +#: ../../upgrading-checklist.rst:117 +msgid "" +"If ``/etc/staff-group-for-usr-local`` does not exist, ``/usr/local`` and " +"all subdirectories created by packages should have permissions 0755 and " +"be owned by ``root:root``. If the file exists, the old permissions of " +"2775 and ownership of root:staff should remain." +msgstr "" + +#: ../../upgrading-checklist.rst:124 +msgid "Version 4.1.3" +msgstr "" + +#: ../../upgrading-checklist.rst:126 +msgid "Released December, 2017." +msgstr "" + +#: ../../upgrading-checklist.rst:131 ../../upgrading-checklist.rst:560 +msgid "5.6.26" +msgstr "" + +#: ../../upgrading-checklist.rst:129 +msgid "" +"URLs given in ``VCS-*`` headers should use a scheme that provides " +"confidentiality (``https``, for example) if the VCS repository supports " +"it. ``[vcs-field-uses-insecure-uri]``" +msgstr "" + +#: ../../upgrading-checklist.rst:137 ../../upgrading-checklist.rst:569 +msgid "7.8" +msgstr "" + +#: ../../upgrading-checklist.rst:134 +msgid "" +"``Built-Using`` should be used exactly when there are license or DFSG " +"requirements to retain full source code in the archive. Previously, the " +"description of the field implied it was needed in other cases too." +msgstr "" + +#: ../../upgrading-checklist.rst:140 +msgid "``libc`` may also install files in ``/lib64``." +msgstr "" + +#: ../../upgrading-checklist.rst:149 +msgid "9.3.3.1" +msgstr "" + +#: ../../upgrading-checklist.rst:143 +msgid "" +"If a package's daemon should not be autostarted unless the local " +"administrator has explicitly requested it, the package's ``postinst`` " +"should use the new ``defaults-disabled`` option of ``update-rc.d``." +msgstr "" + +#: ../../upgrading-checklist.rst:148 +msgid "" +"The old method of including ``DISABLED=yes`` in the package's " +"``/etc/default`` file should not be used." +msgstr "" + +#: ../../upgrading-checklist.rst:154 +msgid "11.4" +msgstr "" + +#: ../../upgrading-checklist.rst:152 +msgid "" +"Clarify that programs may invoke either ``/usr/bin/editor`` and " +"``/usr/bin/pager`` directly, or use ``editor`` and ``pager`` and rely on " +"PATH." +msgstr "" + +#: ../../upgrading-checklist.rst:159 ../../upgrading-checklist.rst:373 +#: ../../upgrading-checklist.rst:593 ../../upgrading-checklist.rst:648 +#: ../../upgrading-checklist.rst:820 ../../upgrading-checklist.rst:895 +#: ../../upgrading-checklist.rst:1019 ../../upgrading-checklist.rst:1156 +#: ../../upgrading-checklist.rst:1161 ../../upgrading-checklist.rst:1211 +msgid "12.5" +msgstr "" + +#: ../../upgrading-checklist.rst:157 +msgid "" +"The Creative Commons CC0 1.0 Universal license (CC0-1.0) is now included " +"in ``/usr/share/common-licenses`` and does not need to be copied verbatim" +" in the package ``copyright`` file." +msgstr "" + +#: ../../upgrading-checklist.rst:162 +msgid "Version 4.1.2" +msgstr "" + +#: ../../upgrading-checklist.rst:164 +msgid "Released November, 2017." +msgstr "" + +#: ../../upgrading-checklist.rst:170 +msgid "3.1.1" +msgstr "" + +#: ../../upgrading-checklist.rst:167 +msgid "" +"Binary packages that have potentially offensive content should have the " +"suffix ``-offensive``. This replaces an older convention to use " +"``-off``. As before, whether the contents of a package needs this " +"content warning is a matter of maintainer discretion." +msgstr "" + +#: ../../upgrading-checklist.rst:177 ../../upgrading-checklist.rst:786 +#: ../../upgrading-checklist.rst:792 ../../upgrading-checklist.rst:957 +#: ../../upgrading-checklist.rst:1244 ../../upgrading-checklist.rst:1357 +#: ../../upgrading-checklist.rst:1510 ../../upgrading-checklist.rst:1741 +#: ../../upgrading-checklist.rst:1765 +msgid "10.2" +msgstr "" + +#: ../../upgrading-checklist.rst:173 +msgid "" +"Private shared object files should be installed in subdirectories of " +"``/usr/lib`` or ``/usr/lib/triplet``. This change permits private shared" +" object files to take advantage of multiarch, and also removes the " +"implication that it is permissible to install private shared object files" +" directly into ``/usr/lib/triplet``." +msgstr "" + +#: ../../upgrading-checklist.rst:182 ../../upgrading-checklist.rst:798 +#: ../../upgrading-checklist.rst:1070 ../../upgrading-checklist.rst:1178 +#: ../../upgrading-checklist.rst:1281 +msgid "10.4" +msgstr "" + +#: ../../upgrading-checklist.rst:180 +msgid "" +"The shebang at the top of Perl command scripts must be " +"``#!/usr/bin/perl``. (Previously, this was a 'should' rather than a " +"'must'.)" +msgstr "" + +#: ../../upgrading-checklist.rst:185 +msgid "Version 4.1.1" +msgstr "" + +#: ../../upgrading-checklist.rst:187 +msgid "Released September, 2017." +msgstr "" + +#: ../../upgrading-checklist.rst:190 ../../upgrading-checklist.rst:465 +#: ../../upgrading-checklist.rst:1032 ../../upgrading-checklist.rst:1036 +msgid "4.4" +msgstr "" + +#: ../../upgrading-checklist.rst:190 +msgid "debian/changelog must exist in source packages." +msgstr "" + +#: ../../upgrading-checklist.rst:193 +msgid "9.2.3" +msgstr "" + +#: ../../upgrading-checklist.rst:193 +msgid "The canonical non-existent home directory is ``/nonexistent``." +msgstr "" + +#: ../../upgrading-checklist.rst:196 +msgid "Version 4.1.0" +msgstr "" + +#: ../../upgrading-checklist.rst:198 ../../upgrading-checklist.rst:241 +msgid "Released August, 2017." +msgstr "" + +#: ../../upgrading-checklist.rst:202 +msgid "2.2.1" +msgstr "" + +#: ../../upgrading-checklist.rst:201 +msgid "" +"Non-default alternative dependencies on non-free packages are permitted " +"for packages in main." +msgstr "" + +#: ../../upgrading-checklist.rst:209 +msgid "4.11" +msgstr "" + +#: ../../upgrading-checklist.rst:205 +msgid "" +"If upstream provides OpenPGP signatures, including the upstream signing " +"key as ``debian/upstream/signing-key.asc`` in the source package and " +"using the ``pgpsigurlmangle`` option in ``debian/watch`` configuration to" +" indicate how to find the upstream signature for new releases is " +"recommended." +msgstr "" + +#: ../../upgrading-checklist.rst:213 ../../upgrading-checklist.rst:217 +msgid "4.15" +msgstr "" + +#: ../../upgrading-checklist.rst:212 +msgid "" +"Packages should build reproducibly when certain factors are held " +"constant; see 4.15 for the list." +msgstr "" + +#: ../../upgrading-checklist.rst:216 +msgid "" +"Packages are recommended to build reproducibly even when build paths and " +"most environment variables are allowed to vary." +msgstr "" + +#: ../../upgrading-checklist.rst:220 +msgid "Only the dynamic linker may install files to ``/lib64/``." +msgstr "" + +#: ../../upgrading-checklist.rst:222 +msgid "" +"No package for a 64 bit architecture may install files to ``/usr/lib64/``" +" or any subdirectory." +msgstr "" + +#: ../../upgrading-checklist.rst:236 ../../upgrading-checklist.rst:1369 +#: ../../upgrading-checklist.rst:1518 ../../upgrading-checklist.rst:1647 +msgid "11.8.3" +msgstr "" + +#: ../../upgrading-checklist.rst:226 +msgid "" +"The required behaviour of ``x-terminal-emulator -e`` has been clarified, " +"and updated to replace a false claim about the behaviour of ``xterm``." +msgstr "" + +#: ../../upgrading-checklist.rst:230 +msgid "" +"Programs must support ``-e command`` where ``command`` may include " +"multiple arguments, which must be executed as if the arguments were " +"passed to ``execvp`` directly, bypassing the shell." +msgstr "" + +#: ../../upgrading-checklist.rst:234 +msgid "" +"If this execution fails and ``-e`` has a single argument, ``xterm``'s " +"fallback behaviour of passing ``command`` to the shell is permitted but " +"not required." +msgstr "" + +#: ../../upgrading-checklist.rst:239 +msgid "Version 4.0.1" +msgstr "" + +#: ../../upgrading-checklist.rst:254 ../../upgrading-checklist.rst:1469 +msgid "2.5" +msgstr "" + +#: ../../upgrading-checklist.rst:244 +msgid "" +"Priorities are now used only for controlling which packages are part of a" +" minimal or standard Debian installation and should be selected based on " +"functionality provided directly to users (so nearly all shared libraries " +"should have a priority of ``optional``). Packages may now depend on " +"packages with a lower priority." +msgstr "" + +#: ../../upgrading-checklist.rst:250 +msgid "" +"The ``extra`` priority has been deprecated and should be treated as " +"equivalent to ``optional``. All ``extra`` priorities should be changed to" +" ``optional``. Packages with a priority of ``optional`` may conflict with" +" each other (but packages that both have a priority of ``standard`` or " +"higher still may not conflict)." +msgstr "" + +#: ../../upgrading-checklist.rst:258 +msgid "5.6.30" +msgstr "" + +#: ../../upgrading-checklist.rst:257 +msgid "" +"New section documenting the ``Testsuite`` field in Debian source control " +"files." +msgstr "" + +#: ../../upgrading-checklist.rst:262 +msgid "8.1.1" +msgstr "" + +#: ../../upgrading-checklist.rst:261 +msgid "" +"Shared libraries must now invoke ``ldconfig`` by means of triggers, " +"instead of maintscripts." +msgstr "" + +#: ../../upgrading-checklist.rst:266 ../../upgrading-checklist.rst:272 +#: ../../upgrading-checklist.rst:1704 +msgid "9.3.3" +msgstr "" + +#: ../../upgrading-checklist.rst:265 +msgid "" +"Packages are recommended to use debhelper tools instead of invoking " +"``update-rc.d`` and ``invoke-rc.d`` directly." +msgstr "" + +#: ../../upgrading-checklist.rst:269 +msgid "" +"Policy's description of how the local system administrator may modify the" +" runlevels at which a daemon is started and stopped, and how init scripts" +" may depend on other init scripts, have been removed. These are now " +"handled by LSB headers." +msgstr "" + +#: ../../upgrading-checklist.rst:278 +msgid "9.4" +msgstr "" + +#: ../../upgrading-checklist.rst:275 +msgid "" +"Policy's specification of the console messages that should be emitted by " +"``init.d`` scripts has been removed. This is now defined by LSB, for " +"sysvinit, and is not expected to be followed by other init systems." +msgstr "" + +#: ../../upgrading-checklist.rst:282 ../../upgrading-checklist.rst:406 +msgid "9.6" +msgstr "" + +#: ../../upgrading-checklist.rst:281 +msgid "" +"Packages installing a Free Desktop entry must not also install a Debian " +"menu system entry." +msgstr "" + +#: ../../upgrading-checklist.rst:287 +msgid "9.9" +msgstr "" + +#: ../../upgrading-checklist.rst:285 +msgid "" +"The prohibition against depending on environment variables for reasonable" +" defaults is only for programs on the system PATH and only for custom " +"environment variable settings (not, say, a sane PATH)." +msgstr "" + +#: ../../upgrading-checklist.rst:290 +msgid "Version 4.0.0" +msgstr "" + +#: ../../upgrading-checklist.rst:292 +msgid "Released May, 2017." +msgstr "" + +#: ../../upgrading-checklist.rst:296 +msgid "4.3" +msgstr "" + +#: ../../upgrading-checklist.rst:295 +msgid "" +"``config.sub`` and ``config.guess`` should be updated at build time or " +"replaced with the versions from autotools-dev." +msgstr "" + +#: ../../upgrading-checklist.rst:299 +msgid "" +"New ``TARGET`` set of ``dpkg-architecture`` variables and new " +"``DEB_*_ARCH_BITS`` and ``DEB_*_ARCH_ENDIAN`` variables." +msgstr "" + +#: ../../upgrading-checklist.rst:303 +msgid "" +"New ``DEB_BUILD_OPTIONS`` tag, ``nodoc``, which says to suppress " +"documentation generation (but continue to build all binary packages, even" +" documentation packages, just let them be mostly empty)." +msgstr "" + +#: ../../upgrading-checklist.rst:310 ../../upgrading-checklist.rst:1051 +msgid "5.2" +msgstr "" + +#: ../../upgrading-checklist.rst:308 +msgid "" +"Automatically-generated debug packages do not need to have a " +"corresponding paragraph in ``debian/control``. (This is existing " +"practice; this Policy update is just clearer about it.)" +msgstr "" + +#: ../../upgrading-checklist.rst:313 +msgid "Colons are not permitted in upstream version numbers." +msgstr "" + +#: ../../upgrading-checklist.rst:317 +msgid "7.7" +msgstr "" + +#: ../../upgrading-checklist.rst:316 +msgid "" +"New ``Build-Depends-Arch`` and ``Build-Conflicts-Arch`` fields are now " +"supported." +msgstr "" + +#: ../../upgrading-checklist.rst:322 ../../upgrading-checklist.rst:770 +#: ../../upgrading-checklist.rst:882 +msgid "8.4" +msgstr "" + +#: ../../upgrading-checklist.rst:320 +msgid "" +"The recommended package name for shared library development files is now " +"libraryname-dev or librarynameapiversion-dev, not librarynamesoversion-" +"dev." +msgstr "" + +#: ../../upgrading-checklist.rst:325 +msgid "" +"The stable release of Debian supports ``/run``, so packages may now " +"assume that it exists and do not need any special dependency on a version" +" of initscripts." +msgstr "" + +#: ../../upgrading-checklist.rst:332 ../../upgrading-checklist.rst:335 +#: ../../upgrading-checklist.rst:1061 ../../upgrading-checklist.rst:1066 +#: ../../upgrading-checklist.rst:1391 ../../upgrading-checklist.rst:1601 +msgid "9.3.2" +msgstr "" + +#: ../../upgrading-checklist.rst:330 +msgid "" +"New optional ``try-restart`` standard init script argument, which (if " +"supported) should restart the service if it is already running and " +"otherwise just report success." +msgstr "" + +#: ../../upgrading-checklist.rst:335 +msgid "Support for the ``status`` init script argument is recommended." +msgstr "" + +#: ../../upgrading-checklist.rst:340 ../../upgrading-checklist.rst:1286 +msgid "9.3.3.2" +msgstr "" + +#: ../../upgrading-checklist.rst:338 +msgid "" +"Packages must not call ``/etc/init.d`` scripts directly even as a " +"fallback, and instead must always use ``invoke-rc.d`` (which is essential" +" and shouldn't require any conditional)." +msgstr "" + +#: ../../upgrading-checklist.rst:344 +msgid "9.11.1" +msgstr "" + +#: ../../upgrading-checklist.rst:343 +msgid "" +"Instructions for ``upstart`` integration removed since ``upstart`` is no " +"longer maintained in Debian." +msgstr "" + +#: ../../upgrading-checklist.rst:349 ../../upgrading-checklist.rst:460 +#: ../../upgrading-checklist.rst:1447 ../../upgrading-checklist.rst:1630 +msgid "10.1" +msgstr "" + +#: ../../upgrading-checklist.rst:347 +msgid "" +"Packages may not install files in both ``/path`` and ``/usr/path``, and " +"must manage any backward-compatibility symlinks so that they don't break " +"if ``/path`` and ``/usr/path`` are the same directory." +msgstr "" + +#: ../../upgrading-checklist.rst:359 ../../upgrading-checklist.rst:925 +msgid "10.6" +msgstr "" + +#: ../../upgrading-checklist.rst:352 +msgid "" +"Packages should assume device files in ``/dev`` are dynamically managed " +"and don't have to be created by the package. Packages other than those " +"whose purpose is to manage ``/dev`` must not create or remove files there" +" when a dynamic management facility is in use. Named pipes and device " +"files outside of ``/dev`` should normally be created on demand via init " +"scripts, systemd units, or similar mechanisms, but may be created and " +"removed in maintainer scripts if they must be created during package " +"installation." +msgstr "" + +#: ../../upgrading-checklist.rst:363 ../../upgrading-checklist.rst:806 +msgid "10.9" +msgstr "" + +#: ../../upgrading-checklist.rst:362 +msgid "" +"Checking with the base-passwd maintainer is no longer required (or " +"desirable) when creating a new dynamic user or group in a package." +msgstr "" + +#: ../../upgrading-checklist.rst:368 ../../upgrading-checklist.rst:436 +#: ../../upgrading-checklist.rst:1477 ../../upgrading-checklist.rst:1610 +msgid "12.3" +msgstr "" + +#: ../../upgrading-checklist.rst:366 +msgid "" +"Dependencies on \\*-doc packages should be at most Recommends (Suggests " +"if they only include documentation in supplemental formats)." +msgstr "" + +#: ../../upgrading-checklist.rst:371 +msgid "" +"The Mozilla Public License 1.1 and 2.0 (MPL-1.1 and MPL-2.0) are now " +"included in ``/usr/share/common-licenses`` and do not need to be copied " +"verbatim in the package ``copyright`` file." +msgstr "" + +#: ../../upgrading-checklist.rst:377 ../../upgrading-checklist.rst:652 +msgid "copyright-format" +msgstr "" + +#: ../../upgrading-checklist.rst:376 +msgid "" +"The ``https`` form of the copyright-format URL is now allowed and " +"preferred in the ``Format`` field." +msgstr "" + +#: ../../upgrading-checklist.rst:382 ../../upgrading-checklist.rst:480 +#: ../../upgrading-checklist.rst:485 ../../upgrading-checklist.rst:661 +#: ../../upgrading-checklist.rst:906 ../../upgrading-checklist.rst:911 +#: ../../upgrading-checklist.rst:982 +msgid "perl" +msgstr "" + +#: ../../upgrading-checklist.rst:380 +msgid "" +"The Perl search path now includes multiarch directories. The vendor " +"directory for architecture-specific modules is now versioned to support " +"multiarch." +msgstr "" + +#: ../../upgrading-checklist.rst:386 ../../upgrading-checklist.rst:391 +#: ../../upgrading-checklist.rst:397 ../../upgrading-checklist.rst:473 +#: ../../upgrading-checklist.rst:476 ../../upgrading-checklist.rst:543 +#: ../../upgrading-checklist.rst:665 ../../upgrading-checklist.rst:731 +msgid "virtual" +msgstr "" + +#: ../../upgrading-checklist.rst:385 +msgid "" +"New ``adventure`` virtual package for implementations of the classic " +"Colossal Cave Adventure game." +msgstr "" + +#: ../../upgrading-checklist.rst:389 +msgid "" +"New ``httpd-wsgi3`` virtual package for Python 3 WSGI-capable HTTP " +"servers. The existing ``httpd-wsgi`` virtual package is for Python 2 " +"WSGI-capable HTTP servers." +msgstr "" + +#: ../../upgrading-checklist.rst:394 +msgid "" +"New ``virtual-mysql-client``, ``virtual-mysql-client-core``, ``virtual-" +"mysql-server``, ``virtual-mysql-server-core``, and ``virtual-mysql-" +"testsuite`` virtual packages for MySQL-compatible software." +msgstr "" + +#: ../../upgrading-checklist.rst:400 +msgid "Version 3.9.8" +msgstr "" + +#: ../../upgrading-checklist.rst:402 +msgid "Released April, 2016." +msgstr "" + +#: ../../upgrading-checklist.rst:405 +msgid "" +"The menu system is deprecated in favor of the FreeDesktop menu standard. " +"New requirements set for FreeDesktop menu entries." +msgstr "" + +#: ../../upgrading-checklist.rst:412 ../../upgrading-checklist.rst:586 +msgid "9.7" +msgstr "" + +#: ../../upgrading-checklist.rst:409 +msgid "" +"New instructions for registering media type handlers with the FreeDesktop" +" system, which automatically synchronizes with mailcap and therefore " +"replaces mailcap registration for packages using desktop entries." +msgstr "" + +#: ../../upgrading-checklist.rst:415 +msgid "Version 3.9.7" +msgstr "" + +#: ../../upgrading-checklist.rst:417 +msgid "Released February, 2016." +msgstr "" + +#: ../../upgrading-checklist.rst:420 +msgid "10.5" +msgstr "" + +#: ../../upgrading-checklist.rst:420 +msgid "Symbolic links must not traverse above the root directory." +msgstr "" + +#: ../../upgrading-checklist.rst:424 ../../upgrading-checklist.rst:885 +msgid "9.2.2" +msgstr "" + +#: ../../upgrading-checklist.rst:423 +msgid "" +"32bit UIDs in the range 65536-4294967293 are reserved for dynamically " +"allocated user accounts." +msgstr "" + +#: ../../upgrading-checklist.rst:428 ../../upgrading-checklist.rst:495 +#: ../../upgrading-checklist.rst:693 ../../upgrading-checklist.rst:833 +#: ../../upgrading-checklist.rst:1047 +msgid "5.1" +msgstr "" + +#: ../../upgrading-checklist.rst:427 +msgid "" +"Empty field values in control files are only permitted in the " +"``debian/control`` file of a source package." +msgstr "" + +#: ../../upgrading-checklist.rst:431 +msgid "``debian/rules``: required targets must not attempt network access." +msgstr "" + +#: ../../upgrading-checklist.rst:434 +msgid "" +"recommend to ship additional documentation for package ``pkg`` in a " +"separate package ``pkg-doc`` and install it into ``/usr/share/doc/pkg``." +msgstr "" + +#: ../../upgrading-checklist.rst:439 +msgid "Version 3.9.6" +msgstr "" + +#: ../../upgrading-checklist.rst:441 +msgid "Released September, 2014." +msgstr "" + +#: ../../upgrading-checklist.rst:447 ../../upgrading-checklist.rst:451 +#: ../../upgrading-checklist.rst:456 ../../upgrading-checklist.rst:1007 +#: ../../upgrading-checklist.rst:1751 +msgid "9.1" +msgstr "" + +#: ../../upgrading-checklist.rst:444 +msgid "" +"The FHS is relaxed to allow a subdirectory of ``/usr/lib`` to hold a " +"mixture of architecture-independent and architecture-dependent files, " +"though directories entirely composed of architecture-independent files " +"should be located in ``/usr/share``." +msgstr "" + +#: ../../upgrading-checklist.rst:450 +msgid "" +"The FHS requirement for ``/usr/local/lib64`` to exist if ``/lib64`` or " +"``/usr/lib64`` exists is removed." +msgstr "" + +#: ../../upgrading-checklist.rst:454 +msgid "" +"An FHS exception has been granted for multiarch include files, permitting" +" header files to instead be installed to ``/usr/include/triplet``." +msgstr "" + +#: ../../upgrading-checklist.rst:459 +msgid "" +"Binaries must not be statically linked with the GNU C library, see policy" +" for exceptions." +msgstr "" + +#: ../../upgrading-checklist.rst:463 +msgid "" +"It is clarified that signature appearing in debian/changelog should be " +"the details of the person who prepared this release of the package." +msgstr "" + +#: ../../upgrading-checklist.rst:468 ../../upgrading-checklist.rst:816 +#: ../../upgrading-checklist.rst:1231 ../../upgrading-checklist.rst:1259 +#: ../../upgrading-checklist.rst:1263 ../../upgrading-checklist.rst:1308 +#: ../../upgrading-checklist.rst:1473 ../../upgrading-checklist.rst:1483 +msgid "11.5" +msgstr "" + +#: ../../upgrading-checklist.rst:468 +msgid "The default web document root is now ``/var/www/html``" +msgstr "" + +#: ../../upgrading-checklist.rst:471 +msgid "" +"``java1-runtime`` and ``java2-runtime`` are removed, ``javaN-runtime`` " +"and ``javaN-runtime-headless`` are added for all N between 5 and 9." +msgstr "" + +#: ../../upgrading-checklist.rst:476 +msgid "Added ``httpd-wsgi`` for WSGI capable HTTP servers." +msgstr "" + +#: ../../upgrading-checklist.rst:479 +msgid "" +"Perl packages should use the ``%Config`` hash to locate module paths " +"instead of hardcoding paths in ``@INC``." +msgstr "" + +#: ../../upgrading-checklist.rst:483 +msgid "" +"Perl binary modules and any modules installed into " +"``$Config{vendorarch}`` must depend on the relevant perlapi-\\* package." +msgstr "" + +#: ../../upgrading-checklist.rst:488 +msgid "Version 3.9.5" +msgstr "" + +#: ../../upgrading-checklist.rst:490 +msgid "Released October, 2013." +msgstr "" + +#: ../../upgrading-checklist.rst:493 +msgid "" +"Control data fields must not start with the hyphen character (``-``), to " +"avoid potential confusions when parsing clearsigned control data files " +"that were not properly unescaped." +msgstr "" + +#: ../../upgrading-checklist.rst:499 +msgid "5.4, 5.6.24" +msgstr "" + +#: ../../upgrading-checklist.rst:498 +msgid "" +"``Checksums-Sha1`` and ``Checksums-Sha256`` are now mandatory in ``.dsc``" +" files." +msgstr "" + +#: ../../upgrading-checklist.rst:503 +msgid "5.6.25, 5.8.1" +msgstr "" + +#: ../../upgrading-checklist.rst:502 +msgid "" +"The ``DM-Upload-Allowed`` field is obsolete. Permissions are now granted " +"via *dak-commands* files." +msgstr "" + +#: ../../upgrading-checklist.rst:507 +msgid "5.6.27" +msgstr "" + +#: ../../upgrading-checklist.rst:506 +msgid "" +"New section documenting the ``Package-List`` field in Debian source " +"control files." +msgstr "" + +#: ../../upgrading-checklist.rst:511 +msgid "5.6.28" +msgstr "" + +#: ../../upgrading-checklist.rst:510 +msgid "" +"New section documenting the ``Package-Type`` field in source package " +"control files." +msgstr "" + +#: ../../upgrading-checklist.rst:515 +msgid "5.6.29" +msgstr "" + +#: ../../upgrading-checklist.rst:514 +msgid "New section documenting the ``Dgit`` field in Debian source control files." +msgstr "" + +#: ../../upgrading-checklist.rst:518 +msgid "9.1.1.8" +msgstr "" + +#: ../../upgrading-checklist.rst:518 +msgid "The exception to the FHS for the ``/selinux`` was removed." +msgstr "" + +#: ../../upgrading-checklist.rst:523 ../../upgrading-checklist.rst:1561 +msgid "10.7.3" +msgstr "" + +#: ../../upgrading-checklist.rst:521 +msgid "" +"Packages should remove all obsolete configuration files without local " +"changes during upgrades. The ``dpkg-maintscript-helper`` tool, available " +"from the dpkg package since *Wheezy*, can help with this." +msgstr "" + +#: ../../upgrading-checklist.rst:528 +msgid "10.10" +msgstr "" + +#: ../../upgrading-checklist.rst:526 +msgid "" +"The name of the files and directories installed by binary packages must " +"be encoded in UTF-8 and should be restricted to ASCII when possible. In " +"the system PATH, they must be restricted to ASCII." +msgstr "" + +#: ../../upgrading-checklist.rst:532 +msgid "11.5.2" +msgstr "" + +#: ../../upgrading-checklist.rst:531 +msgid "Stop recommending to serve HTML documents from ``/usr/share/doc/package``." +msgstr "" + +#: ../../upgrading-checklist.rst:537 ../../upgrading-checklist.rst:978 +msgid "12.2" +msgstr "" + +#: ../../upgrading-checklist.rst:535 +msgid "" +"Packages distributing Info documents should use install-info's trigger, " +"and do not need anymore to depend on ``dpkg (>= 1.15.4) | install-info``." +msgstr "" + +#: ../../upgrading-checklist.rst:540 ../../upgrading-checklist.rst:900 +#: ../../upgrading-checklist.rst:1164 +msgid "debconf" +msgstr "" + +#: ../../upgrading-checklist.rst:540 +msgid "The ``escape`` capability is now documented." +msgstr "" + +#: ../../upgrading-checklist.rst:543 +msgid "``mp3-decoder`` and ``mp3-encoder`` are removed." +msgstr "" + +#: ../../upgrading-checklist.rst:546 +msgid "Version 3.9.4" +msgstr "" + +#: ../../upgrading-checklist.rst:548 +msgid "Released August, 2012." +msgstr "" + +#: ../../upgrading-checklist.rst:551 ../../upgrading-checklist.rst:602 +#: ../../upgrading-checklist.rst:994 +msgid "2.4" +msgstr "" + +#: ../../upgrading-checklist.rst:551 +msgid "New *tasks* archive section." +msgstr "" + +#: ../../upgrading-checklist.rst:554 +msgid "" +"``build-arch`` and ``build-indep`` are now mandatory targets in " +"``debian/rules``." +msgstr "" + +#: ../../upgrading-checklist.rst:558 +msgid "" +"New section documenting the ``Vcs-*`` fields, which are already in " +"widespread use. Note the mechanism for specifying the Git branch used for" +" packaging in the Vcs-Git field." +msgstr "" + +#: ../../upgrading-checklist.rst:563 ../../upgrading-checklist.rst:611 +#: ../../upgrading-checklist.rst:755 ../../upgrading-checklist.rst:1556 +#: ../../upgrading-checklist.rst:1679 +msgid "7.1" +msgstr "" + +#: ../../upgrading-checklist.rst:563 +msgid "The deprecated relations < and > now must not be used." +msgstr "" + +#: ../../upgrading-checklist.rst:566 +msgid "" +"New ``Built-Using`` field, which must be used to document the source " +"packages for any binaries that are incorporated into this package at " +"build time. This is used to ensure that the archive meets license " +"requirements for providing source for all binaries." +msgstr "" + +#: ../../upgrading-checklist.rst:577 ../../upgrading-checklist.rst:1202 +msgid "8.6" +msgstr "" + +#: ../../upgrading-checklist.rst:572 +msgid "" +"Policy for dependencies between shared libraries and other packages has " +"been largely rewritten to document the ``symbols`` system and more " +"clearly document handling of shared library ABI changes. ``symbols`` " +"files are now recommended over ``shlibs`` files in most situations. All " +"maintainers of shared library packages should review the entirety of this" +" section." +msgstr "" + +#: ../../upgrading-checklist.rst:580 +msgid "" +"Packages must not assume the ``/run`` directory exists or is usable " +"without a dependency on ``initscripts (>= 2.88dsf-13.3)`` until the " +"stable release of Debian supports ``/run``." +msgstr "" + +#: ../../upgrading-checklist.rst:585 +msgid "" +"Packages including MIME configuration can now rely on triggers and do not" +" need to call update-mime." +msgstr "" + +#: ../../upgrading-checklist.rst:590 +msgid "9.11" +msgstr "" + +#: ../../upgrading-checklist.rst:589 +msgid "" +"New section documenting general requirements for alternate init systems " +"and specific requirements for integrating with upstart." +msgstr "" + +#: ../../upgrading-checklist.rst:593 +msgid "All copyright files must be encoded in UTF-8." +msgstr "" + +#: ../../upgrading-checklist.rst:596 +msgid "Version 3.9.3" +msgstr "" + +#: ../../upgrading-checklist.rst:598 +msgid "Released February, 2012." +msgstr "" + +#: ../../upgrading-checklist.rst:601 +msgid "" +"New archive sections *education*, *introspection*, and *metapackages* " +"added." +msgstr "" + +#: ../../upgrading-checklist.rst:607 ../../upgrading-checklist.rst:944 +msgid "5.6.8" +msgstr "" + +#: ../../upgrading-checklist.rst:605 +msgid "" +"The ``Architecture`` field in ``*.dsc`` files may now contain the value " +"``any all`` for source packages building both architecture-independent " +"and architecture-dependent packages." +msgstr "" + +#: ../../upgrading-checklist.rst:610 +msgid "" +"If a dependency is restricted to particular architectures, the list of " +"architectures must be non-empty." +msgstr "" + +#: ../../upgrading-checklist.rst:614 +msgid "" +"``/run`` is allowed as an exception to the FHS and replaces ``/var/run``." +" ``/run/lock`` replaces ``/var/lock``. The FHS requirements for the older" +" directories apply to these directories as well. Backward compatibility " +"links will be maintained and packages need not switch to referencing " +"``/run`` directly yet. Files in ``/run`` should be stored in a temporary " +"file system." +msgstr "" + +#: ../../upgrading-checklist.rst:624 +msgid "9.1.4" +msgstr "" + +#: ../../upgrading-checklist.rst:622 +msgid "" +"New section spelling out the requirements for packages that use files in " +"``/run``, ``/var/run``, or ``/var/lock``. This generalizes information " +"previously only in 9.3.2." +msgstr "" + +#: ../../upgrading-checklist.rst:631 ../../upgrading-checklist.rst:1140 +msgid "9.5" +msgstr "" + +#: ../../upgrading-checklist.rst:627 +msgid "" +"Cron job file names must not contain ``.`` or ``+`` or they will be " +"ignored by cron. They should replace those characters with ``_``. If a " +"package provides multiple cron job files in the same directory, they " +"should each start with the package name (possibly modified as above), " +"``-``, and then some suitable suffix." +msgstr "" + +#: ../../upgrading-checklist.rst:634 +msgid "9.10" +msgstr "" + +#: ../../upgrading-checklist.rst:634 +msgid "Packages using doc-base do not need to call install-docs anymore." +msgstr "" + +#: ../../upgrading-checklist.rst:638 +msgid "10.7.4" +msgstr "" + +#: ../../upgrading-checklist.rst:637 +msgid "" +"Packages that declare the same ``conffile`` may see left-over " +"configuration files from each other even if they conflict." +msgstr "" + +#: ../../upgrading-checklist.rst:643 +msgid "11.8" +msgstr "" + +#: ../../upgrading-checklist.rst:641 +msgid "" +"The Policy rules around Motif libraries were just a special case of " +"normal rules for non-free dependencies and were largely obsolete, so they" +" have been removed." +msgstr "" + +#: ../../upgrading-checklist.rst:646 +msgid "" +"``debian/copyright`` is no longer required to list the Debian maintainers" +" involved in the creation of the package (although note that the " +"requirement to list copyright information is unchanged)." +msgstr "" + +#: ../../upgrading-checklist.rst:651 +msgid "" +"Version 1.0 of the \"Machine-readable ``debian/copyright`` file\" " +"specification is included." +msgstr "" + +#: ../../upgrading-checklist.rst:657 +msgid "mime" +msgstr "" + +#: ../../upgrading-checklist.rst:655 +msgid "" +"This separate document has been retired and and its (short) contents " +"merged into Policy section 9.7. There are no changes to the requirements." +msgstr "" + +#: ../../upgrading-checklist.rst:660 +msgid "" +"Packages may declare an interest in the perl-major-upgrade trigger to be " +"notified of major upgrades of perl." +msgstr "" + +#: ../../upgrading-checklist.rst:664 +msgid "" +"``ttf-japanese-{mincho, gothic}`` is renamed to ``fonts-japanese-{mincho," +" gothic}``." +msgstr "" + +#: ../../upgrading-checklist.rst:668 +msgid "Version 3.9.2" +msgstr "" + +#: ../../upgrading-checklist.rst:670 +msgid "Released April, 2011." +msgstr "" + +#: ../../upgrading-checklist.rst:674 +msgid "\\*" +msgstr "" + +#: ../../upgrading-checklist.rst:673 +msgid "" +"Multiple clarifications throughout Policy where \"installed\" was used " +"and the more precise terms \"unpacked\" or \"configured\" were intended." +msgstr "" + +#: ../../upgrading-checklist.rst:680 +msgid "3.3" +msgstr "" + +#: ../../upgrading-checklist.rst:677 +msgid "" +"The maintainer address must accept mail from Debian role accounts and the" +" BTS. At least one human must be listed with their personal email address" +" in ``Uploaders`` if the maintainer is a shared email address. The duties" +" of a maintainer are also clearer." +msgstr "" + +#: ../../upgrading-checklist.rst:686 +msgid "5" +msgstr "" + +#: ../../upgrading-checklist.rst:683 +msgid "" +"All control fields are now classified as simple, folded, or multiline, " +"which governs whether their values must be a single line or may be " +"continued across multiple lines and whether line breaks are significant." +msgstr "" + +#: ../../upgrading-checklist.rst:689 +msgid "" +"Parsers are allowed to accept paragraph separation lines containing " +"whitespace, but control files should use completely empty lines. Ordering" +" of paragraphs is significant. Field names must be composed of printable " +"ASCII characters except colon and must not begin with #." +msgstr "" + +#: ../../upgrading-checklist.rst:696 +msgid "5.6.25" +msgstr "" + +#: ../../upgrading-checklist.rst:696 +msgid "The ``DM-Upload-Allowed`` field is now documented." +msgstr "" + +#: ../../upgrading-checklist.rst:703 +msgid "6.5" +msgstr "" + +#: ../../upgrading-checklist.rst:699 +msgid "" +"The system state maintainer scripts can rely upon during each possible " +"invocation is now documented. In several less-common cases, this is " +"stricter than Policy had previously documented. Packages with complex " +"maintainer scripts should be reviewed in light of this new documentation." +msgstr "" + +#: ../../upgrading-checklist.rst:708 ../../upgrading-checklist.rst:715 +msgid "7.2" +msgstr "" + +#: ../../upgrading-checklist.rst:706 +msgid "" +"The impact on system state when maintainer scripts that are part of a " +"circular dependency are run is now documented. Circular dependencies are " +"now a should not." +msgstr "" + +#: ../../upgrading-checklist.rst:711 +msgid "" +"The system state when ``postinst`` and ``prerm`` scripts are run is now " +"documented, and the documentation of the special case of dependency state" +" for ``postrm`` scripts has been improved. ``postrm`` scripts are " +"required to gracefully skip actions if their dependencies are not " +"available." +msgstr "" + +#: ../../upgrading-checklist.rst:718 +msgid "" +"GNU/Hurd systems are allowed ``/hurd`` and ``/servers`` directories in " +"the root filesystem." +msgstr "" + +#: ../../upgrading-checklist.rst:722 +msgid "" +"Packages installing to architecture-specific subdirectories of " +"``/usr/lib`` must use the value returned by ``dpkg-architecture " +"-qDEB_HOST_MULTIARCH``, not by ``dpkg-architecture -qDEB_HOST_GNU_TYPE``;" +" this is a path change on i386 architectures and a no-op for other " +"architectures." +msgstr "" + +#: ../../upgrading-checklist.rst:729 +msgid "" +"``mailx`` is now a virtual package provided by packages that install " +"``/usr/bin/mailx`` and implement at least the POSIX-required interface." +msgstr "" + +#: ../../upgrading-checklist.rst:734 +msgid "Version 3.9.1" +msgstr "" + +#: ../../upgrading-checklist.rst:736 +msgid "Released July, 2010." +msgstr "" + +#: ../../upgrading-checklist.rst:741 ../../upgrading-checklist.rst:1731 +msgid "3.2.1" +msgstr "" + +#: ../../upgrading-checklist.rst:739 +msgid "" +"Date-based version components should be given as the four-digit year, " +"two-digit month, and then two-digit day, but may have embedded " +"punctuation." +msgstr "" + +#: ../../upgrading-checklist.rst:745 ../../upgrading-checklist.rst:1437 +msgid "3.9" +msgstr "" + +#: ../../upgrading-checklist.rst:744 +msgid "" +"Maintainer scripts must pass ``--package`` to ``dpkg-divert`` when " +"creating or removing diversions and must not use ``--local``." +msgstr "" + +#: ../../upgrading-checklist.rst:750 +msgid "4.10" +msgstr "" + +#: ../../upgrading-checklist.rst:748 +msgid "" +"Only ``dpkg-gencontrol`` supports variable substitution. ``dpkg-" +"genchanges`` (for ``*.changes``) and ``dpkg-source`` (for ``*.dsc``) do " +"not." +msgstr "" + +#: ../../upgrading-checklist.rst:753 +msgid "" +"Architecture restrictions and wildcards are also allowed in binary " +"package relationships provided that the binary package is not " +"architecture-independent." +msgstr "" + +#: ../../upgrading-checklist.rst:760 ../../upgrading-checklist.rst:872 +msgid "7.4" +msgstr "" + +#: ../../upgrading-checklist.rst:758 +msgid "" +"``Conflicts`` and ``Breaks`` should only be used when there are file " +"conflicts or one package breaks the other, not just because two packages " +"provide similar functionality but don't interfere." +msgstr "" + +#: ../../upgrading-checklist.rst:766 ../../upgrading-checklist.rst:1304 +#: ../../upgrading-checklist.rst:1579 +msgid "8.1" +msgstr "" + +#: ../../upgrading-checklist.rst:763 +msgid "" +"The SONAME of a library should change whenever the ABI of the library " +"changes in a way that isn't backward-compatible. It should not change if " +"the library ABI changes are backward-compatible. Discourage bundling " +"shared libraries together in one package." +msgstr "" + +#: ../../upgrading-checklist.rst:769 +msgid "Ada Library Information (``*.ali``) files must be installed read-only." +msgstr "" + +#: ../../upgrading-checklist.rst:774 +msgid "8.6.1, 8.6.2, 8.6.5" +msgstr "" + +#: ../../upgrading-checklist.rst:773 +msgid "" +"Packages should normally not include a ``shlibs.local`` file since we now" +" have complete ``shlibs`` coverage." +msgstr "" + +#: ../../upgrading-checklist.rst:778 +msgid "8.6.3" +msgstr "" + +#: ../../upgrading-checklist.rst:777 +msgid "" +"The SONAME of a library may instead be of the form ``name-major-" +"version.so``." +msgstr "" + +#: ../../upgrading-checklist.rst:781 +msgid "" +"Libtool ``.la`` files should not be installed for public libraries. If " +"they're required (for ``libltdl``, for instance), the ``dependency_libs``" +" setting should be emptied. Library packages historically including " +"``.la`` files must continue to include them (with ``dependency_libs`` " +"emptied) until all libraries that depend on that library have removed or " +"emptied their ``.la`` files." +msgstr "" + +#: ../../upgrading-checklist.rst:789 +msgid "" +"Libraries no longer need to be built with ``-D_REENTRANT``, which was an " +"obsolete LinuxThreads requirement. Instead, say explicitly that libraries" +" should be built with threading support and to be thread-safe if the " +"library supports this." +msgstr "" + +#: ../../upgrading-checklist.rst:795 +msgid "" +"``/bin/sh`` scripts may assume that ``kill`` supports an argument of " +"``-signal``, that ``kill`` and ``trap`` support the numeric signals " +"listed in the XSI extension, and that signal 13 (SIGPIPE) can be trapped " +"with ``trap``." +msgstr "" + +#: ../../upgrading-checklist.rst:802 ../../upgrading-checklist.rst:1768 +msgid "10.8" +msgstr "" + +#: ../../upgrading-checklist.rst:801 +msgid "" +"Use of ``/etc/logrotate.d/package`` for logrotate rules is now " +"recommended." +msgstr "" + +#: ../../upgrading-checklist.rst:805 +msgid "" +"Control information files should be owned by ``root:root`` and either " +"mode 644 or mode 755." +msgstr "" + +#: ../../upgrading-checklist.rst:811 +msgid "11.4, 11.8.3, 11.8.4" +msgstr "" + +#: ../../upgrading-checklist.rst:809 +msgid "" +"Packages providing alternatives for ``editor``, ``pager``, ``x-terminal-" +"emulator``, or ``x-window-manager`` should also provide a slave " +"alternative for the corresponding manual page." +msgstr "" + +#: ../../upgrading-checklist.rst:814 +msgid "" +"Cgi-bin executable files may be installed in subdirectories of ``/usr/lib" +"/cgi-bin`` and web servers should serve out executables in those " +"subdirectories." +msgstr "" + +#: ../../upgrading-checklist.rst:819 +msgid "" +"The GPL version 1 is now included in common-licenses and should be " +"referenced from there instead of included in the ``copyright`` file." +msgstr "" + +#: ../../upgrading-checklist.rst:823 +msgid "Version 3.9.0" +msgstr "" + +#: ../../upgrading-checklist.rst:825 +msgid "Released June, 2010." +msgstr "" + +#: ../../upgrading-checklist.rst:829 +msgid "4.4, 5.6.15" +msgstr "" + +#: ../../upgrading-checklist.rst:828 +msgid "" +"The required format for the date in a changelog entry and in the Date " +"control field is now precisely specified." +msgstr "" + +#: ../../upgrading-checklist.rst:832 +msgid "" +"A control paragraph must not contain more than one instance of a " +"particular field name." +msgstr "" + +#: ../../upgrading-checklist.rst:837 +msgid "5.4, 5.5, 5.6.24" +msgstr "" + +#: ../../upgrading-checklist.rst:836 +msgid "" +"The ``Checksums-Sha1`` and ``Checksums-Sha256`` fields in ``*.dsc`` and " +"``*.changes`` files are now documented and recommended." +msgstr "" + +#: ../../upgrading-checklist.rst:843 +msgid "5.5, 5.6.16" +msgstr "" + +#: ../../upgrading-checklist.rst:840 +msgid "" +"The ``Format`` field of ``.changes`` files is now 1.8. The ``Format`` " +"field syntax for source package ``.dsc`` files allows a subtype in " +"parentheses, and it is used for a different purpose than the ``Format`` " +"field for ``.changes`` files." +msgstr "" + +#: ../../upgrading-checklist.rst:847 +msgid "5.6.2" +msgstr "" + +#: ../../upgrading-checklist.rst:846 +msgid "The syntax of the ``Maintainer`` field is now must rather than should." +msgstr "" + +#: ../../upgrading-checklist.rst:851 ../../upgrading-checklist.rst:1116 +msgid "5.6.3" +msgstr "" + +#: ../../upgrading-checklist.rst:850 +msgid "" +"The comma separating entries in ``Uploaders`` is now must rather than " +"should." +msgstr "" + +#: ../../upgrading-checklist.rst:856 +msgid "5.6.8, 7.1, 11.1.1" +msgstr "" + +#: ../../upgrading-checklist.rst:854 +msgid "" +"Architecture wildcards may be used in addition to specific architectures " +"in ``debian/control`` and ``*.dsc`` Architecture fields, and in " +"architecture restrictions in build relationships." +msgstr "" + +#: ../../upgrading-checklist.rst:863 +msgid "6.3" +msgstr "" + +#: ../../upgrading-checklist.rst:859 +msgid "" +"Maintainer scripts are no longer guaranteed to run with a controlling " +"terminal and must be able to fall back to noninteractive behavior " +"(debconf handles this). Maintainer scripts may abort if there is no " +"controlling terminal and no reasonable default for a high-priority " +"question, but should avoid this if possible." +msgstr "" + +#: ../../upgrading-checklist.rst:867 +msgid "7.3, 7.6.1" +msgstr "" + +#: ../../upgrading-checklist.rst:866 +msgid "" +"``Breaks`` should be used with ``Replaces`` for moving files between " +"packages." +msgstr "" + +#: ../../upgrading-checklist.rst:870 +msgid "" +"``Breaks`` should normally be used instead of ``Conflicts`` for transient" +" issues and moving files between packages. New documentation of when each" +" should be used." +msgstr "" + +#: ../../upgrading-checklist.rst:876 +msgid "7.5" +msgstr "" + +#: ../../upgrading-checklist.rst:875 +msgid "" +"Use ``Conflicts`` with ``Provides`` if only one provider of a virtual " +"facility can be installed at a time." +msgstr "" + +#: ../../upgrading-checklist.rst:879 +msgid "" +"All shared library development files are no longer required to be in the " +"``-dev`` package, only be available when the ``-dev`` package is " +"installed. This allows the ``-dev`` package to be split as long as it " +"depends on the additional packages." +msgstr "" + +#: ../../upgrading-checklist.rst:885 +msgid "The UID range of user accounts is extended to 1000-59999." +msgstr "" + +#: ../../upgrading-checklist.rst:889 +msgid "9.3.2, 10.4" +msgstr "" + +#: ../../upgrading-checklist.rst:888 +msgid "" +"``init.d`` scripts are a possible exception from the normal requirement " +"to use ``set -e`` in each shell script." +msgstr "" + +#: ../../upgrading-checklist.rst:892 +msgid "" +"The UCB BSD license was removed from the list of licenses that should be " +"referenced from ``/usr/share/common-licenses/BSD``. It should instead be " +"included directly in ``debian/copyright``, although it will still be in " +"common-licenses for the time being." +msgstr "" + +#: ../../upgrading-checklist.rst:898 +msgid "" +"``SETTITLE`` is now documented (it has been supported for some time). " +"``SETTITLE`` is like ``TITLE`` but takes a template instead of a string " +"to allow translation." +msgstr "" + +#: ../../upgrading-checklist.rst:903 +msgid "" +"perl-base now provides perlapi-abiname instead of a package based solely " +"on the Perl version. Perl packages must now depend on " +"perlapi-$Config{debian\\_abi}, falling back on ``$Config{version}`` if " +"``$Config{debian_abi}`` is not set." +msgstr "" + +#: ../../upgrading-checklist.rst:909 +msgid "" +"Packages using ``Makefile.PL`` should use ``DESTDIR`` rather than " +"``PREFIX`` to install into the package staging area. ``PREFIX`` only " +"worked due to a Debian-local patch." +msgstr "" + +#: ../../upgrading-checklist.rst:914 +msgid "Version 3.8.4" +msgstr "" + +#: ../../upgrading-checklist.rst:916 +msgid "Released January, 2010." +msgstr "" + +#: ../../upgrading-checklist.rst:919 +msgid "" +"An FHS exception has been granted for multiarch libraries. Permitting " +"files to instead be installed to ``/lib/triplet`` and " +"``/usr/lib/triplet`` directories." +msgstr "" + +#: ../../upgrading-checklist.rst:924 +msgid "" +"Packages may not contain named pipes and should instead create them in " +"postinst and remove them in prerm or postrm." +msgstr "" + +#: ../../upgrading-checklist.rst:928 +msgid "" +"``/sys`` and ``/selinux`` directories are explicitly allowed as an " +"exception to the FHS." +msgstr "" + +#: ../../upgrading-checklist.rst:932 +msgid "Version 3.8.3" +msgstr "" + +#: ../../upgrading-checklist.rst:934 +msgid "Released August, 2009." +msgstr "" + +#: ../../upgrading-checklist.rst:937 +msgid "" +"DEB\\_\\*\\_ARCH\\_CPU and DEB\\_\\*\\_ARCH\\_OS variables are now " +"documented and recommended over GNU-style variables for that information." +msgstr "" + +#: ../../upgrading-checklist.rst:942 +msgid "" +"Source package Architecture fields may contain *all* in combination with " +"other architectures. Clarify when *all* and *any* may be used in " +"different versions of the field." +msgstr "" + +#: ../../upgrading-checklist.rst:948 +msgid "5.6.14" +msgstr "" + +#: ../../upgrading-checklist.rst:947 +msgid "" +"The Debian archive software does not support uploading to multiple " +"distributions with one ``*.changes`` file." +msgstr "" + +#: ../../upgrading-checklist.rst:951 +msgid "5.6.19" +msgstr "" + +#: ../../upgrading-checklist.rst:951 +msgid "The Binary field may span multiple lines." +msgstr "" + +#: ../../upgrading-checklist.rst:954 +msgid "" +"Shared library packages are no longer allowed to install libraries in a " +"non-standard location and modify ``ld.so.conf``. Packages should either " +"be installed in a standard library directory or packages using them " +"should be built with RPATH." +msgstr "" + +#: ../../upgrading-checklist.rst:962 ../../upgrading-checklist.rst:1249 +#: ../../upgrading-checklist.rst:1529 ../../upgrading-checklist.rst:1662 +msgid "11.8.7" +msgstr "" + +#: ../../upgrading-checklist.rst:960 +msgid "" +"Installation directories for X programs have been clarified. Packages are" +" no longer required to pre-depend on x11-common before installing into " +"``/usr/include/X11`` and ``/usr/lib/X11``." +msgstr "" + +#: ../../upgrading-checklist.rst:966 ../../upgrading-checklist.rst:972 +#: ../../upgrading-checklist.rst:1152 ../../upgrading-checklist.rst:1422 +#: ../../upgrading-checklist.rst:1507 +msgid "12.1" +msgstr "" + +#: ../../upgrading-checklist.rst:965 +msgid "" +"Manual pages are no longer required to contain only characters " +"representable in the legacy encoding for that language." +msgstr "" + +#: ../../upgrading-checklist.rst:969 +msgid "" +"Localized man pages should either be kept up-to-date with the original " +"version or warn that they're not up-to-date, either with warning text or " +"by showing missing or changed portions in the original language." +msgstr "" + +#: ../../upgrading-checklist.rst:975 +msgid "" +"install-info is now handled via triggers so packages no longer need to " +"invoke it in maintainer scripts. Info documents should now have directory" +" sections and entries in the document. Packages containing info documents" +" should add a dependency to support partial upgrades." +msgstr "" + +#: ../../upgrading-checklist.rst:981 +msgid "" +"The requirement for Perl modules to have a versioned Depend and Build-" +"Depend on ``perl >= 5.6.0-16`` has been removed." +msgstr "" + +#: ../../upgrading-checklist.rst:985 +msgid "Version 3.8.2" +msgstr "" + +#: ../../upgrading-checklist.rst:987 +msgid "Released June, 2009." +msgstr "" + +#: ../../upgrading-checklist.rst:990 +msgid "" +"The list of archive sections has been significantly expanded. See `this " +"debian-devel-announce message <http://lists.debian.org/debian-devel-" +"announce/2009/03/msg00010.html>`__ for the list of new sections and rules" +" for how to categorize packages." +msgstr "" + +#: ../../upgrading-checklist.rst:999 ../../upgrading-checklist.rst:1207 +msgid "3.9.1" +msgstr "" + +#: ../../upgrading-checklist.rst:997 +msgid "" +"All packages must use debconf or equivalent for user prompting, though " +"essential packages or their dependencies may also fall back on other " +"methods." +msgstr "" + +#: ../../upgrading-checklist.rst:1003 ../../upgrading-checklist.rst:1193 +msgid "5.6.1" +msgstr "" + +#: ../../upgrading-checklist.rst:1002 +msgid "The requirements for source package names are now explicitly spelled out." +msgstr "" + +#: ../../upgrading-checklist.rst:1006 +msgid "" +"Legacy XFree86 servers no longer get a special exception from the FHS " +"permitting ``/etc/X11/XF86Config-4``." +msgstr "" + +#: ../../upgrading-checklist.rst:1011 +msgid "9.1.3" +msgstr "" + +#: ../../upgrading-checklist.rst:1010 +msgid "" +"Removed obsolete dependency requirements for packages that use " +"``/var/mail``." +msgstr "" + +#: ../../upgrading-checklist.rst:1015 ../../upgrading-checklist.rst:1522 +#: ../../upgrading-checklist.rst:1588 +msgid "11.8.5" +msgstr "" + +#: ../../upgrading-checklist.rst:1014 +msgid "" +"Speedo fonts are now deprecated. The X backend was disabled starting in " +"lenny." +msgstr "" + +#: ../../upgrading-checklist.rst:1018 +msgid "" +"The GNU Free Documentation License version 1.3 is included in common-" +"licenses and should be referenced from there." +msgstr "" + +#: ../../upgrading-checklist.rst:1022 +msgid "Version 3.8.1" +msgstr "" + +#: ../../upgrading-checklist.rst:1024 +msgid "Released March, 2009." +msgstr "" + +#: ../../upgrading-checklist.rst:1029 +msgid "3.8" +msgstr "" + +#: ../../upgrading-checklist.rst:1027 +msgid "" +"Care should be taken when adding functionality to essential and such " +"additions create an obligation to support that functionality in essential" +" forever unless significant work is done." +msgstr "" + +#: ../../upgrading-checklist.rst:1032 +msgid "Changelog files must be encoded in UTF-8." +msgstr "" + +#: ../../upgrading-checklist.rst:1035 +msgid "" +"Some format requirements for changelog files are now \"must\" instead of " +"\"should.\"" +msgstr "" + +#: ../../upgrading-checklist.rst:1040 +msgid "4.4.1" +msgstr "" + +#: ../../upgrading-checklist.rst:1039 +msgid "" +"Alternative changelog formats have been removed. Debian only supports one" +" changelog format for the Debian Archive." +msgstr "" + +#: ../../upgrading-checklist.rst:1043 +msgid "" +"New nocheck option for DEB\\_BUILD\\_OPTIONS indicating any build-time " +"test suite provided by the package should not be run." +msgstr "" + +#: ../../upgrading-checklist.rst:1047 +msgid "All control files must be encoded in UTF-8." +msgstr "" + +#: ../../upgrading-checklist.rst:1050 +msgid "" +"``debian/control`` allows comment lines starting with # with no preceding" +" whitespace." +msgstr "" + +#: ../../upgrading-checklist.rst:1057 +msgid "9.3" +msgstr "" + +#: ../../upgrading-checklist.rst:1054 +msgid "" +"Init scripts ending in .sh are not handled specially. They are not " +"sourced and are not guaranteed to be run by ``/bin/sh`` regardless of the" +" #! line. This brings Policy in line with the long-standing behavior of " +"the init system in Debian." +msgstr "" + +#: ../../upgrading-checklist.rst:1060 +msgid "" +"The start action of an init script must exit successfully and not start " +"the daemon again if it's already running." +msgstr "" + +#: ../../upgrading-checklist.rst:1064 +msgid "" +"``/var/run`` and ``/var/lock`` may be mounted as temporary filesystems, " +"and init scripts must therefore create any necessary subdirectories " +"dynamically." +msgstr "" + +#: ../../upgrading-checklist.rst:1069 +msgid "" +"``/bin/sh`` scripts may assume that local can take multiple variable " +"arguments and supports assignment." +msgstr "" + +#: ../../upgrading-checklist.rst:1074 ../../upgrading-checklist.rst:1543 +#: ../../upgrading-checklist.rst:1723 +msgid "11.6" +msgstr "" + +#: ../../upgrading-checklist.rst:1073 +msgid "" +"User mailboxes may be mode 600 and owned by the user rather than mode " +"660, owned by user, and group mail." +msgstr "" + +#: ../../upgrading-checklist.rst:1077 +msgid "Version 3.8.0" +msgstr "" + +#: ../../upgrading-checklist.rst:1079 +msgid "Released June, 2008." +msgstr "" + +#: ../../upgrading-checklist.rst:1084 +msgid "2.4, 3.7" +msgstr "" + +#: ../../upgrading-checklist.rst:1082 +msgid "" +"The base section has been removed. contrib and non-free have been removed" +" from the section list; they are only categories. The base system is now " +"defined by priority." +msgstr "" + +#: ../../upgrading-checklist.rst:1087 +msgid "" +"If ``dpkg-source -x`` doesn't provide the source that will be compiled, a" +" debian/rules patch target is recommended and should do whatever else is " +"necessary." +msgstr "" + +#: ../../upgrading-checklist.rst:1095 +msgid "4.9.1, 10.1" +msgstr "" + +#: ../../upgrading-checklist.rst:1092 +msgid "" +"Standardized the format of DEB\\_BUILD\\_OPTIONS. Specified permitted " +"characters for tags, required that tags be whitespace-separated, allowed " +"packages to assume non-conflicting tags, and required unknown flags be " +"ignored." +msgstr "" + +#: ../../upgrading-checklist.rst:1098 +msgid "" +"Added parallel=n to the standardized DEB\\_BUILD\\_OPTIONS tags, " +"indicating that a package should be built using up to n parallel " +"processes if the package supports it" +msgstr "" + +#: ../../upgrading-checklist.rst:1105 +msgid "4.13" +msgstr "" + +#: ../../upgrading-checklist.rst:1103 +msgid "" +"Debian packages should not use convenience copies of code from other " +"packages unless the included package is explicitly intended to be used " +"that way." +msgstr "" + +#: ../../upgrading-checklist.rst:1113 +msgid "4.14" +msgstr "" + +#: ../../upgrading-checklist.rst:1108 +msgid "" +"If dpkg-source -x doesn't produce source ready for editing and building " +"with dpkg-buildpackage, packages should include a " +"``debian/README.source`` file explaining how to generate the patched " +"source, add a new modification, and remove an existing modification. This" +" file may also be used to document packaging a new upstream release and " +"any other complexity of the Debian build process." +msgstr "" + +#: ../../upgrading-checklist.rst:1116 +msgid "The Uploaders field in debian/control may be wrapped." +msgstr "" + +#: ../../upgrading-checklist.rst:1119 +msgid "" +"An empty Debian revision is equivalent to a Debian revision of 0 in a " +"version number." +msgstr "" + +#: ../../upgrading-checklist.rst:1123 +msgid "5.6.23" +msgstr "" + +#: ../../upgrading-checklist.rst:1123 +msgid "New Homepage field for upstream web sites." +msgstr "" + +#: ../../upgrading-checklist.rst:1129 +msgid "6.5, 6.6, 7" +msgstr "" + +#: ../../upgrading-checklist.rst:1126 +msgid "" +"The Breaks field declares that this package breaks another and prevents " +"installation of the breaking package unless the package named in Breaks " +"is deconfigured first. This field should not be used until the dpkg in " +"Debian stable supports it." +msgstr "" + +#: ../../upgrading-checklist.rst:1135 +msgid "8.1, 8.2" +msgstr "" + +#: ../../upgrading-checklist.rst:1132 +msgid "" +"Clarify which files should go into a shared library package, into a " +"separate package, or into the -dev package. Suggest -tools instead of " +"-runtime for runtime support programs, since that naming is more common " +"in Debian." +msgstr "" + +#: ../../upgrading-checklist.rst:1138 +msgid "" +"Files in ``/etc/cron.{hourly,daily,weekly,monthly}`` must be " +"configuration files (upgraded from should). Mention the hourly directory." +msgstr "" + +#: ../../upgrading-checklist.rst:1144 ../../upgrading-checklist.rst:1525 +#: ../../upgrading-checklist.rst:1570 ../../upgrading-checklist.rst:1658 +msgid "11.8.6" +msgstr "" + +#: ../../upgrading-checklist.rst:1143 +msgid "" +"Packages providing ``/etc/X11/Xresources`` files need not conflict with " +"``xbase (<< 3.3.2.3a-2)``, which is long-obsolete." +msgstr "" + +#: ../../upgrading-checklist.rst:1147 +msgid "" +"Manual pages in locale-specific directories should use either the legacy " +"encoding for that directory or UTF-8. Country names should not be " +"included in locale-specific manual page directories unless indicating a " +"significant difference in the language. All characters in the manual page" +" source should be representable in the legacy encoding for a locale even " +"if the man page is encoded in UTF-8." +msgstr "" + +#: ../../upgrading-checklist.rst:1155 +msgid "" +"The Apache 2.0 license is now in common-licenses and should be referenced" +" rather than quoted in ``debian/copyright``." +msgstr "" + +#: ../../upgrading-checklist.rst:1159 +msgid "" +"Packages in contrib and non-free should state in the copyright file that " +"the package is not part of Debian GNU/Linux and briefly explain why." +msgstr "" + +#: ../../upgrading-checklist.rst:1164 +msgid "Underscore (``_``) is allowed in debconf template names." +msgstr "" + +#: ../../upgrading-checklist.rst:1167 +msgid "Version 3.7.3" +msgstr "" + +#: ../../upgrading-checklist.rst:1169 +msgid "Released December, 2007." +msgstr "" + +#: ../../upgrading-checklist.rst:1172 +msgid "" +"Package version numbers may contain tildes, which sort before anything, " +"even the end of a part." +msgstr "" + +#: ../../upgrading-checklist.rst:1176 +msgid "" +"Scripts may assume that ``/bin/sh`` supports local (at a basic level) and" +" that its test builtin (if any) supports -a and -o binary logical " +"operators." +msgstr "" + +#: ../../upgrading-checklist.rst:1183 +msgid "8.5" +msgstr "" + +#: ../../upgrading-checklist.rst:1181 +msgid "" +"The substitution variable ${binary:Version} should be used in place of " +"${Source-Version} for dependencies between packages of the same library." +msgstr "" + +#: ../../upgrading-checklist.rst:1189 ../../upgrading-checklist.rst:1350 +#: ../../upgrading-checklist.rst:1414 +msgid "menu policy" +msgstr "" + +#: ../../upgrading-checklist.rst:1186 +msgid "" +"Substantial reorganization and renaming of sections in the Debian menu " +"structure. Packages with menu entries should be reviewed to see if the " +"menu section has been renamed or if one of the new sections would be more" +" appropriate." +msgstr "" + +#: ../../upgrading-checklist.rst:1192 +msgid "" +"The Source field in a .changes file may contain a version number in " +"parentheses." +msgstr "" + +#: ../../upgrading-checklist.rst:1197 +msgid "5.6.17" +msgstr "" + +#: ../../upgrading-checklist.rst:1196 +msgid "" +"The acceptable values for the Urgency field are low, medium, high, " +"critical, or emergency." +msgstr "" + +#: ../../upgrading-checklist.rst:1200 +msgid "" +"The shlibs file now allows an optional type field, indicating the type of" +" package for which the line is valid. The only currently supported type " +"is udeb, used with packages for the Debian Installer." +msgstr "" + +#: ../../upgrading-checklist.rst:1205 +msgid "" +"Packages following the Debian Configuration management specification must" +" allow for translation of their messages by using a gettext-based system " +"such as po-debconf." +msgstr "" + +#: ../../upgrading-checklist.rst:1210 +msgid "" +"GFDL 1.2, GPL 3, and LGPL 3 are now in common-licenses and should be " +"referenced rather than quoted in debian/copyright." +msgstr "" + +#: ../../upgrading-checklist.rst:1214 +msgid "Version 3.7.2.2" +msgstr "" + +#: ../../upgrading-checklist.rst:1216 +msgid "Released October, 2006." +msgstr "" + +#: ../../upgrading-checklist.rst:1218 ../../upgrading-checklist.rst:1595 +msgid "" +"This release broke the normal rule against introducing normative changes " +"without changing the major patch level." +msgstr "" + +#: ../../upgrading-checklist.rst:1223 +msgid "6.1" +msgstr "" + +#: ../../upgrading-checklist.rst:1222 +msgid "" +"Maintainer scripts must not be world writeable (up from a should to a " +"must)" +msgstr "" + +#: ../../upgrading-checklist.rst:1226 +msgid "Version 3.7.2" +msgstr "" + +#: ../../upgrading-checklist.rst:1228 ../../upgrading-checklist.rst:1236 +#: ../../upgrading-checklist.rst:1254 +msgid "Released April, 2006." +msgstr "" + +#: ../../upgrading-checklist.rst:1231 +msgid "Revert the cgi-lib change." +msgstr "" + +#: ../../upgrading-checklist.rst:1234 +msgid "Version 3.7.1" +msgstr "" + +#: ../../upgrading-checklist.rst:1239 +msgid "" +"It is now possible to create shared libraries without relocatable code " +"(using -fPIC) in certain exceptional cases, provided some procedures are " +"followed, and for creating static libraries with relocatable code (again," +" using -fPIC). Discussion on debian-devel@lists.debian.org, getting a " +"rough consensus, and documenting it in README.Debian constitute most of " +"the process." +msgstr "" + +#: ../../upgrading-checklist.rst:1247 +msgid "" +"Packages should install any relevant files into the directories " +"``/usr/include/X11/`` and ``/usr/lib/X11/``, but if they do so, they must" +" pre-depend on ``x11-common (>= 1:7.0.0)``" +msgstr "" + +#: ../../upgrading-checklist.rst:1252 +msgid "Version 3.7.0" +msgstr "" + +#: ../../upgrading-checklist.rst:1257 +msgid "" +"Packages shipping web server CGI files are expected to install them in " +"``/usr/lib/cgi-lib/`` directories. This location change perhaps should be" +" documented in NEWS" +msgstr "" + +#: ../../upgrading-checklist.rst:1262 +msgid "" +"Web server packages should include a standard scriptAlias of cgi-lib to " +"``/usr/lib/cgi-lib``." +msgstr "" + +#: ../../upgrading-checklist.rst:1266 +msgid "" +"The version of FHS mandated by policy has been upped to 2.3. There should" +" be no changes required for most packages, though new top level " +"directories ``/media``, ``/srv``, etc. may be of interest." +msgstr "" + +#: ../../upgrading-checklist.rst:1276 +msgid "5.1, 5.6.3" +msgstr "" + +#: ../../upgrading-checklist.rst:1271 +msgid "" +"All fields, apart from the Uploaders field, in the control file are " +"supposed to be a single logical line, which may be spread over multiple " +"physical lines (newline followed by space is elided). However, any parser" +" for the control file must allow the Uploaders field to be spread over " +"multiple physical lines as well, to prepare for future changes." +msgstr "" + +#: ../../upgrading-checklist.rst:1279 +msgid "" +"When scripts are installed into a directory in the system PATH, the " +"script name should not include an extension that denotes the scripting " +"language currently used to implement it." +msgstr "" + +#: ../../upgrading-checklist.rst:1284 +msgid "" +"packages that invoke initscripts now must use invoke-rc.d to do so since " +"it also pays attention to run levels and other local constraints." +msgstr "" + +#: ../../upgrading-checklist.rst:1291 +msgid "11.8.5.2, 11.8.7, etc" +msgstr "" + +#: ../../upgrading-checklist.rst:1289 +msgid "" +"We no longer use ``/usr/X11R6``, since we have migrated away to using " +"Xorg paths. This means, for one thing, fonts live in " +"``/usr/share/fonts/X11/`` now, and ``/usr/X11R6`` is gone." +msgstr "" + +#: ../../upgrading-checklist.rst:1294 +msgid "Version 3.6.2" +msgstr "" + +#: ../../upgrading-checklist.rst:1296 +msgid "Released June, 2005." +msgstr "" + +#: ../../upgrading-checklist.rst:1298 +msgid "Recommend doc-base, and not menu, for registering package documentation." +msgstr "" + +#: ../../upgrading-checklist.rst:1302 +msgid "" +"Run time support programs should live in subdirectories of ``/usr/lib/`` " +"or ``/usr/share``, and preferably the shared lib is named the same as the" +" package name (to avoid name collisions)." +msgstr "" + +#: ../../upgrading-checklist.rst:1307 +msgid "" +"It is recommended that HTTP servers provide an alias /images to allow " +"packages to share image files with the web server" +msgstr "" + +#: ../../upgrading-checklist.rst:1311 +msgid "Version 3.6.1" +msgstr "" + +#: ../../upgrading-checklist.rst:1313 +msgid "Released August, 2003." +msgstr "" + +#: ../../upgrading-checklist.rst:1317 +msgid "3.10.1" +msgstr "" + +#: ../../upgrading-checklist.rst:1316 +msgid "" +"Prompting the user should be done using debconf. Non debconf user prompts" +" are now deprecated." +msgstr "" + +#: ../../upgrading-checklist.rst:1320 +msgid "Version 3.6.0" +msgstr "" + +#: ../../upgrading-checklist.rst:1322 +msgid "Released July, 2003." +msgstr "" + +#: ../../upgrading-checklist.rst:1324 +msgid "" +"Restructuring caused shifts in section numbers and bumping of the minor " +"version number." +msgstr "" + +#: ../../upgrading-checklist.rst:1327 +msgid "" +"Many packaging manual appendices that were integrated into policy " +"sections are now empty, and replaced with links to the Policy. In " +"particular, the appendices that included the list of control fields were " +"updated (new fields like Closes, Changed-By were added) and the list of " +"fields for each of control, .changes and .dsc files is now in Policy, and" +" they're marked mandatory, recommended or optional based on the current " +"practice and the behavior of the deb-building tool-chain." +msgstr "" + +#: ../../upgrading-checklist.rst:1336 +msgid "" +"Elimination of needlessly deep section levels, primarily in the chapter " +"Debian Archive, from which two new chapters were split out, Binary " +"packages and Source packages. What remained was reordered properly, that " +"is, some sects became sects etc." +msgstr "" + +#: ../../upgrading-checklist.rst:1341 +msgid "" +"Several sections that were redundant, crufty or simply not designed with " +"any sort of vision, were rearranged according to the formula that " +"everything should be either in the same place or properly interlinked. " +"Some things remained split up between different chapters when they talked" +" about different aspects of files: their content, their syntax, and their" +" placement in the file system. In particular, see the new sections about " +"changelog files." +msgstr "" + +#: ../../upgrading-checklist.rst:1350 +msgid "Added Games/Simulation and Apps/Education to menu sub-policy" +msgstr "" + +#: ../../upgrading-checklist.rst:1353 +msgid "C.2.2" +msgstr "" + +#: ../../upgrading-checklist.rst:1353 +msgid "Debian changelogs should be UTF-8 encoded." +msgstr "" + +#: ../../upgrading-checklist.rst:1356 +msgid "" +"shared libraries must be linked against all libraries that they use " +"symbols from in the same way that binaries are." +msgstr "" + +#: ../../upgrading-checklist.rst:1360 ../../upgrading-checklist.rst:1411 +msgid "7.6" +msgstr "" + +#: ../../upgrading-checklist.rst:1360 +msgid "build-depends-indep need not be satisfied during clean target." +msgstr "" + +#: ../../upgrading-checklist.rst:1363 +msgid "Version 3.5.10" +msgstr "" + +#: ../../upgrading-checklist.rst:1365 +msgid "Released May, 2003." +msgstr "" + +#: ../../upgrading-checklist.rst:1368 +msgid "" +"packages providing the x-terminal-emulator virtual package ought to " +"ensure that they interpret the command line exactly like xterm does." +msgstr "" + +#: ../../upgrading-checklist.rst:1373 ../../upgrading-checklist.rst:1441 +#: ../../upgrading-checklist.rst:1652 +msgid "11.8.4" +msgstr "" + +#: ../../upgrading-checklist.rst:1372 +msgid "" +"Window managers compliant with the Window Manager Specification Project " +"may add 40 points for ranking in the alternatives" +msgstr "" + +#: ../../upgrading-checklist.rst:1376 +msgid "Version 3.5.9" +msgstr "" + +#: ../../upgrading-checklist.rst:1378 +msgid "Released March, 2003." +msgstr "" + +#: ../../upgrading-checklist.rst:1382 +msgid "3.4.2" +msgstr "" + +#: ../../upgrading-checklist.rst:1381 +msgid "" +"The section describing the Description: package field once again has full" +" details of the long description format." +msgstr "" + +#: ../../upgrading-checklist.rst:1387 +msgid "4.2" +msgstr "" + +#: ../../upgrading-checklist.rst:1385 +msgid "" +"Clarified that if a package has non-build-essential build-dependencies, " +"it should have them listed in the Build-Depends and related fields (i.e. " +"it's not merely optional)." +msgstr "" + +#: ../../upgrading-checklist.rst:1390 +msgid "" +"When asked to restart a service that isn't already running, the init " +"script should start the service." +msgstr "" + +#: ../../upgrading-checklist.rst:1396 ../../upgrading-checklist.rst:1761 +msgid "12.6" +msgstr "" + +#: ../../upgrading-checklist.rst:1394 +msgid "" +"If the purpose of a package is to provide examples, then the example " +"files can be installed into ``/usr/share/doc/package`` (rather than " +"``/usr/share/doc/package/examples``)." +msgstr "" + +#: ../../upgrading-checklist.rst:1399 +msgid "Version 3.5.8" +msgstr "" + +#: ../../upgrading-checklist.rst:1401 +msgid "Released November, 2002." +msgstr "" + +#: ../../upgrading-checklist.rst:1406 ../../upgrading-checklist.rst:1709 +#: ../../upgrading-checklist.rst:1728 +msgid "12.7" +msgstr "" + +#: ../../upgrading-checklist.rst:1404 +msgid "" +"It is no longer necessary to keep a log of changes to the upstream " +"sources in the copyright file. Instead, all such changes should be " +"documented in the changelog file." +msgstr "" + +#: ../../upgrading-checklist.rst:1409 +msgid "" +"Build-Depends, Build-Conflicts, Build-Depends-Indep, and Build-Conflicts-" +"Indep must also be satisfied when the clean target is called." +msgstr "" + +#: ../../upgrading-checklist.rst:1414 +msgid "A new Apps/Science menu section is available" +msgstr "" + +#: ../../upgrading-checklist.rst:1417 +msgid "debconf policy" +msgstr "" + +#: ../../upgrading-checklist.rst:1417 +msgid "debconf specification cleared up, various changes." +msgstr "" + +#: ../../upgrading-checklist.rst:1420 +msgid "" +"It is no longer recommended to create symlinks from nonexistent manual " +"pages to undocumented(7). Missing manual pages for programs are still a " +"bug." +msgstr "" + +#: ../../upgrading-checklist.rst:1425 +msgid "Version 3.5.7" +msgstr "" + +#: ../../upgrading-checklist.rst:1427 +msgid "Released August, 2002." +msgstr "" + +#: ../../upgrading-checklist.rst:1429 +msgid "" +"Packages no longer have to ask permission to call MAKEDEV in postinst, " +"merely notifying the user ought to be enough." +msgstr "" + +#: ../../upgrading-checklist.rst:1433 +msgid "2.2.4" +msgstr "" + +#: ../../upgrading-checklist.rst:1433 +msgid "cryptographic software may now be included in the main archive." +msgstr "" + +#: ../../upgrading-checklist.rst:1436 +msgid "" +"task packages are no longer permitted; tasks are now created by a special" +" Tasks: field in the control file." +msgstr "" + +#: ../../upgrading-checklist.rst:1440 +msgid "" +"window managers that support netwm can now add 20 points when they add " +"themselves as an alternative for ``/usr/bin/x-window-manager``" +msgstr "" + +#: ../../upgrading-checklist.rst:1444 +msgid "" +"The default compilation options have now changed, one should provide " +"debugging symbols in all cases, and optionally step back optimization to " +"-O0, depending on the DEB\\_BUILD\\_OPTIONS environment variable." +msgstr "" + +#: ../../upgrading-checklist.rst:1453 +msgid "7.6, 4.8" +msgstr "" + +#: ../../upgrading-checklist.rst:1450 +msgid "" +"Added mention of build-arch, build-indep, etc, in describing the " +"relationships with Build-Depends, Build-Conflicts, Build-Depends-Indep, " +"and Build-Conflicts-Indep. May need to review the new rules." +msgstr "" + +#: ../../upgrading-checklist.rst:1457 ../../upgrading-checklist.rst:1670 +msgid "8" +msgstr "" + +#: ../../upgrading-checklist.rst:1456 +msgid "" +"Changed rules on how, and when, to invoke ldconfig in maintainer scripts." +" Long rationale." +msgstr "" + +#: ../../upgrading-checklist.rst:1459 +msgid "" +"*Added the last note in 3.5.6 upgrading checklist item regarding build " +"rules, please see below*" +msgstr "" + +#: ../../upgrading-checklist.rst:1463 +msgid "Version 3.5.6" +msgstr "" + +#: ../../upgrading-checklist.rst:1465 +msgid "Released July, 2001." +msgstr "" + +#: ../../upgrading-checklist.rst:1468 +msgid "" +"Emacs and TeX are no longer mandated by policy to be priority standard " +"packages" +msgstr "" + +#: ../../upgrading-checklist.rst:1472 +msgid "" +"Programs that access docs need to do so via ``/usr/share/doc``, and not " +"via ``/usr/doc/`` as was the policy previously" +msgstr "" + +#: ../../upgrading-checklist.rst:1476 +msgid "" +"Putting documentation in ``/usr/doc`` versus ``/usr/share/doc`` is now a " +"\"serious\" policy violation." +msgstr "" + +#: ../../upgrading-checklist.rst:1480 +msgid "" +"For web servers, one should not provide non-local access to the " +"``/usr/share/doc`` hierarchy. If one can't provide access controls for " +"the http://localhost/doc/ directory, then it is preferred that one ask " +"permission to expose that information during the install." +msgstr "" + +#: ../../upgrading-checklist.rst:1487 +msgid "7" +msgstr "" + +#: ../../upgrading-checklist.rst:1486 +msgid "" +"There are new rules for build-indep/build-arch targets and there is a new" +" Build-Depend-Indep semantic." +msgstr "" + +#: ../../upgrading-checklist.rst:1490 +msgid "Version 3.5.5" +msgstr "" + +#: ../../upgrading-checklist.rst:1492 +msgid "Released May, 2001." +msgstr "" + +#: ../../upgrading-checklist.rst:1495 +msgid "" +"Manpages should not rely on header information to have alternative " +"manpage names available; it should only use symlinks or .so pages to do " +"this" +msgstr "" + +#: ../../upgrading-checklist.rst:1499 +msgid "" +"*Clarified note in 3.5.3.0 upgrading checklist regarding examples and " +"templates: this refers only to those examples used by scripts; see " +"section 10.7.3 for the whole story*" +msgstr "" + +#: ../../upgrading-checklist.rst:1503 +msgid "" +"Included a new section 10.9.1 describing the use of dpkg-statoverride; " +"this does not have the weight of policy" +msgstr "" + +#: ../../upgrading-checklist.rst:1506 +msgid "" +"Clarify Standards-Version: you don't need to rebuild your packages just " +"to change the Standards-Version!" +msgstr "" + +#: ../../upgrading-checklist.rst:1510 +msgid "Plugins are no longer bound by all the rules of shared libraries" +msgstr "" + +#: ../../upgrading-checklist.rst:1533 +msgid "X Windows related things:" +msgstr "" + +#: ../../upgrading-checklist.rst:1515 ../../upgrading-checklist.rst:1620 +msgid "11.8.1" +msgstr "" + +#: ../../upgrading-checklist.rst:1514 +msgid "Clarification of priority levels of X Window System related packages" +msgstr "" + +#: ../../upgrading-checklist.rst:1518 +msgid "Rules for defining x-terminal-emulator improved" +msgstr "" + +#: ../../upgrading-checklist.rst:1521 +msgid "" +"X Font policy rewritten: you must read this if you provide fonts for the " +"X Window System" +msgstr "" + +#: ../../upgrading-checklist.rst:1525 +msgid "Packages must not ship ``/usr/X11R6/lib/X11/app-defaults/``" +msgstr "" + +#: ../../upgrading-checklist.rst:1528 +msgid "" +"X-related packages should usually use the regular FHS locations; imake-" +"using packages are exempted from this" +msgstr "" + +#: ../../upgrading-checklist.rst:1533 +msgid "11.8.8" +msgstr "" + +#: ../../upgrading-checklist.rst:1532 +msgid "OpenMotif linked binaries have the same rules as OSF/Motif-linked ones" +msgstr "" + +#: ../../upgrading-checklist.rst:1536 +msgid "Version 3.5.4" +msgstr "" + +#: ../../upgrading-checklist.rst:1538 ../../upgrading-checklist.rst:1552 +msgid "Released April, 2001." +msgstr "" + +#: ../../upgrading-checklist.rst:1541 +msgid "" +"The system-wide mail directory is now /var/mail, no longer " +"/var/spool/mail. Any packages accessing the mail spool should access it " +"via /var/mail and include a suitable Depends field;" +msgstr "" + +#: ../../upgrading-checklist.rst:1547 +msgid "11.9; perl-policy" +msgstr "" + +#: ../../upgrading-checklist.rst:1546 +msgid "" +"The perl policy is now part of Debian policy proper. Perl programs and " +"modules should follow the current Perl policy" +msgstr "" + +#: ../../upgrading-checklist.rst:1550 +msgid "Version 3.5.3" +msgstr "" + +#: ../../upgrading-checklist.rst:1555 +msgid "" +"Build-Depends arch syntax has been changed to be less ambiguous. This " +"should not affect any current packages" +msgstr "" + +#: ../../upgrading-checklist.rst:1559 +msgid "" +"Examples and templates files for use by scripts should now live in " +"``/usr/share/<package>`` or ``/usr/lib/<package>``, with symbolic links " +"from ``/usr/share/doc/<package>/examples`` as needed" +msgstr "" + +#: ../../upgrading-checklist.rst:1564 +msgid "Version 3.5.2" +msgstr "" + +#: ../../upgrading-checklist.rst:1566 ../../upgrading-checklist.rst:1575 +msgid "Released February, 2001." +msgstr "" + +#: ../../upgrading-checklist.rst:1569 +msgid "" +"X app-defaults directory has moved from ``/usr/X11R6/lib/X11/app-" +"defaults`` to ``/etc/X11/app-defaults``" +msgstr "" + +#: ../../upgrading-checklist.rst:1573 +msgid "Version 3.5.1" +msgstr "" + +#: ../../upgrading-checklist.rst:1578 +msgid "" +"dpkg-shlibdeps now uses objdump, so shared libraries have to be run " +"through dpkg-shlibdeps as well as executables" +msgstr "" + +#: ../../upgrading-checklist.rst:1582 +msgid "Version 3.5.0" +msgstr "" + +#: ../../upgrading-checklist.rst:1584 ../../upgrading-checklist.rst:1593 +msgid "Released January, 2001." +msgstr "" + +#: ../../upgrading-checklist.rst:1587 +msgid "" +"Font packages for the X Window System must now declare a dependency on " +"``xutils (>= 4.0.2)``" +msgstr "" + +#: ../../upgrading-checklist.rst:1591 +msgid "Version 3.2.1.1" +msgstr "" + +#: ../../upgrading-checklist.rst:1599 +msgid "" +"Daemon startup scripts in ``/etc/init.d/`` should not contain modifiable " +"parameters; these should be moved to a file in ``/etc/default/``" +msgstr "" + +#: ../../upgrading-checklist.rst:1604 +msgid "" +"Files in ``/usr/share/doc`` must not be referenced by any program. If " +"such files are needed, they must be placed in ``/usr/share/<package>/``, " +"and symbolic links created as required in ``/usr/share/doc/<package>/``" +msgstr "" + +#: ../../upgrading-checklist.rst:1609 +msgid "" +"Much of the packaging manual has now been imported into the policy " +"document" +msgstr "" + +#: ../../upgrading-checklist.rst:1613 +msgid "Version 3.2.1" +msgstr "" + +#: ../../upgrading-checklist.rst:1615 ../../upgrading-checklist.rst:1625 +msgid "Released August, 2000." +msgstr "" + +#: ../../upgrading-checklist.rst:1618 +msgid "" +"A package of priority standard or higher may provide two binaries, one " +"compiled with support for the X Window System, and the other without" +msgstr "" + +#: ../../upgrading-checklist.rst:1623 +msgid "Version 3.2.0" +msgstr "" + +#: ../../upgrading-checklist.rst:1628 +msgid "" +"By default executables should not be built with the debugging option -g. " +"Instead, it is recommended to support building the package with debugging" +" information optionally." +msgstr "" + +#: ../../upgrading-checklist.rst:1658 +msgid "12.8" +msgstr "" + +#: ../../upgrading-checklist.rst:1633 +msgid "" +"Policy for packages where the upstream uses HTML changelog files has been" +" expanded. In short, a plain text changelog file should always be " +"generated for the upstream changes" +msgstr "" + +#: ../../upgrading-checklist.rst:1637 +msgid "" +"Please note that the new release of the X window system (3.2) shall " +"probably need sweeping changes in policy" +msgstr "" + +#: ../../upgrading-checklist.rst:1640 +msgid "" +"Policy for packages providing the following X-based features has been " +"codified:" +msgstr "" + +#: ../../upgrading-checklist.rst:1644 +msgid "11.8.2" +msgstr "" + +#: ../../upgrading-checklist.rst:1644 +msgid "X server (virtual package xserver)" +msgstr "" + +#: ../../upgrading-checklist.rst:1647 +msgid "X terminal emulator (virtual package x-terminal-emulator)" +msgstr "" + +#: ../../upgrading-checklist.rst:1650 +msgid "" +"X window manager (virtual package x-window-manager, and ``/usr/bin/x" +"-window-manager`` alternative, with priority calculation guidelines)" +msgstr "" + +#: ../../upgrading-checklist.rst:1655 +msgid "12.8.5" +msgstr "" + +#: ../../upgrading-checklist.rst:1655 +msgid "X fonts (this section has been written from scratch)" +msgstr "" + +#: ../../upgrading-checklist.rst:1658 +msgid "X application defaults" +msgstr "" + +#: ../../upgrading-checklist.rst:1661 +msgid "" +"Policy for packages using the X Window System and FHS issues has been " +"clarified;" +msgstr "" + +#: ../../upgrading-checklist.rst:1665 +msgid "11.7.3" +msgstr "" + +#: ../../upgrading-checklist.rst:1665 +msgid "No package may contain or make hard links to conffiles" +msgstr "" + +#: ../../upgrading-checklist.rst:1668 +msgid "" +"Noted that newer dpkg versions do not require extreme care in always " +"creating the shared lib before the symlink, so the unpack order be " +"correct" +msgstr "" + +#: ../../upgrading-checklist.rst:1673 +msgid "Version 3.1.1" +msgstr "" + +#: ../../upgrading-checklist.rst:1675 +msgid "Released November, 1999." +msgstr "" + +#: ../../upgrading-checklist.rst:1678 +msgid "" +"Correction to semantics of architecture lists in Build-Depends etc. " +"Should not affect many packages" +msgstr "" + +#: ../../upgrading-checklist.rst:1682 +msgid "Version 3.1.0" +msgstr "" + +#: ../../upgrading-checklist.rst:1684 +msgid "Released October, 1999." +msgstr "" + +#: ../../upgrading-checklist.rst:1689 +msgid "defunct" +msgstr "" + +#: ../../upgrading-checklist.rst:1687 +msgid "" +"``/usr/doc/<package>`` has to be a symlink pointing to " +"``/usr/share/doc/<package>``, to be maintained by postinst and prerm " +"scripts." +msgstr "" + +#: ../../upgrading-checklist.rst:1692 +msgid "7.1, 7.6" +msgstr "" + +#: ../../upgrading-checklist.rst:1692 +msgid "Introduced source dependencies (Build-Depends, etc.)" +msgstr "" + +#: ../../upgrading-checklist.rst:1697 +msgid "9.3.4" +msgstr "" + +#: ../../upgrading-checklist.rst:1695 +msgid "" +"``/etc/rc.boot`` has been deprecated in favour of ``/etc/rcS.d``. " +"(Packages should not be touching this directory, but should use update-" +"rc.d instead)" +msgstr "" + +#: ../../upgrading-checklist.rst:1700 +msgid "" +"update-rc.d is now the *only* allowable way of accessing the " +"``/etc/rc?.d/[SK]??*`` links. Any scripts which manipulate them directly " +"must be changed to use update-rc.d instead. (This is because the file-rc " +"package handles this information in an incompatible way.)" +msgstr "" + +#: ../../upgrading-checklist.rst:1707 +msgid "" +"Architecture-specific examples go in ``/usr/lib/<package>/examples`` with" +" symlinks from ``/usr/share/doc/<package>/examples/*`` or from " +"``/usr/share/doc/<package>/examples`` itself" +msgstr "" + +#: ../../upgrading-checklist.rst:1712 +msgid "Updated FHS to a 2.1 draft; this reverts ``/var/state`` to ``/var/lib``" +msgstr "" + +#: ../../upgrading-checklist.rst:1716 +msgid "9.7; mime-policy" +msgstr "" + +#: ../../upgrading-checklist.rst:1716 +msgid "Added MIME sub-policy document" +msgstr "" + +#: ../../upgrading-checklist.rst:1719 +msgid "12.4" +msgstr "" + +#: ../../upgrading-checklist.rst:1719 +msgid "VISUAL is allowed as a (higher priority) alternative to EDITOR" +msgstr "" + +#: ../../upgrading-checklist.rst:1722 +msgid "" +"Modified liblockfile description, which affects mailbox-accessing " +"programs. Please see the policy document for details" +msgstr "" + +#: ../../upgrading-checklist.rst:1726 +msgid "" +"If a package provides a changelog in HTML format, a text-only version " +"should also be included. (Such a version may be prepared using ``lynx " +"-dump -nolist``.)" +msgstr "" + +#: ../../upgrading-checklist.rst:1731 +msgid "Description of how to handle version numbers based on dates added" +msgstr "" + +#: ../../upgrading-checklist.rst:1734 +msgid "Version 3.0.1" +msgstr "" + +#: ../../upgrading-checklist.rst:1736 +msgid "Released July, 1999." +msgstr "" + +#: ../../upgrading-checklist.rst:1739 +msgid "" +"Added the clarification that the .la files are essential for the packages" +" using libtool's libltdl library, in which case the .la files must go in " +"the run-time library package" +msgstr "" + +#: ../../upgrading-checklist.rst:1744 +msgid "Version 3.0.0" +msgstr "" + +#: ../../upgrading-checklist.rst:1746 +msgid "Released June, 1999." +msgstr "" + +#: ../../upgrading-checklist.rst:1749 +msgid "" +"Debian formally moves from the FSSTND to the FHS. This is a major change," +" and the implications of this move are probably not all known." +msgstr "" + +#: ../../upgrading-checklist.rst:1755 +msgid "4.1" +msgstr "" + +#: ../../upgrading-checklist.rst:1754 +msgid "" +"Only 3 digits of the Standards version need be included in control files," +" though all four digits are still permitted." +msgstr "" + +#: ../../upgrading-checklist.rst:1758 +msgid "" +"The location of the GPL has changed to ``/usr/share/common-licenses``. " +"This may require changing the copyright files to point to the correct " +"location of the GPL and other major licenses" +msgstr "" + +#: ../../upgrading-checklist.rst:1764 +msgid "" +"Packages that use libtool to create shared libraries must include the .la" +" files in the -dev packages" +msgstr "" + +#: ../../upgrading-checklist.rst:1768 +msgid "Use logrotate to rotate log files" +msgstr "" + +#: ../../upgrading-checklist.rst:1771 +msgid "now 11.8" +msgstr "" + +#: ../../upgrading-checklist.rst:1771 +msgid "section 5.8 has been rewritten (Programs for the X Window System)" +msgstr "" + +#: ../../upgrading-checklist.rst:1775 +msgid "9.6; menu-policy" +msgstr "" + +#: ../../upgrading-checklist.rst:1774 +msgid "" +"There is now an associated menu policy, in a separate document, that " +"carries the full weight of Debian policy" +msgstr "" + +#: ../../upgrading-checklist.rst:1780 +msgid "11.3" +msgstr "" + +#: ../../upgrading-checklist.rst:1778 +msgid "" +"Programs which need to modify the files ``/var/run/utmp``, " +"``/var/log/wtmp`` and ``/var/log/lastlog`` must be installed setgid utmp" +msgstr "" + +#: ../../upgrading-checklist.rst:1783 +msgid "Version 2.5.0" +msgstr "" + +#: ../../upgrading-checklist.rst:1785 +msgid "Released October, 1998." +msgstr "" + +#: ../../upgrading-checklist.rst:1787 +msgid "" +"*Please note that section numbers below this point may not match the " +"current Policy Manual.*" +msgstr "" + +#: ../../upgrading-checklist.rst:1790 +msgid "Rearranged the manual to create a new Section 4, Files" +msgstr "" + +#: ../../upgrading-checklist.rst:1792 +msgid "" +"Section 3.3 (\"Files\") was moved to Section 4. The Sections that were " +"Section 4 and Section 5 were moved down to become Section 5 and Section " +"6." +msgstr "" + +#: ../../upgrading-checklist.rst:1796 +msgid "" +"What was Section 5.5 (\"Log files\") is now a subsection of the new " +"Section 4 (\"Files\"), becoming section 4.8, placed after \"Configuration" +" files\", moving the Section 4.8 (\"Permissions and owners\") to Section " +"4.9. All subsections of the old Section 5 after 5.5 were moved down to " +"fill in the number gap." +msgstr "" + +#: ../../upgrading-checklist.rst:1802 +msgid "" +"Modified the section about changelog files to accommodate upstream " +"changelogs which were formatted as HTML. These upstream changelog files " +"should now be accessible as ``/usr/doc/package/changelog.html.gz``" +msgstr "" + +#: ../../upgrading-checklist.rst:1807 +msgid "" +"Symlinks are permissible to link the real, or upstream, changelog name to" +" the Debian mandated name." +msgstr "" + +#: ../../upgrading-checklist.rst:1810 +msgid "" +"Clarified that HTML documentation should be present in some package, " +"though not necessarily the main binary package." +msgstr "" + +#: ../../upgrading-checklist.rst:1813 +msgid "" +"Corrected all references to the location of the copyright files. The " +"correct location is ``/usr/doc/package/copyright``" +msgstr "" + +#: ../../upgrading-checklist.rst:1816 +msgid "Ratified the architecture specification strings to cater to the HURD." +msgstr "" + +#: ../../upgrading-checklist.rst:1819 +msgid "Version 2.4.1" +msgstr "" + +#: ../../upgrading-checklist.rst:1821 +msgid "Released April, 1998." +msgstr "" + +#: ../../upgrading-checklist.rst:1826 +msgid "Updated section 3.3.5 Symbolic links" +msgstr "" + +#: ../../upgrading-checklist.rst:1824 +msgid "" +"symbolic links within a toplevel directory should be relative, symbolic " +"links between toplevel directories should be absolute (cf., Policy Weekly" +" Issue#6, topic 2)" +msgstr "" + +#: ../../upgrading-checklist.rst:1830 ../../upgrading-checklist.rst:1895 +msgid "Updated section 4.9 Games" +msgstr "" + +#: ../../upgrading-checklist.rst:1829 +msgid "" +"manpages for games should be installed in ``/usr/man/man6`` (cf., Policy " +"Weekly Issue#6, topic 3)" +msgstr "" + +#: ../../upgrading-checklist.rst:1835 +msgid "Updated Chapter 12 Shared Libraries" +msgstr "" + +#: ../../upgrading-checklist.rst:1833 +msgid "" +"ldconfig must be called in the postinst script if the package installs " +"shared libraries (cf., Policy Weekly Issue #6, fixes:bug#20515)" +msgstr "" + +#: ../../upgrading-checklist.rst:1838 +msgid "Version 2.4.0" +msgstr "" + +#: ../../upgrading-checklist.rst:1840 +msgid "Released January, 1998" +msgstr "" + +#: ../../upgrading-checklist.rst:1850 +msgid "Updated section 3.3.4 Scripts" +msgstr "" + +#: ../../upgrading-checklist.rst:1843 +msgid "/bin/sh may be any POSIX compatible shell" +msgstr "" + +#: ../../upgrading-checklist.rst:1845 +msgid "scripts including bashisms have to specify ``/bin/bash`` as interpreter" +msgstr "" + +#: ../../upgrading-checklist.rst:1848 +msgid "" +"scripts which create files in world-writable directories (e.g., in " +"``/tmp``) should use tempfile or mktemp for creating the directory" +msgstr "" + +#: ../../upgrading-checklist.rst:1854 +msgid "Updated section 3.3.5 Symbolic Links" +msgstr "" + +#: ../../upgrading-checklist.rst:1853 +msgid "" +"symbolic links referencing compressed files must have the same file " +"extension as the referenced file" +msgstr "" + +#: ../../upgrading-checklist.rst:1857 +msgid "Updated section 3.3.6 Device files" +msgstr "" + +#: ../../upgrading-checklist.rst:1857 +msgid "``/dev/tty*`` serial devices should be used instead of ``/dev/cu*``" +msgstr "" + +#: ../../upgrading-checklist.rst:1864 +msgid "Updated section 3.4.2 Writing the scripts in ``/etc/init.d``" +msgstr "" + +#: ../../upgrading-checklist.rst:1860 +msgid "" +"all ``/etc/init.d`` scripts have to provide the following options: start," +" stop, restart, force-reload" +msgstr "" + +#: ../../upgrading-checklist.rst:1863 +msgid "the reload option is optional and must never stop and restart the service" +msgstr "" + +#: ../../upgrading-checklist.rst:1868 +msgid "Updated section 3.5 Cron jobs" +msgstr "" + +#: ../../upgrading-checklist.rst:1867 +msgid "" +"cron jobs that need to be executed more often than daily should be " +"installed into ``/etc/cron.d``" +msgstr "" + +#: ../../upgrading-checklist.rst:1873 +msgid "Updated section 3.7 Menus" +msgstr "" + +#: ../../upgrading-checklist.rst:1871 +msgid "" +"removed section about how to register HTML docs to \\`menu' (the " +"corresponding section in 4.4, Web servers and applications, has been " +"removed in policy 2.2.0.0 already, so this one was obsolete)" +msgstr "" + +#: ../../upgrading-checklist.rst:1876 +msgid "New section 3.8 Keyboard configuration" +msgstr "" + +#: ../../upgrading-checklist.rst:1876 +msgid "details about how the backspace and delete keys should be handled" +msgstr "" + +#: ../../upgrading-checklist.rst:1880 +msgid "New section 3.9 Environment variables" +msgstr "" + +#: ../../upgrading-checklist.rst:1879 +msgid "" +"no program must depend on environment variables to get a reasonable " +"default configuration" +msgstr "" + +#: ../../upgrading-checklist.rst:1884 +msgid "New section 4.6 News system configuration" +msgstr "" + +#: ../../upgrading-checklist.rst:1883 +msgid "" +"``/etc/news/organization`` and ``/etc/news/server`` should be supported " +"by all news servers and clients" +msgstr "" + +#: ../../upgrading-checklist.rst:1891 +msgid "Updated section 4.7 Programs for the X Window System" +msgstr "" + +#: ../../upgrading-checklist.rst:1887 +msgid "" +"programs requiring a non-free Motif library should be provided as foo-" +"smotif and foo-dmotif package" +msgstr "" + +#: ../../upgrading-checklist.rst:1890 +msgid "" +"if lesstif works reliably for such program, it should be linked against " +"lesstif and not against a non-free Motif library" +msgstr "" + +#: ../../upgrading-checklist.rst:1894 +msgid "" +"games for X Windows have to be installed in ``/usr/games``, just as non-X" +" games" +msgstr "" + +#: ../../upgrading-checklist.rst:1898 +msgid "Version 2.3.0" +msgstr "" + +#: ../../upgrading-checklist.rst:1900 +msgid "Released September, 1997." +msgstr "" + +#: ../../upgrading-checklist.rst:1902 +msgid "" +"new section \\`4.2 Daemons' including rules for ``/etc/services``, " +"``/etc/protocols``, ``/etc/rpc``, and ``/etc/inetd.conf``" +msgstr "" + +#: ../../upgrading-checklist.rst:1905 +msgid "" +"updated section about \\`Configuration files': packages may not touch " +"other packages' configuration files" +msgstr "" + +#: ../../upgrading-checklist.rst:1908 +msgid "MUAs and MTAs have to use liblockfile" +msgstr "" + +#: ../../upgrading-checklist.rst:1911 +msgid "Version 2.2.0" +msgstr "" + +#: ../../upgrading-checklist.rst:1913 +msgid "Released July, 1997." +msgstr "" + +#: ../../upgrading-checklist.rst:1915 +msgid "" +"added section 4.1 \\`Architecture specification strings': use " +"<arch>-linux where <arch> is one of the following: i386, alpha, arm, " +"m68k, powerpc, sparc." +msgstr "" + +#: ../../upgrading-checklist.rst:1919 +msgid "detailed rules for ``/usr/local``" +msgstr "" + +#: ../../upgrading-checklist.rst:1921 +msgid "user ID's" +msgstr "" + +#: ../../upgrading-checklist.rst:1923 +msgid "editor/pager policy" +msgstr "" + +#: ../../upgrading-checklist.rst:1925 +msgid "cron jobs" +msgstr "" + +#: ../../upgrading-checklist.rst:1927 +msgid "device files" +msgstr "" + +#: ../../upgrading-checklist.rst:1929 +msgid "don't install shared libraries as executable" +msgstr "" + +#: ../../upgrading-checklist.rst:1931 +msgid "app-defaults files may not be conffiles" +msgstr "" + +#: ../../upgrading-checklist.rst:1934 +msgid "Version 2.1.3" +msgstr "" + +#: ../../upgrading-checklist.rst:1936 +msgid "Released March, 1997." +msgstr "" + +#: ../../upgrading-checklist.rst:1938 +msgid "two programs with different functionality must not have the same name" +msgstr "" + +#: ../../upgrading-checklist.rst:1940 +msgid "\"Webstandard 3.0\"" +msgstr "" + +#: ../../upgrading-checklist.rst:1942 +msgid "\"Standard for Console Messages\"" +msgstr "" + +#: ../../upgrading-checklist.rst:1944 +msgid "Libraries should be compiled with ``-D_REENTRANT``" +msgstr "" + +#: ../../upgrading-checklist.rst:1946 +msgid "Libraries should be stripped with ``strip --strip-unneeded``" +msgstr "" + +#: ../../upgrading-checklist.rst:1949 +msgid "Version 2.1.2" +msgstr "" + +#: ../../upgrading-checklist.rst:1951 +msgid "Released November, 1996." +msgstr "" + +#: ../../upgrading-checklist.rst:1953 +msgid "Some changes WRT shared libraries" +msgstr "" + +#: ../../upgrading-checklist.rst:1956 +msgid "Version 2.1.1" +msgstr "" + +#: ../../upgrading-checklist.rst:1958 +msgid "Released September, 1996." +msgstr "" + +#: ../../upgrading-checklist.rst:1960 +msgid "No hard links in source packages" +msgstr "" + +#: ../../upgrading-checklist.rst:1962 +msgid "Do not use ``dpkg-divert`` or ``update-alternatives`` without consultation" +msgstr "" + +#: ../../upgrading-checklist.rst:1965 +msgid "Shared libraries must be installed stripped" +msgstr "" + +#: ../../upgrading-checklist.rst:1968 +msgid "Version 2.1.0" +msgstr "" + +#: ../../upgrading-checklist.rst:1970 +msgid "Released August, 1996." +msgstr "" + +#: ../../upgrading-checklist.rst:1972 +msgid "Upstream changelog must be installed too" +msgstr "" + |