diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20101222/001848.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20101222/001848.html | 249 |
1 files changed, 249 insertions, 0 deletions
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> |