PowerShell / PowerShell/PSResourceGet

Please fix PowerShellGetv2 Bug for Powershell Core modules update

Aperta
#617 1 commento 1 reazione 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Needs-Attention :wave:
Lingua principale
C#
Stelle
576
Fork
114
Merge medio
1g 2h
PR unite (30g)
7

Descrizione

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

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Direzione di ricerca

Inizia esaminando la pull request #592 di PowerShellGetv2 indicata e riproducendo il comportamento di aggiornamento dei moduli in PowerShell Core. Il lavoro è completato quando i moduli installati originariamente a livello globale rimangono nell’ambito globale dopo l’aggiornamento, invece di essere reinstallati per l’utente corrente.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
powershell
Ambito
cli, tooling
Tipo di issue
Bug
Difficoltà
2/5
Tempo stimato
1-3 ore
Stato di attività
Ferma
Chiarezza
Abbastanza chiara
Idoneità per principianti
35/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.