summaryrefslogtreecommitdiffstats
path: root/tags/v/version-refers-to-distribution.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/v/version-refers-to-distribution.tag
parentInitial commit. (diff)
downloadlintian-75808db17caf8b960b351e3408e74142f4c85aac.tar.xz
lintian-75808db17caf8b960b351e3408e74142f4c85aac.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/v/version-refers-to-distribution.tag')
-rw-r--r--tags/v/version-refers-to-distribution.tag14
1 files changed, 14 insertions, 0 deletions
diff --git a/tags/v/version-refers-to-distribution.tag b/tags/v/version-refers-to-distribution.tag
new file mode 100644
index 0000000..79d6cc3
--- /dev/null
+++ b/tags/v/version-refers-to-distribution.tag
@@ -0,0 +1,14 @@
+Tag: version-refers-to-distribution
+Severity: warning
+Check: debian/changelog
+Explanation: The Debian portion of the package version contains a reference to a
+ particular Debian release or distribution. This should only be done for
+ uploads targeted at a particular release, not at unstable or
+ experimental, and should refer to the release by version number or code
+ name.
+ .
+ Using "testing" or "stable" in a package version targeted at the current
+ testing or stable release is less informative than using the code name or
+ version number and may cause annoying version sequencing issues if the
+ package doesn't change before the next release cycle starts.
+See-Also: developer-reference 5.14.3