From: Pete Wyckoff <pw@padd.com>
To: Arthur <a.foulon@amesys.fr>
Cc: git@vger.kernel.org
Subject: Re: git-p4 clone @all error
Date: Sat, 3 Nov 2012 10:09:46 -0400 [thread overview]
Message-ID: <20121103140946.GB4651@padd.com> (raw)
In-Reply-To: <1351593879401-7570219.post@n2.nabble.com>
a.foulon@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
next prev parent reply other threads:[~2012-11-03 14:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 10:44 git-p4 clone @all error Arthur
2012-10-31 13:18 ` Arthur
2012-10-31 14:01 ` Thomas Berg
2012-11-03 23:13 ` Pete Wyckoff
2012-11-05 10:02 ` Arthur
2012-11-05 22:12 ` Pete Wyckoff
2012-11-06 0:25 ` Vitor Antunes
2012-11-06 8:55 ` Arthur
2012-11-06 13:54 ` Vitor Antunes
2012-11-06 14:20 ` Arthur
2012-11-06 18:35 ` Vitor Antunes
2012-11-06 14:03 ` Arthur
2012-11-03 14:09 ` Pete Wyckoff [this message]
2012-11-03 23:07 ` [PATCH] git p4: catch p4 describe errors Pete Wyckoff
2012-11-03 23:12 ` Matt Arsenault
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121103140946.GB4651@padd.com \
--to=pw@padd.com \
--cc=a.foulon@amesys.fr \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).