Skip to content

Install-PSResource with NoClobber produces command conflict when there is none #204

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

Closed
ThomasNieto opened this issue Jul 28, 2020 · 1 comment · Fixed by #509
Closed

Comments

@ThomasNieto
Copy link
Contributor

ThomasNieto commented Jul 28, 2020

During Install-PSResource with -NoClobber produces an error for a command conflict when there is none.

Steps to reproduce.

Get-Command *acme* # returns nothing

Install-PSResource acme-ps -TrustRepository -NoClobber -Verbose
VERBOSE: Current user scope installation path: C:\Users\Thomas\Documents\WindowsPowerShell
VERBOSE: All users scope installation path: C:\Program Files\WindowsPowerShell
VERBOSE: Scope is: CurrentUser
Install-PSResource: Command(s) with name(s) 'System.Linq.Enumerable+WhereEnumerableIterator`1[System.Management.Automation.PSObject]' is already available on this system. Installing 'ACME-PS' may override the existing command. If you still want to install 'ACME-PS', remove the -NoClobber parameter.
@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.91. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@issue-label-bot issue-label-bot bot added the Issue-Bug Something isn't working label Jul 28, 2020
@ThomasNieto ThomasNieto changed the title Install-PSResource does not honor DefaultCommandPrefix during NoClobber Install-PSResource with NoClobber produces command conflict when there is none Jul 31, 2020
@SydneyhSmith SydneyhSmith added this to the 3.0-Resolved milestone Sep 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants