'Twas brillig, and Pascal Terjan at 15/01/13 18:34 did gyre and gimble: > On Tue, Jan 15, 2013 at 6:21 PM, Thierry Vignaud >>>> 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... > > The options used to apply to all versions > They were copied to cauldron specific rules and those ones removed > from the default rules
That's what I took from it too. Those copied rules used to apply to everything, but because of the extra rules I wanted for cauldron only, all the other rules were copied to a cauldron specific list. It doesn't mean they are all new. At least that was my assumption of it all - no idea of the implementation! Col -- Colin Guthrie colin(at)mageia.org http://colin.guthr.ie/ Day Job: Tribalogic Limited http://www.tribalogic.net/ Open Source: Mageia Contributor http://www.mageia.org/ PulseAudio Hacker http://www.pulseaudio.org/ Trac Hacker http://trac.edgewall.org/