Closed LoopedBard3 closed 10 months ago
This is still an issue with the rc.2.23456.1 version.
@rbhanda can you check if something's up with the release pipeline for the nightly builds?
The -Version
flag only downloads publicly released versions, and there aren't available builds for RC2 yet. If you use the 'daily'
Quality argument with the 8.0
channel, however, you will download and use the latest RC2 nightlies from this installer repo.
Using version 8.0.100-rc.2.23456.1 seems to be working now while rc.2.23455.25 still fails, does that mean that there are now available builds for RC2 starting with rc.2.23456.1 and it was just transient error?
@baronfel @LoopedBard3
We check the package exists on both the public and nightly feeds: https://dotnetbuilds.azureedge.net/public
, and https://dotnetcli.azureedge.net/dotnet
Then use this feed a the specific version
.\\dotnet-install.ps1 -Version {sdkVersion} -NoPath -SkipNonVersionedFiles -InstallDir {dotnetHome} -AzureFeed {dotnetFeed}
I think it's the correct way to get the packages, but this specific version didn't get published correctly.
Hi @rbhanda,
Could you check if the links were generated for the requested package?
I am not sure if I can do anything here. https://dotnetcli.azureedge.net/dotnet/Sdk/8.0.100-rc.2.23455.25/dotnet-sdk-8.0.100-rc.2.23455.25-win-arm64.zip - this link will not exist until RC2 is available publicly.
close as not a bug.
When attempting to use the dotnet-install script to install the latest dotnet version (8.0.100-rc.2.23455.25 as of writing) on a Windows Arm64 machine, the install ends up failing with 404 errors for one of the links. Here is part of an error:
The error repeats a few times before exiting the install. Attempting to access this link manually also returns a 404/blob does not exist error.