Package Details: powershell 7.3.7-1

Git Clone URL: (read-only, click to copy)
Package Base: powershell
Description: A cross-platform automation and configuration tool/framework (latest release)
Upstream URL:
Keywords: .net automation microsoft net powershell script scripting shell
Licenses: MIT
Submitter: jsteel
Maintainer: kylesferrazza (richardba, carsme)
Last Packager: carsme
Votes: 80
Popularity: 3.38
First Submitted: 2016-11-26 22:16 (UTC)
Last Updated: 2023-09-20 21:28 (UTC)

Pinned Comments

kylesferrazza commented on 2017-10-26 18:01 (UTC)

Note that the binary is now called "pwsh"

Latest Comments

1 2 3 4 5 6 .. 17 Next › Last »

ReinekeFuchs commented on 2023-09-24 10:13 (UTC) (edited on 2023-09-24 10:14 (UTC) by ReinekeFuchs)

I get this error

Tests Passed: 10708, Failed: 1, Skipped: 1894, Pending: 367, Inconclusive: 2 TEST FAILURES

Description: UseNewEnvironment parameter should reset environment variables for child process

Name: Start-Process.UseNewEnvironment parameter should reset environment variables for child process message:

Expected strings to be the same, but they were different.

Expected length: 3

Actual length: 1

Strings differ at index 1.

Expected: ';ds'

But was: ';'


at <ScriptBlock>, /home/ds/Pakete/powershell/src/PowerShell-7.3.7/test/powershell/Modules/Microsoft.PowerShell.Management/Start-Process.Tests.ps1: line 205

205: Get-Content -LiteralPath $outputFile | Should -BeExactly ";$userName" Exception: 1 tests in test/powershell failed

==> ERROR: A failure occurred in check().


carsme commented on 2023-04-15 16:18 (UTC)

@kylesferrazza, Ah, missed that! Thanks for fixing it so quickly :)

This is most likely related to the switch to building with --no-self-contained instead of --self-contaied.

kylesferrazza commented on 2023-04-15 16:13 (UTC)

@carsme thanks for adding those modules!

It seems dotnet-runtime is a missing runtime dep now?

Without it:

With it:

carsme commented on 2023-04-15 14:31 (UTC) (edited on 2023-04-15 14:31 (UTC) by carsme)

@D3vil0p3r @JakeMoe, I've managed to include the modules that are bundled with the upstream built package (for example PowerShellGet and PSReadLine). Feel free to test.


D3vil0p3r commented on 2023-03-28 22:07 (UTC)

So, let's ask to @kylesferrazza @carsme

JakeMoe commented on 2023-03-28 20:01 (UTC)

@D3vil0p3r I didn't decide anything, it's not my package, I was just asking why I was missing so many modules (including PSReadLine).

D3vil0p3r commented on 2023-03-28 15:02 (UTC)

@JakeMoe thank you for the answer. Ok, I will go on powershell-bin package. One question: why did not you decide to implement the autocompletion and the PSReadLine module also on "powershell" package but only on "powershell-bin"?

JakeMoe commented on 2023-03-27 20:57 (UTC)

@D3vil0p3r I think autocompletion is part of PSReadLine, one of the module I was missing; see my comments and the reply just below your comment.

D3vil0p3r commented on 2023-03-27 19:48 (UTC)

This powershell package does not support autocompletion?

JakeMoe commented on 2023-03-01 21:18 (UTC)

@carsme Cheers for that, I've tried the bin package and it's got PowerShellGet, and Get-PsRepository shows PSGallery. :-) It's also got PSReadLine so tab completion and other features work as well. ;-)