repeated-trigger-name
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.
For more information please consult:
- the deb-triggers(5) manual page
- Bug#698723
The tag is present in Lintian version 2.114.163.
That is the most recent version we know about.
We use semantic versions.
The patch number is a commit step indicator relative to the
2.114.0
release tag in our Git
repository.
You can find the detection logic for this version at commit f5107b6. For merge requests, please use the latest version in the Lintian check triggers.
Visibility: error