If you are rebuilding in the same directory, delete the file, it should redownload and have the correct checksum.
I'll put in some sort of fix as soon as I get back to a real machine with my SSH keys.
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: | custom |
Conflicts: | minecraft-launcher-beta |
Provides: | minecraft-launcher-beta |
Submitter: | shoghicp |
Maintainer: | pschichtel |
Last Packager: | pschichtel |
Votes: | 1098 |
Popularity: | 4.12 |
First Submitted: | 2017-01-18 14:17 (UTC) |
Last Updated: | 2024-06-17 22:10 (UTC) |
« First ‹ Previous 1 .. 23 24 25 26 27 28 29 30 31 32 33 .. 52 Next › Last »
If you are rebuilding in the same directory, delete the file, it should redownload and have the correct checksum.
I'll put in some sort of fix as soon as I get back to a real machine with my SSH keys.
Also reporting in: Minecraft.tar.gz fails sha256 checksum in 2.1.1218-1 update
As for the reusing of filenames, I put that on the TODO pile :)
I haven't attempted to reproduce yet, however it could be a caching issue (either on your end or smorky's).
Hmm... it works for me? On multiple machines?
You'll have to provide more details about what's going wrong, because I just don't see it.
smorky: That's because when mojang update the snapshot, the link doesn't change. That means that the checksum is different so will fail integrity checks.
Ideally, mojang would provide versioned or datestamped links for the snapshots, but AFAIK they don't. Them updating the release build would also work, but iirc the latest release build doesn't even work anymore.
Minecraft.tar.gz fails sha256 checksum in 2.1.1218-1 update.
@BombStrike My apologies. Your response to my request (and recent comment) helped me to understand why things are the way that they are between the two packages.
@BombStrike: I see, my bad!
@Brottweiler The tweet mentioned do not talk about the download link, but about the version file and my package already points to the link requested by Dinnerbone: https://aur.archlinux.org/cgit/aur.git/tree/minecraft?h=minecraft#n11
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.