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

[Niels Thykier <niels@thykier.net>]

On 2012-09-22 12:49, Peter Palfrader wrote:
> 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:
> 
> [...]
> 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
> 
> 

Hi,

(As mentioned on IRC,)  I cannot reproduce this in Wheezy, but it is
visible on lintian.d.o.  I suspect it is related to
Parse::DebianChangelog and indeed its upstream changelog has:

"""
Parse-DebianChangelog (1.2.0) unstable; urgency=low

  * DebianChangelog:
    [...]
    - Allow '.' and '+' in distribution names. Patch by John Wright.
      (Closes: #565238)
    [...]
 -- Frank Lichtenheld <frank@lichtenheld.de>  Mon, 04 Apr 2011 [...]
"""

Not sure if there is something we can do about it though...

~Niels