Re: Is build node 8 broken?

Florian Hubold <[email protected]> Mon, 23 Jan 2012 20:47:57 +0100
Newsgroups gmane.linux.mandrake.cooker.devel
Message-ID <[email protected]>
Am 21.01.2012 20:35, schrieb [email protected]:
>> On Jan 21, 2012, at 1:27 PM, [email protected] wrote:
>>
>>>  AFAIK rpmlint is not being run in all nodes.
>>>
>> Slightly off-topic question:
>>
>> 	Are the rpmlint policies (as implemented atm) approx. correct?
>>
>> What I'm asking indirectly is this:
>>
>> 	Having builds fail because of zero-tolerance policy monitoring
>> 	is annoying until one starts to realize that rpmlin often helps
>> 	identify flaws earlier.
>>
>> Is rpmlint becoming useful or not?
>   I think it does more good than harm, and depending on you mood,
> the spell suggestions may even make you smile :-)
>
>   Need better error report on what happened to a few packages, e.g.
> chromium-browser-beta and ed, and I think some kernel packages.
> But most important, some place with documentation, and "howto"
> disable specific errors, actually, my suggestion is, downgrade
> errors to warnings, not silence it.
Like in http://wiki.mandriva.com/en/Development/Packaging/Problems#Rpmlint_errors
or http://fedoraproject.org/wiki/Common_Rpmlint_issues
or http://en.opensuse.org/openSUSE:Packaging_checks ?

I can only tell for Mageia, but having more of these are errors instead of
warnings,
and abort during building/upload (with some helpful error messages, which shows
the actual rpmlint warning/errors) can help improve overall packaging quality,
IMHO.
>> 73 de Jeff
> Paulo
>
>