Package Details: mindustry-bin 1:6.0_126.2-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: 14
Popularity: 0.34
First Submitted: 2019-10-08 13:45
Last Updated: 2021-03-29 18:07

Dependencies (4)

Required by (0)

Sources (4)

Latest Comments

1 2 Next › Last »

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. 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 or something similar to mark the version of the game. For example

dmitmel commented on 2019-10-08 17:32

eschwartz: Thanks for your help very much!

eschwartz commented on 2019-10-08 17:30

Yes, you'll need to have the existing additional pkgname deleted (or merged, but there are no comments or votes to merge anyway) before you can push an update containing an additional pkgname in this .SRCINFO.