summaryrefslogtreecommitdiffstats
path: root/hosts/p64c-armhf-rb.debian.net/etc/munin/plugin-conf.d
diff options
context:
space:
mode:
authorJohannes 'josch' Schauer <josch@mister-muffin.de>2017-03-30 14:37:58 +0200
committerHolger Levsen <holger@layer-acht.org>2017-03-31 10:57:17 +0200
commitdd347bb5e0587fed7e6881c8cb0ed3ca60b6595b (patch)
tree024e05e4e1006df10d36aacec9c652d06400bf89 /hosts/p64c-armhf-rb.debian.net/etc/munin/plugin-conf.d
parent79c4c28f25c71ce9147530e16a11b3e7230d4b79 (diff)
downloadjenkins.debian.net-dd347bb5e0587fed7e6881c8cb0ed3ca60b6595b.tar.xz
bin/find_dpkg_trigger_cycles.sh: ignore dependencies on Essential:yes packages
The implicit dependencies of all binary packages on all Essential:yes packages cannot result in a trigger cycle for two reasons: 1. Policy §3.8 says "Since dpkg will not prevent upgrading of other packages while an `essential' package is in an unconfigured state" which implies that because triggers check the possibility to process or not triggers based on normal dpkg dependency resolution, then essential does not apply. 2. The trigger documentation in /usr/share/doc/dpkg-dev/triggers.txt.gz does not mention Essential at all and when talking about dependency satisfiability it only refers to Depends field. Signed-off-by: Mattia Rizzolo <mattia@debian.org>
Diffstat (limited to 'hosts/p64c-armhf-rb.debian.net/etc/munin/plugin-conf.d')
0 files changed, 0 insertions, 0 deletions