summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/20101223/001877.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/20101223/001877.html')
-rw-r--r--zarb-ml/mageia-dev/20101223/001877.html124
1 files changed, 124 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101223/001877.html b/zarb-ml/mageia-dev/20101223/001877.html
new file mode 100644
index 000000000..254873d32
--- /dev/null
+++ b/zarb-ml/mageia-dev/20101223/001877.html
@@ -0,0 +1,124 @@
+<!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=%3C20101223195121.GE2660%40sisay.ephaone.org%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="001876.html">
+ <LINK REL="Next" HREF="001880.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Proposal for bugzilla</H1>
+ <B>Michael scherer</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20bugzilla&In-Reply-To=%3C20101223195121.GE2660%40sisay.ephaone.org%3E"
+ TITLE="[Mageia-dev] Proposal for bugzilla">misc at zarb.org
+ </A><BR>
+ <I>Thu Dec 23 20:51:21 CET 2010</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="001876.html">[Mageia-dev] Proposal for bugzilla
+</A></li>
+ <LI>Next message: <A HREF="001880.html">[Mageia-dev] Proposal for bugzilla
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#1877">[ date ]</a>
+ <a href="thread.html#1877">[ thread ]</a>
+ <a href="subject.html#1877">[ subject ]</a>
+ <a href="author.html#1877">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>On Thu, Dec 23, 2010 at 12:43:23AM +0100, Samuel Verschelde wrote:
+&gt;<i> Le mercredi 22 d&#233;cembre 2010 20:34:18, Ahmad Samir a &#233;crit :
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; On 22 December 2010 21:25, Frederic Janssens &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">fjanss at gmail.com</A>&gt; wrote:
+</I>&gt;<i> &gt; &gt; On 2010-12-22, Ahmad Samir &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">ahmadsamir3891 at gmail.com</A>&gt; wrote:
+</I>&gt;<i> &gt; &gt;&gt; On 22 December 2010 18:37, Frederic Janssens &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">fjanss at gmail.com</A>&gt; wrote:
+</I>&gt;<i> &gt; &gt;&gt;&gt; On 2010-12-22, Ahmad Samir &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">ahmadsamir3891 at gmail.com</A>&gt; wrote:
+</I>&gt;<i> &gt; &gt;&gt;&gt;&gt; On 22 December 2010 01:32, Frederic Janssens &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">fjanss at gmail.com</A>&gt; wrote:
+</I>&gt;<i> &gt; &gt;
+</I>&gt;<i> &gt; &gt;&gt;&gt;&gt;&gt; First I think it would be usefull to have a multiline (Large Text Box)
+</I>&gt;<i> &gt; &gt;&gt;&gt;&gt;&gt; 'RPM Packages' field, instead of a single line (Free Text) field as
+</I>&gt;<i> &gt; &gt;&gt;&gt;&gt;&gt; used by mandriva.
+</I>&gt;<i> &gt; &gt;&gt;&gt;&gt;&gt; A single bug can concern more than one rpm. One thing mageia-app-db
+</I>&gt;<i> &gt; &gt;&gt;&gt;&gt;&gt; will do is search all bugs affecting an rpm. For that search to be
+</I>&gt;<i> &gt; &gt;&gt;&gt;&gt;&gt; meaningfull all affected rpms should be mentioned.
+</I>&gt;<i> &gt; &gt;&gt;&gt;&gt;
+</I>&gt;<i> &gt; &gt;&gt;&gt;&gt; 'One bug per report' is what we should do (did); if a bug originates
+</I>&gt;<i> &gt; &gt;&gt;&gt;&gt; from more than one package, a separate report for each of them should
+</I>&gt;<i> &gt; &gt;&gt;&gt;&gt; be opened with the Block/Dependency set correctly.
+</I>&gt;<i> &gt; &gt;&gt;&gt;
+</I>&gt;<i> &gt; &gt;&gt;&gt; Sorry for not beeing clear.
+</I>&gt;<i> &gt; &gt;&gt;&gt; What I propose is not for the case 'a bug originates from more than
+</I>&gt;<i> &gt; &gt;&gt;&gt; one package';
+</I>&gt;<i> &gt; &gt;&gt;&gt; but for the case 'a bug manifests itself in than one package'.
+</I>&gt;<i> &gt; &gt;&gt;
+</I>&gt;<i> &gt; &gt;&gt; A bug that manifests in more than one package must originate from
+</I>&gt;<i> &gt; &gt;&gt; 'some package', that 'some package' is the only one that should be in
+</I>&gt;<i> &gt; &gt;&gt; the 'RPM Package' field; i.e that's the package that's going to need
+</I>&gt;<i> &gt; &gt;&gt; fixing.
+</I>&gt;<i> &gt; &gt;
+</I>&gt;<i> &gt; &gt; Sorry again, what I mean, and should have written, is :
+</I>&gt;<i> &gt; &gt; 'a bug manifests itself in one package, but in more than one -version-release'.
+</I>&gt;<i> &gt; &gt;
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; There's no way in bugzilla to do this at the moment (there's talk
+</I>&gt;<i> &gt; about this being implemented in bugzilla-4.0, which I haven't tried
+</I>&gt;<i> &gt; before). Traditionally the Whiteboard field was used for such issues
+</I>&gt;<i> &gt; (or separate reports were opened for each affected stable release).
+</I>&gt;<i> &gt; Having a multi-line RPM Package wouldn't be the way to go with this
+</I>&gt;<i> &gt; (IMHO).
+</I>&gt;<i> &gt;
+</I>&gt;<i>
+</I>&gt;<i> In fact I think Frederic was talking about several versions of the same
+</I>&gt;<i> package, not necessarily several versions of the distribution. However,
+</I>&gt;<i> I don't think we can or should ask people to write down every package
+</I>&gt;<i> version which has the bug.
+</I>&gt;<i>
+</I>&gt;<i> We can guess many things automatically, provided the information is of
+</I>&gt;<i> good quality (the RPM/SRPM field always has a complete filename in it,
+</I>&gt;<i> and all affected versions of the distribution are flagged, whatever the
+</I>&gt;<i> way used for that : multivalue field when it'll be possible, whiteboard meanwhile...).
+</I>&gt;<i>
+</I>&gt;<i> For those who don't wan't to read everything, example 1 may be enough,
+</I>&gt;<i> I'm just trying to cover several cases, not that every case brings
+</I>&gt;<i> something really important to the discussion. My point in those examples
+</I>&gt;<i> is that we can provide useful information regarding bugs on packages in
+</I>&gt;<i> software managers or mageia-app-db, but that depends on the information
+</I>&gt;<i> present in the bug reports, that's what I'd like this to be taken into
+</I>&gt;<i> account in bug handling processes.
+</I>
+What about using the changelog for signalling what bug
+have been closed ?
+
+Something like what is done by debian
+<A HREF="http://www.debian.org/doc/developers-reference/pkgs.html#upload-bugfix">http://www.debian.org/doc/developers-reference/pkgs.html#upload-bugfix</A>
+
+--
+Michael Scherer
+</PRE>
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="001876.html">[Mageia-dev] Proposal for bugzilla
+</A></li>
+ <LI>Next message: <A HREF="001880.html">[Mageia-dev] Proposal for bugzilla
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#1877">[ date ]</a>
+ <a href="thread.html#1877">[ thread ]</a>
+ <a href="subject.html#1877">[ subject ]</a>
+ <a href="author.html#1877">[ 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>