This is interesting, but the critical information that is still missing is what version of GemStone are you starting your upgrade with and what version of GLASS do you have loaded in the image BEFORE starting the upgrade:

1. What version of GemStone are you using in your `update_test` stone?
2. Please provide a complete list of the SHAs for all of the projects that you have loaded in the stone that you are upgrading from .... a snapshot of the tODE project list is the best ... presumably you have tODE loaded in your stone, so if you aren't prepared to connect using a tODE client, I can supply you with a doit that you can run to get the same information from either topaz (if you don't have tODE installed) or tODE (via the todeIt script)

If I had both of these pieces of information, I would have a very good chance of being able to reproduce your problem and be on my way to providing a solution ...

Dale

And the reasons for that are, that ConfigurationOfGofer is dkh.39 (which references gemstone.com) and NOT dkh.45 (which references seaside.gemtalksystems.com). Now th question is, WHY is not a newer version of Gofer loaded ...

Marten

Marten Feldtmann via Glass [hidden email] hat am 5. Januar 2020 um 22:54 geschrieben:

I have found  referencse to gemstone.com in the new updated 3.5.1 database:

ConfigurationOfGoferProjectLoader class>postLoadGSDoIt10alpha21

ConfigurationOfGofer class>>baseline100:, baseline1021:,baseline1051:

_______________________________________________ Glass mailing list [hidden email] https://lists.gemtalksystems.com/mailman/listinfo/glass