Package Details: mindustry-bin 1:7.0_135.1-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: 17
Popularity: 0.36
First Submitted: 2019-10-08 13:45 (UTC)
Last Updated: 2022-04-01 08:44 (UTC)

Dependencies (4)

Required by (0)

Sources (4)

Latest Comments

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. 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 (UTC)

dmitmel: Sure, it should work well.

dmitmel commented on 2019-10-25 10:55 (UTC)

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 (UTC) (edited on 2019-10-25 09:16 (UTC) by Firstbober)

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.

dmitmel commented on 2019-10-08 17:32 (UTC)

eschwartz: Thanks for your help very much!

eschwartz commented on 2019-10-08 17:30 (UTC)

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.

dmitmel commented on 2019-10-08 17:17 (UTC)

eschwartz: Yeah, I'm probably going to do that way. Also: if I make a split package with pkgbase=mindustry and which contains two packages mindustry and mindustry-server, should I ask for deletion of mindustry-server?

eschwartz commented on 2019-10-08 17:14 (UTC)

That would be my recommendation. :) Change this one to build from source, and add a pinned comment telling people where to find a precompiled binary package if they prefer.

dmitmel commented on 2019-10-08 17:11 (UTC)

eschwartz: So should I make a pinned comment about the split of this package into mindustry and mindustry-bin?

eschwartz commented on 2019-10-08 17:09 (UTC)

No, you're wrong. People who have installed this package already are expecting to install "the software", and are ambivalent about how it is created. People who go to download a package ending in -bin are explicitly saying "I consider using precompiled assets to be important".

Also there is already a notification system, it is called "the comments section". :)

dmitmel commented on 2019-10-08 16:54 (UTC)

eschwartz: because most people who have already installed this package are expecting a pre-compiled binary, I can't think of a way to add compilation here and notify users about migration to mindustry-bin.

eschwartz commented on 2019-10-08 15:23 (UTC)

Why not just update it to run ./gradlew desktop:dist on the downloaded source code?

dmitmel commented on 2019-10-08 13:21 (UTC)

vasya, thanks for your suggestion. I may be missremembering, but I read somewhere on ArchWiki that Java applications are the only exception to the -bin suffix rule. Although I couldn't find anything like that now, so yeah, I'm going to rename this package. Thanks!

vasya commented on 2019-10-08 07:08 (UTC)

Hi Dmitro! Thanks for publishing the game. Can you change the package name to "mindustry-bin" please? The general AUR guidelines say to use the name of "-bin" if the AUR package uses already built binaries, or use a name without "-bin" if sources are downloaded and then built.