Open dalehenrich opened 5 years ago
This issue is recorded by internal bug 48168 - Recent Metacello update introduced a bug in 3.2.x upgrade to 3.5.0
If there is a need to upgrade from 3.2.x or before to 3.5.0, then you need to checkout the issue_504_patch tag before you do the upgrade (using $GS_HOME/bin/upgradeStone). After you have upgraded, checkout the latest master branch and load that into your upgraded stone ...
With a recent merge, I inadvertently overwrote the "year old change" ... need to revert this if it is safe...
This year old change has broken GemStone upgrades from 3.2.x to 3.5.0. I have recently patched GLASS, but I won't be patch the upgrade process itself until we release 3.5.1, so this bug is memorializing the fact that I intend to patch metacello-work to allow upgrades to function again and will remove the patch once 3.5.1 is released ...
I'm not sure how this recent build and earlier builds were passing for GemStone all this time, but it has surfaced has an issue and it needs to be addressed