From 99a4be2c6b147dee0675afc41cab7918e00bcabd Mon Sep 17 00:00:00 2001 From: "mozilla%colinogilvie.co.uk" <> Date: Fri, 24 Nov 2006 04:25:37 +0000 Subject: Bug 361251: update Bugzilla FAQ Patch by victory(_RSZ_) ; r=LpSolit; r=Colin --- docs/xml/faq.xml | 182 +++++++++++++++++++++++++++++++++++++++++-------------- 1 file changed, 138 insertions(+), 44 deletions(-) diff --git a/docs/xml/faq.xml b/docs/xml/faq.xml index 947371019..80f411375 100644 --- a/docs/xml/faq.xml +++ b/docs/xml/faq.xml @@ -13,6 +13,21 @@ General Questions + + + + Can I try out Bugzilla somewhere? + + + + + If you want to take a test ride, there are test installations + at , + ready to play with directly from your browser. + + + + @@ -126,7 +141,7 @@ The best way to make an enhancement request is to file + url="https://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla">file a bug at bugzilla.mozilla.org and set the Severity to 'enhancement'. Your 'request for enhancement' (RFE) will start out in the UNCONFIRMED state, and will stay there until @@ -169,35 +184,44 @@ and was available for the hardware Netscape intended to run it on. - There is currently work in progress to make Bugzilla work on - PostgreSQL; track the progress of this initiative in bug 98304. - - - Sybase support is no longer being worked on. Even if it eventually - happens, it's VERY unlikely to work without the end-user-company - having to stick a few developers on making several manual changes. - Sybase is just NOT very standards-compliant (despite all the hype), - and it turned out that way too much had to be changed to make it - work -- like moving half of the application logic into stored - procedures to get any kind of decent performance out of it. - Bug - 173130 is the relevant bug. + Bugzilla 2.20 contains experimental support for PostgreSQL. + Bugzilla 2.22 contains complete, stable support for PostgreSQL. + As of this release, using PostgreSQL with Bugzilla should + be as stable as using MySQL. If you experience any problems + with PostgreSQL compatibility, they will be taken as + seriously as if you were running MySQL. Red Hat once ran a version of Bugzilla that worked on Oracle, but that was long, long ago; that version (Bugzilla 2.8) is - now obsolete, insecure, and totally unsupported. Red Hat's - current Bugzilla (based on Bugzilla 2.17.1) uses PostgreSQL, - and work is being done to merge those changes into the main - distribution. (See above.) At this time we know of no recent - ports of Bugzilla to Oracle. (In our honest opinion, Bugzilla - doesn't need what Oracle offers.) + now obsolete, insecure, and totally unsupported. + + + In August of 2005, Wim Coekaerts (Director of Linux + Engineering at Oracle Corporation) wrote to Dave Miller + confirming that Oracle intends to implement and support + Bugzilla. Since then, no further information has been + forthcoming. Track progress at + + Bug 189947. - Bug - 237862 is a good bug to read through if you'd like to see - what progress is being made on general database compatibility. + Sybase support is no longer being worked on. Even if it + eventually happens, it's VERY unlikely to work without + the end-user-company having to stick a few developers on + making several manual changes. Sybase is just NOT very + standards-compliant (despite all the hype), and it turned + out that way too much had to be changed to make it work -- + like moving half of the application logic into stored + procedures to get any kind of decent performance out of it. + + Bug 173130 is the relevant bug. + + + + Bug 237862 is a good bug to read through if you'd + like to see what progress is being made on general database + compatibility. @@ -301,7 +325,7 @@ perl runtests.pl 2 --verbose - + @@ -318,7 +342,22 @@ perl runtests.pl 2 --verbose - + + + + + How can Bugzilla be made to work under SELinux? + + + + + Unfortunately there are no step-by-step instructions, + but the following URL contains hints on how to do it: + + + + + @@ -355,7 +394,7 @@ perl runtests.pl 2 --verbose There is no GUI for adding fields to Bugzilla at this time. You can follow development of this feature in - bug 91037 + bug 91037 @@ -369,7 +408,7 @@ perl runtests.pl 2 --verbose - Yes. Look at + Yes. Look at for samples of what Bugzilla can do in reporting and graphing. Fuller documentation is provided in . @@ -481,7 +520,7 @@ perl runtests.pl 2 --verbose Some admin interfaces have been templatized (for easy localization) but many of them are still available in English only. Also, there may be issues with the charset not being declared. See bug 126226 + url="https://bugzilla.mozilla.org/show_bug.cgi?id=126266">bug 126226 for more information. @@ -598,7 +637,7 @@ perl runtests.pl 2 --verbose See the documentation on Customization for more details, specifically . - + @@ -712,7 +751,7 @@ perl runtests.pl 2 --verbose See also the instructions in . - + @@ -781,7 +820,7 @@ password=mypassword command line. - + On your new machine, follow the instructions found in as far as setting up the physical @@ -833,7 +872,7 @@ password=mypassword Run MySQL like this: mysqld --skip-grant-tables. Please remember that this makes MySQL as secure as taping a $100 to the floor of a football stadium bathroom for - safekeeping. + safekeeping. @@ -952,7 +991,7 @@ password=mypassword For older versions of Bugzilla, you may be able to apply Klaas Freitag's patch for whineatassigned, which can be found in - bug + bug 6679. Note that this patch was made in 2000, so it may take some work to apply cleanly to any releases of Bugzilla newer than that, but you can use it as a starting point. @@ -961,7 +1000,7 @@ password=mypassword An updated (and much-expanded) version of this functionality is due to be released as part of Bugzilla 2.20; see - bug + bug 185090 for the discussion, and for more up-to-date patches if you just can't wait. @@ -1124,6 +1163,61 @@ password=mypassword as a troubleshooting step. + + You may also be suffering from a client version mismatch: + + + MySQL 4.1 and up uses an authentication protocol based on + a password hashing algorithm that is incompatible with that + used by older clients. If you upgrade the server to 4.1, + attempts to connect to it with an older client may fail + with the following message: + + + shell> mysql + Client does not support authentication protocol requested + by server; consider upgrading MySQL client + + + + To solve this problem, you should use one of the following + approaches: + + + + + + Upgrade all client programs to use a 4.1.1 or newer + client library. + + + + + When connecting to the server with a pre-4.1 client + program, use an account that still has a + pre-4.1-style password. + + + + + Reset the password to pre-4.1 style for each user + that needs to use a pre-4.1 client program. + This can be done using the SET PASSWORD statement + and the OLD_PASSWORD() function: + + mysql> SET PASSWORD FOR + -> ' some_user '@' some_host ' = OLD_PASSWORD(' newpwd '); + + + + + + + + + + + @@ -1358,16 +1452,16 @@ password=mypassword have your choice of patches: - Bug 35195 + Bug 35195 seeks to add an ...and accept the bug checkbox to the UI. It has two patches attached to it: - attachment 8029 + attachment 8029 was originally created for Bugzilla 2.12, while - attachment 91372 + attachment 91372 is an updated version for Bugzilla 2.16 - Bug + Bug 37613 also provides two patches (against Bugzilla 2.12): one to add a 'Take Bug' option, and the other to automatically reassign the bug on 'Accept'. @@ -1501,13 +1595,13 @@ password=mypassword - Try + Try this link to view current bugs or requests for enhancement for Bugzilla. You can view bugs marked for &bz-nextver; release - here. + here. This list includes bugs for the &bz-nextver; release that have already been fixed and checked into CVS. Please consult the @@ -1529,7 +1623,7 @@ password=mypassword This is well-documented in bug + url="https://bugzilla.mozilla.org/show_bug.cgi?id=49862">bug 49862. Ultimately, it's as easy as adding the --- priority field to your localconfig file in the appropriate area, re-running checksetup.pl, and then @@ -1552,7 +1646,7 @@ password=mypassword Enter a bug into bugzilla.mozilla.org for the Bugzilla + url="https://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla">Bugzilla product. @@ -1571,7 +1665,7 @@ password=mypassword Announce your patch and the associated URL - (http://bugzilla.mozilla.org/show_bug.cgi?id=XXXXXX) + (https://bugzilla.mozilla.org/show_bug.cgi?id=XXXXXX) for discussion in the newsgroup (mozilla.support.bugzilla). You'll get a really good, fairly immediate reaction to the -- cgit v1.2.3-24-g4f1b