From: gerv%gerv.net <>
Date: Fri, 26 Jul 2002 04:03:27 +0000 (+0000)
Subject: Last-minute tweaks and fixes for 2.16 release.
X-Git-Tag: bugzilla-2.16~3
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=6500050c5797c0fa2ceb53aece8d3b965ef7b5a9;p=thirdparty%2Fbugzilla.git
Last-minute tweaks and fixes for 2.16 release.
---
diff --git a/docs/sgml/Bugzilla-Guide.sgml b/docs/sgml/Bugzilla-Guide.sgml
index b99a3b9dd5..b8868a618d 100644
--- a/docs/sgml/Bugzilla-Guide.sgml
+++ b/docs/sgml/Bugzilla-Guide.sgml
@@ -82,16 +82,6 @@ try to avoid clutter and feel free to waste space in the code to make it more re
organizations around the world, tracking millions of bugs.
-
-
- 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
diff --git a/docs/sgml/administration.sgml b/docs/sgml/administration.sgml
index 66489469d3..f932beb25a 100644
--- a/docs/sgml/administration.sgml
+++ b/docs/sgml/administration.sgml
@@ -921,53 +921,68 @@
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,
template, which contains a directory for
each installed localisation. The default English templates are
therefore in en. Underneath that, there
- are two directories - default and
- custom (you may have to create
- custom yourself.) The default
- directory contains all the templates shipped with Bugzilla.
+ is the default directory and optionally the
+ custom directory. The default
+ 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 template/en/default. This is probably the
- best method for small changes, because if you then execute a
+ 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 if you are going to use
+ the CVS method of upgrading, because if you then execute a
cvs update, any template fixes will get
automagically merged into your modified versions.
- 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.
+ If you use this method, your installation will break if CVS conflicts
+ occur.
- 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.
+ The other method is to copy the templates into a mirrored directory
+ structure under template/en/custom. 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.
-
+
- If you are making changes to contribute back to Bugzilla (and we'd
- love to have them), then please read the
- Developers
- Guide first.
+ 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.
+
+
+
+
+
+ How To Edit Templates
The syntax of the Template Toolkit language is beyond the scope of
@@ -979,11 +994,41 @@
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 <. 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.
@@ -1052,13 +1097,38 @@
- global/header.html.tmpl and
+ global/header.html.tmpl:
+ 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.
+
+
bug/create/create.html.tmpl and
bug/create/comment.txt.tmpl:
@@ -1072,7 +1142,7 @@
guided
bug submission form.
-
+
To make this work, create a custom template for
enter_bug.cgi (the default template, on which you
diff --git a/docs/sgml/conventions.sgml b/docs/sgml/conventions.sgml
index ccc661086d..7334b02b8b 100644
--- a/docs/sgml/conventions.sgml
+++ b/docs/sgml/conventions.sgml
@@ -138,11 +138,9 @@
Code Example
-
-para
+ para
Beginning and end of paragraph
-para
-
+para
diff --git a/docs/sgml/installation.sgml b/docs/sgml/installation.sgml
index d9297ce47c..0433b4b520 100644
--- a/docs/sgml/installation.sgml
+++ b/docs/sgml/installation.sgml
@@ -1122,6 +1122,10 @@
non-English-speaking Bugzilla sites, I suggest changing
ISO-8859-1
, above, to
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.
@@ -1236,25 +1240,40 @@
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.
+
+
Win32 Installation: Step-by-step
@@ -2033,6 +2052,26 @@ binmode(STDOUT);
problems.
+
+ 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.
+
+
+
+
DBD::Sponge::db prepare failed
diff --git a/docs/sgml/introduction.sgml b/docs/sgml/introduction.sgml
index 88f9b26822..33907552b5 100644
--- a/docs/sgml/introduction.sgml
+++ b/docs/sgml/introduction.sgml
@@ -104,7 +104,10 @@
management, chip design and development problem tracking (both
pre-and-post fabrication), and software and hardware bug tracking for
luminaries such as Redhat, NASA, Linux-Mandrake, and VA Systems.
- Combined with systems such as CVS, Bonsai, or Perforce SCM, Bugzilla
+ Combined with systems such as
+ CVS,
+ Bonsai, or
+ Perforce SCM, Bugzilla
provides a powerful, easy-to-use solution to configuration management and
replication problems.
diff --git a/docs/sgml/using.sgml b/docs/sgml/using.sgml
index 74cca38255..a3986c27d2 100644
--- a/docs/sgml/using.sgml
+++ b/docs/sgml/using.sgml
@@ -8,7 +8,7 @@
This section contains information for end-users of Bugzilla.
There is a Bugzilla test installation, called
- Landfill,
+ Landfill,
which you are welcome to play with (if it's up.)
However, it does not necessarily
have all Bugzilla features enabled, and often runs cutting-edge versions
@@ -22,8 +22,8 @@
Consult with the administrator responsible for your installation of
Bugzilla for the URL you should use to access it. If you're
test-driving Bugzilla, use this URL:
-
- http://landfill.tequilarista.org/bugzilla-tip/
+
+ http://landfill.bugzilla.org/bugzilla-tip/
@@ -69,7 +69,7 @@
The core of Bugzilla is the screen which displays a particular
bug. It's a good place to explain some Bugzilla concepts.
+ url="http://landfill.bugzilla.org/bugzilla-tip/show_bug.cgi?id=1">
Bug 1 on Landfill
is a good example. Note that the labels for most fields are hyperlinks;
@@ -269,8 +269,8 @@
The Bugzilla Search page is is the interface where you can find
any bug report, comment, or patch currently in the Bugzilla system. You
can play with it here:
-
- landfill.tequilarista.org/bugzilla-tip/query.cgi
+
+ landfill.bugzilla.org/bugzilla-tip/query.cgi
.
@@ -282,7 +282,7 @@
Highly advanced querying is done using Boolean Charts, which have
their own
+ url="http://landfill.bugzilla.org/bugzilla-tip/booleanchart.html">
context-sensitive help
.
@@ -339,7 +339,7 @@
Years of bug writing experience has been distilled for your
reading pleasure into the
+ url="http://landfill.bugzilla.org/bugzilla-tip/bugwritinghelp.html">
Bug Writing Guidelines.
While some of the advice is Mozilla-specific, the basic principles of
reporting Reproducible, Specific bugs, isolating the Product you are
@@ -353,11 +353,11 @@
Go to
-
+
Landfill
in your browser and click
+ url="http://landfill.bugzilla.org/bugzilla-tip/enter_bug.cgi">
Enter a new bug report.
diff --git a/docs/sgml/variants.sgml b/docs/sgml/variants.sgml
index 2668acb355..73f6822fbd 100644
--- a/docs/sgml/variants.sgml
+++ b/docs/sgml/variants.sgml
@@ -13,9 +13,8 @@
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
@@ -49,7 +48,7 @@
Scarab
Scarab is a new open source bug-tracking system built using Java
- Serlet technology. It is currently at version 1.0 beta 7.
+ Serlet technology. It is currently at version 1.0 beta 8.
URL:
http://scarab.tigris.org
diff --git a/docs/xml/Bugzilla-Guide.xml b/docs/xml/Bugzilla-Guide.xml
index b99a3b9dd5..b8868a618d 100644
--- a/docs/xml/Bugzilla-Guide.xml
+++ b/docs/xml/Bugzilla-Guide.xml
@@ -82,16 +82,6 @@ try to avoid clutter and feel free to waste space in the code to make it more re
organizations around the world, tracking millions of bugs.
-
-
- 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
diff --git a/docs/xml/administration.xml b/docs/xml/administration.xml
index 66489469d3..f932beb25a 100644
--- a/docs/xml/administration.xml
+++ b/docs/xml/administration.xml
@@ -921,53 +921,68 @@
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,
template, which contains a directory for
each installed localisation. The default English templates are
therefore in en. Underneath that, there
- are two directories - default and
- custom (you may have to create
- custom yourself.) The default
- directory contains all the templates shipped with Bugzilla.
+ is the default directory and optionally the
+ custom directory. The default
+ 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 template/en/default. This is probably the
- best method for small changes, because if you then execute a
+ 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 if you are going to use
+ the CVS method of upgrading, because if you then execute a
cvs update, any template fixes will get
automagically merged into your modified versions.
- 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.
+ If you use this method, your installation will break if CVS conflicts
+ occur.
- 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.
+ The other method is to copy the templates into a mirrored directory
+ structure under template/en/custom. 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.
-
+
- If you are making changes to contribute back to Bugzilla (and we'd
- love to have them), then please read the
- Developers
- Guide first.
+ 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.
+
+
+
+
+
+ How To Edit Templates
The syntax of the Template Toolkit language is beyond the scope of
@@ -979,11 +994,41 @@
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 <. 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.
@@ -1052,13 +1097,38 @@
- global/header.html.tmpl and
+ global/header.html.tmpl:
+ 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.
+
+
bug/create/create.html.tmpl and
bug/create/comment.txt.tmpl:
@@ -1072,7 +1142,7 @@
guided
bug submission form.
-
+
To make this work, create a custom template for
enter_bug.cgi (the default template, on which you
diff --git a/docs/xml/conventions.xml b/docs/xml/conventions.xml
index ccc661086d..7334b02b8b 100644
--- a/docs/xml/conventions.xml
+++ b/docs/xml/conventions.xml
@@ -138,11 +138,9 @@
Code Example
-
-para
+ para
Beginning and end of paragraph
-para
-
+para
diff --git a/docs/xml/installation.xml b/docs/xml/installation.xml
index d9297ce47c..0433b4b520 100644
--- a/docs/xml/installation.xml
+++ b/docs/xml/installation.xml
@@ -1122,6 +1122,10 @@
non-English-speaking Bugzilla sites, I suggest changing
ISO-8859-1
, above, to
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.
@@ -1236,25 +1240,40 @@
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.
+
+
Win32 Installation: Step-by-step
@@ -2033,6 +2052,26 @@ binmode(STDOUT);
problems.
+
+ 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.
+
+
+
+
DBD::Sponge::db prepare failed
diff --git a/docs/xml/introduction.xml b/docs/xml/introduction.xml
index 88f9b26822..33907552b5 100644
--- a/docs/xml/introduction.xml
+++ b/docs/xml/introduction.xml
@@ -104,7 +104,10 @@
management, chip design and development problem tracking (both
pre-and-post fabrication), and software and hardware bug tracking for
luminaries such as Redhat, NASA, Linux-Mandrake, and VA Systems.
- Combined with systems such as CVS, Bonsai, or Perforce SCM, Bugzilla
+ Combined with systems such as
+ CVS,
+ Bonsai, or
+ Perforce SCM, Bugzilla
provides a powerful, easy-to-use solution to configuration management and
replication problems.
diff --git a/docs/xml/using.xml b/docs/xml/using.xml
index 74cca38255..a3986c27d2 100644
--- a/docs/xml/using.xml
+++ b/docs/xml/using.xml
@@ -8,7 +8,7 @@
This section contains information for end-users of Bugzilla.
There is a Bugzilla test installation, called
- Landfill,
+ Landfill,
which you are welcome to play with (if it's up.)
However, it does not necessarily
have all Bugzilla features enabled, and often runs cutting-edge versions
@@ -22,8 +22,8 @@
Consult with the administrator responsible for your installation of
Bugzilla for the URL you should use to access it. If you're
test-driving Bugzilla, use this URL:
-
- http://landfill.tequilarista.org/bugzilla-tip/
+
+ http://landfill.bugzilla.org/bugzilla-tip/
@@ -69,7 +69,7 @@
The core of Bugzilla is the screen which displays a particular
bug. It's a good place to explain some Bugzilla concepts.
+ url="http://landfill.bugzilla.org/bugzilla-tip/show_bug.cgi?id=1">
Bug 1 on Landfill
is a good example. Note that the labels for most fields are hyperlinks;
@@ -269,8 +269,8 @@
The Bugzilla Search page is is the interface where you can find
any bug report, comment, or patch currently in the Bugzilla system. You
can play with it here:
-
- landfill.tequilarista.org/bugzilla-tip/query.cgi
+
+ landfill.bugzilla.org/bugzilla-tip/query.cgi
.
@@ -282,7 +282,7 @@
Highly advanced querying is done using Boolean Charts, which have
their own
+ url="http://landfill.bugzilla.org/bugzilla-tip/booleanchart.html">
context-sensitive help
.
@@ -339,7 +339,7 @@
Years of bug writing experience has been distilled for your
reading pleasure into the
+ url="http://landfill.bugzilla.org/bugzilla-tip/bugwritinghelp.html">
Bug Writing Guidelines.
While some of the advice is Mozilla-specific, the basic principles of
reporting Reproducible, Specific bugs, isolating the Product you are
@@ -353,11 +353,11 @@
Go to
-
+
Landfill
in your browser and click
+ url="http://landfill.bugzilla.org/bugzilla-tip/enter_bug.cgi">
Enter a new bug report.
diff --git a/docs/xml/variants.xml b/docs/xml/variants.xml
index 2668acb355..73f6822fbd 100644
--- a/docs/xml/variants.xml
+++ b/docs/xml/variants.xml
@@ -13,9 +13,8 @@
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
@@ -49,7 +48,7 @@
Scarab
Scarab is a new open source bug-tracking system built using Java
- Serlet technology. It is currently at version 1.0 beta 7.
+ Serlet technology. It is currently at version 1.0 beta 8.
URL:
http://scarab.tigris.org