Windows web-installer "Select another release to install" not working

[lehtoj]

OS: Windows 10 64-bit

In Elixir Web-installer when selecting "Select another release to install", it still installs the latest version no matter which release is selected.

[josevalim]

When did you download the installer?

@chyndman could this be related to the fact we finally started listing the shas for installations here?

[lehtoj]

I downloaded the installer yesterday, shortly before the 1.4.0 release. At the time 1.3.4 was the latest release.

[josevalim]

@KeeperB5 thank you for the info. Can you please try again and let me know if this time it works? Also, can you make sure you don't have another Elixir installed in your system that may be set with higher precedence than the one from the installer? I believe on Windows you can run something like where elixir.

[lehtoj]

The installer is supposed to remove any previous version of Elixir prior to installing the selected version, and it does. I also do not have Elixir or Erlang installed by other means than the Elixir installer.

I re-downloaded the web installer, and unfortunately now even "Install the latest stable release" option is broken.
Error message

Selecting version 1.3.4 still downloads 1.4.0 and attempts to run the 1.4.0 installer, with the above error message.

[josevalim]

@KeeperB5 I see. So I believe the bug is unrelated to the sha hashes. I have added the sha's back, can you please check if installing at least v1.4.0 now works again?

[lehtoj]

Latest stable option works again.

[lehtoj]

I only now realized Windows installer has its own repo. Oops, sorry.

[chyndman]

@KeeperB5 no problem, I've created a new thread at elixir-lang/elixir-windows-setup#8 to pick up the discussion. I haven't yet reproduced this issue myself but I want to revisit the code I haven't touched in months anyway, which might shed some light.

@josevalim the CSV changes should not have caused this issue.

[josevalim]

@chyndman good to know, thanks for looking into this! I will close this since we have moved the issue to the appropriate tracker. :)