Bastian Kleineidam <[EMAIL PROTECTED]> writes: > I stumbled also over the warning today. I use a "private" distribution > name for packages I don't want to upload anywhere but my own box. > So +1 from me for making the warning overridable.
The hard part about overriding warnings about the *.changes file is that it's the very first thing that lintian looks at and it's not clear where the overrides should be put. A *.changes file doesn't have to include a source package and may include multiple binary packages, all of which may have separate override files. Furthermore, lintian reads the *.changes file to figure out what it's supposed to check and therefore hasn't seen any of the override files while it's trying to parse the *.changes file. The only place I could see adding overrides for those checks would be with some sort of command-line option that overrode a selected tag from the command line. Would that work for the use cases that you have in mind? -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
