Why is java-runtime=8 required? why not >=8 ?
Search Criteria
Package Details: minecraft-launcher 1:2.1.3-1
Package Actions
| 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: | 1097 |
| Popularity: | 2.70 |
| First Submitted: | 2017-01-18 14:17 (UTC) |
| Last Updated: | 2024-11-28 00:27 (UTC) |
Dependencies (6)
- gcc-libs (gcc-libs-gitAUR, gccrs-libs-gitAUR, gcc11-libsAUR, gcc-libs-snapshotAUR)
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR)
- libgpg-error (libgpg-error-gitAUR)
- zlib (zlib-ng-compat-gitAUR, zlib-gitAUR, zlib-ng-compat)
- flite (flite1AUR) (optional) – narrator support
- org.freedesktop.secrets (keepassxc-gitAUR, gnome-keyring-gitAUR, pass-secrets-gitAUR, keepassxc-allow-aur-extension-originAUR, keepassxc-allow-aur-extension-origin-binAUR, pass-secret-service-binAUR, dssdAUR, pass-secret-service-gitAUR, bitw-gitAUR, gnome-keyring, keepassxc, kwallet, kwallet5) (optional) – persistent login support
Sources (3)
jpegxguy commented on 2018-07-06 17:24 (UTC)
petr commented on 2018-07-06 16:15 (UTC)
The fix should be in. As long as you don't have something extra in the network doing caching, it should work.
petr commented on 2018-07-03 18:47 (UTC)
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.
Tank116 commented on 2018-07-03 15:29 (UTC)
Also reporting in: Minecraft.tar.gz fails sha256 checksum in 2.1.1218-1 update
petr commented on 2018-06-30 19:35 (UTC)
As for the reusing of filenames, I put that on the TODO pile :)
mattsturgeon commented on 2018-06-30 19:28 (UTC)
I haven't attempted to reproduce yet, however it could be a caching issue (either on your end or smorky's).
petr commented on 2018-06-30 19:26 (UTC)
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.
mattsturgeon commented on 2018-06-30 17:12 (UTC)
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.
smorky commented on 2018-06-30 16:07 (UTC)
Minecraft.tar.gz fails sha256 checksum in 2.1.1218-1 update.
mkolassa commented on 2018-06-13 15:44 (UTC)
@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.
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.