1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Proposal for bugzilla
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20bugzilla&In-Reply-To=%3C4D127494.1020106%40laposte.net%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="001855.html">
<LINK REL="Next" HREF="001862.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Proposal for bugzilla</H1>
<B>andre999</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20bugzilla&In-Reply-To=%3C4D127494.1020106%40laposte.net%3E"
TITLE="[Mageia-dev] Proposal for bugzilla">andr55 at laposte.net
</A><BR>
<I>Wed Dec 22 22:58:44 CET 2010</I>
<P><UL>
<LI>Previous message: <A HREF="001855.html">[Mageia-dev] Proposal for bugzilla
</A></li>
<LI>Next message: <A HREF="001862.html">[Mageia-dev] Proposal for bugzilla
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1860">[ date ]</a>
<a href="thread.html#1860">[ thread ]</a>
<a href="subject.html#1860">[ subject ]</a>
<a href="author.html#1860">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Maarten Vanraes a écrit :
><i>
</I>><i> Op woensdag 22 december 2010 20:38:06 schreef Ahmad Samir:
</I>>><i> On 22 December 2010 21:30, Renaud MICHEL<<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">r.h.michel+mageia at gmail.com</A>>
</I>><i> wrote:
</I>>>><i> On mercredi 22 décembre 2010 at 18:46, Ahmad Samir wrote :
</I>>>>>><i> Sorry for not beeing clear.
</I>>>>>><i> What I propose is not for the case 'a bug originates from more than
</I>>>>>><i> one package';
</I>>>>>><i> but for the case 'a bug manifests itself in than one package'.
</I>
If we agree that a bug can originate in more than one package, a
multiline (multi-rpm) field could be useful.
>>>><i> A bug that manifests in more than one package must originate from
</I>>>>><i> 'some package', that 'some package' is the only one that should be in
</I>>>>><i> the 'RPM Package' field; i.e that's the package that's going to need
</I>>>>><i> fixing.
</I>>>><i>
</I>>>><i> I agree, but that doesn't mean the user is able to identify the
</I>>>><i> problematic package, even if he has good knowledge of the way packages
</I>>>><i> work.
</I>>>><i>
</I>>>><i> Let's say for example that there is a problem with libxy, it is compiled
</I>>>><i> with a bad combination of optimizations that make some of its functions
</I>>>><i> behave randomly.
</I>>>><i> appA appB and appC use libxy, but appC only use simple functions that are
</I>>>><i> not affected by the optimization problem, so only appA and appB behave
</I>>>><i> badly.
</I>>>><i> Even if the user know about packages dependencies, as appC work fine he
</I>>>><i> may not come to the conclusion that libxy is causing the problem.
</I>>>><i> But he may still consider the problems with appA and appB to be related
</I>>>><i> because they started at the same time (the latest update that included
</I>>>><i> libxy).
</I>>>><i> So if he can fill a single bug report for both appA and appB, that is a
</I>>>><i> good hint to the developer that he should investigate in the
</I>>>><i> dependencies those apps have in common.
</I>>>><i>
</I>>>><i> So if you accept only one package per bug report, it may be harder to
</I>>>><i> find the actual cause, as those two apps may be maintained by different
</I>>>><i> people, each investigating the problem for his own app.
</I>
Good point.
>>><i> --
</I>>>><i> Renaud Michel
</I>>><i>
</I>>><i> Sure, but there's strace and gdb crash backtraces, that's what devs
</I>>><i> use to find where a crash/bug happens, whether it's in their
</I>>><i> package/code or somewhere else.
</I>>><i>
</I>>><i> To be more clear it's "one bug per report", that bug originates from a
</I>>><i> package, that's what gets to be put in the 'RPM Package' field; it's
</I>>><i> not unheard of that the 'RPM Package' field is changed through out the
</I>>><i> life cycle of a bug report.
</I>><i>
</I>><i> yes, but suppose there's a firefox issue and it appears to be a problem with a
</I>><i> system library, after it gets changed, people will never find this problem
</I>><i> again; since they look for firefox...
</I>
We could retain a reference to a package that manifests but doesn't
actually contain a bug by putting parentheses around its name.
- André
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="001855.html">[Mageia-dev] Proposal for bugzilla
</A></li>
<LI>Next message: <A HREF="001862.html">[Mageia-dev] Proposal for bugzilla
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1860">[ date ]</a>
<a href="thread.html#1860">[ thread ]</a>
<a href="subject.html#1860">[ subject ]</a>
<a href="author.html#1860">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>
|
