The version string in a historical changelog entry was not parsed correctly. Usually, that means it does not conform to policy.
It can also happen when a package changes from native to non-native (or the other way around). Historical entries are then in a nonconforming format.
As a side note, Lintian cannot tell whether a package changed from naive to non-native, or the other way around. It can only say whether the historical changelog entries comply with the current nativeness of a package.
For more information please consult:
- Debian Policy Manual section 5.6.12
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/changelog.