Install failing on i386 system

We are attempting to install SDKMAN on Ubuntu running in a i386 VM. Most of the installation goes through, but towards the end one of the curl commands fail with exit code 22.

++ current_command='curl --fail --location --progress-bar "${SDKMAN_SERVICE}/broker/download/native/install/${SDKMAN_NATIVE_VERSION}/${SDKMAN_PLATFORM}" > "$sdkman_zip_file"'

curl --fail --location --progress-bar https://api.sdkman.io/2/broker/download/native/install/0.5.0/linuxx32
##O#- #
curl: (22) The requested URL returned error: 404 Not Found
++ track_last_command
++ last_command='curl --fail --location --progress-bar "${SDKMAN_SERVICE}/broker/download/native/install/${SDKMAN_NATIVE_VERSION}/${SDKMAN_PLATFORM}" > "$sdkman_zip_file"'
++ current_command='curl --fail --location --progress-bar "${SDKMAN_SERVICE}/broker/download/native/install/${SDKMAN_NATIVE_VERSION}/${SDKMAN_PLATFORM}" > "$sdkman_zip_file"'

echo_failed_command

local exit_code=22

Is it possible the page is missing from the site? The page that is not found is https://api.sdkman.io/2/broker/download/native/install/0.5.0/linuxx32

@Rinocenc

Hi @Rinocenc, I'm not sure what you mean by page from the site, but we currently don't support 32-bit architectures for the native sdkman CLI. Could you tell me if you are trying to run this on a CI pipeline or a developer machine?

Hello Marco, This is on a developer machine. The developer has a 32 bit version of Ubuntu installed and tried using the SDKMan Documentation portal to install it. This is the error message at the end of the installation (we added -x after bash to watch the execution). ++ track_last_command ++ last_command='sdkman_zip_file="${sdkman_tmp_folder}/sdkman-native-${SDKMAN_NATIVE_VERSION}.zip"' ++ current_command='echo "* Downloading..."' + echo '* Downloading...' * Downloading... ++ track_last_command ++ last_command='echo "* Downloading..."' ++ current_command='curl --fail --location --progress-bar "${SDKMAN_SERVICE}/broker/download/native/install/${SDKMAN_NATIVE_VERSION}/${SDKMAN_PLATFORM}" > "$sdkman_zip_file"' + curl --fail --location --progress-bar https://api.sdkman.io/2/broker/download/native/install/0.5.0/linuxx32 ##O#- # curl: (22) The requested URL returned error: 404 Not Found ++ track_last_command ++ last_command='curl --fail --location --progress-bar "${SDKMAN_SERVICE}/broker/download/native/install/${SDKMAN_NATIVE_VERSION}/${SDKMAN_PLATFORM}" > "$sdkman_zip_file"' ++ current_command='curl --fail --location --progress-bar "${SDKMAN_SERVICE}/broker/download/native/install/${SDKMAN_NATIVE_VERSION}/${SDKMAN_PLATFORM}" > "$sdkman_zip_file"' + echo_failed_command + local exit_code=22 + [[ 22 != \0 ]] + echo ''\''curl --fail --location --progress-bar "${SDKMAN_SERVICE}/broker/download/native/install/${SDKMAN_NATIVE_VERSION}/${SDKMAN_PLATFORM}" > "$sdkman_zip_file"'\'': command failed with exit code 22.' 'curl --fail --location --progress-bar "${SDKMAN_SERVICE}/broker/download/native/install/${SDKMAN_NATIVE_VERSION}/${SDKMAN_PLATFORM}" > "$sdkman_zip_file"': command failed with exit code 22. Thank you, Richard Inocencio LOCKSS Technical Support Specialist Digital Library Systems and Services Stanford, CA 94305

…

________________________________ From: Marco Vermeulen ***@***.***> Sent: Monday, February 17, 2025 2:06 PM To: sdkman/sdkman-cli-native ***@***.***> Cc: Richard Daniel Inocencio ***@***.***>; Mention ***@***.***> Subject: Re: [sdkman/sdkman-cli-native] Install failing on i386 system (Issue #293) Hi @Rinocenc<https://github.com/Rinocenc>, I'm not sure what you mean by page from the site, but we currently don't support 32-bit architectures for the native sdkman CLI. Could you tell me if you are trying to run this on a CI pipeline or a developer machine? — Reply to this email directly, view it on GitHub<#293 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AF2F7M4VFTDQL3IT2FKVGAT2QJMNBAVCNFSM6AAAAABW55HONCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRUGE2DKMJUGM>. You are receiving this because you were mentioned.Message ID: ***@***.***> [marc0der]marc0der left a comment (sdkman/sdkman-cli-native#293)<#293 (comment)> Hi @Rinocenc<https://github.com/Rinocenc>, I'm not sure what you mean by page from the site, but we currently don't support 32-bit architectures for the native sdkman CLI. Could you tell me if you are trying to run this on a CI pipeline or a developer machine? — Reply to this email directly, view it on GitHub<#293 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AF2F7M4VFTDQL3IT2FKVGAT2QJMNBAVCNFSM6AAAAABW55HONCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRUGE2DKMJUGM>. You are receiving this because you were mentioned.Message ID: ***@***.***>

@Rinocenc

Hi, @Rinocenc. I'm sorry for the delay with this.

I'd love to get this working, but I need your help as I don't have an i686 machine or VM. I've compiled new binaries, and you should be able to find the 32-bit variant on our download page. To test whether it works:

Download the file called sdkman-cli-native-0.5.10-i686-unknown-linux-gnu.zip
Extract the file and move the contents of sdkman-cli-native-0.5.10-i686-unknown-linux-gnu/libexec/ into the ~/.sdkman/libexec directory.

cd ~/Downlods
wget https://github.com/sdkman/sdkman-cli-native/releases/download/v0.5.10/sdkman-cli-native-0.5.10-i686-unknown-linux-gnu.zip
unzip sdkman-cli-native-0.5.10-i686-unknown-linux-gnu.zip
mv -v sdkman-cli-native-0.5.10-i686-unknown-linux-gnu/libexec/* ~/.sdkman/libexec/

If the files were correctly moved to this directory, you succeeded. You can now test it by running the sdk version command. You should see the following:

sdk version

SDKMAN!
script: 5.19.0
native: 0.5.10

This proves that the binaries are working. Once you've completed this, with your help, I would like to make it part of our installation procedure. But first, let's test if the binaries themselves work.

I really appreciate your help with this. I will try this tonight when I am home from the office and let you know the results. It is very neat that you are considering making this part of the installation procedure and I will help however I can. Thank you, Richard Inocencio LOCKSS Technical Support Specialist Digital Library Systems and Services Stanford, CA 94305

…

________________________________ From: Marco Vermeulen ***@***.***> Sent: Tuesday, March 4, 2025 8:53 AM To: sdkman/sdkman-cli-native ***@***.***> Cc: Richard Daniel Inocencio ***@***.***>; Mention ***@***.***> Subject: Re: [sdkman/sdkman-cli-native] Install failing on i386 system (Issue #293) Hi, @Rinocenc<https://github.com/Rinocenc>. I'm sorry for the delay with this. I'd love to get this working, but I need your help as I don't have an i686 machine or VM. I've compiled new binaries, and you should be able to find the 32-bit variant on our download page<https://github.com/sdkman/sdkman-cli-native/releases/tag/v0.5.10>. To test whether it works: 1. Download the file called sdkman-cli-native-0.5.10-i686-unknown-linux-gnu.zip 2. Extract the file and move the contents of sdkman-cli-native-0.5.10-i686-unknown-linux-gnu/libexec/ into the ~/.sdkman/libexec directory. cd ~/Downlods wget https://github.com/sdkman/sdkman-cli-native/releases/download/v0.5.10/sdkman-cli-native-0.5.10-i686-unknown-linux-gnu.zip unzip sdkman-cli-native-0.5.10-i686-unknown-linux-gnu.zip mv -v sdkman-cli-native-0.5.10-i686-unknown-linux-gnu/libexec/* ~/.sdkman/libexec/ If the files were correctly moved to this directory, you succeeded. You can now test it by running the sdk version command. You should see the following: sdk version SDKMAN! script: 5.19.0 native: 0.5.10 This proves that the binaries are working. Once you've completed this, with your help, I would like to make it part of our installation procedure. But first, let's test if the binaries themselves work. — Reply to this email directly, view it on GitHub<#293 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AF2F7M5CIYI4QY74WYCAS4T2SXK7NAVCNFSM6AAAAABW55HONCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOJYGMZDENJTGE>. You are receiving this because you were mentioned.Message ID: ***@***.***> [marc0der]marc0der left a comment (sdkman/sdkman-cli-native#293)<#293 (comment)> Hi, @Rinocenc<https://github.com/Rinocenc>. I'm sorry for the delay with this. I'd love to get this working, but I need your help as I don't have an i686 machine or VM. I've compiled new binaries, and you should be able to find the 32-bit variant on our download page<https://github.com/sdkman/sdkman-cli-native/releases/tag/v0.5.10>. To test whether it works: 1. Download the file called sdkman-cli-native-0.5.10-i686-unknown-linux-gnu.zip 2. Extract the file and move the contents of sdkman-cli-native-0.5.10-i686-unknown-linux-gnu/libexec/ into the ~/.sdkman/libexec directory. cd ~/Downlods wget https://github.com/sdkman/sdkman-cli-native/releases/download/v0.5.10/sdkman-cli-native-0.5.10-i686-unknown-linux-gnu.zip unzip sdkman-cli-native-0.5.10-i686-unknown-linux-gnu.zip mv -v sdkman-cli-native-0.5.10-i686-unknown-linux-gnu/libexec/* ~/.sdkman/libexec/ If the files were correctly moved to this directory, you succeeded. You can now test it by running the sdk version command. You should see the following: sdk version SDKMAN! script: 5.19.0 native: 0.5.10 This proves that the binaries are working. Once you've completed this, with your help, I would like to make it part of our installation procedure. But first, let's test if the binaries themselves work. — Reply to this email directly, view it on GitHub<#293 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AF2F7M5CIYI4QY74WYCAS4T2SXK7NAVCNFSM6AAAAABW55HONCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOJYGMZDENJTGE>. You are receiving this because you were mentioned.Message ID: ***@***.***>

@Rinocenc

Hi @Rinocenc, just checking in if you managed to get this working.

Hello Marco, I tried the installation steps but was unable to get it working. I tried * Running the installation as mentioned in first message * Downloading your zip file and unzipping it * moving the contents to ~/.sdk/libexec/ * running "sdk version" I kept running into an error message stating that ~/.sdkman/var/version was not a valid path. I tried to trick the install by adding a softlink from ~/.sdkman/libexec/version to ~/.sdkman/var/version but was met with a new error. I have listed the entire output from my terminal in the text file attached to this message. I even tried adding a bit of Rust debugging info as mentioned in the error messages Thank you, Richard Inocencio LOCKSS Technical Support Specialist Digital Library Systems and Services Stanford, CA 94305

…

________________________________ From: Marco Vermeulen ***@***.***> Sent: Monday, March 10, 2025 2:55 AM To: sdkman/sdkman-cli-native ***@***.***> Cc: Richard Daniel Inocencio ***@***.***>; Mention ***@***.***> Subject: Re: [sdkman/sdkman-cli-native] Install failing on i386 system (Issue #293) Hi @Rinocenc<https://github.com/Rinocenc>, just checking in if you managed to get this working. — Reply to this email directly, view it on GitHub<#293 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AF2F7MYIFHKKHWVPQ2D4HRD2TVOPNAVCNFSM6AAAAABW55HONCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJQGAYTCMJXGQ>. You are receiving this because you were mentioned.Message ID: ***@***.***> [marc0der]marc0der left a comment (sdkman/sdkman-cli-native#293)<#293 (comment)> Hi @Rinocenc<https://github.com/Rinocenc>, just checking in if you managed to get this working. — Reply to this email directly, view it on GitHub<#293 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AF2F7MYIFHKKHWVPQ2D4HRD2TVOPNAVCNFSM6AAAAABW55HONCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJQGAYTCMJXGQ>. You are receiving this because you were mentioned.Message ID: ***@***.***> ***@***.***:~/Downloads$ mv -v sdkman-cli-native-0.5.10-i686-unknown-linux-gnu/libexec/* /home/inocencr/.sdkman/libexec/ 'sdkman-cli-native-0.5.10-i686-unknown-linux-gnu/libexec/default' -> '/home/inocencr/.sdkman/libexec/default' 'sdkman-cli-native-0.5.10-i686-unknown-linux-gnu/libexec/help' -> '/home/inocencr/.sdkman/libexec/help' 'sdkman-cli-native-0.5.10-i686-unknown-linux-gnu/libexec/home' -> '/home/inocencr/.sdkman/libexec/home' 'sdkman-cli-native-0.5.10-i686-unknown-linux-gnu/libexec/uninstall' -> '/home/inocencr/.sdkman/libexec/uninstall' 'sdkman-cli-native-0.5.10-i686-unknown-linux-gnu/libexec/version' -> '/home/inocencr/.sdkman/libexec/version' ***@***.***:~/Downloads$ sdk version No command 'sdk' found, did you mean: Command 'sd' from package 'sd' (universe) Command 'sdb' from package 'sdb' (universe) Command 'skk' from package 'libskk-dev' (universe) Command 'sdc' from package 'hpsockd' (universe) Command 'sak' from package 'seqan-apps' (universe) Command 'fdk' from package 'plastimatch' (universe) Command 'sdf' from package 'sdf' (universe) Command 'sds' from package 'simh' (universe) sdk: command not found ***@***.***:~/Downloads$ source /home/inocencr/.sdkman/bin/sdkman-init.sh ***@***.***:~/Downloads$ sdk version thread 'main' panicked at src/lib.rs:38:13: not a valid path: /home/inocencr/.sdkman/var/version note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace ***@***.***:~/Downloads$ cd ***@***.***:~$ sdk version thread 'main' panicked at src/lib.rs:38:13: not a valid path: /home/inocencr/.sdkman/var/version note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace ***@***.***:~$ export RUST_BACKTRACE=1 ***@***.***:~$ sdk version thread 'main' panicked at src/lib.rs:38:13: not a valid path: /home/inocencr/.sdkman/var/version stack backtrace: 0: rust_begin_unwind 1: core::panicking::panic_fmt 2: sdkman_cli_native::helpers::check_file_exists 3: version::main note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace. ***@***.***:~$ export RUST_BACKTRACE=full ***@***.***:~$ sdk version thread 'main' panicked at src/lib.rs:38:13: not a valid path: /home/inocencr/.sdkman/var/version stack backtrace: 0: 0x4f4d1c - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::hc4c9d8fd4809a23d 1: 0x510c07 - core::fmt::write::hddd6b9a50b95c6b3 2: 0x4f2616 - std::io::Write::write_fmt::he0760fb71b3e9bdb 3: 0x4f4bc9 - std::sys::backtrace::BacktraceLock::print::h22507086ea75f19c 4: 0x4f5b31 - std::panicking::default_hook::{{closure}}::hfcb8454165269fb4 5: 0x4f5934 - std::panicking::default_hook::hb0a5ca6a5ff0a6fd 6: 0x4f6209 - std::panicking::rust_panic_with_hook::h22a26b339096c0ea 7: 0x4f6084 - std::panicking::begin_panic_handler::{{closure}}::h2044f2dece8b082b 8: 0x4f51b9 - std::sys::backtrace::__rust_end_short_backtrace::h129ce808a5647b47 9: 0x4f5ccd - rust_begin_unwind 10: 0x4ccbf0 - core::panicking::panic_fmt::hd5db137d5c60db19 11: 0x4cde8b - sdkman_cli_native::helpers::check_file_exists::h674ddc664372b5c4 12: 0x4cd4e5 - version::main::h1c45f340dcf8d99f 13: 0x4cd3c2 - std::sys::backtrace::__rust_begin_short_backtrace::h9c4335eb5e5688d4 14: 0x4cd39b - std::rt::lang_start::{{closure}}::h8fe5dff910e9619f 15: 0x4ef59f - std::rt::lang_start_internal::heb64f2ccbe20b727 16: 0x4cd8e8 - main 17: 0xb75c9647 - __libc_start_main 18: 0x4cd249 - <unknown> ***@***.***:~$ ls -l /home/inocencr/.sdkman/ total 36 drwxr-xr-x 2 inocencr inocencr 4096 Mar 10 10:52 bin drwxrwxr-x 2 inocencr inocencr 4096 Mar 10 10:52 candidates drwxr-xr-x 3 inocencr inocencr 4096 Mar 10 10:52 contrib drwxrwxr-x 2 inocencr inocencr 4096 Mar 10 10:52 etc drwxrwxr-x 2 inocencr inocencr 4096 Mar 10 10:52 ext drwxrwxr-x 2 inocencr inocencr 4096 Mar 10 10:53 libexec drwxr-xr-x 2 inocencr inocencr 4096 Mar 10 10:52 src drwxrwxr-x 2 inocencr inocencr 4096 Mar 10 10:52 tmp drwxrwxr-x 2 inocencr inocencr 4096 Mar 10 10:53 var ***@***.***:~$ ls -l /home/inocencr/.sdkman/var/ total 8 -rw-rw-r-- 1 inocencr inocencr 561 Mar 10 10:52 candidates -rw-rw-r-- 1 inocencr inocencr 0 Mar 10 10:53 delay_upgrade -rw-rw-r-- 1 inocencr inocencr 9 Mar 10 10:52 platform ***@***.***:~$ ln -s /home/inocencr/.sdkman/libexec/version /home/inocencr/.sdkman/var/version ***@***.***:~$ sdk version thread 'main' panicked at src/lib.rs:38:13: not a valid path: /home/inocencr/.sdkman/var/version_native stack backtrace: 0: 0x4f7d1c - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::hc4c9d8fd4809a23d 1: 0x513c07 - core::fmt::write::hddd6b9a50b95c6b3 2: 0x4f5616 - std::io::Write::write_fmt::he0760fb71b3e9bdb 3: 0x4f7bc9 - std::sys::backtrace::BacktraceLock::print::h22507086ea75f19c 4: 0x4f8b31 - std::panicking::default_hook::{{closure}}::hfcb8454165269fb4 5: 0x4f8934 - std::panicking::default_hook::hb0a5ca6a5ff0a6fd 6: 0x4f9209 - std::panicking::rust_panic_with_hook::h22a26b339096c0ea 7: 0x4f9084 - std::panicking::begin_panic_handler::{{closure}}::h2044f2dece8b082b 8: 0x4f81b9 - std::sys::backtrace::__rust_end_short_backtrace::h129ce808a5647b47 9: 0x4f8ccd - rust_begin_unwind 10: 0x4cfbf0 - core::panicking::panic_fmt::hd5db137d5c60db19 11: 0x4d0e8b - sdkman_cli_native::helpers::check_file_exists::h674ddc664372b5c4 12: 0x4d0571 - version::main::h1c45f340dcf8d99f 13: 0x4d03c2 - std::sys::backtrace::__rust_begin_short_backtrace::h9c4335eb5e5688d4 14: 0x4d039b - std::rt::lang_start::{{closure}}::h8fe5dff910e9619f 15: 0x4f259f - std::rt::lang_start_internal::heb64f2ccbe20b727 16: 0x4d08e8 - main 17: 0xb759b647 - __libc_start_main 18: 0x4d0249 - <unknown>

Right, your installation was seemingly never completed because it couldn't find the zip i686 binary when you first installed it. Let's see if we can fix this. I'm going to ask you to send me the output of the following command:

uname -sm

Once I have this information, I can make the changes to the installer to ensure it works as it should so you can start over.

Hello Marco, The output of that command is Linux i686 I will be happy to test the changes that you make. Thank you, Richard Inocencio LOCKSS Technical Support Specialist Digital Library Systems and Services Stanford, CA 94305

…

________________________________ From: Marco Vermeulen ***@***.***> Sent: Monday, March 10, 2025 1:29 PM To: sdkman/sdkman-cli-native ***@***.***> Cc: Richard Daniel Inocencio ***@***.***>; Mention ***@***.***> Subject: Re: [sdkman/sdkman-cli-native] Install failing on i386 system (Issue #293) Right, your installation was seemingly never completed because it couldn't find the zip i686 binary when you first installed it. Let's see if we can fix this. I'm going to ask you to send me the output of the following command: uname -sm Once I have this information, I can make the changes to the installer to ensure it works as it should so you can start over. — Reply to this email directly, view it on GitHub<#293 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AF2F7M3EG7M6GN54XOHXFLT2TXY3JAVCNFSM6AAAAABW55HONCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJRG42DSNRQGM>. You are receiving this because you were mentioned.Message ID: ***@***.***> [marc0der]marc0der left a comment (sdkman/sdkman-cli-native#293)<#293 (comment)> Right, your installation was seemingly never completed because it couldn't find the zip i686 binary when you first installed it. Let's see if we can fix this. I'm going to ask you to send me the output of the following command: uname -sm Once I have this information, I can make the changes to the installer to ensure it works as it should so you can start over. — Reply to this email directly, view it on GitHub<#293 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AF2F7M3EG7M6GN54XOHXFLT2TXY3JAVCNFSM6AAAAABW55HONCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJRG42DSNRQGM>. You are receiving this because you were mentioned.Message ID: ***@***.***>

@Rinocenc

Hi @Rinocenc, I've deployed the necessary changes, and it's ready for you to test.

To test it, you must delete your current installation by removing the entire ~.sdkman directory. Once you've done this, you can attempt a fresh installation in the usual manner using the curl command on our website. Let me know how that goes!

Hello Marco, The installation was successful using the usual manner! I really appreciate all of your help with this. When trying to list the different Java versions, I am met with a message "There are currently no version of java for 32bit Linux". Will this be fixed in the future? Sincerely, Richard Inocencio LOCKSS Technical Support Specialist Digital Library Systems and Services Stanford, CA 94305

…

________________________________ From: Marco Vermeulen ***@***.***> Sent: Wednesday, March 12, 2025 3:17 PM To: sdkman/sdkman-cli-native ***@***.***> Cc: Richard Daniel Inocencio ***@***.***>; Mention ***@***.***> Subject: Re: [sdkman/sdkman-cli-native] Install failing on i386 system (Issue #293) Hi @Rinocenc<https://github.com/Rinocenc>, I've deployed the necessary changes, and it's ready for you to test. To test it, you must delete your current installation by removing the entire ~.sdkman directory. Once you've done this, you can attempt a fresh installation in the usual manner using the curl command on our website. Let me know how that goes! — Reply to this email directly, view it on GitHub<#293 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AF2F7MZZN5EDIPPPL62L6NL2UCXAXAVCNFSM6AAAAABW55HONCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJZGI2TENRXGI>. You are receiving this because you were mentioned.Message ID: ***@***.***> [marc0der]marc0der left a comment (sdkman/sdkman-cli-native#293)<#293 (comment)> Hi @Rinocenc<https://github.com/Rinocenc>, I've deployed the necessary changes, and it's ready for you to test. To test it, you must delete your current installation by removing the entire ~.sdkman directory. Once you've done this, you can attempt a fresh installation in the usual manner using the curl command on our website. Let me know how that goes! — Reply to this email directly, view it on GitHub<#293 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AF2F7MZZN5EDIPPPL62L6NL2UCXAXAVCNFSM6AAAAABW55HONCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJZGI2TENRXGI>. You are receiving this because you were mentioned.Message ID: ***@***.***>

@eddumelendez

So glad that this worked for you! Hopefully, this will help others, too.

Regarding support for 32-bit Java, it seems like support from all the major vendors has dropped off significantly (or perhaps the disco integration project is no longer passing them through to us; @eddumelendez might be able to help).

That said, I found two old versions of Liberica JDK from Bellsoft in the database that were no longer marked visible. I've changed their status, so you should be able to see them now. Let me know if that works for you.

In the meantime, @eddumelendez, would you please check if the 32-bit binaries are still propagating?

Hello Marco, Java 8 is the version that I needed, and Liberica satisfied that! I really appreciate all of your help with this! Thank you, Richard Inocencio LOCKSS Technical Support Specialist Digital Library Systems and Services Stanford, CA 94305

…

________________________________ From: Marco Vermeulen ***@***.***> Sent: Saturday, March 15, 2025 6:46 AM To: sdkman/sdkman-cli-native ***@***.***> Cc: Richard Daniel Inocencio ***@***.***>; Mention ***@***.***> Subject: Re: [sdkman/sdkman-cli-native] Install failing on i386 system (Issue #293) So glad that this worked for you! Hopefully, this will help others, too. Regarding support for 32-bit Java, it seems like support from all the major vendors has dropped off significantly (or perhaps the disco integration project is no longer passing them through to us; @eddumelendez<https://github.com/eddumelendez> might be able to help). That said, I found two old versions of Liberica JDK from Bellsoft in the database that were no longer marked visible. I've changed their status, so you should be able to see them now. Let me know if that works for you. In the meantime, @eddumelendez<https://github.com/eddumelendez>, would you please check if the 32-bit binaries are still propagating? — Reply to this email directly, view it on GitHub<#293 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AF2F7M24YPXBEBZTEQ5IZRL2UQVMDAVCNFSM6AAAAABW55HONCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMRWGU3DSMJTGQ>. You are receiving this because you were mentioned.Message ID: ***@***.***> [marc0der]marc0der left a comment (sdkman/sdkman-cli-native#293)<#293 (comment)> So glad that this worked for you! Hopefully, this will help others, too. Regarding support for 32-bit Java, it seems like support from all the major vendors has dropped off significantly (or perhaps the disco integration project is no longer passing them through to us; @eddumelendez<https://github.com/eddumelendez> might be able to help). That said, I found two old versions of Liberica JDK from Bellsoft in the database that were no longer marked visible. I've changed their status, so you should be able to see them now. Let me know if that works for you. In the meantime, @eddumelendez<https://github.com/eddumelendez>, would you please check if the 32-bit binaries are still propagating? — Reply to this email directly, view it on GitHub<#293 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AF2F7M24YPXBEBZTEQ5IZRL2UQVMDAVCNFSM6AAAAABW55HONCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMRWGU3DSMJTGQ>. You are receiving this because you were mentioned.Message ID: ***@***.***>

Navigation Menu

Repository navigation

Install failing on i386 system #293

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Install failing on i386 system #293

Description

Activity

marc0der commented on Feb 17, 2025

Rinocenc commented on Feb 18, 2025

marc0der commented on Mar 4, 2025

Rinocenc commented on Mar 6, 2025

marc0der commented on Mar 10, 2025

Rinocenc commented on Mar 10, 2025

marc0der commented on Mar 10, 2025

Rinocenc commented on Mar 11, 2025

marc0der commented on Mar 12, 2025

Rinocenc commented on Mar 13, 2025

marc0der commented on Mar 15, 2025

Rinocenc commented on Mar 18, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions