starship: Problems with chocolatey 2.0
Current Behavior
After updating to 1.50.0, Starship fails to start. I recieve the following error:
C:\ProgramData\chocolatey\lib\starship\tools\starship.exe: The term 'C:\ProgramData\chocolatey\lib\starship\tools\starship.exe' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
Expected Behavior
Starship continues to work.
Additional context/Screenshots
- I tried uninstall and reinstalling without success.
$ choco install starship
...
starship v1.15.0 [Approved]
starship package files install completed. Performing other installation steps.
The install of starship was successful.
Software installed to 'C:\ProgramData\chocolatey\lib\starship'
- I tried downgrading to the previous
1.14.2version without success.
Possible Solution
Recently, I updated chocolatey to version 2.0.0. After this update, and installing starship:
- Choco says it installs to
C:\ProgramData\chocolatey\lib\starship - Windows Explorer says the file is located at
C:\Program Files\starship\bin\starship.exe Invoke-Expression (&starship init powershell)tries to runC:\ProgramData\chocolatey\lib\starship\tools\starship.exe
Environment
- Starship version: 1.15.0
- Powershell version: 7.3.4
- Operating system: Windows 10.0.19045
- Terminal emulator: Windows Terminal 1.16.10261.0
- Git Commit Hash:
- Branch/Tag: master
- Rust Version: rustc 1.70.0 (90c541806 2023-05-31)
- Rust channel: stable-x86_64-pc-windows-msvc release
- Build Time: 2023-06-06 14:43:30 +00:00
Relevant Shell Configuration
<unknown config>
Starship Configuration
Removed config file but still occures.
About this issue
- Original URL
- State: closed
- Created a year ago
- Reactions: 1
- Comments: 19 (3 by maintainers)
Uninstalling
starshipand switching tostarship.installorstarship.portableshould also work. Please also consider switching to winget. This sounds like a bug in chocolatey 2.0 please try to report the bug there as well.