Re: reporting/harness and stderr
"Adam D. Barratt" <adam@adam-barratt.org.uk> writes:
> In either case, I'm presuming a 1:1 mapping between unexpected lines and
> tags, so that a package producing lots of noise would in turn produce
> lots of tags. For example, the earliest entry in my error log is:
>
> tar: ./dev/rd/0: Cannot mknod: Operation not permitted
> [... and a couple of dozen more ...]
> tar: ./dev/ptmx: Cannot mknod: Operation not permitted
> tar: Error exit delayed from previous errors
> internal error.
> internal error: could not unpack package to desired level: No such file or directory
>
> and would therefore produce approximately 30 extra tags.
Yeah, that's what I meant. Basically, I'd like to prefix every line that
was sent to stderr with a "W: <package>: package-chokes-lintian ".
(We should probably figure out some way of special-casing the udeb that
does the above, btw. It's the one udeb that contains devices and it's
part of the base system setup and somewhat unavoidable. It's similar to
excluding base-files from some of the stuff in the checks/files check,
although the error actually happens during package unpack.)
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: