setBadness(..., 1000) requires nominating a specific warning category as bad, rather than being able to do so for all warnings.
Is there a straightforward way to make any warning return an error code for an RPM build that requires all exceptions to be listed in rpmlintrc with an explanation for the filter?
(It looks like setting BadnessThreshold might be supposed to do it, but I'm not sure if that needs to be done in conjunction with additional settings that give non-zero badness scores to the various warnings)
(I'm not sure if this is a docs request for the README or a feature request, as I couldn't work out if it wasn't supported without adjusting badness levels first, or if I'm just using too old a version for -o BadnessThreshold=-1 to work by default)
(Edit: previously came up in #1162, but that didn't address the "any warnings should be treated as errors" aspect, and didn't result in any docs updates)
setBadness(..., 1000)requires nominating a specific warning category as bad, rather than being able to do so for all warnings.Is there a straightforward way to make any warning return an error code for an RPM build that requires all exceptions to be listed in
rpmlintrcwith an explanation for the filter?(It looks like setting
BadnessThresholdmight be supposed to do it, but I'm not sure if that needs to be done in conjunction with additional settings that give non-zero badness scores to the various warnings)(I'm not sure if this is a docs request for the README or a feature request, as I couldn't work out if it wasn't supported without adjusting badness levels first, or if I'm just using too old a version for
-o BadnessThreshold=-1to work by default)(Edit: previously came up in #1162, but that didn't address the "any warnings should be treated as errors" aspect, and didn't result in any docs updates)