Restore trying the wrong source, and failing if that is unavailable #13950
Labels
Area:NewDependencyResolver
Issues related to the new dependency graph resolver
Type:Bug
WaitingForCustomer
Applied when a NuGet triage person needs more info from the OP
NuGet Product Used
dotnet.exe
Product Version
9.0.100
Worked before?
Version 8, not sure exactly which
Impact
I'm unable to use this version
Repro Steps & Context
I have a GitHub repo that generates various Nuget packages, one of which uses Telerik components for Blazor.
The
nuget.config
file for the repo can be seen here, and the YAML file for the master branch can be seen here.I have built this repo (and consequently published the packages) many times, and have never had problems (other than my own of course!). However, I pushed some changes today, and the build failed.
For every package referenced in the repo, I get lines like the following...
Notice that the package in question is not a Telerik one, so I have no idea why it's looking on the Telerik feed. Also, the Telerik feed is the second one in the
nuget.config
file, so I would have expected it to check the nuget feed first. Furthermore, if I open the package manager in Visual Studio and look for packages on the Telerik feed, it finds them fine, which implies that the feed is working fine.I tried commenting out the line in
nuget.config
that references the Telerik feed, but that failed...I tried adding `` --ignore-failed-sources
to each
dotnet restore` line in the `.yaml` file, but that didn't help. The build failed with the same results. Didn't try the nuget feed after the Telerik one failed.Anyone able to advise? I need to publish a new version of a package, but can't.
Please let me know if there is any more info I can add.
Thanks
Verbose Logs
No response
The text was updated successfully, but these errors were encountered: