I'm attempting to install RequestTracker on CentOS 6.5. Running "make testdeps" as recommended by RT's installation guide, I'm presented with lists of missing Perl modules.
One of these lines reads:
Encode >= 2.39 ...MISSING
Now, "yum whatprovides '*/Encode.pm' " informs me that that module is part of the core Perl distribution, and is installed on my system. Opening the file itself reveals:
# $Id: Encode.pm,v 2.35 2009/07/13 00:49:38 dankogai Exp $
so I know that I have version 2.35 of that module installed, and obviously that's < 2.39. So I need to get 2.39 installed.
What is the correct way to do this on CentOS? The last time I had to do anything like this, it was on a Debian box, I went through the process recommended by the guys in #perl, and was left with a broken system that was a real joy to piece back together...
Am 04.02.2014 um 22:49 schrieb Michael Mol mikemol@gmail.com:
I'm attempting to install RequestTracker on CentOS 6.5. Running "make testdeps" as recommended by RT's installation guide, I'm presented with lists of missing Perl modules.
One of these lines reads:
Encode >= 2.39 ...MISSINGNow, "yum whatprovides '*/Encode.pm' " informs me that that module is part of the core Perl distribution, and is installed on my system. Opening the file itself reveals:
# $Id: Encode.pm,v 2.35 2009/07/13 00:49:38 dankogai Exp $
so I know that I have version 2.35 of that module installed, and obviously that's < 2.39. So I need to get 2.39 installed.
What is the correct way to do this on CentOS? The last time I had to do anything like this, it was on a Debian box, I went through the process recommended by the guys in #perl, and was left with a broken system that was a real joy to piece back together…
I’m not sure about CentOS. This guide: http://binarynature.blogspot.pt/2013/05/install-request-tracker-4.html
suggest installing all the modules via CPAN (onto the original installation).
I don’t believe this is going to work very well, once it touches modules already part of the initial installation (as in your case).
Historically, you were best off with installing a perl from source into a different directory and using RT’s installer to fix all the dependencies.
You can then update these modules as needed or required by security-issues / RT updates/upgrades, without interfering with the base OS update mechanism.
If you choose this route, I would suggest using the NGINX+fast-cgi implementation, as you don’t have to worry about the mod_perl from base etc.
Admittedly, this reduces CentOS to little more than a kernel+filesystem+sshd - but unless you find a repository that provides all the modules (well over a hundred last time I counted, significantly more if you enable all the optional dependencies) in all the right versions, all of the time, you will have a hell of a problem keeping RT running smoothly.
I have no experience with Debian/Ubuntu, but I’d really only use packages in case I could package them up myself, specifically for this task.
Well, it seems you have to install RT manually on CentOS 6 [1].
On 02/05/2014 12:33 AM, Rainer Duffner wrote:
I have no experience with Debian/Ubuntu, but I’d really only use packages in case I could package them up myself, specifically for this task.
For Debian, there are packages readily available, which get updated automatically. I had not any problems with dependencies. You don't have to do anything. Sorry, to say this on this list, but this is a task I would choose Debian for [2].
[1] http://howtoconfigure.blogspot.pt/2013/05/how-to-install-request-tracker-40x... [2] http://packages.debian.org/de/wheezy/request-tracker4
Am Wed, 05 Feb 2014 06:23:25 +0100 schrieb Chris ch2009@arcor.de:
Well, it seems you have to install RT manually on CentOS 6 [1].
On 02/05/2014 12:33 AM, Rainer Duffner wrote:
I have no experience with Debian/Ubuntu, but I’d really only use packages in case I could package them up myself, specifically for this task.
For Debian, there are packages readily available, which get updated automatically.
Well, there are also packages for FreeBSD. RT and all dependencies.
I had not any problems with dependencies. You don't have to do anything. Sorry, to say this on this list, but this is a task I would choose Debian for [2].
The reason I wouldn't just blindly install or update packages is that I don't believe that even the Debian guys do sufficient testing to ensure that RT actually works after the update.
This is, of course, a highly RT-specific discussion. But in defense of CentOS, I don't see a fundamental problem running RT on it - actually, due to the long support-cycles, it might even be better suited than e.g. Ubuntu LTS. Ticketing-Systems usually have exceptionally long replacement-cycles. You just have to make sure you know what you are doing and find a usable change-management strategy.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 02/04/2014 03:49 PM, Michael Mol wrote:
Use Software Collections. There's a newer perl inside software collections, that contains a newer version of Encode for this and will meet your dependencies. There still isn't an rpm based installer for RT, but you'll be able to do things in a 'more correct' way than overwriting the system perl via cpan bundle updates.
- -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77
On Wed, Feb 5, 2014 at 10:50 AM, Jim Perrin jperrin@centos.org wrote:
Use Software Collections. There's a newer perl inside software collections, that contains a newer version of Encode for this and will meet your dependencies. There still isn't an rpm based installer for RT, but you'll be able to do things in a 'more correct' way than overwriting the system perl via cpan bundle updates.
Is there an overview of how software collections work somewhere? That is, how a user interacts with a choice of versions of the same thing?
On 02/05/2014 04:43 PM, Les Mikesell wrote:
On Wed, Feb 5, 2014 at 10:50 AM, Jim Perrin jperrin@centos.org wrote:
Use Software Collections. There's a newer perl inside software collections, that contains a newer version of Encode for this and will meet your dependencies. There still isn't an rpm based installer for RT, but you'll be able to do things in a 'more correct' way than overwriting the system perl via cpan bundle updates.
Is there an overview of how software collections work somewhere? That is, how a user interacts with a choice of versions of the same thing?
Yes, see this link:
https://access.redhat.com/site/documentation/en-US/Red_Hat_Software_Collecti...
Obviously, any mention of RHN and subscriptions should be ignored and instead the setup to get software collections is:
yum install centos-release-SCL
Once the release package is installed, all the "yum install" directions in the documentation will work fine.
(so that means my command above replaces Section 2.1 in the documentation, but the rest of the documentation is going to work correctly)
-
Always Learning -
Chris -
Jim Perrin -
Johnny Hughes -
Les Mikesell -
Michael Mol -
Rainer Duffner