Bug#688388: false positive debian-news-entry-has-unknown-version

[Peter Palfrader <weasel@debian.org>]

Package: lintian
Version: 2.5.10.1~bpo60+1
Severity: normal

Hi,

it seems lintian has a false positive for
debian-news-entry-has-unknown-version in tor:

| W: tor: debian-news-entry-has-unknown-version 0.2.0.26-rc-1

} $ grep 0.2.0.26-rc-1 changelog tor.NEWS 
} changelog:tor (0.2.0.26-rc-1) experimental; urgency=critical
} tor.NEWS:tor (0.2.0.26-rc-1) experimental; urgency=critical

It turns out that 0.2.0.26-rc-1 is not in the %versions hash.

Only these versions are in the hash:

known 0.2.3.3-alpha-1
known 0.2.3.4-alpha-1
known 0.2.3.5-alpha-1
known 0.2.3.6-alpha-1
known 0.2.3.7-alpha-1
known 0.2.3.8-alpha-1
known 0.2.3.9-alpha-1
known 0.2.3.10-alpha-1
known 0.2.3.11-alpha-1
known 0.2.3.11-alpha-2
known 0.2.3.12-alpha-1
known 0.2.3.13-alpha-1
known 0.2.3.14-alpha-1
known 0.2.3.15-alpha-1
known 0.2.3.16-alpha-1
known 0.2.3.17-beta-1
known 0.2.3.17-beta-2
known 0.2.3.17-beta-3
known 0.2.3.18-rc-1
known 0.2.3.19-rc-1
known 0.2.3.20-rc-1
known 0.2.3.21-rc-1
known 0.2.4.1-alpha-1
known 0.2.4.2-alpha-1
known 0.2.4.3-alpha-1

It turns out that the entry before 0.2.3.3-alpha-1 is:

| tor (0.2.3.1-alpha-1) tor-0.2.3.x; urgency=low
| 
|   * New upstream version.
|   * Forward port debian/patches/14_fix_geoip_warning.
| 
|  -- Peter Palfrader <weasel@debian.org>  Fri, 06 May 2011 17:08:03 +0200

Note the non-standard distribution/suite.

There are many other fine changelog entries after this one.

lintian probably shouldn't abort adding versions just because it
does not recognize a distribution/suite.

Cheers,
weasel