From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2011-August/007612.html | 104 +++++++++++++++++++++++++++++ 1 file changed, 104 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-August/007612.html (limited to 'zarb-ml/mageia-dev/2011-August/007612.html') diff --git a/zarb-ml/mageia-dev/2011-August/007612.html b/zarb-ml/mageia-dev/2011-August/007612.html new file mode 100644 index 000000000..b5580369c --- /dev/null +++ b/zarb-ml/mageia-dev/2011-August/007612.html @@ -0,0 +1,104 @@ + + + + [Mageia-dev] Rpmlint configuration, false positives + + + + + + + + + +

[Mageia-dev] Rpmlint configuration, false positives

+ Florian Hubold + doktor5000 at arcor.de +
+ Sat Aug 27 22:26:02 CEST 2011 +

+
+ +
Am 27.08.2011 22:16, schrieb Guillaume Rousse:
+> On 27/08/2011 22:06, Florian Hubold wrote:
+>> 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?
+> rpmrebuild won't work if you can't read the files included in the source 
+> package after extracting them.
+Yes, understood perfectly.
+But why does it complain about 0664 which would be the default for those
+files with a freshly created /home? Maybe it should only warn if the permissions
+are actually less?
+>
+>> *%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?
+> Because you won't notice your patch doesn't apply anymore until you build on 
+> the platform where it is actually applied. In most case, it will be the 
+> buildbot which fails, whereas your own local build was OK. The point here is 
+> 'the earlier it breaks, the quicker it gets noticed'.
+>
+Ah, silly me. Now i got it.
+
+ + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1