Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why has the 'gu' binary been removed from graalvm releases, is there an alternative? #7571

Closed
ashesfall opened this issue Oct 9, 2023 · 3 comments
Assignees
Labels

Comments

@ashesfall
Copy link

Describe the issue
After installing (on linux x64, mac aarch64, etc) from https://github.com/graalvm/graalvm-ce-dev-builds/releases
None of these contain the 'gu' binary that I have used in the past to install and update other graalvm components and tools.
I have looked all over for an explanation either of how to obtain 'gu' separately or perform the same operations without it, and there is nothing anywhere. Most graalvm documentation, even some updated quite recently, refers directly to 'gu'. Recent release notes don't appear to explain this either.

Steps to reproduce the issue
Please include both build steps as well as run steps

  1. Download and unpack the graalvm release
  2. Check the /bin directory for 'gu', which is no longer available

Describe GraalVM and your environment:

  • graalvm-community-openjdk-21+35.1
  • JDK major version: 21
  • OS: Amazon Linux2
  • Architecture: x64
@ashesfall ashesfall added the bug label Oct 9, 2023
@fniephaus fniephaus self-assigned this Oct 9, 2023
@fniephaus
Copy link
Member

Hi @ashesfall, please take a look at #6855. Feel free to get in touch if you have any questions!

@ashesfall
Copy link
Author

Thank you, I'm glad to finally see the explanation somewhere. It would be great if this was broadcast more clearly (or if an explanation of the change was displayed by the old 'gu' when running commands like 'update' or 'install'). It was very hard to figure out what was going on.

@fniephaus
Copy link
Member

Apologies for the inconvenience, @ashesfall. We have announced this in different places, including the community roadmap. We also planned to ship a script that print a migration warning, but unfortunately, the script was not included in the release due to misconfiguration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants