Lintian tag: repeated-trigger-name

Type: error

Description (from lintian-explain-tags)

The package repeats the same trigger. There should be no reason to do this
and it may lead to confusing results or errors.

For the same "base" type of trigger (e.g. two interest-type triggers) the
last declaration will be the effective one.

This tag is also triggered if the package has an activate trigger for
something on which it also declares an interest. The only (but rather
unlikely) reason to do this is if another package *also* declares an
interest and this package needs to activate that other package. If the
package is using it for this exact purpose, then please use a Lintian
override to state this.

Please remove any duplicate definitions.

Please refer to the deb-triggers(5) manual page and Bug#698723 for
details.

Visibility: error
Show-Always: no
Check: triggers

Affected packages

source version binary tag type tag information count
clevis 20-1 clevis-initramfs/20-1 error repeated-trigger-name update-initramfs (lines 1 3) [triggers] 8
clevis 20-1 clevis-initramfs/20-1+b1 error repeated-trigger-name update-initramfs (lines 1 3) [triggers] 1
lorene 0.0.0~cvs20161116+dfsg-1.3 liblorene-debian1t64/0.0.0~cvs20161116+dfsg-1.3+b1 error repeated-trigger-name ldconfig (lines 1 3) [triggers] 9
lorene 0.0.0~cvs20161116+dfsg-1.3 liblorene-export-debian0t64/0.0.0~cvs20161116+dfsg-1.3+b1 error repeated-trigger-name ldconfig (lines 1 3) [triggers] 9
lorene 0.0.0~cvs20161116+dfsg-1.3 liblorenef77-debian1t64/0.0.0~cvs20161116+dfsg-1.3+b1 error repeated-trigger-name ldconfig (lines 1 3) [triggers] 9