Package Details: mindustry-bin 1:7.0_141.3-1

Git Clone URL: (read-only, click to copy)
Package Base: mindustry-bin
Description: A sandbox tower defense game written in Java
Upstream URL:
Licenses: GPL3
Conflicts: mindustry
Provides: mindustry
Submitter: dmitmel
Maintainer: dmitmel
Last Packager: dmitmel
Votes: 21
Popularity: 1.24
First Submitted: 2019-10-08 13:45 (UTC)
Last Updated: 2023-01-22 18:48 (UTC)

Dependencies (4)

Required by (0)

Sources (4)

Latest Comments

1 2 3 Next › Last »

RuMaks commented on 2022-08-30 12:50 (UTC)

mindustry-bin-138.jar doesn't pass the validity check (expected checksum: 56148b9e80003329f923cf99da1873b306abaf6d699dc62f803d42830343dae2)

dmitmel commented on 2021-10-18 15:09 (UTC)

akhial: fixed

akhial commented on 2021-10-18 13:34 (UTC)

mindustry-bin-133.jar is failing the validity check..

Expected: a8f4eab8a7d211988bf718775ab8004a198673a94d2e823e70a0ddc44ce4bb8c Actual: 441c3fb5abe8b1fdb1ba620714c16076b4f3f0b3b0b9af52aa100e0a7aee3108

dmitmel commented on 2021-08-16 09:16 (UTC)

E3LDDfrK: I think you are supposed to run sudo archlinux-java set <something> after installing a JRE for the first time. Not sure why this is not done automatically for JREs, but is for JDKs.

E3LDDfrK commented on 2021-08-16 01:49 (UTC) (edited on 2021-08-16 13:35 (UTC) by E3LDDfrK)

I personally got this error:

/usr/bin/mindustry: line 2: /usr/bin/java: No such file or directory

I have jre-openjdk for the java-runtime>=8 dependency if it matters. Same error with mindustry package.

edit: Installing jdk-openjdk fixes it for me. So I guess there's a java-environment dependency missing?

edit2: Thanks for the answer @dmitmel.

Eisfunke commented on 2020-11-29 18:18 (UTC)

dmitmel: That's interesting, thank you. No need to investigate on my account, I don't want to bother you. 119 works again, that's enough for me :D

dmitmel commented on 2020-11-29 17:05 (UTC) (edited on 2020-11-29 17:05 (UTC) by dmitmel)

Eisfunke: Interesting. I suppose the upstream has updated updated the tag for v118. Because as you can see from the commit history I did update the checksum. I still have the "counterfeit" JAR file for v118 with the hash 4a724410d7a3c6f3ca076037713e7da357bfc6199ca661cc73a7805f901a44af, if you want I can investigate.

Eisfunke commented on 2020-11-29 17:02 (UTC)

dmitmel: Thanks for replying and sorry for the wrong link.

That's exactly my point: the checksum of the JAR is a07fbd97e245ebe571fcfd1179f0292f449f2dd2d2cafdd6012631c61e24f1e7, as I wrote and as you confirmed. But the PKGBUILD says 4a724410d7a3c6f3ca076037713e7da357bfc6199ca661cc73a7805f901a44af.

When I edit the PKGBUILD and paste a07fbd97e245ebe571fcfd1179f0292f449f2dd2d2cafdd6012631c61e24f1e7, the checksum you confirmed, it builds correctly.

But that's probably irrelevant now, as 119 has been released half an hour ago :D

dmitmel commented on 2020-11-29 16:14 (UTC)

Eisfunke: First of all, you linked to the JAR of a wrong version (108 instead of 118), secondly, this is a problem on your end. I've re-downloaded the latest JAR and its SHA256 checksum is a07fbd97e245ebe571fcfd1179f0292f449f2dd2d2cafdd6012631c61e24f1e7, as expected. I also ran updpkgsums just in case, nothing has been updated.

Eisfunke commented on 2020-11-29 15:48 (UTC)

Validity check fails for me for Build 118, the checksum seems to be wrong. has the checksum a07fbd97e245ebe571fcfd1179f0292f449f2dd2d2cafdd6012631c61e24f1e7 for me, but the PKGBUILD has one starting with 4a.