Thank you for filling out a Git bug report! Please answer the following questions to help us understand your issue. What did you do before the bug happened? (Steps to reproduce your issue) Run `git p4 clone //path/to/p4/depot --destination=/tmp/localcopy` What did you expect to happen? (Expected behavior) The command should have imported perforce depot to a git repository What happened instead? (Actual behavior) The command threw error fatal: 'p4' appears to be a git command, but we were not able to execute it. Maybe git-p4 is broken? What's different between what you expected and what actually happened? The command did not perform desired operation Anything else you want to add: The machine does not have python on path I noticed `git-p4`'s shebang line points to python. On my local git installation, i was able to update shebang line on git-p4 to python3 and the command worked as expected. With python3 now being default should be update git-p4 to run using python3 ? Please review the rest of the bug report below. You can delete any lines you don't wish to share. [System Info] git version: git version 2.30.2 cpu: x86_64 no commit associated with this build sizeof-long: 8 sizeof-size_t: 8 shell-path: /bin/sh uname: Linux 5.10.0-33-amd64 #1 SMP Debian 5.10.226-1 (2024-10-03) x86_64 compiler info: gnuc: 10.2 libc info: glibc: 2.31 $SHELL (typically, interactive shell): /bin/tcsh [Enabled Hooks] not run from a git repository - no hooks to show
