Closed lebarsfa closed 1 year ago
Can you go back to the above comment and add both a list of installed packages and the log files that cover the issue? If they are long, please add them as a gist and link to them from the above. Please don't add them in a new comment, but edit the above one and add them.
Please also add the OS version being used.
Those are required for us to look at this further.
OK, I added more details to be able to reproduce the problem.
@lebarsfa it looks like you have included the output from the console, this is not what we are after. But rather, the contents of the log file will be located here: %ChocolateyInstall%\logs\chocolatey.log
(there may be numbered files as well).
Please upload the contents of this file to https://gist.github.com
and link to the uploaded content in your initial post.
Sorry, I added it to the top of the Output Log section.
I confirm I was able to reproduce this issue.
A new version of Chocolatey CLI (v2.1.0-alpha-20230608) has been released which aims to address this issue. You can find the release notes here:
https://docs.chocolatey.org/en-us/choco/release-notes#alpha-20230608-june-8-2023
And the package here:
https://community.chocolatey.org/packages/chocolatey/2.1.0-alpha-20230608
You should be able to upgrade to this package version using:
choco upgrade chocolatey --pre
If you could take this for a spin, and verify that the issue is now resolved, that would be very helpful.
Thank you, I confirm the problem seems to be solved.
I had the seemingly same issue : Choco was mixing neovim with vim, that is, Choco would remove pin for vim, but then still consider it to be pinned. I upgraded Choco with choco upgrade chocolatey --pre
. All is fixed now, many thanks. You should push the preview to production version.
@Gitoo22 said... You should push the preview to production version.
Yes, that is the plan. There is still a couple of open issues in the 2.1.0 milestone that we need to complete before we push a new stable version of Chocolatey CLI.
:tada: This issue has been resolved in version 2.1.0 :tada:
The release is available on:
Your GitReleaseManager bot :package::rocket:
Checklist
What You Are Seeing?
I think this example is clear enough:
This looks inconsistent and in the end I cannot uninstall mingw since it is still pinned.
What is Expected?
Remove the pin of the correct package and have consistent output in the command.
How Did You Get This To Happen?
To reproduce on a clean Windows (see also output log below):
System Details
Installed Packages
Output Log
See also https://gist.github.com/lebarsfa/f3073eafbd7713d8c3222dd628ec512b/raw/3d28b4295999bf1bb6427e0af19029e6c313a40b/chocolatey.log
Additional Context
No response