debian/copyright file mentions
but the source version has no repack suffix.
Repackaged sources are expected to indicate in their version number that they are different from the upstream release. It is commonly done by adding a repack suffix to the upstream version.
The choice of repack suffix depends on the reason for repackaging.
When some files were excluded because licensing was a concern, the
+dfsg may be appropriate. In more generic cases, one
Upstream sources are sometimes repackaged by accident when using old
dh_make. It can also happen when a maintainer
invokes the dh_make option
--createorig even though it is
According to the Debian Developer's Reference 188.8.131.52, the repack suffix is not required.
Please include such a suffix in the changelog version number to avoid this warning.
For more information please consult:
The tag is present in Lintian version
That is the most recent version we know about.
We use semantic versions.
The patch number is a commit step indicator relative to the
release tag in our Git
You can find the detection logic for this version at commit ffc17eb. For merge requests, please use the latest version in the Lintian check debian/copyright/dep5.