Package Details: mindustry-bin 1:7.0_132-1

Git Clone URL: https://aur.archlinux.org/mindustry-bin.git (read-only, click to copy)
Package Base: mindustry-bin
Description: A sandbox tower defense game written in Java
Upstream URL: https://github.com/Anuken/Mindustry
Licenses: GPL3
Conflicts: mindustry
Provides: mindustry
Submitter: dmitmel
Maintainer: dmitmel
Last Packager: dmitmel
Votes: 15
Popularity: 0.24
First Submitted: 2019-10-08 13:45
Last Updated: 2021-10-16 19:44

Dependencies (4)

Required by (0)

Sources (4)

Latest Comments

1 2 Next › Last »

dmitmel commented on 2021-08-16 09:16

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

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

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

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

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

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

Validity check fails for me for Build 118, the checksum seems to be wrong. https://github.com/Anuken/Mindustry/releases/download/v108/Mindustry.jar has the checksum a07fbd97e245ebe571fcfd1179f0292f449f2dd2d2cafdd6012631c61e24f1e7 for me, but the PKGBUILD has one starting with 4a.

Firstbober commented on 2019-10-25 11:21

dmitmel: Sure, it should work well.

dmitmel commented on 2019-10-25 10:55

Firstbober: Thanks, didn't consider that, I'll change that later (I don't have a access to my machine right now). Although I think that the version should instead look like major.minor_build to show that the build number isn't reset on each new minor/major version.

Firstbober commented on 2019-10-25 09:15

I think the version number should look like major.minor.patch.0.build or something similar to mark the version of the game. For example 5.0.0.0.97.