chore(nomachine-client): drop src override once nixpkgs#518152 lands

[Bad3r]

Type

chore

Scope

nomachine-client

Summary

modules/apps/nomachine-client.nix overrides pkgs.nomachine-client to fetch nomachine_9.5.7_2_x86_64.tar.gz (sha256 8f4ZL3Ko5VunojXLvTS9P3oB+ZVCSYIA0GIjM8VpUO4=) and bumps version to 9.5.7. The upstream nixpkgs derivation still pins 9.4.14, whose tarball the vendor has pulled: https://download.nomachine.com/download/9.4/Linux/nomachine_9.4.14_1_x86_64.tar.gz now 301-redirects to the homepage, so the fetch fails with a hash mismatch and the unpack step then chokes on an HTML payload. Override is temporary until NixOS/nixpkgs#518152 ("nomachine-client: 9.4.14 -> 9.5.7") merges and propagates through nixos-unstable.

Unblock condition

Unblocked when NixOS/nixpkgs#518152 merges and the resulting commit reaches the nixos-unstable channel tracked by this flake.

Upstream pull requests

blocker NixOS/nixpkgs#518152 - nomachine-client: 9.4.14 -> 9.5.7

Upstream issues

none

Upstream releases and channels

none

Local workaround / affected code

modules/apps/nomachine-client.nix

Exit criteria

• Unblock condition satisfied
• ./build.sh --update pulls in a lockfile revision with the fix
• Local follow-up implemented for every file listed above
• All affected hosts rebuild cleanly
• Post-fix validation commands (below), if any, succeed

Validation

nix eval .#nixosConfigurations.system76.pkgs.nomachine-client.version
nix build .#nixosConfigurations.system76.config.system.build.toplevel

Notes

nxplayer --version on the override reports NXPLAYER - Version 9.5.7. The upstream package.nix also tracks an i686-linux source; this repo only builds for x86_64-linux, so the i686 hash is intentionally not handled by the override.

Confirmations

• I searched existing status(blocked-upstream) issues and this is not a duplicate.
• Upstream references are canonical for their role: blocker/fix entries point at the repo that ships the fix.
• Every non-none reference line starts with a reserved role keyword (blocker, fix, related, superseded).
• Every entry in Local workaround / affected code reflects the current state on main.
• The type and scope in the issue title match the Type and Scope body fields.