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