@@ -2491,18 +2499,21 @@ endif
- Each paragraph consists of a series of data fields; each
- field consists of the field name, followed by a colon and
- then the data/value associated with that field. The field
- name is composed of 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
- be:
+ Each paragraph consists of a series of data fields. Each field
+ consists of the field name followed by a colon and then the
+ data/value associated with that field. The field name is
+ composed of US-ASCII characters excluding control characters,
+ space, and colon (i.e., characters in the ranges 33-57 and
+ 59-126, inclusive). Field names must not begin with the comment
+ character, #.
+
+
+
+ The field ends at the end of the line or at the end of the last
+ continuation line (see below). Horizontal whitespace (spaces
+ and tabs) may occur immediately before or after the value and is
+ ignored there; it is conventional to put a single space after
+ the colon. For example, a field might be:
Package: libc6
@@ -2696,7 +2707,7 @@ Package: libc6
This file consists of a single paragraph, possibly surrounded by
a PGP signature. The fields of that paragraph are listed below.
- Their syntax is described above, in [.
+ Their syntax is described above, in ][.
]
- Format (mandatory)
@@ -6161,11 +6172,11 @@ install -m644 debian/shlibs.package debian/package/DEBIAN/
File System Structure
- The location of all installed files and directories must
- comply with the Filesystem Hierarchy Standard (FHS),
- version 2.3, with the exceptions noted below, and except
- where doing so would violate other terms of Debian
- Policy. The following exceptions to the FHS apply:
+ The location of all files and directories must comply with the
+ Filesystem Hierarchy Standard (FHS), version 2.3, with the
+ exceptions noted below, and except where doing so would
+ violate other terms of Debian Policy. The following
+ exceptions to the FHS apply:
-
@@ -6246,6 +6257,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
@@ -6388,6 +6418,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.
+
+
@@ -6762,15 +6815,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.
]
@@ -7919,10 +7971,12 @@ fname () {
You may wish to restrict your script to SUSv3 features plus the
above set when possible so that it may use /bin/sh
- as its interpreter. If your script works with dash
- (originally called ash), it probably complies with
- the above requirements, but if you are in doubt, use
- /bin/bash.
+ as its interpreter. Checking your script
+ with checkbashisms from
+ the devscripts package or running your script
+ with posh may help uncover violations of the above
+ requirements. If in doubt whether a script complies with these
+ requirements, use /bin/bash.
@@ -9872,7 +9926,27 @@ END-INFO-DIR-ENTRY
You should not use the copyright file as a general README
file. If your package has such a file it should be
installed in /usr/share/doc/package/README or
- README.Debian or some other appropriate place.
+ README.Debian or some other appropriate place.
+
+
+
+ Machine-readable copyright information
+
+
+ A specification for a standard, machine-readable format
+ for debian/copyright files is maintained as part
+ of the debian-policy package. This
+ document may be found in the copyright-format
+ files in the debian-policy package. It is
+ also available from the Debian web mirrors at
+ .
+
+
+
+ Use of this format is optional.
+
+