Since minecraft-launcher [1] is a x86-64 binary a "-*" for 1.6.93:legacy would be nice as in "1035:0: ~amd64 -*" [1] /usr/bin/minecraft-launcher: ELF 64-bit LSB pie executable, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=c4608e974a830f926e3e77a94cb6213e45011ef0, strippe
Are you sure you haven't installed the wrong version by mistake? I don't see anywhere in the 1.6.93 ebuild where it even mentions a "minecraft-launcher" file, it's using standard java-pkg shell script wrappers around the .jar file.
The legacy version is a jar file which can in theory also be executed on other arches, this is why the legacy version does not hace the -* keyword while the newer versions do.
(In reply to Andrew Ammerlaan from comment #2) > The legacy version is a jar file which can in theory also be executed on > other arches, this is why the legacy version does not hace the -* keyword > while the newer versions do. You are right, when I unmerged the package after the bug report I realized, that I had the wrong version. My system is arm64 (Raspi 400). I didn't understand the documentation right and thought if there is a version with "~arm64" and a version with "~arm64 -*" using ~* would lead to a higher priority of 1.6.93. Thanks for your attention. Below is the text i read. The documentation says [1] > Additional note: If you encounter the -* KEYWORD, this indicates that the package is known to be broken on all systems which are not otherwise listed in KEYWORDS. For example, a binary only package which is built for x86 will look like: > games-fps/quake3-demo-1.11.ebuild:KEYWORDS="-* x86" > To accept this package anyway, use one of the other keywords in package.accept_keywords like this: > games-fps/quake3-demo x86 equery m minecraft-launcher * games-action/minecraft-launcher [gentoo] Maintainer: andrewammerlaan@gentoo.org (Andrew Ammerlaan) Upstream: None specified Homepage: https://www.minecraft.net/ Location: /var/db/repos/gentoo/games-action/minecraft-launcher Keywords: 1.6.93:legacy: ~amd64 Keywords: 1035:0: ~amd64 -* License: Mojang /etc/portage/package.accept_keywords: games-action/minecraft-launcher ~* emerge -vp minecraft-launcher These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N *] games-action/minecraft-launcher-1035::gentoo 0 KiB [1] https://wiki.gentoo.org/wiki//etc/portage/package.accept_keywords#Format_and_examples
(In reply to korte from comment #3) > You are right, when I unmerged the package after the bug report I realized, > that I had the wrong version. My system is arm64 (Raspi 400). > > I didn't understand the documentation right and thought if there is a > version with "~arm64" and a version with "~arm64 -*" using ~* would lead to > a higher priority of 1.6.93. > > Thanks for your attention. Below is the text i read. > > > > The documentation says [1] > > > Additional note: If you encounter the -* KEYWORD, this indicates that the package is known to be broken on all systems which are not otherwise listed in KEYWORDS. For example, a binary only package which is built for x86 will look like: > > games-fps/quake3-demo-1.11.ebuild:KEYWORDS="-* x86" > > To accept this package anyway, use one of the other keywords in package.accept_keywords like this: > > games-fps/quake3-demo x86 That is also how I am reading this, it is implying that accepting the x86 keyword leads to a different behaviour then accepting the ~* keyword for ebuilds that have the -* keyword. So either the wiki should be rewritten or portage is not behaving as intended. Probably it is best to open a discussion on the wiki page to clarify this confusion. Please let me know if you can get the :legacy version to work on your arm64 machine, if it works then we can maybe open a keyword request for arm and arm64. From what I am reading it should work, but only for certain versions of the game and only if you replace the version of lwjgl bundled in the game with a lwjgl version specifically for arm/arm64 (We can add an ewarn message to the ebuild about this that is displayed only on arm/arm64 machines). Microsoft accounts are soon becoming mandatory, in which case the :legacy version of the launcher will likely stop working. The official launcher currently does not support arm/arm64 (though there is of course the mobile apk version of the game that you may be able to run in an Android container such as Anbox), but maybe the ATLauncher or Technic launcher will work on arm/arm64, available in the ::guru repository (though I do not know if they already support Microsoft accounts)? You can also try if MultiMC compiles on arm/arm64, though please be aware that to use Microsoft accounts on MultiMC you'll have to patch in your own secret API key.
> Probably it is best to open a discussion on the wiki page to clarify this > confusion. Did it: https://wiki.gentoo.org/wiki/Talk:/etc/portage/package.accept_keywords > > Please let me know if you can get the :legacy version to work on your arm64 > machine The :legacy version starts but when trying to start minecraft itself the internal lwjgl doesn't work. dev-java/lwjgl-2.9.3::java needs dev-java/apt-mirror to be installed and I will have a look at your suggestions, if they work. Bug 784836 - dev-java/apt-mirror: Please last-rite Additionally my acceleration isn't fully configured and needs some work (OpenGL renderer string: llvmpipe (LLVM 12.0.1, 128 bits)) https://wiki.gentoo.org/wiki/Raspberry_Pi_VC4#Is_it_working.3F Thanks for your further hints. I need some time for that.
Created attachment 755538 [details] copied the log from console
The launcher starts and when I click play demo I get a white screen and nothing happens.
