Please fix PowerShellGetv2 Bug for Powershell Core modules update
还没有人认领这个 Issue。
评估
调研方向
首先查看所引用的 PowerShellGetv2 拉取请求 #592,并在 PowerShell Core 中重现模块更新行为。当最初全局安装的模块在更新后仍保留在全局作用域中,而不是为当前用户重新安装时,即视为完成。
由索引模型根据 Issue 内容生成。
描述
Prerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest released version
- Search the existing issues.
Steps to reproduce
Since this new PowerShellGet module is still not ready and doesn't look like it will be anytime soon (it's more than a year now since I posted the original bug in the old module) I really think the bug in the old module which will reinstall all modules in the user scope instead of the global scope if you update a module should be fixed with my Pull Request there. Could you maybe make this happen even though its not under development any more? You still add other stuff to it apparently, and your own Powershell Core Product still gets delivered with this faulty module and I'm sure it breaks the usage for many people,, maybe without them even knowing.
This is the Bugfix for the old module: https://github.com/PowerShell/PowerShellGetv2/pull/592
I'm adding this Bug here because I don't think you're looking at the bugs of your old module any more.
I think fixing such a major bug with only one line should be doable if you're not able to get the new module out, I have to fix your module manually every time, that can't be it. Please do something about that :/
The fix is also very easy, it's just one line that needs to be fixed.
Expected behavior
Old module should reinstall Powershell Core modules in the global scope if they were originally installed in the global scope.
Actual behavior
Will reinstall ALL Powershell Core modules in the current user scope, even if they were originally installed in the global scope. This will only happen in Powershell Core.
Error details
No response
Environment data
Problem is in module PowerShellGetv2, doesn't depend on any other module.
Visuals
No response
- 主要语言
- C#
- 星标
- 576
- 派生
- 114
- 平均合并
- 1 天 2 小时
- 30 天内合并 PR
- 7
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
PowerShell/PSResourceGet 的其他 Issue
-
Create parent directories only after the containment check in InstallHelper.TryExtractToDirectory 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
PowerShell/PSResourceGet#2056 ·
-
feature_request
难度 2/5 1-3 小时 新手友好度 68/100
PowerShell/PSResourceGet#2013 · 3 条评论 ·
-
Needs-Triage
难度 3/5 1-2 天 新手友好度 68/100
PowerShell/PSResourceGet#2055 ·
-
Needs-Triage
难度 3/5 1-2 天 新手友好度 72/100
PowerShell/PSResourceGet#2054 ·
-
(dsc): Export ignores `--input` filter for `Repository` and `PSResourceList` on DSC 3.3.* or above 未关闭Needs-Triage
难度 3/5 1-2 天 新手友好度 72/100
PowerShell/PSResourceGet#2053 ·
查看 PowerShell/PSResourceGet 的全部 Issue
相似的 Issue
-
bug documentation frontend
难度 2/5 1-3 小时 新手友好度 72/100
azurenoops/spin_agent#975 ·
-
难度 2/5 1-3 小时 新手友好度 86/100
-
:watch: Not Triaged 11.0 fundamentals/subsvc
难度 2/5 1-3 小时 新手友好度 92/100
dotnet/AspNetCore.Docs#37699 ·
-
难度 2/5 1-3 小时 新手友好度 72/100
SubtitleEdit/subtitleedit#15108 · 1 条评论 ·
-
area/docs-content Bug pulumi/docs
难度 1/5 1-3 小时 新手友好度 94/100