Hello, Am I the only one that is unable to install...
# kotlin-toolchain
l
Hello, Am I the only one that is unable to install the lastest Kotlin Toolchain release (0.13.0)? After running
sdk install kotlintoolchain
, I land on this error message:
Stop! The archive was corrupt and has been removed! Please try installing again.
๐Ÿ˜ฑ 4
โœ… 1
Here's the full terminal output I'm getting:
Copy code
Downloading: kotlintoolchain 0.13.0

In progress...

#=#=#
  End-of-central-directory signature not found.  Either this file is not
  a zipfile, or it constitutes one disk of a multi-part archive.  In the
  latter case the central directory and zipfile comment will be found on
  the last disk(s) of this archive.
unzip:  cannot find zipfile directory in one of /Users/louis/.sdkman/tmp/kotlintoolchain-0.13.0.zip or
        /Users/louis/.sdkman/tmp/kotlintoolchain-0.13.0.zip.zip, and cannot find /Users/louis/.sdkman/tmp/kotlintoolchain-0.13.0.zip.ZIP, period.

Stop! The archive was corrupt and has been removed! Please try installing again.
j
The install succeeds for me
a
and for me
"works on my machine" TM
๐Ÿ˜† 1
j
Which system are you on?
By any chance, does the regular install script work for you?
Copy code
curl -fsSL <https://kotl.in/install.sh> | sh
a
could you please repeat just in case?
l
Yes, it does work with the curl command
๐Ÿ‘Œ๐Ÿผ 1
I already tried repeating the sdkman command multiple times, and tried removing the files in the mentioning directory, with exactly the same results.
๐Ÿ‘Œ๐Ÿป 1
I'm on macOS 27
j
Are you behind a proxy? Or on a slow connection? We had a user not long ago who had a proxy that wasn't taken into account, and the archive download just stopped in the middle. Although I have to say the SDKMAN archive is supposed to be tiny, so I don't believe that should be the reason
l
Not that I'm aware of
๐Ÿ™ 1
j
It might be worth asking on the SDKMAN tracker, then. I'm out of ideas, and maybe the maintainer could provide some guidance as to what this error could mean (it does look like a truncated ZIP file, but just in case)
๐Ÿ‘€ 1
l
It's weird to see double file extensions: .zip.zip and .zip.ZIP in the shell output
And ".period"
j
It looks like it's just some fallbacks: it tried the plain filename, then tried to append
.zip
/
.ZIP
"just in case"โ„ข๏ธ
The "period" is just an english idiom to say "at all" (like "point" in French). So it's like "the ZIP directory couldn't be found in X and Y, and the Z file couldn't be found at all".
๐Ÿ‡ฌ๐Ÿ‡ง 1
l
I was on SDKMAN 5.18.2. As I was browsing their GitHub org page from their website, on my way to the issue tracker, I saw a BlueSky link, and their last post was about a barely a day old release.
sdk update
wouldn't do anything, but
sdk selfupdate
got me the SDKMAN 5.32.2 upgrade, and installing the Kotlin toolchain with it worked right after! Thanks for the help ๐Ÿ™๐Ÿผ
yay 2
j
Ah! Thanks for reporting back, this is good to know! So it's probably because we're using the new Sdkman publication system (which goes to a new backend), and I'm guessing the author didn't create some compatibility bridge for old clients