PowerShell / PowerShell/PSResourceGet

Please fix PowerShellGetv2 Bug for Powershell Core modules update

Open
#617 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Needs-Attention :wave:
Dominant language
C#
Stars
576
Forks
114
Avg merge
1d 2h
Merged PRs (30d)
7

Description

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the referenced PowerShellGetv2 pull request #592 and reproducing the module-update behavior in PowerShell Core. Done means modules originally installed globally remain in the global scope after updating, rather than being reinstalled for the current user.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
cli, tooling
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.