summaryrefslogtreecommitdiffstats
path: root/tags/p/possible-new-upstream-release-without-new-version.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-new-upstream-release-without-new-version.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/p/possible-new-upstream-release-without-new-version.tag')
-rw-r--r--tags/p/possible-new-upstream-release-without-new-version.tag9
1 files changed, 9 insertions, 0 deletions
diff --git a/tags/p/possible-new-upstream-release-without-new-version.tag b/tags/p/possible-new-upstream-release-without-new-version.tag
new file mode 100644
index 0000000..f50501d
--- /dev/null
+++ b/tags/p/possible-new-upstream-release-without-new-version.tag
@@ -0,0 +1,9 @@
+Tag: possible-new-upstream-release-without-new-version
+Severity: warning
+Check: debian/changelog
+Explanation: The most recent changelog entry contains an entry that appears to
+ say this is a new upstream release (a comment similar to "new upstream
+ release," possibly with a word between "upstream" and "release"), but the
+ upstream portion of the package version number didn't change. This may
+ indicate that the package version was not updated properly in
+ <code>debian/changelog</code>.