Joey Hess <[EMAIL PROTECTED]> writes: > (For the second time, please preserve my CC.)
> Bart Martens wrote: >> Yes, lintian. Two examples where lintian seems to follow/accept the >> numbering described in developer's reference: >> Example one: Try doing an NMU of dh-make-php with adding ".0.1". Then >> lintian produces this warning: >> W: dh-make-php source: source-nmu-has-incorrect-version-number 0.2.3.0.1 > I don't think lintian counts as something that is broken by this. Old > versions of lintian didn't include this check, since the developer's > reference didn't specify the broken version numbers. I'm happy to change this if need be. > Also, lintian's NMU handling code is broken in plenty of other ways. For > example, it relies heiristically on a given set of phrases in the > changelog to indicate an NMU. That's not really what it's doing, although some of the tags are written to imply that. It's checking the convention in DevRef 5.11.3. That's independent of how it determines whether a package is an NMU. lintian determines whether a package is an NMU by checking the last changelog signature against Maintainers and Uploaders. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
