Re: [Cooker] bugzilla package list a bit short
Am Freitag, 31. Oktober 2003, 12:17:04 Uhr MET, schrieb Glenn Burkhardt: I also notice that the link to the stable version bug database is incorrect; it should be http://bugs.mandrakelinux.com/ (see screen shot, attached). Arrgh, could you please avoid attachments on this list? Some people use a modem to read the cooker list. Thanks, Götz -- What difference does it make to the dead, the orphans and the homeless, whether the mad destruction is wrought under the name of totalitarianism or the holy name of liberty or democracy? Mahatma Gandhi (1869 - 1948), Non-Violence in Peace and War
[Cooker] bugzilla package list a bit short
How does one report a bug to specific packages on Bugzilla? The list of packages is a bit short, as compared to the query page. I'd like to submit a bug for the xfig package. Thanks.
Re: [Cooker] bugzilla package list a bit short
Am Freitag, 31. Oktober 2003, 10:47:49 Uhr MET, schrieb Glenn Burkhardt: How does one report a bug to specific packages on Bugzilla? The list of packages is a bit short, as compared to the query page. I'd like to submit a bug for the xfig package. You're right, the package list is currently broken. You'll have to wait for someone fixing this. -- What difference does it make to the dead, the orphans and the homeless, whether the mad destruction is wrought under the name of totalitarianism or the holy name of liberty or democracy? Mahatma Gandhi (1869 - 1948), Non-Violence in Peace and War
Re: [Cooker] bugzilla package list a bit short
Götz Waschk wrote: Am Freitag, 31. Oktober 2003, 10:47:49 Uhr MET, schrieb Glenn Burkhardt: How does one report a bug to specific packages on Bugzilla? The list of packages is a bit short, as compared to the query page. I'd like to submit a bug for the xfig package. You're right, the package list is currently broken. You'll have to wait for someone fixing this. Also, what is broken is the listed current version. Sometimes 4.4-9mdk is labeled (current) when the 4.4-37mdk is on the list. If you choose the real latest version, there is a scary message saying that probably your bug report will be ignored :/ Eric
Re: [Cooker] Bugzilla update
when viewing my buglist from the bugzilla main page, I get an internal server error ... the URL causing it is: http://qa.mandrakesoft.com/buglist.cgi?bug_status=UNCONFIRMEDbug_status=NEWbug_status=ASSIGNEDbug_status=NEEDINFObug_status=REOPENEDemail1=udo%40vibe.acemailtype1=exactemailassigned_to1=1emailreporter1=1 happy hacking udo Am Wed, 22 Oct 2003 17:32:54 + schrieb Warly: I have merge the bugzilla CVS into qa.mandrakesoft.com. Warn for any error. Moreover I have try to make it a bit faster, shortcircuiting a very slow function and removing the product choice from the bug edition pages (this decrease the page size from 400 KB to about 50 KB) -- Well, if we were to build it idiot proof, someone would build a better idiot. Civilme
Re: [Cooker] Bugzilla update
Warly wrote: Lea Gris [EMAIL PROTECTED] writes: Maybe if mod_gzip was onabled on qa.mandrakesoft.com this would make page loading much faster and less bandwidth hungry. mod_gzip is not yet ported to apache2 Besides, it's more the query time (on the server side) and the rendering time (client-side) that makes a difference. On even a moderately high-speed connection, I could see potential for compression to actually *add* to the download time, if any difference would even be perceptible. I like the solution using the link to a separate page. Kudos to Warly for implementing this suggestion (I forget whose it was) before the 10.0 cycle. - John
[Cooker] [bugzilla] a bug without any status
this bug http://qa.mandrakesoft.com/show_bug.cgi?id=4960 has no status (neither invalid, nor resolved or anything else) - is that correct? or is this a new way of bug extinction :-) happy hacking udo -- Well, if we were to build it idiot proof, someone would build a better idiot. Civilme
[Cooker] Bugzilla update
I have merge the bugzilla CVS into qa.mandrakesoft.com. Warn for any error. Moreover I have try to make it a bit faster, shortcircuiting a very slow function and removing the product choice from the bug edition pages (this decrease the page size from 400 KB to about 50 KB) -- Warly
Re: [Cooker] Bugzilla update
Warly [EMAIL PROTECTED] writes: I have merge the bugzilla CVS into qa.mandrakesoft.com. Warn for any error. Moreover I have try to make it a bit faster, shortcircuiting a very slow function and removing the product choice from the bug edition pages (this decrease the page size from 400 KB to about 50 KB) i love you morpheous !
Re: [Cooker] Bugzilla update
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thierry Vignaud wrote: | Warly [EMAIL PROTECTED] writes: | | |I have merge the bugzilla CVS into qa.mandrakesoft.com. | |Warn for any error. | |Moreover I have try to make it a bit faster, shortcircuiting a very |slow function and removing the product choice from the bug edition |pages (this decrease the page size from 400 KB to about 50 KB) | | | i love you morpheous ! Maybe if mod_gzip was onabled on qa.mandrakesoft.com this would make page loading much faster and less bandwidth hungry. - -- ~ Léa Gris () Campagne du ruban texte brut contre les courriels en HTML, /\ contre les pièces jointes Microsoft. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/lucYiNTO/wgn58kRAhxlAKCcNy9mv7Tw80ruDedsJdJs7qp2MgCdGn49 j3+/aosOdJTCxW7MCrLUWak= =x0u9 -END PGP SIGNATURE-
Re: [Cooker] Bugzilla update
Lea Gris [EMAIL PROTECTED] writes: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thierry Vignaud wrote: | Warly [EMAIL PROTECTED] writes: | | |I have merge the bugzilla CVS into qa.mandrakesoft.com. | |Warn for any error. | |Moreover I have try to make it a bit faster, shortcircuiting a very |slow function and removing the product choice from the bug edition |pages (this decrease the page size from 400 KB to about 50 KB) | | | i love you morpheous ! Maybe if mod_gzip was onabled on qa.mandrakesoft.com this would make page loading much faster and less bandwidth hungry. mod_gzip is not yet ported to apache2 -- Warly
Re: [Cooker] Bugzilla update
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Warly wrote: || i love you morpheous ! | |Maybe if mod_gzip was onabled on qa.mandrakesoft.com this would make |page loading much faster and less bandwidth hungry. | | | mod_gzip is not yet ported to apache2 It as been already replaced by output module deflate for the same purpose in Apache 2.0 : http://httpd.apache.org/docs-2.0/mod/mod_deflate.html - -- ~ Léa Gris () Campagne du ruban texte brut contre les courriels en HTML, /\ contre les pièces jointes Microsoft. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/luywiNTO/wgn58kRArM3AJ4jDDh2H1bgqrEfHGNU854im17SgQCgnl7o cNSBTh4/Z1djx2SKz4MU3ac= =NMZh -END PGP SIGNATURE-
Re: [Cooker] Bugzilla update
On Wed, Oct 22, 2003 at 10:30:36PM +0200, Warly wrote: Lea Gris [EMAIL PROTECTED] writes: Maybe if mod_gzip was onabled on qa.mandrakesoft.com this would make page loading much faster and less bandwidth hungry. mod_gzip is not yet ported to apache2 what about mod_deflate (which is in main)? L. -- Luca Berra -- [EMAIL PROTECTED] Communication Media Services S.r.l. /\ \ / ASCII RIBBON CAMPAIGN XAGAINST HTML MAIL / \
Re: [Cooker] Bugzilla update
onsdagen den 22 oktober 2003 22.30 skrev Warly: Lea Gris [EMAIL PROTECTED] writes: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thierry Vignaud wrote: | Warly [EMAIL PROTECTED] writes: |I have merge the bugzilla CVS into qa.mandrakesoft.com. | |Warn for any error. | |Moreover I have try to make it a bit faster, shortcircuiting a very |slow function and removing the product choice from the bug edition |pages (this decrease the page size from 400 KB to about 50 KB) | | i love you morpheous ! Maybe if mod_gzip was onabled on qa.mandrakesoft.com this would make page loading much faster and less bandwidth hungry. mod_gzip is not yet ported to apache2 Yes it has, but it won't work ;) Also mod_deflate is what you need.
[Cooker] bugzilla
It seems bugzilla accounts are identified by email address. This is a bit of a problem, as mine is still registered as [EMAIL PROTECTED] , an address that no longer works. I looked for a change address option but couldn't see one, and it'd be nice to keep my account instead of opening a new one for this address. Would it be possible for a bugzilla admin to change this? -- adamw
Re: [Cooker] Bugzilla down?
Am Mittwoch, 27. August 2003, 00:40:40 Uhr MET, schrieb Warly: Gettting forbidden error on qa.mandrakesoft.com fixed :) It's not fixed for me: http://qa.mandrakesoft.com/show_bug.cgi?id=4918 -- What difference does it make to the dead, the orphans and the homeless, whether the mad destruction is wrought under the name of totalitarianism or the holy name of liberty or democracy? Mahatma Gandhi (1869 - 1948), Non-Violence in Peace and War
Re: [Cooker] Bugzilla down?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Götz Waschk wrote: Am Mittwoch, 27. August 2003, 00:40:40 Uhr MET, schrieb Warly: Gettting forbidden error on qa.mandrakesoft.com fixed :) It's not fixed for me: http://qa.mandrakesoft.com/show_bug.cgi?id=4918 It's not possible to view/search for bug reports, but it is not possible to post, and probably not to modify: http://qa.mandrakesoft.com/short_desc=Zenity%20emulation%20of%20gdialog%20is%20broken...keywords=form_name=enter_bug Forbidden You don't have permission to access /short_desc=Zenity emulation of gdialog is broken (at least for --menu)comment ... Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request. - -- |--Another happy Mandrake Club member--| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x202 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE/TJzbrJK6UGDSBKcRAvkjAJ4sj2YpyO+ozMSNmewBDwIuD00I8QCfYaT3 Ut/I41DzSUtMhmEqPIx8Bag= =DeLm -END PGP SIGNATURE- * Please click on http://www.cae.co.za/disclaimer.htm to read our e-mail disclaimer or send an e-mail to [EMAIL PROTECTED] for a copy. *
Re: [Cooker] Bugzilla down?
On Wednesday 27 August 2003 14:38, Steffen Barszus wrote: Am Mittwoch, 27. August 2003 13:58 schrieb Buchan Milne: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Götz Waschk wrote: Am Mittwoch, 27. August 2003, 00:40:40 Uhr MET, schrieb Warly: Gettting forbidden error on qa.mandrakesoft.com fixed :) It's not fixed for me: http://qa.mandrakesoft.com/show_bug.cgi?id=4918 It's not possible to view/search for bug reports, but it is not possible to post, and probably not to modify: http://qa.mandrakesoft.com/short_desc=Zenity%20emulation%20of%20gd ia log%20is%20broken...keywords=form_name=enter_bug Forbidden You don't have permission to access /short_desc=Zenity emulation of gdialog is broken (at least for --menu)comment ... Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request. Yep that is what i get since weeks now, but nobody seems to have recognized that yet. It works for me, and i guess for other too so, there is something strange. are you using a proxy ? on which navigator ? can you tell me what did you try exactly to do ? -- Mickaël Scherer
Re: [Cooker] Bugzilla down?
Am Mittwoch, 27. August 2003 13:58 schrieb Buchan Milne: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Götz Waschk wrote: Am Mittwoch, 27. August 2003, 00:40:40 Uhr MET, schrieb Warly: Gettting forbidden error on qa.mandrakesoft.com fixed :) It's not fixed for me: http://qa.mandrakesoft.com/show_bug.cgi?id=4918 It's not possible to view/search for bug reports, but it is not possible to post, and probably not to modify: http://qa.mandrakesoft.com/short_desc=Zenity%20emulation%20of%20gdia log%20is%20broken...keywords=form_name=enter_bug Forbidden You don't have permission to access /short_desc=Zenity emulation of gdialog is broken (at least for --menu)comment ... Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request. Yep that is what i get since weeks now, but nobody seems to have recognized that yet. Steffen
Re: [Cooker] Bugzilla down?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Steffen Barszus wrote: Am Mittwoch, 27. August 2003 13:58 schrieb Buchan Milne: Götz Waschk wrote: Am Mittwoch, 27. August 2003, 00:40:40 Uhr MET, schrieb Warly: Gettting forbidden error on qa.mandrakesoft.com fixed :) It's not fixed for me: http://qa.mandrakesoft.com/show_bug.cgi?id=4918 It's not possible to view/search for bug reports, but it is not possible to post, and probably not to modify: http://qa.mandrakesoft.com/short_desc=Zenity%20emulation%20of%20gdia log%20is%20broken...keywords=form_name=enter_bug Forbidden You don't have permission to access /short_desc=Zenity emulation of gdialog is broken (at least for --menu)comment ... Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request. Yep that is what i get since weeks now, but nobody seems to have recognized that yet. I haven't had problems before, and this one just went through ... Regards, Buchan - -- |--Another happy Mandrake Club member--| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x202 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE/TLZtrJK6UGDSBKcRAlFUAJ4snEaxsgSolK8LVpZL7DYohkWgKwCbBm1c ImCJwpKk+zm/CuK5hW2y+zQ= =SqWw -END PGP SIGNATURE- * Please click on http://www.cae.co.za/disclaimer.htm to read our e-mail disclaimer or send an e-mail to [EMAIL PROTECTED] for a copy. *
Re: [Cooker] Bugzilla down?
Am Mittwoch, 27. August 2003 15:45 schrieb Michael Scherer: On Wednesday 27 August 2003 14:38, Steffen Barszus wrote: Am Mittwoch, 27. August 2003 13:58 schrieb Buchan Milne: http://qa.mandrakesoft.com/short_desc=Zenity%20emulation%20of%20 gd ia log%20is%20broken...keywords=form_name=enter_bug Forbidden You don't have permission to access /short_desc=Zenity emulation of gdialog is broken (at least for --menu)comment ... Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request. Yep that is what i get since weeks now, but nobody seems to have recognized that yet. It works for me, and i guess for other too so, there is something strange. Yep, seems so, as i get new bugzilla mails, so others seem able to post. are you using a proxy ? Nope on which navigator ? Konquerror can you tell me what did you try exactly to do ? I have tried to post a new bug. From what i have discovered it seemed to be a parsing error somehow, at least bugzilla took all content of the post past the first slash as url, what of course wont work. My mail should be in cooker mailinglist archiv, if you want the complete text i tried to enter. Greets Steffen
Re: [Cooker] Bugzilla down?
Am Mittwoch, 27. August 2003 15:47 schrieb Buchan Milne: Yep that is what i get since weeks now, but nobody seems to have recognized that yet. I haven't had problems before, and this one just went through ... Well i had a quick try remembering that the webservers have moved recently. I have deleted all cookies related to qa.linux-mandrake.com and now it have worked. Had a related issue with club too. So it seems its a konquerror issue or at least related. Steffen
RE: [Cooker] Bugzilla down?
Gettting forbidden error on qa.mandrakesoft.com Cory Meisch CPEA Test Technician HP deskjet linux team member Hewlett-Packard Vancouver (360) 212-7009 [EMAIL PROTECTED] Think that's strange then check out http://qa.mandrakesoft.com/wiki/ This page is temporarily closed in protest against software patents. Websites may soon be closed down regularly due to software patents. Software patents can get you prosecuted for publishing texts you wrote yourself! You will be redirected to swpat.ffii.org in 30 seconds for more information. To enter this site, click here.
Re: [Cooker] Bugzilla down?
MEISCH,CORY (HP-Vancouver,ex1) [EMAIL PROTECTED] writes: Gettting forbidden error on qa.mandrakesoft.com fixed :) -- Warly
[Cooker] Bugzilla mail-sending problems?
I added comments for a one bug in the bugzilla but I did not see any mail in the cooker for that bug. Does anybody know is this intentional or is there something wrong in the bugzilla. (Is cooker removed from the cc-targets where bugs are send) Mika
Re: [Cooker] Bugzilla New Bug error today
Frank Griffin [EMAIL PROTECTED] writes: This morning, I bring up Bugzilla's main page, log in, select Enter New Bug, and get an Internal Server Error. Got the same bug trying to get to New Bug from other pages as well. Error occurred at about 09:17 AM EST (GMT - 5:00). I had several bugzilla problems lately, hope it is fixed now. -- Warly
Re: [Cooker] Bugzilla New Bug error today
Warly wrote: Frank Griffin [EMAIL PROTECTED] writes: This morning, I bring up Bugzilla's main page, log in, select Enter New Bug, and get an Internal Server Error. Got the same bug trying to get to New Bug from other pages as well. Error occurred at about 09:17 AM EST (GMT - 5:00). I had several bugzilla problems lately, hope it is fixed now. I've had a problem submitting bug 4615 when a : or - characters were in the summary. Had to remove them. That might be those problems you've fixed, but it may be also still there. Try submitting a bug with lots of text in the body, and a long summary with a colon or hyphen. Best Regards, -- Aleksander Adamowski Jabber JID (to nie e-mail!): [EMAIL PROTECTED] GG#: 274614 ICQ UIN: 19780575 http://olo.office.altkom.com.pl
Re: [Cooker] bugzilla e-mail commands don't work? [was: Bug 4564...]
John Keller wrote: I'm not sure, but it appears that this kind of message doesn't make it to Bugzilla. I've occasionally noticed that e-mail commands aren't reflected in the Bugzilla status, leading to dangling open reports. (replying to self...) I can confirm that the same thing also occurred for (at least) bugs 4678, 4623, and 4566. I updated the corresponding reports in Bugzilla, though maybe I jumped the gun. On the other had, the e-mails that never made it to Bugzilla were written many hours, if not a few days, ago. They certainly *did* make it to the cooker mailing list, so it seems more likely to be a Bugzilla problem. It appears that e-mail containing Bugzilla commands stopped working some time after Thursday, 7 Aug at 5:41 PM CEST. That was when Pixel's update to bug 4549 successfully made it in. As I say, I may be jumping the gun. But this seems to be a recurring problem (I remember it during 9.1 beta/RC testing). I wanted to bring it up to try and avoid too many missed updates for reports that could have been closed long ago (or for people waiting in vain for a maintainer response). I hope this isn't all just a bunch of hot air (weather pun intended)... - John
Re: [Cooker] bugzilla e-mail commands don't work?
Warly wrote: I restart mysql and it works again. Some kind of heat side-effect, likely... I think I can identify with the machine... Though now it doesn't respond on http? - John
Re: [Cooker] bugzilla e-mail commands don't work? [was: Bug 4564...]
John Keller [EMAIL PROTECTED] writes: Pixel wrote: [hamster] [EMAIL PROTECTED] writes: Need to change the wording of the message to Please press Next to continue fixed in CVS @resolution=fixed I'm not sure, but it appears that this kind of message doesn't make it to Bugzilla. I've occasionally noticed that e-mail commands aren't reflected in the Bugzilla status, leading to dangling open reports. In this case, I manually updated the report through the Web interface (too hot, can't sleep, lurking the list). But I wanted to post a heads-up in case there is something broken with Mdk's Bugzilla configuration. warly will fix it, hopefully :)
Re: [Cooker] bugzilla e-mail commands don't work? [was: Bug 4564...]
Pixel wrote: warly will fix it, hopefully :) Cool. In this case, sorry for my soon-to-arrive other message. I was fervently typing it when your reply came in. 3:00 AM + 28 degrees = unclear thinking... - John
[Cooker] BugZilla Down?
Is BugZilla down? I can't connect to qa.mandrakesoft.com but I can ping it.
[Cooker] bugzilla e-mail commands don't work? [was: Bug 4564...]
Pixel wrote: [hamster] [EMAIL PROTECTED] writes: Need to change the wording of the message to Please press Next to continue fixed in CVS @resolution=fixed I'm not sure, but it appears that this kind of message doesn't make it to Bugzilla. I've occasionally noticed that e-mail commands aren't reflected in the Bugzilla status, leading to dangling open reports. In this case, I manually updated the report through the Web interface (too hot, can't sleep, lurking the list). But I wanted to post a heads-up in case there is something broken with Mdk's Bugzilla configuration. - John
[Cooker] Bugzilla is broken ?
Hi! I tried to post a new bug to bugzilla But I did not come trough. What I get is: - Forbidden You don't have permission to access /dvb below dvb-ttpci alps_bsrv2 alps_tdmb7 alps_tdlb7 add below dvb-ttpci grundig_29504-401 grundig_29504-491 add below dvb-ttpci stv0299 ves1820 options dvb-core dvb_shutdown_timeout=5 :o( will attach it, since every path seems to get interpreted by bugzilla Which cards are dvb-cards on this server. Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request. Apache-AdvancedExtranetServer/2.0.44 (Mandrake Linux/6mdk) mod_perl/1.99_08 Perl/v5.8.0 mod_ssl/2.0.44 OpenSSL/0.9.7a Server at qa Port 80 - The message I tried is the following. It seems iut hangs on / and that they get somehow interpreted. As we have current dvb-drivers (mod_dvb) in kernel, it would be nice if the cards could be detected and configured too. What have to be done to configure them ? Put the following code in modules.conf: probeall /dev/dvb dvb-ttpci alias /dev/dvb/* /dev/dvb below dvb-ttpci alps_bsrv2 alps_tdmb7 alps_tdlb7 add below dvb-ttpci grundig_29504-401 grundig_29504-491 add below dvb-ttpci stv0299 ves1820 options dvb-core dvb_shutdown_timeout=5 Which cards are dvb-cards ? all with dvb-ttpci in modules.pcimap ;) Basicly all cards have Vendor Id 0x1131 and Product Id 0x7146. So it are all cards that are curently recognized by : 0x1131 0x7146 dvb-ttpci Philips Semiconductors|SAA7146 The description could be changed to a better value too. The Design is basically by technotrend and build by many vendors, so maybe Technotrend | Digital TV card (DVB) would fit more ? Steffen - Greets Steffen
Re: [Cooker] bugzilla e-mail commands don't work?
Pixel [EMAIL PROTECTED] writes: John Keller [EMAIL PROTECTED] writes: Pixel wrote: [hamster] [EMAIL PROTECTED] writes: Need to change the wording of the message to Please press Next to continue fixed in CVS @resolution=fixed I'm not sure, but it appears that this kind of message doesn't make it to Bugzilla. I've occasionally noticed that e-mail commands aren't reflected in the Bugzilla status, leading to dangling open reports. In this case, I manually updated the report through the Web interface (too hot, can't sleep, lurking the list). But I wanted to post a heads-up in case there is something broken with Mdk's Bugzilla configuration. warly will fix it, hopefully :) I restart mysql and it works again. Some kind of heat side-effect, likely... -- Warly
RE: [Cooker] Bugzilla New Bug error today
Same here... -Original Message- From: Frank Griffin [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 05, 2003 6:20 AM To: Mandrake Cooker Subject: [Cooker] Bugzilla New Bug error today This morning, I bring up Bugzilla's main page, log in, select Enter New Bug, and get an Internal Server Error. Got the same bug trying to get to New Bug from other pages as well. Error occurred at about 09:17 AM EST (GMT - 5:00).
[Cooker] Bugzilla New Bug error today
This morning, I bring up Bugzilla's main page, log in, select Enter New Bug, and get an Internal Server Error. Got the same bug trying to get to New Bug from other pages as well. Error occurred at about 09:17 AM EST (GMT - 5:00).
[Cooker] Bugzilla is down ?
HI ! I have tried to post a bug to bugzilla, but it was down the whole day. Is it possible that there is done some work on it again (Its weekend again;)) or is it just not reachable from here ? Greets Steffen
Re: [Cooker] bugzilla voting not activated ??
Steffen Barszus [EMAIL PROTECTED] writes: How one should vote for bugs ? Ah, damn, something more screwed up by the update. I will put it back. -- Warly
Re: [Cooker] bugzilla voting not activated ??
Warly [EMAIL PROTECTED] writes: Steffen Barszus [EMAIL PROTECTED] writes: How one should vote for bugs ? Ah, damn, something more screwed up by the update. I will put it back. OK should be back again. -- Warly
Re: [Cooker] bugzilla voting not activated ??
Am Montag, 21. Juli 2003 11:48 schrieb Warly: Warly [EMAIL PROTECTED] writes: Steffen Barszus [EMAIL PROTECTED] writes: How one should vote for bugs ? Ah, damn, something more screwed up by the update. I will put it back. OK should be back again. Yep thanks :)) Its there again :) Wouldn't it be usefull to activate compression on cooker ? Steffen
[Cooker] Bugzilla question - Hopefully not off topic
This is in regards to the broken KDE Help indexing tool in the KDE Control Center. Bugzilla says that this was resolved in CVS by KDE however I've just gotten the texstar KDE update to 3.1.2 and it is still broken. Anyone know what is up with this? I'm *really* looking forward to the possiblility of having an automated M$ style help searching tool in Mandrake 9.2 There was a similar tool provided in Mandrake 8.1 and it was really fantastic. :-) Personally, I think that any such tool would redouble it's usefullness if it were independant of the window manager, but that's just me. ;-) Jim C.
[Cooker] bugzilla voting not activated ??
How one should vote for bugs ?
[Cooker] bugzilla and kernel
Yes, it's nice to be getting all of these bugzilla reminders. I'd love to check if my bug is still valid, but I can't run the new kernel. Panic, panic, panic. BTW, is the new alsa in it? 0.9.2 is outdated now. Austin -- Austin Acton Hon.B.Sc. Synthetic Organic Chemist, Teaching Assistant Department of Chemistry, York University, Toronto MandrakeClub Volunteer (www.mandrakeclub.com) homepage: www.groundstate.ca
[Cooker] BugZilla - voting/ compression
Hi ! I have looked at some bugs in bugzilla and hace recognized that i have no link Vote for this bug. Is this something related to my account or a general bugzilla issue ? Other have the same problem ? Further it would be nice to have a reference of keywords one is able to use, so I could vote for a bug per email maybe ? I'm sure this would help others too, Could this be added to the cooker howto ? Another thing that would be nice is, to enable compressed transmission for bugzilla. This would increase speed for slow dialup connections and so ease the use of bugzilla. Regards Steffen
Re: [Cooker] Bugzilla?
Buchan Milne [EMAIL PROTECTED] writes: If serious bug-fixing is going to be done in the near future, we're going to need a working bugzilla ... http://qa.mandrakesoft.com/reports.cgi?product=-All-datasets=NEW%3Adatasets=ASSIGNED%3Adatasets=NEEDINFO%3Adatasets=REOPENED%3Adatasets=UNCONFIRMED%3A seems to imply no new bug reports for a month, and my bugzilla mbox says similar things. Warly? For me it seems to work. -- Warly
Re: [Cooker] Bugzilla?
On Tue 2003-06-03 at 15:33:35 +0200, [EMAIL PROTECTED] wrote: Buchan Milne [EMAIL PROTECTED] writes: If serious bug-fixing is going to be done in the near future, we're going to need a working bugzilla ... http://qa.mandrakesoft.com/reports.cgi?product=-All-datasets=NEW%3Adatasets=ASSIGNED%3Adatasets=NEEDINFO%3Adatasets=REOPENED%3Adatasets=UNCONFIRMED%3A seems to imply no new bug reports for a month, and my bugzilla mbox says similar things. Warly? For me it seems to work. For me the graph ends on about 2003-04-30, I think that was what Buchan referred to with seems to imply no new bug reports for a month. But since there do exist recent bug reports like, e.g. http://qa.mandrakesoft.com/show_bug.cgi?id=4020 from 2003-06-03, this seems only a problem with the reports page. Another point is that I don't get bug report mails via Cooker for quite some while, but this has been mentioned before, I think. And maybe I simply missed a change in policies regarding the mails. HTH, Benjamin.
[Cooker] Bugzilla?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 If serious bug-fixing is going to be done in the near future, we're going to need a working bugzilla ... http://qa.mandrakesoft.com/reports.cgi?product=-All-datasets=NEW%3Adatasets=ASSIGNED%3Adatasets=NEEDINFO%3Adatasets=REOPENED%3Adatasets=UNCONFIRMED%3A seems to imply no new bug reports for a month, and my bugzilla mbox says similar things. Warly? - -- |--Another happy Mandrake Club member--| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x202 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE+225CrJK6UGDSBKcRAnUDAKCvwmAn2JXrvhilc5eVEpZAQAI43wCfYUmC vhBn54HB+Ih7nlGyda6UuFg= =sZT5 -END PGP SIGNATURE- ** Please click on http://www.cae.co.za/disclaimer.htm to read our e-mail disclaimer or send an e-mail to [EMAIL PROTECTED] for a copy. **
Re: [Cooker] bugzilla bug
Pascal [EMAIL PROTECTED] writes: this query on bugzilla http://qa.mandrakesoft.com/reports.cgi?product=mozillaoutput=most_recently_doomeddatasets=NEW%3Adatasets=ASSIGNED%3Adatasets=NEEDINFO%3Adatasets=REOPENED%3Adatasets=UNCONFIRMED%3Alinks=1banner=1 leads to an sql error :) Content-type: text/html Software error: SELECT defaultmilestone FROM products WHERE product = 'mozilla': Unknown column 'product' in 'where clause' at globals.pl line 252. Will try to have a look. -- Warly
[Cooker] bugzilla bug
this query on bugzilla http://qa.mandrakesoft.com/reports.cgi?product=mozillaoutput=most_recently_doomeddatasets=NEW%3Adatasets=ASSIGNED%3Adatasets=NEEDINFO%3Adatasets=REOPENED%3Adatasets=UNCONFIRMED%3Alinks=1banner=1 leads to an sql error :) Content-type: text/html Software error: SELECT defaultmilestone FROM products WHERE product = 'mozilla': Unknown column 'product' in 'where clause' at globals.pl line 252. For help, please send mail to the webmaster ([EMAIL PROTECTED]), giving this error message and the time and date of the error. -- Pascal __ Running 3:08, 4 users, load average: 0.25, 0.34, 0.36 (gcc version 3.2.2 (Mandrake Linux 9.1 3.2.2-3mdk)) Kernel Linux version 2.4.21-0.13mdkenterprise pgp0.pgp Description: signature
[Cooker] bugzilla bug reposts (was: Re: [Bug 3253])
Lots of people have run into this problem...Warly, is this something that can be addressed in Bugzilla or is it hopeless? You can address this after the release, I'm sure you're busy now. bunnadik wrote: http://qa.mandrakesoft.com/show_bug.cgi?id=3253 --- Additional Comments From [EMAIL PROTECTED] 2003-03-14 17:08 --- Oops! When I reloaded the page so see if there'd been some answer, the stupid bugzilla must have reposted the bug somehow. Sorry about that. Peder
Re: [Cooker] Bugzilla - Error when voting for a bug
Jure Repinc [EMAIL PROTECTED] writes: When I try to change my votes in bugzilla I get an error like this: Software error: SELECT fieldid FROM fielddefs WHERE name = 'bug_status': Table 'fielddefs' was not locked with LOCK TABLES at globals.pl line 252. For help, please send mail to the webmaster ([EMAIL PROTECTED]), giving this error message and the time and date of the error. I could not reproduce, could you explain more clearly what you are doing? -- Warly
Re: [Cooker] Bugzilla - Error when voting for a bug
Le Mardi 11 Mars 2003 12:32, Warly a écrit : Jure Repinc [EMAIL PROTECTED] writes: When I try to change my votes in bugzilla I get an error like this: Software error: SELECT fieldid FROM fielddefs WHERE name = 'bug_status': Table 'fielddefs' was not locked with LOCK TABLES at globals.pl line 252. For help, please send mail to the webmaster ([EMAIL PROTECTED]), giving this error message and the time and date of the error. I could not reproduce, could you explain more clearly what you are doing? warly, I had this error sometimes too, but when I post comments to bugs. When it happens, reposting the same page works. Might be a concurrency access in the database which is not handled correctly. -- Pascal Cavy - VMF __ Running 3 days, 16:28, 4 users, load average: 0.26, 0.22, 0.27 (gcc version 3.2.2 (Mandrake Linux 9.1 3.2.2-3mdk)) Kernel Linux version 2.4.21-0.12mdkenterprise
Re: [Cooker] Bugzilla - Error when voting for a bug
On Tue 2003-03-11 at 12:37:23 +0100, [EMAIL PROTECTED] wrote: Le Mardi 11 Mars 2003 12:32, Warly a écrit : Jure Repinc [EMAIL PROTECTED] writes: When I try to change my votes in bugzilla I get an error like this: Software error: SELECT fieldid FROM fielddefs WHERE name = 'bug_status': Table 'fielddefs' was not locked with LOCK TABLES at globals.pl line 252. For help, please send mail to the webmaster ([EMAIL PROTECTED]), giving this error message and the time and date of the error. I could not reproduce, could you explain more clearly what you are doing? warly, I had this error sometimes too, but when I post comments to bugs. When it happens, reposting the same page works. Might be a concurrency access in the database which is not handled correctly. If you mean the error is triggered due to concurrency in the RDBMS, then no, it has nothing to do with that. It simply means that the script has issued a LOCK TABLES beforehand and table fielddefs was not included. Two possible, probable reasons are: - The scripts issues LOCK statements on conditions which may change between accesses (could include concurrency issues of the script) - Or the script failed to issue an intended UNLOCK command for some reason, which would make the next command outside the block protected by the LOCK fail in the observed way. Warly, is there an easy way to get to / see the source of your bugzilla installation? If so, I would take the time to have a look at possible sources for this behaviour. I am not sure how different your version is from the official bugzilla. If using the latter one makes sense, just say so. HTH, Benjamin. pgp0.pgp Description: PGP signature
Re: [Cooker] bugzilla does not query unconfirmed by default
Sascha Noyes [EMAIL PROTECTED] writes: On Sunday 09 March 2003 15:52, Quel Qun wrote: Could the default query please include search in the unconfirmed defects by default? Thanks, -- _ _ _ _ | |_| | |_/ | | | / / -_) | / / | |_\_\___|_|_\_\_| @ sbcglobal.net Yes, I second that. We are getting a horrendous amount of duplicate bug reports. This will lower that amount. Should be OK now. -- Warly
[Cooker] bugzilla does not query unconfirmed by default
Could the default query please include search in the unconfirmed defects by default? Thanks, -- _ _ _ _ | |_| | |_/ | | / / -_) | / / | |_\_\___|_|_\_\_| @ sbcglobal.net
Re: [Cooker] bugzilla does not query unconfirmed by default
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 09 March 2003 15:52, Quel Qun wrote: Could the default query please include search in the unconfirmed defects by default? Thanks, -- _ _ _ _ | |_| | |_/ | | | / / -_) | / / | |_\_\___|_|_\_\_| @ sbcglobal.net Yes, I second that. We are getting a horrendous amount of duplicate bug reports. This will lower that amount. Best, Sascha Noyes - -- Please encrypt all correspondence. PGP key available from: http://individual.utoronto.ca/noyes/snoyes.asc - -- -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+a7tGgzJdfX+cTW8RAjKYAJ0TmlodaiRyvxW8pGXWUmJAA53grgCeLMVI PNNFW1w4ZFYCpkETxiqE+D0= =l2IK -END PGP SIGNATURE-
[Cooker] Bugzilla - Error when voting for a bug
When I try to change my votes in bugzilla I get an error like this: Software error: SELECT fieldid FROM fielddefs WHERE name = 'bug_status': Table 'fielddefs' was not locked with LOCK TABLES at globals.pl line 252. For help, please send mail to the webmaster ([EMAIL PROTECTED]), giving this error message and the time and date of the error.
Re: [Cooker] bugzilla is up again, on port 80 also
Le mar 25/02/2003 à 13:37, Warly a écrit : New machine, one more CPU, some more RAM, fully dedicated to bugzilla, and available on non-encrypted port 80. Hope it will help. YES! =) Next time I come to Paris, I'll buy you some beer ;-) One thing though: http://qa.mandrakesoft.com/mainstat.cgi Software error: Can't load '/usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/auto/GD/GD.so' for module GD: libX11.so.6: cannot open shared object file: No such file or directory at /usr/lib/perl5/5.8.0/i386-linux-thread-multi/DynaLoader.pm line 229. at /usr/lib/perl5/vendor_perl/5.8.0/Chart/Base.pm line 15 Jean-Michel
Re: [Cooker] bugzilla is up again, on port 80 also
Jean-Michel Dault [EMAIL PROTECTED] writes: Le mar 25/02/2003 à 13:37, Warly a écrit : New machine, one more CPU, some more RAM, fully dedicated to bugzilla, and available on non-encrypted port 80. Hope it will help. YES! =) Next time I come to Paris, I'll buy you some beer ;-) One thing though: http://qa.mandrakesoft.com/mainstat.cgi Software error: Can't load '/usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/auto/GD/GD.so' for module GD: libX11.so.6: cannot open shared object file: No such file or directory at /usr/lib/perl5/5.8.0/i386-linux-thread-multi/DynaLoader.pm line 229. at /usr/lib/perl5/vendor_perl/5.8.0/Chart/Base.pm line 15 fixed, thanks. -- Warly
Re: [Cooker] bugzilla is up again, on port 80 also
Le mer 26/02/2003 à 11:54, Warly a écrit : New machine, one more CPU, some more RAM, fully dedicated to bugzilla, and available on non-encrypted port 80. YES! =) Next time I come to Paris, I'll buy you some beer ;-) One thing though: http://qa.mandrakesoft.com/mainstat.cgi Software error: fixed, thanks. Thanks again. It's *really* faster now. The query.cgi page still takes long to load (11 seconds), but that's an *enormous* improvement from the old machine. s/some beer/lots of beer/ ;-) Jean-Michel
Re: [Cooker] bugzilla is up again, on port 80 also
Page: http://qa.mandrakesoft.com/request.cgi gives: Internal Server Error Thomas
Re: [Cooker] bugzilla is up again, on port 80 also
Thomas Backlund [EMAIL PROTECTED] writes: Page: http://qa.mandrakesoft.com/request.cgi gives: Internal Server Error fixed -- Warly
Re: [Cooker] bugzilla is up again, on port 80 also
On Tue, 2003-02-25 at 09:37, Warly wrote: New machine, one more CPU, some more RAM, fully dedicated to bugzilla, and available on non-encrypted port 80. Hope it will help. Much, much faster. Thank you. -- Quel Qun [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part
[Cooker] Bugzilla will be down for some time
I am in the process of migrating it on a new machine. Sorry for the inconvenience -- Warly
[Cooker] bugzilla is up again, on port 80 also
New machine, one more CPU, some more RAM, fully dedicated to bugzilla, and available on non-encrypted port 80. Hope it will help. -- Warly
Re: [Cooker] bugzilla is up again, on port 80 also
Warly, Still looking for a secure connection. V. Your browser sent a request that this server could not understand. Reason: You're speaking plain HTTP to an SSL-enabled server port. Instead use the HTTPS scheme to access this URL, please. Hint: https://qa.mandrakesoft.com/On Tuesday 25 February 2003 12:37 pm, Warly wrote: New machine, one more CPU, some more RAM, fully dedicated to bugzilla, and available on non-encrypted port 80. Hope it will help.
Re: [Cooker] Bugzilla help reminder
David Walser [EMAIL PROTECTED] writes: How can you add someone to the CC list of a bug through the mail interface? You cannot at present, I will have to do it. -- Warly
Re: [Cooker] Bugzilla help reminder
How can you add someone to the CC list of a bug through the mail interface? --- Warly [EMAIL PROTECTED] wrote: Available commands for mail sent to [EMAIL PROTECTED]: -- For these commands, just send a mail to [EMAIL PROTECTED], any line in the mail will be interpreted as a command. canpostabug: usage: canpostabug ask for the permission to post bugs help: usage: help give available commands bug: usage: bug bug ID ask for information about a bug Available commands for bug processing (COMMAND=value): --- These commands are included among comments in mail sent to bug addresses such as [EMAIL PROTECTED] bug_status usage: bug_status=status Change bug status, allowed values are: ASSIGNED REOPENED priority usage: function not implemented vote usage: vote Vote once for this bug. If the bug is in UNCONFIRMED state, a certain number of votes will switch it to NEW state. confirm usage: confirm Confirm an bug in UNCOMFIRMED state, switch it to NEW state. rep_platform usage: function not implemented component usage: component=component_name Change component this of this bug. Component must be valid regarding the product. duplicate usage: duplicate=bug_id Mark this bug as duplicate of bug with ID bug_id assigned_to usage: assigned_to=maintainer_mail Change the maintainer the bug is assigned to, the new assignee must be a valid maintainer. resolution usage: resolution=resolution_type Change bug resolution, valide resolution types are: FIXED INVALID WONTFIX LATER REMIND WORKSFORME product usage: product=product_name Change the product of this bug. The new product must be a valid bugzilla product. If the component is not relevant for this new product, a default one will be choosen. bug_severity usage: function not implemented -- Warly __ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/
Re: [Cooker] Bugzilla very slow
Tibor Pittich [EMAIL PROTECTED] writes: On 18. feb 2003 17:09, Warly wrote: Tibor Pittich [EMAIL PROTECTED] writes: On 18. feb 2003 09:18, Warly wrote: James Sparenberg [EMAIL PROTECTED] writes: The thought I had was to have the default page after login be My Bugs rather than the search page. This alone should cut down tremendously on the load on the server. Don't have bugzilla in front of me but the link should be straight forward enough. done great, but can you synchronize this changes with mozilla sidebar too? if i logged via this sidebar, then i redirected again to search page. Well, I need to figure out where is this thing, but I am affraid that you will need to remove and readd this bar. unfortunately, i remove and add again sidebar today, but still is the same. if i click my bugs into sidebar, then i get full lists of bugs instead only my bugs. It may be because you are not listed as maintainer in bugzilla, could you send me in private your bugzilla account and the packages you are taking care of? -- Warly
Re: [Cooker] Bugzilla very slow
On 20. feb 2003 12:55, Warly wrote: The thought I had was to have the default page after login be My Bugs rather than the search page. This alone should cut down tremendously on the load on the server. Don't have bugzilla in front of me but the link should be straight forward enough. great, but can you synchronize this changes with mozilla sidebar too? if i logged via this sidebar, then i redirected again to search page. Well, I need to figure out where is this thing, but I am affraid that you will need to remove and readd this bar. unfortunately, i remove and add again sidebar today, but still is the same. if i click my bugs into sidebar, then i get full lists of bugs instead only my bugs. It may be because you are not listed as maintainer in bugzilla, could you send me in private your bugzilla account and the packages you are taking care of? i'm sorry, if this mistake is related to my bad english, but i mean other thing. i try explain this detailed: if i logged via web interface, and click to my bugs, then i redirected to page, where is bugs which reported by me, and don't have status fixed, closed, i.e. open bugs. if i logged via mozilla sidebar (or web interface, it doesn't matter) and click to my bugs _into_ mozilla sidebar, then i get defferend listing, which contains _all_ opened bugs. this is difference between my bugs link at web page, and my bugs link at sidebar, which i requested to be synced:) i know, this is cosmetic problem only, but i will expect, that both links behavior are same. msg93661/pgp0.pgp Description: PGP signature
Re: [Cooker] Bugzilla very slow
On 18. feb 2003 17:09, Warly wrote: Tibor Pittich [EMAIL PROTECTED] writes: On 18. feb 2003 09:18, Warly wrote: James Sparenberg [EMAIL PROTECTED] writes: The thought I had was to have the default page after login be My Bugs rather than the search page. This alone should cut down tremendously on the load on the server. Don't have bugzilla in front of me but the link should be straight forward enough. done great, but can you synchronize this changes with mozilla sidebar too? if i logged via this sidebar, then i redirected again to search page. Well, I need to figure out where is this thing, but I am affraid that you will need to remove and readd this bar. unfortunately, i remove and add again sidebar today, but still is the same. if i click my bugs into sidebar, then i get full lists of bugs instead only my bugs. msg93414/pgp0.pgp Description: PGP signature
Re: [Cooker] Bugzilla very slow
James Sparenberg [EMAIL PROTECTED] writes: On Mon, 2003-02-17 at 02:25, Combelles, Christophe (MED, ALTEN) wrote: I had entered a bug for this : https://qa.mandrakesoft.com/show_bug.cgi?id=1449 This can be easily? fixed by separating the product list from the page itself: for example, putting the list into a separate file, so it is recorded in the browser cache, and not reloaded every time. Otherwise, the product selection could be done from a popup window, and the code for the popup should be always the same. The thought I had was to have the default page after login be My Bugs rather than the search page. This alone should cut down tremendously on the load on the server. Don't have bugzilla in front of me but the link should be straight forward enough. done -- Warly
Re: [Cooker] Bugzilla very slow
On 18. feb 2003 09:18, Warly wrote: James Sparenberg [EMAIL PROTECTED] writes: The thought I had was to have the default page after login be My Bugs rather than the search page. This alone should cut down tremendously on the load on the server. Don't have bugzilla in front of me but the link should be straight forward enough. done great, but can you synchronize this changes with mozilla sidebar too? if i logged via this sidebar, then i redirected again to search page. into sidebar is another small bug, if i click to my bugs, then i redirected to page, with all bugs, not only mine. msg92989/pgp0.pgp Description: PGP signature
Re: [Cooker] Bugzilla very slow
Tibor Pittich [EMAIL PROTECTED] writes: On 18. feb 2003 09:18, Warly wrote: James Sparenberg [EMAIL PROTECTED] writes: The thought I had was to have the default page after login be My Bugs rather than the search page. This alone should cut down tremendously on the load on the server. Don't have bugzilla in front of me but the link should be straight forward enough. done great, but can you synchronize this changes with mozilla sidebar too? if i logged via this sidebar, then i redirected again to search page. Well, I need to figure out where is this thing, but I am affraid that you will need to remove and readd this bar. -- Warly
Re: [Cooker] Bugzilla very slow
On Tue, 2003-02-18 at 08:09, Warly wrote: Tibor Pittich [EMAIL PROTECTED] writes: On 18. feb 2003 09:18, Warly wrote: James Sparenberg [EMAIL PROTECTED] writes: The thought I had was to have the default page after login be My Bugs rather than the search page. This alone should cut down tremendously on the load on the server. Don't have bugzilla in front of me but the link should be straight forward enough. done great, but can you synchronize this changes with mozilla sidebar too? if i logged via this sidebar, then i redirected again to search page. Well, I need to figure out where is this thing, but I am affraid that you will need to remove and readd this bar. Warly, I noticed you changed the order of pages in Bugzilla... It loads and reacts a lot faster from here. Thanks. James
Re: [Cooker] Bugzilla very slow
I had entered a bug for this : https://qa.mandrakesoft.com/show_bug.cgi?id=1449 This can be easily? fixed by separating the product list from the page itself: for example, putting the list into a separate file, so it is recorded in the browser cache, and not reloaded every time. Otherwise, the product selection could be done from a popup window, and the code for the popup should be always the same. Jean-Michel Dault wrote: I always knew bugzilla was slow, but it gets worse every day, so I measured it: time -f %E lynx --dump https://qa.mandrakesoft.com/query.cgi/dev/null 0:25.60 25 seconds to load the query page... that's awful. Compare to some other mandrake web sites (https and http) time -f %E lynx --dump https://mandrakesecure.com /dev/null 0:05.46 time -f %E lynx --dump www.mandrakesoft.com /dev/null 0:01.43 I'm sure we could tweak Apache to get a bit more performance. If I can give a hand, let me know.
Re: [Cooker] Bugzilla very slow
On Mon, 2003-02-17 at 02:25, Combelles, Christophe (MED, ALTEN) wrote: I had entered a bug for this : https://qa.mandrakesoft.com/show_bug.cgi?id=1449 This can be easily? fixed by separating the product list from the page itself: for example, putting the list into a separate file, so it is recorded in the browser cache, and not reloaded every time. Otherwise, the product selection could be done from a popup window, and the code for the popup should be always the same. The thought I had was to have the default page after login be My Bugs rather than the search page. This alone should cut down tremendously on the load on the server. Don't have bugzilla in front of me but the link should be straight forward enough. James Jean-Michel Dault wrote: I always knew bugzilla was slow, but it gets worse every day, so I measured it: time -f %E lynx --dump https://qa.mandrakesoft.com/query.cgi/dev/null 0:25.60 25 seconds to load the query page... that's awful. Compare to some other mandrake web sites (https and http) time -f %E lynx --dump https://mandrakesecure.com /dev/null 0:05.46 time -f %E lynx --dump www.mandrakesoft.com /dev/null 0:01.43 I'm sure we could tweak Apache to get a bit more performance. If I can give a hand, let me know.
[Cooker] bugzilla
Hi! Mandrake's BugZilla is very slow, because some form-pages are very big as there are lots of packages. But most times, one already knows the package, so a very small HTML page with two forms is enough to first search for a keyword and then file a new bugreport. I haven't seen someone else posting it, but it really speeds up filing bug reports :) -- Michael Reinsch [EMAIL PROTECTED] http://mr.uue.org Title: Mandrake Cooker BugZilla Quick Access Mandrake Cooker BugZilla Quick Access Search in Bugreports: New Bugreport for:
Re: [Cooker] bugzilla
On Sunday 16 February 2003 22:00, Michael Reinsch wrote: Hi! Mandrake's BugZilla is very slow, because some form-pages are very big as there are lots of packages. But most times, one already knows the package, so a very small HTML page with two forms is enough to first search for a keyword and then file a new bugreport. I haven't seen someone else posting it, but it really speeds up filing bug reports :) Yes I can second this. It takes over a minute till the site is displayed. The current status is a no go. -- Regards Steffen counter.li.org : #296567. machine: 181800 vdr-box : 87 Please dont CC me, since if I have replied I'll watch the tread. Both mails will be filtered to the ML-folder. Thanks
Re: [Cooker] Bugzilla very slow
måndagen den 17 februari 2003 06.06 skrev Jean-Michel Dault: I always knew bugzilla was slow, but it gets worse every day, so I measured it: time -f %E lynx --dump https://qa.mandrakesoft.com/query.cgi/dev/null 0:25.60 25 seconds to load the query page... that's awful. Compare to some other mandrake web sites (https and http) time -f %E lynx --dump https://mandrakesecure.com /dev/null 0:05.46 time -f %E lynx --dump www.mandrakesoft.com /dev/null 0:01.43 I'm sure we could tweak Apache to get a bit more performance. If I can give a hand, let me know. How mature is vdanens Anthill? Could that relace bugzilla? Can bugzilla run under mod_perl? -- Regards // Oden Eriksson, Deserve-IT.com
Re: [Cooker] Bugzilla very slow
On Mon, Feb 17, 2003 at 07:32:12AM +0100, Oden Eriksson wrote: How mature is vdanens Anthill? Could that relace bugzilla? Can bugzilla run under mod_perl? I don't think anthill is very well suited for what we're doing... From what I understand though YOS is using it for their bug tracking. -- Ben Reser [EMAIL PROTECTED] http://ben.reser.org America does not go abroad in search of monsters to destroy. She is the well-wisher to the freedom and independence of all. She is the champion only of her own. -- John Quincy Adams, July 4th, 1821
[Cooker] Bugzilla very slow
I always knew bugzilla was slow, but it gets worse every day, so I measured it: time -f %E lynx --dump https://qa.mandrakesoft.com/query.cgi/dev/null 0:25.60 25 seconds to load the query page... that's awful. Compare to some other mandrake web sites (https and http) time -f %E lynx --dump https://mandrakesecure.com /dev/null 0:05.46 time -f %E lynx --dump www.mandrakesoft.com /dev/null 0:01.43 I'm sure we could tweak Apache to get a bit more performance. If I can give a hand, let me know.
[Cooker] Bugzilla Suggestion
Can we get the From field to be the person posting the message. At least the name part of it if not the email addy? As it stands now the From field is the bug id which is already in the Subject. So this creates some redundent information in my email index. It'd be nice to easily scan down and see that say Pixel or GC etc... had already replied and that I probably didn't need to reply. As it stands now I have to go and specifically look at each message to see who's said something so far... -- Ben Reser [EMAIL PROTECTED] http://ben.reser.org America does not go abroad in search of monsters to destroy. She is the well-wisher to the freedom and independence of all. She is the champion only of her own. -- John Quincy Adams, July 4th, 1821
[Cooker] Bugzilla help reminder
Available commands for mail sent to [EMAIL PROTECTED]: -- For these commands, just send a mail to [EMAIL PROTECTED], any line in the mail will be interpreted as a command. canpostabug: usage: canpostabug ask for the permission to post bugs help: usage: help give available commands bug: usage: bug bug ID ask for information about a bug Available commands for bug processing (@COMMAND=value): --- These commands are included among comments in mail sent to bug addresses such as [EMAIL PROTECTED] bug_status usage: @bug_status=status Change bug status, allowed values are: ASSIGNED REOPENED priority usage: function not implemented vote usage: @vote Vote once for this bug. If the bug is in UNCONFIRMED state, a certain number of votes will switch it to NEW state. confirm usage: @confirm Confirm an bug in UNCOMFIRMED state, switch it to NEW state. rep_platform usage: function not implemented component usage: @component=component_name Change component this of this bug. Component must be valid regarding the product. duplicate usage: @duplicate=bug_id Mark this bug as duplicate of bug with ID bug_id assigned_to usage: @assigned_to=maintainer_mail Change the maintainer the bug is assigned to, the new assignee must be a valid maintainer. resolution usage: @resolution=resolution_type Change bug resolution, valide resolution types are: FIXED INVALID WONTFIX LATER REMIND WORKSFORME product usage: @product=product_name Change the product of this bug. The new product must be a valid bugzilla product. If the component is not relevant for this new product, a default one will be choosen. bug_severity usage: function not implemented -- Warly
[Cooker] bugzilla bugs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 There are two annoying issues with bugzilla at the moment: 1. There are two entries for drakconf (drakconf DrakConf). When one votes for a bug that is listed under drakconf, then there is also a check-box for the same bug under DrakConf. 2.(is perhaps related to 1) Voting for multiple bugs that appear in the same component (in this case drakconf) is not possible. Bugzilla gives the error message: ¨You may only use at most 1 votes for bugs in the drakconf product, but you are trying to use 2.¨ I´m trying to vote for both bug 770 805. Sascha Noyes - -- Please encrypt all correspondence. PGP key available from: http://individual.utoronto.ca/noyes/snoyes.asc - -- -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+JEzKgzJdfX+cTW8RAt/YAKC1Q+/rRNzBY/6rR4/6WryqpLxBKACgpK22 B38xU5ZqJSWNRRZkmBDzk8I= =ET1n -END PGP SIGNATURE-
[Cooker] bugzilla is broken - eom
-- Quel Qun [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part
Re: [Cooker] bugzilla is broken - eom
fixed -- Warly
Re: [Cooker] bugzilla is broken - eom
On Sun, 2003-01-12 at 11:10, Warly wrote: fixed Faster than light! -- Quel Qun [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part
Re: [Cooker] bugzilla and bugstatus
Quel Qun [EMAIL PROTECTED] writes: On Thu, 2003-01-02 at 17:16, Steffen Barszus wrote: Hi ! I wonder how many votes a bug needs to get confirmed status, and how I can influence a bug to be confirmed. I've reported some bugs some time ago and the still are in status unconfirmed. As long as they are unconfirmed they are ignored right ? I'm namely interested in bugs 634-636. So if someone can state on this ... ?! It needs one vote to be confirmed and its status switched to new. two votes. -- Warly
Re: [Cooker] bugzilla and bugstatus
On Thu, 2003-01-02 at 17:16, Steffen Barszus wrote: Hi ! I wonder how many votes a bug needs to get confirmed status, and how I can influence a bug to be confirmed. I've reported some bugs some time ago and the still are in status unconfirmed. As long as they are unconfirmed they are ignored right ? I'm namely interested in bugs 634-636. So if someone can state on this ... ?! It needs one vote to be confirmed and its status switched to new. -- Quel Qun [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part
[Cooker] bugzilla and bugstatus
Hi ! I wonder how many votes a bug needs to get confirmed status, and how I can influence a bug to be confirmed. I've reported some bugs some time ago and the still are in status unconfirmed. As long as they are unconfirmed they are ignored right ? I'm namely interested in bugs 634-636. So if someone can state on this ... ?! Greets Steffen -- counter.li.org : #296567. machine: 181800 vdr-box : 87 Please dont CC me, since if I have replied I'll watch the tread. Both mails will be filtered to the ML-folder. Thanks
Re: [Cooker] bugzilla and bugstatus
Quel Qun wrote: On Thu, 2003-01-02 at 17:16, Steffen Barszus wrote: Hi ! I wonder how many votes a bug needs to get confirmed status, and how I can influence a bug to be confirmed. I've reported some bugs some time ago and the still are in status unconfirmed. As long as they are unconfirmed they are ignored right ? I'm namely interested in bugs 634-636. So if someone can state on this ... ?! It needs one vote to be confirmed and its status switched to new. And how does one take the verbal confirm as comment one of bug 634 as of 14.12.02 and tell the person to please vote??? that person suggested pushing it to confirmed as they knew it existed since version 7.2. I would like to know how to vote also, please???
Re: [Cooker] bugzilla and bugstatus
On Thu, 2003-01-02 at 21:16, John Danielson, II wrote: Quel Qun wrote: On Thu, 2003-01-02 at 17:16, Steffen Barszus wrote: Hi ! I wonder how many votes a bug needs to get confirmed status, and how I can influence a bug to be confirmed. I've reported some bugs some time ago and the still are in status unconfirmed. As long as they are unconfirmed they are ignored right ? I'm namely interested in bugs 634-636. So if someone can state on this ... ?! It needs one vote to be confirmed and its status switched to new. And how does one take the verbal confirm as comment one of bug 634 as of 14.12.02 and tell the person to please vote??? that person suggested pushing it to confirmed as they knew it existed since version 7.2. I would like to know how to vote also, please??? Just reply to the bug email from bugzilla with @vote on a line and your comment. That should make it. You can also login https://qa/mandrakesoft.com look for the bug report and vote for it. -- Quel Qun [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part
[Cooker] Bugzilla problems
In regards to all the discussion on Bugzilla, I just attempted to post to Bugzilla and was refused on the login. I then attempted to create an account and was informed that I already have an account (which is probably true). I then attempted to change my password and at that point Bugzilla just croaked and wouldn't proceed any further. It is rather frustrating to write up a report and then be stymied by a dysfunctional website.
Re: [Cooker] Bugzilla problems
George Mitchell [EMAIL PROTECTED] writes: In regards to all the discussion on Bugzilla, I just attempted to post to Bugzilla and was refused on the login. I then attempted to create an account and was informed that I already have an account (which is probably true). I then attempted to change my password and at that point Bugzilla just croaked and wouldn't proceed any further. It is rather frustrating to write up a report and then be stymied by a dysfunctional website. I had a report of a user who had the same trouble, but was not able to reproduce, what is your mail login in bugzilla? -- Warly
Re: [Cooker] Bugzilla problems
Warly, sorry to complain about this amidst so many far more crucial problems, but appreciate any help you can provide. My Bugzilla login is [EMAIL PROTECTED] Thanks and best wishes to all at Mandrake. - George Warly wrote: George Mitchell [EMAIL PROTECTED] writes: In regards to all the discussion on Bugzilla, I just attempted to post to Bugzilla and was refused on the login. I then attempted to create an account and was informed that I already have an account (which is probably true). I then attempted to change my password and at that point Bugzilla just croaked and wouldn't proceed any further. It is rather frustrating to write up a report and then be stymied by a dysfunctional website. I had a report of a user who had the same trouble, but was not able to reproduce, what is your mail login in bugzilla?
Re: [Cooker] Bugzilla posts absolutely nescessary?
On Monday 09 December 2002 16:50, Warly wrote: I think there is 2 problems. - first one is technical, when you reply to the bug into cooker you get your comment posted both by sympa an bugzilla, this I can fix. - second one is maintainers and subscribers problems. Some of them do not care of bugzilla post, and filter them out. Creating a separate mailing list will ease the filtering problem of the people of the second point, but guys who care about bugs will not see any change except having to subscribe to two mailing lists instead of one. As a consequence, I will try: - to fix the duplicate problem so that anyone could reply to a bug in cooker without caring of the address is responding to. Bugzilla will takes care not to send duplicates. - to make it clearer on bugzilla that it is only for development version. And also to do an automatic search before the bug is posted to ask user if by chance his bug is not already reported. There is a bigger problem. The bugzilla post are unreadable. They start with https://qa.mandrakesoft.com/show_bug.cgi? which says nothing to me except when i go to that webpage. Than there is optional some extra info. After that you get the addition comment. aka the real meat of the reply and than you get the --- You are receiving this mail because:---. My suggestion is to start with addition comment because that is the important part of the message and than you can decide quickly if it is important for you or not. Than have the https stuff and than to remove the --- You are receiving this mail because:--- part of the mail when it is send to the cooker list. I can see why one would add it to a email to a CC'er but on cooker it is just two more lines to (not)read.
Re: [Cooker] Bugzilla posts absolutely nescessary?
On Friday 13 December 2002 14:31, andre wrote: There is a bigger problem. The bugzilla post are unreadable. They start with https://qa.mandrakesoft.com/show_bug.cgi? which says nothing to me except when i go to that webpage. Than there is optional some extra info. After that you get the addition comment. aka the real meat of the reply and than you get the --- You are receiving this mail because:---. My suggestion is to start with addition comment because that is the important part of the message and than you can decide quickly if it is important for you or not. Than have the https stuff and than to remove the --- You are receiving this mail because:--- part of the mail when it is send to the cooker list. I can see why one would add it to a email to a CC'er but on cooker it is just two more lines to (not)read. Other problem is that bugzilla post don't form threads which makes the quite difficult to read
[Cooker] bugzilla error adding comments to a bug
I tried to add some comments to bug 442. When I tried to commit the comments I got an error: Bugzilla has suffered an internal error. Please save this page and send it to [EMAIL PROTECTED] with details of what you were doing at the time this message appeared. URL: https://qa.mandrakesoft.com/process_bug.cgi A legal Version was not set. Variables: I went back and tried to change the version to the most recent and it then complained that it was an illegal change. How can I add comments to this bug? b. -- Brian J. Murrell msg83738/pgp0.pgp Description: PGP signature
