Russ Allbery wrote: > Felipe Sateler <[EMAIL PROTECTED]> writes: > >> What you want may be achieved by enforcing the use of lintian, but I >> don't know how that can be done. > > The primary barrier to enforcing the use of lintian is #243976. lintian > needs to get much better about identifying the source of checks, the > certainty that something is wrong, and the severity level so that dak can > run lintian in a very specific way to only reject packages with fairly > certain errors according to sources with the strength of Policy.
man lintian says that when the exit status is 1, policy violations have been detected. As a first step, dak could check the exit code, and reject packages when it is 1, forwarding the lintian output to the maintainer (since E tags have high certainty, right?). This way, although tests won't be comprehensive, they would better than the current status quo. If a test result is indeed a false positive, the maintainer should have filed a bug to lintian and/or provided an override file before doing the upload. -- Felipe Sateler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
