-
Notifications
You must be signed in to change notification settings - Fork 906
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to target version 3.1.0 of Chocolatey.NuGet.Client assemblies #508
Comments
This will require .NET 4.5 for the upgrade to a v3 version of NuGet so this will need to move to |
Hi ferventcoder, |
It is definitely a bit early. No estimate yet on this. |
Just wondered if there is any update on when this might be fixed? |
Looking at late 2017 depending on where it falls in prioritization. Right now it is a few back on the list. We have a pretty aggressive schedule so it could be done in 2017 but it may fall back to 2018. |
Hi @ferventcoder, |
@timbrown5 Note the Milestone - that gives you the best idea on where things are. It's definitely scheduled, but priorities shift based on customer needs, etc. |
What is the current version of NuGet used by Chocolatey? The error is this one:
|
@eriviere Chocolatey in what version? It is 2.11, but we're moving it up to 2.14 soon. Hopefully that will make the move up to v3 better. |
…tion This commit updates the file snapshot service to honor version normalization with fallbacks to old version methods. This is done as we are moving towards normalizing version numbers in most of the code, which causes a conflict when installing, upgrading or uninstalling packages that sometimes it would use non-normalized version number, and other times it would use normalized version numbers. Now with this change it will prefer to use normalized version number, but will continue to read/update package versions that was installed using non-normalized version numbers.
This commit updates the uninstall process to ensure that the nupkg file is removed, even in the cases where only partial file removals has happened. This will prevent the package from being listed as installed when partial removal is done. While the original code does not pose any problems with normal usage of CLI, it will not remove the nuget packages when the package has been modified, like what Licensed Extension does when optimizing installations.
…tion This commit updates the file snapshot service to honor version normalization with fallbacks to old version methods. This is done as we are moving towards normalizing version numbers in most of the code, which causes a conflict when installing, upgrading or uninstalling packages that sometimes it would use non-normalized version number, and other times it would use normalized version numbers. Now with this change it will prefer to use normalized version number, but will continue to read/update package versions that was installed using non-normalized version numbers.
This commit updates the uninstall process to ensure that the nupkg file is removed, even in the cases where only partial file removals has happened. This will prevent the package from being listed as installed when partial removal is done. While the original code does not pose any problems with normal usage of CLI, it will not remove the nuget packages when the package has been modified, like what Licensed Extension does when optimizing installations.
(#508) Fix some files not being removed during uninstall/upgrade
This commit updates the Equals comparisons in the nuget service to be cake insensitive. This is done as without this change the user will always have to pass in the identifier in the exact casing that is returned from the nuget server, causing issues especially during upgrade scenarios. Additionally, Equals and Compare methods has been added to the banned API list to prevent the use of these without specifying a StringComparison.
This commit updates the Equals comparisons in the nuget service to be case insensitive. This is done as without this change the user will always have to pass in the identifier in the exact casing that is returned from the nuget server, causing issues especially during upgrade scenarios. Additionally, Equals and Compare methods has been added to the banned API list to prevent the use of these without specifying a StringComparison.
This commit updates the Equals comparisons in the nuget service to be case insensitive. This is done as without this change the user will always have to pass in the identifier in the exact casing that is returned from the nuget server, causing issues especially during upgrade scenarios. Additionally, Equals and Compare methods has been added to the banned API list to prevent the use of these without specifying a StringComparison.
(#508) Do case insensitive comparison on package ids
This commit removes any uses of the custom public tuple method, and replaces all its uses with the new Resource endpoint class that caches previously used endpoints.
This commit updates the FindPackage method we use when installing and acquiring information about a package to properly handle feeds when there is a mix of feeds that support v2 odata queries, and when there is one or more feeds that only support v3 feeds without the fallback to v2 odata APIs.
(#508) Fix v3 feeds mixed with v2 feeds not finding packages
When we first brought in the new NuGet.Client, a change was made to how the callback for the HandlePackageResult was done. Previously, this didn't receive a ChocolateyConfiguration object from the callback, but then it did. As a result, the wrong instance of the ChocolateyConfiguration object was sent along to continue the operation, which meant all the environment information had not been set correctly. This caused a problem when trying to install the cygwin package since there is a check against what operating system the process is being run on, which hadn't been set correctly. This came up when running choco install chere --source cygwin, which failed to install Cygwin correctly. This change has been in the code base a while, and it was only when testing the installation of a package from an alternative source that this came up.
* release/2.0.0: (422 commits) (maint) Update Chocolatey.NuGet.Client version (build) Update GRM Template to add full stop. (build) Update GRM config for BuildAutomation tag (#508) Ensure correct configuration object is used (tests) Use nuspec for version normalization tests (tests) Tag version normalization Pester tests (#158) Restore --source in tab completion for list (#158) Refactoring based on pairing session (#158) Restore --source for choco list (maint) Add vscode settings file (maint) Changes during pairing session (tests) Add non-normalized version Pester tests (maint) Update testing vagrant for granular runs (maint) Update Pester test for Pester v5 norms (#1174) Add non-normalized packages for tests (#508) Fix v3 feeds mixed with v2 feeds not finding packages (#508) Do case insensitive comparison on package ids (maint) Remove prerelease warnings from the nuspec (maint/doc) Amend GenerateDocs for list/search split (#2902) Ensure PowerShell tasks use SystemDefault TLS ...
🎉 This issue has been resolved in version 2.0.0 🎉 The release is available on: Your GitReleaseManager bot 📦🚀 |
* master: (148 commits) (#948) Add user as sensitive argument (#158) Error on list -lo without -r (doc) Update description of page-size argument (#158) Restore -lo warning when not using -r (#158) Update tests (#158) Relegate the -lo warning to log-file-only (#3165) Update count method to support nuget service (maint) Update Chocolatey.NuGet.Client version (build) Update GRM Template to add full stop. (build) Update GRM config for BuildAutomation tag (#508) Ensure correct configuration object is used (tests) Use nuspec for version normalization tests (tests) Tag version normalization Pester tests (#158) Restore --source in tab completion for list (#158) Refactoring based on pairing session (#158) Restore --source for choco list (maint) Add vscode settings file (maint) Changes during pairing session (tests) Add non-normalized version Pester tests (maint) Update testing vagrant for granular runs ...
This helps ensure that package IDs are handled in a case insensitive manner.
This helps ensure that package IDs are handled in a case insensitive manner.
This helps ensure that package IDs are handled in a case insensitive manner.
This helps ensure that package IDs are handled in a case insensitive manner.
This helps ensure that package IDs are handled in a case insensitive manner.
This helps ensure that package IDs are handled in a case insensitive manner.
This helps ensure that package IDs are handled in a case insensitive manner.
NuGet/Home#1839
Upgrade NuGet.Core to a version that better handles conflict resolution
May fix #507
May fix #227
May fix #116
May fix #1158
Relates to #2592 - support for embedded icons
References
The text was updated successfully, but these errors were encountered: