diff options
author | Guillem Jover <guillem@debian.org> | 2011-08-17 16:44:18 +0200 |
---|---|---|
committer | Guillem Jover <guillem@debian.org> | 2011-08-20 14:46:25 +0200 |
commit | dbe742b7db83d108e1ea143f2688ca5444007ba9 (patch) | |
tree | 5210061e864c05c78fca067534cc7435c112ab4c /doc/triggers.txt | |
parent | 312253830448926152020c8ce0f7834b8452a5d9 (diff) | |
download | dpkg-dbe742b7db83d108e1ea143f2688ca5444007ba9.tar.gz |
Fix spelling errors
Found by codespell.
Diffstat (limited to 'doc/triggers.txt')
-rw-r--r-- | doc/triggers.txt | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/triggers.txt b/doc/triggers.txt index 75579fa80..2d891ff54 100644 --- a/doc/triggers.txt +++ b/doc/triggers.txt @@ -126,7 +126,7 @@ reasonable states by default. If the `postinst triggered' run fails the package goes to `config-failed', so that the trigger processing will not be attempted -again until explictly requested. +again until explicitly requested. | @@ -175,7 +175,7 @@ that T may automatically go from `triggers-awaited' to `installed'. Or to put it another way, triggered actions are considered irrelevant if the interested package I is not configured. When I's postinst is called with `configure', it must do whatever actions are necessary to -deal with any trigger activations which might have occured while it +deal with any trigger activations which might have occurred while it was not configured, just as if the package was being configured for the first time. @@ -264,7 +264,7 @@ dpkg during package unpack or removal. The pathname must be absolute. File triggers should not generally be used without mutual consent. The use of a file trigger, and the name of the trigger used, should be stated in policy, so that a package which creates a relevant file in a -maintainer script can activate the trigger explictly. +maintainer script can activate the trigger explicitly. File triggers must definitely not be used as an escalation tool in disagreements between different packages as to the desired contents of |