plink not found

307 views
Skip to first unread message

illeg...@gmail.com

unread,
Jun 1, 2019, 5:45:26 PM6/1/19
to tortoisegit-users
Tortoise git 2.8.0.0 running on Windows 10

I have msys2 installed and am using the msys2 git for tortoise git (all the msys2 stuff is current according to pacman)

Whenever I attempt via the GUI to do something that refers to a remote repository, I get an error dialog like:

git.exe pull --progress -v --no-rebase "origin"

error: cannot run C:\Program Files\TortoiseGit\bin\TortoiseGitPlink.exe: No such file or directory
fatal: unable to fork

git did not exit cleanly (exit code 1) (109 ms @ 6/1/2019 16:26:23)

Tortoise git is installed in the default location, which is where that path points, and the file exists there:

C:\>dir "c:\Program Files\TortoiseGit\bin\TortoiseGitPlink.exe"
 Volume in drive C is OS
 Volume Serial Number is 7452-E6EF

 Directory of c:\Program Files\TortoiseGit\bin

02/28/2019  22:16           566,432 TortoiseGitPlink.exe
               1 File(s)        566,432 bytes
               0 Dir(s)  311,373,410,304 bytes free

I haven't changed protections anywhere in c:\Program Files, and a quick check shows the file should be accessible -- anyway the message says "does not exist".

Removing Tortoise Git, rebooting, and reinstalling doesn't help.

Suggestions?  I see stuff relating to there being a space in the file path or to environment variable GIT_SSH, but GIT_SSH is not defined on this system, and plink is in its default install location (that can't not work, right?).

Sven Strickroth

unread,
Jun 3, 2019, 5:52:45 AM6/3/19
to tortoise...@googlegroups.com, illeg...@gmail.com
Hi,

Am 01.06.2019 um 23:45 schrieb illeg...@gmail.com:
> error: cannot run C:\Program Files\TortoiseGit\bin\TortoiseGitPlink.exe:
> No such file or directory
> fatal: unable to fork

Maybe TortoiseGitPlink is not correctly set. Please check the path on
TortoiseGit->Settings->Network. Generall, it should be sufficient if you
just type "tortoisegitplink.exe" or "ssh" there, depending on which ssh
client you want to use.

--
Best regards,
Sven Strickroth
PGP key id F5A9D4C4 @ any key-server

David Dyer-Bennet

unread,
Oct 22, 2019, 12:05:49 AM10/22/19
to tortoisegit-users

On Monday, June 3, 2019 at 4:52:45 AM UTC-5, Sven Strickroth wrote:
Hi,

Am 01.06.2019 um 23:45 schrieb illeg...@gmail.com:
> error: cannot run C:\Program Files\TortoiseGit\bin\TortoiseGitPlink.exe:
> No such file or directory
> fatal: unable to fork

Maybe TortoiseGitPlink is not correctly set. Please check the path on
TortoiseGit->Settings->Network. Generall, it should be sufficient if you
just type "tortoisegitplink.exe" or "ssh" there, depending on which ssh
client you want to use.

Nope; the path given in the error message is the correct path to the program, and I can run the program from the command line using that path.

I finally figured out what was going on today, and it's nothing like any of the suggestions I've found online.  There are probably many ways to get this error, like the "space in path" issues that sometimes come up, and just having things set wrong.  But those aren't what my problem is.

What I'm doing is trying (now, finally, succeeding) to run Msys2 git and Tortoise git *cooperatively* on my Windows 10 laptop -- I've got my mshs2 home directory pointing to /c/Users/ddb, which is my Windows home directory, so they're sharing everything, including Git configs. I do of course have Tortoise Git set to use their Msys2 hack.  And, to avoid the space in path problem (if it's real?), I copied TortoiseGitPlink.exe to my c:\bin directory (not a standard bin, but in all my paths; a place I put things I want accessible from both environments easily). 

I debugged this by working with the Msys2 command line git -- it was getting the same error.  Looking at the error in that environment, I realized the problem was that the path that was configured in Tortoise Git config was a Windows path. Changing it to an Msys2 path (/c/bin/TortoiseGitPlink.exe) fixed the problem. And it fixed the problem in Tortoise Git as well -- because it's configured to run Msys2 git for the actual work, and that expects Msys2 paths

I'm *so* happy to finally get these working in parallel, with all the same configuration!!!!!
Reply all
Reply to author
Forward
0 new messages