By default running 'emerge minecraft-launcher' picks the old legacy version (1.6.93) of the launcher rather than the newest version which is 1.0.1221. The workaround is running 'emerge =games-action/minecraft-launcher-1.0.1221' so I think the naming needs to be changed for this as new users are hitting this often it seems on Reddit. Reproducible: Always Steps to Reproduce: 1.emerge minecraft-launcher Actual Results: Old legacy version is pulled in Expected Results: Latest release should be pulled in
It looks like the legacy version installs as /usr/bin/minecraft-launcher-legacy in order to not collide, so maybe it'd make sense to just rename the ebuild to match that? There could be an argument made for removing it entirely, but as long as the old account system works (it still does, despite MS's years of saber-rattling) there's no reason to jump the gun.
That sounds like a good working solution to me to make the experience better for everyone.
> The workaround is running 'emerge =games-action/minecraft-launcher-1.0.1221' > so I think the naming needs to be changed for this as new users are hitting > this often it seems on Reddit. Instead of specifying a version number you can select which slot to install like this: For the new launcher: emerge minecraft-launcher:0 and for the legacy launcher: emerge minecraft-launcher:legacy Or, as already mentioned, you can install both simultaneously. I don't know where you have seen this issue pop-up on Reddit, but please pass the above information on to whoever is facing similar problems over there. The root of the problem is Mojang's version number scheme, which is all over the place, we've had: 2.X.XXXX, YYYY, and now we have 1.0.ZZZZ (which unfortunately happens to be a lower number then 1.6.93). Sadly there is not a lot I can do to change that (apart from inventing my own version numbering scheme). I'd rather not remove the legacy version because it (surprisingly) still works, and I know some people (who have not migrated to MS accounts) still use it. What I would like to do is package the actual launcher instead of the bootstrap script that automatically fetches and updates the launcher. This would solve our problem because then the versioning scheme would be consistent (i.e. latest version of the launcher is currently 2.3.451, latest version of the bootstrapper is 1.0.1221). However, it appears to be impossible to download an archive of a specific version of the launcher from the website (i.e. I can get minecraft.tar.gz, but not minecraft-2.3.451.tar.gz). Without the version number the ebuild would fail to verify the checksum each time the launcher is updated on the server. If anyone has a solution to the above problem I'd love to hear it. The URL where you can find the latest versions of all the things is included in the ebuild as a comment.
How about using Enne's idea of splitting the legacy version into it's own i.e minecraft-launcher and minecraft-launcher-legacy? This is a recent issue though because I know when I installed Gentoo it did pick the latest launcher.
(In reply to immolo from comment #4) > How about using Enne's idea of splitting the legacy version into it's own > i.e minecraft-launcher and minecraft-launcher-legacy? Sure, we can do that. I'll look into it. I'd still prefer to package the actual launcher properly which would also solve the problem. > This is a recent issue though because I know when I installed Gentoo it did > pick the latest launcher. That is because the version numbering scheme of the bootstrap script recently changed from e.g. 2112 to 1.0.1221. The former is bigger then 1.6.93, the latter is not.
> That is because the version numbering scheme of the bootstrap script > recently changed from e.g. 2112 to 1.0.1221. The former is bigger then > 1.6.93, the latter is not. This has nudged a memory and no I see how the problem has occurred. I agree your way is the ideal solution however it seems every other distro which packages from source is taken to splitting them up although I feel they may have always done it this way. If I find anything that may help then I'll add it here.
(In reply to Andrew Ammerlaan from comment #3) > What I would like to do is package the actual launcher instead of the > bootstrap script that automatically fetches and updates the launcher. This > would solve our problem because then the versioning scheme would be > consistent (i.e. latest version of the launcher is currently 2.3.451, latest > version of the bootstrapper is 1.0.1221). However, it appears to be > impossible to download an archive of a specific version of the launcher from > the website (i.e. I can get minecraft.tar.gz, but not > minecraft-2.3.451.tar.gz). Without the version number the ebuild would fail > to verify the checksum each time the launcher is updated on the server. So I looked into this and wrote some python script that gets the url of each file listed in the manifest.json, which can then be easily copied into the ebuild. However, there is a problem. The only way this will work is by overriding the default --workDir of the launcher (so it actually uses the files installed by the ebuild instead of auto-updating again in the users home directory). This has the side-effect of also moving all user (account) settings to this directory (which would then have to be writeable for all users). This would mean that login accounts would be shared by all users of the computer, which of course is not what we want. So unfortunately packaging the launcher itself is not possible. I double checked and it turns out that the migration to microsoft accounts is no longer optional (as of March this year). I tried logging into the legacy launcher with my microsoft account, this does not work. Therefore the legacy launcher does not work at all, so I'll solve this bug the easy way by removing it.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=aa1f9893f0bdf6242f5c6de8067cb9aee17ee569 commit aa1f9893f0bdf6242f5c6de8067cb9aee17ee569 Author: Andrew Ammerlaan <andrewammerlaan@gentoo.org> AuthorDate: 2022-11-02 12:03:21 +0000 Commit: Andrew Ammerlaan <andrewammerlaan@gentoo.org> CommitDate: 2022-11-02 12:03:27 +0000 games-action/minecraft-launcher: drop 1.6.93 It is no longer possible to login using the legacy java based launcher. Closes: https://bugs.gentoo.org/877797 Signed-off-by: Andrew Ammerlaan <andrewammerlaan@gentoo.org> games-action/minecraft-launcher/Manifest | 1 - .../minecraft-launcher-1.6.93.ebuild | 34 ---------------------- 2 files changed, 35 deletions(-)
