diff options
| author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
|---|---|---|
| committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
| commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
| tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/20101225/001893.html | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-master.tar archives-master.tar.gz archives-master.tar.bz2 archives-master.tar.xz archives-master.zip | |
Diffstat (limited to 'zarb-ml/mageia-dev/20101225/001893.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20101225/001893.html | 165 |
1 files changed, 165 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101225/001893.html b/zarb-ml/mageia-dev/20101225/001893.html new file mode 100644 index 000000000..afb8fe1ea --- /dev/null +++ b/zarb-ml/mageia-dev/20101225/001893.html @@ -0,0 +1,165 @@ +<!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=%3C4D15CF3A.3080403%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001892.html"> + <LINK REL="Next" HREF="001894.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=%3C4D15CF3A.3080403%40laposte.net%3E" + TITLE="[Mageia-dev] Proposal for bugzilla">andr55 at laposte.net + </A><BR> + <I>Sat Dec 25 12:02:18 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001892.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001894.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1893">[ date ]</a> + <a href="thread.html#1893">[ thread ]</a> + <a href="subject.html#1893">[ subject ]</a> + <a href="author.html#1893">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Maarten Vanraes a écrit : +><i> +</I>><i> Op zaterdag 25 december 2010 10:18:17 schreef andre999: +</I>>><i> Maarten Vanraes a écrit : +</I>>>><i> Op donderdag 23 december 2010 22:23:56 schreef Ahmad Samir: +</I>>>>><i> On 23 December 2010 22:01, Samuel Verschelde<<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">stormi at laposte.net</A>> wrote: +</I>>>>>><i> I remember some years ago you could choose the exact version of the +</I>>>>>><i> package for which you reported a bug, from a list. I agree that +</I>>>>>><i> improving the UI side helpers could be useful. +</I>>>>>><i> +</I>>>>>><i> Regards +</I>>>>>><i> +</I>>>>>><i> Samuel Verschelde +</I>>>>><i> +</I>>>>><i> As was said by dmorgan, listing each SRPM slowed down bugzilla a lot; +</I>>>>><i> the distro has a lot of SRPMS... +</I>>>><i> +</I>>>><i> an ajax search is better; it doesn't add much and only gets searched if +</I>>>><i> you enter at least 2 chars, or something like that. +</I>>>><i> +</I>>>><i> if such an ajax is wanted, i can write that if i can use app-mageia-db or +</I>>>><i> similar as a list. +</I>>><i> +</I>>><i> OK, I did a little search on Ajax, and I think that I understand now. +</I>>><i> It seems that you're proposing autocompletion on the text typed in the +</I>>><i> field - and only matches will be downloaded. +</I>>><i> But if it starts with 2 characters, there could be still 1000's of names +</I>>><i> downloaded. +</I>>><i> I would suggest that we would need at least 5 characters to restrict the +</I>>><i> names downloaded to a reasonable number. +</I>>><i> +</I>>><i> Also, there is another factor. If we are looking for srpm names, but +</I>>><i> the user enters binary rpm names, there will not necessarily be a match, +</I>>><i> particularly if the srpm results in more than one binary rpm. +</I>>><i> So in some cases this will not work. +</I>>><i> +</I>>><i> But I have another idea. +</I>>><i> Maybe we could have separate (binary) rpm and srpm fields. +</I>>><i> There is a button on the page, which will invoke the command to give the +</I>>><i> srpms associated with the binary rpms. +</I>>><i> Would this be workable ? +</I>>><i> Something that would execute +</I>>><i> $ rpm -q --qf '{sourcerpm}' {pkg-name} +</I>>><i> and would automatically enter the result in the srpm field, or at least +</I>>><i> display it so it could be typed in. +</I>>><i> +</I>>><i> Of course, this would have to be done by the user experiencing the +</I>>><i> problems, to ensure having the correct version. +</I>>><i> We would also have to deal with the cases where more than one rpm has +</I>>><i> the bug. +</I>>><i> +</I>>><i> If we can automate this, we can dispense with the potential problems +</I>>><i> associated with a list of srpms. And it would be (at least somewhat) +</I>>><i> more efficient both server and client side, as well. +</I>>><i> +</I>>><i> Just an idea +</I>>><i> +</I>>><i> André +</I>><i> +</I>><i> this is no more than sort of TAB completion on the urpmi commands. +</I> +That part I understand. +Only these values will be downloaded, so some online traffic. + +><i> averagely 2 characters have ~600 possibilities; meaning that 2 chars give +</I>><i> average 25 srpm results. in practice this can be 150 results or something +</I> +Your numbers are right. Obviously I had one too many zeros. + +><i> consider also the fact that these are src.rpm , so huge lib**** and the fact +</I>><i> that we won't be starting with everything... +</I> +I was thinking of lib*, which is why I said more than 3 characters. + +><i> imho instead of destroying an idea you don't know much about; why don't i +</I>><i> implement it and then you can evaluate if it's bad or not. +</I> +Actually, I was trying brainstorming. We all know that such ideas don't +necessarily lead anywhere. +It is certain that your idea is a lot better than it first appeared. + +However, invoking the rpm command has certain advantages. +Most importantly, if done on the system of the user finding the bug, it +reports exactly the correct version of the srpm. + +For example, on my system, if I type in the console exactly : + +rpm -q --qf '%{sourcerpm}' binutils + +_without_ the version, it returns : + +binutils-2.19.51.0.2-1mnb2.src.rpm + +_with_ the version, which is exactly what we want. + +So I have a suggestion. +With your Ajax skills, I imagine that you would be capable of setting a +button which automatically invokes that command on a binary rpm field, +to fill a srpm field ? +Could you try that as well ? +If it works, then I think we would have a better solution. + +I could try it, but my html/javascript skills are quite limited. +Just a suggestion. + +Regards + +André +</PRE> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001892.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001894.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1893">[ date ]</a> + <a href="thread.html#1893">[ thread ]</a> + <a href="subject.html#1893">[ subject ]</a> + <a href="author.html#1893">[ 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> |