Hi everybody, We know them all and some of us get frustrated by them: lints and brp checks aborting our builds, even though make and make install perfectly passed through (well, one correction here already: APPARENTLY perfectly passed). I do not argue against the checks at all and I think they are a good thing (tm). But sometimes they can be a little bit cryptic and most of the time require work. so I started a series of blog posts (2 so far) which try to address them. Please bare with me, I'm no hard core crack coder, but I will try to summarize the usual causes and solutions to a problem. Not in every case will the provided solution fit and if you're not sure about correctness in your package: discuss the matter with upstream. Anyway, once you produce a patch, you should always make sure upstream gets it too. So what were the blog posts about so far? Part 1: how to fix brp and rpmlint warnings ? today: Expression compares a char* pointer with a string literal http://dominique.leuenberger.net/blog/?p=151 Part 2: how to fix brp and rpmlint warnings ? today: I: Program causes undefined operation (likely same variable used twice and post/pre incremented in the same expression) http://dominique.leuenberger.net/blog/?p=178 As noted on the first entry, i will gladly take recommendations for which errors you would like to see an entry. I will try to write them up, likely 1 or 2 per week (I am actually not that much of a writer... 0 Hope the series is useful to you... If it saves you a few minutes here and there, then it is. Best regards, Dominique -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org