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
Regression in PowerShell 7.4.2 on macOS prevents starting due to incorrect capitalization of file names on case sensitive file systems #21521
Comments
This looks like a problem with the tar
Also looks like a problem with the pkg
|
Doing a build of 7.4.2 results in the correct naming of the library, so it does seem like the casing is being changed during packaging. I don't see anything in the packaging script that would convert the casing to lower. cc @adityapatwardhan @TravisEz13 The .pkg results in the correct casing so it looks like just a problem in the tgz |
Homebrew uses the pkg: Taking the build from https://github.com/PowerShell/PowerShell/releases/download/v7.4.2/powershell-7.4.2-osx-arm64.pkg, I'm seeing the same result that @rhubarb-geek-nz already mentioned:
If your local build has the correct naming, that suggests there is something different between your local build and the release publishing pipeline? It's the same for powershell-7.4.2-osx-x64.pkg btw. |
The mac tgz package is built here which simply relies the packaging module. The copying of the files is done here and I don't see anything that would have changed the casing. If you are using a case-sensitive filesystem on macOS, if you just |
that works just fine |
Prerequisites
Steps to reproduce
Reproduction requires a case-sensitive file system.
I'm experiencing this issue on macOS 14.4.1 (23E224) on ARM.
This is a regression since 7.4.1, reinstalling 7.4.1 via Homebrew works fine:
On 7.4.1,
/usr/local/microsoft/powershell/7/libsystem.native.dylib
does not exist, but/usr/local/microsoft/powershell/7/libSystem.Native.dylib
does.Diff of files in
/usr/local/microsoft/powershell/7
Expected behavior
Actual behavior
Error details
No response
Environment data
Visuals
No response
The text was updated successfully, but these errors were encountered: