doc: Fix wrong dpkg trigger related option names

diff --git a/ChangeLog b/ChangeLog
index ade8a057f6a69390cdea0b19e2b1d5b2ab8771ad..5971afcef828eacf6a194334f399523e88629b32 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2008-04-08  Guillem Jover  <guillem@debian.org>
+
+       * doc/triggers.txt: Fix wrong dpkg trigger related option names.
+
 2008-04-08  Guillem Jover  <guillem@debian.org>
 
        * doc/triggers.txt: Move parts of the document into proper man pages.

diff --git a/doc/triggers.txt b/doc/triggers.txt
index f71c038d66567f8503de80c7e3945c46acaba2fb..915e8e744347f52a2a6df40bc6a291faa382df27 100644 (file)
--- 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