At least for windows there is just a small patch to be applied. Don't know if this is different with the Linux version.

I'm getting a MD5 checksum error:

$ ./gog_unmechanical_2.1.0.4.sh
Verifying archive integrity...Error in MD5 checksums: 344e96c63f90e54e302a3b2b4abc30ed is different from eecf4208f1ec0ea163b3613bf3a16270


Any other penguin with the same issue? It's funny because I've just got an update for another game on Humble and I'm also having a MD5 checksum error with it... (I'd say it's something on my end were not for the fact that the 4 games I've got so far in GOG's winter sale have installed without issue)

Thanks! Any result? Now I'm getting a checksum error for the updated Mini Metro Linux build as well...

I'd totally agree it's my connection's fault, except that:

1) Not everything I download gets corrupted. As I said, tonight I've bought Afterlife, LOOM, Shovel Knight and Zak McKracken from GOG and all of these .sh installlers have worked alright.

2) I'm getting a ckecksum error for an update from Humble, but the MD5 I obtain from my downloaded copy and the one provided by them in my Humble library are in perfect agreement with each other, so I don't know what to think...

EDIT: point #2 reminded me: any chance you could provide MD5 hashes on the download pages (like Humble does) so we could check these kind of problems by ourselves?

Indeed there is! Voted. :)

Thanks again! No rush, I'm more than happy to learn that it doesn't seem to be my computer's or my line's fault. ^_^

1) It's not your connection.

I redownloaded the installer and got the same error. I don't own Mini Metro, but what if GOG Linux team has mixed the checksums of those two games? :-P

2) If you're interested, MD5 algorithm has known vulnerabilities. There could be multiple errors, resulting to the correct hash value!
There's an example on wikipedia.

In most cases the problem is not on your end.
But it's possible that an error could occur where the md5sum value is stored inside the installer plus other errors of course. So the installer fails, but a correct hash is produced by an external tool!

EDIT: I transferred to this topic from "the what did just update". I didn't see that there was a second page!

Just re-downloaded it, but I'm afraid I'm getting the same error: :(

$ ./gog_unmechanical_2.1.0.4.sh
Verifying archive integrity...Error in MD5 checksums: 344e96c63f90e54e302a3b2b4abc30ed is different from eecf4208f1ec0ea163b3613bf3a16270

Here's the checksum I'm getting for the whole installer, if it's of any use to you:

$ md5sum gog_unmechanical_2.1.0.4.sh
97ac4370252086a8dad05100ad0fa719 gog_unmechanical_2.1.0.4.sh

Same here.

$ ./gog_unmechanical_2.1.0.4.sh
Verifying archive integrity...Error in MD5 checksums: 344e96c63f90e54e302a3b2b4abc30ed is different from eecf4208f1ec0ea163b3613bf3a16270
$ md5sum gog_unmechanical_2.1.0.4.sh
97ac4370252086a8dad05100ad0fa719 gog_unmechanical_2.1.0.4.sh

The problem persists.