We just saw this problem. This was due to a mistake in the packaging of scripts and the ThirPart. For this new release, we have defined a new production/packaging line, theoretically more robust, but apparently we still must reinforce some tests/checking. Thanks for your feedbacks and sorry for the inconvenience.

Your analysis and your comments are fully right. But to simplify the use, we are doing a repackaging of a pure and verified Linux 32bits version only in place of the corrupted 32/64bits one currently online.

Thanks again,

Regards,

Julien for the SPIS team.