Open gsscoder opened 2 years ago
@gsscoder Can you go back and complete the issue template rather than using freeform?
Analyzing things better I see that the package upgraded is nodejs.install
and not nodejs
. Anyway it seems impossible to pin it.
Tried with:
choco pin add -n="nodejs.install"
choco pin add -n="'nodejs.install'"
I'm able to skipt it using:
choco upgrade all --except="'nodejs.install'"
Feel free to close the issue.
Best regards
@gsscoder What error did you get when trying to pin the package? I have just tried, and it worked fine for me.
From looking at that I wonder if we should have choco
warn about pinning packages that have a corresponding .install
package that isn't being pinned. 🤔
From looking at that I wonder if we should have
choco
warn about pinning packages that have a corresponding.install
package that isn't being pinned. 🤔
Or perhaps a new option that also pins dependencies?
There is a precedence for this type of logic during the uninstall of a package. For example, if I attempt to uninstall notepadplusplus
I get the following:
I think it would be a good addition to do the same with the pin operation is attempted.
I had the same went to C:\ProgramData\chocolatey\lib\nodejs.install\ and removed nodejs.install.nupkg file then the choco commands started to work
What You Are Seeing?
choco
command upgraded a pinned package.nodejs
pinned at version12.13.0
. Previous runs of choco upgrade all behavied correctly.What is Expected?
I'm expecting this to not happen: pinned package NOT upgraded.
How Did You Get This To Happen? (Steps to Reproduce)
Previously:
Now:
choco upgrade all
Output Log