# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, 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-07-10 16:09+0000\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 ""

