Bug 44286

GemStone/S 64 Bit

3.2, 3.1.0.6, 3.1.0.5, 3.1.0.4, 3.1.0.3, 3.1.0.2, 3.1.0.1, 3.1

3.2.1

Seaside upgrade creates package-cache directory in current directory

When upgrading a seaside application, the upgrade process attempts to create the package-cache directory in the current working directory.  This will error if the current directory is not writable.

Workaround

The fix is to modify the upgrade code to set the cache repository before starting the upgrade.  The following modification can be made to $GEMSTONE/upgrade/upgradeSeasideImage.topaz, starting around line 237.

The code should look like this:

! Set the cache repository
run
MCCacheRepository setDefault: MCDictionaryRepository new.
true

%

! explicitly load each of the configuration packages listed in BootstrapApplicationLoadSpecs
!
run
BootstrapApplicationLoadSpecs do: [:loadSpec |
    Gofer new
        directory: (ServerFileDirectory on: (loadSpec at: 4));
        package: (loadSpec at: 1);
        load.
].
true
%


Last updated: 5/28/14