man: Fix bogus description of --force-confmiss

This force option is the only one that performs its action independently
of the conffile changing or not in the new package. The description was
bogusly updated when trying to clarify the other conf force options.

Regression introduced in commit 4bcc6b8e0a587b432b145fafa642674607cddddd.

Reported-by: Sven Joachim <svenjoac@gmx.de>
Closes: #846395

1 files changed, 3 insertions, 4 deletions

diff --git a/man/dpkg.man b/man/dpkg.man
index 80e736321..abdaf0f64 100644
--- a/man/dpkg.man
+++ b/man/dpkg.man
@@ -544,9 +544,8 @@ Install, even if it conflicts with another package. This is dangerous,
 for it will usually cause overwriting of some files.
 
 \fBconfmiss\fP:
-If a conffile is missing and the version in the package did change, always
-install the missing conffile without prompting. This is dangerous, since
-it means not preserving a change (removing) made to the file.
+Always install the missing conffile without prompting. This is dangerous,
+since it means not preserving a change (removing) made to the file.
 
 \fBconfnew\fP:
 If a conffile has been modified and the version in the package did change,
@@ -571,7 +570,7 @@ that to decide the final action.
 If a conffile has been modified always offer to replace it with the
 version in the package, even if the version in the package did not
 change (since dpkg 1.15.8).
-If any of \fB\-\-force\-confmiss\fP, \fB\-\-force\-confnew\fP,
+If any of \fB\-\-force\-confnew\fP,
 \fB\-\-force\-confold\fP, or \fB\-\-force\-confdef\fP is also given,
 it will be used to decide the final action.