diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-August/007608.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-August/007608.html | 141 |
1 files changed, 141 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-August/007608.html b/zarb-ml/mageia-dev/2011-August/007608.html new file mode 100644 index 000000000..05da7d60e --- /dev/null +++ b/zarb-ml/mageia-dev/2011-August/007608.html @@ -0,0 +1,141 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Rpmlint configuration, false positives + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Rpmlint%20configuration%2C%20false%20positives&In-Reply-To=%3C4E594E59.5040501%40arcor.de%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="007607.html"> + <LINK REL="Next" HREF="007610.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Rpmlint configuration, false positives</H1> + <B>Florian Hubold</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Rpmlint%20configuration%2C%20false%20positives&In-Reply-To=%3C4E594E59.5040501%40arcor.de%3E" + TITLE="[Mageia-dev] Rpmlint configuration, false positives">doktor5000 at arcor.de + </A><BR> + <I>Sat Aug 27 22:06:49 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="007607.html">[Mageia-dev] Looking for a Mageia packaging mentor +</A></li> + <LI>Next message: <A HREF="007610.html">[Mageia-dev] Rpmlint configuration, false positives +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#7608">[ date ]</a> + <a href="thread.html#7608">[ thread ]</a> + <a href="subject.html#7608">[ subject ]</a> + <a href="author.html#7608">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Am 04.03.2011 22:30, schrieb Michael Scherer: +><i> +</I>><i> +</I>><i> But we can filter and configure it to be a little more perfect. +</I>><i> +</I>><i> In a rather autocratic fashion, as the maintainer of rpmlint ( both packages +</I>><i> and uptream ), as a packager representative, and as a apprentice dictator +</I>><i> ( since there is lots of open position in this sector since a few weeks ), +</I>><i> I propose that this become the canonical source for rpmlint configuration. +</I>><i> +</I>><i> In practice, that mean that false positives will have to be added there, +</I>><i> that stuff that are noted as errors need to be set in that package, and +</I>><i> any policy changes must be made there. +</I>><i> +</I>><i> So the question is "how do we deal with evolution ( ie, how do we decide +</I>><i> something is now a error, or no longer one". +</I>><i> +</I>><i> Traditionally, packagers didn't care at all, and so the configuration bitrotted +</I>><i> since a long time, and people didn't used it, and I just added false positives +</I>><i> when packagers notified it ( ie, almost never, except when I noticed some of +</I>><i> them ). +</I>><i> I suspect that my lack of communication around that didn't help ( and so +</I>><i> people didn't knew they could ask for adding a false positive to the list +</I>><i> of error to ignore ). +</I>><i> +</I>><i> Yet, I think we can do better, so feel free to suggest any mad idea for this. +</I> +What about the following, AFAIK those are deprecated and rpmlint shouldn't +complain about: + +*files-attr-not-set* as i was told by dmorgan, empty default attributes +(%defattr(-,root,root)) +are useless and not needed, but without it rpmlint complains with this warning +for every file. +What's the status quoe here? rpmlint issue or maybe an rpm bug? +Empty %defattr still needed or not and if not, could you make that warning an +exception? + +*no-%clean-section* +*no-cleaning-of-buildroot %clean *related to the former, as %clean is not +needed anymore, +because it's done automagically by rpm as a builtin + + +All the following should be deprecated by filetriggers: + +*library-without-ldconfig-postin +library-without-ldconfig-postun +menu-without-postin +menu-without-postun* + + +I think the following are bogus, but i may be totally wrong: + +*strange-permission * for SOURCES and SPEC it complains if not 0644, why +is that? +*%ifarch-applied-patch* if the build is broken only for i586 for example, +what's wrong about the %ifarch? +Or maybe i don't get the description fully: + + /Patches must be applied on all architectures and may contain + necessary configure and/or code patch to be effective only on a given arch./ + +With the last part of the explanation and the warning itself, i'm confused. If +it is only +effective on one arch and fixed build there, why apply it blindly to the other +where this may break build +or have other unwanted sideeffects? +</PRE> + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="007607.html">[Mageia-dev] Looking for a Mageia packaging mentor +</A></li> + <LI>Next message: <A HREF="007610.html">[Mageia-dev] Rpmlint configuration, false positives +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#7608">[ date ]</a> + <a href="thread.html#7608">[ thread ]</a> + <a href="subject.html#7608">[ subject ]</a> + <a href="author.html#7608">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |