Can't update pkg due to chocolatey-core.extension version mismatch #1956
Comments
|
same error occurring with |
|
There was an issue with chocolatey-core.extension. But for you this might be that you have two versions of chocolatey-core.extension installed. We've seen that before, and it causes the issue you have. But this bothers me a bit - So it appears it might be environmental for your environment that is holding to an exact version. Can you run the scripts at https://chocolatey.org/docs/troubleshooting#already-referencing-a-newer-version-of-packagename and https://chocolatey.org/docs/troubleshooting#chocolatey-is-attempting-to-downgrade-a-package-that-is-a-dependency-of-another-package-on-upgrade ? |
|
Had the same problem today w/ Script 1C:\Users\Brandon> Get-ChildItem -Path "$env:ChocolateyInstall\lib" -Recurse -Filter "*.nupkg" | Where-Object {
Script 2C:\Users\Brandon> $nuspecs = gci $env:ChocolateyInstall\lib -recurse -filter *.nuspec
For now, I'm getting around this problem by doing |
|
Any update on this? Seeing it every time w/ |
|
I experienced the same problem when I tried to upgrade git from version 2.26.0 to latest (2.27.0). I mentioned it on Gitter in channel chocolatey/chocolatey.org. I ran the command @pauby helped me with running In the chocolatey.log I found the same strange dependency problem mentioned earlier in this issue: See dependency |
|
still happening |
bc3tech
changed the title
|
Just to add a data point, I'm also running into this re both git and git.install. |
|
4/22/2022... still happening for me too... This fixed it for me. |
|
Happens to me too. However, I worked around it successfully by using |
|
Happens to me too, for half of the packages I've installed. |
This commit updates the ChocolateyLocalPackageRepository to allow a property being set which allows our code to control whether any directories that are versioned (side by side installed) to be ignored. This is done to prevent NuGet Core throwing an error when it finds multiple package versions of the same package being installed.
|
Yeah, I'm seeing this now on a bunch of packages: |
|
Same issue, couldn't update serveral packages because of conflict between I was able to install all updates, by using the choco upgrade all -i -y |
…o-chocolatey-coreextension-version-mismatch (#1956) Fix packages not being upgraded if SxS installations are available
This commit updates the ChocolateyLocalPackageRepository to allow a property being set which allows our code to control whether any directories that are versioned (side by side installed) to be ignored. This is done to prevent NuGet Core throwing an error when it finds multiple package versions of the same package being installed.
|
@AdmiringWorm @TheCakeIsNaOH @pauby following discussions, I have backed out the changes that were associated with this issue in #2726 The reason for this is that integration tests began failing after these changes were pulled in, namely:
This is due to the fact that the versioned folders are for side by side installations are now ignored, and attempting to update a versioned folder, it doesn't happen, resulting in this output:
Which is quite confusing. We need to decide whether this is now correct and if it is, this associated changes need to be treated as a breaking change and this issue would need to be slated for 2.0.0 rather than 1.2.0. |
|
Based on discussions within the team, we have decided to close this close as not being implemented. This is due to the fact that in the longer term support for side by side installations is going to be removed (in version 2.0.0). There are numerous edge cases when trying to deal with SxS installs, all of which can be mitigated by using separate package ids for differernt package versions, i.e. python2, python3, python, etc. See this issue where SxS option is set to be disabled in 1.2.0 of Chocolatey CLI: #2787 |
Can you help us understand how this issue and SxS installations are related? I'm not seeing anything explaining this, and given myself and many others were seeing the problem not solely when attempting a SxS install, I'm curious to know more. Thanks |
In your original issue report, you stated that:
So SxS installations are related to this issue. The only way that we have been able to replicate this issue, is when SxS installations are in play. If you are able to provide a set of reproducible steps where this issue does happen, and SxS installations aren't involved then we will happily look into it further, but based on the reported issue, and our own internal testing, we feel that there is nothing left to be done here given the direction that we are planning on going. |
I've just run into this, and after more investigation than I'd like, I realised that it was because I've got two side-by-side versions of Python. This isn't Python 2 and 3, but two different versions of 3. Python's versioning scheme allows them to make breaking changes and only increment the second number, so Python 3.10 doesn't run all code that was valid under Python 3.9 etc. (although that specific release only intentionally broke part of the C API rather than the language itself). I know Ruby works the same way. Is it really Chocolatey's preference that side by side installs are accomplished by having a separate package for |
Simply put, yes. While this might not feel like the right way to go about it, from a pure implementation point of view, it is the correct answer. Work has already began in doing this work here: chocolatey-community/chocolatey-packages#1993 |
|
Fair enough. The example of Python 2 vs 3 had me worried that this hadn't been thought through. |
|
For the googlers: Follow-up at #3234. |
What You Are Seeing?
Trying to upgrade
dotnetcoreand receiving multiple errors like:What is Expected?
dotnetcoreshould upgradeHow Did You Get This To Happen? (Steps to Reproduce)
Machine had
dotnetcorev3.0.0 on it (installed a while ago)Today, I did
cinst dotnetcore --version 2.2.8 --sxsas I needed v2.2.8 and wanted the side-by-side install.Then I did
cup alland received these errors as chocolatey attempted to updatedotnetcoreto the latest version: v3.0.1Output Log
Full Log Output
The text was updated successfully, but these errors were encountered: