You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When building nodePackages.meshcommander the resulting binary contains ^M in the shebang line. This causes the binary to fail to execute.
$ nix shell nixpkgs#nodePackages.meshcommander
$ meshcommander /usr/bin/env: ‘node\r’: No such file or directory/usr/bin/env: use -[v]S to pass options in shebang lines
$ hexdump -C $(which meshcommander)00000000 23 21 20 2f 75 73 72 2f 62 69 6e 2f 65 6e 76 20 |#! /usr/bin/env |00000010 6e 6f 64 65 0d 0a 72 65 71 75 69 72 65 28 22 2e |node..require(".| ^^
The bug was introduced between 22.05 and 22.11:
$ nix run nixpkgs#nodePackages.meshcommander/usr/bin/env: ‘node\r’: No such file or directory/usr/bin/env: use -[v]S to pass options in shebang lines
$ nix run nixpkgs/nixos-22.11#nodePackages.meshcommander/usr/bin/env: ‘node\r’: No such file or directory/usr/bin/env: use -[v]S to pass options in shebang lines
$ nix run nixpkgs/nixos-22.05#nodePackages.meshcommanderMeshCommander running on http://127.0.0.1:3000.
Steps To Reproduce
Build pkgs.nodePackages.meshcommander
Execute meshcommander
Expected behavior
The binary runs and doesn't die on a broken shebang.
Notify maintainers
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
Describe the bug
When building
nodePackages.meshcommander
the resulting binary contains^M
in the shebang line. This causes the binary to fail to execute.The bug was introduced between 22.05 and 22.11:
Steps To Reproduce
pkgs.nodePackages.meshcommander
meshcommander
Expected behavior
The binary runs and doesn't die on a broken shebang.
Notify maintainers
Metadata
Please run
nix-shell -p nix-info --run "nix-info -m"
and paste the result.The text was updated successfully, but these errors were encountered: