I don't understand people's desire to use 3rd party RT packages. You're
then at the mercy of the packager, and it makes it harder to fix
problems and apply upgrades when new RT releases come out.
It's better to learn the internals of RT and deal with its
idiosyncrasies than to use a package you find somewhere. They're almost
always extremely outdated, and require quite a bit of configuration. My
RT setup has enough customizations that I keep track of separately that
fighting with someone's RPM package would end up costing me far more
time that it'd save.
Don't get me wrong, I'd *LOVE* *LOVE* *LOVE it if Best Practical
official had RPMs available and would use them in a heartbeat, it would
make my life easier, and make me a happier person as well as make RT
easier to maintain, but 3rd party RPMs are annoying. Don't use them,
just install RT per the instructions.
3.8 is such an improvement over 3.6 if anyone made me go back I'd be
very cranky about it.
On 12/13/10 10:06 AM, Jacob Ritorto wrote:
RedHat is god, ftw!
On 12/13/10 10:59, Kevin Falcone wrote:
On Mon, Dec 13, 2010 at 01:50:44PM +0000, Khusro Jaleel wrote:
I am thinking of migrating an RT instance from a machine running RT
3.8.1 to a machine running 3.6, but I'm not sure if this is even
possible? Is it possible to move the MySQL DBs straight across from
3.8 to 3.6 without any issues? If there are any tweaks to be done,
are they major?
There are some pretty major schema differences, in particular
encodings. I can't recommend against this enough.
I am trying to use a Redhat machine which only has the official EPEL
RT packages which are currently only at 3.6.
If I can't move the DBs across, is there perhaps a way I can perform
a default install on 3.6, then export / import the old (3.8) data
in?
Not really
-kevin
--
John Arends
jare...@illinois.edu
Network Analyst
College of ACES ITCS
University of Illinois at Urbana-Champaign
