summaryrefslogtreecommitdiffstats
path: root/tags/u/unused-override.tag
diff options
context:
space:
mode:
Diffstat (limited to 'tags/u/unused-override.tag')
-rw-r--r--tags/u/unused-override.tag21
1 files changed, 21 insertions, 0 deletions
diff --git a/tags/u/unused-override.tag b/tags/u/unused-override.tag
new file mode 100644
index 0000000..6eab89e
--- /dev/null
+++ b/tags/u/unused-override.tag
@@ -0,0 +1,21 @@
+Tag: unused-override
+Severity: info
+Show-Always: yes
+Check: lintian
+Explanation: Your package specifies the named override but there were no
+ tags that could have been silenced by it.
+ .
+ Maybe you fixed an underlying condition but forgot to remove the
+ override. It is also possible that the Lintian maintainers fixed a
+ false positive.
+ .
+ If the override is now unused, please remove it.
+ .
+ This tag is similar to <code>mismatched-override</code> except there a
+ tag could have been silenced if the context had matched.
+ .
+ Sometimes, overrides end up not being used because a tag appears
+ only on some architectures. In that case, overrides can be equipped
+ with an architecture qualifier.
+See-Also:
+ lintian-manual 2.4.3