diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20101222')
31 files changed, 4008 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101222/001839.html b/zarb-ml/mageia-dev/20101222/001839.html new file mode 100644 index 000000000..929c8bdc0 --- /dev/null +++ b/zarb-ml/mageia-dev/20101222/001839.html @@ -0,0 +1,110 @@ +<!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=%3CAANLkTi%3D04SJTvM7vRqjNgvE0iwB1N4ThirQU7FteEsEO%40mail.gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + + <LINK REL="Next" HREF="001840.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal for bugzilla</H1> + <B>Frederic Janssens</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20bugzilla&In-Reply-To=%3CAANLkTi%3D04SJTvM7vRqjNgvE0iwB1N4ThirQU7FteEsEO%40mail.gmail.com%3E" + TITLE="[Mageia-dev] Proposal for bugzilla">fjanss at gmail.com + </A><BR> + <I>Wed Dec 22 00:32:32 CET 2010</I> + <P><UL> + + <LI>Next message: <A HREF="001840.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1839">[ date ]</a> + <a href="thread.html#1839">[ thread ]</a> + <a href="subject.html#1839">[ subject ]</a> + <a href="author.html#1839">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Wed, Dec 15, 2010 at 17:07, Michael Scherer <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">misc at zarb.org</A>> wrote: +><i> +</I>><i> Le mardi 14 décembre 2010 à 17:05 +0100, Dexter Morgan a écrit : +</I>><i> > I would like to have your input to let us able to provide a bugzilla really soon +</I>><i> +</I>><i> So if I am not wrong, in bugzilla, we have : +</I>><i> - products +</I>><i> - component, contained in products +</I>><i> - and various field, per bug, +</I>><i> +</I>><i> and the way we organize everything will impact the layout. +</I>><i> +</I> +Yes. + +In preparation of the future interaction (by xmlrpc) between the +mageia-app-db site and the mageia bugzilla,  I have been testing +<A HREF="http://bugs.mageia.org/">http://bugs.mageia.org/</A> . +Xmlrpc works, but it will be necessary to configure additional fields. +The minimum would be to add an 'RPM Package' field (such as exists on +<A HREF="https://qa.mandriva.com/">https://qa.mandriva.com/</A>). + +But, as the configuration must be modified anyway, I have been +thinking about what fields we need. + +First I think it would be usefull to have a multiline (Large Text Box) +'RPM Packages' field, instead of a single line (Free Text) field as +used by mandriva. +A single bug can concern more than one rpm. One thing mageia-app-db +will do is search all bugs affecting an rpm. For that search to be +meaningfull all affected rpms should be mentioned. +For the same reason, the way the rpms are mentioned should be 'standardised', +as the search done by bugzilla can only be litteral. + +Something that does not exist in mandriva, but I think would be usefull, is a +'Fixed RPM Packages' that would be filled when the bug is fixed. FIXED +is great, but where (or since which rpm)? + +Perhaps also an 'Upstream' field which would, eventually, indicate +where that bug is filed upstream. + +Finally the "status whiteboard" could be enabled, and used to clearly +explain a workaround, for open bugs (instead of having to figure it +from the comments). (Eventually this field could also be used as the +'Fixed RPM Packages' field when the bug is closed. So it would be the +'Solution' field) + +Apart from the "status whiteboard" which is a parameter to enable +(<A HREF="http://www.bugzilla.org/docs/tip/en/html/parameters.html">http://www.bugzilla.org/docs/tip/en/html/parameters.html</A>); +the fields must be added as custom-fields +(<A HREF="http://www.bugzilla.org/docs/3.6/en/html/custom-fields.html">http://www.bugzilla.org/docs/3.6/en/html/custom-fields.html</A>) + + +-- + +Frederic +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + + <LI>Next message: <A HREF="001840.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1839">[ date ]</a> + <a href="thread.html#1839">[ thread ]</a> + <a href="subject.html#1839">[ subject ]</a> + <a href="author.html#1839">[ 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> diff --git a/zarb-ml/mageia-dev/20101222/001840.html b/zarb-ml/mageia-dev/20101222/001840.html new file mode 100644 index 000000000..a93a06a89 --- /dev/null +++ b/zarb-ml/mageia-dev/20101222/001840.html @@ -0,0 +1,89 @@ +<!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=%3C1292977686.6535.15.camel%40akroma.ephaone.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001839.html"> + <LINK REL="Next" HREF="001844.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=%3C1292977686.6535.15.camel%40akroma.ephaone.org%3E" + TITLE="[Mageia-dev] Proposal for bugzilla">misc at zarb.org + </A><BR> + <I>Wed Dec 22 01:28:06 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001839.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001844.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1840">[ date ]</a> + <a href="thread.html#1840">[ thread ]</a> + <a href="subject.html#1840">[ subject ]</a> + <a href="author.html#1840">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le mercredi 22 décembre 2010 à 00:32 +0100, Frederic Janssens a écrit : +><i> On Wed, Dec 15, 2010 at 17:07, Michael Scherer <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">misc at zarb.org</A>> wrote: +</I>><i> > +</I>><i> > Le mardi 14 décembre 2010 à 17:05 +0100, Dexter Morgan a écrit : +</I>><i> > > I would like to have your input to let us able to provide a bugzilla really soon +</I>><i> > +</I>><i> > So if I am not wrong, in bugzilla, we have : +</I>><i> > - products +</I>><i> > - component, contained in products +</I>><i> > - and various field, per bug, +</I>><i> > +</I>><i> > and the way we organize everything will impact the layout. +</I>><i> > +</I>><i> +</I>><i> Yes. +</I>><i> +</I>><i> In preparation of the future interaction (by xmlrpc) between the +</I>><i> mageia-app-db site and the mageia bugzilla, I have been testing +</I>><i> <A HREF="http://bugs.mageia.org/">http://bugs.mageia.org/</A> . +</I>><i> Xmlrpc works, but it will be necessary to configure additional fields. +</I>><i> The minimum would be to add an 'RPM Package' field (such as exists on +</I>><i> <A HREF="https://qa.mandriva.com/">https://qa.mandriva.com/</A>). +</I> +What about component not related to rpm ? + +And do you mean srpm or rpm ? + +We should also take in account package naming change. + +-- +Michael Scherer + +</PRE> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001839.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001844.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1840">[ date ]</a> + <a href="thread.html#1840">[ thread ]</a> + <a href="subject.html#1840">[ subject ]</a> + <a href="author.html#1840">[ 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> diff --git a/zarb-ml/mageia-dev/20101222/001841.html b/zarb-ml/mageia-dev/20101222/001841.html new file mode 100644 index 000000000..f2f49b16c --- /dev/null +++ b/zarb-ml/mageia-dev/20101222/001841.html @@ -0,0 +1,106 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] mageia sound tasks + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20mageia%20sound%20tasks&In-Reply-To=%3C4D11CA07.20400%40iki.fi%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001853.html"> + <LINK REL="Next" HREF="001842.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] mageia sound tasks</H1> + <B>Thomas Backlund</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20mageia%20sound%20tasks&In-Reply-To=%3C4D11CA07.20400%40iki.fi%3E" + TITLE="[Mageia-dev] mageia sound tasks">tmb at iki.fi + </A><BR> + <I>Wed Dec 22 10:51:03 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001853.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001842.html">[Mageia-dev] mageia sound tasks +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1841">[ date ]</a> + <a href="thread.html#1841">[ thread ]</a> + <a href="subject.html#1841">[ subject ]</a> + <a href="author.html#1841">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>SaschaS skrev 17.12.2010 18:49: +><i> After having a looong chat with the guys from linux4audio and reading +</I>><i> tons of posts in ccrma forum, I must say ..... +</I>><i> +</I>><i> Idea with an rt-kernel for netbooks ....... DISMISSED .... it simply +</I>><i> makes no sense. +</I>><i> Those guys mostly use gentoo and build their own kernel for years now +</I>><i> and they gave me the following hints, that also can be found in +</I>><i> discussions of other distributions: +</I>><i> 1) the kernel (without preemption-patch) should have +</I>><i> +</I>><i> Processor type and features>> Preemption Mode>> Complete Preemption (Real-Time) +</I> +This is already enabled in kernel-tmb + + +><i> Processor type and features>> Timer frequency>> 1000 HZ +</I> +This is already enabled in all -desktop kernels + + +><i> General setup>> RCU Subsystem>> RCU Implementation (Preemptable tree-based hierarchical RCU) +</I> +This is already enabled in kernel-tmb + + +><i> Proccesor Type and features >> Tickless System (Dynamic Ticks) should +</I>><i> be excluded +</I> +This one you can get by booting with "nohz=off" on the kernel command line. + +-- +Thomas +</PRE> + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001853.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001842.html">[Mageia-dev] mageia sound tasks +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1841">[ date ]</a> + <a href="thread.html#1841">[ thread ]</a> + <a href="subject.html#1841">[ subject ]</a> + <a href="author.html#1841">[ 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> diff --git a/zarb-ml/mageia-dev/20101222/001842.html b/zarb-ml/mageia-dev/20101222/001842.html new file mode 100644 index 000000000..c1837219f --- /dev/null +++ b/zarb-ml/mageia-dev/20101222/001842.html @@ -0,0 +1,133 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] mageia sound tasks + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20mageia%20sound%20tasks&In-Reply-To=%3CAANLkTi%3DCqenhST04thg%3DaU8Pt2PD%2BD8a-AGh7pjDyjig%40mail.gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001841.html"> + <LINK REL="Next" HREF="001843.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] mageia sound tasks</H1> + <B>Sascha Schneider</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20mageia%20sound%20tasks&In-Reply-To=%3CAANLkTi%3DCqenhST04thg%3DaU8Pt2PD%2BD8a-AGh7pjDyjig%40mail.gmail.com%3E" + TITLE="[Mageia-dev] mageia sound tasks">ungleichklang at gmail.com + </A><BR> + <I>Wed Dec 22 12:05:19 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001841.html">[Mageia-dev] mageia sound tasks +</A></li> + <LI>Next message: <A HREF="001843.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1842">[ date ]</a> + <a href="thread.html#1842">[ thread ]</a> + <a href="subject.html#1842">[ subject ]</a> + <a href="author.html#1842">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>This sounds great, + +latest kernel-tmb I see in the repos (64bit) is 2.6.31 +will test it this eve on my both mashines with my musicapps. + +Thanks Thomas + +added this kernel as an option to the wiki + +regard, saschas + +2010/12/22 Thomas Backlund <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">tmb at iki.fi</A>> + +><i> SaschaS skrev 17.12.2010 18:49: +</I>><i> +</I>><i> After having a looong chat with the guys from linux4audio and reading +</I>>><i> tons of posts in ccrma forum, I must say ..... +</I>>><i> +</I>>><i> Idea with an rt-kernel for netbooks ....... DISMISSED .... it simply +</I>>><i> makes no sense. +</I>>><i> Those guys mostly use gentoo and build their own kernel for years now +</I>>><i> and they gave me the following hints, that also can be found in +</I>>><i> discussions of other distributions: +</I>>><i> 1) the kernel (without preemption-patch) should have +</I>>><i> +</I>>><i> Processor type and features>> Preemption Mode>> Complete Preemption +</I>>><i> (Real-Time) +</I>>><i> +</I>><i> +</I>><i> This is already enabled in kernel-tmb +</I>><i> +</I>><i> +</I>><i> +</I>><i> Processor type and features>> Timer frequency>> 1000 HZ +</I>>><i> +</I>><i> +</I>><i> This is already enabled in all -desktop kernels +</I>><i> +</I>><i> +</I>><i> +</I>><i> General setup>> RCU Subsystem>> RCU Implementation (Preemptable +</I>>><i> tree-based hierarchical RCU) +</I>>><i> +</I>><i> +</I>><i> This is already enabled in kernel-tmb +</I>><i> +</I>><i> +</I>><i> +</I>><i> Proccesor Type and features >> Tickless System (Dynamic Ticks) should +</I>>><i> be excluded +</I>>><i> +</I>><i> +</I>><i> This one you can get by booting with "nohz=off" on the kernel command line. +</I>><i> +</I>><i> -- +</I>><i> Thomas +</I>><i> +</I>-------------- next part -------------- +An HTML attachment was scrubbed... +URL: </pipermail/mageia-dev/attachments/20101222/538c359e/attachment.html> +</PRE> + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001841.html">[Mageia-dev] mageia sound tasks +</A></li> + <LI>Next message: <A HREF="001843.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1842">[ date ]</a> + <a href="thread.html#1842">[ thread ]</a> + <a href="subject.html#1842">[ subject ]</a> + <a href="author.html#1842">[ 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> diff --git a/zarb-ml/mageia-dev/20101222/001843.html b/zarb-ml/mageia-dev/20101222/001843.html new file mode 100644 index 000000000..66a9fd056 --- /dev/null +++ b/zarb-ml/mageia-dev/20101222/001843.html @@ -0,0 +1,115 @@ +<!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=%3CAANLkTimkRUOvOgK94KuD8n4TEs5cqxW6Te4A6_Ht%2BH-t%40mail.gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001842.html"> + <LINK REL="Next" HREF="001845.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal for bugzilla</H1> + <B>Romain d'Alverny</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20bugzilla&In-Reply-To=%3CAANLkTimkRUOvOgK94KuD8n4TEs5cqxW6Te4A6_Ht%2BH-t%40mail.gmail.com%3E" + TITLE="[Mageia-dev] Proposal for bugzilla">rdalverny at gmail.com + </A><BR> + <I>Wed Dec 22 12:07:21 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001842.html">[Mageia-dev] mageia sound tasks +</A></li> + <LI>Next message: <A HREF="001845.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1843">[ date ]</a> + <a href="thread.html#1843">[ thread ]</a> + <a href="subject.html#1843">[ subject ]</a> + <a href="author.html#1843">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Wed, Dec 15, 2010 at 17:07, Michael Scherer <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">misc at zarb.org</A>> wrote: +><i> Le mardi 14 décembre 2010 à 17:05 +0100, Dexter Morgan a écrit : +</I>>><i> hello, +</I>>><i> +</I>>><i> now that we have a working bugzilla we need to have a working layout. +</I>>><i> +</I>>><i> I created a wiki page presenting what could be done. +</I>>><i> <A HREF="http://mageia.org/wiki/doku.php?id=bugzilla">http://mageia.org/wiki/doku.php?id=bugzilla</A> +</I>>><i> +</I>>><i> I would like to have your input to let us able to provide a bugzilla really soon +</I>><i> +</I>><i> So if I am not wrong, in bugzilla, we have : +</I>><i> - products +</I>><i> - component, contained in products +</I>><i> - and various field, per bug, +</I>><i> +</I>><i> and the way we organize everything will impact the layout. +</I>><i> +</I>><i> And for now, we are just talking of : +</I>><i> - distributions +</I>><i> - website +</I>><i> +</I>><i> this lead me to 3 questions, regarding the proposal "potential layout" +</I>><i> at the end of the page : +</I>><i> +</I>><i> - if we do have 1 product per distribution, +</I> +That's a possibility. One may as well have: + - 1 product per distribution/release (RH way) - that will extend the +list of products to be on the front page (at least the time they are +supported) + - 1 product per distribution/product line (MDV way), managing the +version field for the exact release - that will keep the front page +list sized + + +><i> - what about requests that are not for website, like generic sysadmin +</I>><i> request, or maybe community process, etc ? +</I> +That would be a separate product I guess. + +Romain +</PRE> + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001842.html">[Mageia-dev] mageia sound tasks +</A></li> + <LI>Next message: <A HREF="001845.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1843">[ date ]</a> + <a href="thread.html#1843">[ thread ]</a> + <a href="subject.html#1843">[ subject ]</a> + <a href="author.html#1843">[ 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> diff --git a/zarb-ml/mageia-dev/20101222/001844.html b/zarb-ml/mageia-dev/20101222/001844.html new file mode 100644 index 000000000..b08c8a9e8 --- /dev/null +++ b/zarb-ml/mageia-dev/20101222/001844.html @@ -0,0 +1,116 @@ +<!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=%3CAANLkTinh7A%2B_jhEOEL5L3LkrG6%2B7cM9fujPEPwDRNQme%40mail.gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001840.html"> + <LINK REL="Next" HREF="001857.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal for bugzilla</H1> + <B>Frederic Janssens</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20bugzilla&In-Reply-To=%3CAANLkTinh7A%2B_jhEOEL5L3LkrG6%2B7cM9fujPEPwDRNQme%40mail.gmail.com%3E" + TITLE="[Mageia-dev] Proposal for bugzilla">fjanss at gmail.com + </A><BR> + <I>Wed Dec 22 13:55:02 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001840.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001857.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1844">[ date ]</a> + <a href="thread.html#1844">[ thread ]</a> + <a href="subject.html#1844">[ subject ]</a> + <a href="author.html#1844">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 2010-12-22, Michael Scherer <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">misc at zarb.org</A>> wrote: +><i> Le mercredi 22 décembre 2010 à 00:32 +0100, Frederic Janssens a écrit : +</I>>><i> On Wed, Dec 15, 2010 at 17:07, Michael Scherer <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">misc at zarb.org</A>> wrote: +</I>>><i> > +</I>>><i> > Le mardi 14 décembre 2010 à 17:05 +0100, Dexter Morgan a écrit : +</I>>><i> > > I would like to have your input to let us able to provide a bugzilla +</I>>><i> > > really soon +</I>>><i> > +</I>>><i> > So if I am not wrong, in bugzilla, we have : +</I>>><i> > - products +</I>>><i> > - component, contained in products +</I>>><i> > - and various field, per bug, +</I>>><i> > +</I>>><i> > and the way we organize everything will impact the layout. +</I>>><i> > +</I>>><i> +</I>>><i> Yes. +</I>>><i> +</I>>><i> In preparation of the future interaction (by xmlrpc) between the +</I>>><i> mageia-app-db site and the mageia bugzilla, I have been testing +</I>>><i> <A HREF="http://bugs.mageia.org/">http://bugs.mageia.org/</A> . +</I>>><i> Xmlrpc works, but it will be necessary to configure additional fields. +</I>>><i> The minimum would be to add an 'RPM Package' field (such as exists on +</I>>><i> <A HREF="https://qa.mandriva.com/">https://qa.mandriva.com/</A>). +</I>><i> +</I>><i> What about component not related to rpm ? +</I> +The 'RPM Package' field would be left blank. +(usually many fields are left blank) + +><i> +</I>><i> And do you mean srpm or rpm ? +</I> +On <A HREF="https://qa.mandriva.com/">https://qa.mandriva.com/</A> anything goes. +To permit consistent searches I think we should standardise. +The aim would to be to as specific as needed but not more; +as far as I know that would be : + +name-version-release + +unless the bug is architecture specific, where we would have : + +name-version-release.architecture + +><i> +</I>><i> We should also take in account package naming change. +</I> +which change? + +><i> +</I>><i> -- +</I>><i> Michael Scherer +</I>><i> +</I>><i> +</I> + +-- + +Frederic +</PRE> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001840.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001857.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1844">[ date ]</a> + <a href="thread.html#1844">[ thread ]</a> + <a href="subject.html#1844">[ subject ]</a> + <a href="author.html#1844">[ 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> diff --git a/zarb-ml/mageia-dev/20101222/001845.html b/zarb-ml/mageia-dev/20101222/001845.html new file mode 100644 index 000000000..d75caa490 --- /dev/null +++ b/zarb-ml/mageia-dev/20101222/001845.html @@ -0,0 +1,138 @@ +<!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=%3CAANLkTim%3DWKxNALLfe3L%2BKScZRkrKWdOG5Xqw5yGd6adg%40mail.gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001843.html"> + <LINK REL="Next" HREF="001856.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal for bugzilla</H1> + <B>Ahmad Samir</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20bugzilla&In-Reply-To=%3CAANLkTim%3DWKxNALLfe3L%2BKScZRkrKWdOG5Xqw5yGd6adg%40mail.gmail.com%3E" + TITLE="[Mageia-dev] Proposal for bugzilla">ahmadsamir3891 at gmail.com + </A><BR> + <I>Wed Dec 22 15:08:42 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001843.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001856.html">[Mageia-dev] Choosing packagers representatives +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1845">[ date ]</a> + <a href="thread.html#1845">[ thread ]</a> + <a href="subject.html#1845">[ subject ]</a> + <a href="author.html#1845">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 14 December 2010 18:05, Dexter Morgan <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">dmorganec at gmail.com</A>> wrote: +><i> hello, +</I>><i> +</I>><i> now that we have a working bugzilla we need to have a working layout. +</I>><i> +</I>><i> i created a wiki page presenting what could be done. +</I>><i> <A HREF="http://mageia.org/wiki/doku.php?id=bugzilla">http://mageia.org/wiki/doku.php?id=bugzilla</A> +</I>><i> +</I>><i> I would like to have your input to let us able to provide a bugzilla really soon +</I>><i> +</I>><i> +</I>><i> In the bugreport creation we were thinking of using the mdv way or the +</I>><i> fedora way. +</I>><i> +</I>><i> +</I>><i> Fedora way is to add all srpms in the componment field but there is 2 +</I>><i> pbs with this way : +</I>><i> +</I>><i> -> Users don't know what is a rpms ( like what is the srpms for kwrite ) +</I>><i> -> This slow down the bugzilla too much +</I>><i> +</I> +I am most familiar with the layout at qa.mandriva.com, so I think it's +good to start with it and modify things as needed. + +- I think we should have two 'Products' (for now), Mageia and Websites. + +- Under the 'Product: Mageia' the Version field (1.0, 1.1, 2.0, +Cauldron... etc) specifies the release the bug report affects (with a +whiteboard field to state if the bug affects more than one release (at +least for now)). + +- The Components should be: + - Documentation + - Installation + - RPM packages + - New Packages requests + - Release Media + - Security + - Translations + +Note that I dropped: + - Kernel, as it's just still an rpm package and will be assigned +properly based on the RPM Package field + - Hardware, we won't fix bugs in hardware, we'll fix bugs in the +software handling the hardware (and it was seldom used in the past +anyway) + + +- An "Architecture" field + +- Source RPM / RPM Package + +- Url field, for putting links to upstream bug reports in a clear place + +- Summary + +- Description + +- Severity and Priority fields + +See here for a picture of what I have in mind: +<A HREF="https://qa.mandriva.com/enter_bug.cgi?product=Mandriva%20Linux&format=guided">https://qa.mandriva.com/enter_bug.cgi?product=Mandriva%20Linux&format=guided</A> + +-- +Ahmad Samir +</PRE> + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001843.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001856.html">[Mageia-dev] Choosing packagers representatives +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1845">[ date ]</a> + <a href="thread.html#1845">[ thread ]</a> + <a href="subject.html#1845">[ subject ]</a> + <a href="author.html#1845">[ 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> diff --git a/zarb-ml/mageia-dev/20101222/001846.html b/zarb-ml/mageia-dev/20101222/001846.html new file mode 100644 index 000000000..54b877f3a --- /dev/null +++ b/zarb-ml/mageia-dev/20101222/001846.html @@ -0,0 +1,158 @@ +<!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=%3CAANLkTikiFvH1H2GTRz%2Byz2NKnfFQJ%3D7AmfcGaQEeOQgq%40mail.gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001864.html"> + <LINK REL="Next" HREF="001847.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal for bugzilla</H1> + <B>Ahmad Samir</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20bugzilla&In-Reply-To=%3CAANLkTikiFvH1H2GTRz%2Byz2NKnfFQJ%3D7AmfcGaQEeOQgq%40mail.gmail.com%3E" + TITLE="[Mageia-dev] Proposal for bugzilla">ahmadsamir3891 at gmail.com + </A><BR> + <I>Wed Dec 22 15:27:09 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001864.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001847.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1846">[ date ]</a> + <a href="thread.html#1846">[ thread ]</a> + <a href="subject.html#1846">[ subject ]</a> + <a href="author.html#1846">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 22 December 2010 01:32, Frederic Janssens <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">fjanss at gmail.com</A>> wrote: +><i> On Wed, Dec 15, 2010 at 17:07, Michael Scherer <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">misc at zarb.org</A>> wrote: +</I>>><i> +</I>>><i> Le mardi 14 décembre 2010 à 17:05 +0100, Dexter Morgan a écrit : +</I>>><i> > I would like to have your input to let us able to provide a bugzilla really soon +</I>>><i> +</I>>><i> So if I am not wrong, in bugzilla, we have : +</I>>><i> - products +</I>>><i> - component, contained in products +</I>>><i> - and various field, per bug, +</I>>><i> +</I>>><i> and the way we organize everything will impact the layout. +</I>>><i> +</I>><i> +</I>><i> Yes. +</I>><i> +</I>><i> In preparation of the future interaction (by xmlrpc) between the +</I>><i> mageia-app-db site and the mageia bugzilla,  I have been testing +</I>><i> <A HREF="http://bugs.mageia.org/">http://bugs.mageia.org/</A> . +</I>><i> Xmlrpc works, but it will be necessary to configure additional fields. +</I>><i> The minimum would be to add an 'RPM Package' field (such as exists on +</I>><i> <A HREF="https://qa.mandriva.com/">https://qa.mandriva.com/</A>). +</I>><i> +</I> +That's already agreed upon, whatever it's called, RPM Package or +Component (I am in favour of the former). + +><i> But, as the configuration must be modified anyway, I have been +</I>><i> thinking about what fields we need. +</I>><i> +</I>><i> First I think it would be usefull to have a multiline (Large Text Box) +</I>><i> 'RPM Packages' field, instead of a single line (Free Text) field as +</I>><i> used by mandriva. +</I>><i> A single bug can concern more than one rpm. One thing mageia-app-db +</I>><i> will do is search all bugs affecting an rpm. For that search to be +</I>><i> meaningfull all affected rpms should be mentioned. +</I> +'One bug per report' is what we should do (did); if a bug originates +from more than one package, a separate report for each of them should +be opened with the Block/Dependency set correctly. + +><i> For the same reason, the way the rpms are mentioned should be 'standardised', +</I>><i> as the search done by bugzilla can only be litteral. +</I>><i> +</I> +Usually one doesn't only search in the RPM Package field; experience +tell us that the affected package name will be mentioned many times in +both the summary and the description. + +And if you want to search in the RPM Package field, bugzilla has many +options to do so, look at the bottom of: +<A HREF="https://qa.mandriva.com/query.cgi?format=advanced">https://qa.mandriva.com/query.cgi?format=advanced</A> + +><i> Something that does not exist in mandriva, but I think would be usefull, is a +</I>><i> 'Fixed RPM Packages' that would be filled when the bug is fixed. FIXED +</I>><i> is great, but where (or since which rpm)? +</I>><i> +</I> +IMHO, that's trivia; either the user is savvy enough / has the time to +trudge through the bug report to find out which package release fixes +an issue (which indicates he's the curious type, he'll at least skim +through the bug report anyway), or he's just going to update his +system and get the fix (the latter happens more often). + +><i> Perhaps also an 'Upstream' field which would, eventually, indicate +</I>><i> where that bug is filed upstream. +</I>><i> +</I> +That's similar to the URL field in my proposal (see my previous post +in this thread). + +><i> Finally the "status whiteboard" could be enabled, and used to clearly +</I>><i> explain a workaround, for open bugs (instead of having to figure it +</I>><i> from the comments). (Eventually this field could also be used as the +</I>><i> 'Fixed RPM Packages' field when the bug is closed. So it would be the +</I>><i> 'Solution' field) +</I>><i> +</I> +I don't think this will be adequately useful; if the issue is fixed, +then all the user has to do is update his system. If it's not fixed +and affects a stable release then it should get added to the Errata +page for that release whether there's a workaround (or not); if it +affects Cauldron, well, Cauldron users are supposed to be +fireproof-ready, so they do read bug reports (or skim through them). + +><i> Apart from the "status whiteboard" which is a parameter to enable +</I>><i> (<A HREF="http://www.bugzilla.org/docs/tip/en/html/parameters.html">http://www.bugzilla.org/docs/tip/en/html/parameters.html</A>); +</I>><i> the fields must be added as custom-fields +</I>><i> (<A HREF="http://www.bugzilla.org/docs/3.6/en/html/custom-fields.html">http://www.bugzilla.org/docs/3.6/en/html/custom-fields.html</A>) +</I>><i> +</I>><i> +</I>><i> -- +</I>><i> +</I>><i> Frederic +</I>><i> +</I> + + +-- +Ahmad Samir +</PRE> + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001864.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001847.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1846">[ date ]</a> + <a href="thread.html#1846">[ thread ]</a> + <a href="subject.html#1846">[ subject ]</a> + <a href="author.html#1846">[ 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> diff --git a/zarb-ml/mageia-dev/20101222/001847.html b/zarb-ml/mageia-dev/20101222/001847.html new file mode 100644 index 000000000..23e1cb590 --- /dev/null +++ b/zarb-ml/mageia-dev/20101222/001847.html @@ -0,0 +1,213 @@ +<!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=%3CAANLkTikfJPf8G0dHFb261e77uJ9%3D362PQX6M37POm57P%40mail.gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001846.html"> + <LINK REL="Next" HREF="001848.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal for bugzilla</H1> + <B>Frederic Janssens</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20bugzilla&In-Reply-To=%3CAANLkTikfJPf8G0dHFb261e77uJ9%3D362PQX6M37POm57P%40mail.gmail.com%3E" + TITLE="[Mageia-dev] Proposal for bugzilla">fjanss at gmail.com + </A><BR> + <I>Wed Dec 22 17:37:19 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001846.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001848.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1847">[ date ]</a> + <a href="thread.html#1847">[ thread ]</a> + <a href="subject.html#1847">[ subject ]</a> + <a href="author.html#1847">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 2010-12-22, Ahmad Samir <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">ahmadsamir3891 at gmail.com</A>> wrote: +><i> On 22 December 2010 01:32, Frederic Janssens <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">fjanss at gmail.com</A>> wrote: +</I>>><i> On Wed, Dec 15, 2010 at 17:07, Michael Scherer <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">misc at zarb.org</A>> wrote: +</I>>><i> +</I>>><i> In preparation of the future interaction (by xmlrpc) between the +</I>>><i> mageia-app-db site and the mageia bugzilla, I have been testing +</I>>><i> <A HREF="http://bugs.mageia.org/">http://bugs.mageia.org/</A> . +</I>>><i> Xmlrpc works, but it will be necessary to configure additional fields. +</I>>><i> The minimum would be to add an 'RPM Package' field (such as exists on +</I>>><i> <A HREF="https://qa.mandriva.com/">https://qa.mandriva.com/</A>). +</I>>><i> +</I>><i> +</I>><i> That's already agreed upon, whatever it's called, RPM Package or +</I>><i> Component (I am in favour of the former). +</I> +ok + +>><i> First I think it would be usefull to have a multiline (Large Text Box) +</I>>><i> 'RPM Packages' field, instead of a single line (Free Text) field as +</I>>><i> used by mandriva. +</I>>><i> A single bug can concern more than one rpm. One thing mageia-app-db +</I>>><i> will do is search all bugs affecting an rpm. For that search to be +</I>>><i> meaningfull all affected rpms should be mentioned. +</I>><i> +</I>><i> 'One bug per report' is what we should do (did); if a bug originates +</I>><i> from more than one package, a separate report for each of them should +</I>><i> be opened with the Block/Dependency set correctly. +</I> +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'. +(In fact I think I want to solve the same problem you want to solve with +"with a whiteboard field to state if the bug affects more than one release (at +least for now)" +but in a more specific manner). + +><i> +</I>>><i> For the same reason, the way the rpms are mentioned should be +</I>>><i> 'standardised', +</I>>><i> as the search done by bugzilla can only be litteral. +</I>>><i> +</I>><i> +</I>><i> Usually one doesn't only search in the RPM Package field; experience +</I>><i> tell us that the affected package name will be mentioned many times in +</I>><i> both the summary and the description. +</I>><i> +</I>><i> And if you want to search in the RPM Package field, bugzilla has many +</I>><i> options to do so, look at the bottom of: +</I>><i> <A HREF="https://qa.mandriva.com/query.cgi?format=advanced">https://qa.mandriva.com/query.cgi?format=advanced</A> +</I> +Yes; but I am trying to solve the connection with mageia-app-db. +With the xmlrpc interface it seems the search possibilities are more limited : +(from <A HREF="http://www.bugzilla.org/docs/3.6/en/html/api/Bugzilla/WebService/Bug.html">http://www.bugzilla.org/docs/3.6/en/html/api/Bugzilla/WebService/Bug.html</A>) +:<i> +</I> +" +search + + UNSTABLE + + Description + + Allows you to search for bugs based on particular criteria. + Params + + Unless otherwise specified in the description of a parameter, +bugs are returned if they match exactly the criteria you specify in +these parameters. That is, we don't match against substrings--if a bug +is in the "Widgets" product and you ask for bugs in the "Widg" +product, you won't get anything. + + Criteria are joined in a logical AND. That is, you will be +returned bugs that match all of the criteria, not bugs that match any +of the criteria. + + Each parameter can be either the type it says, or an array of +the types it says. If you pass an array, it means "Give me bugs with +any of these values." For example, if you wanted bugs that were in +either the "Foo" or "Bar" products, you'd pass: + + product => ['Foo', 'Bar'] +" + +><i> +</I>>><i> Something that does not exist in mandriva, but I think would be usefull, +</I>>><i> is a +</I>>><i> 'Fixed RPM Packages' that would be filled when the bug is fixed. FIXED +</I>>><i> is great, but where (or since which rpm)? +</I>>><i> +</I>><i> +</I>><i> IMHO, that's trivia; either the user is savvy enough / has the time to +</I>><i> trudge through the bug report to find out which package release fixes +</I>><i> an issue (which indicates he's the curious type, he'll at least skim +</I>><i> through the bug report anyway), or he's just going to update his +</I>><i> system and get the fix (the latter happens more often). +</I> +Here the 'user' is mageia-app-db. + + +><i> +</I>>><i> Perhaps also an 'Upstream' field which would, eventually, indicate +</I>>><i> where that bug is filed upstream. +</I>>><i> +</I>><i> +</I>><i> That's similar to the URL field in my proposal (see my previous post +</I>><i> in this thread). +</I> +Ok. + +><i> +</I>>><i> Finally the "status whiteboard" could be enabled, and used to clearly +</I>>><i> explain a workaround, for open bugs (instead of having to figure it +</I>>><i> from the comments). (Eventually this field could also be used as the +</I>>><i> 'Fixed RPM Packages' field when the bug is closed. So it would be the +</I>>><i> 'Solution' field) +</I>>><i> +</I>><i> +</I>><i> I don't think this will be adequately useful; if the issue is fixed, +</I>><i> then all the user has to do is update his system. If it's not fixed +</I>><i> and affects a stable release then it should get added to the Errata +</I>><i> page for that release whether there's a workaround (or not); if it +</I> +Still another place to look at. If it concerns the bug it would be +better to have it visible in the bug. + +><i> affects Cauldron, well, Cauldron users are supposed to be +</I>><i> fireproof-ready, so they do read bug reports (or skim through them). +</I> +How is the case represented where the bug is in release, +and the fix is in cauldron ? + + +><i> +</I>>><i> Apart from the "status whiteboard" which is a parameter to enable +</I>>><i> (<A HREF="http://www.bugzilla.org/docs/tip/en/html/parameters.html">http://www.bugzilla.org/docs/tip/en/html/parameters.html</A>); +</I>>><i> the fields must be added as custom-fields +</I>>><i> (<A HREF="http://www.bugzilla.org/docs/3.6/en/html/custom-fields.html">http://www.bugzilla.org/docs/3.6/en/html/custom-fields.html</A>) +</I>>><i> +</I>>><i> +</I>>><i> -- +</I>>><i> +</I>>><i> Frederic +</I>>><i> +</I>><i> +</I>><i> +</I>><i> +</I>><i> -- +</I>><i> Ahmad Samir +</I>><i> +</I> + +-- + +Frederic +</PRE> + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001846.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001848.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1847">[ date ]</a> + <a href="thread.html#1847">[ thread ]</a> + <a href="subject.html#1847">[ subject ]</a> + <a href="author.html#1847">[ 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> diff --git a/zarb-ml/mageia-dev/20101222/001848.html b/zarb-ml/mageia-dev/20101222/001848.html new file mode 100644 index 000000000..ae8dae755 --- /dev/null +++ b/zarb-ml/mageia-dev/20101222/001848.html @@ -0,0 +1,249 @@ +<!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=%3CAANLkTi%3D9Uj1uDD5xAAO8uO8hoJNSz%2BMCObUyrGvQNzTR%40mail.gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001847.html"> + <LINK REL="Next" HREF="001849.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal for bugzilla</H1> + <B>Ahmad Samir</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20bugzilla&In-Reply-To=%3CAANLkTi%3D9Uj1uDD5xAAO8uO8hoJNSz%2BMCObUyrGvQNzTR%40mail.gmail.com%3E" + TITLE="[Mageia-dev] Proposal for bugzilla">ahmadsamir3891 at gmail.com + </A><BR> + <I>Wed Dec 22 18:46:06 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001847.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001849.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1848">[ date ]</a> + <a href="thread.html#1848">[ thread ]</a> + <a href="subject.html#1848">[ subject ]</a> + <a href="author.html#1848">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 22 December 2010 18:37, Frederic Janssens <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">fjanss at gmail.com</A>> wrote: +><i> On 2010-12-22, Ahmad Samir <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">ahmadsamir3891 at gmail.com</A>> wrote: +</I>>><i> On 22 December 2010 01:32, Frederic Janssens <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">fjanss at gmail.com</A>> wrote: +</I>>>><i> On Wed, Dec 15, 2010 at 17:07, Michael Scherer <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">misc at zarb.org</A>> wrote: +</I>>>><i> +</I>>>><i> In preparation of the future interaction (by xmlrpc) between the +</I>>>><i> mageia-app-db site and the mageia bugzilla,  I have been testing +</I>>>><i> <A HREF="http://bugs.mageia.org/">http://bugs.mageia.org/</A> . +</I>>>><i> Xmlrpc works, but it will be necessary to configure additional fields. +</I>>>><i> The minimum would be to add an 'RPM Package' field (such as exists on +</I>>>><i> <A HREF="https://qa.mandriva.com/">https://qa.mandriva.com/</A>). +</I>>>><i> +</I>>><i> +</I>>><i> That's already agreed upon, whatever it's called, RPM Package or +</I>>><i> Component (I am in favour of the former). +</I>><i> +</I>><i> ok +</I>><i> +</I>>>><i> First I think it would be usefull to have a multiline (Large Text Box) +</I>>>><i> 'RPM Packages' field, instead of a single line (Free Text) field as +</I>>>><i> used by mandriva. +</I>>>><i> A single bug can concern more than one rpm. One thing mageia-app-db +</I>>>><i> will do is search all bugs affecting an rpm. For that search to be +</I>>>><i> meaningfull all affected rpms should be mentioned. +</I>>><i> +</I>>><i> 'One bug per report' is what we should do (did); if a bug originates +</I>>><i> from more than one package, a separate report for each of them should +</I>>><i> be opened with the Block/Dependency set correctly. +</I>><i> +</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> +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> (In fact I think I want to solve the same problem you want to solve with +</I>><i> "with a whiteboard field to state if the bug affects more than one release (at +</I>><i> least for now)" +</I>><i> but in a more specific manner). +</I>><i> +</I>>><i> +</I>>>><i> For the same reason, the way the rpms are mentioned should be +</I>>>><i> 'standardised', +</I>>>><i> as the search done by bugzilla can only be litteral. +</I>>>><i> +</I>>><i> +</I>>><i> Usually one doesn't only search in the RPM Package field; experience +</I>>><i> tell us that the affected package name will be mentioned many times in +</I>>><i> both the summary and the description. +</I>>><i> +</I>>><i> And if you want to search in the RPM Package field, bugzilla has many +</I>>><i> options to do so, look at the bottom of: +</I>>><i> <A HREF="https://qa.mandriva.com/query.cgi?format=advanced">https://qa.mandriva.com/query.cgi?format=advanced</A> +</I>><i> +</I>><i> Yes; but I am trying to solve the connection with mageia-app-db. +</I>><i> With the xmlrpc interface it seems the search possibilities are more limited : +</I>><i> (from <A HREF="http://www.bugzilla.org/docs/3.6/en/html/api/Bugzilla/WebService/Bug.html">http://www.bugzilla.org/docs/3.6/en/html/api/Bugzilla/WebService/Bug.html</A>) +</I>><i> : +</I>><i> +</I>><i> " +</I>><i> search +</I>><i> +</I>><i>    UNSTABLE +</I>><i> +</I>><i>    Description +</I>><i> +</I>><i>        Allows you to search for bugs based on particular criteria. +</I>><i>    Params +</I>><i> +</I>><i>        Unless otherwise specified in the description of a parameter, +</I>><i> bugs are returned if they match exactly the criteria you specify in +</I>><i> these parameters. That is, we don't match against substrings--if a bug +</I>><i> is in the "Widgets" product and you ask for bugs in the "Widg" +</I>><i> product, you won't get anything. +</I>><i> +</I>><i>        Criteria are joined in a logical AND. That is, you will be +</I>><i> returned bugs that match all of the criteria, not bugs that match any +</I>><i> of the criteria. +</I>><i> +</I>><i>        Each parameter can be either the type it says, or an array of +</I>><i> the types it says. If you pass an array, it means "Give me bugs with +</I>><i> any of these values." For example, if you wanted bugs that were in +</I>><i> either the "Foo" or "Bar" products, you'd pass: +</I>><i> +</I>><i>         product => ['Foo', 'Bar'] +</I>><i> " +</I>><i> +</I> +I don't know about xmlrpc, but there's no one certain way to fill the +'RPM Package' field; ideally it should be packagename-version-release +(e.g. kwrite-4.5.85-1mdv), whatever search method you use, it has to +be versatile enough to cope with the field content variations. + +FWIW, the best way to search a bugzilla is using the Advanced search +interface; just searching for the package name isn't enough. Usually +it's not a problem for active triage team members to spot duplicates +(from daily contacts with bug reports) and mark them as such. + +>><i> +</I>>>><i> Something that does not exist in mandriva, but I think would be usefull, +</I>>>><i> is a +</I>>>><i> 'Fixed RPM Packages' that would be filled when the bug is fixed. FIXED +</I>>>><i> is great, but where (or since which rpm)? +</I>>>><i> +</I>>><i> +</I>>><i> IMHO, that's trivia; either the user is savvy enough / has the time to +</I>>><i> trudge through the bug report to find out which package release fixes +</I>>><i> an issue (which indicates he's the curious type, he'll at least skim +</I>>><i> through the bug report anyway), or he's just going to update his +</I>>><i> system and get the fix (the latter happens more often). +</I>><i> +</I>><i> Here the 'user' is mageia-app-db. +</I>><i> +</I> +Then this is a premature question; you should wait first to see how +the updates in stable releases are going to be handled (will +everything have to go through the sec team? or sec team will only care +about the essential packages only?... etc because in that case a +security announcement is dispatched, you may be able to grab the +"fixed" version from there). + +><i> +</I>>><i> +</I>>>><i> Perhaps also an 'Upstream' field which would, eventually, indicate +</I>>>><i> where that bug is filed upstream. +</I>>>><i> +</I>>><i> +</I>>><i> That's similar to the URL field in my proposal (see my previous post +</I>>><i> in this thread). +</I>><i> +</I>><i> Ok. +</I>><i> +</I>>><i> +</I>>>><i> Finally the "status whiteboard" could be enabled, and used to clearly +</I>>>><i> explain a workaround, for open bugs (instead of having to figure it +</I>>>><i> from the comments). (Eventually this field could also be used as the +</I>>>><i> 'Fixed RPM Packages' field when the bug is closed. So it would be the +</I>>>><i> 'Solution' field) +</I>>>><i> +</I>>><i> +</I>>><i> I don't think this will be adequately useful; if the issue is fixed, +</I>>><i> then all the user has to do is update his system. If it's not fixed +</I>>><i> and affects a stable release then it should get added to the Errata +</I>>><i> page for that release whether there's a workaround (or not); if it +</I>><i> +</I>><i> Still another place to look at. If it concerns the bug it would be +</I>><i> better to have it visible in the bug. +</I>><i> +</I>>><i> affects Cauldron, well, Cauldron users are supposed to be +</I>>><i> fireproof-ready, so they do read bug reports (or skim through them). +</I>><i> +</I>><i> How is the case represented where the bug is in release, +</I>><i> and the fix is in cauldron ? +</I>><i> +</I> +Then it's not fixed in the afro-mentioned stable release, and should +be in the Errata (if it's an important package, of course). + +><i> +</I>>><i> +</I>>>><i> Apart from the "status whiteboard" which is a parameter to enable +</I>>>><i> (<A HREF="http://www.bugzilla.org/docs/tip/en/html/parameters.html">http://www.bugzilla.org/docs/tip/en/html/parameters.html</A>); +</I>>>><i> the fields must be added as custom-fields +</I>>>><i> (<A HREF="http://www.bugzilla.org/docs/3.6/en/html/custom-fields.html">http://www.bugzilla.org/docs/3.6/en/html/custom-fields.html</A>) +</I>>>><i> +</I>>>><i> +</I>>>><i> -- +</I>>>><i> +</I>>>><i> Frederic +</I>>>><i> +</I>>><i> +</I>>><i> +</I>>><i> +</I>>><i> -- +</I>>><i> Ahmad Samir +</I>>><i> +</I>><i> +</I>><i> +</I>><i> -- +</I>><i> +</I>><i> Frederic +</I>><i> +</I> + + +-- +Ahmad Samir +</PRE> + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001847.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001849.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1848">[ date ]</a> + <a href="thread.html#1848">[ thread ]</a> + <a href="subject.html#1848">[ subject ]</a> + <a href="author.html#1848">[ 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> diff --git a/zarb-ml/mageia-dev/20101222/001849.html b/zarb-ml/mageia-dev/20101222/001849.html new file mode 100644 index 000000000..e96ce6ab5 --- /dev/null +++ b/zarb-ml/mageia-dev/20101222/001849.html @@ -0,0 +1,208 @@ +<!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=%3CAANLkTimqFdmC4fzyrvoR491XLch319yu99w70%3DURVprn%40mail.gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001848.html"> + <LINK REL="Next" HREF="001851.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal for bugzilla</H1> + <B>Frederic Janssens</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20bugzilla&In-Reply-To=%3CAANLkTimqFdmC4fzyrvoR491XLch319yu99w70%3DURVprn%40mail.gmail.com%3E" + TITLE="[Mageia-dev] Proposal for bugzilla">fjanss at gmail.com + </A><BR> + <I>Wed Dec 22 20:25:20 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001848.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001851.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1849">[ date ]</a> + <a href="thread.html#1849">[ thread ]</a> + <a href="subject.html#1849">[ subject ]</a> + <a href="author.html#1849">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 2010-12-22, Ahmad Samir <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">ahmadsamir3891 at gmail.com</A>> wrote: +><i> On 22 December 2010 18:37, Frederic Janssens <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">fjanss at gmail.com</A>> wrote: +</I>>><i> On 2010-12-22, Ahmad Samir <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">ahmadsamir3891 at gmail.com</A>> wrote: +</I>>>><i> On 22 December 2010 01:32, Frederic Janssens <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">fjanss at gmail.com</A>> wrote: +</I> +>>>><i> First I think it would be usefull to have a multiline (Large Text Box) +</I>>>>><i> 'RPM Packages' field, instead of a single line (Free Text) field as +</I>>>>><i> used by mandriva. +</I>>>>><i> A single bug can concern more than one rpm. One thing mageia-app-db +</I>>>>><i> will do is search all bugs affecting an rpm. For that search to be +</I>>>>><i> meaningfull all affected rpms should be mentioned. +</I>>>><i> +</I>>>><i> 'One bug per report' is what we should do (did); if a bug originates +</I>>>><i> from more than one package, a separate report for each of them should +</I>>>><i> be opened with the Block/Dependency set correctly. +</I>>><i> +</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>><i> +</I>><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> +Sorry again, what I mean, and should have written, is : +'a bug manifests itself in one package, but in more than one -version-release'. + +>><i> (In fact I think I want to solve the same problem you want to solve with +</I>>><i> "with a whiteboard field to state if the bug affects more than one release +</I>>><i> (at +</I>>><i> least for now)" +</I>>><i> but in a more specific manner). +</I> + + +>><i> +</I>>>><i> +</I>>>>><i> For the same reason, the way the rpms are mentioned should be +</I>>>>><i> 'standardised', +</I>>>>><i> as the search done by bugzilla can only be litteral. +</I>>>>><i> +</I>>>><i> +</I>>>><i> Usually one doesn't only search in the RPM Package field; experience +</I>>>><i> tell us that the affected package name will be mentioned many times in +</I>>>><i> both the summary and the description. +</I>>>><i> +</I>>>><i> And if you want to search in the RPM Package field, bugzilla has many +</I>>>><i> options to do so, look at the bottom of: +</I>>>><i> <A HREF="https://qa.mandriva.com/query.cgi?format=advanced">https://qa.mandriva.com/query.cgi?format=advanced</A> +</I>>><i> +</I>>><i> Yes; but I am trying to solve the connection with mageia-app-db. +</I>>><i> With the xmlrpc interface it seems the search possibilities are more +</I>>><i> limited : +</I>>><i> (from +</I>>><i> <A HREF="http://www.bugzilla.org/docs/3.6/en/html/api/Bugzilla/WebService/Bug.html">http://www.bugzilla.org/docs/3.6/en/html/api/Bugzilla/WebService/Bug.html</A>) +</I>>><i> : +</I>>><i> +</I>>><i> " +</I>>><i> search +</I>>><i> +</I>>><i> UNSTABLE +</I>>><i> +</I>>><i> Description +</I>>><i> +</I>>><i> Allows you to search for bugs based on particular criteria. +</I>>><i> Params +</I>>><i> +</I>>><i> Unless otherwise specified in the description of a parameter, +</I>>><i> bugs are returned if they match exactly the criteria you specify in +</I>>><i> these parameters. That is, we don't match against substrings--if a bug +</I>>><i> is in the "Widgets" product and you ask for bugs in the "Widg" +</I>>><i> product, you won't get anything. +</I>>><i> +</I>>><i> Criteria are joined in a logical AND. That is, you will be +</I>>><i> returned bugs that match all of the criteria, not bugs that match any +</I>>><i> of the criteria. +</I>>><i> +</I>>><i> Each parameter can be either the type it says, or an array of +</I>>><i> the types it says. If you pass an array, it means "Give me bugs with +</I>>><i> any of these values." For example, if you wanted bugs that were in +</I>>><i> either the "Foo" or "Bar" products, you'd pass: +</I>>><i> +</I>>><i> product => ['Foo', 'Bar'] +</I>>><i> " +</I>>><i> +</I>><i> +</I>><i> I don't know about xmlrpc, but there's no one certain way to fill the +</I>><i> 'RPM Package' field; ideally it should be packagename-version-release +</I>><i> (e.g. kwrite-4.5.85-1mdv), +</I> +That's what I proposed in another post. +If that were the standard, there would be no problem for mageia-app-db. + +><i> whatever search method you use, it has to +</I>><i> be versatile enough to cope with the field content variations. +</I> +To be clear : as indicated above, +the limitation is in what bugzilla offers through it's xmlrpc interface. +We should have to modify the bugzilla code if we wanted access to it's +'advanced search' +through it's xmlrpc interface. + + +><i> +</I>><i> FWIW, the best way to search a bugzilla is using the Advanced search +</I>><i> interface; just searching for the package name isn't enough. Usually +</I>><i> it's not a problem for active triage team members to spot duplicates +</I>><i> (from daily contacts with bug reports) and mark them as such. +</I>><i> +</I>>>><i> +</I>>>>><i> Something that does not exist in mandriva, but I think would be usefull, +</I>>>>><i> is a +</I>>>>><i> 'Fixed RPM Packages' that would be filled when the bug is fixed. FIXED +</I>>>>><i> is great, but where (or since which rpm)? +</I>>>>><i> +</I>>>><i> +</I>>>><i> IMHO, that's trivia; either the user is savvy enough / has the time to +</I>>>><i> trudge through the bug report to find out which package release fixes +</I>>>><i> an issue (which indicates he's the curious type, he'll at least skim +</I>>>><i> through the bug report anyway), or he's just going to update his +</I>>>><i> system and get the fix (the latter happens more often). +</I>>><i> +</I>>><i> Here the 'user' is mageia-app-db. +</I>>><i> +</I>><i> +</I>><i> Then this is a premature question; you should wait first to see how +</I>><i> the updates in stable releases are going to be handled (will +</I>><i> everything have to go through the sec team? or sec team will only care +</I>><i> about the essential packages only?... etc because in that case a +</I>><i> security announcement is dispatched, you may be able to grab the +</I>><i> "fixed" version from there). +</I> +Ok + +>><i> How is the case represented where the bug is in release, +</I>>><i> and the fix is in cauldron ? +</I>>><i> +</I>><i> +</I>><i> Then it's not fixed in the afro-mentioned stable release, and should +</I>><i> be in the Errata (if it's an important package, of course). +</I>><i> +</I> +Ok + +-- + +Frederic +</PRE> + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001848.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001851.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1849">[ date ]</a> + <a href="thread.html#1849">[ thread ]</a> + <a href="subject.html#1849">[ subject ]</a> + <a href="author.html#1849">[ 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> diff --git a/zarb-ml/mageia-dev/20101222/001850.html b/zarb-ml/mageia-dev/20101222/001850.html new file mode 100644 index 000000000..23e9c03a8 --- /dev/null +++ b/zarb-ml/mageia-dev/20101222/001850.html @@ -0,0 +1,95 @@ +<!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=%3C201012222030.38158.r.h.michel%2Bmageia%40gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001858.html"> + <LINK REL="Next" HREF="001852.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal for bugzilla</H1> + <B>Renaud MICHEL</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20bugzilla&In-Reply-To=%3C201012222030.38158.r.h.michel%2Bmageia%40gmail.com%3E" + TITLE="[Mageia-dev] Proposal for bugzilla">r.h.michel+mageia at gmail.com + </A><BR> + <I>Wed Dec 22 20:30:38 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001858.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001852.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1850">[ date ]</a> + <a href="thread.html#1850">[ thread ]</a> + <a href="subject.html#1850">[ subject ]</a> + <a href="author.html#1850">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On mercredi 22 décembre 2010 at 18:46, Ahmad Samir wrote : +><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>><i> +</I>><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 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. + +-- +Renaud Michel +</PRE> + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001858.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001852.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1850">[ date ]</a> + <a href="thread.html#1850">[ thread ]</a> + <a href="subject.html#1850">[ subject ]</a> + <a href="author.html#1850">[ 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> diff --git a/zarb-ml/mageia-dev/20101222/001851.html b/zarb-ml/mageia-dev/20101222/001851.html new file mode 100644 index 000000000..acd9231b7 --- /dev/null +++ b/zarb-ml/mageia-dev/20101222/001851.html @@ -0,0 +1,187 @@ +<!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=%3CAANLkTikPaTi%3DN-Fy-eUeuQPEJC9Ep-ZDBOcKvgPP74F7%40mail.gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001849.html"> + <LINK REL="Next" HREF="001858.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal for bugzilla</H1> + <B>Ahmad Samir</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20bugzilla&In-Reply-To=%3CAANLkTikPaTi%3DN-Fy-eUeuQPEJC9Ep-ZDBOcKvgPP74F7%40mail.gmail.com%3E" + TITLE="[Mageia-dev] Proposal for bugzilla">ahmadsamir3891 at gmail.com + </A><BR> + <I>Wed Dec 22 20:34:18 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001849.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001858.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1851">[ date ]</a> + <a href="thread.html#1851">[ thread ]</a> + <a href="subject.html#1851">[ subject ]</a> + <a href="author.html#1851">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 22 December 2010 21:25, Frederic Janssens <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">fjanss at gmail.com</A>> wrote: +><i> On 2010-12-22, Ahmad Samir <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">ahmadsamir3891 at gmail.com</A>> wrote: +</I>>><i> On 22 December 2010 18:37, Frederic Janssens <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">fjanss at gmail.com</A>> wrote: +</I>>>><i> On 2010-12-22, Ahmad Samir <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">ahmadsamir3891 at gmail.com</A>> wrote: +</I>>>>><i> On 22 December 2010 01:32, Frederic Janssens <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">fjanss at gmail.com</A>> wrote: +</I>><i> +</I>>>>>><i> First I think it would be usefull to have a multiline (Large Text Box) +</I>>>>>><i> 'RPM Packages' field, instead of a single line (Free Text) field as +</I>>>>>><i> used by mandriva. +</I>>>>>><i> A single bug can concern more than one rpm. One thing mageia-app-db +</I>>>>>><i> will do is search all bugs affecting an rpm. For that search to be +</I>>>>>><i> meaningfull all affected rpms should be mentioned. +</I>>>>><i> +</I>>>>><i> 'One bug per report' is what we should do (did); if a bug originates +</I>>>>><i> from more than one package, a separate report for each of them should +</I>>>>><i> be opened with the Block/Dependency set correctly. +</I>>>><i> +</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>>><i> +</I>>><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> Sorry again, what I mean, and should have written, is : +</I>><i> 'a bug manifests itself in one package, but in more than one -version-release'. +</I>><i> +</I> +There's no way in bugzilla to do this at the moment (there's talk +about this being implemented in bugzilla-4.0, which I haven't tried +before). Traditionally the Whiteboard field was used for such issues +(or separate reports were opened for each affected stable release). +Having a multi-line RPM Package wouldn't be the way to go with this +(IMHO). + +>>><i> (In fact I think I want to solve the same problem you want to solve with +</I>>>><i> "with a whiteboard field to state if the bug affects more than one release +</I>>>><i> (at +</I>>>><i> least for now)" +</I>>>><i> but in a more specific manner). +</I>><i> +</I>><i> +</I>><i> +</I>>>><i> +</I>>>>><i> +</I>>>>>><i> For the same reason, the way the rpms are mentioned should be +</I>>>>>><i> 'standardised', +</I>>>>>><i> as the search done by bugzilla can only be litteral. +</I>>>>>><i> +</I>>>>><i> +</I>>>>><i> Usually one doesn't only search in the RPM Package field; experience +</I>>>>><i> tell us that the affected package name will be mentioned many times in +</I>>>>><i> both the summary and the description. +</I>>>>><i> +</I>>>>><i> And if you want to search in the RPM Package field, bugzilla has many +</I>>>>><i> options to do so, look at the bottom of: +</I>>>>><i> <A HREF="https://qa.mandriva.com/query.cgi?format=advanced">https://qa.mandriva.com/query.cgi?format=advanced</A> +</I>>>><i> +</I>>>><i> Yes; but I am trying to solve the connection with mageia-app-db. +</I>>>><i> With the xmlrpc interface it seems the search possibilities are more +</I>>>><i> limited : +</I>>>><i> (from +</I>>>><i> <A HREF="http://www.bugzilla.org/docs/3.6/en/html/api/Bugzilla/WebService/Bug.html">http://www.bugzilla.org/docs/3.6/en/html/api/Bugzilla/WebService/Bug.html</A>) +</I>>>><i> : +</I>>>><i> +</I>>>><i> " +</I>>>><i> search +</I>>>><i> +</I>>>><i>    UNSTABLE +</I>>>><i> +</I>>>><i>    Description +</I>>>><i> +</I>>>><i>        Allows you to search for bugs based on particular criteria. +</I>>>><i>    Params +</I>>>><i> +</I>>>><i>        Unless otherwise specified in the description of a parameter, +</I>>>><i> bugs are returned if they match exactly the criteria you specify in +</I>>>><i> these parameters. That is, we don't match against substrings--if a bug +</I>>>><i> is in the "Widgets" product and you ask for bugs in the "Widg" +</I>>>><i> product, you won't get anything. +</I>>>><i> +</I>>>><i>        Criteria are joined in a logical AND. That is, you will be +</I>>>><i> returned bugs that match all of the criteria, not bugs that match any +</I>>>><i> of the criteria. +</I>>>><i> +</I>>>><i>        Each parameter can be either the type it says, or an array of +</I>>>><i> the types it says. If you pass an array, it means "Give me bugs with +</I>>>><i> any of these values." For example, if you wanted bugs that were in +</I>>>><i> either the "Foo" or "Bar" products, you'd pass: +</I>>>><i> +</I>>>><i>         product => ['Foo', 'Bar'] +</I>>>><i> " +</I>>>><i> +</I>>><i> +</I>>><i> I don't know about xmlrpc, but there's no one certain way to fill the +</I>>><i> 'RPM Package' field; ideally it should be packagename-version-release +</I>>><i> (e.g. kwrite-4.5.85-1mdv), +</I>><i> +</I>><i> That's what I proposed in another post. +</I>><i> If that were the standard, there would be no problem for mageia-app-db. +</I>><i> +</I>>><i> whatever search method you use, it has to +</I>>><i> be versatile enough to cope with the field content variations. +</I>><i> +</I>><i> To be clear : as indicated above, +</I>><i> the limitation is in what bugzilla offers through it's xmlrpc interface. +</I>><i> We should have to modify the bugzilla code if we wanted access to it's +</I>><i> 'advanced search' +</I>><i> through it's xmlrpc interface. +</I>><i> +</I> +Whatever. As long as that doesn't affect the workflow of the triage +team or bugzilla's performance in general, I don't really care +whichever way it get implemented :) + +[...] + +><i> -- +</I>><i> +</I>><i> Frederic +</I>><i> +</I> + + +-- +Ahmad Samir +</PRE> + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001849.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001858.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1851">[ date ]</a> + <a href="thread.html#1851">[ thread ]</a> + <a href="subject.html#1851">[ subject ]</a> + <a href="author.html#1851">[ 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> diff --git a/zarb-ml/mageia-dev/20101222/001852.html b/zarb-ml/mageia-dev/20101222/001852.html new file mode 100644 index 000000000..3c8d0eb37 --- /dev/null +++ b/zarb-ml/mageia-dev/20101222/001852.html @@ -0,0 +1,109 @@ +<!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=%3CAANLkTiniFL6-EmdHfYBVJH9W8fk04k2yasfxby4uph-t%40mail.gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001850.html"> + <LINK REL="Next" HREF="001854.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal for bugzilla</H1> + <B>Ahmad Samir</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20bugzilla&In-Reply-To=%3CAANLkTiniFL6-EmdHfYBVJH9W8fk04k2yasfxby4uph-t%40mail.gmail.com%3E" + TITLE="[Mageia-dev] Proposal for bugzilla">ahmadsamir3891 at gmail.com + </A><BR> + <I>Wed Dec 22 20:38:06 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001850.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001854.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1852">[ date ]</a> + <a href="thread.html#1852">[ thread ]</a> + <a href="subject.html#1852">[ subject ]</a> + <a href="author.html#1852">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>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>> wrote: +><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>>><i> +</I>>><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 problematic +</I>><i> package, even if he has good knowledge of the way packages 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 may +</I>><i> 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 good +</I>><i> hint to the developer that he should investigate in the dependencies those +</I>><i> apps have in common. +</I>><i> +</I>><i> So if you accept only one package per bug report, it may be harder to find +</I>><i> the actual cause, as those two apps may be maintained by different people, +</I>><i> each investigating the problem for his own app. +</I>><i> +</I>><i> -- +</I>><i> Renaud Michel +</I>><i> +</I> +Sure, but there's strace and gdb crash backtraces, that's what devs +use to find where a crash/bug happens, whether it's in their +package/code or somewhere else. + +To be more clear it's "one bug per report", that bug originates from a +package, that's what gets to be put in the 'RPM Package' field; it's +not unheard of that the 'RPM Package' field is changed through out the +life cycle of a bug report. + +-- +Ahmad Samir +</PRE> + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001850.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001854.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1852">[ date ]</a> + <a href="thread.html#1852">[ thread ]</a> + <a href="subject.html#1852">[ subject ]</a> + <a href="author.html#1852">[ 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> diff --git a/zarb-ml/mageia-dev/20101222/001853.html b/zarb-ml/mageia-dev/20101222/001853.html new file mode 100644 index 000000000..f35bc525d --- /dev/null +++ b/zarb-ml/mageia-dev/20101222/001853.html @@ -0,0 +1,99 @@ +<!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=%3C201012222041.54871.maarten.vanraes%40gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001863.html"> + <LINK REL="Next" HREF="001841.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal for bugzilla</H1> + <B>Maarten Vanraes</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20bugzilla&In-Reply-To=%3C201012222041.54871.maarten.vanraes%40gmail.com%3E" + TITLE="[Mageia-dev] Proposal for bugzilla">maarten.vanraes at gmail.com + </A><BR> + <I>Wed Dec 22 20:41:54 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001863.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001841.html">[Mageia-dev] mageia sound tasks +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1853">[ date ]</a> + <a href="thread.html#1853">[ thread ]</a> + <a href="subject.html#1853">[ subject ]</a> + <a href="author.html#1853">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Op woensdag 22 december 2010 20:30:38 schreef Renaud MICHEL: +><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>><i> > +</I>><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 problematic +</I>><i> package, even if he has good knowledge of the way packages 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 may +</I>><i> 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 dependencies +</I>><i> those apps have in common. +</I>><i> +</I>><i> So if you accept only one package per bug report, it may be harder to find +</I>><i> the actual cause, as those two apps may be maintained by different people, +</I>><i> each investigating the problem for his own app. +</I> +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 +</PRE> + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001863.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001841.html">[Mageia-dev] mageia sound tasks +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1853">[ date ]</a> + <a href="thread.html#1853">[ thread ]</a> + <a href="subject.html#1853">[ subject ]</a> + <a href="author.html#1853">[ 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> diff --git a/zarb-ml/mageia-dev/20101222/001854.html b/zarb-ml/mageia-dev/20101222/001854.html new file mode 100644 index 000000000..91472887d --- /dev/null +++ b/zarb-ml/mageia-dev/20101222/001854.html @@ -0,0 +1,111 @@ +<!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=%3C201012222045.14027.maarten.vanraes%40gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001852.html"> + <LINK REL="Next" HREF="001855.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal for bugzilla</H1> + <B>Maarten Vanraes</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20bugzilla&In-Reply-To=%3C201012222045.14027.maarten.vanraes%40gmail.com%3E" + TITLE="[Mageia-dev] Proposal for bugzilla">maarten.vanraes at gmail.com + </A><BR> + <I>Wed Dec 22 20:45:13 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001852.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001855.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1854">[ date ]</a> + <a href="thread.html#1854">[ thread ]</a> + <a href="subject.html#1854">[ subject ]</a> + <a href="author.html#1854">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Op woensdag 22 december 2010 20:38:06 schreef Ahmad Samir: +><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>wrote: +><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>><i> >> +</I>><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>><i> > +</I>><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> +yes, but suppose there's a firefox issue and it appears to be a problem with a +system library, after it gets changed, people will never find this problem +again; since they look for firefox... +</PRE> + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001852.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001855.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1854">[ date ]</a> + <a href="thread.html#1854">[ thread ]</a> + <a href="subject.html#1854">[ subject ]</a> + <a href="author.html#1854">[ 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> diff --git a/zarb-ml/mageia-dev/20101222/001855.html b/zarb-ml/mageia-dev/20101222/001855.html new file mode 100644 index 000000000..b8da2f8ee --- /dev/null +++ b/zarb-ml/mageia-dev/20101222/001855.html @@ -0,0 +1,92 @@ +<!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=%3CAANLkTi%3DFQgNPbB107pgt4CmmdSr3%3Dr3Jg%2Bs7%3D1v3ZL3T%40mail.gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001854.html"> + <LINK REL="Next" HREF="001860.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal for bugzilla</H1> + <B>Ahmad Samir</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20bugzilla&In-Reply-To=%3CAANLkTi%3DFQgNPbB107pgt4CmmdSr3%3Dr3Jg%2Bs7%3D1v3ZL3T%40mail.gmail.com%3E" + TITLE="[Mageia-dev] Proposal for bugzilla">ahmadsamir3891 at gmail.com + </A><BR> + <I>Wed Dec 22 20:54:37 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001854.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001860.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1855">[ date ]</a> + <a href="thread.html#1855">[ thread ]</a> + <a href="subject.html#1855">[ subject ]</a> + <a href="author.html#1855">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 22 December 2010 21:45, Maarten Vanraes <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">maarten.vanraes at gmail.com</A>> wrote: +><i> Op woensdag 22 december 2010 20:38:06 schreef Ahmad Samir: +</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>><i> +</I> +In two years, I probably never used the "RPM Package" as a search +criteria (I don't have any statistics many people use it, my guess +would be a small number); I usually search in the "Comment"s with +"Contains all of the words" or "Contains all of the words/strings" +(not just in mdv bugzilla, but in any bugzilla I use, some of them +enable searching in the bug "Summary"); so you search for "firefox +crash bookmarks" or "firefox crash move tab" or "firefox hang quit", I +think that's what most users will do as the "RPM Package" is a bit +hidden at the bottom. + +IMHO, this is better, because a GTK2+ bug could affect a lot of GTK2+ +apps, I don't think it's ideal to list every single affected package +in the "RPM Package" field. The same goes for kdelibs or perl or +python or ffmpeg... etc. + +-- +Ahmad Samir +</PRE> + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001854.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001860.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1855">[ date ]</a> + <a href="thread.html#1855">[ thread ]</a> + <a href="subject.html#1855">[ subject ]</a> + <a href="author.html#1855">[ 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> diff --git a/zarb-ml/mageia-dev/20101222/001856.html b/zarb-ml/mageia-dev/20101222/001856.html new file mode 100644 index 000000000..16d2ce0c5 --- /dev/null +++ b/zarb-ml/mageia-dev/20101222/001856.html @@ -0,0 +1,84 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Choosing packagers representatives + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Choosing%20packagers%20representatives&In-Reply-To=%3C201012222122.24586.maarten.vanraes%40gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001845.html"> + <LINK REL="Next" HREF="001859.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Choosing packagers representatives</H1> + <B>Maarten Vanraes</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Choosing%20packagers%20representatives&In-Reply-To=%3C201012222122.24586.maarten.vanraes%40gmail.com%3E" + TITLE="[Mageia-dev] Choosing packagers representatives">maarten.vanraes at gmail.com + </A><BR> + <I>Wed Dec 22 21:22:24 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001845.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001859.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1856">[ date ]</a> + <a href="thread.html#1856">[ thread ]</a> + <a href="subject.html#1856">[ subject ]</a> + <a href="author.html#1856">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Op maandag 20 december 2010 23:19:11 schreef Anne nicolas: +><i> Hi there +</I>><i> +</I>><i> > - experience in packaging +</I>><i> > - willing to *manage* team +</I>><i> > - start with these 2 guys until first release is done (as done in i18n +</I>><i> > team) +</I>><i> +</I>><i> I'm applying for packagers reprentative rather on general management +</I>><i> side (organization,meetings, planning...)for the 5 coming months. I +</I>><i> would like to help in order to have a good start then when people know +</I>><i> each other new representatives are elected. +</I>><i> +</I>><i> I've been working in engineering team in Mandriva for the 6 last years +</I>><i> doing some packaging, working on isos release and managing relations +</I>><i> with Mandriva community. +</I>><i> +</I>><i> My full profile here: <A HREF="http://www.linkedin.com/profile/view?id=4195950">http://www.linkedin.com/profile/view?id=4195950</A> +</I>><i> +</I>><i> Cheers +</I> +I nominate Anne, if she's backed by an expert(god-level) packager +</PRE> + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001845.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001859.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1856">[ date ]</a> + <a href="thread.html#1856">[ thread ]</a> + <a href="subject.html#1856">[ subject ]</a> + <a href="author.html#1856">[ 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> diff --git a/zarb-ml/mageia-dev/20101222/001857.html b/zarb-ml/mageia-dev/20101222/001857.html new file mode 100644 index 000000000..39c7a575b --- /dev/null +++ b/zarb-ml/mageia-dev/20101222/001857.html @@ -0,0 +1,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=%3C20101222202539.GB17809%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="001844.html"> + <LINK REL="Next" HREF="001864.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=%3C20101222202539.GB17809%40sisay.ephaone.org%3E" + TITLE="[Mageia-dev] Proposal for bugzilla">misc at zarb.org + </A><BR> + <I>Wed Dec 22 21:25:39 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001844.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001864.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1857">[ date ]</a> + <a href="thread.html#1857">[ thread ]</a> + <a href="subject.html#1857">[ subject ]</a> + <a href="author.html#1857">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Wed, Dec 22, 2010 at 01:55:02PM +0100, Frederic Janssens wrote: +><i> On 2010-12-22, Michael Scherer <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">misc at zarb.org</A>> wrote: +</I>><i> > Le mercredi 22 décembre 2010 à 00:32 +0100, Frederic Janssens a écrit : +</I>><i> >> On Wed, Dec 15, 2010 at 17:07, Michael Scherer <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">misc at zarb.org</A>> wrote: +</I>><i> >> > +</I>><i> >> > Le mardi 14 décembre 2010 à 17:05 +0100, Dexter Morgan a écrit : +</I>><i> >> > > I would like to have your input to let us able to provide a bugzilla +</I>><i> >> > > really soon +</I>><i> >> > +</I>><i> >> > So if I am not wrong, in bugzilla, we have : +</I>><i> >> > - products +</I>><i> >> > - component, contained in products +</I>><i> >> > - and various field, per bug, +</I>><i> >> > +</I>><i> >> > and the way we organize everything will impact the layout. +</I>><i> >> > +</I>><i> >> +</I>><i> >> Yes. +</I>><i> >> +</I>><i> >> In preparation of the future interaction (by xmlrpc) between the +</I>><i> >> mageia-app-db site and the mageia bugzilla, I have been testing +</I>><i> >> <A HREF="http://bugs.mageia.org/">http://bugs.mageia.org/</A> . +</I>><i> >> Xmlrpc works, but it will be necessary to configure additional fields. +</I>><i> >> The minimum would be to add an 'RPM Package' field (such as exists on +</I>><i> >> <A HREF="https://qa.mandriva.com/">https://qa.mandriva.com/</A>). +</I>><i> > +</I>><i> > What about component not related to rpm ? +</I>><i> +</I>><i> The 'RPM Package' field would be left blank. +</I>><i> (usually many fields are left blank) +</I> +That's quite useless clutter in this case :/ + +><i> > +</I>><i> > And do you mean srpm or rpm ? +</I>><i> +</I>><i> On <A HREF="https://qa.mandriva.com/">https://qa.mandriva.com/</A> anything goes. +</I>><i> To permit consistent searches I think we should standardise. +</I>><i> The aim would to be to as specific as needed but not more; +</I>><i> as far as I know that would be : +</I>><i> +</I>><i> name-version-release +</I>><i> +</I>><i> unless the bug is architecture specific, where we would have : +</I>><i> +</I>><i> name-version-release.architecture +</I> +There is already a "architecture" field, afaik, as well as a version field, +no ? + +( I didn't check as I refuse to enter my password over a insecured http session ). + +And I think that giving rpm ( and not srpm ) will make search a little bit complex +in some corner cases ( can will also cause problem for the next point ). + +><i> > +</I>><i> > We should also take in account package naming change. +</I>><i> +</I>><i> which change? +</I> +Well, when a rpm change name, rename it in the field to be the new name, so not all bugs +are lost. + +-- +Michael Scherer +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001844.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001864.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1857">[ date ]</a> + <a href="thread.html#1857">[ thread ]</a> + <a href="subject.html#1857">[ subject ]</a> + <a href="author.html#1857">[ 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> diff --git a/zarb-ml/mageia-dev/20101222/001858.html b/zarb-ml/mageia-dev/20101222/001858.html new file mode 100644 index 000000000..c04f78560 --- /dev/null +++ b/zarb-ml/mageia-dev/20101222/001858.html @@ -0,0 +1,71 @@ +<!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=%3C20101222204101.GC17809%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="001851.html"> + <LINK REL="Next" HREF="001850.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=%3C20101222204101.GC17809%40sisay.ephaone.org%3E" + TITLE="[Mageia-dev] Proposal for bugzilla">misc at zarb.org + </A><BR> + <I>Wed Dec 22 21:41:01 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001851.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001850.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1858">[ date ]</a> + <a href="thread.html#1858">[ thread ]</a> + <a href="subject.html#1858">[ subject ]</a> + <a href="author.html#1858">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Wed, Dec 22, 2010 at 09:34:18PM +0200, Ahmad Samir wrote: +><i> On 22 December 2010 21:25, Frederic Janssens <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">fjanss at gmail.com</A>> wrote: +</I>><i> > Sorry again, what I mean, and should have written, is : +</I>><i> > 'a bug manifests itself in one package, but in more than one -version-release'. +</I>><i> > +</I>><i> +</I>><i> There's no way in bugzilla to do this at the moment (there's talk +</I>><i> about this being implemented in bugzilla-4.0, which I haven't tried +</I>><i> before). +</I> +Not before 4.2.X, according to meeting logs : +<A HREF="http://meetbot.mageia.org/mageia-meeting/2010/mageia-meeting.2010-11-08-19.06.log.html#l-102">http://meetbot.mageia.org/mageia-meeting/2010/mageia-meeting.2010-11-08-19.06.log.html#l-102</A> + +-- +Michael Scherer +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001851.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001850.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1858">[ date ]</a> + <a href="thread.html#1858">[ thread ]</a> + <a href="subject.html#1858">[ subject ]</a> + <a href="author.html#1858">[ 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> diff --git a/zarb-ml/mageia-dev/20101222/001859.html b/zarb-ml/mageia-dev/20101222/001859.html new file mode 100644 index 000000000..f67509e83 --- /dev/null +++ b/zarb-ml/mageia-dev/20101222/001859.html @@ -0,0 +1,114 @@ +<!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=%3C4D126DD8.9040806%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001856.html"> + <LINK REL="Next" HREF="001861.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=%3C4D126DD8.9040806%40laposte.net%3E" + TITLE="[Mageia-dev] Proposal for bugzilla">andr55 at laposte.net + </A><BR> + <I>Wed Dec 22 22:30:00 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001856.html">[Mageia-dev] Choosing packagers representatives +</A></li> + <LI>Next message: <A HREF="001861.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1859">[ date ]</a> + <a href="thread.html#1859">[ thread ]</a> + <a href="subject.html#1859">[ subject ]</a> + <a href="author.html#1859">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Dexter Morgan a écrit : +><i> +</I>><i> hello, +</I>><i> +</I>><i> now that we have a working bugzilla we need to have a working layout. +</I>><i> +</I>><i> i created a wiki page presenting what could be done. +</I>><i> <A HREF="http://mageia.org/wiki/doku.php?id=bugzilla">http://mageia.org/wiki/doku.php?id=bugzilla</A> +</I>><i> +</I>><i> I would like to have your input to let us able to provide a bugzilla really soon +</I>><i> +</I>><i> +</I>><i> In the bugreport creation we were thinking of using the mdv way or the +</I>><i> fedora way. +</I>><i> +</I>><i> +</I>><i> Fedora way is to add all srpms in the componment field but there is 2 +</I>><i> pbs with this way : +</I>><i> +</I>><i> -> Users don't know what is a rpms ( like what is the srpms for kwrite ) +</I>><i> -> This slow down the bugzilla too much +</I> +Reaction from an end-user that has filed/commented/viewed a lot of bug +reports. + +- I like the idea of separating +-- main bug reports. +All releases together. A lot of end-users are not very aware of the +version/release of the software with the bug until they are well into +the reporting process. So selecting the release would be better delayed +to the bug report entry page. +Plus the idea of eventually having bugs applying to multiple releases +(mentioned on another post) sounds good, as well. + +-- documentation +Tends to be reported/corrected by different people than software bugs. + +-- localisation (maybe combined with documentation ?) +Also tends to be reported by different people than software bugs, and +corrected by translators. + +-- cauldron + +- Better to avoid listing .srpm's. Most end-users filing bug reports +have no idea what they are. So no point in slowing down bugzilla for that. +And from the .rpm, packagers/developers will be able to find the .srpm +quickly enough. + +- The idea of a multiline .rpm field (mentioned on another post) seems +an excellent idea. Better to list all related .rpm's in one location +than putting additional .rpms into the description and/or comment +fields. (Not only for mageia-app-db.) + +my 2 cents :) +</PRE> + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001856.html">[Mageia-dev] Choosing packagers representatives +</A></li> + <LI>Next message: <A HREF="001861.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1859">[ date ]</a> + <a href="thread.html#1859">[ thread ]</a> + <a href="subject.html#1859">[ subject ]</a> + <a href="author.html#1859">[ 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> diff --git a/zarb-ml/mageia-dev/20101222/001860.html b/zarb-ml/mageia-dev/20101222/001860.html new file mode 100644 index 000000000..ee1d05d2a --- /dev/null +++ b/zarb-ml/mageia-dev/20101222/001860.html @@ -0,0 +1,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> diff --git a/zarb-ml/mageia-dev/20101222/001861.html b/zarb-ml/mageia-dev/20101222/001861.html new file mode 100644 index 000000000..a9ffb23f7 --- /dev/null +++ b/zarb-ml/mageia-dev/20101222/001861.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=%3C201012222323.26718.maarten.vanraes%40gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001859.html"> + + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal for bugzilla</H1> + <B>Maarten Vanraes</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20bugzilla&In-Reply-To=%3C201012222323.26718.maarten.vanraes%40gmail.com%3E" + TITLE="[Mageia-dev] Proposal for bugzilla">maarten.vanraes at gmail.com + </A><BR> + <I>Wed Dec 22 23:23:26 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001859.html">[Mageia-dev] Proposal for bugzilla +</A></li> + + <LI> <B>Messages sorted by:</B> + <a href="date.html#1861">[ date ]</a> + <a href="thread.html#1861">[ thread ]</a> + <a href="subject.html#1861">[ subject ]</a> + <a href="author.html#1861">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Op woensdag 22 december 2010 22:30:00 schreef andre999: +><i> Dexter Morgan a écrit : +</I>><i> > hello, +</I>><i> > +</I>><i> > now that we have a working bugzilla we need to have a working layout. +</I>><i> > +</I>><i> > i created a wiki page presenting what could be done. +</I>><i> > <A HREF="http://mageia.org/wiki/doku.php?id=bugzilla">http://mageia.org/wiki/doku.php?id=bugzilla</A> +</I>><i> > +</I>><i> > I would like to have your input to let us able to provide a bugzilla +</I>><i> > really soon +</I>><i> > +</I>><i> > +</I>><i> > In the bugreport creation we were thinking of using the mdv way or the +</I>><i> > fedora way. +</I>><i> > +</I>><i> > +</I>><i> > Fedora way is to add all srpms in the componment field but there is 2 +</I>><i> > pbs with this way : +</I>><i> > +</I>><i> > -> Users don't know what is a rpms ( like what is the srpms for kwrite ) +</I>><i> > -> This slow down the bugzilla too much +</I>><i> +</I>><i> Reaction from an end-user that has filed/commented/viewed a lot of bug +</I>><i> reports. +</I>><i> +</I>><i> - I like the idea of separating +</I>><i> -- main bug reports. +</I>><i> All releases together. A lot of end-users are not very aware of the +</I>><i> version/release of the software with the bug until they are well into +</I>><i> the reporting process. So selecting the release would be better delayed +</I>><i> to the bug report entry page. +</I>><i> Plus the idea of eventually having bugs applying to multiple releases +</I>><i> (mentioned on another post) sounds good, as well. +</I>><i> +</I>><i> -- documentation +</I>><i> Tends to be reported/corrected by different people than software bugs. +</I> +good call + +><i> -- localisation (maybe combined with documentation ?) +</I>><i> Also tends to be reported by different people than software bugs, and +</I>><i> corrected by translators. +</I> +again good call + +><i> -- cauldron +</I> +i doubt this + +><i> - Better to avoid listing .srpm's. Most end-users filing bug reports +</I>><i> have no idea what they are. So no point in slowing down bugzilla for that. +</I>><i> And from the .rpm, packagers/developers will be able to find the .srpm +</I>><i> quickly enough. +</I> +actually, the triage team finds this alot quicker than package maintainers, +they often only care about their own package, and if it's not assigned to +their package they won't be looking for it. + +i do agree that users often have no clue of what specific component is +responsible for what, and they often get it wrong if they try. + +><i> - The idea of a multiline .rpm field (mentioned on another post) seems +</I>><i> an excellent idea. Better to list all related .rpm's in one location +</I>><i> than putting additional .rpms into the description and/or comment +</I>><i> fields. (Not only for mageia-app-db.) +</I>><i> +</I>><i> my 2 cents :) +</I></PRE> + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001859.html">[Mageia-dev] Proposal for bugzilla +</A></li> + + <LI> <B>Messages sorted by:</B> + <a href="date.html#1861">[ date ]</a> + <a href="thread.html#1861">[ thread ]</a> + <a href="subject.html#1861">[ subject ]</a> + <a href="author.html#1861">[ 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> diff --git a/zarb-ml/mageia-dev/20101222/001862.html b/zarb-ml/mageia-dev/20101222/001862.html new file mode 100644 index 000000000..0c3a288c2 --- /dev/null +++ b/zarb-ml/mageia-dev/20101222/001862.html @@ -0,0 +1,81 @@ +<!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=%3C201012222325.16148.stormi%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001860.html"> + <LINK REL="Next" HREF="001863.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal for bugzilla</H1> + <B>Samuel Verschelde</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20bugzilla&In-Reply-To=%3C201012222325.16148.stormi%40laposte.net%3E" + TITLE="[Mageia-dev] Proposal for bugzilla">stormi at laposte.net + </A><BR> + <I>Wed Dec 22 23:25:16 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001860.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001863.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1862">[ date ]</a> + <a href="thread.html#1862">[ thread ]</a> + <a href="subject.html#1862">[ subject ]</a> + <a href="author.html#1862">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le mercredi 22 décembre 2010 22:58:44, andre999 a écrit : +><i> +</I>><i> Maarten Vanraes a écrit : +</I>><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>><i> +</I>><i> If we agree that a bug can originate in more than one package, a +</I>><i> multiline (multi-rpm) field could be useful. +</I> +No need for a multiline field. If we agree that the field, by convention, can contain one rpm name (common case) or more, separated by commas for example, then it wont add complexity over the initial proposal from Ahmad and would still allow people to flag more RPMs if they want. + +From the bug solving point of view, this would not add much benefit, but for users it may bring some useful information, for example in mageia-app-db. Indeed, like it was said earlier, if the problem shows in package A but is in fact a bug in package B, it's still useful to have package A mentioned so that we can say, on the package's page in mageia-app-db "Hey, there's a known open bug for this package". + + +Regards + +Samuel Verschelde +</PRE> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001860.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001863.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1862">[ date ]</a> + <a href="thread.html#1862">[ thread ]</a> + <a href="subject.html#1862">[ subject ]</a> + <a href="author.html#1862">[ 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> diff --git a/zarb-ml/mageia-dev/20101222/001863.html b/zarb-ml/mageia-dev/20101222/001863.html new file mode 100644 index 000000000..08d8fd33c --- /dev/null +++ b/zarb-ml/mageia-dev/20101222/001863.html @@ -0,0 +1,91 @@ +<!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=%3C201012222329.42636.maarten.vanraes%40gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001862.html"> + <LINK REL="Next" HREF="001853.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal for bugzilla</H1> + <B>Maarten Vanraes</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20bugzilla&In-Reply-To=%3C201012222329.42636.maarten.vanraes%40gmail.com%3E" + TITLE="[Mageia-dev] Proposal for bugzilla">maarten.vanraes at gmail.com + </A><BR> + <I>Wed Dec 22 23:29:42 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001862.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001853.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1863">[ date ]</a> + <a href="thread.html#1863">[ thread ]</a> + <a href="subject.html#1863">[ subject ]</a> + <a href="author.html#1863">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Op woensdag 22 december 2010 23:25:16 schreef Samuel Verschelde: +><i> Le mercredi 22 décembre 2010 22:58:44, andre999 a écrit : +</I>><i> > Maarten Vanraes a écrit : +</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> > > +</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>><i> > +</I>><i> > If we agree that a bug can originate in more than one package, a +</I>><i> > multiline (multi-rpm) field could be useful. +</I>><i> +</I>><i> No need for a multiline field. If we agree that the field, by convention, +</I>><i> can contain one rpm name (common case) or more, separated by commas for +</I>><i> example, then it wont add complexity over the initial proposal from Ahmad +</I>><i> and would still allow people to flag more RPMs if they want. +</I>><i> +</I>><i> From the bug solving point of view, this would not add much benefit, but +</I>><i> for users it may bring some useful information, for example in +</I>><i> mageia-app-db. Indeed, like it was said earlier, if the problem shows in +</I>><i> package A but is in fact a bug in package B, it's still useful to have +</I>><i> package A mentioned so that we can say, on the package's page in +</I>><i> mageia-app-db "Hey, there's a known open bug for this package". +</I>><i> +</I>><i> +</I>><i> Regards +</I>><i> +</I>><i> Samuel Verschelde +</I> + +good compromise +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001862.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001853.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1863">[ date ]</a> + <a href="thread.html#1863">[ thread ]</a> + <a href="subject.html#1863">[ subject ]</a> + <a href="author.html#1863">[ 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> diff --git a/zarb-ml/mageia-dev/20101222/001864.html b/zarb-ml/mageia-dev/20101222/001864.html new file mode 100644 index 000000000..bace494fe --- /dev/null +++ b/zarb-ml/mageia-dev/20101222/001864.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=%3C201012222334.35990.stormi%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001857.html"> + <LINK REL="Next" HREF="001846.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal for bugzilla</H1> + <B>Samuel Verschelde</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20bugzilla&In-Reply-To=%3C201012222334.35990.stormi%40laposte.net%3E" + TITLE="[Mageia-dev] Proposal for bugzilla">stormi at laposte.net + </A><BR> + <I>Wed Dec 22 23:34:35 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001857.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001846.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1864">[ date ]</a> + <a href="thread.html#1864">[ thread ]</a> + <a href="subject.html#1864">[ subject ]</a> + <a href="author.html#1864">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le mercredi 22 décembre 2010 21:25:39, Michael scherer a écrit : +><i> +</I>><i> On Wed, Dec 22, 2010 at 01:55:02PM +0100, Frederic Janssens wrote: +</I>><i> > On 2010-12-22, Michael Scherer <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">misc at zarb.org</A>> wrote: +</I>><i> > > Le mercredi 22 décembre 2010 à 00:32 +0100, Frederic Janssens a écrit : +</I>><i> > >> On Wed, Dec 15, 2010 at 17:07, Michael Scherer <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">misc at zarb.org</A>> wrote: +</I>><i> > >> > +</I>><i> > >> > Le mardi 14 décembre 2010 à 17:05 +0100, Dexter Morgan a écrit : +</I>><i> > >> > > I would like to have your input to let us able to provide a bugzilla +</I>><i> > >> > > really soon +</I>><i> > >> > +</I>><i> > >> > So if I am not wrong, in bugzilla, we have : +</I>><i> > >> > - products +</I>><i> > >> > - component, contained in products +</I>><i> > >> > - and various field, per bug, +</I>><i> > >> > +</I>><i> > >> > and the way we organize everything will impact the layout. +</I>><i> > >> > +</I>><i> > >> +</I>><i> > >> Yes. +</I>><i> > >> +</I>><i> > >> In preparation of the future interaction (by xmlrpc) between the +</I>><i> > >> mageia-app-db site and the mageia bugzilla, I have been testing +</I>><i> > >> <A HREF="http://bugs.mageia.org/">http://bugs.mageia.org/</A> . +</I>><i> > >> Xmlrpc works, but it will be necessary to configure additional fields. +</I>><i> > >> The minimum would be to add an 'RPM Package' field (such as exists on +</I>><i> > >> <A HREF="https://qa.mandriva.com/">https://qa.mandriva.com/</A>). +</I>><i> > > +</I>><i> > > What about component not related to rpm ? +</I>><i> > +</I>><i> > The 'RPM Package' field would be left blank. +</I>><i> > (usually many fields are left blank) +</I>><i> +</I>><i> That's quite useless clutter in this case :/ +</I>><i> +</I>><i> > > +</I>><i> > > And do you mean srpm or rpm ? +</I>><i> > +</I>><i> > On <A HREF="https://qa.mandriva.com/">https://qa.mandriva.com/</A> anything goes. +</I>><i> > To permit consistent searches I think we should standardise. +</I>><i> > The aim would to be to as specific as needed but not more; +</I>><i> > as far as I know that would be : +</I>><i> > +</I>><i> > name-version-release +</I>><i> > +</I>><i> > unless the bug is architecture specific, where we would have : +</I>><i> > +</I>><i> > name-version-release.architecture +</I>><i> +</I>><i> There is already a "architecture" field, afaik, as well as a version field, +</I>><i> no ? +</I>><i> +</I>><i> ( I didn't check as I refuse to enter my password over a insecured http session ). +</I>><i> +</I>><i> And I think that giving rpm ( and not srpm ) will make search a little bit complex +</I>><i> in some corner cases ( can will also cause problem for the next point ). +</I>><i> +</I> +So you think the (S)RPM field should only contain SRPM filenames ? + +If yes, I agree with that, because as Frederic stated above, in current Mandriva bugzilla, there's no enforced rule for that. You can put anything in the field, and you often end up with rpm filenames, or simple package names (e.g. "virtualbox"). + +However asking bug reporters to know the SRPM is too much, so this rule can only be enforced on Packagers and Triage Team side I think. This is already how it works on qa.mandriva.com : if you know the SRPM, you put it, if not someone will triage and do it for you. + +Ahmad, would there be a problem in enforcing such a policy (i.e. SRPM field should be empty or contain a valid SRPM name ? Where valid means "looks like the name of a SRPM") ? + +Regards + +Samuel Verschelde +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001857.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001846.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1864">[ date ]</a> + <a href="thread.html#1864">[ thread ]</a> + <a href="subject.html#1864">[ subject ]</a> + <a href="author.html#1864">[ 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> diff --git a/zarb-ml/mageia-dev/20101222/author.html b/zarb-ml/mageia-dev/20101222/author.html new file mode 100644 index 000000000..86670c0ca --- /dev/null +++ b/zarb-ml/mageia-dev/20101222/author.html @@ -0,0 +1,177 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <title>The Mageia-dev 22 December 2010 Archive by author</title> + <META NAME="robots" CONTENT="noindex,follow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <a name="start"></A> + <h1>22 December 2010 Archives by author</h1> + <ul> + <li> <b>Messages sorted by:</b> + <a href="thread.html#start">[ thread ]</a> + <a href="subject.html#start">[ subject ]</a> + + <a href="date.html#start">[ date ]</a> + + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p><b>Starting:</b> <i>Wed Dec 22 00:32:32 CET 2010</i><br> + <b>Ending:</b> <i>Wed Dec 22 23:34:35 CET 2010</i><br> + <b>Messages:</b> 26<p> + <ul> + +<LI><A HREF="001841.html">[Mageia-dev] mageia sound tasks +</A><A NAME="1841"> </A> +<I>Thomas Backlund +</I> + +<LI><A HREF="001839.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1839"> </A> +<I>Frederic Janssens +</I> + +<LI><A HREF="001844.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1844"> </A> +<I>Frederic Janssens +</I> + +<LI><A HREF="001847.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1847"> </A> +<I>Frederic Janssens +</I> + +<LI><A HREF="001849.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1849"> </A> +<I>Frederic Janssens +</I> + +<LI><A HREF="001850.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1850"> </A> +<I>Renaud MICHEL +</I> + +<LI><A HREF="001845.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1845"> </A> +<I>Ahmad Samir +</I> + +<LI><A HREF="001846.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1846"> </A> +<I>Ahmad Samir +</I> + +<LI><A HREF="001848.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1848"> </A> +<I>Ahmad Samir +</I> + +<LI><A HREF="001851.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1851"> </A> +<I>Ahmad Samir +</I> + +<LI><A HREF="001852.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1852"> </A> +<I>Ahmad Samir +</I> + +<LI><A HREF="001855.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1855"> </A> +<I>Ahmad Samir +</I> + +<LI><A HREF="001840.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1840"> </A> +<I>Michael Scherer +</I> + +<LI><A HREF="001842.html">[Mageia-dev] mageia sound tasks +</A><A NAME="1842"> </A> +<I>Sascha Schneider +</I> + +<LI><A HREF="001853.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1853"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="001854.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1854"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="001856.html">[Mageia-dev] Choosing packagers representatives +</A><A NAME="1856"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="001861.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1861"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="001863.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1863"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="001862.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1862"> </A> +<I>Samuel Verschelde +</I> + +<LI><A HREF="001864.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1864"> </A> +<I>Samuel Verschelde +</I> + +<LI><A HREF="001859.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1859"> </A> +<I>andre999 +</I> + +<LI><A HREF="001860.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1860"> </A> +<I>andre999 +</I> + +<LI><A HREF="001843.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1843"> </A> +<I>Romain d'Alverny +</I> + +<LI><A HREF="001857.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1857"> </A> +<I>Michael scherer +</I> + +<LI><A HREF="001858.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1858"> </A> +<I>Michael scherer +</I> + + </ul> + <p> + <a name="end"><b>Last message date:</b></a> + <i>Wed Dec 22 23:34:35 CET 2010</i><br> + <b>Archived on:</b> <i>Wed Dec 22 23:34:47 CET 2010</i> + <p> + <ul> + <li> <b>Messages sorted by:</b> + <a href="thread.html#start">[ thread ]</a> + <a href="subject.html#start">[ subject ]</a> + + <a href="date.html#start">[ date ]</a> + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p> + <hr> + <i>This archive was generated by + Pipermail 0.09 (Mailman edition).</i> + </BODY> +</HTML> + diff --git a/zarb-ml/mageia-dev/20101222/date.html b/zarb-ml/mageia-dev/20101222/date.html new file mode 100644 index 000000000..a059fa9e8 --- /dev/null +++ b/zarb-ml/mageia-dev/20101222/date.html @@ -0,0 +1,177 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <title>The Mageia-dev 22 December 2010 Archive by date</title> + <META NAME="robots" CONTENT="noindex,follow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <a name="start"></A> + <h1>22 December 2010 Archives by date</h1> + <ul> + <li> <b>Messages sorted by:</b> + <a href="thread.html#start">[ thread ]</a> + <a href="subject.html#start">[ subject ]</a> + <a href="author.html#start">[ author ]</a> + + + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p><b>Starting:</b> <i>Wed Dec 22 00:32:32 CET 2010</i><br> + <b>Ending:</b> <i>Wed Dec 22 23:34:35 CET 2010</i><br> + <b>Messages:</b> 26<p> + <ul> + +<LI><A HREF="001839.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1839"> </A> +<I>Frederic Janssens +</I> + +<LI><A HREF="001840.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1840"> </A> +<I>Michael Scherer +</I> + +<LI><A HREF="001841.html">[Mageia-dev] mageia sound tasks +</A><A NAME="1841"> </A> +<I>Thomas Backlund +</I> + +<LI><A HREF="001842.html">[Mageia-dev] mageia sound tasks +</A><A NAME="1842"> </A> +<I>Sascha Schneider +</I> + +<LI><A HREF="001843.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1843"> </A> +<I>Romain d'Alverny +</I> + +<LI><A HREF="001844.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1844"> </A> +<I>Frederic Janssens +</I> + +<LI><A HREF="001845.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1845"> </A> +<I>Ahmad Samir +</I> + +<LI><A HREF="001846.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1846"> </A> +<I>Ahmad Samir +</I> + +<LI><A HREF="001847.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1847"> </A> +<I>Frederic Janssens +</I> + +<LI><A HREF="001848.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1848"> </A> +<I>Ahmad Samir +</I> + +<LI><A HREF="001849.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1849"> </A> +<I>Frederic Janssens +</I> + +<LI><A HREF="001850.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1850"> </A> +<I>Renaud MICHEL +</I> + +<LI><A HREF="001851.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1851"> </A> +<I>Ahmad Samir +</I> + +<LI><A HREF="001852.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1852"> </A> +<I>Ahmad Samir +</I> + +<LI><A HREF="001853.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1853"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="001854.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1854"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="001855.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1855"> </A> +<I>Ahmad Samir +</I> + +<LI><A HREF="001856.html">[Mageia-dev] Choosing packagers representatives +</A><A NAME="1856"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="001857.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1857"> </A> +<I>Michael scherer +</I> + +<LI><A HREF="001858.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1858"> </A> +<I>Michael scherer +</I> + +<LI><A HREF="001859.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1859"> </A> +<I>andre999 +</I> + +<LI><A HREF="001860.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1860"> </A> +<I>andre999 +</I> + +<LI><A HREF="001861.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1861"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="001862.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1862"> </A> +<I>Samuel Verschelde +</I> + +<LI><A HREF="001863.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1863"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="001864.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1864"> </A> +<I>Samuel Verschelde +</I> + + </ul> + <p> + <a name="end"><b>Last message date:</b></a> + <i>Wed Dec 22 23:34:35 CET 2010</i><br> + <b>Archived on:</b> <i>Wed Dec 22 23:34:47 CET 2010</i> + <p> + <ul> + <li> <b>Messages sorted by:</b> + <a href="thread.html#start">[ thread ]</a> + <a href="subject.html#start">[ subject ]</a> + <a href="author.html#start">[ author ]</a> + + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p> + <hr> + <i>This archive was generated by + Pipermail 0.09 (Mailman edition).</i> + </BODY> +</HTML> + diff --git a/zarb-ml/mageia-dev/20101222/index.html b/zarb-ml/mageia-dev/20101222/index.html new file mode 120000 index 000000000..db4b46f72 --- /dev/null +++ b/zarb-ml/mageia-dev/20101222/index.html @@ -0,0 +1 @@ +thread.html
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/20101222/subject.html b/zarb-ml/mageia-dev/20101222/subject.html new file mode 100644 index 000000000..1008754d9 --- /dev/null +++ b/zarb-ml/mageia-dev/20101222/subject.html @@ -0,0 +1,177 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <title>The Mageia-dev 22 December 2010 Archive by subject</title> + <META NAME="robots" CONTENT="noindex,follow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <a name="start"></A> + <h1>22 December 2010 Archives by subject</h1> + <ul> + <li> <b>Messages sorted by:</b> + <a href="thread.html#start">[ thread ]</a> + + <a href="author.html#start">[ author ]</a> + <a href="date.html#start">[ date ]</a> + + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p><b>Starting:</b> <i>Wed Dec 22 00:32:32 CET 2010</i><br> + <b>Ending:</b> <i>Wed Dec 22 23:34:35 CET 2010</i><br> + <b>Messages:</b> 26<p> + <ul> + +<LI><A HREF="001856.html">[Mageia-dev] Choosing packagers representatives +</A><A NAME="1856"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="001841.html">[Mageia-dev] mageia sound tasks +</A><A NAME="1841"> </A> +<I>Thomas Backlund +</I> + +<LI><A HREF="001842.html">[Mageia-dev] mageia sound tasks +</A><A NAME="1842"> </A> +<I>Sascha Schneider +</I> + +<LI><A HREF="001839.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1839"> </A> +<I>Frederic Janssens +</I> + +<LI><A HREF="001840.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1840"> </A> +<I>Michael Scherer +</I> + +<LI><A HREF="001843.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1843"> </A> +<I>Romain d'Alverny +</I> + +<LI><A HREF="001844.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1844"> </A> +<I>Frederic Janssens +</I> + +<LI><A HREF="001845.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1845"> </A> +<I>Ahmad Samir +</I> + +<LI><A HREF="001846.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1846"> </A> +<I>Ahmad Samir +</I> + +<LI><A HREF="001847.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1847"> </A> +<I>Frederic Janssens +</I> + +<LI><A HREF="001848.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1848"> </A> +<I>Ahmad Samir +</I> + +<LI><A HREF="001849.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1849"> </A> +<I>Frederic Janssens +</I> + +<LI><A HREF="001850.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1850"> </A> +<I>Renaud MICHEL +</I> + +<LI><A HREF="001851.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1851"> </A> +<I>Ahmad Samir +</I> + +<LI><A HREF="001852.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1852"> </A> +<I>Ahmad Samir +</I> + +<LI><A HREF="001853.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1853"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="001854.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1854"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="001855.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1855"> </A> +<I>Ahmad Samir +</I> + +<LI><A HREF="001857.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1857"> </A> +<I>Michael scherer +</I> + +<LI><A HREF="001858.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1858"> </A> +<I>Michael scherer +</I> + +<LI><A HREF="001859.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1859"> </A> +<I>andre999 +</I> + +<LI><A HREF="001860.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1860"> </A> +<I>andre999 +</I> + +<LI><A HREF="001861.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1861"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="001862.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1862"> </A> +<I>Samuel Verschelde +</I> + +<LI><A HREF="001863.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1863"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="001864.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1864"> </A> +<I>Samuel Verschelde +</I> + + </ul> + <p> + <a name="end"><b>Last message date:</b></a> + <i>Wed Dec 22 23:34:35 CET 2010</i><br> + <b>Archived on:</b> <i>Wed Dec 22 23:34:47 CET 2010</i> + <p> + <ul> + <li> <b>Messages sorted by:</b> + <a href="thread.html#start">[ thread ]</a> + + <a href="author.html#start">[ author ]</a> + <a href="date.html#start">[ date ]</a> + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p> + <hr> + <i>This archive was generated by + Pipermail 0.09 (Mailman edition).</i> + </BODY> +</HTML> + diff --git a/zarb-ml/mageia-dev/20101222/thread.html b/zarb-ml/mageia-dev/20101222/thread.html new file mode 100644 index 000000000..2eb81125f --- /dev/null +++ b/zarb-ml/mageia-dev/20101222/thread.html @@ -0,0 +1,217 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <title>The Mageia-dev 22 December 2010 Archive by thread</title> + <META NAME="robots" CONTENT="noindex,follow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <a name="start"></A> + <h1>22 December 2010 Archives by thread</h1> + <ul> + <li> <b>Messages sorted by:</b> + + <a href="subject.html#start">[ subject ]</a> + <a href="author.html#start">[ author ]</a> + <a href="date.html#start">[ date ]</a> + + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p><b>Starting:</b> <i>Wed Dec 22 00:32:32 CET 2010</i><br> + <b>Ending:</b> <i>Wed Dec 22 23:34:35 CET 2010</i><br> + <b>Messages:</b> 26<p> + <ul> + +<!--0 01292974352- --> +<LI><A HREF="001839.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1839"> </A> +<I>Frederic Janssens +</I> + +<UL> +<!--1 01292974352-01292977686- --> +<LI><A HREF="001840.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1840"> </A> +<I>Michael Scherer +</I> + +<UL> +<!--2 01292974352-01292977686-01293022502- --> +<LI><A HREF="001844.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1844"> </A> +<I>Frederic Janssens +</I> + +<UL> +<!--3 01292974352-01292977686-01293022502-01293049539- --> +<LI><A HREF="001857.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1857"> </A> +<I>Michael scherer +</I> + +<!--3 01292974352-01292977686-01293022502-01293049539-01293057275- --> +<LI><A HREF="001864.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1864"> </A> +<I>Samuel Verschelde +</I> + +</UL> +</UL> +<!--1 01292974352-01293028029- --> +<LI><A HREF="001846.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1846"> </A> +<I>Ahmad Samir +</I> + +<UL> +<!--2 01292974352-01293028029-01293035839- --> +<LI><A HREF="001847.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1847"> </A> +<I>Frederic Janssens +</I> + +<UL> +<!--3 01292974352-01293028029-01293035839-01293039966- --> +<LI><A HREF="001848.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1848"> </A> +<I>Ahmad Samir +</I> + +<!--3 01292974352-01293028029-01293035839-01293039966-01293045920- --> +<LI><A HREF="001849.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1849"> </A> +<I>Frederic Janssens +</I> + +<!--3 01292974352-01293028029-01293035839-01293039966-01293045920-01293046458- --> +<LI><A HREF="001851.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1851"> </A> +<I>Ahmad Samir +</I> + +<!--3 01292974352-01293028029-01293035839-01293039966-01293045920-01293046458-01293050461- --> +<LI><A HREF="001858.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1858"> </A> +<I>Michael scherer +</I> + +<!--3 01292974352-01293028029-01293035839-01293039966-01293046238- --> +<LI><A HREF="001850.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1850"> </A> +<I>Renaud MICHEL +</I> + +<!--3 01292974352-01293028029-01293035839-01293039966-01293046238-01293046686- --> +<LI><A HREF="001852.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1852"> </A> +<I>Ahmad Samir +</I> + +<!--3 01292974352-01293028029-01293035839-01293039966-01293046238-01293046686-01293047113- --> +<LI><A HREF="001854.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1854"> </A> +<I>Maarten Vanraes +</I> + +<!--3 01292974352-01293028029-01293035839-01293039966-01293046238-01293046686-01293047113-01293047677- --> +<LI><A HREF="001855.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1855"> </A> +<I>Ahmad Samir +</I> + +<!--3 01292974352-01293028029-01293035839-01293039966-01293046238-01293046686-01293047113-01293055124- --> +<LI><A HREF="001860.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1860"> </A> +<I>andre999 +</I> + +<!--3 01292974352-01293028029-01293035839-01293039966-01293046238-01293046686-01293047113-01293055124-01293056716- --> +<LI><A HREF="001862.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1862"> </A> +<I>Samuel Verschelde +</I> + +<!--3 01292974352-01293028029-01293035839-01293039966-01293046238-01293046686-01293047113-01293055124-01293056716-01293056982- --> +<LI><A HREF="001863.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1863"> </A> +<I>Maarten Vanraes +</I> + +<!--3 01292974352-01293028029-01293035839-01293039966-01293046238-01293046914- --> +<LI><A HREF="001853.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1853"> </A> +<I>Maarten Vanraes +</I> + +</UL> +</UL> +</UL> +<!--0 01293011463- --> +<LI><A HREF="001841.html">[Mageia-dev] mageia sound tasks +</A><A NAME="1841"> </A> +<I>Thomas Backlund +</I> + +<UL> +<!--1 01293011463-01293015919- --> +<LI><A HREF="001842.html">[Mageia-dev] mageia sound tasks +</A><A NAME="1842"> </A> +<I>Sascha Schneider +</I> + +</UL> +<!--0 01293016041- --> +<LI><A HREF="001843.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1843"> </A> +<I>Romain d'Alverny +</I> + +<!--0 01293026922- --> +<LI><A HREF="001845.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1845"> </A> +<I>Ahmad Samir +</I> + +<!--0 01293049344- --> +<LI><A HREF="001856.html">[Mageia-dev] Choosing packagers representatives +</A><A NAME="1856"> </A> +<I>Maarten Vanraes +</I> + +<!--0 01293053400- --> +<LI><A HREF="001859.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1859"> </A> +<I>andre999 +</I> + +<UL> +<!--1 01293053400-01293056606- --> +<LI><A HREF="001861.html">[Mageia-dev] Proposal for bugzilla +</A><A NAME="1861"> </A> +<I>Maarten Vanraes +</I> + +</UL> + </ul> + <p> + <a name="end"><b>Last message date:</b></a> + <i>Wed Dec 22 23:34:35 CET 2010</i><br> + <b>Archived on:</b> <i>Wed Dec 22 23:34:47 CET 2010</i> + <p> + <ul> + <li> <b>Messages sorted by:</b> + + <a href="subject.html#start">[ subject ]</a> + <a href="author.html#start">[ author ]</a> + <a href="date.html#start">[ date ]</a> + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p> + <hr> + <i>This archive was generated by + Pipermail 0.09 (Mailman edition).</i> + </BODY> +</HTML> + |