X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=policy.sgml;h=8100da082bd123ab85cf97a6788b5cd656b99cb4;hb=6d5f4e0d2c088969b86863cdd0033c917054c207;hp=85e406256ed2264cd7dcb6cb9804b00157572ad9;hpb=1f73071f581d5e268835a278a7a74a4234386735;p=debian%2Fdebian-policy.git
diff --git a/policy.sgml b/policy.sgml
index 85e4062..8100da0 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -15,7 +15,7 @@
This manual describes the policy requirements for the Debian
- GNU/Linux distribution. This includes the structure and
+ 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.
@@ -50,7 +50,7 @@
A copy of the GNU General Public License is available as
- /usr/share/common-licenses/GPL in the Debian GNU/Linux
+ /usr/share/common-licenses/GPL in the Debian
distribution or on the World Wide Web at
. You can also
@@ -68,7 +68,7 @@
Scope
This manual describes the policy requirements for the Debian
- GNU/Linux distribution. This includes the structure and
+ 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
@@ -218,12 +218,13 @@
The actual editing is done by a group of maintainers that have
no editorial powers. These are the current maintainers:
-
- - Julian Gilbey
- - Branden Robinson
- - Josip Rodin
- - Manoj Srivastava
-
+
+ - Russ Allbery
+ - Bill Allombert
+ - Andrew McMillan
+ - Manoj Srivastava
+ - Colin Watson
+
@@ -257,7 +258,6 @@
-
@@ -314,7 +314,7 @@
The Debian Archive
- The Debian GNU/Linux system is maintained and distributed as a
+ 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
@@ -348,8 +348,7 @@
- The main archive area forms the Debian GNU/Linux
- distribution.
+ The main archive area forms the Debian distribution.
@@ -465,6 +464,20 @@
The main archive area
+
+ 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
+ See for
+ more about what we mean by free software.
+ .
+
+
Every package in main must comply with the DFSG
(Debian Free Software Guidelines).
@@ -474,11 +487,11 @@
In addition, the packages in main
-
- must not require a package outside of main
- for compilation or execution (thus, the package must
- not declare a "Depends", "Recommends", or
- "Build-Depends" relationship on a non-main
- package),
+ 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", or "Build-Depends-Indep"
+ relationship on a non-main package),
-
must not be so buggy that we refuse to support them,
@@ -496,6 +509,13 @@
The contrib archive area
+
+ 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.
+
+
Every package in contrib must comply with the DFSG.
@@ -514,7 +534,6 @@
-
Examples of packages which would be included in
contrib are:
@@ -536,6 +555,15 @@
The non-free archive area
+
+ 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.
+
+
Packages must be placed in non-free if they are
not compliant with the DFSG or are encumbered by patents
@@ -680,12 +708,13 @@
list of sections. At present, they are:
admin, cli-mono, comm, database,
devel, debug, doc, editors,
- electronics, embedded, fonts,
- games, gnome, graphics, gnu-r,
- gnustep, hamradio, haskell,
- httpd, interpreters, java, kde,
- kernel, libs, libdevel, lisp,
- localization, mail, math, misc,
+ education, electronics, embedded,
+ fonts, games, gnome, graphics,
+ gnu-r, gnustep, hamradio, haskell,
+ httpd, interpreters, introspection,
+ java, kde, kernel, libs,
+ libdevel, lisp, localization,
+ mail, math, metapackages, misc,
net, news, ocaml, oldlibs,
otherosfs, perl, php, python,
ruby, science, shells, sound,
@@ -796,7 +825,7 @@
Binary packages
- The Debian GNU/Linux distribution is based on the Debian
+ 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.
@@ -907,23 +936,40 @@
-
+
The maintainer of a package
- Every package must have a Debian maintainer (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 ensuring that
- the package is placed in the appropriate distributions.
-
-
-
- The maintainer must be specified in the
- Maintainer control field with their correct name
- and a working email address. If one person maintains
- several packages, they should try to avoid having
- different forms of their name and email address in
+ 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.
+
+
+
+ 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.
+ A sample implementation of such a whitelist written for the
+ Mailman mailing list management software is used for mailing
+ lists hosted by alioth.debian.org.
+
+ 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.
@@ -933,15 +979,23 @@
- If the maintainer of a package quits from the Debian
- project, "Debian QA Group"
- packages@qa.debian.org takes over the
- maintainer-ship of the package until someone else
- volunteers for that task. These packages are called
- orphaned packages.
- The detailed procedure for doing this gracefully can
- be found in the Debian Developer's Reference,
- see [.
+ 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 ][ for the
+ syntax of that field.
+ ]
+
+
+ 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.
+ The detailed procedure for gracefully orphaning a package can
+ be found in the Debian Developer's Reference
+ (see [).
]
@@ -1036,7 +1090,7 @@
-
+
Dependencies
@@ -1079,10 +1133,10 @@
- Sometimes, a package requires another package to be installed
- and configured before it can be installed. In this
- case, you must specify a Pre-Depends entry for
- the package.
+ 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.
@@ -1143,7 +1197,7 @@
The base system is a minimum subset of the Debian
- GNU/Linux system that is installed before everything else
+ 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.
@@ -1801,23 +1855,26 @@
identical behavior.
+
+ The following targets are required and must be implemented
+ by debian/rules: clean, binary,
+ binary-arch, binary-indep, and build.
+ These are the targets called by dpkg-buildpackage.
+
+
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. At a minimum, required targets are the
- ones called by dpkg-buildpackage, namely,
- clean, binary, binary-arch,
- binary-indep, and build. It also follows
- that any target that these targets depend on must also be
+ 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.
- The targets are as follows (required unless stated otherwise):
+ The targets are as follows:
- build
+ build (required)
-
The build target should perform all the
@@ -1928,8 +1985,8 @@
- binary, binary-arch,
- binary-indep
+ binary (required), binary-arch
+ (required), binary-indep (required)
-
@@ -1977,7 +2034,7 @@
- clean
+ clean (required)
-
This must undo any effects that the build
@@ -2059,14 +2116,21 @@
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 machine (the machine type
- we are building on) as well as for the host machine (the
- machine type we are building for). Here is a list of
- supported make variables:
+ 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. 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).
+
+
+
+ Here is a list of supported make variables:
-
DEB_*_ARCH (the Debian architecture)
@@ -2090,8 +2154,8 @@
DEB_*_GNU_TYPE)
where * is either BUILD for specification of
- the build machine or HOST for specification of the
- host machine.
+ the build architecture or HOST for specification of the
+ host architecture.
@@ -2415,19 +2479,26 @@ endif
fields
The paragraphs are also sometimes referred to as stanzas.
.
- The paragraphs are separated by blank lines. Some control
+ 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.)
+ refer to binary packages generated from the source.) The
+ ordering of the paragraphs in control files is significant.
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. It ends at
- the end of the (logical) line. Horizontal whitespace
+ then the data/value associated with that field. The field
+ name is composed of printable ASCII characters (i.e.,
+ characters that have values between 33 and 126, inclusive)
+ except colon and must not with a begin with #. 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
@@ -2445,21 +2516,51 @@ Package: libc6
- Many fields' values may span several lines; in this case
- each continuation line must start with a space or a tab.
- Any trailing spaces or tabs at the end of individual
- lines of a field value are ignored.
+ There are three types of fields:
+
+ simple
+ -
+ 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.
+
+ folded
+ -
+ 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.
+ 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.
+
+
+ multiline
+ -
+ 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.
+
+
- In fields where it is specified that lines may not wrap,
- only a single line of data is allowed and whitespace is not
- significant in a field body. Whitespace must not appear
+ 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.
+
+ The presence and purpose of a field, and the syntax of its
+ value may differ between types of control files.
+
+
Field names are not case-sensitive, but it is usual to
capitalize the field names using mixed case as shown below.
@@ -2468,9 +2569,17 @@ Package: libc6
- Blank lines, or lines consisting only of spaces and tabs,
- are not allowed within field values or between fields - that
- would mean a new paragraph.
+ Paragraph separators (empty lines) and lines consisting only of
+ spaces and tabs are not allowed within field values or between
+ fields. Empty lines in field values are usually escaped by
+ representing them by a space followed by a dot.
+
+
+
+ Lines starting with # without any preceding whitespace are comments
+ 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.
@@ -2501,6 +2610,7 @@ Package: libc6
- Source (mandatory)
- Maintainer (mandatory)
- Uploaders
+ - DM-Upload-Allowed
- Section (recommended)
- Priority (recommended)
- Build-Depends et al
@@ -2535,8 +2645,8 @@ Package: libc6
.changes file to accompany the upload, and by
dpkg-source when it creates the
.dsc source control file as part of a source
- archive. Many fields are permitted to span multiple lines in
- debian/control but not in any other control
+ 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.
@@ -2549,16 +2659,6 @@ Package: libc6
when they generate output control files.
See [ for details.
]
-
-
- In addition to the control file syntax described above, this file may also contain
- comment lines starting with # without any preceding
- whitespace. All such lines are ignored, even in the middle of
- continuation lines for a multiline field, and do not end a
- multiline field.
-
-
@@ -2606,6 +2706,7 @@ Package: libc6
- Version (mandatory)
- Maintainer (mandatory)
- Uploaders
+ - DM-Upload-Allowed
- Homepage
- Standards-Version (recommended)
- Build-Depends et al
@@ -2616,7 +2717,7 @@ Package: libc6
- The source package control file is generated by
+ 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
@@ -2727,28 +2828,36 @@ Package: libc6
putting the name in round brackets and moving it to the
end, and bringing the email address forward).
+
+
+ See [ for additional requirements and
+ information about package maintainers.
+ ]
Uploaders
- List of the names and email addresses of co-maintainers of
- the package, if any. If the package has other maintainers
- beside the one named in the
- Maintainer field, 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. This is an optional
- field.
+ 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 Maintainer
+ field, 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.
+
+
+
+ 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.
- Any parser that interprets the Uploaders field in
- debian/control must permit it to span multiple
- lines. Line breaks in an Uploaders field that spans multiple
- lines are not significant and the semantics of the field are
- the same as if the line breaks had not been present.
+ The Uploaders field in debian/control can be folded.
@@ -2865,34 +2974,42 @@ Package: libc6
- In the source package control file .dsc, this
- field may contain either the architecture
- wildcard any or a list of architectures and
- architecture wildcards separated by spaces. If a list is
- given, it may include (or consist solely of) the special
+ 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.
+
+
+
+ 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 source package control
+ 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.
- Specifying any indicates that the source package
+ 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 either be specific to whatever the current build
- architecture is or will be architecture-independent.
+ will be specific to whatever the current build architecture is.
Specifying only all indicates that the source package
- will only build architecture-independent packages. If this is
- the case, all must be used rather than any;
- any implies that the source package will build at
- least one architecture-dependent package.
+ will only build architecture-independent packages.
+
+
+
+ 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-dependant package and one architecture-independent
+ package.
@@ -2928,7 +3045,7 @@ Package: libc6
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 main source control data file.
+ paragraph of a source package control file.
@@ -3164,7 +3281,8 @@ Package: libc6
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. The field's format is as follows:
+ long description. It is a multiline field with the following
+ format:
@@ -3184,6 +3302,7 @@ Package: libc6
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.
-
@@ -3194,7 +3313,8 @@ Package: libc6
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).
+ indenting work correctly, for example). The line must
+ contain at least one non-whitespace character.
-
@@ -3228,8 +3348,8 @@ Package: libc6
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. The content of the field is expressed as
- continuation lines, one line per package. Each line 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.
@@ -3365,7 +3485,7 @@ Package: libc6
Changes
- This field contains the human-readable changes data, describing
+ This multiline field contains the human-readable changes data, describing
the differences between the last version and the current one.
@@ -3403,7 +3523,7 @@ Package: libc6
Binary
- This field is a list of binary packages. Its syntax and
+ This folded field is a list of binary packages. Its syntax and
meaning varies depending on the control file in which it
appears.
@@ -3413,7 +3533,7 @@ Package: libc6
packages which a source package can produce, separated by
commas
A space after each comma is conventional.
- . It may span multiple lines. The source package
+ . 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
@@ -3423,7 +3543,7 @@ Package: libc6
When it appears in a .changes file, it lists the
names of the binary packages being uploaded, separated by
- whitespace (not commas). It may span multiple lines.
+ whitespace (not commas).
@@ -3546,7 +3666,7 @@ Files:
and Checksums-Sha256
- These fields contain a list of files with a checksum and size
+ 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
@@ -3585,6 +3705,21 @@ Checksums-Sha256:
must match the list of files in the Files field.
+
+
+ DM-Upload-Allowed
+
+
+ The most recent version of a package uploaded to unstable or
+ experimental must include the field DM-Upload-Allowed:
+ yes in the source section of its source control file for
+ the Debian archive to accept uploads signed with a key in the
+ Debian Maintainer keyring. See the General
+ Resolution for more
+ details.
+
+
@@ -3594,7 +3729,7 @@ Checksums-Sha256:
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
- source package control files or upload control files.
+ Debian source control files or upload control files.
@@ -3611,7 +3746,7 @@ Checksums-Sha256:
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 source package control
+ letter S is used in Debian source control
files and where C is used in upload control
(.changes) files.
@@ -3622,7 +3757,7 @@ Checksums-Sha256:
XBS-Comment: I stand between the candle and the star.
- then the binary and source package control files will contain the
+ then the binary and Debian source control files will contain the
field
Comment: I stand between the candle and the star.
@@ -3683,7 +3818,7 @@ Checksums-Sha256:
Broadly speaking the preinst is called before
- (a particular version of) a package is installed, and the
+ (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.
@@ -3767,111 +3902,200 @@ Checksums-Sha256:
-
- -
- new-preinst install
-
- -
- new-preinst install old-version
-
- -
- new-preinst upgrade old-version
-
- -
- old-preinst abort-upgrade
- new-version
-
-
+ 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.
+
-
- -
- postinst configure
- most-recently-configured-version
-
- -
- old-postinst abort-upgrade
- new-version
-
- -
- conflictor's-postinst abort-remove
- in-favour package
- new-version
-
+ The preinst script may be called in the following
+ ways:
+
+ new-preinst install
+ new-preinst install
+ old-version
+ new-preinst upgrade
+ old-version
-
- postinst abort-remove
+ 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.
+
+ old-preinst abort-upgrade
+ new-version
-
- deconfigured's-postinst
- abort-deconfigure in-favour
- failed-install-package version
- [removing conflicting-package
- version]
+ 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.
+ This can happen if the new version of the package no
+ longer pre-depends on a package that had been partially
+ upgraded.
+
-
+
+
-
- -
- prerm remove
-
- -
- old-prerm upgrade
- new-version
-
- -
- new-prerm failed-upgrade
- old-version
-
+ The postinst script may be called in the following
+ ways:
+
+ postinst configure
+ most-recently-configured-version
-
- conflictor's-prerm remove
- in-favour package
- new-version
+ 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
[.
]
+
+ old-postinst abort-upgrade
+ new-version
+ conflictor's-postinst abort-remove
+ in-favour package
+ new-version
+ postinst abort-remove
+ deconfigured's-postinst
+ abort-deconfigure in-favour
+ failed-install-package version
+ [removing conflicting-package
+ version]
-
- deconfigured's-prerm deconfigure
- in-favour package-being-installed
- version [removing
- conflicting-package
- version]
+ 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.
+ 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".
+
+ 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.
-
+
+
-
- -
- postrm remove
-
- -
- postrm purge
-
- -
- old-postrm upgrade
- new-version
-
+ The prerm script may be called in the following
+ ways:
+
+ prerm remove
+ old-prerm
+ upgradenew-version
+ conflictor's-prerm remove
+ in-favour package
+ new-version
+ deconfigured's-prerm deconfigure
+ in-favour package-being-installed
+ version [removing
+ conflicting-package version]
-
- new-postrm failed-upgrade
- old-version
+ 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.
+
+ new-prerm failed-upgrade
+ old-version
-
- new-postrm abort-install
+ 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.
+
+
+
+
+ The postrm script may be called in the following
+ ways:
+
+ postrm remove
+ postrm purge
+ old-postrm upgrade
+ new-version
+ disappearer's-postrm disappear
+ overwriter overwriter-version
-
- new-postrm abort-install
- old-version
+ 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.
+ This is often done by checking whether the command or
+ facility the postrm intends to call is
+ available before calling it. For example:
+
+if [ "$1" = purge ] && [ -e /usr/share/debconf/confmodule ]; then
+ . /usr/share/debconf/confmodule
+ db_purge
+fi
+
+ in postrm purges the debconf
+ configuration for the package
+ if debconf is installed.
+
+
+ new-postrm failed-upgrade
+ old-version
-
- new-postrm abort-upgrade
- old-version
+ 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.
+
+ new-postrm abort-install
+ new-postrm abort-install
+ old-version
+ new-postrm abort-upgrade
+ old-version
-
- disappearer's-postrm disappear
- overwriter
- overwriter-version
+ Called before unpacking the new package as part of the
+ error handling of preinst failures. May assume
+ the same state as preinst can assume.
-
+
-
+
Details of unpack phase of installation or upgrade
@@ -4073,7 +4297,7 @@ Checksums-Sha256:
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 installed which overwrites a file from another
+ is unpacked which overwrites a file from another
package, and is then removed again.
Part of the problem is due to what is arguably a
bug in dpkg.
@@ -4209,7 +4433,7 @@ Checksums-Sha256:
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 installed have already
+ 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).
@@ -4380,13 +4604,13 @@ Checksums-Sha256:
specification subject to the rules in [, and must appear where it's necessary to
disambiguate; it is not otherwise significant. All of the
- relationship fields may span multiple lines. For
+ 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 wrapping a relationship field, it
+ 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.
]
@@ -4404,7 +4628,8 @@ Depends: libc6 (>= 2.2.1), exim | mail-transport-agent
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 list of Debian architecture names
+ The brackets enclose a non-empty list of Debian architecture names
+ in the format described in [,
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.)
@@ -4472,7 +4697,8 @@ Build-Depends: foo [!i386] | bar [!amd64]
]
Relationships may also be restricted to a certain set of
- architectures using architecture wildcards. The syntax for
+ architectures using architecture wildcards in the format
+ described in [. The syntax for
declaring such restrictions is the same as declaring
restrictions using a certain set of architectures without
architecture wildcards. For example:
@@ -4549,31 +4775,40 @@ Build-Depends: foo [linux-any], bar [any-i386], baz [!linux-any]
]
- For this reason packages in an installation run are usually
- all unpacked first and all configured later; this gives
- later versions of packages with dependencies on later
- versions of other packages the opportunity to have their
- dependencies satisfied.
+ 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.
+
+ 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.
+
-
- In case of circular dependencies, since installation or
- removal order honoring the dependency order can't be
- established, dependency loops are broken at some point
- (based on rules below), and some packages may not be able to
- rely on their dependencies being present when being
- installed or removed, 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, so as to ensure that
- all postinst scripts run with the dependencies properly
- configured if this is possible. Otherwise the breaking point
- is arbitrary.
-
-
- The Depends field thus allows package maintainers
- to impose an order in which packages should be configured.
+ 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.
@@ -4585,7 +4820,8 @@ Build-Depends: foo [linux-any], bar [any-i386], baz [!linux-any]
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.
+ configured (unless there is a circular dependency as
+ described above).
@@ -4597,12 +4833,31 @@ Build-Depends: foo [linux-any], bar [any-i386], baz [!linux-any]
The Depends field should also be used if the
- postinst, prerm or
- postrm scripts require the package to be
- present in order to run. Note, however, that the
- postrm cannot rely on any non-essential
- packages to be present during the purge
- phase.
+ 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.
+
+
+
+ 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.
+
Recommends
@@ -4661,11 +4916,21 @@ Build-Depends: foo [linux-any], bar [any-i386], baz [!linux-any]
- When the package declaring a pre-dependency is about
- to be configured, the pre-dependency will be
- treated as a normal Depends, that is, it will
- be considered satisfied only if the depended-on
- package has been correctly configured.
+ 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.
+
+
+
+ Pre-Depends are also required if the
+ preinst script depends on the named package.
+ It is best to avoid this situation if possible.
@@ -4676,10 +4941,10 @@ Build-Depends: foo [linux-any], bar [any-i386], baz [!linux-any]
- Pre-Depends are also required if the
- preinst script depends on the named
- package. It is best to avoid this situation if
- possible.
+ 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 [.
]
@@ -4705,7 +4970,7 @@ Build-Depends: foo [linux-any], bar [any-i386], baz [!linux-any]
When one binary package declares that it breaks another,
dpkg will refuse to allow the package which
- declares Breaks be installed unless the broken
+ declares Breaks to be unpacked unless the broken
package is deconfigured first, and it will refuse to
allow the broken package to be reconfigured.
@@ -4756,18 +5021,18 @@ Build-Depends: foo [linux-any], bar [any-i386], baz [!linux-any]
Conflicting binary packages - Conflicts
- When one binary package declares a conflict with another
- using a Conflicts field, dpkg will
- refuse to allow them to be installed on the system at the
- same time. This is a stronger restriction than Breaks,
- which just prevents both packages from being configured at the
- same time. Conflicting packages cannot be unpacked on the
- system at the same time.
+ 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.
- If one package is to be installed, the other must be removed
- first. If the package being installed is marked as replacing
+ If one package is to be unpacked, the other must be removed
+ first. If the package being unpacked is marked as replacing
(see [, 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
@@ -4816,7 +5081,7 @@ Build-Depends: foo [linux-any], bar [any-i386], baz [!linux-any]
]- when two packages provide the same file and will
continue to do so,
- in conjunction with Provides when only one
- package providing a given virtual facility may be installed
+ package providing a given virtual facility may be unpacked
at a time (see
[),]
- in other cases where one must prevent simultaneous
installation of two packages for reasons that are ongoing
@@ -5048,7 +5313,7 @@ Provides: mail-transport-agent
Conflicts: mail-transport-agent
Replaces: mail-transport-agent
- ensuring that only one MTA can be installed at any one
+ ensuring that only one MTA can be unpacked at any one
time. See
[ for more information about this
example.
@@ -5319,12 +5584,9 @@ Replaces: mail-transport-agent
library directories of the dynamic linker (which are currently
/usr/lib and /lib) or a directory that is
listed in /etc/ld.so.conf
- These are currently
- ]
- - /usr/local/lib
- - /usr/lib/libc5-compat
- - /lib/libc5-compat
-
+ These are currently /usr/local/lib plus
+ directories under /lib and /usr/lib
+ matching the multiarch triplet for the system architecture.
must use ldconfig to update the shared library
system.
@@ -5347,7 +5609,7 @@ Replaces: mail-transport-agent
During install or upgrade, the preinst is called before
- the new files are installed, so calling "ldconfig" is
+ the new files are unpacked, so calling "ldconfig" is
pointless. The preinst of an existing package can also be
called if an upgrade fails. However, this happens during
the critical time when a shared libs may exist on-disk
@@ -5492,7 +5754,7 @@ Replaces: mail-transport-agent
[) 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 installed).
+ filename clash if both were unpacked).
]
@@ -5937,13 +6199,13 @@ install -m644 debian/shlibs.package debian/package/DEBIAN/
/lib/triplet and
/usr/lib/triplet, where
triplet is the value returned by
- dpkg-architecture -qDEB_HOST_GNU_TYPE for the
+ 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/i486-linux-gnu.
+ libraries to /usr/lib/i386-linux-gnu.
This is necessary in order to reserve the directories for
use in cross-installation of library packages from other
@@ -5984,6 +6246,25 @@ install -m644 debian/shlibs.package debian/package/DEBIAN/
symlinked there, is relaxed to a recommendation.
+ -
+
+ The additional directory /run in the root
+ file system is allowed. /run
+ replaces /var/run, and the
+ subdirectory /run/lock
+ replaces /var/lock, with
+ the /var directories replaced by symlinks
+ for backwards compatibility. /run
+ and /run/lock must follow all of the
+ requirements in the FHS for /var/run
+ and /var/lock, respectively, such as file
+ naming conventions, file format requirements, or the
+ requirement that files be cleared during the boot
+ process. Files and directories residing
+ in /run should be stored on a temporary
+ file system.
+
+
-
The following directories in the root filesystem are
@@ -5993,9 +6274,21 @@ install -m644 debian/shlibs.package debian/package/DEBIAN/
to get access to kernel information.
+ -
+
+ On GNU/Hurd systems, the following additional
+ directories are allowed in the root
+ filesystem: /hurd
+ and /servers.
+ These directories are used to store translators and as
+ a set of standard names for mount points,
+ respectively.
+
+
+
-
+
The version of this document referred here can be
found in the debian-policy package or on package debian/package/DEBIAN/
For example, the emacsen-common package could
contain something like
-if [ ! -e /usr/local/share/emacs ]
-then
- if mkdir /usr/local/share/emacs 2>/dev/null
- then
- chown root:staff /usr/local/share/emacs
- chmod 2775 /usr/local/share/emacs
+if [ ! -e /usr/local/share/emacs ]; then
+ if mkdir /usr/local/share/emacs 2>/dev/null; then
+ if chown root:staff /usr/local/share/emacs; then
+ chmod 2775 /usr/local/share/emacs || true
+ fi
fi
fi
@@ -6115,6 +6407,29 @@ rmdir /usr/local/share/emacs 2>/dev/null || true
though the spool may still be physically located there.
+
+
+ /run and /run/lock
+
+
+ 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 [
+ for more information.
+ ]
+
+
+ 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.
+
+
@@ -6489,15 +6804,14 @@ test -f program-executed-later-in-script || exit 0
- /var/run and /var/lock may be mounted
- as temporary filesystems
- For example, using the RAMRUN and RAMLOCK
- options in /etc/default/rcS.
- , so the init.d scripts must handle this
- correctly. This will typically amount to creating any required
- subdirectories dynamically when the init.d script
- is run, rather than including them in the package and relying on
- dpkg to create them.
+ 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 [ for more information.
]
@@ -6866,18 +7180,20 @@ Reloading description configuration...done.
-
+
Cron jobs
Packages must not modify the configuration file
/etc/crontab, and they must not modify the files in
- /var/spool/cron/crontabs.
+ /var/spool/cron/crontabs.
+
- If a package wants to install a job that has to be executed
- via cron, it should place a file with the name of the
- package in one or more of the following directories:
+ If a package wants to install a job that has to be executed via
+ cron, it should place a file named as specified
+ in [ into one or more of the following
+ directories:
/etc/cron.hourly
/etc/cron.daily
@@ -6887,7 +7203,8 @@ Reloading description configuration...done.
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.]
+ /etc/crontab.
+
All files installed in any of these directories must be
@@ -6898,15 +7215,18 @@ Reloading description configuration...done.
If a certain job has to be executed at some other frequency or
- at a specific time, the package should install a file
- /etc/cron.d/package. This file uses the
- same syntax as /etc/crontab and is processed by
- cron automatically. The file must also be
+ at a specific time, the package should install a file in
+ /etc/cron.d with a name as specified
+ in [. 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.)]
+ running.)
+
+
Unlike crontab files described in the IEEE Std
1003.1-2008 (POSIX.1) available from
@@ -6949,6 +7269,30 @@ Reloading description configuration...done.
execute scripts in
/etc/cron.{hourly,daily,weekly,monthly}.
+
+
+ Cron job file names
+
+
+ The file name of a cron job file should normally match the
+ name of the package from which it comes.
+
+
+
+ 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.
+
+
+
+ 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.
+
+
@@ -7224,9 +7582,8 @@ exec /usr/lib/foo/foo "$@"
package that provides online documentation (other than just
manual pages) to register these documents with
doc-base by installing a
- doc-base control file via the
- doc-base control file in
+ /usr/share/doc-base/.
Please refer to the documentation that comes with the
@@ -7589,7 +7946,7 @@ fname () {
- 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.
+ kill above, 13 (SIGPIPE) must be allowed.
If a shell script requires non-SUSv3 features from the shell
@@ -7645,11 +8002,23 @@ fname () {
Symbolic links
- In general, symbolic links within a top-level directory
- should be relative, and symbolic links pointing from one
- top-level directory into another should be absolute. (A
- top-level directory is a sub-directory of the root
- directory /.)
+ 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.
+ 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.
+
@@ -7902,22 +8271,6 @@ ln -fs ../sbin/sendmail debian/tmp/usr/bin/runq
Sharing configuration files
-
- Packages which specify the same file as a
- conffile must be tagged as conflicting
- with each other. (This is an instance of the general rule
- about not sharing files. Note that neither alternatives
- nor diversions are likely to be appropriate in this case;
- in particular, dpkg does not handle diverted
- conffiles well.)
-
-
-
- The maintainer scripts must not alter a conffile
- of any package, including the one the scripts
- belong to.
-
-
If two or more packages use the same configuration file
and it is reasonable for both to be installed at the same
@@ -7967,6 +8320,34 @@ ln -fs ../sbin/sendmail debian/tmp/usr/bin/runq
and which manages the shared configuration files. (The
sgml-base package is a good example.)
+
+
+ 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
+ conffiles well.
+
+
+
+ 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.
+
+
+
+ The maintainer scripts must not alter a conffile
+ of any package, including the one the scripts
+ belong to.
+
@@ -8838,9 +9219,9 @@ name ["syshostname"]:
-
If the window manager complies with ,
- written by the , add 40 points.
@@ -9108,41 +9489,6 @@ name ["syshostname"]:
policy (such as for [).
]
-
-
- The OSF/Motif and OpenMotif libraries
-
-
- Programs that require the non-DFSG-compliant OSF/Motif or
- OpenMotif libraries
- OSF/Motif and OpenMotif are collectively referred to as
- "Motif" in this policy document.
-
- should be compiled against and tested with LessTif (a free
- re-implementation of Motif) instead. If the maintainer
- judges that the program or programs do not work
- sufficiently well with LessTif to be distributed and
- supported, but do so when compiled against Motif, then two
- versions of the package should be created; one linked
- statically against Motif and with -smotif
- appended to the package name, and one linked dynamically
- against Motif and with -dmotif appended to the
- package name.
-
-
-
- Both Motif-linked versions are dependent
- upon non-DFSG-compliant software and thus cannot be
- uploaded to the main distribution; if the
- software is itself DFSG-compliant it may be uploaded to
- the contrib distribution. While known existing
- versions of Motif permit unlimited redistribution of
- binaries linked against the library (whether statically or
- dynamically), it is the package maintainer's
- responsibility to determine whether this is permitted by
- the license of the copy of Motif in their possession.
-
-
@@ -9255,13 +9601,13 @@ name ["syshostname"]:
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.
- It is not very hard to write a man page. See the
+ It is not very hard to write a man page. See the
,
- , the examples
- created by debmake or dh_make,
- the helper program help2man, or the
- directory /usr/share/doc/man-db/examples.
+ , the examples created
+ by dh_make, the helper
+ program help2man, or the
+ directory /usr/share/doc/man-db/examples.
@@ -9507,16 +9853,14 @@ END-INFO-DIR-ENTRY
In addition, the copyright file must say where the upstream
- sources (if any) were obtained. It should name the original
- authors of the package and the Debian maintainer(s) who were
- involved with its creation.
+ sources (if any) were obtained, and should name the original
+ authors.
Packages in the contrib or non-free archive
areas should state in the copyright file that the package is not
- part of the Debian GNU/Linux distribution and briefly explain
- why.
+ part of the Debian distribution and briefly explain why.
@@ -9529,8 +9873,8 @@ END-INFO-DIR-ENTRY
/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 copyrights must be extractable by
+ first package Depends on the second. These rules are important
+ because copyright files must be extractable by
mechanical means.
@@ -9687,9 +10031,8 @@ END-INFO-DIR-ENTRY
dpkg is a suite of programs for creating binary
package files and installing and removing them on Unix
systems.
- dpkg is targeted primarily at Debian
- GNU/Linux, but may work on or be ported to other
- systems.
+ dpkg is targeted primarily at Debian, but may
+ work on or be ported to other systems.
@@ -9734,13 +10077,10 @@ END-INFO-DIR-ENTRY
- The Debian version of the FSF's GNU hello program is provided
- as an example for people wishing to create Debian
- packages. The Debian debmake package is
- recommended as a very helpful tool in creating and maintaining
- Debian packages. However, while the tools and examples are
- helpful, they do not replace the need to read and follow the
- Policy and Programmer's Manual.
+ 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.
@@ -9814,7 +10154,7 @@ END-INFO-DIR-ENTRY
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 installed.
+ by dpkg when the package is unpacked.
@@ -11029,7 +11369,7 @@ END-INFO-DIR-ENTRY
dpkg-divert --package smailwrapper --remove --rename \
--divert /usr/sbin/smail.real /usr/sbin/smail
fi
- where 1.02-2 is the version at which the
+ 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
@@ -11050,4 +11390,4 @@ END-INFO-DIR-ENTRY
-
+