Topic: Bugzilla on SME 6.0

[Michiel]

Hi,
Has anyone succesfully installed bugzilla on SME 6.0? If so, would you mind sharing the required packages and your notes?
thanks,
Michiel

[Knuddi]

I am also very interested in knowing this. So far I run it on a CentOS 3 server but I would much rather run on the SME. It properly can be done if you install all the development tools and install from scratch including a ton of Perl updates.

Anyone?

[Knuddi]

Michiel,

I have now installed BZ on a SME 6.0.1 server and I installed a few dev. tools to be able to do it. These were needed only to get and update a ton of Perl modules. I am not sure whether they are all nessesary (I am quite sure not) but it was easy . These are all found on http://mirror.contribs.org/smeserver/contribs/hpe/devtools-6.01/dev-rpms/

autoconf-2.13-17.noarch.rpm
automake-1.4p5-4.noarch.rpm
bison-1.35-1.i386.rpm
cpp-2.96-113.i386.rpm
gcc-2.96-113.i386.rpm
gcc-c++-2.96-113.i386.rpm
gettext-0.11.1-2.i386.rpm
glibc-devel-2.2.5-44.i386.rpm
glibc-kernheaders-2.4-7.16.i386.rpm
kernel-source-2.4.20-18.7.i386.rpm
libacl-2.0.11-7.i386.rpm
libacl-devel-2.0.11-7.i386.rpm
libattr-2.0.8-6.i386.rpm
libstdc++-devel-2.96-113.i386.rpm
m4-1.4.1-7.i386.rpm
mkisofs-1.10-11.i386.rpm
ncurses-devel-5.2-26.i386.rpm
readline-devel-4.2a-4.i386.rpm

Next I updated the CPAN base.
# perl -MCPAN -e 'install Bundle::CPAN'

Then I took all the Perl modules one by one as indicated by Bugzilla installation guide.

Create a ibay called bugzilla and untar'ed a BZ tar file into cgi-bin. Ran ./checksetup.pl to verify all modules were there and create a basis installation. My installation is a little tricky as my mySQL database is on another server.

These are the basics I think.

Enjoy,
Jesper

[gordonr]

Next I updated the CPAN base.
# perl -MCPAN -e 'install Bundle::CPAN'

Then I took all the Perl modules one by one as indicated by Bugzilla installation guide.

A much better way is to use 'cpan2rpm' to generate RPMs from all of the Perl modules. CPAN is great for development, but (IMO) is not the way to install perl modules on production systems as those modules won't get updated during system upgrades.

I am interested in doing a Bugzilla install, but on SME7 rather than 6. I expect most of the Perl modules will already exist. This is probably also true for 6 - have a look on www.atrpms.net and www.freshrpms.net, for the "Fedora Legacy" or RH7 builds.

This set of RPMs might be a good start (for 6.x):

http://mirror.contribs.org/smeserver/contribs/gordonr/bugzilla/rpms/RPMS/i386/

You'll need to --force install perl-PathTools as it conflicts with the perl-5.6.1 RPM and the perl-5.6.1 RPM has an @INC path which is backwards

[gordonr]

NOTE: You must protect the Bugzilla files. Here's an httpd.conf fragment which does:

Code: [Select]


Alias   /bugzilla  /home/httpd/html/bugzilla-2.20

<Directory /home/httpd/html/bugzilla-2.20>
    Options +Indexes +ExecCGI
    DirectoryIndex index.cgi
    AllowOverride Limit
    order deny,allow
    allow from all

    <FilesMatch ^(.*\.pl|.*localconfig.*)$>
      order deny,allow
      deny from all
    </FilesMatch>
    <FilesMatch ^(localconfig.js|localconfig.rdf)$>
      order deny,allow
      allow from all
    </FilesMatch>
</Directory>


[Knuddi]

gordonr,

Love cpan2rpm - didn't know it existed

I agree with the httpd.conf but this is easier said than done with the SME server that creates these automatically. Do you have a template to wrap this in?

[gordonr]

gordonr,

Love cpan2rpm - didn't know it existed

A wonderful tool.

I agree with the httpd.conf but this is easier said than done with the SME server that creates these automatically. Do you have a template to wrap this in?

I just put that in /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/99bugzilla, expanded /etc/httpd.conf and restarted httpd-e-smith.

[Knuddi]

Sure that it could be done this way - but this will create two Directory sections for BZ.

I get these errors in my /var/log/httpd/error_log files that I have problems getting rid of.

[Fri Nov  4 06:32:13 2005] [error] (13)Permission denied: exec of /home/e-smith/files/ibays/bugzilla/cgi-bin/skins/standard/global.css failed
[Fri Nov  4 06:32:13 2005] [error] [client 192.168.100.100] Premature end of script headers: /home/e-smith/files/ibays/bugzilla/cgi-bin/skins/standard/global.css
[Fri Nov  4 06:32:13 2005] [error] (13)Permission denied: exec of /home/e-smith/files/ibays/bugzilla/cgi-bin/skins/custom/global.css failed
[Fri Nov  4 06:32:13 2005] [error] [client 192.168.100.100] Premature end of script headers: /home/e-smith/files/ibays/bugzilla/cgi-bin/skins/custom/global.css

This also means that I do not get the Ant and other graphics in my browser. Do you get the same?

All the rest works as expected.

[gordonr]

Sure that it could be done this way - but this will create two Directory sections for BZ.

I don't see why. I only have one.

I get these errors in my /var/log/httpd/error_log files that I have problems getting rid of.
[...]
This also means that I do not get the Ant and other graphics in my browser. Do you get the same?

All the rest works as expected.

No - I get the Ant and other graphics.

See here:

http://bugs.contribs.org/

Sounds like a permissions problem to me.

[Knuddi]

Now I see. I am trying to install in an Ibays (the SME way) and you have "just" placed BZ in a dir and created the httpd section yourself. That's also why you do not have multiple sections in your expanded httpd.conf file.

Have you tried to install in an ibays?

[gordonr]

Now I see. I am trying to install in an Ibays (the SME way)

This is a very common misconception. I-bays are information storage areas, shared between Samba, Appletalk, FTP and the web. They were not designed for web applications, which have their own security and storage requirements.

The Bugzilla code should be stored somewhere safe and installed by an RPM. It doesn't need/want to be in an i-bay. The Bugzilla data is in MySQL.

and you have "just" placed BZ in a dir and created the httpd section yourself. That's also why you do not have multiple sections in your expanded httpd.conf file.

This is what we did with IMP/Webmail and it is "The Right Way To Do It"[TM]

Have you tried to install in an ibays?

No. There's no need, and it's much better not to.

[Jáder]

Gordon

I´m glad to know the right way... I allways used to install web applications (awstats, helpdesk, cms, ...) on ibays.
And I think several rpms to SME do not use your approach and install on ibays.

I think this information should be wide spread (a HowTo,   a fixed link on forums, ... ) so people start to use the right way.

What do you think about ?

Thanks

Jáder

[wellsi]

As a start I have copied the information into the wiki:

http://no.longer.valid/phpwiki/index.php/Web%20Applications%20Guidelines

which is linked from

http://no.longer.valid/phpwiki/index.php/Development

This information should be re-worked later, but at least it won't be lost.

[pfloor]

NOTE: You must protect the Bugzilla files. Here's an httpd.conf fragment which does:

Code: [Select]


Alias   /bugzilla  /home/httpd/html/bugzilla-2.20

<Directory /home/httpd/html/bugzilla-2.20>
    Options +Indexes +ExecCGI
    DirectoryIndex index.cgi
    AllowOverride Limit
    order deny,allow
    allow from all

    <FilesMatch ^(.*\.pl|.*localconfig.*)$>
      order deny,allow
      deny from all
    </FilesMatch>
    <FilesMatch ^(localconfig.js|localconfig.rdf)$>
      order deny,allow
      allow from all
    </FilesMatch>
</Directory>


Gordon, is there any way to make the alias specific to only one domain?

Paul

[gordonr]

Gordon, is there any way to make the alias specific to only one domain?

Yes. You'd need to create this fragment in a file in /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/VirtualHosts
and only generate the output in a given virtual host.