Nuget Package Version 3.2.1 Broken
See original GitHub issueIssue
The latest version of Amazon.Lambda.Tools (3.2.1), available from Nuget, cannot be installed because the package is missing the DotnetToolSettings.xml
file.
Replication
$ dotnet tool install --global --version 3.2.1 Amazon.Lambda.Tools
Tool 'amazon.lambda.tools' failed to update due to the following:
The settings file in the tool's NuGet package is invalid: Settings file 'DotnetToolSettings.xml' was not found in the package.
Tool 'amazon.lambda.tools' failed to install. Please contact the tool author for assistance.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:7
- Comments:12 (3 by maintainers)
Top Results From Across the Web
NuGet Issues - Updating a package breaks build
NuGet has decided that any attempt to update a package destroys my Solution. I am running Visual Studio 2013 Ultimate w/ Update 3....
Read more >Package upgrade leaves a project in a broken state if the ...
When removing these files NuGet verifies that the contents of the file are the same as the original packages before deleting them. Potentially ......
Read more >NuGet Package Restore not working as expected
When I attempt to use the NuGet Installer command to perform a package ... [12:05:55][restore] Unable to find version '3.2.1' of package ......
Read more >Best Practices for Versioning NuGet Packages in ...
Improperly versioning your NuGet packages can lead to lots of problems. ... headaches and wasted time from confusing and “broken” packages.
Read more >MSB3277: Found conflicts between different versions of ' ...
This error occurs during a build when more than one version of the same dependent ... Framework.dll C:\Users\user\.nuget\packages\microsoft.
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
Version 3.2.2 is out which fixes the problem. I apologize again for this happening.
For those that are curious we have been refreshing our build infrastructure and this was the first release to happen from Linux which triggered a file permission issue with the files that got added to the NuGet package. We will be adding more validations in our release process to ensure this doesn’t happen again. I appreciate all of your support/feedback for these tools.
Codebuild default settings too.
No worries Norm - stuff happens 😊👍
On Fri, Apr 19, 2019, 17:29 psbmiller notifications@github.com wrote: