[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1031878: --fail-on warnings fails overrides even though --fail-on overrides is not specified



Package: lintian

Version: 2.104.0

Running `lintian --fail-on warnings` on a package which overrides all warnings in debian/lintian-overrides unexpectedly returns exit code 2. Expected behavior is for this command to return exit code 0 unless `lintian --fail-on overrides` is also specified.

Reading `man lintian` implies that `lintian --fail-on warnings` and `lintian --fail-on overrides` should have distinct behaviors. However, `lintian --fail-on warnings` seems to behave as if `lintian --fail-on warnings,overrides` were specified instead.

If `lintian --fail-on warnings` should always fail on warnings, even when debian/lintian-overrides overrides these warnings, the documentation should probably be clarified. However, this behavior leaves no way to check that a package having one or more overrides has no additional issues.

I run lintian as part of my build process. I'd like to fail the build if lintian finds issues with either the source package or the binary package. Currently, if I use --fail-on, and the package has any overrides, lintian always returns exit code 2. And if I don't use --fail-on, lintian always returns exit code 0. I seem to be unable to have lintian return a non-zero exit code only when a package has an issue that has not yet been fixed or overridden. Using --ftp-master-rejects might return such an exit code, however, such an exit code is not documented and would prevent using a --profile.

Same discussion applies for `--fail-on errors` etc.

Thanks,
Daniel Kauffman
Business Experience Designer
Rock Solid Solutions LLC


Reply to: