Powershell: Powershell not found

[dustinmoris]

The latest Powershell build doesn't seem to be able to execute a Powershell script any longer.

I have two identical builds where one has successfully finished with an older version of Powershell (6.0.0-beta.8-1.ubuntu.14.04) and the other fails with the latest version (6.0.0-beta.9-1.ubuntu.14.04):

Successful build
Failed build

Please find all relevant details from the full build logs above.

Do I need to change anything? It seems like basic functionality is broken now.

[SteveL-MSFT]

I believe the problem is that we're in the middle of the beta.9 release with some packages published (which renamed the exe to pwsh), but the full release isn't done yet. This should be resolved by tomorrow once the beta.9 release is complete.

[mmattes]

See for a temporary fix by creating a link

[daxian-dbw]

@dustinmoris The PowerShell Core executable was renamed to be pwsh starting from beta.9 release, and that's why the Travis CI failed with the new package. Please see the issue #4214 for the discussion details.

[SteveL-MSFT]

This should be working now since we've completed the beta.9 release

[sandersaares]

I confirm that I can reproduce the issue - using the "powershell" command does not work, which broke quite a lot of our automation.

[SteveL-MSFT]

@sandersaares just to be clear, this issue is specifically about a race condition with our Travis-CI script and publishing of beta.9. Dependency on powershell exe name should be discussed under https://github.com/PowerShell/PowerShell/issues/4214 although I would suggest creating a symlink to pwsh if you have tooling that expects powershell

[jgreat]

Please update the .deb package to include a link from /opt/microsoft/powershell/6.0.0-beta.9/pwsh to /usr/bin/powershell. This is breaking VS Code and compatibility between Linux and Windows scripting.