Package: bugzilla3
Severity: normal
Tags: patch
Please find attached changes to the README.Debian file for the bugzilla3
package.
Feel free to apply them using the GPL if this patch appears suitable.
Regards,
Jeremiah
-- System Information:
Debian Release: 5.0.4
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- README.Debian 2010-02-02 15:36:31.000000000 +0100
+++ README.Debian.bugzilla 2010-02-02 15:45:43.000000000 +0100
@@ -4,34 +4,36 @@
Customisation
------------------------------------------------------------------------------
- The /etc/bugzilla3/pre-checksetup.d and post-checksetup.d directories will be
- executed by /usr/share/bugzilla3/lib/checksetup.pl script:
+ The /etc/bugzilla3/pre-checksetup.d and post-checksetup.d directories hold
+ scritps which will be executed by /usr/share/bugzilla3/lib/checksetup.pl:
+
# run-parts --verbose --exit-on-error --lsbsysinit <dir>
+
Put your own scripts into this directory.
- You have also the possiblity to use your own template and skin directories.
- Use the /etc/bugzilla3/template and /etc/bugzilla3/sinks directory for that.
- The content will by copied 1:1 to the corresponding directories by default
- /etc/bugzilla3/pre-checksetup.d scripts.
+ You can use your own templates and skins; put them in
/etc/bugzilla3/template
+ and /etc/bugzilla3/skins. This content gets copied to the corresponding
+ directories by the /etc/bugzilla3/pre-checksetup.d scripts.
User/Group and mode of files and directories are managed with
dpkg-statoverride.
- At installation time defaults are used. If you intent to change them please
- use
+ If you intend to change the default values please use
+
# dpkg-statoverride --update --add root root 0640 /etc/bugzill3/localconfig
- The is something sepecial should be mentioned at this place. To manage
- template files you have only to dpkg-statoverride the
/var/lib/bugzilla3/template
- directory and /var/lib/bugzilla3/template/en/default/index.html.tmpl file.
+ For template files, you'll only have to use 'dpkg-stateoverride' on the
+ /var/lib/bugzilla3/template directory and the
+ /var/lib/bugzilla3/template/en/default/index.html.tmpl file.
+
This information will be used to set the user/group and mode of all
directories
- and files recursive within the
+ and files recursively within the
- /var/lib/bugzilla3/template
- /var/lib/bugzilla3/data/template
directories.
Check the /etc/bugzilla3/post-checksetup.d/15restoredpkgstatoverride script
for
more implementation details.
- The reason why we are doing it this way is speed because dpkg-statoverride
- is really slow to manage as many files as the directory contains. I hope this
- is not annoying you. Otherwise reprot a bug with an idear how to process
this ;-)
+ The reason why we do it this way is speed, 'dpkg-statoverride' is really
slow.
+ I hope this is not annoying to you. Otherwise reprot a bug with a
suggestions
+ on how to improve the situation. ;-)
About GraphViz and dependency graphs ("webdotbase")
------------------------------------------------------------------------------
@@ -43,19 +45,19 @@
About the "urlbase" setting
------------------------------------------------------------------------------
- Whe bugzilla is installed for the first time, you have to edit the conffile
+ When bugzilla is installed for the first time, you have to edit the conffile
/etc/bugzilla3/params and change the value of urlbase to something that makes
sense according to your installation. For instance, you can set it to
'/bugzilla3/' if you don't use VirtualHosts.
That parameter will be used by Bugzilla for building links in a lot of
places,
- so take care to its value.
+ so take care to assign it a correct value.
About /usr/share/bugzilla3/lib/email_in.pl (Debian Bug #528780, #549700)
------------------------------------------------------------------------------
- To use this software you the libemail-reply-perl and
- libemail-mime-attachment-stripper-perl packages are required but
- not existing for Debian. To resolve this depenceny please go throug the next
- steps within your shell:
+ To use this software you need the libemail-reply-perl and
+ libemail-mime-attachment-stripper-perl packages. They don't yet exist in
+ Debian. To resolve this depenceny please follow these steps:
+
$ sudo apt-get install dh-make-perl
$ mkdir tmp
$ cd tmp
@@ -63,9 +65,9 @@
$ sudo dpkg -i ~/.cpan/build/libemail-reply-perl_*.deb
$ dh-make-perl --build --cpan Email::Mime::Attachment::Stripper
$ sudo dpkg -i ~/.cpan/build/libemail-mime-attachment-stripper-perl_*.deb
-
- As long the libemail-reply-perl and libemail-mime-attachment-stripper-perl
- packages are not official this steps are mandatory to be done.
+
+ Until these two packages are officially in debian, this is the way to install
+ them.
Install further packages to get email_in.pl working:
$ sudo apt-get install libemail-mime-creator-perl libemail-date-format-perl
@@ -77,10 +79,10 @@
------------------------------------------------------------------------------
Installation of outstanding packages is not supported right now. Please
refer to Suggested and Recommended packages (dpkg --status bugzilla3) to
- get an overview about packages Perl modules.
+ get information on other needed perl modules.
- Use dh-make-perl (application and package name) to install non-packages
- Perl modules like described in the previous section.
+ You can use dh-make-perl (application and package name) to install needed
+ Perl modules as described in the previous section.
How to set several VirtualHosts with this package
------------------------------------------------------------------------------
@@ -94,20 +96,18 @@
# a2enmod env
- Then, you have to prepare a configuration directory for your virtual
- host. The simpliest way is to copy the one the package created:
+ Then prepare a configuration directory for your virtual host. The simpliest
+ way is to copy the one the package created:
`/etc/bugzilla3'.
Name this new configuration directory like that:
`/etc/bugzilla3/sites/host' where `host' is the name of your virtual host.
- You have now to add a virtual host section in your Apache configuraiton
file.
- This can be achieved in different ways, depending on the kind of VirtualHost
- you want.
-
- This package comes with two virtual host examples, located under
+ Add a virtual host section in your Apache configuraiton file.
+ This can be done in different ways, depending on the kind of VirtualHost
+ you want. This package comes with two virtual host examples, located under
`/usr/share/doc/bugzilla3/examples/'.
- If you want a vritualhost that uses the same static files as the orginal
+ If you want a virtualhost that uses the same static files as the orginal
package, just use the example: `vh-basic.conf'.
If you'd rather have different static files for the virtual host, you can
@@ -120,8 +120,10 @@
- X_BUGZILLA_WEBPATH wich is the prefix to prepend to every static files in
the templates.
- When you are ok with the apache configuration, you can restart it and
- test your virtual host.
+ When you are okay with the apache configuration, you can restart it and
+ test your virtual host;
+
+ # apache2ctl graceful
If you want to have specific templates for a given virtual host, that's also
possible, just copy `/var/lib/bugzilla3/template' to
@@ -130,7 +132,7 @@
At this time, you can set a different database for each virtual host,
customize templates for another or even share the same database... Everything
- is possible with few effort.
+ is possible with a little effort.
Even though each bugzilla site will be updated with checksetup.pl, the params
file won't be updated. The only params file that is updated during the
@@ -139,4 +141,3 @@
Thanks to Yann Dirson for the mod_env idea.
-- Raphael Bossek <boss...@debian.org> Mon, 05 May 2008 13:07:36 +0200
-
