-
-
Notifications
You must be signed in to change notification settings - Fork 811
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
Help! Chocolatey Upgrade Issues #272
Comments
Related: chocolatey/choco#327 |
I think it would be expected to use PowerShellGet >= v5. I think it is reasonable to ask folks to install PackageManagement for v3/v4 (vs installing Chocolatey). Unfortunately, for v2 there will be no PackageManagement solution from the PowerShell team. Maybe we just make do with using Chocolatey for PS v2 users? |
I'm fine with this, since we're dropping v2 support for 1.0. I suppose it wouldn't hurt to try to fix the Chocolatey upgrade process before 0.7 drops? I have never bothered with Chocolatey prereleases, but it seems like a good idea for this big release. |
I believe this is all resolved by #358. If anyone stumbles on this using posh-git 0.7 or newer, please leave a note (or open a new issue). |
I'd love some help figuring out why Chocolatey upgrades are failing. I'm barely familiar with how the posh-git Chocolatey install works, but it feels way overcomplicated, not very PowerShell-y, and out of date with how Chocolatey has evolved.
Does anyone know of a similar PowerShell module package that installs/upgrades cleanly? Or would it make sense to take a dependency on newer PowerShell package management stuff to DRY up the various ways people are now getting posh-git?
https://chocolatey.org/packages/poshgit#comment-2569064630
https://chocolatey.org/packages/poshgit#comment-2571834761
The text was updated successfully, but these errors were encountered: