On 15 January 2013 19:17, Colin Guthrie <mag...@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...