[Mageia-dev] Proposal for bugzilla

Maarten Vanraes maarten.vanraes at gmail.com
Wed Dec 22 20:41:54 CET 2010

Op woensdag 22 december 2010 20:30:38 schreef Renaud MICHEL:
> On mercredi 22 décembre 2010 at 18:46, Ahmad Samir wrote :
> > > Sorry for not beeing clear.
> > > What I propose is not for the case 'a bug originates from more than
> > > one package';
> > > but for the case 'a bug manifests itself in than one package'.
> > 
> > A bug that manifests in more than one package must originate from
> > 'some package', that 'some package' is the only one that should be in
> > the 'RPM Package' field; i.e that's the package that's going to need
> > fixing.
> I agree, but that doesn't mean the user is able to identify the problematic
> package, even if he has good knowledge of the way packages work.
> Let's say for example that there is a problem with libxy, it is compiled
> with a bad combination of optimizations that make some of its functions
> behave randomly.
> appA appB and appC use libxy, but appC only use simple functions that are
> not affected by the optimization problem, so only appA and appB behave
> badly.
> Even if the user know about packages dependencies, as appC work fine he may
> not come to the conclusion that libxy is causing the problem.
> But he may still consider the problems with appA and appB to be related
> because they started at the same time (the latest update that included
> libxy).
> So if he can fill a single bug report for both appA and appB, that is a
> good hint to the developer that he should investigate in the dependencies
> those apps have in common.
> So if you accept only one package per bug report, it may be harder to find
> the actual cause, as those two apps may be maintained by different people,
> each investigating the problem for his own app.

i do concur with that; and also finding the bug report if you have the same 
problem can be tricky, if it's actual problem is one of the dependencies

More information about the Mageia-dev mailing list