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/2013-January/021656.html | 98 +++++++++++++++++++++++++++++ 1 file changed, 98 insertions(+) create mode 100644 zarb-ml/mageia-dev/2013-January/021656.html (limited to 'zarb-ml/mageia-dev/2013-January/021656.html') diff --git a/zarb-ml/mageia-dev/2013-January/021656.html b/zarb-ml/mageia-dev/2013-January/021656.html new file mode 100644 index 000000000..d039680dd --- /dev/null +++ b/zarb-ml/mageia-dev/2013-January/021656.html @@ -0,0 +1,98 @@ + + + + [Mageia-dev] Help needed: rpmlint checks not working + + + + + + + + + +

[Mageia-dev] Help needed: rpmlint checks not working

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Tue Jan 15 19:21:47 CET 2013 +

+
+ +
On 15 January 2013 19:17, Colin Guthrie <mageia at colin.guthr.ie> wrote:
+>>>>>>> Will this affect mga2 builds too? It shouldn't there so hopefully there
+>>>>>>> is no conflict :)
+>>>>>>
+>>>>>> Hmm, actually it probably applies to Mageia 2 builds too. I will try to
+>>>>>> change this.
+>>>>>
+>>>>> This should now be fixed.
+>>>>>
+>>>>> http://svnweb.mageia.org/adm/puppet/modules/buildsystem/templates/youri/submit-upload.conf?r1=2963&r2=2967
+>>>>
+>>>> Isn't that commit showing we didn't rejected some packages which
+>>>> should have been due to missing rules?
+>>>
+>>> Yes, we didn't reject some packages which should have been. Until this
+>>> commit :
+>>> http://svnweb.mageia.org/adm/puppet/modules/buildsystem/templates/youri/submit-upload.conf?r1=2928&r2=2963
+>>>
+>>> But after this one we were rejecting too much on Mageia 2. Now it should
+>>> be ok on Cauldron and Mageia 2.
+>>
+>> Well no. No as in it may be possible that some updates upload will
+>> break due to some error now being detected and rejected.
+>> Could we script a pass on all packages with that rpmlint config to
+>> catch any such packages and fix them?
+>
+> Well the first commit certainly applied to updates (and I queried as
+> much), but I think the second commit means it only applies to cauldron,
+> not any updates to mga2 etc.
+
+My point is we just added to _CAULDRON_ == mga3 a lot of rules that were missed,
+just after mass rebuild, and I fear that when we'll try to issue
+updates to _mga3_,
+we may see some being rejected, this is why I ask we check current cauldron
+with upload server rpmlint config...
+
+ + + + + + + + + + +
+

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