1dpkg-trigger(1) dpkg suite dpkg-trigger(1)
2
3
4
6 dpkg-trigger - a package trigger utility
7
9 dpkg-trigger [option...] trigger-name
10 dpkg-trigger [option...] command
11
13 dpkg-trigger is a tool to explicitly activate triggers and check for
14 its support on the running dpkg.
15
16 This can be used by maintainer scripts in complex and conditional
17 situations where the file triggers, or the declarative activate
18 triggers control file directive, are insufficiently rich. It can also
19 be used for testing and by system administrators (but note that the
20 triggers won't actually be run by dpkg-trigger).
21
22 Unrecognized trigger name syntaxes are an error for dpkg-trigger.
23
25 --check-supported
26 Check if the running dpkg supports triggers (usually called from
27 a postinst). Will exit 0 if a triggers-capable dpkg has run, or
28 1 with an error message to stderr if not. Normally, however, it
29 is better just to activate the desired trigger with
30 dpkg-trigger.
31
32 -?, --help
33 Show the usage message and exit.
34
35 --version
36 Show the version and exit.
37
39 --admindir=dir
40 Change the location of the dpkg database. The default location
41 is /var/lib/dpkg.
42
43 --by-package=package
44 Override trigger awaiter (normally set by dpkg through the
45 DPKG_MAINTSCRIPT_PACKAGE environment variable of the maintainer
46 scripts, naming the package to which the script belongs, and
47 this will be used by default).
48
49 --no-await
50 This option arranges that the calling package T (if any) need
51 not await the processing of this trigger; the interested
52 package(s) I, will not be added to T's trigger processing
53 awaited list and T's status is unchanged. T may be considered
54 installed even though I may not yet have processed the trigger.
55
56 --await
57 This option does the inverse of --no-await (since dpkg 1.17.21).
58 It is currently the default behavior.
59
60 --no-act
61 Just test, do not actually change anything.
62
64 0 The requested action was successfully performed. Or a check or
65 assertion command returned true.
66
67 1 A check or assertion command returned false.
68
69 2 Fatal or unrecoverable error due to invalid command-line usage,
70 or interactions with the system, such as accesses to the
71 database, memory allocations, etc.
72
74 DPKG_ADMINDIR
75 If set and the --admindir option has not been specified, it will
76 be used as the dpkg data directory.
77
79 dpkg(1), deb-triggers(5), /usr/share/doc/dpkg-dev/triggers.txt.gz.
80
81
82
831.18.25 2018-06-26 dpkg-trigger(1)