Upgrading a package won't work as depending versions are not resolved properly #1408
Comments
|
@NicoHaase that is definitely incorrect behavior. I think what you may be running into is multiple nupkgs confusing choco - take a look at https://chocolatey.org/docs/troubleshooting#already-referencing-a-newer-version-of-packagename and see if you have any stray nupkgs sitting around. |
|
Nope, that did not help. I used the script to remove these possibly broken files, but the update is still not possible. The verbose log of actions looks similar to the posted one |
|
Actually I wonder if you have another package that is restricting the version of git and Chocolatey it trying to correct that during upgrade. |
|
Output of |
|
There you are:
|
|
@NicoHaase okay, I have something new for you to run: $nuspecs = gci $env:ChocolateyInstall\lib -recurse -filter *.nuspec
foreach ($nuspec in $nuspecs) {
[xml]$nuspecContent = Get-Content $nuspec.FullName
$dependencies = $nuspecContent.package.metadata.dependencies.dependency
if ($dependencies -ne $null) {
Write-Host "$($nuspecContent.package.metadata.id) v$($nuspecContent.package.metadata.version) dependencies:"
foreach ($dependency in $dependencies) {
$dependencyOperator = ">="
if (!$dependency.version) { $dependencyOperator = "" }
elseif ($dependency.version.Contains('[')) { $dependencyOperator = "=" }
$dependencyVersion = $dependency.version
if (!$dependencyVersion) { $dependencyVersion = "{Any Version}"}
Write-Host " - $($dependency.id) $dependencyOperator $($dependencyVersion)"
}
}
} |
|
That's the result: |
|
Another thought here - there may be a local cache of nupkgs that is not getting cleared. Are you familiar with those locations? |
|
The cache is supposed to be ignored, but let's ensure it is not causing the issue. |
|
How can I ensure that? Which folders should I clear or rename? |
|
In an explorer window, paste |
|
I cleared the folder with cached nupkg-files and the whole %TEMP% folder, but the update still won't run :( |
|
Deeper checks now:
Provide both of those (you may want to scrub both first to ensure no sensitive data is exposed). |
|
That's it :) Trace outputWhat I find interesting is that the script outputting dependencies writes that docker-toolbox expects git.install >= 2.5.0 (so any version after that), while the installer wants to install version 2.5.0 and explicitly no other. How to work with Fiddler? I don't know that tool |
|
@ferventcoder do you have any more hints about what could have gone wrong? |
|
@ferventcoder any news on this? The package was updated to 18.01.0, but updating still fails |
|
@NicoHaase fiddler is at https://www.telerik.com/fiddler. |
|
This is an error in several places I believe. Look at #227 |
|
I have tried and tried and tried to reproduce this, and the closest I can get is this error occurring with @NicoHaase is this still an issue for you? Are you currently able to reproduce this behaviour, and if so, are you able to provide steps to reproduce it on a fresh system (or in Windows Sandbox). |
|
@corbob this bug report is nearly six years old, and I'm no longer using Chocolatey, so I can't tell you whether this is resolved or not |
|
Thank you for the update @NicoHaase. I'll close off this issue. Should it happen again we can always re-open or open a new issue. |
corbob
added
Invalid / Not Issue / No repro / Not Implementing
and removed
0 - Waiting on User
labels
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What You Are Seeing?
Update of docker-toolbox tries to install old version of git.install which should be an "update"
What is Expected?
Updating docker-toolbox won't downgrade a recent git installation
How Did You Get This To Happen? (Steps to Reproduce)
Installed packages (amongst others):
docker-toolbox v17.06.0
git v 2.14.1
git.install v2.14.1
chocolatey 0.10.8
chocolatey-core.extension 1.3.1
chocolatey 0.9.9.8
Ran
cup allOutput Log
The text was updated successfully, but these errors were encountered: