GemStone upgrades from 3.2.x to 3.5.0 are broken by year old change #504
Assignees
Labels
Comments
|
This issue is recorded by internal bug |
dalehenrich
added a commit
to dalehenrich/metacello-work
that referenced
this issue
Jun 20, 2019
…tory class >> projectDirectoryFrom:version:
dalehenrich
added a commit
to GsDevKit/GsDevKit_home
that referenced
this issue
Jun 21, 2019
…ing; Metacello/metacello#504 patch is working; restore the full lineup
|
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 ... |
dalehenrich
added a commit
to dalehenrich/metacello-work
that referenced
this issue
Sep 25, 2019
…tworkRepository>>projectDirectoryFrom:version: ... defer merging issue_504 branch until 3.5.1 has been released to avoid causing upgrade failures to show up in GsDevKit_home travis tests
4 tasks
|
With a recent merge, I inadvertently overwrote the "year old change" ... need to revert this if it is safe... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
The text was updated successfully, but these errors were encountered: