{"thread":{"id":"22188","subject":"Bug? git-svn clone dies with \"fatal: ambiguous argument '...': unknown revision or path not in the working tree.\"","startedAt":"2010-01-12T23:58:34Z","lastAt":"2010-01-14T23:57:30Z","messageCount":3,"participants":["Eric Hanchrow","Eric Wong","Sam Vilain"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"131413","messageId":"36366a981001121558v5324f2fbucf096e4c82402912@mail.gmail.com","threadId":"22188","inReplyTo":null,"subject":"Bug? git-svn clone dies with \"fatal: ambiguous argument '...': unknown revision or path not in the working tree.\"","fromName":"Eric Hanchrow","fromEmail":"eric.hanchrow@gmail.com","sentAt":"2010-01-12T23:58:34Z","receivedAt":"2010-01-12T23:58:34Z","isPatch":false,"sender":{"key":"eric.hanchrow@gmail.com","avatar":"https://avatars.githubusercontent.com/u/3145?v=4"},"body":"I have been using git-svn happily for many months, updating git from\ngit://git.kernel.org/pub/scm/git/git.git every once in a while.  I\njust updated to c0eb604330e1288300d915f25868d1eed88d3038, and tried to\nclone the same svn repo that I've been using for a long time:\n\n$ git svn clone http://svn/repos/cozi/kits --stdlayout\n\nIt chugged along happily for a while, but then died like this:\n\nfatal: ambiguous argument\n'2d2df13977551168a54ffa9b706484242a58736a^..d038748d49a0de5802fe3c13f46d0e080d064290':\nunknown revision or path not in the working tree.\nUse '--' to separate paths from revisions\nrev-list 2d2df13977551168a54ffa9b706484242a58736a^..d038748d49a0de5802fe3c13f46d0e080d064290:\ncommand returned error: 128\n\n\"git show 2d2df13977551168a54ffa9b706484242a58736a\" shows that the\ncommit in question corresponds to a commit in svn that created an\nempty directory:\n\n15:56:46 [COZIGROUP\\erich@ubuntu64-erich kits] (master)$  git show -w\n2d2df13977551168a54ffa9b706484242a58736a\ncommit 2d2df13977551168a54ffa9b706484242a58736a\nAuthor: cozigroup\\erich <cozigroup\\erich@1248e456-dc32-5a46-b6cc-76877e1dc968>\nDate:   Wed Jan 14 18:35:00 2009 +0000\n\n    This branch will hold work I've done to refactor the vcs backend\nstuff, and add support for Mercurial.\n\n\n    git-svn-id: http://svn/repos/cozi/kits/branches/vcs-refactor@18735\n1248e456-dc32-5a46-b6cc-76877e1dc968\n\n\n15:41:01 [COZIGROUP\\erich@ubuntu64-erich hmm]$ svn log --limit=1\n-vr18735 http://svn/repos/cozi\n------------------------------------------------------------------------\nr18735 | cozigroup\\erich | 2009-01-14 10:35:00 -0800 (Wed, 14 Jan\n2009) | 2 lines\nChanged paths:\n   A /kits/branches/vcs-refactor\n\nThis branch will hold work I've done to refactor the vcs backend\nstuff, and add support for Mercurial.\n\nIf I recall correctly, that commit was a mistake: I'd forgotten that\nthe proper way to create a branch in svn is to copy the trunk, and not\nto create an empty directory first.\n\nHere I am creating that branch the proper way:\n\nr18736 | cozigroup\\erich | 2009-01-14 10:35:30 -0800 (Wed, 14 Jan\n2009) | 2 lines\nChanged paths:\n   D /kits/branches/vcs-refactor\n\nD'oh.  We branch by _copying_, not making empty directories :-|\n\n------------------------------------------------------------------------\nr18737 | cozigroup\\erich | 2009-01-14 10:36:37 -0800 (Wed, 14 Jan\n2009) | 2 lines\nChanged paths:\n   A /kits/branches/vcs-refactor (from /kits/trunk:18671)\n\nRefactoring the version-control stuff, and adding Mercurial support.\n\n------------------------------------------------------------------------\n\n15:56:51 [COZIGROUP\\erich@ubuntu64-erich kits] (master)$ git show -w\nd038748d49a0de5802fe3c13f46d0e080d064290\ncommit d038748d49a0de5802fe3c13f46d0e080d064290\nMerge: 5108824 a370f0b\nAuthor: cozigroup\\erich <cozigroup\\erich@1248e456-dc32-5a46-b6cc-76877e1dc968>\nDate:   Tue Jan 20 18:34:26 2009 +0000\n\n    Merged from trunk.\n\n\n    git-svn-id: http://svn/repos/cozi/kits/branches/vcs-refactor@18920\n1248e456-dc32-5a46-b6cc-76877e1dc968\n\nAnd here is (what might be) the first attempt to modify stuff in that directory:\n\n15:52:52 [COZIGROUP\\erich@ubuntu64-erich kits] (master)$ svn log\n--limit=1 -vr18920 http://svn/repos/cozi\n------------------------------------------------------------------------\nr18920 | cozigroup\\erich | 2009-01-20 10:34:26 -0800 (Tue, 20 Jan\n2009) | 2 lines\nChanged paths:\n   M /kits/branches/vcs-refactor\n   A /kits/branches/vcs-refactor/lib/CoziPlatform/cozi/resources.py\n(from /kits/trunk/lib/CoziPlatform/cozi/resources.py:18919)\n   M /kits/branches/vcs-refactor/lib/CoziSecurity/cozi/authorize.py\n   M /kits/branches/vcs-refactor/lib/CoziSecurity/cozi/eguidtests.py\n   M /kits/branches/vcs-refactor/lib/CoziVaultRESTServices/cozi/screen_saver_api.py\n   M /kits/branches/vcs-refactor/lib/CoziVaultRESTServices/cozi/screen_saver_calendar_xml.tmpl\n   M /kits/branches/vcs-refactor/lib/CoziVaultRESTServices/cozi/web_client.py\n\nMerged from trunk.\n\n\nAnyway -- I suspect that my svn repos layout is ... er ... unusual,\nand has hit some sorta edge case in git-svn.  Is there some workaround\nI can use, or is this a bug?\n\nThanks\n"},{"id":"131420","messageId":"20100113052958.GA23182@dcvr.yhbt.net","threadId":"22188","inReplyTo":"36366a981001121558v5324f2fbucf096e4c82402912@mail.gmail.com","subject":"Re: Bug? git-svn clone dies with \"fatal: ambiguous argument '...': unknown revision or path not in the working tree.\"","fromName":"Eric Wong","fromEmail":"normalperson@yhbt.net","sentAt":"2010-01-13T05:29:58Z","receivedAt":"2010-01-13T05:29:58Z","isPatch":false,"sender":{"key":"e@80x24.org","avatar":null},"body":"Eric Hanchrow <eric.hanchrow@gmail.com> wrote:\n> I have been using git-svn happily for many months, updating git from\n> git://git.kernel.org/pub/scm/git/git.git every once in a while.  I\n> just updated to c0eb604330e1288300d915f25868d1eed88d3038, and tried to\n> clone the same svn repo that I've been using for a long time:\n> \n> $ git svn clone http://svn/repos/cozi/kits --stdlayout\n> \n> It chugged along happily for a while, but then died like this:\n> \n> fatal: ambiguous argument\n> '2d2df13977551168a54ffa9b706484242a58736a^..d038748d49a0de5802fe3c13f46d0e080d064290':\n\nHi Eric,\n\nI suspect you're hitting a bug with the newly-added mergeinfo support.\n\nAs we see below, d038748d49a0de5802fe3c13f46d0e080d064290 is a merge\ncommit.  So I'll Cc Sam and Andrew on this since they know their way\naround the mergeinfo stuff far better than I do and will hopefully have\nsome insight into things.\n\nSince it's probably related to the new mergeinfo handling, reverting to\na version without it (1.6.5.7) might be the best way to go for now.\n\nThanks for the report!\n\n> unknown revision or path not in the working tree.\n> Use '--' to separate paths from revisions\n> rev-list 2d2df13977551168a54ffa9b706484242a58736a^..d038748d49a0de5802fe3c13f46d0e080d064290:\n> command returned error: 128\n> \n> \"git show 2d2df13977551168a54ffa9b706484242a58736a\" shows that the\n> commit in question corresponds to a commit in svn that created an\n> empty directory:\n> \n> 15:56:46 [COZIGROUP\\erich@ubuntu64-erich kits] (master)$  git show -w\n> 2d2df13977551168a54ffa9b706484242a58736a\n> commit 2d2df13977551168a54ffa9b706484242a58736a\n> Author: cozigroup\\erich <cozigroup\\erich@1248e456-dc32-5a46-b6cc-76877e1dc968>\n> Date:   Wed Jan 14 18:35:00 2009 +0000\n> \n>     This branch will hold work I've done to refactor the vcs backend\n> stuff, and add support for Mercurial.\n> \n> \n>     git-svn-id: http://svn/repos/cozi/kits/branches/vcs-refactor@18735\n> 1248e456-dc32-5a46-b6cc-76877e1dc968\n> \n> \n> 15:41:01 [COZIGROUP\\erich@ubuntu64-erich hmm]$ svn log --limit=1\n> -vr18735 http://svn/repos/cozi\n> ------------------------------------------------------------------------\n> r18735 | cozigroup\\erich | 2009-01-14 10:35:00 -0800 (Wed, 14 Jan\n> 2009) | 2 lines\n> Changed paths:\n>    A /kits/branches/vcs-refactor\n> \n> This branch will hold work I've done to refactor the vcs backend\n> stuff, and add support for Mercurial.\n> \n> If I recall correctly, that commit was a mistake: I'd forgotten that\n> the proper way to create a branch in svn is to copy the trunk, and not\n> to create an empty directory first.\n> \n> Here I am creating that branch the proper way:\n> \n> r18736 | cozigroup\\erich | 2009-01-14 10:35:30 -0800 (Wed, 14 Jan\n> 2009) | 2 lines\n> Changed paths:\n>    D /kits/branches/vcs-refactor\n> \n> D'oh.  We branch by _copying_, not making empty directories :-|\n> \n> ------------------------------------------------------------------------\n> r18737 | cozigroup\\erich | 2009-01-14 10:36:37 -0800 (Wed, 14 Jan\n> 2009) | 2 lines\n> Changed paths:\n>    A /kits/branches/vcs-refactor (from /kits/trunk:18671)\n> \n> Refactoring the version-control stuff, and adding Mercurial support.\n> \n> ------------------------------------------------------------------------\n> \n> 15:56:51 [COZIGROUP\\erich@ubuntu64-erich kits] (master)$ git show -w\n> d038748d49a0de5802fe3c13f46d0e080d064290\n> commit d038748d49a0de5802fe3c13f46d0e080d064290\n> Merge: 5108824 a370f0b\n> Author: cozigroup\\erich <cozigroup\\erich@1248e456-dc32-5a46-b6cc-76877e1dc968>\n> Date:   Tue Jan 20 18:34:26 2009 +0000\n> \n>     Merged from trunk.\n> \n> \n>     git-svn-id: http://svn/repos/cozi/kits/branches/vcs-refactor@18920\n> 1248e456-dc32-5a46-b6cc-76877e1dc968\n> \n> And here is (what might be) the first attempt to modify stuff in that directory:\n> \n> 15:52:52 [COZIGROUP\\erich@ubuntu64-erich kits] (master)$ svn log\n> --limit=1 -vr18920 http://svn/repos/cozi\n> ------------------------------------------------------------------------\n> r18920 | cozigroup\\erich | 2009-01-20 10:34:26 -0800 (Tue, 20 Jan\n> 2009) | 2 lines\n> Changed paths:\n>    M /kits/branches/vcs-refactor\n>    A /kits/branches/vcs-refactor/lib/CoziPlatform/cozi/resources.py\n> (from /kits/trunk/lib/CoziPlatform/cozi/resources.py:18919)\n>    M /kits/branches/vcs-refactor/lib/CoziSecurity/cozi/authorize.py\n>    M /kits/branches/vcs-refactor/lib/CoziSecurity/cozi/eguidtests.py\n>    M /kits/branches/vcs-refactor/lib/CoziVaultRESTServices/cozi/screen_saver_api.py\n>    M /kits/branches/vcs-refactor/lib/CoziVaultRESTServices/cozi/screen_saver_calendar_xml.tmpl\n>    M /kits/branches/vcs-refactor/lib/CoziVaultRESTServices/cozi/web_client.py\n> \n> Merged from trunk.\n> \n> \n> Anyway -- I suspect that my svn repos layout is ... er ... unusual,\n> and has hit some sorta edge case in git-svn.  Is there some workaround\n> I can use, or is this a bug?\n>\n> Thanks\n> --\n"},{"id":"131694","messageId":"4B4FAF6A.2070407@vilain.net","threadId":"22188","inReplyTo":"20100113052958.GA23182@dcvr.yhbt.net","subject":"Re: [spf:guess] Re: Bug? git-svn clone dies with \"fatal: ambiguous argument '...': unknown revision or path not in the working tree.\"","fromName":"Sam Vilain","fromEmail":"sam@vilain.net","sentAt":"2010-01-14T23:57:30Z","receivedAt":"2010-01-14T23:57:30Z","isPatch":false,"sender":{"key":"sam@vilain.net","avatar":"https://gravatar.com/avatar/8fc840ca854dbf6f7065b4335e3b934951c1dca3b11db688e95e471901f8f4a8?d=mp&s=160"},"body":"Eric Wong wrote:\n>> It chugged along happily for a while, but then died like this:\n>>\n>> fatal: ambiguous argument\n>> '2d2df13977551168a54ffa9b706484242a58736a^..d038748d49a0de5802fe3c13f46d0e080d064290':\n>>     \n> [...]\n> As we see below, d038748d49a0de5802fe3c13f46d0e080d064290 is a merge\n> commit.  So I'll Cc Sam and Andrew on this since they know their way\n> around the mergeinfo stuff far better than I do and will hopefully have\n> some insight into things.\n>\n> Since it's probably related to the new mergeinfo handling, reverting to\n> a version without it (1.6.5.7) might be the best way to go for now.\n>   \n\nI'm at a loss. I can't get my rev-list to say \"ambiguous argument\" when\nI pass it a similar range (eg d4e1b47a9225^..a24a32dd on git.git). Why\ndoes it matter that the d038748 commit is a merge commit?\n\nEric H, is this repository available publicly for me to test? I guess\nit's possible that argument is not being passed to rev-list but to some\nother command ... would be nice to be able to reproduce it.\n\nSam\n"}]}