summaryrefslogtreecommitdiffstats
path: root/tags/p/possible-missing-colon-in-closes.tag
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-14 13:42:30 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-14 13:42:30 +0000
commit75808db17caf8b960b351e3408e74142f4c85aac (patch)
tree7989e9c09a4240248bf4658a22208a0a52d991c4 /tags/p/possible-missing-colon-in-closes.tag
parentInitial commit. (diff)
downloadlintian-upstream.tar.xz
lintian-upstream.zip
Adding upstream version 2.117.0.upstream/2.117.0upstream
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'tags/p/possible-missing-colon-in-closes.tag')
-rw-r--r--tags/p/possible-missing-colon-in-closes.tag7
1 files changed, 7 insertions, 0 deletions
diff --git a/tags/p/possible-missing-colon-in-closes.tag b/tags/p/possible-missing-colon-in-closes.tag
new file mode 100644
index 0000000..0844483
--- /dev/null
+++ b/tags/p/possible-missing-colon-in-closes.tag
@@ -0,0 +1,7 @@
+Tag: possible-missing-colon-in-closes
+Severity: error
+Check: debian/changelog
+Explanation: To close a bug in the Debian changelog, the word "closes" must be
+ followed by a colon. This entry looked like it was intended to close a
+ bug, but there's no colon after "closes".
+See-Also: debian-policy 4.4