{"thread":{"id":"31979","subject":"git-p4 clone @all error","startedAt":"2012-10-30T10:44:39Z","lastAt":"2012-11-06T18:35:16Z","messageCount":15,"participants":["Arthur","Thomas Berg","Pete Wyckoff","Matt Arsenault","Vitor Antunes"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"202192","messageId":"1351593879401-7570219.post@n2.nabble.com","threadId":"31979","inReplyTo":null,"subject":"git-p4 clone @all error","fromName":"Arthur","fromEmail":"a.foulon@amesys.fr","sentAt":"2012-10-30T10:44:39Z","receivedAt":"2012-10-30T10:44:39Z","isPatch":false,"sender":{"key":"a.foulon@amesys.fr","avatar":null},"body":"Hi,\n\n(I am a French student, sorry for my English.)\n\nSo, i want import my perforce projet on my server git.\n\nperforce my project tree :\n\ndepot\n dev_data\n mainline\n release_1.0\n release_1.0.0\n\nmy command is :\n\ngit-p4 clone -v --detect-branches //depot@all /home/user/projets/deport\n\nThe problem :\n\nImporting revision 7727 (100%)Traceback (most recent call last):\n File \"/usr/bin/git-p4\", line 3183, in \n main()\n File \"/usr/bin/git-p4\", line 3177, in main\n if not cmd.run(args):\n File \"/usr/bin/git-p4\", line 3048, in run\n if not P4Sync.run(self, depotPaths):\n File \"/usr/bin/git-p4\", line 2911, in run\n self.importChanges(changes)\n File \"/usr/bin/git-p4\", line 2618, in importChanges\n self.initialParent)\n File \"/usr/bin/git-p4\", line 2198, in commit\n epoch = details[\"time\"]\nKeyError: 'time'\n\nif i make a p4 sync //depot/...#head on my perforce server i've this error : \nLibrarian checkout\ndepot/mainline/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/api429decryption.txt failed.\nopen for read: depot/mainline/xxxxxxxxxxxxxxxxxx/api429decryption.txt,v: Le\nfichier spcifi est introuvable.\n\nMy p4 clone can't checking out files after importing revision..\n\nI hope I was clear ...\n\nThanks for your help.\n\n\n\n--\nView this message in context: http://git.661346.n2.nabble.com/git-p4-clone-all-error-tp7570219.html\nSent from the git mailing list archive at Nabble.com.\n"},{"id":"202309","messageId":"1351689500498-7570343.post@n2.nabble.com","threadId":"31979","inReplyTo":"1351593879401-7570219.post@n2.nabble.com","subject":"Re: git-p4 clone @all error","fromName":"Arthur","fromEmail":"a.foulon@amesys.fr","sentAt":"2012-10-31T13:18:20Z","receivedAt":"2012-10-31T13:18:20Z","isPatch":false,"sender":{"key":"a.foulon@amesys.fr","avatar":null},"body":"up\n\n\n\n--\nView this message in context: http://git.661346.n2.nabble.com/git-p4-clone-all-error-tp7570219p7570343.html\nSent from the git mailing list archive at Nabble.com.\n"},{"id":"202311","messageId":"CABYiQp=1HEW=53U2Rck5vckhq0PB3C9iuanoXeVvNG6Xv5+oHg@mail.gmail.com","threadId":"31979","inReplyTo":"1351593879401-7570219.post@n2.nabble.com","subject":"Re: git-p4 clone @all error","fromName":"Thomas Berg","fromEmail":"merlin66b@gmail.com","sentAt":"2012-10-31T14:01:13Z","receivedAt":"2012-10-31T14:01:13Z","isPatch":false,"sender":{"key":"merlin66b@gmail.com","avatar":null},"body":"Hi,\n\nSorry, forgot to reply-to-all, here is my response again:\n\nOn Tue, Oct 30, 2012 at 11:44 AM, Arthur wrote:\n> The problem :\n>\n> Importing revision 7727 (100%)Traceback (most recent call last):\n> File \"/usr/bin/git-p4\", line 3183, in \n> main()\n> File \"/usr/bin/git-p4\", line 3177, in main\n> if not cmd.run(args):\n> File \"/usr/bin/git-p4\", line 3048, in run\n> if not P4Sync.run(self, depotPaths):\n> File \"/usr/bin/git-p4\", line 2911, in run\n> self.importChanges(changes)\n> File \"/usr/bin/git-p4\", line 2618, in importChanges\n> self.initialParent)\n> File \"/usr/bin/git-p4\", line 2198, in commit\n> epoch = details[\"time\"]\n> KeyError: 'time'\n>\n\nAre you permanently converting a project, or are you planning to\ncontinue submitting to perforce with git-p4?\n\nI have seen similar bugs myself when using the --detect-branches\noption. The branch detection in git-p4 is flaky anyway: it is limited\nwhat it can handle, and it used to require correct perforce branch\nspecs at least, so I would recommend not using it unless you know what\nit is doing under the hood.\n\nInstead I would just clone a single branch at a time (drop the\n--detect-branches) and work on that.\n\nI do this even in the rare cases when I need more than one perforce\nbranch in the same git repo - there are other ways to achieve the same\nthing.\n\n- Thomas\n"},{"id":"202465","messageId":"20121103140946.GB4651@padd.com","threadId":"31979","inReplyTo":"1351593879401-7570219.post@n2.nabble.com","subject":"Re: git-p4 clone @all error","fromName":"Pete Wyckoff","fromEmail":"pw@padd.com","sentAt":"2012-11-03T14:09:46Z","receivedAt":"2012-11-03T14:09:46Z","isPatch":false,"sender":{"key":"pw@padd.com","avatar":null},"body":"a.foulon@amesys.fr wrote on Tue, 30 Oct 2012 03:44 -0700:\n> So, i want import my perforce projet on my server git.\n> \n> perforce my project tree :\n> \n> depot\n> dev_data\n> mainline\n> release_1.0\n> release_1.0.0\n> \n> my command is :\n> \n> git-p4 clone -v --detect-branches //depot@all /home/user/projets/deport\n> \n> The problem :\n> \n> Importing revision 7727 (100%)Traceback (most recent call last):\n> File \"/usr/bin/git-p4\", line 3183, in \n> main()\n> File \"/usr/bin/git-p4\", line 3177, in main\n> if not cmd.run(args):\n> File \"/usr/bin/git-p4\", line 3048, in run\n> if not P4Sync.run(self, depotPaths):\n> File \"/usr/bin/git-p4\", line 2911, in run\n> self.importChanges(changes)\n> File \"/usr/bin/git-p4\", line 2618, in importChanges\n> self.initialParent)\n> File \"/usr/bin/git-p4\", line 2198, in commit\n> epoch = details[\"time\"]\n> KeyError: 'time'\n\nThis isn't the --detect-branches code path, as far as I can tell.\nLine 2618, importChanges, is the not-detect case. But either\nway, I suspect that p4 returns results we weren't expecting, and\nthis is just the symptom of that problem.\n\n> if i make a p4 sync //depot/...#head on my perforce server i've this error : \n> Librarian checkout\n> depot/mainline/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/api429decryption.txt failed.\n> open for read: depot/mainline/xxxxxxxxxxxxxxxxxx/api429decryption.txt,v: Le\n> fichier spcifi est introuvable.\n> \n> My p4 clone can't checking out files after importing revision..\n\nI've seen this before at our site. If you search for \"librarian\nchecout\" you'll see lots of messages suggesting there's some sort\nof problem with the p4 server.\n\nI'm going to work on a patch to git-p4 to make it print a more\nuseful diagnostic in the case of your error above. Can you\nmake this problem occur reliably?\n\n\t\t-- Pete\n"},{"id":"202471","messageId":"20121103230701.GA11267@padd.com","threadId":"31979","inReplyTo":"20121103140946.GB4651@padd.com","subject":"[PATCH] git p4: catch p4 describe errors","fromName":"Pete Wyckoff","fromEmail":"pw@padd.com","sentAt":"2012-11-03T23:07:01Z","receivedAt":"2012-11-03T23:07:01Z","isPatch":true,"sender":{"key":"pw@padd.com","avatar":null},"body":"Group the two calls to \"p4 describe\" into a new helper function,\nand try to validate the p4 results. The current behavior when p4\ndescribe fails is to die with a python backtrace. The new behavior\nwill print the full response.\n\nBased-on-patch-by: Matt Arsenault \nSigned-off-by: Pete Wyckoff \n---\n\nArthur and Matt, you've both had intermittent \"p4 describe\"\nerrors. I've not been able to repeat this or come up with\na possible root cause. But it is clear that the error handling\nin this area is weak.\n\nCan you continue using git-p4 with this patch applied? If\nit fails again, at least we'll get some interesting output.\n\nThis is appropriate for upstream too, since it should do no harm\nand might flush out a bug at some point. It includes \"-s\" on\nboth p4 describe calls now as Matt suggested.\n\n\t\t-- Pete\n\n git-p4.py | 35 ++++++++++++++++++++++++++---------\n 1 file changed, 26 insertions(+), 9 deletions(-)\n\ndiff --git a/git-p4.py b/git-p4.py\nindex 882b1bb..e51a081 100755\n--- a/git-p4.py\n+++ b/git-p4.py\n@@ -169,6 +169,29 @@ def p4_reopen(type, f):\n def p4_move(src, dest):\n p4_system([\"move\", \"-k\", wildcard_encode(src), wildcard_encode(dest)])\n \n+def p4_describe(change):\n+ \"\"\"Make sure it returns a valid result by checking for\n+ the presence of field \"time\". Return a dict of the\n+ results.\"\"\"\n+\n+ ds = p4CmdList([\"describe\", \"-s\", str(change)])\n+ if len(ds) != 1:\n+ die(\"p4 describe -s %d did not return 1 result: %s\" % (change, str(ds)))\n+\n+ d = ds[0]\n+\n+ if \"p4ExitCode\" in d:\n+ die(\"p4 describe -s %d exited with %d: %s\" % (change, d[\"p4ExitCode\"],\n+ str(d)))\n+ if \"code\" in d:\n+ if d[\"code\"] == \"error\":\n+ die(\"p4 describe -s %d returned error code: %s\" % (change, str(d)))\n+\n+ if \"time\" not in d:\n+ die(\"p4 describe -s %d returned no \\\"time\\\": %s\" % (change, str(d)))\n+\n+ return d\n+\n #\n # Canonicalize the p4 type and return a tuple of the\n # base type, plus any modifiers. See \"p4 help filetypes\"\n@@ -2543,7 +2566,7 @@ class P4Sync(Command, P4UserMap):\n def importChanges(self, changes):\n cnt = 1\n for change in changes:\n- description = p4Cmd([\"describe\", str(change)])\n+ description = p4_describe(change)\n self.updateOptionDict(description)\n \n if not self.silent:\n@@ -2667,14 +2690,8 @@ class P4Sync(Command, P4UserMap):\n \n # Use time from top-most change so that all git p4 clones of\n # the same p4 repo have the same commit SHA1s.\n- res = p4CmdList(\"describe -s %d\" % newestRevision)\n- newestTime = None\n- for r in res:\n- if r.has_key('time'):\n- newestTime = int(r['time'])\n- if newestTime is None:\n- die(\"\\\"describe -s\\\" on newest change %d did not give a time\")\n- details[\"time\"] = newestTime\n+ res = p4_describe(newestRevision)\n+ details[\"time\"] = res[\"time\"]\n \n self.updateOptionDict(details)\n try:\n-- \n1.7.12.1.457.g468b3ef\n"},{"id":"202472","messageId":"5747DA7F-485C-4AF3-88A4-B19F517C1E11@gmail.com","threadId":"31979","inReplyTo":"20121103230701.GA11267@padd.com","subject":"Re: [PATCH] git p4: catch p4 describe errors","fromName":"Matt Arsenault","fromEmail":"arsenm2@gmail.com","sentAt":"2012-11-03T23:12:07Z","receivedAt":"2012-11-03T23:12:07Z","isPatch":true,"sender":{"key":"arsenm2@gmail.com","avatar":null},"body":"\nOn Nov 3, 2012, at 16:07 , Pete Wyckoff wrote:\n> \n> Arthur and Matt, you've both had intermittent \"p4 describe\"\n> errors. I've not been able to repeat this or come up with\n> a possible root cause. But it is clear that the error handling\n> in this area is weak.\nI tried this week to find the commit that caused the problem, but there were too many to sift through so I haven't managed to see it again either"},{"id":"202473","messageId":"20121103231305.GB11267@padd.com","threadId":"31979","inReplyTo":"CABYiQp=1HEW=53U2Rck5vckhq0PB3C9iuanoXeVvNG6Xv5+oHg@mail.gmail.com","subject":"Re: git-p4 clone @all error","fromName":"Pete Wyckoff","fromEmail":"pw@padd.com","sentAt":"2012-11-03T23:13:05Z","receivedAt":"2012-11-03T23:13:05Z","isPatch":false,"sender":{"key":"pw@padd.com","avatar":null},"body":"merlin66b@gmail.com wrote on Wed, 31 Oct 2012 15:01 +0100:\n> On Tue, Oct 30, 2012 at 11:44 AM, Arthur wrote:\n> > The problem :\n> >\n> > Importing revision 7727 (100%)Traceback (most recent call last):\n> > File \"/usr/bin/git-p4\", line 3183, in \n> > main()\n> > File \"/usr/bin/git-p4\", line 3177, in main\n> > if not cmd.run(args):\n> > File \"/usr/bin/git-p4\", line 3048, in run\n> > if not P4Sync.run(self, depotPaths):\n> > File \"/usr/bin/git-p4\", line 2911, in run\n> > self.importChanges(changes)\n> > File \"/usr/bin/git-p4\", line 2618, in importChanges\n> > self.initialParent)\n> > File \"/usr/bin/git-p4\", line 2198, in commit\n> > epoch = details[\"time\"]\n> > KeyError: 'time'\n> \n> Are you permanently converting a project, or are you planning to\n> continue submitting to perforce with git-p4?\n> \n> I have seen similar bugs myself when using the --detect-branches\n> option.\n\nI hope --detect-branches is unrelated to any problems related to\np4 describe, because it is used identically both with and without\nthe option. But you never know.\n\n> The branch detection in git-p4 is flaky anyway: it is limited\n> what it can handle, and it used to require correct perforce branch\n> specs at least, so I would recommend not using it unless you know what\n> it is doing under the hood.\n\nIt relies on heuristics because the git idea of branches doesn't\nhave a direct analog in p4, even though p4 users will organize\ntheir files and directories in ways that suggest branches. The\nway it works is described in the BRANCH DETECTION part of the\ngit-p4.1 man page.\n\nThe man page also explains how you can use a config variable\nto explicitly define the branch relationships. This might help:\n\ngit-p4.branchList::\n List of branches to be imported when branch detection is\n enabled. Each entry should be a pair of branch names separated\n by a colon (:). This example declares that both branchA and\n branchB were created from main:\n\n\tgit config git-p4.branchList main:branchA\n\tgit config --add git-p4.branchList main:branchB\n\nIt still only works for branches at the same \"level\" of the\ndepot path.\n\n> Instead I would just clone a single branch at a time (drop the\n> --detect-branches) and work on that.\n> \n> I do this even in the rare cases when I need more than one perforce\n> branch in the same git repo - there are other ways to achieve the same\n> thing.\n\nYep, that should alway works.\n\n\t\t-- Pete\n"},{"id":"202539","messageId":"1352109747598-7570575.post@n2.nabble.com","threadId":"31979","inReplyTo":"20121103231305.GB11267@padd.com","subject":"Re: git-p4 clone @all error","fromName":"Arthur","fromEmail":"a.foulon@amesys.fr","sentAt":"2012-11-05T10:02:27Z","receivedAt":"2012-11-05T10:02:27Z","isPatch":false,"sender":{"key":"a.foulon@amesys.fr","avatar":null},"body":"Hi,\n\nHere is my import :\n\nImporting from //depot@all into XXXXX\nInitialized empty Git repository in\n/home/arthur/projets_git/XXXXX/XXXXX/.git/\nImporting revision 4258 (43%)\n Importing new branch depot/DEV_DATA\n\n Resuming with change 4258\nImporting revision 5828 (63%)\n Importing new branch depot/RELEASE_1.0\n\n Resuming with change 5828\nImporting revision 7720 (88%)\n Importing new branch depot/RELEASE_1.0.0\n\n Resuming with change 7720\nImporting revision 8588 (100%)\nUpdated branches: DEV_DATA RELEASE_1.0 MAINLINE/02_SubSystem/10_ARINC_429\nMAINLINE RELEASE_1.0.0 \nfast-import failed: error: unable to resolve reference\nrefs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429: Not a directory\nerror: Unable to lock\nrefs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429\nerror: unable to resolve reference\nrefs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429: Not a directory\nerror: Unable to lock\nrefs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429\nerror: unable to resolve reference\nrefs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429: Not a directory\nerror: Unable to lock\nrefs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429\nerror: unable to resolve reference\nrefs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429: Not a directory\nerror: Unable to lock\nrefs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429\nerror: unable to resolve reference\nrefs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429: Not a directory\nerror: Unable to lock\nrefs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429\nerror: unable to resolve reference\nrefs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429: Not a directory\nerror: Unable to lock\nrefs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429\nerror: unable to resolve reference\nrefs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429: Not a directory\nerror: Unable to lock\nrefs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429\ngit-fast-import statistics:\n---------------------------------------------------------------------\nAlloc'd objects: 170000\nTotal objects: 169644 ( 195421 duplicates )\n blobs : 92182 ( 186294 duplicates 74565 deltas)\n trees : 70889 ( 9127 duplicates 57686 deltas)\n commits: 6573 ( 0 duplicates 0 deltas)\n tags : 0 ( 0 duplicates 0 deltas)\nTotal branches: 8 ( 8 loads )\n marks: 1024 ( 0 unique )\n atoms: 19603\nMemory total: 19217 KiB\n pools: 12576 KiB\n objects: 6640 KiB\n---------------------------------------------------------------------\npack_report: getpagesize() = 4096\npack_report: core.packedGitWindowSize = 33554432\npack_report: core.packedGitLimit = 268435456\npack_report: pack_used_ctr = 19803\npack_report: pack_mmap_calls = 65\npack_report: pack_open_windows = 10 / 11\npack_report: pack_mapped = 257715823 / 268009874\n---------------------------------------------------------------------\n\n\nImport crash after importing revision, my import have not files\n\n\n\n--\nView this message in context: http://git.661346.n2.nabble.com/git-p4-clone-all-error-tp7570219p7570575.html\nSent from the git mailing list archive at Nabble.com.\n"},{"id":"202569","messageId":"20121105221212.GA12003@padd.com","threadId":"31979","inReplyTo":"1352109747598-7570575.post@n2.nabble.com","subject":"Re: git-p4 clone @all error","fromName":"Pete Wyckoff","fromEmail":"pw@padd.com","sentAt":"2012-11-05T22:12:12Z","receivedAt":"2012-11-05T22:12:12Z","isPatch":false,"sender":{"key":"pw@padd.com","avatar":null},"body":"a.foulon@amesys.fr wrote on Mon, 05 Nov 2012 02:02 -0800:\n> Hi,\n> \n> Here is my import :\n> \n> Importing from //depot@all into XXXXX\n> Initialized empty Git repository in\n> /home/arthur/projets_git/XXXXX/XXXXX/.git/\n> Importing revision 4258 (43%)\n> Importing new branch depot/DEV_DATA\n> \n> Resuming with change 4258\n> Importing revision 5828 (63%)\n> Importing new branch depot/RELEASE_1.0\n> \n> Resuming with change 5828\n> Importing revision 7720 (88%)\n> Importing new branch depot/RELEASE_1.0.0\n> \n> Resuming with change 7720\n> Importing revision 8588 (100%)\n> Updated branches: DEV_DATA RELEASE_1.0 MAINLINE/02_SubSystem/10_ARINC_429\n> MAINLINE RELEASE_1.0.0 \n> fast-import failed: error: unable to resolve reference\n> refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429: Not a directory\n> error: Unable to lock\n> refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429\n> error: unable to resolve reference\n> refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429: Not a directory\n> error: Unable to lock\n> refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429\n> error: unable to resolve reference\n> refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429: Not a directory\n> error: Unable to lock\n> refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429\n> error: unable to resolve reference\n> refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429: Not a directory\n> error: Unable to lock\n> refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429\n> error: unable to resolve reference\n> refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429: Not a directory\n> error: Unable to lock\n> refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429\n> error: unable to resolve reference\n> refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429: Not a directory\n> error: Unable to lock\n> refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429\n> error: unable to resolve reference\n> refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429: Not a directory\n> error: Unable to lock\n> refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429\n> git-fast-import statistics:\n> ---------------------------------------------------------------------\n> Alloc'd objects: 170000\n> Total objects: 169644 ( 195421 duplicates )\n> blobs : 92182 ( 186294 duplicates 74565 deltas)\n> trees : 70889 ( 9127 duplicates 57686 deltas)\n> commits: 6573 ( 0 duplicates 0 deltas)\n> tags : 0 ( 0 duplicates 0 deltas)\n> Total branches: 8 ( 8 loads )\n> marks: 1024 ( 0 unique )\n> atoms: 19603\n> Memory total: 19217 KiB\n> pools: 12576 KiB\n> objects: 6640 KiB\n> ---------------------------------------------------------------------\n> pack_report: getpagesize() = 4096\n> pack_report: core.packedGitWindowSize = 33554432\n> pack_report: core.packedGitLimit = 268435456\n> pack_report: pack_used_ctr = 19803\n> pack_report: pack_mmap_calls = 65\n> pack_report: pack_open_windows = 10 / 11\n> pack_report: pack_mapped = 257715823 / 268009874\n> ---------------------------------------------------------------------\n> \n> \n> Import crash after importing revision, my import have not files\n\nThanks, that is interesting output.\n\nAdding Vitor who knows his way around the branch detection\ncode. The first mail by Arthur is here, which focuses more\non the backtrace from \"p4 describe\" errors, but also suggests\nsomething is dodgy in branch detection:\n\n http://thread.gmane.org/gmane.comp.version-control.git/208693\n\nI'm not sure if this is a --verbose run, though, as I don't see\nany chatter like \"branch is xxx\". So I'm not sure if the\nauto-parent detection code got run.\n\nThe \"unable to resolve reference\" comes from refs.c, which is\nwhen fast-import calls update_branch() on each of the changed\nbranches as it is finishing.\n\nVitor, what could git-p4 have done to create a branch name called\n\"refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429\"?\nAny other questions for Arthur?\n\n\t\t-- Pete\n"},{"id":"202576","messageId":"20121106002515.5b7eba50@fenix.utopia.dhis.org","threadId":"31979","inReplyTo":"20121105221212.GA12003@padd.com","subject":"Re: git-p4 clone @all error","fromName":"Vitor Antunes","fromEmail":"vitor.hda@gmail.com","sentAt":"2012-11-06T00:25:15Z","receivedAt":"2012-11-06T00:25:15Z","isPatch":false,"sender":{"key":"vitor.hda@gmail.com","avatar":"https://avatars.githubusercontent.com/u/606876?v=4"},"body":"On Mon, 5 Nov 2012 17:12:12 -0500\nPete Wyckoff wrote:\n\n> Thanks, that is interesting output.\n> \n> Adding Vitor who knows his way around the branch detection\n> code. The first mail by Arthur is here, which focuses more\n> on the backtrace from \"p4 describe\" errors, but also suggests\n> something is dodgy in branch detection:\n> \n> http://thread.gmane.org/gmane.comp.version-control.git/208693\n> \n> I'm not sure if this is a --verbose run, though, as I don't see\n> any chatter like \"branch is xxx\". So I'm not sure if the\n> auto-parent detection code got run.\n> \n> The \"unable to resolve reference\" comes from refs.c, which is\n> when fast-import calls update_branch() on each of the changed\n> branches as it is finishing.\n> \n> Vitor, what could git-p4 have done to create a branch name called\n> \"refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429\"?\n> Any other questions for Arthur?\n> \n\nHi Arthur,\n\nCould you please share with us your git-p4.branchList configuration?\nWould it also be possible to describe a bit more on your depot\nstructure? I'm particularly concerned about its integration history.\n\nI suspect the error you are experiencing is connected to a wrong\nconfiguration. Please take into account that each entry must be in the\nform of origin:destination, where \"origin\" is the folder used as the\nsource of the integration to \"destination\" when first created.\n\nVitor\n"},{"id":"202584","messageId":"1352192140569-7570622.post@n2.nabble.com","threadId":"31979","inReplyTo":"20121106002515.5b7eba50@fenix.utopia.dhis.org","subject":"Re: git-p4 clone @all error","fromName":"Arthur","fromEmail":"a.foulon@amesys.fr","sentAt":"2012-11-06T08:55:40Z","receivedAt":"2012-11-06T08:55:40Z","isPatch":false,"sender":{"key":"a.foulon@amesys.fr","avatar":null},"body":"Thanks for your support,\n\nIf i get latest révision on Perforce i have this errors :\n\n\n/ 590 errors reported\n Librarian checkout\ndepot/mainline/02_subsystem/10_arinc_429/00_cots/01_bsp_aim/original\nfiles/api429decryption.txt failed.\n open for read:\ndepot/mainline/02_subsystem/10_arinc_429/00_cots/01_bsp_aim/original\nfiles/api429decryption.txt,v: Le fichier spcifi est introuvable.\n Librarian checkout\ndepot/mainline/02_subsystem/10_arinc_429/00_cots/01_bsp_aim/original\nfiles/api429linuxrelnotes.pdf failed.\n open for read:\ndepot/mainline/02_subsystem/10_arinc_429/00_cots/01_bsp_aim/original\nfiles/api429linuxrelnotes.pdf,d\\1.1150: Le chemin d'accs spcifi est\nintrouvable.\n Librarian checkout\ndepot/mainline/02_subsystem/10_arinc_429/00_cots/01_bsp_aim/original\nfiles/lien vers readme.txt failed.\n .../\n\nPerforce can't find the files because they were removed. (option\nobliterate...)\nSo the error on the Perforce clone may come from this.\n\n\nHow i can show git-p4.branchList ?\n\nMy depot structure :\n\nMAINLINE\n DEV_DATA\n RELEASE_1.0\n RELEASE_1.0.0\n\n\n\n\n--\nView this message in context: http://git.661346.n2.nabble.com/git-p4-clone-all-error-tp7570219p7570622.html\nSent from the git mailing list archive at Nabble.com.\n"},{"id":"202590","messageId":"loom.20121106T135442-279@post.gmane.org","threadId":"31979","inReplyTo":"1352192140569-7570622.post@n2.nabble.com","subject":"Re: git-p4 clone @all error","fromName":"Vitor Antunes","fromEmail":"vitor.hda@gmail.com","sentAt":"2012-11-06T13:54:48Z","receivedAt":"2012-11-06T13:54:48Z","isPatch":false,"sender":{"key":"vitor.hda@gmail.com","avatar":"https://avatars.githubusercontent.com/u/606876?v=4"},"body":"Arthur amesys.fr> writes:\n\n> \n> Thanks for your support,\n> \n> If i get latest révision on Perforce i have this errors :\n> \n> / 590 errors reported\n> Librarian checkout\n> depot/mainline/02_subsystem/10_arinc_429/00_cots/01_bsp_aim/original\n> files/api429decryption.txt failed.\n> open for read:\n> depot/mainline/02_subsystem/10_arinc_429/00_cots/01_bsp_aim/original\n> files/api429decryption.txt,v: Le fichier spcifi est introuvable.\n> Librarian checkout\n> depot/mainline/02_subsystem/10_arinc_429/00_cots/01_bsp_aim/original\n> files/api429linuxrelnotes.pdf failed.\n> open for read:\n> depot/mainline/02_subsystem/10_arinc_429/00_cots/01_bsp_aim/original\n> files/api429linuxrelnotes.pdf,d\\1.1150: Le chemin d'accs spcifi est\n> introuvable.\n> Librarian checkout\n> depot/mainline/02_subsystem/10_arinc_429/00_cots/01_bsp_aim/original\n> files/lien vers readme.txt failed.\n> .../\n> \n> Perforce can't find the files because they were removed. (option\n> obliterate...)\n> So the error on the Perforce clone may come from this.\n\nTo be honest, I don't know how git-p4 behaves when obliterate is used.\n\n> How i can show git-p4.branchList ?\n>\n> My depot structure :\n> \n> MAINLINE\n> DEV_DATA\n> RELEASE_1.0\n> RELEASE_1.0.0\n> \n\nThis tells me you did not setup the branchList configuration. In your\n~/.gitconfig please add the following:\n\n[git-p4]\n branchList = DEV_DATA:RELEASE_1.0\n branchList = DEV_DATA:RELEASE_1.0.0\n\nThis assumes that the RELEASE branches are integrated from DEV_DATA.\nAfter the import is successful you can move the [git-p4] from\n~/.gitconfig to .git/config of the git repository.\n\nPlease make sure you keep in CC, because I'm not subscribed to the\nmailing list.\n\nVitor\n"},{"id":"202591","messageId":"1352210590188-7570630.post@n2.nabble.com","threadId":"31979","inReplyTo":"1352192140569-7570622.post@n2.nabble.com","subject":"Re: git-p4 clone @all error","fromName":"Arthur","fromEmail":"a.foulon@amesys.fr","sentAt":"2012-11-06T14:03:10Z","receivedAt":"2012-11-06T14:03:10Z","isPatch":false,"sender":{"key":"a.foulon@amesys.fr","avatar":null},"body":"root@Srv-git:/home/arthur/projets_git# git config git-p4.branchList \nmain:MAINLINE\nerror: More than one value for the key git-p4.branchlist: MAINLINE:DEV_DATA\nerror: More than one value for the key git-p4.branchlist:\nMAINLINE:RELEASE_1.0\nerror: More than one value for the key git-p4.branchlist:\nMAINLINE:RELEASE_1.0.0\n\n\n\n\n--\nView this message in context: http://git.661346.n2.nabble.com/git-p4-clone-all-error-tp7570219p7570630.html\nSent from the git mailing list archive at Nabble.com.\n"},{"id":"202592","messageId":"1352211607674-7570631.post@n2.nabble.com","threadId":"31979","inReplyTo":"loom.20121106T135442-279@post.gmane.org","subject":"Re: git-p4 clone @all error","fromName":"Arthur","fromEmail":"a.foulon@amesys.fr","sentAt":"2012-11-06T14:20:07Z","receivedAt":"2012-11-06T14:20:07Z","isPatch":false,"sender":{"key":"a.foulon@amesys.fr","avatar":null},"body":"In ~/.gitconfig i've :\n\n\n[user]\n name = Arthur\n email = a.xxxxx@xxxxx.fr\n[git-p4]\n branchList = MAINLINE:DEV_DATA\n branchList = MAINLINE:RELEASE_1.0\n branchList = MAINLINE:RELEASE_1.0.0\n\nit's ok ?\nSo :\n\n/# git config git-p4.branchList \nMAINLINE:DEV_DATA\nerror: More than one value for the key git-p4.branchlist:\nMAINLINE:RELEASE_1.0\nerror: More than one value for the key git-p4.branchlist:\nMAINLINE:RELEASE_1.0.0/\n\n\n\n--\nView this message in context: http://git.661346.n2.nabble.com/git-p4-clone-all-error-tp7570219p7570631.html\nSent from the git mailing list archive at Nabble.com.\n"},{"id":"202595","messageId":"loom.20121106T193301-775@post.gmane.org","threadId":"31979","inReplyTo":"1352211607674-7570631.post@n2.nabble.com","subject":"Re: git-p4 clone @all error","fromName":"Vitor Antunes","fromEmail":"vitor.hda@gmail.com","sentAt":"2012-11-06T18:35:16Z","receivedAt":"2012-11-06T18:35:16Z","isPatch":false,"sender":{"key":"vitor.hda@gmail.com","avatar":"https://avatars.githubusercontent.com/u/606876?v=4"},"body":"Arthur amesys.fr> writes:\n\n> \n> In ~/.gitconfig i've :\n> \n> [user]\n> name = Arthur\n> email = a.xxxxx xxxxx.fr\n> [git-p4]\n> branchList = MAINLINE:DEV_DATA\n> branchList = MAINLINE:RELEASE_1.0\n> branchList = MAINLINE:RELEASE_1.0.0\n> \n> it's ok ?\n> So :\n> \n> /# git config git-p4.branchList \n> MAINLINE:DEV_DATA\n> error: More than one value for the key git-p4.branchlist:\n> MAINLINE:RELEASE_1.0\n> error: More than one value for the key git-p4.branchlist:\n> MAINLINE:RELEASE_1.0.0/\n\nYou need to run \"git config --get-all git-p4.branchList\" to avoid those\nwarnings.\n\nHow does \"git p4 clone //depot@all\" behave with these options?\n\nVitor\n\nP.S. - Please keep me in Cc:\n"}]}