зеркало из https://github.com/mozilla/gecko-dev.git
Recompile docs so (hopefully) I can get some feedback on the installation chapter changes.
This commit is contained in:
jake%bugzilla.org
Родитель
518c726992
Коммит
ec98f98bf8
Разница между файлами не показана из-за своего большого размера
Загрузить разницу
|
|
@ -180,22 +180,22 @@ HREF="cust-templates.html"
|
|||
><DL
|
||||
><DT
|
||||
>5.7.1. <A
|
||||
HREF="cust-templates.html#AEN1425"
|
||||
HREF="cust-templates.html#AEN1524"
|
||||
>What to Edit</A
|
||||
></DT
|
||||
><DT
|
||||
>5.7.2. <A
|
||||
HREF="cust-templates.html#AEN1444"
|
||||
HREF="cust-templates.html#AEN1543"
|
||||
>How To Edit Templates</A
|
||||
></DT
|
||||
><DT
|
||||
>5.7.3. <A
|
||||
HREF="cust-templates.html#AEN1454"
|
||||
HREF="cust-templates.html#AEN1553"
|
||||
>Template Formats</A
|
||||
></DT
|
||||
><DT
|
||||
>5.7.4. <A
|
||||
HREF="cust-templates.html#AEN1467"
|
||||
HREF="cust-templates.html#AEN1566"
|
||||
>Particular Templates</A
|
||||
></DT
|
||||
></DL
|
||||
|
|
|
|||
|
|
@ -81,7 +81,7 @@ NAME="conventions"
|
|||
><DIV
|
||||
CLASS="informaltable"
|
||||
><A
|
||||
NAME="AEN110"
|
||||
NAME="AEN111"
|
||||
></A
|
||||
><P
|
||||
></P
|
||||
|
|
|
|||
|
|
@ -96,9 +96,9 @@ VALIGN="TOP"
|
|||
><P
|
||||
> 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
|
||||
License, Version 1.1 or any later version published by the
|
||||
Free Software Foundation; with no Invariant Sections, no
|
||||
Front-Cover Texts, and with no Back-Cover Texts. A copy of
|
||||
Front-Cover Texts, and with no Back-Cover Texts. A copy of
|
||||
the license is included in <A
|
||||
HREF="gfdl.html"
|
||||
>Appendix E</A
|
||||
|
|
|
|||
|
|
@ -184,13 +184,13 @@ HREF="news://news.mozilla.org/netscape/public/mozilla/webtools"
|
|||
TARGET="_top"
|
||||
>news://news.mozilla.org/netscape/public/mozilla/webtools</A
|
||||
>
|
||||
newsgroup. Without your discussions, insight, suggestions, and patches,
|
||||
newsgroup. Without your discussions, insight, suggestions, and patches,
|
||||
this could never have happened.
|
||||
</P
|
||||
><P
|
||||
> Thanks also go to the following people for significant contributions
|
||||
to this documentation (in alphabetical order):
|
||||
Andrew Pearson, Ben FrantzDale, Eric Hanson, Gervase Markham, Joe Robins, Kevin Brannen, Ron Teitelbaum, Spencer Smith, Zach Liption
|
||||
Andrew Pearson, Ben FrantzDale, Eric Hanson, Gervase Markham, Joe Robins, Kevin Brannen, Martin Wulffeld, Ron Teitelbaum, Spencer Smith, Zach Liption
|
||||
.
|
||||
</P
|
||||
></DIV
|
||||
|
|
|
|||
|
|
@ -99,7 +99,7 @@ CLASS="section"
|
|||
><H2
|
||||
CLASS="section"
|
||||
><A
|
||||
NAME="AEN1425"
|
||||
NAME="AEN1524"
|
||||
></A
|
||||
>5.7.1. What to Edit</H2
|
||||
><P
|
||||
|
|
@ -214,7 +214,7 @@ CLASS="section"
|
|||
><H2
|
||||
CLASS="section"
|
||||
><A
|
||||
NAME="AEN1444"
|
||||
NAME="AEN1543"
|
||||
></A
|
||||
>5.7.2. How To Edit Templates</H2
|
||||
><P
|
||||
|
|
@ -296,7 +296,7 @@ CLASS="section"
|
|||
><H2
|
||||
CLASS="section"
|
||||
><A
|
||||
NAME="AEN1454"
|
||||
NAME="AEN1553"
|
||||
></A
|
||||
>5.7.3. Template Formats</H2
|
||||
><P
|
||||
|
|
@ -358,7 +358,7 @@ CLASS="section"
|
|||
><H2
|
||||
CLASS="section"
|
||||
><A
|
||||
NAME="AEN1467"
|
||||
NAME="AEN1566"
|
||||
></A
|
||||
>5.7.4. Particular Templates</H2
|
||||
><P
|
||||
|
|
|
|||
|
|
@ -108,7 +108,7 @@ NAME="dbdoc"
|
|||
><P
|
||||
>But Certain Death speaks up -- a tiny voice, from the dark corners
|
||||
of the conference room. "I have a concern," the voice hisses from the
|
||||
darkness, "about the use of the word 'verified'.</P
|
||||
darkness, "about the use of the word 'verified'."</P
|
||||
><P
|
||||
>The room, previously filled with happy chatter, lapses into
|
||||
reverential silence as Certain Death (better known as the Vice President
|
||||
|
|
@ -135,7 +135,7 @@ CLASS="section"
|
|||
><H2
|
||||
CLASS="section"
|
||||
><A
|
||||
NAME="AEN2091"
|
||||
NAME="AEN2190"
|
||||
></A
|
||||
>B.2.1. Bugzilla Database Basics</H2
|
||||
><P
|
||||
|
|
@ -154,14 +154,12 @@ CLASS="QUOTE"
|
|||
>"tinyint"</SPAN
|
||||
>
|
||||
|
||||
entry in MySQL. I recommend you refer to the MySQL documentation,
|
||||
available at
|
||||
entry in MySQL. I recommend you refer to the
|
||||
<A
|
||||
HREF="http://www.mysql.com/doc.html"
|
||||
HREF="http://www.mysql.com/documentation/"
|
||||
TARGET="_top"
|
||||
>MySQL.com</A
|
||||
>MySQL documentation</A
|
||||
>
|
||||
|
||||
. Below are the basics you need to know about the Bugzilla database.
|
||||
Check the chart above for more details.</P
|
||||
><P
|
||||
|
|
@ -205,7 +203,7 @@ HREF="http://www.mysql.com/php/manual.php3?section=Privilege_system"
|
|||
TARGET="_top"
|
||||
>MySQL
|
||||
searchable documentation</A
|
||||
>.
|
||||
>.
|
||||
</P
|
||||
></LI
|
||||
><LI
|
||||
|
|
@ -251,7 +249,7 @@ CLASS="section"
|
|||
><H3
|
||||
CLASS="section"
|
||||
><A
|
||||
NAME="AEN2118"
|
||||
NAME="AEN2217"
|
||||
></A
|
||||
>B.2.1.1. Bugzilla Database Tables</H3
|
||||
><P
|
||||
|
|
@ -322,14 +320,14 @@ CLASS="programlisting"
|
|||
><P
|
||||
CLASS="literallayout"
|
||||
><br>
|
||||
Here's an overview of what each table does. Most columns in each table have<br>
|
||||
Here's an overview of what each table does. Most columns in each table have<br>
|
||||
descriptive names that make it fairly trivial to figure out their jobs.<br>
|
||||
<br>
|
||||
attachments: This table stores all attachments to bugs. It tends to be your<br>
|
||||
attachments: This table stores all attachments to bugs. It tends to be your<br>
|
||||
largest table, yet also generally has the fewest entries because file<br>
|
||||
attachments are so (relatively) large.<br>
|
||||
<br>
|
||||
bugs: This is the core of your system. The bugs table stores most of the<br>
|
||||
bugs: This is the core of your system. The bugs table stores most of the<br>
|
||||
current information about a bug, with the exception of the info stored in the<br>
|
||||
other tables.<br>
|
||||
<br>
|
||||
|
|
@ -337,26 +335,26 @@ bugs_activity: This stores information regarding
|
|||
when -- a history file.<br>
|
||||
<br>
|
||||
cc: This tiny table simply stores all the CC information for any bug which has<br>
|
||||
any entries in the CC field of the bug. Note that, like most other tables in<br>
|
||||
any entries in the CC field of the bug. Note that, like most other tables in<br>
|
||||
Bugzilla, it does not refer to users by their user names, but by their unique<br>
|
||||
userid, stored as a primary key in the profiles table.<br>
|
||||
<br>
|
||||
components: This stores the programs and components (or products and<br>
|
||||
components, in newer Bugzilla parlance) for Bugzilla. Curiously, the "program"<br>
|
||||
components, in newer Bugzilla parlance) for Bugzilla. Curiously, the "program"<br>
|
||||
(product) field is the full name of the product, rather than some other unique<br>
|
||||
identifier, like bug_id and user_id are elsewhere in the database.<br>
|
||||
<br>
|
||||
dependencies: Stores data about those cool dependency trees.<br>
|
||||
<br>
|
||||
fielddefs: A nifty table that defines other tables. For instance, when you<br>
|
||||
fielddefs: A nifty table that defines other tables. For instance, when you<br>
|
||||
submit a form that changes the value of "AssignedTo" this table allows<br>
|
||||
translation to the actual field name "assigned_to" for entry into MySQL.<br>
|
||||
<br>
|
||||
groups: defines bitmasks for groups. A bitmask is a number that can uniquely<br>
|
||||
identify group memberships. For instance, say the group that is allowed to<br>
|
||||
groups: defines bitmasks for groups. A bitmask is a number that can uniquely<br>
|
||||
identify group memberships. For instance, say the group that is allowed to<br>
|
||||
tweak parameters is assigned a value of "1", the group that is allowed to edit<br>
|
||||
users is assigned a "2", and the group that is allowed to create new groups is<br>
|
||||
assigned the bitmask of "4". By uniquely combining the group bitmasks (much<br>
|
||||
assigned the bitmask of "4". By uniquely combining the group bitmasks (much<br>
|
||||
like the chmod command in UNIX,) you can identify a user is allowed to tweak<br>
|
||||
parameters and create groups, but not edit users, by giving him a bitmask of<br>
|
||||
"5", or a user allowed to edit users and create groups, but not tweak<br>
|
||||
|
|
@ -371,15 +369,15 @@ keywords: Unlike what you'd think, this table 
|
|||
associated with which bug id's.<br>
|
||||
<br>
|
||||
logincookies: This stores every login cookie ever assigned to you for every<br>
|
||||
machine you've ever logged into Bugzilla from. Curiously, it never does any<br>
|
||||
housecleaning -- I see cookies in this file I've not used for months. However,<br>
|
||||
machine you've ever logged into Bugzilla from. Curiously, it never does any<br>
|
||||
housecleaning -- I see cookies in this file I've not used for months. However,<br>
|
||||
since Bugzilla never expires your cookie (for convenience' sake), it makes<br>
|
||||
sense.<br>
|
||||
<br>
|
||||
longdescs: The meat of bugzilla -- here is where all user comments are stored!<br>
|
||||
You've only got 2^24 bytes per comment (it's a mediumtext field), so speak<br>
|
||||
sparingly -- that's only the amount of space the Old Testament from the Bible<br>
|
||||
would take (uncompressed, 16 megabytes). Each comment is keyed to the<br>
|
||||
would take (uncompressed, 16 megabytes). Each comment is keyed to the<br>
|
||||
bug_id to which it's attached, so the order is necessarily chronological, for<br>
|
||||
comments are played back in the order in which they are received.<br>
|
||||
<br>
|
||||
|
|
@ -387,12 +385,12 @@ milestones: Interesting that milestones are assoc
|
|||
in this table, but Bugzilla does not yet support differing milestones by<br>
|
||||
product through the standard configuration interfaces.<br>
|
||||
<br>
|
||||
namedqueries: This is where everybody stores their "custom queries". Very<br>
|
||||
namedqueries: This is where everybody stores their "custom queries". Very<br>
|
||||
cool feature; it beats the tar out of having to bookmark each cool query you<br>
|
||||
construct.<br>
|
||||
<br>
|
||||
products: What products you have, whether new bug entries are allowed for the<br>
|
||||
product, what milestone you're working toward on that product, votes, etc. It<br>
|
||||
product, what milestone you're working toward on that product, votes, etc. It<br>
|
||||
will be nice when the components table supports these same features, so you<br>
|
||||
could close a particular component for bug entry without having to close an<br>
|
||||
entire product...<br>
|
||||
|
|
@ -427,7 +425,7 @@ mysql> show columns from table;<br>
|
|||
mysql> select * from table;<br>
|
||||
<br>
|
||||
-- note: this is a very bad idea to do on, for instance, the "bugs" table if<br>
|
||||
you have 50,000 bugs. You'll be sitting there a while until you ctrl-c or<br>
|
||||
you have 50,000 bugs. You'll be sitting there a while until you ctrl-c or<br>
|
||||
50,000 bugs play across your screen.<br>
|
||||
<br>
|
||||
You can limit the display from above a little with the command, where<br>
|
||||
|
|
@ -440,7 +438,7 @@ mysql> select * from table where (column
|
|||
mysql> select * from table where (column != "some info");<br>
|
||||
<br>
|
||||
Let's take our example from the introduction, and assume you need to change<br>
|
||||
the word "verified" to "approved" in the resolution field. We know from the<br>
|
||||
the word "verified" to "approved" in the resolution field. We know from the<br>
|
||||
above information that the resolution is likely to be stored in the "bugs"<br>
|
||||
table. Note we'll need to change a little perl code as well as this database<br>
|
||||
change, but I won't plunge into that in this document. Let's verify the<br>
|
||||
|
|
@ -451,10 +449,10 @@ mysql> show columns from bugs<br>
|
|||
(exceedingly long output truncated here)<br>
|
||||
| bug_status| enum('UNCONFIRMED','NEW','ASSIGNED','REOPENED','RESOLVED','VERIFIED','CLOSED')||MUL | UNCONFIRMED||<br>
|
||||
<br>
|
||||
Sorry about that long line. We see from this that the "bug status" column is<br>
|
||||
Sorry about that long line. We see from this that the "bug status" column is<br>
|
||||
an "enum field", which is a MySQL peculiarity where a string type field can<br>
|
||||
only have certain types of entries. While I think this is very cool, it's not<br>
|
||||
standard SQL. Anyway, we need to add the possible enum field entry<br>
|
||||
only have certain types of entries. While I think this is very cool, it's not<br>
|
||||
standard SQL. Anyway, we need to add the possible enum field entry<br>
|
||||
'APPROVED' by altering the "bugs" table.<br>
|
||||
<br>
|
||||
mysql> ALTER table bugs CHANGE bug_status bug_status<br>
|
||||
|
|
@ -470,15 +468,15 @@ mysql> show columns from bugs;<br>
|
|||
<br>
|
||||
you'll see that the bug_status field has an extra "APPROVED" enum that's<br>
|
||||
available! Cool thing, too, is that this is reflected on your query page as<br>
|
||||
well -- you can query by the new status. But how's it fit into the existing<br>
|
||||
well -- you can query by the new status. But how's it fit into the existing<br>
|
||||
scheme of things?<br>
|
||||
Looks like you need to go back and look for instances of the word "verified"<br>
|
||||
in the perl code for Bugzilla -- wherever you find "verified", change it to<br>
|
||||
"approved" and you're in business (make sure that's a case-insensitive search).<br>
|
||||
Although you can query by the enum field, you can't give something a status<br>
|
||||
of "APPROVED" until you make the perl changes. Note that this change I<br>
|
||||
of "APPROVED" until you make the perl changes. Note that this change I<br>
|
||||
mentioned can also be done by editing checksetup.pl, which automates a lot of<br>
|
||||
this. But you need to know this stuff anyway, right?<br>
|
||||
this. But you need to know this stuff anyway, right?<br>
|
||||
</P
|
||||
></DIV
|
||||
></DIV
|
||||
|
|
|
|||
|
|
@ -87,15 +87,15 @@ NAME="disclaimer"
|
|||
</P
|
||||
><P
|
||||
> All copyrights are held by their respective owners, unless
|
||||
specifically noted otherwise. Use of a term in this document
|
||||
specifically noted otherwise. Use of a term in this document
|
||||
should not be regarded as affecting the validity of any
|
||||
trademark or service mark.
|
||||
</P
|
||||
><P
|
||||
> Naming of particular products or brands should not be seen as
|
||||
endorsements, with the exception of the term "GNU/Linux". We
|
||||
endorsements, with the exception of the term "GNU/Linux". We
|
||||
wholeheartedly endorse the use of GNU/Linux in every situation
|
||||
where it is appropriate. It is an extremely versatile, stable,
|
||||
where it is appropriate. It is an extremely versatile, stable,
|
||||
and robust operating system that offers an ideal operating
|
||||
environment for Bugzilla.
|
||||
</P
|
||||
|
|
@ -110,10 +110,10 @@ NAME="disclaimer"
|
|||
documented or fixed in the code, security holes surely exist.
|
||||
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. The Bugzilla development
|
||||
other network services with Bugzilla. The Bugzilla development
|
||||
team members, Netscape Communications, America Online Inc., and
|
||||
any affiliated developers or sponsors assume no liability for
|
||||
your use of this product. You have the source code to this
|
||||
your use of this product. You have the source code to this
|
||||
product, and are responsible for auditing it yourself to ensure
|
||||
your security needs are met.
|
||||
</P
|
||||
|
|
|
|||
|
|
@ -81,7 +81,7 @@ CLASS="section"
|
|||
><H2
|
||||
CLASS="section"
|
||||
><A
|
||||
NAME="AEN687"
|
||||
NAME="AEN786"
|
||||
></A
|
||||
>4.2.1. Dependency Charts</H2
|
||||
><P
|
||||
|
|
@ -145,7 +145,7 @@ CLASS="section"
|
|||
><H2
|
||||
CLASS="section"
|
||||
><A
|
||||
NAME="AEN702"
|
||||
NAME="AEN801"
|
||||
></A
|
||||
>4.2.2. Bug Graphs</H2
|
||||
><P
|
||||
|
|
@ -204,7 +204,7 @@ CLASS="section"
|
|||
><H2
|
||||
CLASS="section"
|
||||
><A
|
||||
NAME="AEN715"
|
||||
NAME="AEN814"
|
||||
></A
|
||||
>4.2.3. The Whining Cron</H2
|
||||
><P
|
||||
|
|
@ -386,13 +386,13 @@ HREF="http://www.openldap.org/"
|
|||
TARGET="_top"
|
||||
> OpenLDAP</A
|
||||
> with Bugzilla, using any of a number of administration
|
||||
tools. You should apply the patch attached this bug:
|
||||
tools. You should apply the patch attached to
|
||||
<A
|
||||
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=158630"
|
||||
TARGET="_top"
|
||||
> http://bugzilla.mozilla.org/show_bug.cgi?id=158630</A
|
||||
>, then set
|
||||
the following object classes for your users:
|
||||
>bug 158630</A
|
||||
>
|
||||
, then set the following object classes for your users:
|
||||
|
||||
<P
|
||||
></P
|
||||
|
|
@ -450,7 +450,7 @@ NAME="content-type"
|
|||
<A
|
||||
HREF="http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3"
|
||||
TARGET="_top"
|
||||
> http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3</A
|
||||
>http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3</A
|
||||
>.
|
||||
Executing the following code snippet from a UNIX command shell will
|
||||
rectify the problem if your Bugzilla installation is intended for an
|
||||
|
|
@ -523,13 +523,13 @@ VALIGN="TOP"
|
|||
><P
|
||||
>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. See
|
||||
marked up in this way to load twice. See
|
||||
<A
|
||||
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=126266"
|
||||
TARGET="_top"
|
||||
>bug
|
||||
126266</A
|
||||
> for more information including progress toward making
|
||||
>bug 126266</A
|
||||
>
|
||||
for more information including progress toward making
|
||||
bugzilla charset aware by default.
|
||||
</P
|
||||
></TD
|
||||
|
|
@ -610,7 +610,7 @@ CLASS="filename"
|
|||
HREF="http://www.snert.com/Software/mod_throttle/"
|
||||
TARGET="_top"
|
||||
>http://www.snert.com/Software/mod_throttle/</A
|
||||
>
|
||||
>.
|
||||
Follow the instructions to install into your Apache install.
|
||||
<EM
|
||||
>This module only functions with the Apache web
|
||||
|
|
|
|||
|
|
@ -497,7 +497,7 @@ HREF="faq.html#faq-use-changeaddress"
|
|||
><DT
|
||||
>A.7.2. <A
|
||||
HREF="faq.html#faq-use-query"
|
||||
> The query page is very confusing. Isn't there a simpler way to query?
|
||||
> The query page is very confusing. Isn't there a simpler way to query?
|
||||
</A
|
||||
></DT
|
||||
><DT
|
||||
|
|
@ -511,7 +511,7 @@ HREF="faq.html#faq-use-accept"
|
|||
>A.7.4. <A
|
||||
HREF="faq.html#faq-use-attachment"
|
||||
> I can't upload anything into the database via the "Create Attachment"
|
||||
link. What am I doing wrong?
|
||||
link. What am I doing wrong?
|
||||
</A
|
||||
></DT
|
||||
><DT
|
||||
|
|
@ -587,8 +587,8 @@ CLASS="answer"
|
|||
information at <A
|
||||
HREF="http://www.bugzilla.org/"
|
||||
TARGET="_top"
|
||||
> http://www.bugzilla.org/</A
|
||||
>
|
||||
>http://www.bugzilla.org/</A
|
||||
>.
|
||||
</P
|
||||
></DIV
|
||||
></DIV
|
||||
|
|
@ -616,8 +616,8 @@ CLASS="answer"
|
|||
See details at <A
|
||||
HREF="http://www.mozilla.org/MPL/"
|
||||
TARGET="_top"
|
||||
> http://www.mozilla.org/MPL/</A
|
||||
>
|
||||
>http://www.mozilla.org/MPL/</A
|
||||
>.
|
||||
</P
|
||||
></DIV
|
||||
></DIV
|
||||
|
|
@ -653,7 +653,7 @@ TARGET="_top"
|
|||
> <A
|
||||
HREF="http://www.collab.net/"
|
||||
TARGET="_top"
|
||||
>www.collab.net</A
|
||||
>http://www.collab.net/</A
|
||||
> offers
|
||||
Bugzilla as part of their standard offering to large projects.
|
||||
They do have some minimum fees that are pretty hefty, and generally
|
||||
|
|
@ -691,7 +691,7 @@ CLASS="answer"
|
|||
There are <EM
|
||||
>dozens</EM
|
||||
> of major companies with public
|
||||
Bugzilla sites to track bugs in their products. A few include:
|
||||
Bugzilla sites to track bugs in their products. A few include:
|
||||
<P
|
||||
></P
|
||||
><TABLE
|
||||
|
|
@ -799,7 +799,7 @@ HREF="http://www.bugzilla.org/who_we_are.html"
|
|||
TARGET="_top"
|
||||
>core team</A
|
||||
>,
|
||||
led by Dave Miller (justdave@netscape.com).
|
||||
led by Dave Miller (justdave@netscape.com).
|
||||
</P
|
||||
></DIV
|
||||
></DIV
|
||||
|
|
@ -863,8 +863,8 @@ CLASS="answer"
|
|||
> </B
|
||||
>
|
||||
It may be that the support has not been built yet, or that you
|
||||
have not yet found it. Bugzilla is making tremendous strides in
|
||||
usability, customizability, scalability, and user interface. It
|
||||
have not yet found it. Bugzilla is making tremendous strides in
|
||||
usability, customizability, scalability, and user interface. It
|
||||
is widely considered the most complete and popular open-source
|
||||
bug-tracking software in existence.
|
||||
</P
|
||||
|
|
@ -907,16 +907,16 @@ CLASS="answer"
|
|||
</P
|
||||
><P
|
||||
> There is currently work in progress to make Bugzilla work on
|
||||
PostgreSQL and Sybase in the default distribution. You can track
|
||||
the progress of these initiatives in bugs <A
|
||||
PostgreSQL and Sybase in the default distribution. You can track
|
||||
the progress of these initiatives in <A
|
||||
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=98304"
|
||||
TARGET="_top"
|
||||
>98304</A
|
||||
>bug 98304</A
|
||||
>
|
||||
and <A
|
||||
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=173130"
|
||||
TARGET="_top"
|
||||
>173130</A
|
||||
>bug 173130</A
|
||||
>
|
||||
respectively.
|
||||
</P
|
||||
|
|
@ -956,11 +956,11 @@ CLASS="filename"
|
|||
> because when
|
||||
Terry first started writing the code for mozilla.org he needed a
|
||||
version of Perl and other tools that were completely under his
|
||||
control. This location was abandoned for the 2.18 release in favor
|
||||
control. This location was abandoned for the 2.18 release in favor
|
||||
of the more sensible <TT
|
||||
CLASS="filename"
|
||||
>/usr/bin/perl</TT
|
||||
>. If you
|
||||
>. If you
|
||||
installed an older verion of Bugzilla and created the symlink we
|
||||
suggested, you can remove it now (provided that you don't have
|
||||
anything else, such as Bonsai, using it and you don't intend to
|
||||
|
|
@ -993,7 +993,7 @@ CLASS="answer"
|
|||
> </B
|
||||
>
|
||||
Yes, the following bit of perl magic will change all the shebang
|
||||
lines. Be sure to change <TT
|
||||
lines. Be sure to change <TT
|
||||
CLASS="filename"
|
||||
>/usr/local/bin/perl</TT
|
||||
>
|
||||
|
|
@ -1100,7 +1100,7 @@ CLASS="answer"
|
|||
><B
|
||||
> </B
|
||||
>
|
||||
It is web and e-mail based. You can edit bugs by sending specially
|
||||
It is web and e-mail based. You can edit bugs by sending specially
|
||||
formatted email to a properly configured Bugzilla, or control via the web.
|
||||
</P
|
||||
></DIV
|
||||
|
|
@ -1203,7 +1203,7 @@ CLASS="answer"
|
|||
> </B
|
||||
>
|
||||
Yes - any sort of attachment is allowed, although administrators can
|
||||
configure a maximum size.
|
||||
configure a maximum size.
|
||||
Bugzilla gives the user the option of either using the MIME-type
|
||||
supplied by the browser, choosing from a pre-defined list or
|
||||
manually typing any arbitrary MIME-type.
|
||||
|
|
@ -1232,17 +1232,17 @@ CLASS="answer"
|
|||
><B
|
||||
> </B
|
||||
>
|
||||
Yes. However, modifying some fields, notably those related to bug
|
||||
Yes. However, modifying some fields, notably those related to bug
|
||||
progression states, also require adjusting the program logic to
|
||||
compensate for the change.
|
||||
</P
|
||||
><P
|
||||
> There is no GUI for adding fields to Bugzilla at this
|
||||
time. You can follow development of this feature at
|
||||
time. You can follow development of this feature in
|
||||
<A
|
||||
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=91037"
|
||||
TARGET="_top"
|
||||
>http://bugzilla.mozilla.org/show_bug.cgi?id=91037</A
|
||||
>bug 91037</A
|
||||
>
|
||||
</P
|
||||
></DIV
|
||||
|
|
@ -1268,12 +1268,12 @@ CLASS="answer"
|
|||
><B
|
||||
> </B
|
||||
>
|
||||
Yes. Look at <A
|
||||
Yes. Look at <A
|
||||
HREF="http://bugzilla.mozilla.org/report.cgi"
|
||||
TARGET="_top"
|
||||
> http://bugzilla.mozilla.org/report.cgi</A
|
||||
> for samples of what
|
||||
Bugzilla can do in reporting and graphing.
|
||||
>http://bugzilla.mozilla.org/report.cgi</A
|
||||
>
|
||||
for samples of what Bugzilla can do in reporting and graphing.
|
||||
</P
|
||||
><P
|
||||
> If you can not get the reports you want from the included reporting
|
||||
|
|
@ -1306,7 +1306,7 @@ CLASS="answer"
|
|||
><B
|
||||
> </B
|
||||
>
|
||||
Email notification is user-configurable. By default, the bug id and
|
||||
Email notification is user-configurable. By default, the bug id and
|
||||
Summary of the bug report accompany each email notification, along with
|
||||
a list of the changes made.
|
||||
</P
|
||||
|
|
@ -1384,7 +1384,7 @@ VALIGN="TOP"
|
|||
> If you decide to use the bugzilla_email integration features
|
||||
to allow Bugzilla to record responses to mail with the associated bug,
|
||||
you may need to caution your users to set their mailer to "respond
|
||||
to messages in the format in which they were sent". For security reasons
|
||||
to messages in the format in which they were sent". For security reasons
|
||||
Bugzilla ignores HTML tags in comments, and if a user sends HTML-based
|
||||
email into Bugzilla the resulting comment looks downright awful.
|
||||
</P
|
||||
|
|
@ -1421,7 +1421,7 @@ CLASS="answer"
|
|||
>
|
||||
Bugzilla can output buglists as HTML (the default), CSV or RDF.
|
||||
The link for CSV can be found at the bottom of the buglist in HTML
|
||||
format. This CSV format can easily be imported into MS Excel or
|
||||
format. This CSV format can easily be imported into MS Excel or
|
||||
other spread-sheet applications.
|
||||
</P
|
||||
><P
|
||||
|
|
@ -1429,7 +1429,7 @@ CLASS="answer"
|
|||
<TT
|
||||
CLASS="computeroutput"
|
||||
>&ctype=rdf</TT
|
||||
> to the URL. RDF
|
||||
> to the URL. RDF
|
||||
is meant to be machine readable and thus it is assumed that the
|
||||
URL would be generated progmatically so there is no user visible
|
||||
link to this format.
|
||||
|
|
@ -1479,15 +1479,15 @@ CLASS="answer"
|
|||
><B
|
||||
> </B
|
||||
>
|
||||
Yes. For more information including available translated templates,
|
||||
Yes. For more information including available translated templates,
|
||||
see <A
|
||||
HREF="http://www.bugzilla.org/download.html#localizations"
|
||||
TARGET="_top"
|
||||
>http://www.bugzilla.org/download.html#localizations</A
|
||||
>.
|
||||
The admin interfaces are still not included in these translated
|
||||
templates and is therefore still English only. Also, there may be
|
||||
issues with the charset not being declared. See <A
|
||||
templates and is therefore still English only. Also, there may be
|
||||
issues with the charset not being declared. See <A
|
||||
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=126266"
|
||||
TARGET="_top"
|
||||
>bug 126226</A
|
||||
|
|
@ -1517,7 +1517,7 @@ CLASS="answer"
|
|||
><B
|
||||
> </B
|
||||
>
|
||||
Yes. No. Yes (using the CSV format).
|
||||
Yes. No. Yes (using the CSV format).
|
||||
</P
|
||||
></DIV
|
||||
></DIV
|
||||
|
|
@ -1542,7 +1542,7 @@ CLASS="answer"
|
|||
><B
|
||||
> </B
|
||||
>
|
||||
You have no idea. Bugzilla's query interface, particularly with the
|
||||
You have no idea. Bugzilla's query interface, particularly with the
|
||||
advanced Boolean operators, is incredibly versatile.
|
||||
</P
|
||||
></DIV
|
||||
|
|
@ -1569,7 +1569,7 @@ CLASS="answer"
|
|||
><B
|
||||
> </B
|
||||
>
|
||||
Bugzilla does not lock records. It provides mid-air collision detection,
|
||||
Bugzilla does not lock records. It provides mid-air collision detection,
|
||||
and offers the offending user a choice of options to deal with the conflict.
|
||||
</P
|
||||
></DIV
|
||||
|
|
@ -1599,8 +1599,8 @@ CLASS="answer"
|
|||
at <A
|
||||
HREF="http://www.mysql.com/doc/B/a/Backup.html"
|
||||
TARGET="_top"
|
||||
> http://www.mysql.com/doc/B/a/Backup.html</A
|
||||
>
|
||||
>http://www.mysql.com/doc/B/a/Backup.html</A
|
||||
>.
|
||||
</P
|
||||
></DIV
|
||||
></DIV
|
||||
|
|
@ -1624,8 +1624,8 @@ CLASS="answer"
|
|||
><B
|
||||
> </B
|
||||
>
|
||||
Yes. However, commits to the database must wait
|
||||
until the tables are unlocked. Bugzilla databases are typically
|
||||
Yes. However, commits to the database must wait
|
||||
until the tables are unlocked. Bugzilla databases are typically
|
||||
very small, and backups routinely take less than a minute.
|
||||
</P
|
||||
></DIV
|
||||
|
|
@ -1659,7 +1659,7 @@ CLASS="answer"
|
|||
</P
|
||||
><P
|
||||
> Commercial Bug-tracking software typically costs somewhere upwards
|
||||
of $20,000 or more for 5-10 floating licenses. Bugzilla consultation
|
||||
of $20,000 or more for 5-10 floating licenses. Bugzilla consultation
|
||||
is available from skilled members of the newsgroup. Simple questions
|
||||
are answered there and then.
|
||||
</P
|
||||
|
|
@ -1689,9 +1689,9 @@ CLASS="answer"
|
|||
><B
|
||||
> </B
|
||||
>
|
||||
It all depends on your level of commitment. Someone with much Bugzilla
|
||||
It all depends on your level of commitment. Someone with much Bugzilla
|
||||
experience can get you up and running in less than a day, and
|
||||
your Bugzilla install can run untended for years. If your
|
||||
your Bugzilla install can run untended for years. If your
|
||||
Bugzilla strategy is critical to your business workflow, hire somebody
|
||||
with reasonable UNIX or Perl skills to handle your process management and
|
||||
bug-tracking maintenance & customization.
|
||||
|
|
@ -1719,7 +1719,7 @@ CLASS="answer"
|
|||
><B
|
||||
> </B
|
||||
>
|
||||
No. MySQL asks, if you find their product valuable, that you purchase
|
||||
No. MySQL asks, if you find their product valuable, that you purchase
|
||||
a support contract from them that suits your needs.
|
||||
</P
|
||||
></DIV
|
||||
|
|
@ -1753,7 +1753,7 @@ CLASS="answer"
|
|||
><B
|
||||
> </B
|
||||
>
|
||||
Run MySQL like this: "mysqld --skip-grant-tables". Please remember <EM
|
||||
Run MySQL like this: "mysqld --skip-grant-tables". Please remember <EM
|
||||
>this
|
||||
makes MySQL as secure as taping a $100 to the floor of a football stadium
|
||||
bathroom for safekeeping.</EM
|
||||
|
|
@ -1902,11 +1902,11 @@ CLASS="answer"
|
|||
><B
|
||||
> </B
|
||||
>
|
||||
Try Klaas Freitag's excellent patch for "whineatassigned" functionality.
|
||||
You can find it at <A
|
||||
Try Klaas Freitag's excellent patch for "whineatassigned"
|
||||
functionality. You can find it in <A
|
||||
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=6679"
|
||||
TARGET="_top"
|
||||
>http://bugzilla.mozilla.org/show_bug.cgi?id=6679</A
|
||||
>bug 6679</A
|
||||
>. This
|
||||
patch is against an older version of Bugzilla, so you must apply
|
||||
the diffs manually.
|
||||
|
|
@ -1938,7 +1938,7 @@ CLASS="answer"
|
|||
You can call bug_email.pl directly from your aliases file, with
|
||||
an entry like this:
|
||||
<A
|
||||
NAME="AEN1886"
|
||||
NAME="AEN1985"
|
||||
></A
|
||||
><BLOCKQUOTE
|
||||
CLASS="BLOCKQUOTE"
|
||||
|
|
@ -1949,7 +1949,7 @@ CLASS="BLOCKQUOTE"
|
|||
>
|
||||
However, this is fairly nasty and subject to problems; you also
|
||||
need to set up your smrsh (sendmail restricted shell) to allow
|
||||
it. In a pinch, though, it can work.
|
||||
it. In a pinch, though, it can work.
|
||||
</P
|
||||
></DIV
|
||||
></DIV
|
||||
|
|
@ -2066,7 +2066,7 @@ CLASS="answer"
|
|||
</P
|
||||
><P
|
||||
> If you never receive mail from Bugzilla, chances you do not have
|
||||
sendmail in "/usr/lib/sendmail". Ensure sendmail lives in, or is symlinked
|
||||
sendmail in "/usr/lib/sendmail". Ensure sendmail lives in, or is symlinked
|
||||
to, "/usr/lib/sendmail".
|
||||
</P
|
||||
></DIV
|
||||
|
|
@ -2101,7 +2101,7 @@ CLASS="answer"
|
|||
>
|
||||
Red Hat's old version of Bugzilla (based on 2.8) worked on Oracle.
|
||||
Red Hat's newer version (based on 2.17.1 and soon to be merged into
|
||||
the main distribution) runs on PostgreSQL. At this time we know of
|
||||
the main distribution) runs on PostgreSQL. At this time we know of
|
||||
no recent ports of Bugzilla to Oracle but do intend to support it
|
||||
in the future (possibly the 2.20 time-frame).
|
||||
</P
|
||||
|
|
@ -2140,15 +2140,15 @@ CLASS="filename"
|
|||
it finishes without errors, you're
|
||||
<EM
|
||||
>probably</EM
|
||||
> OK. If it doesn't come back
|
||||
> OK. If it doesn't come back
|
||||
OK (i.e. any red letters), there are certain things
|
||||
Bugzilla can recover from and certain things it can't. If
|
||||
Bugzilla can recover from and certain things it can't. If
|
||||
it can't auto-recover, I hope you're familiar with
|
||||
mysqladmin commands or have installed another way to
|
||||
manage your database. Sanity Check, although it is a good
|
||||
manage your database. Sanity Check, although it is a good
|
||||
basic check on your database integrity, by no means is a
|
||||
substitute for competent database administration and
|
||||
avoiding deletion of data. It is not exhaustive, and was
|
||||
avoiding deletion of data. It is not exhaustive, and was
|
||||
created to do a basic check for the most common problems
|
||||
in Bugzilla databases.
|
||||
</P
|
||||
|
|
@ -2181,7 +2181,7 @@ CLASS="command"
|
|||
>mysql</B
|
||||
>
|
||||
command line utility to manually insert, delete and modify table
|
||||
information. There are also more intuitive GUI clients available.
|
||||
information. There are also more intuitive GUI clients available.
|
||||
Personal favorites of the Bugzilla team are <A
|
||||
HREF="http://www.phpmyadmin.net/"
|
||||
TARGET="_top"
|
||||
|
|
@ -2277,7 +2277,7 @@ CLASS="answer"
|
|||
><B
|
||||
> </B
|
||||
>
|
||||
Well, you can synchronize or you can move bugs. Synchronization will
|
||||
Well, you can synchronize or you can move bugs. Synchronization will
|
||||
only work one way -- you can create a read-only copy of the database
|
||||
at one site, and have it regularly updated at intervals from the main
|
||||
database.
|
||||
|
|
@ -2347,8 +2347,8 @@ CLASS="answer"
|
|||
><B
|
||||
> </B
|
||||
>
|
||||
Not currently. Bundle::Bugzilla enormously simplifies Bugzilla
|
||||
installation on UNIX systems. If someone can volunteer to
|
||||
Not currently. Bundle::Bugzilla enormously simplifies Bugzilla
|
||||
installation on UNIX systems. If someone can volunteer to
|
||||
create a suitable PPM bundle for Win32, it would be appreciated.
|
||||
</P
|
||||
></DIV
|
||||
|
|
@ -2382,7 +2382,7 @@ CLASS="answer"
|
|||
><P
|
||||
> Microsoft has some advice on this matter, as well:
|
||||
<A
|
||||
NAME="AEN1969"
|
||||
NAME="AEN2068"
|
||||
></A
|
||||
><BLOCKQUOTE
|
||||
CLASS="BLOCKQUOTE"
|
||||
|
|
@ -2463,10 +2463,10 @@ CLASS="command"
|
|||
I reckon TimeDate and Data::Dumper come with the activeperl. You can check
|
||||
the ActiveState site for packages for installation through PPM.
|
||||
<A
|
||||
HREF=" http://www.activestate.com/Packages/"
|
||||
HREF="http://www.activestate.com/Packages/"
|
||||
TARGET="_top"
|
||||
> http://www.activestate.com/Packages/</A
|
||||
>
|
||||
>http://www.activestate.com/Packages/</A
|
||||
>.
|
||||
</P
|
||||
></DIV
|
||||
></DIV
|
||||
|
|
@ -2514,7 +2514,7 @@ NAME="faq-use-query"
|
|||
><B
|
||||
>A.7.2. </B
|
||||
>
|
||||
The query page is very confusing. Isn't there a simpler way to query?
|
||||
The query page is very confusing. Isn't there a simpler way to query?
|
||||
</P
|
||||
></DIV
|
||||
><DIV
|
||||
|
|
@ -2551,8 +2551,7 @@ CLASS="answer"
|
|||
> </B
|
||||
>
|
||||
The current behavior is acceptable to bugzilla.mozilla.org and most
|
||||
users. You have your choice of patches
|
||||
to change this behavior, however.
|
||||
users. You have your choice of patches to change this behavior, however.
|
||||
<P
|
||||
></P
|
||||
><TABLE
|
||||
|
|
@ -2579,8 +2578,8 @@ TARGET="_top"
|
|||
><P
|
||||
></P
|
||||
>
|
||||
Note that these patches are somewhat dated. You will need to apply
|
||||
them manually.
|
||||
Note that these patches are somewhat dated. You will need to apply
|
||||
them manually.
|
||||
</P
|
||||
></DIV
|
||||
></DIV
|
||||
|
|
@ -2596,7 +2595,7 @@ NAME="faq-use-attachment"
|
|||
>A.7.4. </B
|
||||
>
|
||||
I can't upload anything into the database via the "Create Attachment"
|
||||
link. What am I doing wrong?
|
||||
link. What am I doing wrong?
|
||||
</P
|
||||
></DIV
|
||||
><DIV
|
||||
|
|
@ -2606,7 +2605,7 @@ CLASS="answer"
|
|||
> </B
|
||||
>
|
||||
The most likely cause is a very old browser or a browser that is
|
||||
incompatible with file upload via POST. Download the latest Netscape,
|
||||
incompatible with file upload via POST. Download the latest Netscape,
|
||||
Microsoft, or Mozilla browser to handle uploads correctly.
|
||||
</P
|
||||
></DIV
|
||||
|
|
@ -2632,8 +2631,8 @@ CLASS="answer"
|
|||
> </B
|
||||
>
|
||||
In the Bugzilla administrator UI, edit the keyword and it will let you
|
||||
replace the old keyword name with a new one. This will cause a problem
|
||||
with the keyword cache. Run sanitycheck.cgi to fix it.
|
||||
replace the old keyword name with a new one. This will cause a problem
|
||||
with the keyword cache. Run sanitycheck.cgi to fix it.
|
||||
</P
|
||||
></DIV
|
||||
></DIV
|
||||
|
|
@ -2666,7 +2665,7 @@ CLASS="answer"
|
|||
> </B
|
||||
>
|
||||
Gerv and Myk suggest a 2-space indent, with embedded code sections on
|
||||
their own line, in line with outer tags. Like this:</P
|
||||
their own line, in line with outer tags. Like this:</P
|
||||
><TABLE
|
||||
BORDER="0"
|
||||
BGCOLOR="#E0E0E0"
|
||||
|
|
@ -2701,7 +2700,7 @@ CLASS="programlisting"
|
|||
><P
|
||||
>Please note that many have differing opinions on this subject,
|
||||
and the existing templates in Bugzilla espouse both this and a 4-space
|
||||
style. Either is acceptable; the above is preferred.</P
|
||||
style. Either is acceptable; the above is preferred.</P
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
|
|
@ -2739,7 +2738,7 @@ TARGET="_top"
|
|||
>here</A
|
||||
>.
|
||||
This list includes bugs for the 2.18 release that have already
|
||||
been fixed and checked into CVS. Please consult the
|
||||
been fixed and checked into CVS. Please consult the
|
||||
<A
|
||||
HREF="http://www.bugzilla.org/"
|
||||
TARGET="_top"
|
||||
|
|
@ -2771,14 +2770,13 @@ CLASS="answer"
|
|||
><B
|
||||
> </B
|
||||
>
|
||||
This is well-documented here: <A
|
||||
This is well-documented in <A
|
||||
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=49862"
|
||||
TARGET="_top"
|
||||
> http://bugzilla.mozilla.org/show_bug.cgi?id=49862</A
|
||||
>. Ultimately, it's as easy
|
||||
as adding the "---" priority field to your localconfig file in the appropriate area,
|
||||
re-running checksetup.pl, and then changing the default priority in your browser using
|
||||
"editparams.cgi".
|
||||
> bug 49862</A
|
||||
>. Ultimately, it's as easy as adding the "---" priority field to your
|
||||
localconfig file in the appropriate area, re-running checksetup.pl, and then changing the
|
||||
default priority in your browser using "editparams.cgi".
|
||||
</P
|
||||
></DIV
|
||||
></DIV
|
||||
|
|
@ -2827,7 +2825,7 @@ TARGET="_top"
|
|||
or new source file by clicking
|
||||
"Create a new attachment" link on the bug page you've just created, and
|
||||
include any descriptions of database changes you may make, into the bug
|
||||
ID you submitted in step #1. Be sure and click the "Patch" checkbox
|
||||
ID you submitted in step #1. Be sure and click the "Patch" checkbox
|
||||
to indicate the text you are sending is a patch!
|
||||
</P
|
||||
></LI
|
||||
|
|
@ -2835,7 +2833,7 @@ TARGET="_top"
|
|||
><P
|
||||
> Announce your patch and the associated URL
|
||||
(http://bugzilla.mozilla.org/show_bug.cgi?id=XXXXXX) for discussion in
|
||||
the newsgroup (netscape.public.mozilla.webtools). You'll get a really
|
||||
the newsgroup (netscape.public.mozilla.webtools). You'll get a really
|
||||
good, fairly immediate reaction to the implications of your patch,
|
||||
which will also give us an idea how well-received the change would
|
||||
be.
|
||||
|
|
|
|||
|
|
@ -84,10 +84,8 @@ NAME="gfdl-10"
|
|||
<A
|
||||
HREF="http://www.gnu.org/copyleft/"
|
||||
TARGET="_top"
|
||||
> http://www.gnu.org/copyleft/</A
|
||||
>
|
||||
|
||||
.</P
|
||||
>http://www.gnu.org/copyleft/</A
|
||||
>.</P
|
||||
><P
|
||||
>Each version of the License is given a distinguishing version
|
||||
number. If the Document specifies that a particular numbered version of
|
||||
|
|
|
|||
|
|
@ -81,7 +81,7 @@ NAME="gfdl-howto"
|
|||
of the License in the document and put the following copyright and
|
||||
license notices just after the title page:</P
|
||||
><A
|
||||
NAME="AEN2296"
|
||||
NAME="AEN2395"
|
||||
></A
|
||||
><BLOCKQUOTE
|
||||
CLASS="BLOCKQUOTE"
|
||||
|
|
|
|||
|
|
@ -144,7 +144,7 @@ HREF="gfdl-howto.html"
|
|||
><P
|
||||
>Version 1.1, March 2000</P
|
||||
><A
|
||||
NAME="AEN2206"
|
||||
NAME="AEN2305"
|
||||
></A
|
||||
><BLOCKQUOTE
|
||||
CLASS="BLOCKQUOTE"
|
||||
|
|
|
|||
|
|
@ -70,7 +70,7 @@ CLASS="glossdiv"
|
|||
><H1
|
||||
CLASS="glossdiv"
|
||||
><A
|
||||
NAME="AEN2301"
|
||||
NAME="AEN2400"
|
||||
></A
|
||||
>0-9, high ascii</H1
|
||||
><DL
|
||||
|
|
@ -353,13 +353,9 @@ NAME="gloss-component"
|
|||
NAME="gloss-cpan"
|
||||
></A
|
||||
><B
|
||||
> <SPAN
|
||||
CLASS="acronym"
|
||||
>CPAN</SPAN
|
||||
>
|
||||
</B
|
||||
>Comprehensive Perl Archive Network</B
|
||||
></DT
|
||||
><DD
|
||||
> (CPAN)<DD
|
||||
><P
|
||||
> <SPAN
|
||||
CLASS="acronym"
|
||||
|
|
@ -600,6 +596,22 @@ NAME="gloss-p"
|
|||
>P</H1
|
||||
><DL
|
||||
><DT
|
||||
><A
|
||||
NAME="gloss-ppm"
|
||||
></A
|
||||
><B
|
||||
>Perl Package Manager</B
|
||||
></DT
|
||||
> (PPM)<DD
|
||||
><P
|
||||
><A
|
||||
HREF="http://aspn.activestate.com/ASPN/Downloads/ActivePerl/PPM/"
|
||||
TARGET="_top"
|
||||
>http://aspn.activestate.com/ASPN/Downloads/ActivePerl/PPM/</A
|
||||
>
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
><B
|
||||
>Product</B
|
||||
></DT
|
||||
|
|
@ -866,7 +878,7 @@ NAME="gloss-zarro"
|
|||
Terry had the following to say:
|
||||
</P
|
||||
><A
|
||||
NAME="AEN2521"
|
||||
NAME="AEN2626"
|
||||
></A
|
||||
><TABLE
|
||||
BORDER="0"
|
||||
|
|
|
|||
|
|
@ -84,7 +84,7 @@ CLASS="section"
|
|||
><H2
|
||||
CLASS="section"
|
||||
><A
|
||||
NAME="AEN370"
|
||||
NAME="AEN371"
|
||||
></A
|
||||
>3.2.1. Autolinkification</H2
|
||||
><P
|
||||
|
|
@ -232,7 +232,7 @@ CLASS="section"
|
|||
><H2
|
||||
CLASS="section"
|
||||
><A
|
||||
NAME="AEN399"
|
||||
NAME="AEN400"
|
||||
></A
|
||||
>3.2.5. Filing Bugs</H2
|
||||
><P
|
||||
|
|
|
|||
|
|
@ -105,8 +105,8 @@ NAME="myaccount"
|
|||
<A
|
||||
HREF="http://landfill.bugzilla.org/bugzilla-tip/"
|
||||
TARGET="_top"
|
||||
> http://landfill.bugzilla.org/bugzilla-tip/</A
|
||||
>
|
||||
>http://landfill.bugzilla.org/bugzilla-tip/</A
|
||||
>.
|
||||
</P
|
||||
><P
|
||||
></P
|
||||
|
|
@ -441,10 +441,8 @@ NAME="query"
|
|||
<A
|
||||
HREF="http://landfill.bugzilla.org/bugzilla-tip/query.cgi"
|
||||
TARGET="_top"
|
||||
> landfill.bugzilla.org/bugzilla-tip/query.cgi</A
|
||||
>
|
||||
|
||||
.</P
|
||||
>http://landfill.bugzilla.org/bugzilla-tip/query.cgi</A
|
||||
>.</P
|
||||
><P
|
||||
>The Search page has controls for selecting different possible
|
||||
values for all of the fields in a bug, as described above. Once you've
|
||||
|
|
|
|||
|
|
@ -120,7 +120,7 @@ CLASS="command"
|
|||
>./checksetup.pl</B
|
||||
> (shown in <A
|
||||
HREF="http.html#http-apache-htaccess"
|
||||
>Example 4-1</A
|
||||
>Example 4-2</A
|
||||
>
|
||||
for the curious) are allowed to override Apache's normal access
|
||||
permissions or else important password information may be exposed to the
|
||||
|
|
@ -241,7 +241,7 @@ NAME="http-apache-htaccess"
|
|||
></A
|
||||
><P
|
||||
><B
|
||||
>Example 4-1. <TT
|
||||
>Example 4-2. <TT
|
||||
CLASS="filename"
|
||||
>.htaccess</TT
|
||||
> files for Apache</B
|
||||
|
|
@ -420,7 +420,7 @@ CLASS="productname"
|
|||
<A
|
||||
HREF="http://support.microsoft.com/support/kb/articles/Q245/2/25.asp"
|
||||
TARGET="_top"
|
||||
>Q245225 </A
|
||||
>Q245225</A
|
||||
>
|
||||
for <SPAN
|
||||
CLASS="productname"
|
||||
|
|
@ -552,12 +552,11 @@ VALIGN="TOP"
|
|||
<TT
|
||||
CLASS="filename"
|
||||
>localconfig</TT
|
||||
>. For more information, see
|
||||
>. For more information, see
|
||||
<A
|
||||
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=186383"
|
||||
TARGET="_top"
|
||||
>bug
|
||||
186383</A
|
||||
> bug 186383</A
|
||||
> or <A
|
||||
HREF="http://online.securityfocus.com/bid/6501"
|
||||
TARGET="_top"
|
||||
|
|
|
|||
|
|
@ -451,11 +451,16 @@ CLASS="LOT"
|
|||
></DT
|
||||
><DT
|
||||
>4-1. <A
|
||||
HREF="stepbystep.html#install-mysql-packets"
|
||||
>Set Max Packet Size in MySQL</A
|
||||
></DT
|
||||
><DT
|
||||
>4-2. <A
|
||||
HREF="troubleshooting.html#trouble-filetemp-errors"
|
||||
>Other File::Temp error messages</A
|
||||
></DT
|
||||
><DT
|
||||
>4-2. <A
|
||||
>4-3. <A
|
||||
HREF="troubleshooting.html#trouble-filetemp-patch"
|
||||
>Patch for File::Temp in Perl 5.6.0</A
|
||||
></DT
|
||||
|
|
@ -471,6 +476,11 @@ CLASS="LOT"
|
|||
></DT
|
||||
><DT
|
||||
>4-1. <A
|
||||
HREF="stepbystep.html#install-perlmodules-cpan"
|
||||
>Installing perl modules with CPAN</A
|
||||
></DT
|
||||
><DT
|
||||
>4-2. <A
|
||||
HREF="http.html#http-apache-htaccess"
|
||||
><TT
|
||||
CLASS="filename"
|
||||
|
|
|
|||
|
|
@ -88,55 +88,45 @@ HREF="stepbystep.html"
|
|||
><DL
|
||||
><DT
|
||||
>4.1.1. <A
|
||||
HREF="stepbystep.html#intstall-into"
|
||||
>Introduction</A
|
||||
></DT
|
||||
><DT
|
||||
>4.1.2. <A
|
||||
HREF="stepbystep.html#install-package-list"
|
||||
>Package List</A
|
||||
></DT
|
||||
><DT
|
||||
>4.1.3. <A
|
||||
HREF="stepbystep.html#install-mysql"
|
||||
>MySQL</A
|
||||
></DT
|
||||
><DT
|
||||
>4.1.4. <A
|
||||
>4.1.2. <A
|
||||
HREF="stepbystep.html#install-perl"
|
||||
>Perl</A
|
||||
></DT
|
||||
><DT
|
||||
>4.1.5. <A
|
||||
HREF="stepbystep.html#perl-modules"
|
||||
>4.1.3. <A
|
||||
HREF="stepbystep.html#install-perlmodules"
|
||||
>Perl Modules</A
|
||||
></DT
|
||||
><DT
|
||||
>4.1.6. <A
|
||||
HREF="stepbystep.html#sbs-http"
|
||||
>4.1.4. <A
|
||||
HREF="stepbystep.html#install-webserver"
|
||||
>HTTP Server</A
|
||||
></DT
|
||||
><DT
|
||||
>4.1.7. <A
|
||||
HREF="stepbystep.html#AEN600"
|
||||
>4.1.5. <A
|
||||
HREF="stepbystep.html#install-bzfiles"
|
||||
>Bugzilla</A
|
||||
></DT
|
||||
><DT
|
||||
>4.1.8. <A
|
||||
HREF="stepbystep.html#AEN611"
|
||||
>4.1.6. <A
|
||||
HREF="stepbystep.html#install-setupdatabase"
|
||||
>Setting Up the MySQL Database</A
|
||||
></DT
|
||||
><DT
|
||||
>4.1.9. <A
|
||||
HREF="stepbystep.html#AEN649"
|
||||
>4.1.7. <A
|
||||
HREF="stepbystep.html#AEN749"
|
||||
><TT
|
||||
CLASS="filename"
|
||||
>checksetup.pl</TT
|
||||
></A
|
||||
></DT
|
||||
><DT
|
||||
>4.1.10. <A
|
||||
HREF="stepbystep.html#AEN681"
|
||||
>4.1.8. <A
|
||||
HREF="stepbystep.html#AEN780"
|
||||
>Configuring Bugzilla</A
|
||||
></DT
|
||||
></DL
|
||||
|
|
@ -150,17 +140,17 @@ HREF="extraconfig.html"
|
|||
><DL
|
||||
><DT
|
||||
>4.2.1. <A
|
||||
HREF="extraconfig.html#AEN687"
|
||||
HREF="extraconfig.html#AEN786"
|
||||
>Dependency Charts</A
|
||||
></DT
|
||||
><DT
|
||||
>4.2.2. <A
|
||||
HREF="extraconfig.html#AEN702"
|
||||
HREF="extraconfig.html#AEN801"
|
||||
>Bug Graphs</A
|
||||
></DT
|
||||
><DT
|
||||
>4.2.3. <A
|
||||
HREF="extraconfig.html#AEN715"
|
||||
HREF="extraconfig.html#AEN814"
|
||||
>The Whining Cron</A
|
||||
></DT
|
||||
><DT
|
||||
|
|
@ -268,12 +258,12 @@ HREF="troubleshooting.html"
|
|||
><DL
|
||||
><DT
|
||||
>4.5.1. <A
|
||||
HREF="troubleshooting.html#AEN977"
|
||||
HREF="troubleshooting.html#AEN1076"
|
||||
>Bundle::Bugzilla makes me upgrade to Perl 5.6.1</A
|
||||
></DT
|
||||
><DT
|
||||
>4.5.2. <A
|
||||
HREF="troubleshooting.html#AEN982"
|
||||
HREF="troubleshooting.html#AEN1081"
|
||||
>DBD::Sponge::db prepare failed</A
|
||||
></DT
|
||||
><DT
|
||||
|
|
|
|||
|
|
@ -131,11 +131,10 @@ CLASS="filename"
|
|||
><P
|
||||
>There is also a CVSZilla project, based upon somewhat dated
|
||||
Bugzilla code, to integrate CVS and Bugzilla through CVS' ability to
|
||||
email. Check it out at:
|
||||
<A
|
||||
email. Check it out at: <A
|
||||
HREF="http://homepages.kcbbs.gen.nz/~tonyg/"
|
||||
TARGET="_top"
|
||||
> http://homepages.kcbbs.gen.nz/~tonyg/</A
|
||||
>http://homepages.kcbbs.gen.nz/~tonyg/</A
|
||||
>.
|
||||
</P
|
||||
></DIV
|
||||
|
|
@ -153,7 +152,7 @@ NAME="scm"
|
|||
<A
|
||||
HREF="http://www.ravenbrook.com/project/p4dti/"
|
||||
TARGET="_top"
|
||||
> http://www.ravenbrook.com/project/p4dti</A
|
||||
>http://www.ravenbrook.com/project/p4dti/</A
|
||||
>
|
||||
|
||||
.
|
||||
|
|
@ -167,7 +166,7 @@ CLASS="QUOTE"
|
|||
<A
|
||||
HREF="http://public.perforce.com/public/perforce/p4dti/index.html"
|
||||
TARGET="_top"
|
||||
> http://public.perforce.com/public/perforce/p4dti/index.html</A
|
||||
>http://public.perforce.com/public/perforce/p4dti/index.html</A
|
||||
>
|
||||
|
||||
.</P
|
||||
|
|
|
|||
|
|
@ -93,7 +93,7 @@ NAME="newversions"
|
|||
> The newest version of this guide can always be found at <A
|
||||
HREF="http://www.bugzilla.org"
|
||||
TARGET="_top"
|
||||
>bugzilla.org</A
|
||||
>http://www.bugzilla.org</A
|
||||
>; including
|
||||
documentation for past releases and the current development version.
|
||||
</P
|
||||
|
|
@ -108,13 +108,12 @@ TARGET="_top"
|
|||
</P
|
||||
><P
|
||||
> The latest version of this document can always be checked out via CVS.
|
||||
Please follow the instructions available at
|
||||
<A
|
||||
Please follow the <A
|
||||
HREF="http://www.mozilla.org/cvs.html"
|
||||
TARGET="_top"
|
||||
>the Mozilla CVS page</A
|
||||
>,
|
||||
and check out the <TT
|
||||
>Mozilla CVS</A
|
||||
>
|
||||
instructions and check out the <TT
|
||||
CLASS="filename"
|
||||
>mozilla/webtools/bugzilla/docs/</TT
|
||||
>
|
||||
|
|
|
|||
|
|
@ -143,19 +143,23 @@ CLASS="section"
|
|||
><H3
|
||||
CLASS="section"
|
||||
><A
|
||||
NAME="win32-perl-modules"
|
||||
NAME="win32-perlmodules"
|
||||
></A
|
||||
>4.3.1.2. Perl Modules on Win32</H3
|
||||
><P
|
||||
>Bugzilla on Windows requires the same perl modules found in
|
||||
<A
|
||||
HREF="stepbystep.html#install-package-list"
|
||||
>Section 4.1.2</A
|
||||
HREF="stepbystep.html#install-perlmodules"
|
||||
>Section 4.1.3</A
|
||||
>. The main difference is that
|
||||
windows uses <B
|
||||
CLASS="command"
|
||||
>ppm</B
|
||||
> instead of CPAN.
|
||||
windows uses <A
|
||||
HREF="glossary.html#gloss-ppm"
|
||||
><I
|
||||
CLASS="glossterm"
|
||||
>PPM</I
|
||||
></A
|
||||
> instead of
|
||||
CPAN.
|
||||
</P
|
||||
><TABLE
|
||||
BORDER="0"
|
||||
|
|
@ -606,7 +610,7 @@ CLASS="prompt"
|
|||
> <B
|
||||
CLASS="command"
|
||||
>urpmi perl-MailTools</B
|
||||
> <A
|
||||
> <A
|
||||
NAME="test-mailtools"
|
||||
><IMG
|
||||
SRC="../images/callouts/1.gif"
|
||||
|
|
|
|||
|
|
@ -406,12 +406,11 @@ NAME="security-access"
|
|||
not be accessible is rather complicated. A new installation method
|
||||
is currently in the works which should solve this by allowing files
|
||||
that shouldn't be accessible from the web to be placed in directory
|
||||
outside the webroot. See
|
||||
outside the webroot. See
|
||||
<A
|
||||
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=44659"
|
||||
TARGET="_top"
|
||||
>bug
|
||||
44659</A
|
||||
> bug 44659</A
|
||||
> for more information.
|
||||
</P
|
||||
><P
|
||||
|
|
|
|||
Разница между файлами не показана из-за своего большого размера
Загрузить разницу
|
|
@ -85,7 +85,7 @@ CLASS="section"
|
|||
><H2
|
||||
CLASS="section"
|
||||
><A
|
||||
NAME="AEN977"
|
||||
NAME="AEN1076"
|
||||
></A
|
||||
>4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2
|
||||
><P
|
||||
|
|
@ -110,7 +110,7 @@ CLASS="section"
|
|||
><H2
|
||||
CLASS="section"
|
||||
><A
|
||||
NAME="AEN982"
|
||||
NAME="AEN1081"
|
||||
></A
|
||||
>4.5.2. DBD::Sponge::db prepare failed</H2
|
||||
><P
|
||||
|
|
@ -266,7 +266,7 @@ CLASS="productname"
|
|||
5.6.0. Many minor variations of this error have been reported. Examples
|
||||
can be found in <A
|
||||
HREF="troubleshooting.html#trouble-filetemp-errors"
|
||||
>Figure 4-1</A
|
||||
>Figure 4-2</A
|
||||
>.
|
||||
</P
|
||||
><DIV
|
||||
|
|
@ -276,7 +276,7 @@ NAME="trouble-filetemp-errors"
|
|||
></A
|
||||
><P
|
||||
><B
|
||||
>Figure 4-1. Other File::Temp error messages</B
|
||||
>Figure 4-2. Other File::Temp error messages</B
|
||||
></P
|
||||
><TABLE
|
||||
BORDER="0"
|
||||
|
|
@ -307,7 +307,7 @@ at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 233.
|
|||
or higher solved the problem for them. A less involved fix is to apply
|
||||
the patch in <A
|
||||
HREF="troubleshooting.html#trouble-filetemp-patch"
|
||||
>Figure 4-2</A
|
||||
>Figure 4-3</A
|
||||
>. The patch is also
|
||||
available as a <A
|
||||
HREF="../xml/filetemp.patch"
|
||||
|
|
@ -322,7 +322,7 @@ NAME="trouble-filetemp-patch"
|
|||
></A
|
||||
><P
|
||||
><B
|
||||
>Figure 4-2. Patch for File::Temp in Perl 5.6.0</B
|
||||
>Figure 4-3. Patch for File::Temp in Perl 5.6.0</B
|
||||
></P
|
||||
><TABLE
|
||||
BORDER="0"
|
||||
|
|
|
|||
|
|
@ -122,7 +122,7 @@ HREF="hintsandtips.html"
|
|||
><DL
|
||||
><DT
|
||||
>3.2.1. <A
|
||||
HREF="hintsandtips.html#AEN370"
|
||||
HREF="hintsandtips.html#AEN371"
|
||||
>Autolinkification</A
|
||||
></DT
|
||||
><DT
|
||||
|
|
@ -142,7 +142,7 @@ HREF="hintsandtips.html#attachments"
|
|||
></DT
|
||||
><DT
|
||||
>3.2.5. <A
|
||||
HREF="hintsandtips.html#AEN399"
|
||||
HREF="hintsandtips.html#AEN400"
|
||||
>Filing Bugs</A
|
||||
></DT
|
||||
></DL
|
||||
|
|
|
|||
|
|
@ -84,12 +84,10 @@ CLASS="QUOTE"
|
|||
>
|
||||
functionality.</P
|
||||
><P
|
||||
>URL:
|
||||
<A
|
||||
>URL: <A
|
||||
HREF="http://www.perforce.com/perforce/technotes/note052.html"
|
||||
TARGET="_top"
|
||||
> http://www.perforce.com/perforce/technotes/note052.html
|
||||
</A
|
||||
>http://www.perforce.com/perforce/technotes/note052.html</A
|
||||
>
|
||||
</P
|
||||
><P
|
||||
|
|
|
|||
|
|
@ -78,26 +78,25 @@ NAME="variant-redhat"
|
|||
>D.1. Red Hat Bugzilla</H1
|
||||
><P
|
||||
>Red Hat's old fork of Bugzilla which was based on version 2.8 is now
|
||||
obsolete. The newest version in use is based on version 2.17.1 and is in
|
||||
the process of being integrated into the main Bugzilla source tree. The
|
||||
obsolete. The newest version in use is based on version 2.17.1 and is in
|
||||
the process of being integrated into the main Bugzilla source tree. The
|
||||
back-end is modified to work with PostgreSQL instead of MySQL and they have
|
||||
custom templates to get their desired look and feel, but other than that it
|
||||
is Bugzilla 2.17.1. Dave Lawrence of Red Hat put forth a great deal of
|
||||
is Bugzilla 2.17.1. Dave Lawrence of Red Hat put forth a great deal of
|
||||
effort to make sure that the changes he made could be integrated back into
|
||||
the main tree.
|
||||
<A
|
||||
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=98304"
|
||||
TARGET="_top"
|
||||
>Bug
|
||||
98304</A
|
||||
> exists to track this integration.
|
||||
>Bug 98304</A
|
||||
>
|
||||
exists to track this integration.
|
||||
</P
|
||||
><P
|
||||
>URL:
|
||||
<A
|
||||
>URL: <A
|
||||
HREF="http://bugzilla.redhat.com/bugzilla/"
|
||||
TARGET="_top"
|
||||
> http://bugzilla.redhat.com/bugzilla/</A
|
||||
>http://bugzilla.redhat.com/bugzilla/</A
|
||||
>
|
||||
</P
|
||||
><P
|
||||
|
|
|
|||
|
|
@ -80,11 +80,10 @@ NAME="variant-scarab"
|
|||
>Scarab is a new open source bug-tracking system built using Java
|
||||
Servlet technology. It is currently at version 1.0 beta 13.</P
|
||||
><P
|
||||
>URL:
|
||||
<A
|
||||
>URL: <A
|
||||
HREF="http://scarab.tigris.org/"
|
||||
TARGET="_top"
|
||||
>http://scarab.tigris.org</A
|
||||
>http://scarab.tigris.org/</A
|
||||
>
|
||||
</P
|
||||
><P
|
||||
|
|
|
|||
|
|
@ -81,11 +81,10 @@ NAME="variant-sourceforge"
|
|||
distributed free software and open source projects over the Internet.
|
||||
It has a built-in bug tracker, but it's not highly thought of.</P
|
||||
><P
|
||||
>URL:
|
||||
<A
|
||||
>URL: <A
|
||||
HREF="http://www.sourceforge.net"
|
||||
TARGET="_top"
|
||||
> http://www.sourceforge.net</A
|
||||
>http://www.sourceforge.net</A
|
||||
>
|
||||
</P
|
||||
><P
|
||||
|
|
|
|||
|
|
@ -119,8 +119,8 @@ HREF="variant-sourceforge.html"
|
|||
<A
|
||||
HREF="http://linas.org/linux/pm.html"
|
||||
TARGET="_top"
|
||||
> http://linas.org/linux/pm.html</A
|
||||
>
|
||||
>http://linas.org/linux/pm.html</A
|
||||
>.
|
||||
</P
|
||||
></DIV
|
||||
><DIV
|
||||
|
|
|
|||
|
|
@ -106,7 +106,7 @@ TYPE="1"
|
|||
><P
|
||||
><EM
|
||||
>Maximum Votes a person can put on a single
|
||||
bug"</EM
|
||||
bug</EM
|
||||
>:
|
||||
It should probably be some number lower than the
|
||||
"Maximum votes per person". Don't set this field to "0" if
|
||||
|
|
|
|||
Разница между файлами не показана из-за своего большого размера
Загрузить разницу
Загрузка…
Ссылка в новой задаче