git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git-p4 clone @all error

From
PWPete Wyckoff <pw@padd.com>
Date
Nov 3, 2012, 14:09 UTC
Message-ID
<20121103140946.GB4651@padd.com>
In-Reply-To
<1351593879401-7570219.post@n2.nabble.com>
a.foulon@amesys.fr wrote on Tue, 30 Oct 2012 03:44 -0700:
Show 30 quoted lines
> 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.

Show 7 quoted lines
> 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
Previous: ArthurNext: Pete Wyckoff
Message 13 of 15 in “git-p4 clone @all error”
  1. ArthurOct 30, 2012
  2. ArthurOct 31, 2012
  3. Thomas BergOct 31, 2012
  4. Pete WyckoffNov 3, 2012
  5. ArthurNov 5, 2012
  6. Pete WyckoffNov 5, 2012
  7. Vitor AntunesNov 6, 2012
  8. ArthurNov 6, 2012
  9. Vitor AntunesNov 6, 2012
  10. ArthurNov 6, 2012
  11. Vitor AntunesNov 6, 2012
  12. ArthurNov 6, 2012
  13. Pete WyckoffNov 3, 2012
  14. git p4: catch p4 describe errorsPete Wyckoff, Nov 3, 2012
  15. Matt ArsenaultNov 3, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.