Redhat RPMs?

I’ve been trying to install RT3 on a RedHat 8.0 system and it’s just not
working out for me. I don’t know near enought what I should know for
something like this plus I keep getting derailed by other projects. Does
anybody have an RPM or quick install of all the parts so I can get this up
and running. RT2 or 3, RedHat 7.3, 8.0, or 9, I don’t much care (though I
would prefer RT3 on RH8 or 9).

Thanks much.

Clayton

Clayton Tavernier
IS Consultant
Kennerly-Spratling, Inc.
(510) 667-3795

I’ve been trying to install RT3 on a RedHat 8.0 system and it’s just not
working out for me. I don’t know near enought what I should know for
something like this plus I keep getting derailed by other projects. Does
anybody have an RPM or quick install of all the parts so I can get this up
and running. RT2 or 3, RedHat 7.3, 8.0, or 9, I don’t much care (though I
would prefer RT3 on RH8 or 9).

Clayton,

Funny you should ask. In the next week or two I’m going to build all the
necessary RPMs and instructions for RHL 8. The only real differences are
I’ll be doing it on/in a vserver - but this shouldn’t matter - and for
a PostgreSQL database located on another system - which probably will.

Rod
"Open Source Software - Sometimes you get more than you paid for…"

Funny you should ask. In the next week or two I’m going to build all the
necessary RPMs and instructions for RHL 8. The only real differences are
I’ll be doing it on/in a vserver - but this shouldn’t matter - and for
a PostgreSQL database located on another system - which probably will.

Rod

I just finished a by hand install on RH8. The things that took me a
while to get were:

a) all of the perl depends. This was a complete mess. Took me the
better part of a day to get everything installed an working.
WWW::Mechanize in particular did not install gracefully and I had to
hand install it (ignoring the failed make test).

Several of the perl modules from CPAN refused to install and I had to
fall back to the rpms from RH8.

Getting real RPMS for all of the perl depends would go a LONG way to
making rt easier to install, faster too.

b) I needed Active Directory support and I wanted apache2 so I went with
the absolute latest versions of apache and mod_perl. Everything seems
kosher but it took some doing.

I feel your pain. I did this once before (then lost the HD on that
server) so did it again for RT2. We want to go to RT3 and be able to
recover if the hardware should go south again. In fact we’re going to
have a standby waiting so there is very minimal down time.

I just finished a by hand install on RH8. The things that took me a
while to get were:

a) all of the perl depends. This was a complete mess. Took me the
better part of a day to get everything installed an working.
WWW::Mechanize in particular did not install gracefully and I had to
hand install it (ignoring the failed make test).

I’ll look at the fixdeps stuff and friends to determine what is needed
and try using cpan2rpm to build the RPMs.

Several of the perl modules from CPAN refused to install and I had to
fall back to the rpms from RH8.

Hum. I kind of noticed this but then found I was missing some local
utilities and once they were in place things worked ‘better’. We’ll see
if the gods smile brighter on me than you. :slight_smile:
I did discover that I needed psql (PostgreSQL command interface) to
build the remote database. I hope to overcome this issue if it hasn’t
already been done by using DBI for everything. Anyone in the know know if
the mysql command tool is used to build its database?

Getting real RPMS for all of the perl depends would go a LONG way to
making rt easier to install, faster too.

b) I needed Active Directory support and I wanted apache2 so I went with
the absolute latest versions of apache and mod_perl. Everything seems
kosher but it took some doing.

Mod_perl2 is working? Jesse and Robert mentioned at OSCON that some
people have had luck with Apache2 and mod_perl2 while others haven’t.

Rod
"Open Source Software - Sometimes you get more than you paid for…"

I feel your pain. I did this once before (then lost the HD on that
server) so did it again for RT2. We want to go to RT3 and be able to
recover if the hardware should go south again. In fact we’re going to
have a standby waiting so there is very minimal down time.

yeah, I have NO ability to recreate this server currently. That is my
next priority once it is in full use. Since we have zero hardware I
will have to experiment on a test machine and come up with a rapid
deployment scheme. Your work would go a long way to helping me there.
My cpan -> rpm experience is non-existant.

b) I needed Active Directory support and I wanted apache2 so I went with
the absolute latest versions of apache and mod_perl. Everything seems
kosher but it took some doing.

Mod_perl2 is working? Jesse and Robert mentioned at OSCON that some
people have had luck with Apache2 and mod_perl2 while others haven’t.

I have a server up and running with apache 2.0.46 (.47 came out the day
I got my setup working) and mod_perl2 0.99.09. Most of my problem was
learning the compile process not actual apache/mod_perl issues.

The one big snag was a change in globals handling, which was referenced
here earlier this week. You need the following in webmux.

require Apache::RequestUtil;
no warnings ‘redefine’;
my $sub = *Apache::request{CODE};
*Apache::request = sub {
my $r;
eval { $r = $sub->(‘Apache’); };
# warn $@ if $@;
return $r;
};

right after the BEGIN {} block. I am sure this will go away with the
next mod_perl release.

Admittedly, users are not pounding me yet, so maybe there are stability
problems I haven’t run into. This is the first RT setup here so we are
still testing things.

Users authenticate off of our Active Directory system beautifully with
the mod_ldap and mod_auth_ldap config.

This one time, at band camp, Sean Perry wrote:

a) all of the perl depends. This was a complete mess. Took me the
better part of a day to get everything installed an working.
WWW::Mechanize in particular did not install gracefully and I had to
hand install it (ignoring the failed make test).

Several of the perl modules from CPAN refused to install and I had to
fall back to the rpms from RH8.

Getting real RPMS for all of the perl depends would go a LONG way to
making rt easier to install, faster too.

b) I needed Active Directory support and I wanted apache2 so I went with
the absolute latest versions of apache and mod_perl. Everything seems
kosher but it took some doing.

I’ve been posting to -users over the last 3 months or so regarding
installing RT3 on RH8, there’s my apache configuration for apache2 and
modperl, and an apache configuration for apache2+mod_fastcgi in the
archives.

cpan2rpm (first hit on google) is a fantastic tool for using CPAN modules on
rpm based systems; the caveat with Red Hat 8 and CPAN is that, as you’ve
discovered, not everything will install without a ‘force’, there happen to
be some cyclic dependencies in some CPAN modules, and there are even cases
where the CPAN modules that come as part of the perl base RPM are broken or
out of date for RT3.

I chose the cpan2rpm path for my installation because I wanted to be able to
manage upgrades to the modules in the Red Hat way, keeping track of CPAN and
RPMs separately is too hard. I also need to be able to reproduce a
machine’s installation and installing pe-built packages is much faster than
building a module with each machine build.

There are no special instructions needed for installing RT on Red Hat
though, I’ve followed the install instructions for every install I’ve done.

jaq@spacepants.org http://spacepants.org/jaq.gpg

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jamie Wilkinson wrote:

cpan2rpm (first hit on google) is a fantastic tool for using CPAN modules on
rpm based systems; the caveat with Red Hat 8 and CPAN is that, as you’ve
discovered, not everything will install without a ‘force’, there happen to
be some cyclic dependencies in some CPAN modules, and there are even cases
where the CPAN modules that come as part of the perl base RPM are broken or
out of date for RT3.

I chose the cpan2rpm path for my installation because I wanted to be able to
manage upgrades to the modules in the Red Hat way, keeping track of CPAN and
RPMs separately is too hard. I also need to be able to reproduce a
machine’s installation and installing pe-built packages is much faster than
building a module with each machine build.

Just an FYI, most of the ones that you need to “replace” (that also come
with perl on redhat) you can usually take care of with cpan2rpm by doing:

cpan2rpm --shadow-pure

That will make it not try to replace the existing version, it will just
override it. Then you don’t have to install with --force. Between

  • –shadow-pure and --make-no-test, you should be able to install all of
    RT’s dependencies without forcing things on the RPM database, I believe.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/D3bfUu+jZtP2Zf4RAkD9AJ93kXXR3yVNLM4RBP5CVg76ZZ3jggCeJizr
lcd2w0Y+zC7dvXYdfVgYIJk=
=EehM
-----END PGP SIGNATURE-----