Arch Linux User Repository

@Samwell9854 Unfortunately, I cannot reproduce this. Regardless, I've removed the test in 7.4.1-2. Thanks for reporting.

New install, v7.4.1, same issue as with @ReinekeFuchs.

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.

Until it is fixed, you can do this for now.

Example with yay:

yay --editmenu -S powershell

Then add the following line at the end inside the check() function, right after the other 'rm test/...' lines

rm test/powershell/Modules/Microsoft.PowerShell.Management/Start-Process.Tests.ps1

Alternatively, manually edit the PKGBUILD file, then run makepkg -si

Upgrading from 7.3.7-1 -> 7.3.8-1

Tests completed in 428.31s
Tests Passed: 10708, Failed: 1, Skipped: 1911, Pending: 367, Inconclusive: 2
TEST FAILURES
Description: Doesn't run the login profile when -Login not used
Name:        ConsoleHost unit tests.-Login pwsh switch.Doesn't run the login profile when -Login not used
message:
Expected $null or empty, but got 9d3795e2-2190-467c-8a1d-92321b183a1e.
stack-trace:
at <ScriptBlock>, /home/klieber/.cache/yay/powershell/src/PowerShell-7.3.8/test/powershell/Host/ConsoleHost.Tests.ps1: line 287
287:             $result | Should -BeNullOrEmpty
Exception: 1 tests in test/powershell failed
==> ERROR: A failure occurred in check().
    Aborting...
 -> error making: powershell-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
powershell - exit status 4

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: ';'

stack-trace:

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().

Aborting...

@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.

@carsme thanks for adding those modules!

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

Without it: https://paste.ee/r/IuG27/0

With it: https://paste.ee/d/R72Bp/0

@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.

See: https://aur.archlinux.org/cgit/aur.git/commit/PKGBUILD?h=powershell&id=58c58ea7292cf02c6eb1c2d4961ddc84326cff77

So, let's ask to @kylesferrazza @carsme

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

@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"?