| Git Clone URL: | https://aur.archlinux.org/minecraft-launcher.git (read-only, click to copy) |
|---|---|
| Package Base: | minecraft-launcher |
| Description: | Official Minecraft Launcher |
| Upstream URL: | https://mojang.com/ |
| Keywords: | game minecraft |
| Licenses: | All Rights Reserved |
| Conflicts: | minecraft-launcher-beta |
| Provides: | minecraft-launcher-beta |
| Submitter: | shoghicp |
| Maintainer: | MrAnno |
| Last Packager: | MrAnno |
| Votes: | 1095 |
| Popularity: | 6.97 |
| First Submitted: | 2017-01-18 14:17 (UTC) |
| Last Updated: | 2022-06-07 18:27 (UTC) |
I get the same error for this package as minecraft-launcher:
==> Validating source files with sha256sums... minecraft-2.2.741.deb ... FAILED ==> ERROR: One or more files did not pass the validity check! Failed to build minecraft
Any help please? Referencing the pinned comment, I get this output from updpkgsums:
==> ERROR: PKGBUILD not found or is not a file
ok, I set pkgver=2.2.909 and the sha256sums provided by Vinnie_PT
I am still getting the error:
==> Retrieving sources... -> Found minecraft-2.2.909.deb ==> ERROR: Integrity checks (sha256) differ in size from the source array.
To say more: only a name clash between official repo and AUR package is formally forbidden. So if there will be some minecraft in Arch repo, we may still provide some minecraft-deb or other implementation. The package has the right to exist even if it has at least one user.
You mistake me for someone else. I maintain a lot of packages in Arch User Repositor, this package is just one of them and it doesn't break any rules. This is the free software community, we are not a branch of M$ or whatever other company. If some package is promoted as an 'official' way to install a game, we appreciate it. But until there will be an official package in one of official Arch repo's this implementation or any different one has the right to exist.
What's your problem? You're maintaining a copy of an already existing package, why continuing?
@bkb
Thank you for holding. Your call is important to us. Please continue to hold and the next available agent will answer your call.
Minecraft-launcher was recognized as an official package for Arch by Microsoft
The launcher was chosen over the game itself
So unless your package is meant as a plug-in, a child of Minecraft-launcher to install Minecraft in the launcher, so unless Minecraft-launcher becomes a dependency of your package, you should delete this package
And if you want the Deb to be used in the launcher package, discuss with the maintainer
To get the latest version change the following lines in your PKGBUILD
pkgver=2.2.909
sha256sums=( '02e6067790bb65b2f0229ae297806bbdc77d1d1934f8a49d5ca21286728da297' '677e2442a1ae83cc58d8d403666e508129e97dbed37fdfafdceac6101dc0dee7' '35c2bcaeb09fa4b8864e9422fd66bf60847706f8b4400ec4a66ba6436b101f71' )
@randyzhu
Breaking news :)
I saw mention of this package on official site half a year ago.
Pinned Comments
petr commented on 2021-10-08 09:04 (UTC)
The package version is the version of the launcher bootstrap - the part that actually downloads and updates the launcher.
That means the version number of the actual launcher (2.x.xxx) is different from the version here (9xx+) on a fundamental level, and should not be compared.
The package is outdated only when the bootstrap version you get here is different from the bootstrap version you would get from minecraft.net when using the raw tarball.