Can't unpack Latest release of CGE

Bugs
1

Hi all!

Today I downloaded the latest release of CGE “castle-engine-7.0-alpha.3.snapshot-win64-x86_64.zip” from Release Latest release of Castle Game Engine (Auto-Updated Snapshot) · castle-engine/castle-engine · GitHub . I checked the sha256 and it’s ok. But I got unpack error:

image
image579×178 4.84 KB

I tried different archivers such as integrated in Double Commander and Ark under Kubuntu, but nothing helps.

PS: The bundle version unpacks successfully. It’s what I’m using for now.

2

Hi there. I’ve just downloaded it (from SourceForge, Linux x86-64bit version) and I have the exact same problem using xArchiver. Seems like the ZIP files are corrupted.

[edit] I’ve tested the boundle version and it works too. Just to confirm.

3

Thank you both for reporting!

Fixed. In short – in a few hours, all the releases on Release Latest release of Castle Game Engine (Auto-Updated Snapshot) · castle-engine/castle-engine · GitHub should be good. Please then download a new one (bundled or not, as you prefer).

The bundled version you got earlier today is unfortunately not up-to-date (while the ZIP was not corrupted, but it reflects engine version from October 25), and this is actually a result of the same bug. In a few hours, all versions (bundled and not) will be correct and up-to-date.

Details what was broken:

  • Thanks for all the information, this allowed me to find the problem quicker. Since both GitHub and SourceForge downloads were broken, the error was at creation not upload. And you reported both castle-engine-7.0-alpha.3.snapshot-win64-x86_64.zip and castle-engine-7.0-alpha.3.snapshot-linux-x86_64.zip broken → so 2 ZIPs are broken, this cannot be a random accident :slight_smile:

  • I observed another error actually: although you both reported that “bundled” versions work, but… they are actually outdated. That is,

    1. castle-engine-7.0-alpha.3.snapshot-linux-x86_64-bundle.zip and
    2. castle-engine-7.0-alpha.3.snapshot-win64-x86_64-bundle.zip

    have been outdated, they reflected the engine state from October 25, not from today. And I’ve made some huge engine merge this week :), more details about it on news soon. Don’t miss out on it :slight_smile:

  • All in all, everything above was a consequence of trivial mistake I made on October 25 in this commit. I set shell variable CGE_PACK_BUNDLE=true instead of CGE_PACK_BUNDLE=yes… which makes a huge difference, as the script expected yes :slight_smile: Shell scripts don’t have “boolean type and type checking” like Pascal so such silly mistake was possible. Fixed now, also with a precaution to next time clearly fail if CGE_PACK_BUNDLE will be mistakenly set to a non-handled value.

  • As a result of previous mixup, the GitHub Actions made 2 versions of non-bundled ZIP (and 0 versions of bundled ZIPs), and they were clashing at being used – looks like download-artifact GitHub action wasn’t prepared that someone will try to put 2 files, with the same name, in the artifacts directory. It resulted in some nonsense being uploaded, which matched neither build (looking at SHA256 sums).

I fixed it now, and I also plan to put some additional checks in-place this mistake will not happen again. A script could download things from Release Latest release of Castle Game Engine (Auto-Updated Snapshot) · castle-engine/castle-engine · GitHub , check they can be unpacked, check they are all up-to-date (if one was uploaded a month earlier than another – that should be an automatic error).

2 Likes