On Wed, 25 May 2011, Samuel Verschelde wrote: > > Le mercredi 25 mai 2011 17:36:29, Colin Guthrie a écrit : > > 'Twas brillig, and Colin Guthrie at 24/05/11 17:21 did gyre and gimble: > > > 'Twas brillig, and Thierry Vignaud at 24/05/11 17:01 did gyre and gimble: > > >> On 24 May 2011 17:56, nicolas vigier <[email protected]> wrote: > > >>>>> Done. > > >>>> > > >>>> We are in freeze. If we say "no" to security change, I see no reason > > >>>> to say yes to others stuff. > > >>> > > >>> It is not a change on existing package, but a new package, so I think > > >>> it is unlikely to create regression. > > >> > > >> Yes it can. > > >> It may have Provides on an already existing package > > >> It may have Obsoletes on an already existing package > > >> It may have provides file requested by another package > > >> ... > > >> > > >> That wouldn't be the first time.... > > > > > > True. These don't apply to this package, but I understand the risks. > > > > > > Anyway, this is the last one from me until the updates are open :) > > > > Actually there was a cockup in here after all. I forgot to fix the > > categories after "liberating" the base SPEC from fedora. > > > > I've updated it to something sensible now so if the categories in > > drakrpm etc. are considered important enough, then this should be pushed > > through. > > > > Sorry! :$ > > > > I support this request because after the release it will be too late : we > will > have category pollution in rpmdrake and mageia-app-db, which we will not be > able to fix with an update.
Pushed by misc.
