rhubarb-geek-nz
rhubarb-geek-nz
https://github.com/PowerShell/PowerShell/issues/18211
The problem is trying to replace "powershell" with "powershell-lts". Both apt and dpkg will see them as two different packages as they have different package names. ``` trying to overwrite...
> I don't use any package managers and everything works fine. Just unpack to `/opt/microsoft/powershell/7/` and symlink pwsh to the `$PATH`, in `/usr/bin` for example. Forget about `dpgg` or `apt`...
[see discussion](https://github.com/PowerShell/PowerShell/discussions/18120) Have created package of 7.2.6 for macOS ARM64 without Rosetta, required change to both installer and the macOS application icon app.
The certificate is purely to show that the package has not been tampered with. It is not an assertion of copyright over any of the packaged contents. The original licenses...
> I see you are repackaging and signing it with your personal certificate. While your fix addresses the issue this type of cert swap is typically frowned upon. You may...
Suggest PowerShell should not use build-ids in the RPM packaging if repackaging identical binaries. `--define "_build_id_links none" `
If it was a signed 8 bit byte then it would make sense as it would be twos complement sign extension. ``` PS> (0b11111111).GetType().Name Int32 PS> 0b11111111 -1 ```
> And 65535 I raise you 4294967295 for an unsigned 32 bit all ones
24 is a multiple of 8 but this rule is not applied ``` PS > 0b111111111111111111111111 16777215 PS > (0b111111111111111111111111).GetType().Name Int32 ```