Hi Nima,
Upgrade was realized following five steps found in https://openacs.org/doc/openacs-5-1/upgrade-5-0-dot.html, section "Upgrading a Custom or CVS site".
Step 1:
followed instructions found in https://openacs.org/doc/openacs-5-1/upgrade-openacs-files.html, section "Upgrading files for a site in a private CVS repository"
I just used oacs-5-1 tag for upgrade instead openacs-5-1-compat.
We have just little design an tcl code changes in our original dotlrn-2-0-3 install. There were not changes in data model. In Merging New OpenACS code we had no conflicts.
Step 2:
Before go into step 2 with our new merged code we needed to backup acs-authentication (merged) and checkout acs-authentication from our old custom code in cvs:
In new merged code tree (upgraded system):
mv service0/package/acs-authentication service0/package/acs-authentication.new
then checkout your old acs-authentication package into new merged code tree. This step is important or you will not get login in your upgraded system.
Ok. Start you upgraded service with your original database (our old database was running postgresql-7.3.4. A dump was generate and inserted in postgresql-7-4-5). After start:
- Login in,
- change acs-authentication:
mv service0/package/acs-authentication service0/package/acs-authentication.old
mv service0/package/acs-authentication.new service0/package/acs-authentication
- realize step 2 in docs (upgrade via apm from local).
Step 3/Step 4/ Step 5: realized as is.
Nima, the upgraded system is in testing. People will navigate this week and see everything works. The upgrade was realized last weekend untill now there were no problems.
