Fail to install Tye CI build 0.11.0
See original GitHub issueOS: Windows 10
Repro Steps:
- Install .NET Core 3.1.
- Install Tye CI build using the command.
dotnet tool install -g Microsoft.Tye --version "0.11.0-*" --add-source https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet5/nuget/v3/index.json
Expect: Succeed to install Tye CI build 0.11.0.
Actual: Fail to install Tye CI build 0.11.0.
Error Info:
C:\WINDOWS\system32>dotnet tool install -g Microsoft.Tye --version "0.11.0-*" --add-source https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet5/nuget/v3/index.json
Welcome to .NET Core 3.1!
---------------------
SDK Version: 3.1.413
Telemetry
---------
The .NET Core tools collect usage data in order to help us improve your experience. It is collected by Microsoft and shared with the community. You can opt-out of telemetry by setting the DOTNET_CLI_TELEMETRY_OPTOUT environment variable to '1' or 'true' using your favorite shell.
Read more about .NET Core CLI Tools telemetry: https://aka.ms/dotnet-cli-telemetry
----------------
Explore documentation: https://aka.ms/dotnet-docs
Report issues and find source on GitHub: https://github.com/dotnet/core
Find out what's new: https://aka.ms/dotnet-whats-new
Learn about the installed HTTPS developer cert: https://aka.ms/aspnet-core-https
Use 'dotnet --help' to see available commands or visit: https://aka.ms/dotnet-cli-docs
Write your first app: https://aka.ms/first-net-core-app
--------------------------------------------------------------------------------------
error NU1102: Unable to find package microsoft.tye with version (>= 0.11.0)
error NU1102: - Found 328 version(s) in https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet5/nuget/v3/index.json [ Nearest version: 0.10.0-alpha.21420.1 ]
error NU1102: - Found 11 version(s) in nuget.org [ Nearest version: 0.10.0-alpha.21420.1 ]
The tool package could not be restored.
Tool 'microsoft.tye' failed to install. This failure may have been caused by:
* You are attempting to install a preview release and did not use the --version option to specify the version.
* A package by this name was found, but it was not a .NET Core tool.
* The required NuGet feed cannot be accessed, perhaps because of an Internet connection problem.
* You mistyped the name of the tool.
For more reasons, including package naming enforcement, visit https://aka.ms/failure-installing-tool
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
tye/docs/getting_started.md at main · dotnet/tye
Tye is a tool that makes developing, testing, and deploying microservices and distributed ... This will install the newest available build from our...
Read more >ruby on rails - An error occurred while installing rugged
But an error occurred while installing rugged : Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native extension. /usr/local/bin ...
Read more >Heroku Deployment Broken
I have some code from the failing build log and the passing build log ... installed netrc-0.11.0 Successfully installed dpl-heroku-1.10.8 ...
Read more >What is the cause of "npm WARN EBADENGINE"?
After downloading and installing the new node, just rerun npm install inside the directory of your project. It sorted my problem,.
Read more >Apache Arrow 0.12.0 Release
Apache Arrow 0.12.0 (20 January 2019) This is a major release covering more than 3 months of development. Download Source Artifacts Binary Artifacts...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@Hylaean I feel you, trust me. 😃 While Tye is absolutely still under active development, it’s admittedly slower than I’d like. Our team has a number of responsibilities, not all of which are as publicly visible as projects like Tye, so not all of our efforts can be seen.
I have proposed https://github.com/dotnet/tye/pull/1218 to fix this. A better solution would be to include this step in the PR validation gates