fix: start_to_to.sh for backwards compat

[turadg]

#88 broke the tacit API of what files are in the Docker images available to downstream builds.

The downstream should be copying its own dependencies into the filesystem so that they aren't coupled to the @agoric/synthetic-chain used to produce the upstream images.

That's apparently not the case for some branch in agoric-sdk so this is a stop-gap until further investigation.

[mhofman]

#88 broke the tacit API of what files are in the Docker images available to downstream builds.

The downstream should be copying its own dependencies into the filesystem so that they aren't coupled to the @agoric/synthetic-chain used to produce the upstream images.

That's apparently not the case for some branch in agoric-sdk so this is a stop-gap until further investigation.

agoric-sdk does nothing special but using version 0.0.4-3 of synthetic-chain. The problem I think is that synthetic-chain is expecting some files to be in the target image when preparing an upgrade?

Anyway, I triggered a manual workflow of this branch, which should build the use-* image. Once this completes, I'll re-run the failed agoric-sdk integration test, validating is this fix works, at which point I'll approve.

[turadg]

The problem I think is that synthetic-chain is expecting some files to be in the target image when preparing an upgrade?

Yes, the version of synthetic-chain in that branch. I'm not saying it's a bug in agoric-sdk, just that the behavior in that branch is expecting a file it shouldn't. It worked (until it didn't) but it wasn't meant to.

Once this completes, I'll re-run the failed agoric-sdk integration test, validating is this fix works, at which point I'll approve.

Good plan. Feel free to merge as well.

[mhofman]

agoric-sdk test re-run passed.