On 2025-02-06 at 01:27:48, Kapil Somani wrote: > 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? Can you mention where you got your version of Git from? Is this a Debian Git, one you compiled yourself, or another one entirely? > 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 ? I think if you compiled this yourself, you probably need to set PYTHON_PATH to a suitable Python when running the Makefile, and that will rewrite the shebang. If you got this from another source, then they should have compiled the package with a suitable PYTHON_PATH and depended on an appropriate version of Python. I realize that Python 3 is now the default, but there were apparently still some people who want to use Python 2.7 last time this came up, so the default shebang hasn't changed. According to Python upstream, `python` can be of any version, although for all distros I'm aware of, `python` is always version 2. -- brian m. carlson (they/them or he/him) Toronto, Ontario, CA
Attachment:
signature.asc
Description: PGP signature
