Use the "Failed-Config" state instead of the synonymous halfconfigured

These terms are synonyms. dpkg and dselect use halfconfigured
internally and Failed-config when talking to the user. This patch
ensures that policy uses the same term as dpkg does when talking to
the user ("Failed-Config") for consistency.

Signed-off-by: Manoj Srivastava <srivasta@debian.org>

diff --git a/policy.sgml b/policy.sgml
index 042e82f05f0d0fb700211dc2fef44cc8966d98bf..8bfd563f3b82ee7098ffcf700c3aef463fca99b3 100644 (file)
--- a/policy.sgml
+++ b/policy.sgml
@@ -4417,12 +4417,12 @@ Build-Depends: foo [!i386] | bar [!amd64]
                be <em>unpacked</em> the pre-dependency can be
                satisfied if the depended-on package is either fully
                configured, <em>or even if</em> the depended-on
-               package(s) are only unpacked or half-configured,
-               provided that they have been configured correctly at
-               some point in the past (and not removed or partially
-               removed since).  In this case, both the
+               package(s) are only unpacked or in the "Failed-Config"
+               state, provided that they have been configured
+               correctly at some point in the past (and not removed
+               or partially removed since).  In this case, both the
                previously-configured and currently unpacked or
-               half-configured versions must satisfy any version
+               "Failed-Config" versions must satisfy any version
                clause in the <tt>Pre-Depends</tt> field.
              </p>