{
    "content": [
        {
            "type": "text",
            "text": "# deb-triggers (man)\n\n## NAME\n\ndeb-triggers - package triggers\n\n## SYNOPSIS\n\ndebian/triggers, debian/binary-package.triggers, DEBIAN/triggers\n\n## DESCRIPTION\n\nA package declares its relationship to some trigger(s) by including a triggers file in its\ncontrol archive (i.e. DEBIAN/triggers during package creation).\n\n## Sections\n\n- **NAME**\n- **SYNOPSIS**\n- **DESCRIPTION**\n- **SEE ALSO**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n"
        }
    ],
    "structuredContent": {
        "command": "deb-triggers",
        "section": "",
        "mode": "man",
        "summary": "deb-triggers - package triggers",
        "synopsis": "debian/triggers, debian/binary-package.triggers, DEBIAN/triggers",
        "tldr_summary": null,
        "tldr_examples": [],
        "tldr_source": null,
        "flags": [],
        "examples": [],
        "see_also": [
            {
                "name": "dpkg-trigger",
                "section": "1",
                "url": "https://www.chedong.com/phpMan.php/man/dpkg-trigger/1/json"
            },
            {
                "name": "dpkg",
                "section": "1",
                "url": "https://www.chedong.com/phpMan.php/man/dpkg/1/json"
            }
        ],
        "section_outline": [
            {
                "name": "NAME",
                "lines": 2,
                "subsections": []
            },
            {
                "name": "SYNOPSIS",
                "lines": 2,
                "subsections": []
            },
            {
                "name": "DESCRIPTION",
                "lines": 59,
                "subsections": []
            },
            {
                "name": "SEE ALSO",
                "lines": 3,
                "subsections": []
            }
        ],
        "sections": {
            "NAME": {
                "content": "deb-triggers - package triggers\n",
                "subsections": []
            },
            "SYNOPSIS": {
                "content": "debian/triggers, debian/binary-package.triggers, DEBIAN/triggers\n",
                "subsections": []
            },
            "DESCRIPTION": {
                "content": "A package declares its relationship to some trigger(s) by including a triggers file in its\ncontrol archive (i.e. DEBIAN/triggers during package creation).\n\nThis file contains directives, one per line.  Leading and trailing whitespace and everything\nafter the first # on any line will be trimmed, and empty lines will be ignored.\n\nThe trigger control directives currently supported are:\n\ninterest trigger-name\ninterest-await trigger-name\ninterest-noawait trigger-name\nSpecifies  that  the package is interested in the named trigger.  All triggers in which a\npackage is interested must be listed using this directive in the triggers control file.\n\nThe “await” variants put the triggering package in triggers-awaited  state  depending  on\nhow  the  trigger  was  activated.   The  “noawait”  variant  does not put the triggering\npackages in triggers-awaited state, even if the triggering package  declared  an  “await”\nactivation  (either  with  an activate-await or activate directive, or by using the dpkg-\ntrigger --no-await command-line option).  The “noawait” variant should be used  when  the\nfunctionality provided by the trigger is not crucial.\n\nactivate trigger-name\nactivate-await trigger-name\nactivate-noawait trigger-name\nArranges  that  changes to this package's state will activate the specified trigger.  The\ntrigger will be activated at the start of the following  operations:  unpack,  configure,\nremove (including for the benefit of a conflicting package), purge and deconfigure.\n\nThe  “await”  variants  only  put the triggering package in triggers-awaited state if the\ninterest directive is also “await”.  The “noawait”  variant  never  puts  the  triggering\npackages  in  triggers-awaited  state.   The  “noawait”  variant  should be used when the\nfunctionality provided by the trigger is not crucial.\n\nIf this package disappears during the unpacking of another package the  trigger  will  be\nactivated  when  the  disappearance  is  noted  towards  the  end of the unpack.  Trigger\nprocessing,  and  transition  from  triggers-awaited  to  installed,   does   not   cause\nactivations.   In the case of unpack, triggers mentioned in both the old and new versions\nof the package will be activated.\n\nUnknown directives are an error which will prevent installation of the package.\n\nThe “-noawait” variants should always be favored when possible since triggering packages  are\nnot  put  in  triggers-awaited state and can thus be immediately configured without requiring\nthe processing of the trigger.  If the triggering packages are dependencies of other upgraded\npackages, it will avoid an early trigger processing run and  make  it  possible  to  run  the\ntrigger only once as one of the last steps of the upgrade.\n\nThe “-noawait” variants are supported since dpkg 1.16.1, and will lead to errors if used with\nan older dpkg.\n\nThe “-await” alias variants are supported since dpkg 1.17.21, and will lead to errors if used\nwith an older dpkg.\n\nWhen a package provides an interest-noawait directive, any activation will set the triggering\npackage  into  “noawait”  mode,  regardless  of the awaiting mode requested by the activation\n(either “await” or “noawait”).   When  a  package  provides  an  interest  or  interest-await\ndirective, any activation will set the triggering package into “await” or “noawait“ depending\non how it was activated.\n",
                "subsections": []
            },
            "SEE ALSO": {
                "content": "dpkg-trigger(1), dpkg(1), /usr/share/doc/dpkg/spec/triggers.txt.\n\n1.22.6                                       2026-05-06                              deb-triggers(5)",
                "subsections": []
            }
        }
    }
}