From: gerv%gerv.net <> Date: Fri, 26 Jul 2002 03:48:28 +0000 (+0000) Subject: Removing unnecessary files and regenerating. X-Git-Tag: bugzilla-2.16~5 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=bc146ad2daaf9a4c86250f1e75dab55b687befa4;p=thirdparty%2Fbugzilla.git Removing unnecessary files and regenerating. --- diff --git a/docs/html/administration.html b/docs/html/administration.html index 06b0592414..c85d9acdda 100644 --- a/docs/html/administration.html +++ b/docs/html/administration.html @@ -154,17 +154,22 @@ HREF="cust-templates.html" >
5.7.1. What to Edit
5.7.2. Template FormatsHow To Edit Templates
5.7.3. Template Formats
5.7.4. Particular Templates
Bonsai
The Bugzilla Guide
PrevChapter 6. Integrating Bugzilla with Third-Party ToolsNext

6.1. Bonsai

Bonsai is a web-based tool for managing - CVS, the Concurrent Versioning System - - . Using Bonsai, administrators can control open/closed status of trees, - query a fast relational database back-end for change, branch, and comment - information, and view changes made since the last time the tree was - closed. These kinds of changes cause the engineer responsible to be - "on the hook" - - (include cool URL link here for Hook policies at mozilla.org). Bonsai - also includes gateways to - Tinderbox, the Mozilla automated build management system - - and Bugzilla

PrevHomeNext
Integrating Bugzilla with Third-Party ToolsUpCVS
\ No newline at end of file diff --git a/docs/html/bsdinstall.html b/docs/html/bsdinstall.html deleted file mode 100644 index aeb9870f7d..0000000000 --- a/docs/html/bsdinstall.html +++ /dev/null @@ -1,151 +0,0 @@ -BSD Installation Notes
The Bugzilla Guide
PrevChapter 4. InstallationNext

4.3. BSD Installation Notes

For instructions on how to set up Bugzilla on FreeBSD, NetBSD, - OpenBSD, BSDi, etc. please consult - Section 4.2 - - .

PrevHomeNext
Mac OS X Installation NotesUpInstallation General Notes
\ No newline at end of file diff --git a/docs/html/bzhacking.html b/docs/html/bzhacking.html deleted file mode 100644 index d343106247..0000000000 --- a/docs/html/bzhacking.html +++ /dev/null @@ -1,492 +0,0 @@ -Hacking Bugzilla
The Bugzilla Guide
PrevAppendix D. Useful Patches and Utilities for BugzillaNext

D.5. Hacking Bugzilla

The following is a guide for reviewers when checking code into Bugzilla's - CVS repostory at mozilla.org. If you wish to submit patches to Bugzilla, - you should follow the rules and style conventions below. Any code that - does not adhere to these basic rules will not be added to Bugzilla's - codebase. -

D.5.1. Things that have caused problems and should be avoided

  1. Usage of variables in Regular Expressions -

    It is very important that you don't use a variable in a regular - expression unless that variable is supposed to contain an expression. - This especially applies when using grep. You should use: - 

    
grep ($_ eq $value, @array);
-
    -

    -- NOT THIS -- - 

    
grep (/$value/, @array);
-
    -

    If you need to use a non-expression variable inside of an expression, be - sure to quote it properly (using \Q..\E). -

D.5.2. Coding Style for Bugzilla

While it's true that not all of the code currently in Bugzilla adheres to - this (or any) styleguide, it is something that is being worked toward. Therefore, - we ask that all new code (submitted patches and new files) follow this guide - as closely as possible (if you're only changing 1 or 2 lines, you don't have - to reformat the entire file :). -

The Bugzilla development team has decided to adopt the perl style guide as - published by Larry Wall. This giude can be found in "Programming - Perl" (the camel book) or by typing man perlstyle at - your favorite shell prompt. -

What appears below if a brief summary, please refer to the perl style - guide if you don't see your question covered here. It is much better to submit - a patch which fails these criteria than no patch at all, but please try to meet - these minimum standards when submitting code to Bugzilla. -

PrevHomeNext
The Quicksearch UtilityUpGNU Free Documentation License
\ No newline at end of file diff --git a/docs/html/contributors.html b/docs/html/contributors.html deleted file mode 100644 index 5d4e28e0c4..0000000000 --- a/docs/html/contributors.html +++ /dev/null @@ -1,150 +0,0 @@ -Contributors
The Bugzilla Guide
PrevChapter 1. About This GuideNext

1.6. Contributors

Thanks go to these people for significant contributions to this - documentation (in no particular order): -

Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen, Ron - Teitelbaum, Jacob Steenhagen, Joe Robins -

PrevHomeNext
CreditsUpFeedback
\ No newline at end of file diff --git a/docs/html/conventions.html b/docs/html/conventions.html index 2929c57208..40ce3f8c42 100644 --- a/docs/html/conventions.html +++ b/docs/html/conventions.html @@ -79,7 +79,7 @@ NAME="conventions">1.5. Document Conventions


<para>
@@ -399,8 +399,7 @@ Beginning and end of paragraph
 </para>
-
1.1. Copyright Information
1.1.1. GNU Free Documentation License

Version 1.1, March 2000

Copyright (C) 2000 Free Software Foundation, Inc. 59 Temple Place, @@ -570,7 +570,7 @@ NAME="gfdl-howto">How to use this License for your documents

Copyright (c) YEAR YOUR NAME. Permission is granted to copy, diff --git a/docs/html/cust-templates.html b/docs/html/cust-templates.html index 010897c240..f4bda5a42b 100644 --- a/docs/html/cust-templates.html +++ b/docs/html/cust-templates.html @@ -97,10 +97,10 @@ CLASS="section" >

5.7.1. What to Edit

5.7.1. What to Edit

There are several ways to take advantage of Bugzilla's templates, - and which you use depends on what you want to do. The Bugzilla +> There are two different ways of editing of Bugzilla's templates, + and which you use depends mainly on how you upgrade Bugzilla. The template directory structure is that there's a top level directory, en. Underneath that, there - are two directories - default and +> directory and optionally the custom (you may have to create - custom yourself.) The directory. The default - directory contains all the templates shipped with Bugzilla. + directory contains all the templates shipped with Bugzilla, whereas + the custom directory does not exist at first and + must be created if you want to use it.

One method of making customisations is to directly edit the templates - in The first method of making customisations is to directly edit the + templates in template/en/default. This is probably the - best method for small changes, because if you then execute a +>. This is + probably the best method for small changes if you are going to use + the CVS method of upgrading, because if you then execute a cvs update

If you use this method, your installation will break if CVS conflicts + occur. +

The other method is to copy the templates into a mirrored directory - structure under template/en/custom. - This method is better if - you are going to make major changes, because it is guaranteed that - the contents of this directory will not be touched during an upgrade, - and you can then decide whether to continue using your own templates, - or make the effort to merge your changes into the new versions by - hand. This is also the correct method to use if you upgrade Bugzilla - by untarring tarballs over the top, rather than using CVS. It's perfectly - acceptable to mix and match these two methods. +>. The templates + in this directory automatically override those in default. + This is the technique you + need to use if you use the overwriting method of upgrade, because + otherwise your changes will be lost. This method is also better if + you are using the CVS method of upgrading and are going to make major + changes, because it is guaranteed that the contents of this directory + will not be touched during an upgrade, and you can then decide whether + to continue using your own templates, or make the effort to merge your + changes into the new versions by hand.

Editing templates is a good way of doing a "poor man's custom fields". - For example, if you don't use the Status Whiteboard, but want to have - a free-form text entry box for "Build Identifier", then you can just - edit the templates to change the field labels. It's still be called - status_whiteboard internally, but your users don't need to know that. +> If you use this method, your installation may break if incompatible + changes are made to the template interface. If such changes are made + they will be documented in the release notes, provided you are using a + stable release of Bugzilla. If you use using unstable code, you will + need to deal with this one yourself, although if possible the changes + will be mentioned before they occur in the deprecations section of the + previous stable release's release notes.

Don't directly edit the compiled templates in + data/template/* - your + changes will be lost when Template Toolkit recompiles them. +

5.7.2. How To Edit Templates

The syntax of the Template Toolkit language is beyond the scope of this guide. It's reasonably easy to pick up by looking at the current @@ -186,6 +224,31 @@ TARGET="_top" reasons) to always HTML filter things which come from the database or user input, to prevent cross-site scripting attacks.

However, one thing you should take particular care about is the need + to properly HTML filter data that has been passed into the template. + This means that if the data can possibly contain special HTML characters + such as <, and the data was not intended to be HTML, they need to be + converted to entity form, ie &lt;. You use the 'html' filter in the + Template Toolkit to do this. If you fail to do this, you may open up + your installation to cross-site scripting attacks. +

Also note that Bugzilla adds a few filters of its own, that are not + in standard Template Toolkit. In particular, the 'url_quote' filter + can convert characters that are illegal or have special meaning in URLs, + such as &, to the encoded form, ie %26. This actually encodes most + characters (but not the common ones such as letters and numbers and so + on), including the HTML-special characters, so there's never a need to + HTML filter afterwards. +

Editing templates is a good way of doing a "poor man's custom fields". + For example, if you don't use the Status Whiteboard, but want to have + a free-form text entry box for "Build Identifier", then you can just + edit the templates to change the field labels. It's still be called + status_whiteboard internally, but your users don't need to know that. +

Don't directly edit the compiled templates in - data/template/* - your - changes will be lost when Template Toolkit recompiles them. -

If you are making template changes that you intend on submitting back + for inclusion in standard Bugzilla, you should read the relevant + sections of the + Developers' + Guide. +

5.7.2. Template Formats

5.7.3. Template Formats

Some CGIs have the ability to use more than one template. For example, buglist.cgi can output bug lists as RDF or two @@ -284,7 +350,7 @@ CLASS="section" >

5.7.3. Particular Templates

5.7.4. Particular Templates

There are a few templates you may be particularly interested in customising for your installation. @@ -300,14 +366,42 @@ CLASS="command" > global/header.html.tmpl and - : + This defines the header that goes on all Bugzilla pages. + The header includes the banner, which is what appears to users + and is probably what you want to edit instead. However the + header also includes the HTML HEAD section, so you could for + example add a stylesheet or META tag by editing the header. +

global/banner.html.tmpl: + This contains the "banner", the part of the header that appears + at the top of all Bugzilla pages. The default banner is reasonably + barren, so you'll probably want to customise this to give your + installation a distinctive look and feel. It is recommended you + preserve the Bugzilla version number in some form so the version + you are running can be determined, and users know what docs to read. +

global/footer.html.tmpl: - These define the header and footer that go on all Bugzilla pages. - Editing these is a way to quickly get a distinctive look and - feel for your Bugzilla installation. + This defines the footer that goes on all Bugzilla pages. Editing + this is another way to quickly get a distinctive look and feel for + your Bugzilla installation. +

bug/create/user-message.html.tmpl: + This is a message that appears near the top of the bug reporting page. + By modifying this, you can tell your users how they should report + bugs.

CVS

The Bugzilla Guide
PrevChapter 6. Integrating Bugzilla with Third-Party ToolsNext

6.2. CVS

CVS integration is best accomplished, at this point, using the - Bugzilla Email Gateway. There have been some files submitted to allow - greater CVS integration, but we need to make certain that Bugzilla is not - tied into one particular software management package.

Follow the instructions in the FAQ for enabling Bugzilla e-mail - integration. Ensure that your check-in script sends an email to your - Bugzilla e-mail gateway with the subject of - "[Bug XXXX]" - - , and you can have CVS check-in comments append to your Bugzilla bug. If - you have your check-in script include an @resolution field, you can even - change the Bugzilla bug state.

There is also a project, based upon somewhat dated Bugzilla code, - to integrate CVS and Bugzilla through CVS' ability to email. Check it out - at: - http://homepages.kcbbs.gen.nz/~tonyg/ - - , under the - "cvszilla" - - link.

PrevHomeNext
BonsaiUpPerforce SCM
\ No newline at end of file diff --git a/docs/html/dbdoc.html b/docs/html/dbdoc.html index 21dbd2ddb1..49e9b6526f 100644 --- a/docs/html/dbdoc.html +++ b/docs/html/dbdoc.html @@ -133,7 +133,7 @@ CLASS="section" >

B.2.1. Bugzilla Database Basics

B.2.1. Bugzilla Database Basics

If you were like me, at this point you're totally clueless about the internals of MySQL, and if it weren't for this executive order from @@ -247,7 +247,7 @@ CLASS="section" >

B.2.1.1. Bugzilla Database Tables

B.2.1.1. Bugzilla Database Tables

Imagine your MySQL database as a series of spreadsheets, and you won't be too far off. If you use this command:

Software Download Links
The Bugzilla Guide
PrevNext

Appendix B. Software Download Links

All of these sites are current as of April, 2001. Hopefully they'll - stay current for a while.

Apache Web Server: - http://www.apache.org - - Optional web server for Bugzilla, but recommended because of broad user - base and support.

Bugzilla: - http://www.bugzilla.org/ -

MySQL: - http://www.mysql.com/ -

Perl: - http://www.perl.org/ -

CPAN: - http://www.cpan.org/ -

DBI Perl module: - http://www.cpan.org/modules/by-module/DBI/ -

Data::Dumper module: - http://www.cpan.org/modules/by-module/Data/ -

MySQL related Perl modules: - http://www.cpan.org/modules/by-module/Mysql/ -

TimeDate Perl module collection: - http://www.cpan.org/modules/by-module/Date/ -

GD Perl module: - http://www.cpan.org/modules/by-module/GD/ - - Alternately, you should be able to find the latest version of GD at - http://www.boutell.com/gd/ -

Chart::Base module: - http://www.cpan.org/modules/by-module/Chart/ -

(But remember, Bundle::Bugzilla will install all the modules for you.) -

PrevHomeNext
The Bugzilla FAQ The Bugzilla Database
\ No newline at end of file diff --git a/docs/html/errata.html b/docs/html/errata.html deleted file mode 100644 index 5096600954..0000000000 --- a/docs/html/errata.html +++ /dev/null @@ -1,285 +0,0 @@ -ERRATA
The Bugzilla Guide
PrevChapter 4. InstallationNext

4.5. ERRATA

Here are some miscellaneous notes about possible issues you main - run into when you begin your Bugzilla installation. Reference platforms - for Bugzilla installation are Redhat Linux 7.2, Linux-Mandrake 8.0, and - Solaris 8.

If you are installing Bugzilla on S.u.S.e. Linux, or some other - distributions with - "paranoid" - - security options, it is possible that the checksetup.pl script may fail - with the error: - cannot chdir(/var/spool/mqueue): Permission - denied - - This is because your - /var/spool/mqueue - - directory has a mode of - "drwx------" - - . Type - chmod 755 - /var/spool/mqueue - - - as root to fix this problem.
Bugzilla may be installed on Macintosh OS X (10), which is a - unix-based (BSD) operating system. Everything required for Bugzilla on - OS X will install cleanly, but the optional GD perl module which is - used for bug charting requires some additional setup for installation. - Please see the Mac OS X installation section below for details
Release Notes for Bugzilla &bz-ver; are available at - docs/rel_notes.txt - - in your Bugzilla source distribution.
The preferred documentation for Bugzilla is available in docs/, - with a variety of document types available. Please refer to these - documents when installing, configuring, and maintaining your Bugzilla - installation.

Bugzilla is not a package where you can just plop it in a - directory, twiddle a few things, and you're off. Installing Bugzilla - assumes you know your variant of UNIX or Microsoft Windows well, are - familiar with the command line, and are comfortable compiling and - installing a plethora of third-party utilities. To install Bugzilla on - Win32 requires fair Perl proficiency, and if you use a webserver other - than Apache you should be intimately familiar with the security - mechanisms and CGI environment thereof.

Bugzilla has not undergone a complete security review. Security - holes may exist in the code. Great care should be taken both in the - installation and usage of this software. Carefully consider the - implications of installing other network services with Bugzilla.

PrevHomeNext
General Installation NotesUpAdministering Bugzilla
\ No newline at end of file diff --git a/docs/html/extraconfig.html b/docs/html/extraconfig.html index 79279a0ef8..fb8ceb4459 100644 --- a/docs/html/extraconfig.html +++ b/docs/html/extraconfig.html @@ -435,6 +435,10 @@ CLASS="QUOTE" CLASS="QUOTE" >"UTF-8".

Note: using <meta> tags to set the charset is not + recommended, as there's a bug in Netscape 4.x which causes pages + marked up in this way to load twice.

A.1.1. Where can I find information about Bugzilla?
A.1.2. What license is Bugzilla distributed under?
A.1.3. How do I get commercial support for Bugzilla?
A.1.4. What major companies or projects are currently using Bugzilla for bug-tracking?
A.1.5. Who maintains Bugzilla?
A.1.6. How does Bugzilla stack up against other bug-tracking databases?
A.1.7. Why doesn't Bugzilla offer this or that feature or compatability with this other tracking software?
A.1.8. Why MySQL? I'm interested in seeing Bugzilla run on Oracle/Sybase/Msql/PostgreSQL/MSSQL.
A.1.9. Why do the scripts say "/usr/bonsaitools/bin/perl" instead of "/usr/bin/perl" or something else?
A.1.10. Is there an easy way to change the Bugzilla cookie name?
A.2.1. Is Bugzilla web-based, or do you have to have specific software or a specific operating system on your machine?
A.2.2. Can Bugzilla integrate with Perforce (SCM software)?
A.2.3. Does Bugzilla allow the user to track multiple projects?
A.2.4. If I am on many projects, and search for all bugs assigned to me, will Bugzilla list them for me and allow me to sort by project, severity etc?
A.2.5. Does Bugzilla allow attachments (text, screenshots, URLs etc)? If yes, are there any that are NOT allowed?
A.2.6. Does Bugzilla allow us to define our own priorities and levels? Do we have complete freedom to change the labels of fields and format of them, and the choice of acceptable values? @@ -199,35 +199,35 @@ HREF="faq.html#AEN1736" >
A.2.7. Does Bugzilla provide any reporting features, metrics, graphs, etc? You know, the type of stuff that management likes to see. :)
A.2.8. Is there email notification and if so, what do you see when you get an email?
A.2.9. Can email notification be set up to send to multiple people, some on the To List, CC List, BCC List etc?
A.2.10. Do users have to have any particular type of email application?
A.2.11. Does Bugzilla allow data to be imported and exported? If I had outsiders write up a bug report using a MS Word bug template, could that template be imported into "matching" fields? If I wanted to take the results of a query @@ -236,28 +236,28 @@ HREF="faq.html#AEN1767" >
A.2.12. Has anyone converted Bugzilla to another language to be used in other countries? Is it localizable?
A.2.13. Can a user create and save reports? Can they do this in Word format? Excel format?
A.2.14. Does Bugzilla have the ability to search by word, phrase, compound search?
A.2.15. Does Bugzilla provide record locking when there is simultaneous access to the same bug? Does the second person get a notice that the bug is in use or how are they notified? @@ -265,19 +265,19 @@ HREF="faq.html#AEN1790" >
A.2.16. Are there any backup features provided?
A.2.17. Can users be on the system while a backup is in progress?
A.2.18. What type of human resources are needed to be on staff to install and maintain Bugzilla? Specifically, what type of skills does the person need to have? I need to find out if we were to go with Bugzilla, what types of @@ -287,7 +287,7 @@ HREF="faq.html#AEN1806" >
A.2.19. What time frame are we looking at if we decide to hire people to install and maintain the Bugzilla? Is this something that takes hours or weeks to install and a couple of hours per week to maintain and customize or is this @@ -297,7 +297,7 @@ HREF="faq.html#AEN1812" >
A.2.20. Is there any licensing fee or other fees for using Bugzilla? Any out-of-pocket cost other than the bodies needed as identified above?
A.3.1. How do I completely disable MySQL security if it's giving me problems (I've followed the instructions in the installation section of this guide)?
A.3.2. Are there any security problems with Bugzilla?
A.3.3. I've implemented the security fixes mentioned in Chris Yeh's security advisory of 5/10/2000 advising not to run MySQL as root, and am running into problems with MySQL no longer working correctly. @@ -343,48 +343,48 @@ HREF="faq.html#faq-email" >
A.4.1. I have a user who doesn't want to receive any more email from Bugzilla. How do I stop it entirely for this user?
A.4.2. I'm evaluating/testing Bugzilla, and don't want it to send email to anyone but me. How do I do it?
A.4.3. I want whineatnews.pl to whine at something more, or other than, only new bugs. How do I do it?
A.4.4. I don't like/want to use Procmail to hand mail off to bug_email.pl. What alternatives do I have?
A.4.5. How do I set up the email interface to submit/change bugs via email?
A.4.6. Email takes FOREVER to reach me from Bugzilla -- it's extremely slow. What gives?
A.4.7. How come email from Bugzilla changes never reaches me?
A.5.1. I've heard Bugzilla can be used with Oracle?
A.5.2. I think my database might be corrupted, or contain invalid entries. What do I do?
A.5.3. I want to manually edit some entries in my database. How?
A.5.4. I try to add myself as a user, but Bugzilla always tells me my password is wrong.
A.5.5. I think I've set up MySQL permissions correctly, but Bugzilla still can't connect.
A.5.6. How do I synchronize bug information among multiple different Bugzilla databases?
A.6.1. What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
A.6.2. Is there a "Bundle::Bugzilla" equivalent for Win32?
A.6.3. CGI's are failing with a "something.cgi is not a valid Windows NT application" error. Why?
A.6.4. I'm having trouble with the perl modules for NT not being able to talk to to the database.
A.7.1. How do I change my user name (email address) in Bugzilla?
A.7.2. The query page is very confusing. Isn't there a simpler way to query?
A.7.3. I'm confused by the behavior of the "accept" button in the Show Bug form. Why doesn't it assign the bug to me when I accept it?
A.7.4. I can't upload anything into the database via the "Create Attachment" link. What am I doing wrong?
A.7.5. Email submissions to Bugzilla that have attachments end up asking me to save it as a "cgi" file.
A.7.6. How do I change a keyword in Bugzilla, once some bugs are using it?
A.8.1. What bugs are in Bugzilla right now?
A.8.2. How can I change the default priority to a null value? For instance, have the default priority be "---" instead of "P2"?
A.8.3. What's the best way to submit patches? What guidelines should I follow?

A.1.1. Where can I find information about Bugzilla?

A.1.2. What license is Bugzilla distributed under? @@ -614,7 +614,7 @@ CLASS="qandaentry" CLASS="question" >

A.1.3. How do I get commercial support for Bugzilla? @@ -649,7 +649,7 @@ CLASS="qandaentry" CLASS="question" >

A.1.4. What major companies or projects are currently using Bugzilla @@ -757,7 +757,7 @@ CLASS="qandaentry" CLASS="question" >

A.1.5. Who maintains Bugzilla? @@ -785,7 +785,7 @@ CLASS="qandaentry" CLASS="question" >

A.1.6. How does Bugzilla stack up against other bug-tracking databases? @@ -821,7 +821,7 @@ CLASS="qandaentry" CLASS="question" >

A.1.7. Why doesn't Bugzilla offer this or that feature or compatability @@ -859,7 +859,7 @@ CLASS="qandaentry" CLASS="question" >

A.1.8. Why MySQL? I'm interested in seeing Bugzilla run on @@ -883,7 +883,7 @@ CLASS="qandaentry" CLASS="question" >

A.1.9. Why do the scripts say "/usr/bonsaitools/bin/perl" instead of @@ -914,7 +914,7 @@ CLASS="qandaentry" CLASS="question" >

A.1.10. Is there an easy way to change the Bugzilla cookie name? @@ -972,7 +972,7 @@ CLASS="qandaentry" CLASS="question" >

A.2.1. Is Bugzilla web-based, or do you have to have specific software or @@ -996,7 +996,7 @@ CLASS="qandaentry" CLASS="question" >

A.2.2. Can Bugzilla integrate with @@ -1020,7 +1020,7 @@ CLASS="qandaentry" CLASS="question" >

A.2.3. Does Bugzilla allow the user to track multiple projects? @@ -1045,7 +1045,7 @@ CLASS="qandaentry" CLASS="question" >

A.2.4. If I am on many projects, and search for all bugs assigned to me, will @@ -1068,7 +1068,7 @@ CLASS="qandaentry" CLASS="question" >

A.2.5. Does Bugzilla allow attachments (text, screenshots, URLs etc)? If yes, @@ -1095,7 +1095,7 @@ CLASS="qandaentry" CLASS="question" >

A.2.6. Does Bugzilla allow us to define our own priorities and levels? Do we @@ -1130,7 +1130,7 @@ CLASS="qandaentry" CLASS="question" >

A.2.7. Does Bugzilla provide any reporting features, metrics, graphs, etc? You @@ -1166,7 +1166,7 @@ CLASS="qandaentry" CLASS="question" >

A.2.8. Is there email notification and if so, what do you see when you get an @@ -1191,7 +1191,7 @@ CLASS="qandaentry" CLASS="question" >

A.2.9. Can email notification be set up to send to multiple @@ -1214,7 +1214,7 @@ CLASS="qandaentry" CLASS="question" >

A.2.10. Do users have to have any particular @@ -1271,7 +1271,7 @@ CLASS="qandaentry" CLASS="question" >

A.2.11. Does Bugzilla allow data to be imported and exported? If I had outsiders @@ -1316,7 +1316,7 @@ CLASS="qandaentry" CLASS="question" >

A.2.12. Has anyone converted Bugzilla to another language to be used in other @@ -1342,7 +1342,7 @@ CLASS="qandaentry" CLASS="question" >

A.2.13. Can a user create and save reports? Can they do this in Word format? @@ -1365,7 +1365,7 @@ CLASS="qandaentry" CLASS="question" >

A.2.14. Does Bugzilla have the ability to search by word, phrase, compound @@ -1389,7 +1389,7 @@ CLASS="qandaentry" CLASS="question" >

A.2.15. Does Bugzilla provide record locking when there is simultaneous access @@ -1414,7 +1414,7 @@ CLASS="qandaentry" CLASS="question" >

A.2.16. Are there any backup features provided? @@ -1442,7 +1442,7 @@ CLASS="qandaentry" CLASS="question" >

A.2.17. Can users be on the system while a backup is in progress? @@ -1466,7 +1466,7 @@ CLASS="qandaentry" CLASS="question" >

A.2.18. What type of human resources are needed to be on staff to install and @@ -1499,7 +1499,7 @@ CLASS="qandaentry" CLASS="question" >

A.2.19. What time frame are we looking at if we decide to hire people to install @@ -1530,7 +1530,7 @@ CLASS="qandaentry" CLASS="question" >

A.2.20. Is there any licensing fee or other fees for using Bugzilla? Any @@ -1560,7 +1560,7 @@ CLASS="qandaentry" CLASS="question" >

A.3.1. How do I completely disable MySQL security if it's giving me problems @@ -1587,7 +1587,7 @@ CLASS="qandaentry" CLASS="question" >

A.3.2. Are there any security problems with Bugzilla? @@ -1613,7 +1613,7 @@ CLASS="qandaentry" CLASS="question" >

A.3.3. I've implemented the security fixes mentioned in Chris Yeh's security @@ -1645,7 +1645,7 @@ CLASS="qandaentry" CLASS="question" >

A.4.1. I have a user who doesn't want to receive any more email from Bugzilla. @@ -1669,7 +1669,7 @@ CLASS="qandaentry" CLASS="question" >

A.4.2. I'm evaluating/testing Bugzilla, and don't want it to send email to @@ -1693,7 +1693,7 @@ CLASS="qandaentry" CLASS="question" >

A.4.3. I want whineatnews.pl to whine at something more, or other than, only new @@ -1723,7 +1723,7 @@ CLASS="qandaentry" CLASS="question" >

A.4.4. I don't like/want to use Procmail to hand mail off to bug_email.pl. @@ -1739,7 +1739,7 @@ CLASS="answer" You can call bug_email.pl directly from your aliases file, with an entry like this:

bugzilla-daemon: "|/usr/local/bin/bugzilla/contrib/bug_email.pl" @@ -1758,7 +1758,7 @@ CLASS="qandaentry" CLASS="question" >

A.4.5. How do I set up the email interface to submit/change bugs via email? @@ -1781,7 +1781,7 @@ CLASS="qandaentry" CLASS="question" >

A.4.6. Email takes FOREVER to reach me from Bugzilla -- it's extremely slow. @@ -1814,7 +1814,7 @@ CLASS="qandaentry" CLASS="question" >

A.4.7. How come email from Bugzilla changes never reaches me? @@ -1850,7 +1850,7 @@ CLASS="qandaentry" CLASS="question" >

A.5.1. I've heard Bugzilla can be used with Oracle? @@ -1875,7 +1875,7 @@ CLASS="qandaentry" CLASS="question" >

A.5.2. I think my database might be corrupted, or contain invalid entries. What @@ -1920,7 +1920,7 @@ CLASS="qandaentry" CLASS="question" >

A.5.3. I want to manually edit some entries in my database. How? @@ -1947,7 +1947,7 @@ CLASS="qandaentry" CLASS="question" >

A.5.4. I try to add myself as a user, but Bugzilla always tells me my password is wrong. @@ -1971,7 +1971,7 @@ CLASS="qandaentry" CLASS="question" >

A.5.5. I think I've set up MySQL permissions correctly, but Bugzilla still can't @@ -1998,7 +1998,7 @@ CLASS="qandaentry" CLASS="question" >

A.5.6. How do I synchronize bug information among multiple different Bugzilla @@ -2040,7 +2040,7 @@ CLASS="qandaentry" CLASS="question" >

A.6.1. What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)? @@ -2063,7 +2063,7 @@ CLASS="qandaentry" CLASS="question" >

A.6.2. Is there a "Bundle::Bugzilla" equivalent for Win32? @@ -2087,7 +2087,7 @@ CLASS="qandaentry" CLASS="question" >

A.6.3. CGI's are failing with a "something.cgi is not a valid Windows NT @@ -2108,7 +2108,7 @@ CLASS="answer" >

Microsoft has some advice on this matter, as well:

"Set application mappings. In the ISM, map the extension for the script @@ -2131,7 +2131,7 @@ CLASS="qandaentry" CLASS="question" >

A.6.4. I'm having trouble with the perl modules for NT not being able to talk to @@ -2204,7 +2204,7 @@ CLASS="qandaentry" CLASS="question" >

A.7.1. How do I change my user name (email address) in Bugzilla? @@ -2227,7 +2227,7 @@ CLASS="qandaentry" CLASS="question" >

A.7.2. The query page is very confusing. Isn't there a simpler way to query? @@ -2251,7 +2251,7 @@ CLASS="qandaentry" CLASS="question" >

A.7.3. I'm confused by the behavior of the "accept" button in the Show Bug form. @@ -2304,7 +2304,7 @@ CLASS="qandaentry" CLASS="question" >

A.7.4. I can't upload anything into the database via the "Create Attachment" @@ -2329,7 +2329,7 @@ CLASS="qandaentry" CLASS="question" >

A.7.5. Email submissions to Bugzilla that have attachments end up asking me to @@ -2354,7 +2354,7 @@ CLASS="qandaentry" CLASS="question" >

A.7.6. How do I change a keyword in Bugzilla, once some bugs are using it? @@ -2384,7 +2384,7 @@ CLASS="qandaentry" CLASS="question" >

A.8.1. What bugs are in Bugzilla right now? @@ -2428,7 +2428,7 @@ CLASS="qandaentry" CLASS="question" >

A.8.2. How can I change the default priority to a null value? For instance, have the default @@ -2458,7 +2458,7 @@ CLASS="qandaentry" CLASS="question" >

A.8.3. What's the best way to submit patches? What guidelines should I follow? diff --git a/docs/html/feedback.html b/docs/html/feedback.html deleted file mode 100644 index 2fec0aa05e..0000000000 --- a/docs/html/feedback.html +++ /dev/null @@ -1,161 +0,0 @@ -Feedback

The Bugzilla Guide
PrevChapter 1. About This GuideNext
PrevHomeNext
ContributorsUpTranslations
\ No newline at end of file diff --git a/docs/html/geninstall.html b/docs/html/geninstall.html deleted file mode 100644 index 15d700a4cf..0000000000 --- a/docs/html/geninstall.html +++ /dev/null @@ -1,509 +0,0 @@ -General Installation Notes
The Bugzilla Guide
PrevChapter 4. InstallationNext

4.5. General Installation Notes

4.5.2. Upgrading From Previous Versions

A plain Bugzilla is fairly easy to upgrade from one version to a - newer one. However, things get a bit more complicated if you've made - changes to Bugzilla's code. In this case, you may have to re-make or - reapply those changes. It is recommended that you take a backup of your - database and your entire Bugzilla installation before attempting an - upgrade. You can upgrade a 'clean' installation by untarring a new - tarball over the old installation. If you are upgrading from 2.12 or - later, you can type - cvs -z3 update - - , and resolve conflicts if there are any.

Because the developers of Bugzilla are constantly adding new - tables, columns and fields, you'll probably get SQL errors if you just - update the code and attempt to use Bugzilla. Always run the - checksetup.pl - script whenever you upgrade your installation.

If you are running Bugzilla version 2.8 or lower, and wish to - upgrade to the latest version, please consult the file, - "UPGRADING-pre-2.8" in the Bugzilla root directory after untarring the - archive.

4.5.3. .htaccess - files and security

To enhance the security of your Bugzilla installation, Bugzilla's - checksetup.pl script will generate - .htaccess - - - files which the Apache webserver can use to restrict access to the - bugzilla data files. - These .htaccess files will not work with Apache 1.2.x - but this - has security holes, so you shouldn't be using it anyway. -

If you are using an alternate provider of - webdot - - services for graphing (as described when viewing - editparams.cgi - - in your web browser), you will need to change the ip address in - data/webdot/.htaccess - - to the ip address of the webdot server that you are using.

-

The default .htaccess file may not provide adequate access - restrictions, depending on your web server configuration. Be sure to - check the <Directory> entries for your Bugzilla directory so that - the - .htaccess - - file is allowed to override web server defaults. For instance, let's - assume your installation of Bugzilla is installed to - /usr/local/bugzilla - - . You should have this <Directory> entry in your - httpd.conf - - file:

-

  <Directory /usr/local/bugzilla/>
-  Options +FollowSymLinks +Indexes +Includes +ExecCGI
-  AllowOverride All
-</Directory>
-
- -

The important part above is - "AllowOverride All" - - . Without that, the - .htaccess - - file created by - checksetup.pl - - will not have sufficient permissions to protect your Bugzilla - installation.

If you are using Internet Information Server (IIS) or another - web server which does not observe - .htaccess - conventions, you can disable their creation by editing - localconfig - and setting the - $create_htaccess - variable to - 0. -

4.5.5. Preventing untrusted Bugzilla content from executing malicious - Javascript code

It is possible for a Bugzilla to execute malicious Javascript - code. Due to internationalization concerns, we are unable to - incorporate the code changes necessary to fulfill the CERT advisory - requirements mentioned in - http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3. - Executing the following code snippet from a UNIX command shell will - rectify the problem if your Bugzilla installation is intended for an - English-speaking audience. As always, be sure your Bugzilla - installation has a good backup before making changes, and I recommend - you understand what the script is doing before executing it.

bash# perl -pi -e "s/Content-Type\: text\/html/Content-Type\: text\/html\; charset=ISO-8859-1/i" *.cgi *.pl
-
-

All this one-liner command does is search for all instances of - "Content-type: text/html" - - and replaces it with - "Content-Type: text/html; charset=ISO-8859-1" - - . This specification prevents possible Javascript attacks on the - browser, and is suggested for all English-speaking sites. For - non-English-speaking Bugzilla sites, I suggest changing - "ISO-8859-1", above, to - "UTF-8".

PrevHomeNext
Mac OS X Installation NotesUpTroubleshooting
\ No newline at end of file diff --git a/docs/html/gfdl-0.html b/docs/html/gfdl-0.html deleted file mode 100644 index 3da4eb32bf..0000000000 --- a/docs/html/gfdl-0.html +++ /dev/null @@ -1,163 +0,0 @@ -PREAMBLE
The Bugzilla Guide
PrevAppendix A. GNU Free Documentation LicenseNext

0. PREAMBLE

The purpose of this License is to make a manual, textbook, or other - written document "free" in the sense of freedom: to assure everyone the - effective freedom to copy and redistribute it, with or without modifying - it, either commercially or noncommercially. Secondarily, this License - preserves for the author and publisher a way to get credit for their - work, while not being considered responsible for modifications made by - others.

This License is a kind of "copyleft", which means that derivative - works of the document must themselves be free in the same sense. It - complements the GNU General Public License, which is a copyleft license - designed for free software.

We have designed this License in order to use it for manuals for - free software, because free software needs free documentation: a free - program should come with manuals providing the same freedoms that the - software does. But this License is not limited to software manuals; it - can be used for any textual work, regardless of subject matter or whether - it is published as a printed book. We recommend this License principally - for works whose purpose is instruction or reference.

PrevHomeNext
GNU Free Documentation LicenseUpAPPLICABILITY AND DEFINITIONS
\ No newline at end of file diff --git a/docs/html/gfdl-1.html b/docs/html/gfdl-1.html deleted file mode 100644 index 0ff95b5cd5..0000000000 --- a/docs/html/gfdl-1.html +++ /dev/null @@ -1,198 +0,0 @@ -APPLICABILITY AND DEFINITIONS
The Bugzilla Guide
PrevAppendix A. GNU Free Documentation LicenseNext

1. APPLICABILITY AND DEFINITIONS

This License applies to any manual or other work that contains a - notice placed by the copyright holder saying it can be distributed under - the terms of this License. The "Document", below, refers to any such - manual or work. Any member of the public is a licensee, and is addressed - as "you".

A "Modified Version" of the Document means any work containing the - Document or a portion of it, either copied verbatim, or with - modifications and/or translated into another language.

A "Secondary Section" is a named appendix or a front-matter section - of the Document that deals exclusively with the relationship of the - publishers or authors of the Document to the Document's overall subject - (or to related matters) and contains nothing that could fall directly - within that overall subject. (For example, if the Document is in part a - textbook of mathematics, a Secondary Section may not explain any - mathematics.) The relationship could be a matter of historical connection - with the subject or with related matters, or of legal, commercial, - philosophical, ethical or political position regarding them.

The "Invariant Sections" are certain Secondary Sections whose - titles are designated, as being those of Invariant Sections, in the - notice that says that the Document is released under this License.

The "Cover Texts" are certain short passages of text that are - listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says - that the Document is released under this License.

A "Transparent" copy of the Document means a machine-readable copy, - represented in a format whose specification is available to the general - public, whose contents can be viewed and edited directly and - straightforwardly with generic text editors or (for images composed of - pixels) generic paint programs or (for drawings) some widely available - drawing editor, and that is suitable for input to text formatters or for - automatic translation to a variety of formats suitable for input to text - formatters. A copy made in an otherwise Transparent file format whose - markup has been designed to thwart or discourage subsequent modification - by readers is not Transparent. A copy that is not "Transparent" is called - "Opaque".

Examples of suitable formats for Transparent copies include plain - ASCII without markup, Texinfo input format, LaTeX input format, SGML or - XML using a publicly available DTD, and standard-conforming simple HTML - designed for human modification. Opaque formats include PostScript, PDF, - proprietary formats that can be read and edited only by proprietary word - processors, SGML or XML for which the DTD and/or processing tools are not - generally available, and the machine-generated HTML produced by some word - processors for output purposes only.

The "Title Page" means, for a printed book, the title page itself, - plus such following pages as are needed to hold, legibly, the material - this License requires to appear in the title page. For works in formats - which do not have any title page as such, "Title Page" means the text - near the most prominent appearance of the work's title, preceding the - beginning of the body of the text.

PrevHomeNext
PREAMBLEUpVERBATIM COPYING
\ No newline at end of file diff --git a/docs/html/gfdl-10.html b/docs/html/gfdl-10.html deleted file mode 100644 index f80115ce40..0000000000 --- a/docs/html/gfdl-10.html +++ /dev/null @@ -1,163 +0,0 @@ -FUTURE REVISIONS OF THIS LICENSE
The Bugzilla Guide
PrevAppendix A. GNU Free Documentation LicenseNext

10. FUTURE REVISIONS OF THIS LICENSE

The Free Software Foundation may publish new, revised versions of - the GNU Free Documentation License from time to time. Such new versions - will be similar in spirit to the present version, but may differ in - detail to address new problems or concerns. See - http://www.gnu.org/copyleft/ - - .

Each version of the License is given a distinguishing version - number. If the Document specifies that a particular numbered version of - this License "or any later version" applies to it, you have the option of - following the terms and conditions either of that specified version or of - any later version that has been published (not as a draft) by the Free - Software Foundation. If the Document does not specify a version number of - this License, you may choose any version ever published (not as a draft) - by the Free Software Foundation.

PrevHomeNext
TERMINATIONUpHow to use this License for your documents
\ No newline at end of file diff --git a/docs/html/gfdl-2.html b/docs/html/gfdl-2.html deleted file mode 100644 index 9ff047b60b..0000000000 --- a/docs/html/gfdl-2.html +++ /dev/null @@ -1,155 +0,0 @@ -VERBATIM COPYING
The Bugzilla Guide
PrevAppendix A. GNU Free Documentation LicenseNext
PrevHomeNext
APPLICABILITY AND DEFINITIONSUpCOPYING IN QUANTITY
\ No newline at end of file diff --git a/docs/html/gfdl-3.html b/docs/html/gfdl-3.html deleted file mode 100644 index 948340e2ef..0000000000 --- a/docs/html/gfdl-3.html +++ /dev/null @@ -1,177 +0,0 @@ -COPYING IN QUANTITY
The Bugzilla Guide
PrevAppendix A. GNU Free Documentation LicenseNext

3. COPYING IN QUANTITY

If you publish printed copies of the Document numbering more than - 100, and the Document's license notice requires Cover Texts, you must - enclose the copies in covers that carry, clearly and legibly, all these - Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts - on the back cover. Both covers must also clearly and legibly identify you - as the publisher of these copies. The front cover must present the full - title with all words of the title equally prominent and visible. You may - add other material on the covers in addition. Copying with changes - limited to the covers, as long as they preserve the title of the Document - and satisfy these conditions, can be treated as verbatim copying in other - respects.

If the required texts for either cover are too voluminous to fit - legibly, you should put the first ones listed (as many as fit reasonably) - on the actual cover, and continue the rest onto adjacent pages.

If you publish or distribute Opaque copies of the Document - numbering more than 100, you must either include a machine-readable - Transparent copy along with each Opaque copy, or state in or with each - Opaque copy a publicly-accessible computer-network location containing a - complete Transparent copy of the Document, free of added material, which - the general network-using public has access to download anonymously at no - charge using public-standard network protocols. If you use the latter - option, you must take reasonably prudent steps, when you begin - distribution of Opaque copies in quantity, to ensure that this - Transparent copy will remain thus accessible at the stated location until - at least one year after the last time you distribute an Opaque copy - (directly or through your agents or retailers) of that edition to the - public.

It is requested, but not required, that you contact the authors of - the Document well before redistributing any large number of copies, to - give them a chance to provide you with an updated version of the - Document.

PrevHomeNext
VERBATIM COPYINGUpMODIFICATIONS
\ No newline at end of file diff --git a/docs/html/gfdl-4.html b/docs/html/gfdl-4.html deleted file mode 100644 index d0acc975c7..0000000000 --- a/docs/html/gfdl-4.html +++ /dev/null @@ -1,271 +0,0 @@ -MODIFICATIONS
The Bugzilla Guide
PrevAppendix A. GNU Free Documentation LicenseNext

4. MODIFICATIONS

You may copy and distribute a Modified Version of the Document - under the conditions of sections 2 and 3 above, provided that you release - the Modified Version under precisely this License, with the Modified - Version filling the role of the Document, thus licensing distribution and - modification of the Modified Version to whoever possesses a copy of it. - In addition, you must do these things in the Modified Version:

  1. Use in the Title Page (and on the covers, if any) a title - distinct from that of the Document, and from those of previous - versions (which should, if there were any, be listed in the History - section of the Document). You may use the same title as a previous - version if the original publisher of that version gives - permission.

  2. List on the Title Page, as authors, one or more persons or - entities responsible for authorship of the modifications in the - Modified Version, together with at least five of the principal - authors of the Document (all of its principal authors, if it has less - than five).

  3. State on the Title page the name of the publisher of the - Modified Version, as the publisher.

  4. Preserve all the copyright notices of the Document.

  5. Add an appropriate copyright notice for your modifications - adjacent to the other copyright notices.

  6. Include, immediately after the copyright notices, a license - notice giving the public permission to use the Modified Version under - the terms of this License, in the form shown in the Addendum - below.

  7. Preserve in that license notice the full lists of Invariant - Sections and required Cover Texts given in the Document's license - notice.

  8. Include an unaltered copy of this License.

  9. Preserve the section entitled "History", and its title, and add - to it an item stating at least the title, year, new authors, and - publisher of the Modified Version as given on the Title Page. If - there is no section entitled "History" in the Document, create one - stating the title, year, authors, and publisher of the Document as - given on its Title Page, then add an item describing the Modified - Version as stated in the previous sentence.

  10. Preserve the network location, if any, given in the Document - for public access to a Transparent copy of the Document, and likewise - the network locations given in the Document for previous versions it - was based on. These may be placed in the "History" section. You may - omit a network location for a work that was published at least four - years before the Document itself, or if the original publisher of the - version it refers to gives permission.

  11. In any section entitled "Acknowledgements" or "Dedications", - preserve the section's title, and preserve in the section all the - substance and tone of each of the contributor acknowledgements and/or - dedications given therein.

  12. Preserve all the Invariant Sections of the Document, unaltered - in their text and in their titles. Section numbers or the equivalent - are not considered part of the section titles.

  13. Delete any section entitled "Endorsements". Such a section may - not be included in the Modified Version.

  14. Do not retitle any existing section as "Endorsements" or to - conflict in title with any Invariant Section.

If the Modified Version includes new front-matter sections or - appendices that qualify as Secondary Sections and contain no material - copied from the Document, you may at your option designate some or all of - these sections as invariant. To do this, add their titles to the list of - Invariant Sections in the Modified Version's license notice. These titles - must be distinct from any other section titles.

You may add a section entitled "Endorsements", provided it contains - nothing but endorsements of your Modified Version by various parties--for - example, statements of peer review or that the text has been approved by - an organization as the authoritative definition of a standard.

You may add a passage of up to five words as a Front-Cover Text, - and a passage of up to 25 words as a Back-Cover Text, to the end of the - list of Cover Texts in the Modified Version. Only one passage of - Front-Cover Text and one of Back-Cover Text may be added by (or through - arrangements made by) any one entity. If the Document already includes a - cover text for the same cover, previously added by you or by arrangement - made by the same entity you are acting on behalf of, you may not add - another; but you may replace the old one, on explicit permission from the - previous publisher that added the old one.

The author(s) and publisher(s) of the Document do not by this - License give permission to use their names for publicity for or to assert - or imply endorsement of any Modified Version.

PrevHomeNext
COPYING IN QUANTITYUpCOMBINING DOCUMENTS
\ No newline at end of file diff --git a/docs/html/gfdl-5.html b/docs/html/gfdl-5.html deleted file mode 100644 index 65d8c5f9fa..0000000000 --- a/docs/html/gfdl-5.html +++ /dev/null @@ -1,164 +0,0 @@ -COMBINING DOCUMENTS
The Bugzilla Guide
PrevAppendix A. GNU Free Documentation LicenseNext

5. COMBINING DOCUMENTS

You may combine the Document with other documents released under - this License, under the terms defined in section 4 above for modified - versions, provided that you include in the combination all of the - Invariant Sections of all of the original documents, unmodified, and list - them all as Invariant Sections of your combined work in its license - notice.

The combined work need only contain one copy of this License, and - multiple identical Invariant Sections may be replaced with a single copy. - If there are multiple Invariant Sections with the same name but different - contents, make the title of each such section unique by adding at the end - of it, in parentheses, the name of the original author or publisher of - that section if known, or else a unique number. Make the same adjustment - to the section titles in the list of Invariant Sections in the license - notice of the combined work.

In the combination, you must combine any sections entitled - "History" in the various original documents, forming one section entitled - "History"; likewise combine any sections entitled "Acknowledgements", and - any sections entitled "Dedications". You must delete all sections - entitled "Endorsements."

PrevHomeNext
MODIFICATIONSUpCOLLECTIONS OF DOCUMENTS
\ No newline at end of file diff --git a/docs/html/gfdl-6.html b/docs/html/gfdl-6.html deleted file mode 100644 index a37fd9867c..0000000000 --- a/docs/html/gfdl-6.html +++ /dev/null @@ -1,154 +0,0 @@ -COLLECTIONS OF DOCUMENTS
The Bugzilla Guide
PrevAppendix A. GNU Free Documentation LicenseNext
PrevHomeNext
COMBINING DOCUMENTSUpAGGREGATION WITH INDEPENDENT WORKS
\ No newline at end of file diff --git a/docs/html/gfdl-7.html b/docs/html/gfdl-7.html deleted file mode 100644 index 7b27d80532..0000000000 --- a/docs/html/gfdl-7.html +++ /dev/null @@ -1,157 +0,0 @@ -AGGREGATION WITH INDEPENDENT WORKS
The Bugzilla Guide
PrevAppendix A. GNU Free Documentation LicenseNext

7. AGGREGATION WITH INDEPENDENT WORKS

A compilation of the Document or its derivatives with other - separate and independent documents or works, in or on a volume of a - storage or distribution medium, does not as a whole count as a Modified - Version of the Document, provided no compilation copyright is claimed for - the compilation. Such a compilation is called an "aggregate", and this - License does not apply to the other self-contained works thus compiled - with the Document, on account of their being thus compiled, if they are - not themselves derivative works of the Document.

If the Cover Text requirement of section 3 is applicable to these - copies of the Document, then if the Document is less than one quarter of - the entire aggregate, the Document's Cover Texts may be placed on covers - that surround only the Document within the aggregate. Otherwise they must - appear on covers around the whole aggregate.

PrevHomeNext
COLLECTIONS OF DOCUMENTSUpTRANSLATION
\ No newline at end of file diff --git a/docs/html/gfdl-8.html b/docs/html/gfdl-8.html deleted file mode 100644 index 3cd26498de..0000000000 --- a/docs/html/gfdl-8.html +++ /dev/null @@ -1,153 +0,0 @@ -TRANSLATION
The Bugzilla Guide
PrevAppendix A. GNU Free Documentation LicenseNext
PrevHomeNext
AGGREGATION WITH INDEPENDENT WORKSUpTERMINATION
\ No newline at end of file diff --git a/docs/html/gfdl-9.html b/docs/html/gfdl-9.html deleted file mode 100644 index c66e8a93fd..0000000000 --- a/docs/html/gfdl-9.html +++ /dev/null @@ -1,150 +0,0 @@ -TERMINATION
The Bugzilla Guide
PrevAppendix A. GNU Free Documentation LicenseNext
PrevHomeNext
TRANSLATIONUpFUTURE REVISIONS OF THIS LICENSE
\ No newline at end of file diff --git a/docs/html/gfdl-howto.html b/docs/html/gfdl-howto.html deleted file mode 100644 index 08070e866b..0000000000 --- a/docs/html/gfdl-howto.html +++ /dev/null @@ -1,168 +0,0 @@ -How to use this License for your documents
The Bugzilla Guide
PrevAppendix A. GNU Free Documentation LicenseNext

How to use this License for your documents

To use this License in a document you have written, include a copy - of the License in the document and put the following copyright and - license notices just after the title page:

Copyright (c) YEAR YOUR NAME. Permission is granted to copy, - distribute and/or modify this document under the terms of the GNU Free - Documentation License, Version 1.1 or any later version published by - the Free Software Foundation; with the Invariant Sections being LIST - THEIR TITLES, with the Front-Cover Texts being LIST, and with the - Back-Cover Texts being LIST. A copy of the license is included in the - section entitled "GNU Free Documentation License".

If you have no Invariant Sections, write "with no Invariant - Sections" instead of saying which ones are invariant. If you have no - Front-Cover Texts, write "no Front-Cover Texts" instead of "Front-Cover - Texts being LIST"; likewise for Back-Cover Texts.

If your document contains nontrivial examples of program code, we - recommend releasing these examples in parallel under your choice of free - software license, such as the GNU General Public License, to permit their - use in free software.

PrevHomeNext
FUTURE REVISIONS OF THIS LICENSEUpDisclaimer
\ No newline at end of file diff --git a/docs/html/gfdl.html b/docs/html/gfdl.html deleted file mode 100644 index 91c8e80a59..0000000000 --- a/docs/html/gfdl.html +++ /dev/null @@ -1,221 +0,0 @@ -GNU Free Documentation License
The Bugzilla Guide
PrevNext
PrevHomeNext
Copyright InformationUpPREAMBLE
\ No newline at end of file diff --git a/docs/html/glossary.html b/docs/html/glossary.html index e830ed5824..c6251cb609 100644 --- a/docs/html/glossary.html +++ b/docs/html/glossary.html @@ -68,7 +68,7 @@ CLASS="glossdiv" >

0-9, high ascii

0-9, high ascii
MySQL Permissions & Grant Tables
The Bugzilla Guide
PrevAppendix B. The Bugzilla DatabaseNext

B.3. MySQL Permissions & Grant Tables

The following portion of documentation comes from my answer to an - old discussion of Keystone, a cool product that does trouble-ticket - tracking for IT departments. I wrote this post to the Keystone support - group regarding MySQL grant table permissions, and how to use them - effectively. It is badly in need of updating, as I believe MySQL has - added a field or two to the grant tables since this time, but it serves - as a decent introduction and troubleshooting document for grant table - issues. I used Keynote to track my troubles until I discovered - Bugzilla, which gave me a whole new set of troubles to work on : ) - Although it is of limited use, it still has SOME use, thus it's still - included.

Please note, however, that I was a relatively new user to MySQL - at the time. Some of my suggestions, particularly in how to set up - security, showed a terrible lack of security-related database - experience.

From matt_barnson@singletrac.com Wed Jul 7 09:00:07 1999
-    Date: Mon, 1 Mar 1999 21:37:04 -0700 From: Matthew Barnson
-    matt_barnson@singletrac.com To: keystone-users@homeport.org Subject:
-    [keystone-users] Grant Tables FAQ [The following text is in the
-    "iso-8859-1" character set] [Your display is set for the "US-ASCII"
-    character set] [Some characters may be displayed incorrectly] Maybe we
-    can include this rambling message in the Keystone FAQ? It gets asked a
-    lot, and the only option current listed in the FAQ is
-    "--skip-grant-tables". Really, you can't go wrong by reading section 6 of
-    the MySQL manual, at http://www.mysql.com/Manual/manual.html. I am sure
-    their description is better than mine. MySQL runs fine without
-    permissions set up correctly if you run the mysql daemon with the
-    "--skip-grant-tables" option. Running this way denies access to nobody.
-    Unfortunately, unless you've got yourself firewalled it also opens the
-    potential for abuse if someone knows you're running it. Additionally, the
-    default permissions for MySQL allow anyone at localhost access to the
-    database if the database name begins with "test_" or is named "test"
-    (i.e. "test_keystone"). You can change the name of your database in the
-    keystone.conf file ($sys_dbname). This is the way I am doing it for some
-    of my databases, and it works fine. The methods described below assume
-    you're running MySQL on the same box as your webserver, and that you
-    don't mind if your $sys_dbuser for Keystone has superuser access. See
-    near the bottom of this message for a description of what each field
-    does. Method #1: 1. cd /var/lib #location where you'll want to run
-    /usr/bin/mysql_install_db shell script from to get it to work. 2. ln -s
-    mysql data # soft links the "mysql" directory to "data", which is what
-    mysql_install_db expects. Alternately, you can edit mysql_install_db and
-    change all the "./data" references to "./mysql". 3. Edit
-    /usr/bin/mysql_install_db with your favorite text editor (vi, emacs, jot,
-    pico, etc.) A) Copy the "INSERT INTO db VALUES
-    ('%','test\_%','','Y','Y','Y','Y','Y','Y');" and paste it immediately
-    after itself. Chage the 'test\_%' value to 'keystone', or the value of
-    $sys_dbname in keystone.conf. B) If you are running your keystone
-    database with any user, you'll need to copy the "INSERT INTO user VALUES
-    ('localhost','root','','Y','Y','Y','Y','Y','Y','Y','Y','Y','Y');" line
-    after itself and change 'root' to the name of the keystone database user
-    ($sys_dbuser) in keystone.conf. # adds entries to the script to create
-    grant tables for specific hosts and users. The user you set up has
-    super-user access ($sys_dbuser) -- you may or may not want this. The
-    layout of mysql_install_db is really very uncomplicated. 4.
-    /usr/bin/mysqladmin shutdown # ya gotta shut it down before you can
-    reinstall the grant tables! 5. rm -i /var/lib/mysql/mysql/*.IS?' and
-    answer 'Y' to the deletion questions. # nuke your current grant tables.
-    This WILL NOT delete any other databases than your grant tables. 6.
-    /usr/bin/mysql_install_db # run the script you just edited to install
-    your new grant tables. 7. mysqladmin -u root password (new_password) #
-    change the root MySQL password, or else anyone on localhost can login to
-    MySQL as root and make changes. You can skip this step if you want
-    keystone to connect as root with no password. 8. mysqladmin -u
-    (webserver_user_name) password (new_password) # change the password of
-    the $sys_dbuser. Note that you will need to change the password in the
-    keystone.conf file as well in $sys_dbpasswd, and if your permissions are
-    set up incorrectly anybody can type the URL to your keystone.conf file
-    and get the password. Not that this will help them much if your
-    permissions are set to @localhost. Method #2: easier, but a pain
-    reproducing if you have to delete your grant tables. This is the
-    "recommended" method for altering grant tables in MySQL. I don't use it
-    because I like the other way :) shell> mysql --user=root keystone
-    mysql> GRANT
-    SELECT,INSERT,UPDATE,DELETE,INDEX,ALTER,CREATE,DROP,RELOAD,SHUTDOWN,PROCESS,
-    FILE, ON keystone.* TO <$sys_dbuser name>@localhost IDENTIFIED BY
-    '(password)' WITH GRANT OPTION; OR mysql> GRANT ALL PRIVILEGES ON
-    keystone.* TO <$sys_dbuser name>@localhost IDENTIFIED BY
-    '(password)' WITH GRANT OPTION; # this grants the required permissions to
-    the keystone ($sys_dbuser) account defined in keystone.conf. However, if
-    you are runnning many different MySQL-based apps, as we are, it's
-    generally better to edit the mysql_install_db script to be able to
-    quickly reproduce your permissions structure again. Note that the FILE
-    privelege and WITH GRANT OPTION may not be in your best interest to
-    include. GRANT TABLE FIELDS EXPLANATION: Quick syntax summary: "%" in
-    MySQL is a wildcard. I.E., if you are defining your DB table and in the
-    'host' field and enter '%', that means that any host can access that
-    database. Of course, that host must also have a valid db user in order to
-    do anything useful. 'db'=name of database. In our case, it should be
-    "keystone". "user" should be your "$sys_dbuser" defined in keystone.conf.
-    Note that you CANNOT add or change a password by using the "INSERT INTO
-    db (X)" command -- you must change it with the mysql -u command as
-    defined above. Passwords are stored encrypted in the MySQL database, and
-    if you try to enter it directly into the table they will not match.
-    TABLE: USER. Everything after "password" is a privelege granted (Y/N).
-    This table controls individual user global access rights.
-    'host','user','password','select','insert','update','delete','index','alter'
-    ,'create','drop','grant','reload','shutdown','process','file' TABLE: DB.
-    This controls access of USERS to databases.
-    'host','db','user','select','insert','update','delete','index','alter','crea
-    te','drop','grant' TABLE: HOST. This controls which HOSTS are allowed
-    what global access rights. Note that the HOST table, USER table, and DB
-    table are very closely connected -- if an authorized USER attempts an SQL
-    request from an unauthorized HOST, she's denied. If a request from an
-    authorized HOST is not an authorized USER, it is denied. If a globally
-    authorized USER does not have rights to a certain DB, she's denied. Get
-    the picture?
-    'host','db','select','insert','update','delete','index','alter','create','dr
-    op','grant' You should now have a working knowledge of MySQL grant
-    tables. If there is anything I've left out of this answer that you feel
-    is pertinent, or if my instructions don't work for you, please let me
-    know and I'll re-post this letter again, corrected. I threw it together
-    one night out of exasperation for all the newbies who don't know squat
-    about MySQL yet, so it is almost guaranteed to have errors. Once again,
-    you can't go wrong by reading section 6 of the MySQL manual. It is more
-    detailed than I! http://www.mysql.com/Manual/manual.html.

PrevHomeNext
MySQL Bugzilla Database IntroductionUpUseful Patches and Utilities for Bugzilla
\ No newline at end of file diff --git a/docs/html/how.html b/docs/html/how.html index 68d13ee307..6d7018a0c0 100644 --- a/docs/html/how.html +++ b/docs/html/how.html @@ -78,7 +78,7 @@ NAME="how">3.1. How do I use Bugzilla?This section contains information for end-users of Bugzilla. There is a Bugzilla test installation, called Landfill, @@ -99,9 +99,9 @@ NAME="myaccount">3.1.1. Create a Bugzilla Account http://landfill.tequilarista.org/bugzilla-tip/ http://landfill.bugzilla.org/bugzilla-tip/

3.1.2. Anatomy of a BugThe core of Bugzilla is the screen which displays a particular bug. It's a good place to explain some Bugzilla concepts. Bug 1 on Landfill @@ -431,9 +431,9 @@ NAME="query">3.1.3. Searching for Bugs landfill.tequilarista.org/bugzilla-tip/query.cgi landfill.bugzilla.org/bugzilla-tip/query.cgi .

Highly advanced querying is done using Boolean Charts, which have their own context-sensitive help @@ -535,7 +535,7 @@ NAME="bugreports">3.1.5. Filing BugsYears of bug writing experience has been distilled for your reading pleasure into the Bug Writing Guidelines. @@ -555,13 +555,13 @@ TYPE="1" >

Go to Landfill in your browser and click Enter a new bug report. diff --git a/docs/html/index.html b/docs/html/index.html index 4f78e47531..51024b628b 100644 --- a/docs/html/index.html +++ b/docs/html/index.html @@ -65,39 +65,6 @@ NAME="AEN13">

IMPORTANT: this documentation is currently being - updated for the Bugzilla 2.16 release and is in an unusual state of - flux. Even more than normal, don't believe everything, - or even anything, you read. -

-

This documentation is maintained in DocBook 4.1.2 XML format. Changes are best submitted as plain text or SGML diffs, attached @@ -390,19 +357,19 @@ CLASS="LOT" >

4-1. Installing ActivePerl ppd Modules on Microsoft Windows
4-2. Installing OpenInteract ppd Modules manually on Microsoft Windows
4-3. Removing encrypt() for Windows NT Bugzilla version 2.12 or earlier
User Preferences
The Bugzilla Guide
PrevChapter 3. Using BugzillaNext

3.2. User Preferences

Once you have logged in, you can customise various aspects of - Bugzilla via the "Edit prefs" link in the page footer. - The preferences are split into four tabs:

3.2.2. Email Settings

On this tab you can reduce or increase the amount of email sent - you from Bugzilla, opting in our out depending on your relationship to - the bug and the change that was made to it. (Note that you can also do - client-side filtering using the X-Bugzilla-Reason header which Bugzilla - adds to all bugmail.)

By entering user email names, delineated by commas, into the - "Users to watch" text entry box you can receive a copy of all the - bugmail of other users (security settings permitting.) This powerful - functionality enables seamless transitions as developers change - projects, managers wish to get in touch with the issues faced by their - direct reports, or users go on vacation.

The ability to watch other users may not be available in all - Bugzilla installations. If you can't see it, ask your - administrator.

PrevHomeNext
How do I use Bugzilla?UpInstallation
\ No newline at end of file diff --git a/docs/html/installation.html b/docs/html/installation.html index 34cad2efb3..2f27feedf7 100644 --- a/docs/html/installation.html +++ b/docs/html/installation.html @@ -231,11 +231,16 @@ HREF="troubleshooting.html" >
4.5.1. DBD::Sponge::db prepare failedBundle::Bugzilla makes me upgrade to Perl 5.6.1
4.5.2. DBD::Sponge::db prepare failed
4.5.3. cannot chdir(/var/spool/mqueue)
Post-Installation Checklist
The Bugzilla Guide
PrevChapter 5. Administering BugzillaNext

5.1. Post-Installation Checklist

After installation, follow the checklist below. - If you do not see a recommended - setting for a parameter, consider leaving it at the default while you - perform your initial tests on your Bugzilla setup.

  1. Log in to Bugzilla using the username and password - you defined for the administrator during installation.

  2. Bring up - editparams.cgi - in your web browser (link in footer.) This screen allows you - to change most of Bugzilla's operating parameters. Each comes - with an explanation, and you should go down the list, deciding - on what you want to do about each. -

  3. - maintainer: - The maintainer parameter is the email address of the person - responsible for maintaining this - Bugzilla installation. The address need not be that of a valid Bugzilla - account.

  4. urlbase: - This parameter defines the fully qualified domain name and web - server path to your Bugzilla installation.

    For example, if your Bugzilla query page is - http://www.foo.com/bugzilla/query.cgi, - set your "urlbase" - to http://www.foo.com/bugzilla/.

  5. usebuggroups: - This dictates whether or not to implement group-based security for - Bugzilla. If set, Bugzilla bugs can have an associated 'group', - defining which users are allowed to see and edit the - bug.

    Set "usebuggroups" to "on" - only - if you may wish to restrict access to particular bugs to certain - groups of users. I suggest leaving - this parameter off - while initially testing your Bugzilla.

  6. usebuggroupsentry: - Bugzilla Products can have a group associated with them, so that - certain users can only see bugs in certain products. When this parameter - is set to "on", this places all newly-created bugs in the - group for their product immediately.

  7. shadowdb: - You run into an interesting problem when Bugzilla reaches a - high level of continuous activity. MySQL supports only table-level - write locking. What this means is that if someone needs to make a - change to a bug, they will lock the entire table until the operation - is complete. Locking for write also blocks reads until the write is - complete. The - "shadowdb" - parameter was designed to get around this limitation. While only a - single user is allowed to write to a table at a time, reads can - continue unimpeded on a read-only shadow copy of the database. - Although your database size will double, a shadow database can cause - an enormous performance improvement when implemented on extremely - high-traffic Bugzilla databases.

    As a guide, mozilla.org began needing - "shadowdb" - when they reached around 40,000 Bugzilla users with several hundred - Bugzilla bug changes and comments per day.

    The value of the parameter defines the name of the - shadow bug database. - Set "shadowdb" to e.g. "bug_shadowdb" if you will be running a - *very* large installation of Bugzilla. -

    Enabling "shadowdb" can adversely affect the stability of - your installation of Bugzilla. You should regularly check that your - database is in sync. It is often advisable to force a shadow - database sync nightly via - "cron". -

    -

    If you use the "shadowdb" option, it is only natural that you - should turn the "queryagainstshadowdb" option on as well. Otherwise - you are replicating data into a shadow database for no reason!

  8. shutdownhtml: - - If you need to shut down Bugzilla to perform administration, enter - some descriptive HTML here and anyone who tries to use Bugzilla will - receive a page to that effect. Obviously, editparams.cgi will - still be accessible so you can remove the HTML and re-enable Bugzilla. - :-) -

  9. passwordmail: - - Every time a user creates an account, the text of - this parameter (with substitutions) is sent to the new user along with - their password message.

    Add any text you wish to the "passwordmail" parameter box. For - instance, many people choose to use this box to give a quick training - blurb about how to use Bugzilla at your site.

  10. useqacontact: - - This allows you to define an email address for each component, in - addition - to that of the default owner, who will be sent carbon copies of - incoming bugs.

  11. usestatuswhiteboard: - This defines whether you wish to have a free-form, overwritable field - associated with each bug. The advantage of the Status Whiteboard is - that it can be deleted or modified with ease, and provides an - easily-searchable field for indexing some bugs that have some trait - in common. -

  12. whinedays: - Set this to the number of days you want to let bugs go - in the NEW or REOPENED state before notifying people they have - untouched new bugs. If you do not plan to use this feature, simply do - not set up the whining cron job described in the installation - instructions, or set this value to "0" (never whine).

  13. commenton*: - All these - fields allow you to dictate what changes can pass without comment, - and which must have a comment from the person who changed them. - Often, administrators will allow users to add themselves to the CC - list, accept bugs, or change the Status Whiteboard without adding a - comment as to their reasons for the change, yet require that most - other changes come with an explanation.

    Set the "commenton" options according to your site policy. It - is a wise idea to require comments when users resolve, reassign, or - reopen bugs at the very least. -

    It is generally far better to require a developer comment - when resolving bugs than not. Few things are more annoying to bug - database users than having a developer mark a bug "fixed" without - any comment as to what the fix was (or even that it was truly - fixed!)

    -

  14. supportwatchers: - - Turning on this option allows users to ask to receive copies of - all a particular other user's bug email. This is, of - course, subject to the groupset restrictions on the bug; if the - "watcher" - would not normally be allowed to view a bug, the watcher cannot get - around the system by setting herself up to watch the bugs of someone - with bugs outside her privileges. They would still only receive email - updates for those bugs she could normally view.

PrevHomeNext
Administering BugzillaUpUpgrading to New Releases
\ No newline at end of file diff --git a/docs/html/quicksearch.html b/docs/html/quicksearch.html deleted file mode 100644 index 8312d85db2..0000000000 --- a/docs/html/quicksearch.html +++ /dev/null @@ -1,199 +0,0 @@ -The Quicksearch Utility
The Bugzilla Guide
PrevAppendix D. Useful Patches and Utilities for BugzillaNext

D.3. The Quicksearch Utility

Quicksearch is a single-text-box query tool which uses metacharacters - to indicate what is to be searched. For example, "foo@bar.com" would be - looked for in email address fields, because it contains an @ and so - is an email address. -

Quicksearch consists of two Javascript files, - "quicksearch.js" and "localconfig.js", - and two documentation files, "quicksearch.html" and - "quicksearchhack.html". More information on how to use Quicksearch - can be found there. You'll find the Quicksearch box on Bugzilla's - front page.

To take full advantage of the query power, the Bugzilla maintainer - must edit "localconfig.js" and change the parameters according to the local - installation.

Currently, keywords must be hard-coded in localconfig.js. If they - are not, keywords are not automatically recognized. This means, if - localconfig.js is left unconfigured, that searching for a bug with the - "foo" keyword will only find bugs with "foo" in the summary, status - whiteboard, product or component name, but not those with the keyword - "foo".

Workarounds for Bugzilla users: -

search for '!foo' (this will find only bugs with the keyword - "foo"
search 'foo,!foo' (equivalent to 'foo OR keyword:foo')

-

When this tool is ported from client-side JavaScript to server-side - Perl, the requirement for hard-coding keywords can be fixed. - This - bug - - has details.

PrevHomeNext
Command-line Bugzilla QueriesUpGlossary
\ No newline at end of file diff --git a/docs/html/rhbugzilla.html b/docs/html/rhbugzilla.html index b52a378933..fb1eb3c9a9 100644 --- a/docs/html/rhbugzilla.html +++ b/docs/html/rhbugzilla.html @@ -75,9 +75,8 @@ CLASS="section" >D.1. Red Hat Bugzilla

Red Hat Bugzilla is probably the most popular Bugzilla, after - Bugzilla itself, on the planet. One of the major benefits of Red Hat - Bugzilla is the ability +>Red Hat Bugzilla is a fork of Bugzilla 2.8. + One of its major benefits is the ability to work with Oracle, MySQL, and PostGreSQL databases serving as the back-end, instead of just MySQL. Dave Lawrence of Red Hat is active in the Bugzilla community, and we hope to see a reunification diff --git a/docs/html/scm.html b/docs/html/scm.html deleted file mode 100644 index f812c8596b..0000000000 --- a/docs/html/scm.html +++ /dev/null @@ -1,173 +0,0 @@ -Perforce SCM

The Bugzilla Guide
PrevChapter 6. Integrating Bugzilla with Third-Party ToolsNext

6.3. Perforce SCM

You can find the project page for Bugzilla and Teamtrack Perforce - integration (p4dti) at: - http://www.ravenbrook.com/project/p4dti - - . - "p4dti" - - is now an officially supported product from Perforce, and you can find - the "Perforce Public Depot" p4dti page at - http://public.perforce.com/public/perforce/p4dti/index.html - - .

Integration of Perforce with Bugzilla, once patches are applied, is - seamless. Perforce replication information will appear below the comments - of each bug. Be certain you have a matching set of patches for the - Bugzilla version you are installing. p4dti is designed to support - multiple defect trackers, and maintains its own documentation for it. - Please consult the pages linked above for further information.

PrevHomeNext
CVSUpTinderbox/Tinderbox2
\ No newline at end of file diff --git a/docs/html/setperl.html b/docs/html/setperl.html deleted file mode 100644 index 4582214b5f..0000000000 --- a/docs/html/setperl.html +++ /dev/null @@ -1,326 +0,0 @@ -The setperl.csh Utility
The Bugzilla Guide
PrevAppendix D. Useful Patches and Utilities for BugzillaNext

D.2. The setperl.csh Utility

You can use the "setperl.csh" utility to quickly and easily change - the path to perl on all your Bugzilla files. This is a C-shell script; if - you do not have "csh" or "tcsh" in the search path on your system, it - will not work!

PrevHomeNext
Apache - mod_rewrite - - magicUpCommand-line Bugzilla Queries
\ No newline at end of file diff --git a/docs/html/tinderbox.html b/docs/html/tinderbox.html deleted file mode 100644 index e1b8a687a6..0000000000 --- a/docs/html/tinderbox.html +++ /dev/null @@ -1,144 +0,0 @@ -Tinderbox/Tinderbox2
The Bugzilla Guide
PrevChapter 6. Integrating Bugzilla with Third-Party ToolsNext
PrevHomeNext
Perforce SCMUpBugzilla Variants and Competitors
\ No newline at end of file diff --git a/docs/html/translations.html b/docs/html/translations.html deleted file mode 100644 index dac9b1c7a8..0000000000 --- a/docs/html/translations.html +++ /dev/null @@ -1,156 +0,0 @@ -Translations
The Bugzilla Guide
PrevChapter 1. About This GuideNext
PrevHomeNext
CreditsUpDocument Conventions
\ No newline at end of file diff --git a/docs/html/troubleshooting.html b/docs/html/troubleshooting.html index 10d8b07693..7a4a32d7de 100644 --- a/docs/html/troubleshooting.html +++ b/docs/html/troubleshooting.html @@ -83,7 +83,30 @@ CLASS="section" >

4.5.1. DBD::Sponge::db prepare failed

4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1

Try executing perl -MCPAN -e 'install CPAN' + and then continuing. +

Certain older versions of the CPAN toolset were somewhat naive about how + to upgrade Perl modules. When a couple of modules got rolled into the core + Perl distribution for 5.6.1, CPAN thought that the best way to get those + modules up to date was to haul down the Perl distribution itself and + build it. Needless to say, this has caused headaches for just about + everybody. Upgrading to a newer version of CPAN with the + commandline above should fix things. +

4.5.2. DBD::Sponge::db prepare failed

The following error message may appear due to a bug in DBD::mysql (over which the Bugzilla team have no control): @@ -167,7 +190,7 @@ CLASS="section" >

4.5.2. cannot chdir(/var/spool/mqueue)

4.5.3. cannot chdir(/var/spool/mqueue)

If you are installing Bugzilla on SuSE Linux, or some other distributions with diff --git a/docs/html/usingbz-conc.html b/docs/html/usingbz-conc.html deleted file mode 100644 index 71fbc30452..0000000000 --- a/docs/html/usingbz-conc.html +++ /dev/null @@ -1,152 +0,0 @@ -Using Bugzilla-Conclusion

The Bugzilla Guide
PrevChapter 2. Using BugzillaNext
PrevHomeNext
Where can I find my user preferences?UpInstallation
\ No newline at end of file diff --git a/docs/html/variant-scarab.html b/docs/html/variant-scarab.html index a263fe4e02..14cd54afa4 100644 --- a/docs/html/variant-scarab.html +++ b/docs/html/variant-scarab.html @@ -76,7 +76,7 @@ CLASS="section" NAME="variant-scarab">D.4. Scarab

Scarab is a new open source bug-tracking system built using Java - Serlet technology. It is currently at version 1.0 beta 7.

URL: 2.2. Why Should We Use Bugzilla?CVS, + Bonsai, or + Perforce SCM, Bugzilla provides a powerful, easy-to-use solution to configuration management and replication problems.

4.3. Win32 Installation Notes

This section covers installation on Microsoft Windows 95, 98, ME, - NT, and 2000. Bugzilla works fine on Win32 platforms, but please remember - that the Bugzilla team and the author of the Guide neither endorse nor - support installation on Microsoft Windows. Bugzilla installs and runs - best - - and - easiest - - on UNIX-like operating systems, and that is the way it will stay for the - foreseeable future. The Bugzilla team is considering supporting Win32 for - the 2.16 release and later.

The easiest way to install Bugzilla on Intel-archiecture machines +>This section covers installation on Microsoft Windows. + Bugzilla has been made to work on Win32 platforms, but the Bugzilla team + wish to emphasise that The easiest way to install Bugzilla on + Intel-archiecture machines is to install some variant of GNU/Linux, then follow the UNIX installation instructions in this Guide. If you have any influence in the platform choice for running this system, please choose GNU/Linux instead of Microsoft Windows.

After that warning, here's the situation for 2.16 + and Windows. It doesn't work at all out of the box. + You are almost certainly better off getting + the 2.17 version from CVS (after consultation with the Bugzilla Team to + make sure you are pulling on a stable day) because we'll be doing a load + of work to make the Win32 experience more pleasant than it is now. +

If you still want to try this, to have any hope of getting it to work, + you'll need to apply the + mail patch from + bug 124174. + After that, you'll need to read the (outdated) installation + instructions below, some (probably a lot better) more + recent ones kindly provided by Toms Baugis and Jean-Sebastien + Guay, and also check the + Bugzilla 2.16 Win32 update page + . If we get time, + we'll write some better installation instructions for 2.16 and put + them up there. But no promises. +

Example 4-1. Installing ActivePerl ppd Modules on Microsoft Windows

Example 4-2. Installing OpenInteract ppd Modules manually on Microsoft Windows

From Andrew Pearson:

You can make Bugzilla work with Personal Web Server for @@ -1616,7 +1664,7 @@ VALIGN="TOP"

Example 4-3. Removing encrypt() for Windows NT Bugzilla version 2.12 or earlier