Bug#1110017: debian-policy: Priority should no longer be `recommended`
Control: tags -1 patch
> ACK. Patches welcome.
The patch is pasted below.
diff --git a/policy/ch-archive.rst b/policy/ch-archive.rst
index 302dc8d..3bf5abf 100644
--- a/policy/ch-archive.rst
+++ b/policy/ch-archive.rst
@@ -376,11 +376,14 @@ Priorities
----------
Each package must have a *priority* value, which is set in the metadata
-for the Debian archive and is also included in the package's control
-files (see :ref:`s-f-Priority`). This information is used
+for the Debian archive and is also included in the package's binary
+control files (see :ref:`s-f-Priority`). This information is used
to control which packages are included in standard or minimal Debian
installations.
+If the *Priority* field is not specified in the source control file, dpkg
+sets it to ``optional`` by default starting version 1.22.13.
+
Most Debian packages will have a priority of ``optional``. Priority
levels other than ``optional`` are only used for packages that should be
included by default in a standard installation of Debian.
diff --git a/policy/ch-controlfields.rst b/policy/ch-controlfields.rst
index 9f06cc9..e4390b4 100644
--- a/policy/ch-controlfields.rst
+++ b/policy/ch-controlfields.rst
@@ -116,7 +116,7 @@ The fields in the source package stanza (the first one) are:
- :ref:`Section <s-f-Section>` (recommended)
-- :ref:`Priority <s-f-Priority>` (recommended)
+- :ref:`Priority <s-f-Priority>`
- :ref:`Build-Depends et al <s-sourcebinarydeps>`
@@ -138,7 +138,7 @@ The fields in the binary package stanzas are:
- :ref:`Section <s-f-Section>` (recommended)
-- :ref:`Priority <s-f-Priority>` (recommended)
+- :ref:`Priority <s-f-Priority>`
- :ref:`Essential <s-f-Essential>`
Reply to: