ubuntu-bugcontrol team mailing list archive
-
ubuntu-bugcontrol team
-
Mailing list archive
-
Message #01274
Re: Bug Pattern Writing Experience
On 03/03/2010 01:38 AM, Emmet Hikory wrote:
Brian Murray wrote:
The bug is currently about xserver-xorg-video-intel but it was
originally filed about xorg-server. You can tell this by the
SourcePackage line in the bug description.
<...>
So I envision that xorg-server
will be a collection of xorg-server patterns and also
xserver-xorg-video- driver patterns. Does that make sense to everyone
else?
That really makes sense.
xserver-xorg: xserver-xorg-video-intel, xserver-xorg-input-evdev ...
wesnoth: wesnoth-core wesnoth-httt wesnoth-l wesnoth-low ...
In the case of wesnoth the packages are issued from the same
sourcepackage. They will all pull the bugpattern named wesnoth.xml.
But you could have this situation with the nvidia drivers. The source
packages differs (the suffix is -version) but the failure can be the
same (diversion, build failure, ...)
Couldn't we add some kind of inclusion rule to the bugpattern ?
Something like: <include sourcepackage="xserver-xorg-video-intel"/>
and put the pattern in the xserver-xorg-video-intel
and if a pattern applies to many packages, you'll just have to put the
pattern in a common file and include it.
This may ultimately save space if there are a lot of such
patterns, but I'm not sufficiently familiar with the implentation to
know if this would be hard in terms of local or LP resources.
It's not technically difficult to implement but it needs some discussion
to avoid common issues like circular inclusion, mass grouping of
unrelated reports, rule exclusion for certain packages, scalability, ...
--
-JB
References