-
Notifications
You must be signed in to change notification settings - Fork 907
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
Ensure that the client version used when querying a repository is the version of the underlying NuGet.Client library #1935
Comments
The package has nested dependencies and then you get that error.
Anyway the problem is correctly described in ticket 194: chocolatey presents itself as a nuget client with an old version number. |
Is #194 closed? |
Looks like it is. Please run your command again with |
|
Quick question here - you are using Chocolatey to install something from NuGet - which may just be DLLs. I'm assuming this is on purpose? |
Yes it is on purpose. Basically the main chocolatey package a several nested dependencies and one of them wants a nuget package. |
So basically what can I do? Is there a workaround? |
Same problem for me too.
Ran into following by: My nuget exe installed from chocolatey I didn't understand what is NuGet client version '2.12' when i have version 5.4.0 What I doing wrong? |
The problem is there it has not gone away, how can I solve it? |
I have same poroblem.
Do you have any ideas? |
As a workaround, does using |
Yes, |
@RadmirT as mentioned in the related issue, the reason that this happens is due to the fact that we are embedding a specific version of NuGet.Core into Chocolatey, and it is its version number that is presented when talking to nuget.org. The package that you are trying to install must use "something" (perhaps in the metadata that it uses) that requires a newer client version in order to understand/interpret it. As a result, there is nothing that we can currently do to workaround this. At some point in the future, we will be updating the NuGet.Core library that we are using within Chocolatey, but that isn't going to happen soon. As such, the recommendation would be to use nuget.exe for placing this package where it is required. |
These added tests ensure that a minClientVersion attribute that is higher than the Chocolatey and NuGet assembly versions does not prevent installation or packing.
This both ensures that the user agent is set, when NuGet sources are configured and that it uses the upstream version of NuGet that the NuGet assembles are based on. This same version is used in other areas as well, like minClientVersion, so it applies to multiple areas.
These added tests ensure that a minClientVersion attribute that is higher than the Chocolatey and NuGet assembly versions does not prevent installation or packing.
This both ensures that the user agent is set, when NuGet sources are configured and that it uses the upstream version of NuGet that the NuGet assembles are based on. This same version is used in other areas as well, like minClientVersion, so it applies to multiple areas.
These added tests ensure that a minClientVersion attribute that is higher than the Chocolatey and NuGet assembly versions does not prevent installation or packing.
This both ensures that the user agent is set, when NuGet sources are configured and that it uses the upstream version of NuGet that the NuGet assembles are based on. This same version is used in other areas as well, like minClientVersion, so it applies to multiple areas.
This works with in the latest alpha version 2.0.0-alpha-20230307.
|
These added tests ensure that a minClientVersion attribute that is higher than the Chocolatey and NuGet assembly versions does not prevent installation or packing.
This both ensures that the user agent is set, when NuGet sources are configured and that it uses the upstream version of NuGet that the NuGet assembles are based on. This same version is used in other areas as well, like minClientVersion, so it applies to multiple areas.
That agrees with my testing. See #2999 which is a PR that adds tests for this. |
These added tests ensure that a minClientVersion attribute that is higher than the Chocolatey and NuGet assembly versions does not prevent installation or packing.
This both ensures that the user agent is set, when NuGet sources are configured and that it uses the upstream version of NuGet that the NuGet assembles are based on. This same version is used in other areas as well, like minClientVersion, so it applies to multiple areas.
This both ensures that the user agent is set, when NuGet sources are configured and that it uses the upstream version of NuGet that the NuGet assembles are based on. This same version is used in other areas as well, like minClientVersion, so it applies to multiple areas.
This both ensures that the user agent is set, when NuGet sources are configured and that it uses the upstream version of NuGet that the NuGet assembles are based on. This same version is used in other areas as well, like minClientVersion, so it applies to multiple areas.
This both ensures that the user agent is set, when NuGet sources are configured and that it uses the upstream version of NuGet that the NuGet assembles are based on. This same version is used in other areas as well, like minClientVersion, so it applies to multiple areas.
These added tests ensure that a minClientVersion attribute that is higher than the Chocolatey and NuGet assembly versions does not prevent installation or packing.
This both ensures that the user agent is set, when NuGet sources are configured and that it uses the upstream version of NuGet that the NuGet assembles are based on. This same version is used in other areas as well, like minClientVersion, so it applies to multiple areas.
This both ensures that the user agent is set, when NuGet sources are configured and that it uses the upstream version of NuGet that the NuGet assembles are based on. This same version is used in other areas as well, like minClientVersion, so it applies to multiple areas.
(#1935) Add tests to ensure upstream NuGet version is used.
…ests (chocolatey#1935) Add tests to ensure upstream NuGet version is used.
🎉 This issue has been resolved in version 2.0.0 🎉 The release is available on: Your GitReleaseManager bot 📦🚀 |
I have a problem similar of the one in ticket 194.
I have received this message during installation of a software with choco install:
I have looked at ticket 194 but I need more help to solve it again.
So please tell me how to solve it.
Thanks,
Mario
The text was updated successfully, but these errors were encountered: