Ian Jackson <[EMAIL PROTECTED]> writes: > This would take the form of a `Known-Problems' field in the .changes > file. Initially this would be an X-C-Known-Problems so that old > versions of dpkg-dev can build packages; the archive script would > understand both. The syntax would be something like > > X-C-Known-Problems: > #3923 lintian E: binary-without-manpage ls > #4000 lintian E: postinst-does-not-set-usr-doc-link
I think this is *exactly* what we need. ie, "me too". I'm not sure this has to be in the control file though. It could be in the override file for lintian; instead of simply indicating that an error exists and is normal you could indicate that the error exists but is a bug that's already reported. But putting it in the control file isn't necessarily too bad an idea either, if there are advantages to that instead. -- greg
