Automatic upgrade scripts stopped at 4.8.1, when run again starts at 4.6.0

(Nic Hubbard) #1

We just downloaded the new upgrade scripts for 4.12.0. Currently we are on 4.6.0 and started the upgrade this morning.


Things went well until we got to 4.8.1 and then we got some strange CVS error: "CVS password file /root/.cvspass does not exist" (we saw this error when starting, but re-running the script didn't show it again). Because it failed, we ran the script again, but now the upgrade script seems to think that our system is still on 4.6.0, which it is not.



Why are the upgrade scripts wanting to start again at 4.6.0? We are sort of stuck because we do NOT want to have to run all of the same steps over again as it seems it could screw some things up. Is there a way to get the script to realize what version we are really on?

(Edison Wang) #2

The upgrade script uses CVS linux command to update the code from Squiz's public CVS repository by default. That error seems to be coming out of the CVS command. It has to be fixed before running the upgrade script. I think you might get that error if you just type the cvs command to update code on the server.


The script normally just look at the version file (core/include/version.inc) for the current version of system. If you have CVS successfully updated your code, the version should be updated there already.



There is also a progress file used by autoupgrade script in the script's directory (tmp/.current_progress.php). Sometime if the uprgade is failed in the half way when running steps between 2 versions, but you don't want to resume to the sepcifc step. You can just delete that progress file. In which case, the upgrade script will look at the version.inc file, determine upgrade path, and start fresh.

(Nic Hubbard) #3

[quote]
The script normally just look at the version file (core/include/version.inc) for the current version of system. If you have CVS successfully updated your code, the version should be updated there already.



There is also a progress file used by autoupgrade script in the script's directory (tmp/.current_progress.php). Sometime if the uprgade is failed in the half way when running steps between 2 versions, but you don't want to resume to the sepcifc step. You can just delete that progress file. In which case, the upgrade script will look at the version.inc file, determine upgrade path, and start fresh.

[/quote]



Thanks, I will see if this fixes the issue.