Error running perl etc/upgrade/vulnerable-passwords with existing RT installation

RT Users
1

I have an installation of 3.8.8 on a test machine that we’re trying to
upgrade to RT 4.0.0

If I run configure with --prefix=/opt/rt3 to match the current installation
of RT, running perl etc/upgrade/vulnerable-passwords returns:

Can’t locate object method “new” via package “RT::CurrentUser” at lib/RT.pm
line 481.

Running configure without that switch does not cause this issue. Moving
/opt/rt3 to /opt/rt4 and running configure without the switch DOES cause
the issue to occur.

Am I doing something wrong in the upgrade process? Should I just skip this
step?

Thanks for the info.

Jonah Hirsch

2

Doing an incremental upgrade to 4.0.0 fixed this issue.
Jonah HirschOn Fri, Apr 29, 2011 at 3:00 PM, Jonah Hirsch jwh83@nau.edu wrote:

I have an installation of 3.8.8 on a test machine that we’re trying to
upgrade to RT 4.0.0

If I run configure with --prefix=/opt/rt3 to match the current installation
of RT, running perl etc/upgrade/vulnerable-passwords returns:

Can’t locate object method “new” via package “RT::CurrentUser” at lib/RT.pm
line 481.

Running configure without that switch does not cause this issue. Moving
/opt/rt3 to /opt/rt4 and running configure without the switch DOES cause
the issue to occur.

Am I doing something wrong in the upgrade process? Should I just skip this
step?

Thanks for the info.

Jonah Hirsch

3

I have an installation of 3.8.8 on a test machine that we’re trying to upgrade to RT 4.0.0
If I run configure with --prefix=/opt/rt3 to match the current installation of RT, running
perl etc/upgrade/vulnerable-passwords returns:

Did you read docs/UPGRADING-4.0 for the litany of problems that will
occur if you do that?

Why are you trying to keep the rt3 code around and what part of the
documentation can I change to make it clear that you really shouldn’t
do that?

Just make install cleanly into /opt/rt4 and run the database upgrades

-kevin