2010/12/26 Juergen Weigert
On Dec 23, 10 16:15:10 +0300, Ilya Chernykh wrote:
On Thursday 23 December 2010 16:12:14 Ludwig Nussel wrote:
I cannot disable an rpmlint check. It says "no-return-in-nonvoid-function". I added an rpmlint file with content [...] Is it a bug in OBS?
No, it's a bug in your package. You are supposed to fix the cause of the problem by patching the sources of the package. Ie add a proper return statement at the place the check tells you.
So this message is impossible to disable?
Impossible, I am afraid. In addition to rpmlint, the SUSE BuildService also runs several post-build-checks, which also can trigger warnings or abort the build with errors. Often it is not obvious, if an error message came from rpmlint or from post-build-checks. Anything you do in your .rpmlintrc will only affect rpmlint.
If someone finds a way how to disarm fatal errors from the post-build-checks, please add this info to http://en.opensuse.org/openSUSE:Packaging_checks#Disarming_Fatal_Errors Maybe it is *intentionally* impossible, ... should the wiki say that more clearly?
IIRC you could do something like BuildRequires: -post-build-checks ...and there was an alternative syntax more compatible? Perhaps #!BuildRequires: post-build-checks ?
From memory, reading this ML. Never saw it documented and should be tested before adding it to the wiki. The first time I found this brp vs post-build-checks vs rpmlint thing someone said me the idea was to port all the checks to rpmlint...
Anyway I agree, this case should be patched. And obviously submitted upstream to avoid the "Patching requires efforts and maintenance so that the patch to remain compatible with future versions" part. Could be an stupid patch, but nobody ever rejected me a patch to remove a gcc warning (the thing the post-build-check is looking at). -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org