SqueakSSL plugin doesn't work on Ubuntu 24.04

[theseion]

@fniephaus The reason that some of the Squeak builds fail is that the SqueakSSL plugin doesn't work. I haven't spent the time to look into it in detail, so I don't know why exactly. It's the #primitiveSSLCreate that fails (module loading works).
I suspect that the issue lies with a dependency version, e.g., openssl, since the Squeak 6 build is fine.

I don't think we can do anything about the situation, except for excluding the builds from GH. What do you think?

[fniephaus]

Thanks for investigating, @theseion.
Given that GitHub forces us to upgrade to newer versions of Ubuntu, we should probably upgrade the Squeak VMs. After all, they are also built using GitHub Actions these days.

Maybe @marceltaeumel can help identify a good new VM that can be used for all Squeak builds on Ubuntu 22.04/24.04?

[MariusDoe]

Hey, the CI of git/s also runs Squeak5.x builds (they fail, too).
I just tried to run a Squeak5.3 image with the VM that is used for Squeak6.0 images and SqueakSSL worked (I'm on Arch Linux, but I guess that it would work on Ubuntu 22.04/24.04, too, since the git/s CI for 6.0 works).

Is there a reason why different VMs are used for different versions of Squeak? I investigated the commit history, but couldn't find any reasoning:

• e057947 originally upgraded all versions (pre 6.0) to 202003021730
• 9b56576 then revised that by introducing the split between 5.3/trunk and the rest
• f10f4e0 upgraded to 202101260417, but only trunk
• 54b3774 upgraded trunk again to 202206021410
• 637bde5 seemingly simply followed path of splitting and introduced a new split for 6.0 using the same version as trunk.

If there is no particular reason why this split was introduced except for being careful, then maybe 202206021410 can be used for 5.x as well?

[theseion]

Well, not all VMs are backwards compatible (VMs are tied to specific image format versions). So to be safe, images and VMs are paired. I'm pretty sure the issue is related to the runner changes, where all builds now run on a newer version of Ubuntu which will use a different version of OpenSSL.

@fniephaus. If the newer VMs do really work for the older images, we could just use the current one for all of them. WDYT?

[fniephaus]

Is there a reason why different VMs are used for different versions of Squeak?

If the newer VMs do really work for the older images, we could just use the current one for all of them. WDYT?

We typically use the same VM that ships with the corresponding image. While an older image typically works on a newer VM, you'd not be testing what the majority of users would use.

We haven't updated VMs and images in quite some time. Does the latest 5.3 bundle come with a VM that works on Ubuntu 22/24?