1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
|
<!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=%3C201012251227.19056.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="001893.html">
<LINK REL="Next" HREF="001898.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=%3C201012251227.19056.maarten.vanraes%40gmail.com%3E"
TITLE="[Mageia-dev] Proposal for bugzilla">maarten.vanraes at gmail.com
</A><BR>
<I>Sat Dec 25 12:27:18 CET 2010</I>
<P><UL>
<LI>Previous message: <A HREF="001893.html">[Mageia-dev] Proposal for bugzilla
</A></li>
<LI>Next message: <A HREF="001898.html">[Mageia-dev] Proposal for bugzilla
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1894">[ date ]</a>
<a href="thread.html#1894">[ thread ]</a>
<a href="subject.html#1894">[ subject ]</a>
<a href="author.html#1894">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Op zaterdag 25 december 2010 12:02:18 schreef andre999:
><i> Maarten Vanraes a écrit :
</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>>
</I>wrote:
><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
</I>><i> >>> or 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> >>
</I>><i> >> $ rpm -q --qf '{sourcerpm}' {pkg-name}
</I>><i> >>
</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>><i>
</I>><i> That part I understand.
</I>><i> Only these values will be downloaded, so some online traffic.
</I>><i>
</I>><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>><i>
</I>><i> Your numbers are right. Obviously I had one too many zeros.
</I>><i>
</I>><i> > consider also the fact that these are src.rpm , so huge lib**** and the
</I>><i> > fact that we won't be starting with everything...
</I>><i>
</I>><i> I was thinking of lib*, which is why I said more than 3 characters.
</I>><i>
</I>><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>><i>
</I>><i> Actually, I was trying brainstorming. We all know that such ideas don't
</I>><i> necessarily lead anywhere.
</I>><i> It is certain that your idea is a lot better than it first appeared.
</I>
yeah, sorry, i (and misc) just am trying to suggest an idea that gets broken
off by people who don't even seem to get it; coupled with less sleep and my
cranky, i could've worded it better
><i> However, invoking the rpm command has certain advantages.
</I>><i> Most importantly, if done on the system of the user finding the bug, it
</I>><i> reports exactly the correct version of the srpm.
</I>><i>
</I>><i> For example, on my system, if I type in the console exactly :
</I>><i>
</I>><i> rpm -q --qf '%{sourcerpm}' binutils
</I>><i>
</I>><i> _without_ the version, it returns :
</I>><i>
</I>><i> binutils-2.19.51.0.2-1mnb2.src.rpm
</I>><i>
</I>><i> _with_ the version, which is exactly what we want.
</I>><i>
</I>><i> So I have a suggestion.
</I>><i> With your Ajax skills, I imagine that you would be capable of setting a
</I>><i> button which automatically invokes that command on a binary rpm field,
</I>><i> to fill a srpm field ?
</I>><i> Could you try that as well ?
</I>><i> If it works, then I think we would have a better solution.
</I>
i'm not certain that is required, iirc, the command to find this stuff is out
there; and the info can be found on mageia-app-db i think.
however, if it isn't a src.rpm but a perfect match for a binary rpm, i guess
we could return the src.rpm instead.
><i> I could try it, but my html/javascript skills are quite limited.
</I>><i> Just a suggestion.
</I>><i>
</I>><i> Regards
</I>><i>
</I>><i> André
</I></PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="001893.html">[Mageia-dev] Proposal for bugzilla
</A></li>
<LI>Next message: <A HREF="001898.html">[Mageia-dev] Proposal for bugzilla
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1894">[ date ]</a>
<a href="thread.html#1894">[ thread ]</a>
<a href="subject.html#1894">[ subject ]</a>
<a href="author.html#1894">[ 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>
|
