views:

130

answers:

2

I'm getting a recurring issue with git-p4. On syncing with git-p4 clone //depot/project/main the majority of files are synced up but there are a number of exceptions for which I can find no apparent common denominators. I created a separate Perforce workspace to use with git-p4 and globally set the properties git-p4.client to this workspace and git-p4.useclientspec to true.

On the Perforce server, we version projects as follows:

//depot/project/main
//depot/project/1.0.0
//depot/project/1.1.0

Calling p4 info gives the following version information for the Perforce installation. Summary: It's old.

Server version: P4D/NTX86/2006.2/113956 (2007/01/04)

Can anyone provide leads to debugging this issue or recommend documentation as to what versions of Perforce are supported?

Appreciate the help.

+1  A: 

If you have a direct perforce workspace then p4 info will tell you what the version of the server is.

Douglas Leeder
Thanks! Adding this info to the question.
Tim Clemons
+1  A: 

See my commit in this GitHub repo for a fix I had to make to git-p4 to work with an old version of p4.

Unfortunately I don't remember the details of my change. At a glance it appears to only affect git-p4 submit.

ScottJ
I've tried this out, but unfortunately it doesn't appear to resolve the problem. Thanks for the lead though -- if I come across a fix I'll forward a patch to you.
Tim Clemons