a.fou...@amesys.fr wrote on Tue, 30 Oct 2012 03:44 -0700: > So, i want import my perforce projet on my server git. > > perforce my project tree : > > depot > dev_data > mainline > release_1.0 > release_1.0.0 > > my command is : > > git-p4 clone -v --detect-branches //depot@all /home/user/projets/deport > > The problem : > > Importing revision 7727 (100%)Traceback (most recent call last): > File "/usr/bin/git-p4", line 3183, in <module> > main() > File "/usr/bin/git-p4", line 3177, in main > if not cmd.run(args): > File "/usr/bin/git-p4", line 3048, in run > if not P4Sync.run(self, depotPaths): > File "/usr/bin/git-p4", line 2911, in run > self.importChanges(changes) > File "/usr/bin/git-p4", line 2618, in importChanges > self.initialParent) > File "/usr/bin/git-p4", line 2198, in commit > epoch = details["time"] > KeyError: 'time'
This isn't the --detect-branches code path, as far as I can tell. Line 2618, importChanges, is the not-detect case. But either way, I suspect that p4 returns results we weren't expecting, and this is just the symptom of that problem. > if i make a p4 sync //depot/...#head on my perforce server i've this error : > Librarian checkout > depot/mainline/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/api429decryption.txt failed. > open for read: depot/mainline/xxxxxxxxxxxxxxxxxx/api429decryption.txt,v: Le > fichier spcifi est introuvable. > > My p4 clone can't checking out files after importing revision.. I've seen this before at our site. If you search for "librarian checout" you'll see lots of messages suggesting there's some sort of problem with the p4 server. I'm going to work on a patch to git-p4 to make it print a more useful diagnostic in the case of your error above. Can you make this problem occur reliably? -- Pete -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html