[rt-users] RT upgrade failing!

[Chuck Mead]

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

Has anybody ever successfully upgraded an RT installation acrosse
multiple versions?

I have a failing hard drive on the machine that is running our current
RT installation. I have new hardware on which I am trying to get it
installed. Our old installation is running on FC1. Because our new
machine has SATA drives I need a much newer kernel for this hardware. My
problem is that the RT upgrade path appears to be broken. My original
version is RT 3.0.7_01 and that version requires sperl which is not
required under the new version (3.4.2). As you may know, unless I want
to do a customized perl build on rhel4 there is no sperl. So when I try
to upgrade from 3.0.7_01 to 3.4.2 it wants me to do a series of database
upgrades involving the schemas, acls, and some data inserts.
Theoretically these updates should move my existing database from
version 3.0.7_01 to 3.1.0  to 3.1.15 to 3.1.17 to 3.3.0 to 3.3.11 which
is where it seems to stop.

This all breaks down pretty early though because at 3.1.15 there is no
upgrade schema for postgres and no ACL's update either. The bottom line
here is that it seems there is *NO* viable upgrade path to get from
3.0.7_01 to 3.4.2.

Does anybody have any clues for me?

- --
Chuck Mead <csm at redhat.com>
Instructor II (and resident Postfix bigot), GLS
Disclaimer: "It's Thursday and my name is Locutus of B0rk!"
Addendum: "Bwahahaha! Fire up the orbital mind-control lasers!"

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

iD8DBQFCk5SjZfy0juH51WsRAgssAJ0WAeaAbzaa78iFex8CQtrlz16MQACbBZWM
NeA0ykJv2LgF0vekbmpnZA0=
=+0+c
-----END PGP SIGNATURE-----