summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGuillem Jover <guillem@debian.org>2008-04-08 06:31:52 +0300
committerGuillem Jover <guillem@debian.org>2008-04-08 06:59:59 +0300
commitde995070a648eadd33dc6321a94c19c596149bd6 (patch)
tree68596cc957fbe5c069a0df4c41b426e9bdc12b69 /doc
parent193a7b55b45b3294a1a5a7d36a1052aff6b881ce (diff)
downloaddpkg-de995070a648eadd33dc6321a94c19c596149bd6.tar.gz
doc: Fix wrong dpkg trigger related option names
Diffstat (limited to 'doc')
-rw-r--r--doc/triggers.txt11
1 files changed, 5 insertions, 6 deletions
diff --git a/doc/triggers.txt b/doc/triggers.txt
index f71c038d6..915e8e744 100644
--- a/doc/triggers.txt
+++ b/doc/triggers.txt
@@ -364,14 +364,13 @@ package in `config-failed' or `installed'.
Note that automatic package management tools which call dpkg (like apt
and aptitude) should not attempt to configure individual packages in
state `triggers-pending' (or indeed `triggers-awaited') with dpkg
---triggers <package>... or dpkg --suppress-triggers --configure
-<package>..., or similar approaches. This might defeat dpkg's trigger
-cycle detection.
+--triggers-only <package>... or dpkg --no-triggers --configure <package>...,
+or similar approaches. This might defeat dpkg's trigger cycle detection.
A package management tool which will run dpkg --configure --pending at
-the end may use --suppress-triggers on its other dpkg runs. This
-would be more efficient as it allows more aggressive deferral (and
-hence more unification) of trigger processing.
+the end may use --no-triggers on its other dpkg runs. This would be
+more efficient as it allows more aggressive deferral (and hence more
+unification) of trigger processing.
Error handling