{"thread":{"id":"7260","subject":"error with symlinks on OSX","startedAt":"2007-03-15T17:12:29Z","lastAt":"2007-03-15T22:19:43Z","messageCount":3,"participants":["Seth Falcon","Shawn O. Pearce"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"37173","messageId":"m2r6rqbfcy.fsf@ziti.local","threadId":"7260","inReplyTo":null,"subject":"error with symlinks on OSX","fromName":"Seth Falcon","fromEmail":"sethfalcon@gmail.com","sentAt":"2007-03-15T17:12:29Z","receivedAt":"2007-03-15T17:12:29Z","isPatch":false,"sender":{"key":"sethfalcon@gmail.com","avatar":"https://gravatar.com/avatar/fd62fe73d3013b12fce71d5269ec52eaca3c4cee479efc6eea3603d6f1d8bf8d?d=mp&s=160"},"body":"Hi,\n\nI've been tracking an svn repository using git-svn and today when I\ndid:\n\n   git svn rebase\n\n   (which is equivalent to git svn fetch && git rebase\n   remotes/git-svn)\n\nI got errors like this:\n\nerror: git-checkout-index: unable to create symlink Category/Makefile (Invalid argument)\n\nNow while my file system isn't smart enough to tell the difference\nbetween t and T, it does support symlinks AFAIK.\n\ngit version 1.5.0.2.293.g102a0\n\nI can provide more info if it would help.\n\n+ seth\n"},{"id":"37175","messageId":"20070315194410.GC29547@spearce.org","threadId":"7260","inReplyTo":"m2r6rqbfcy.fsf@ziti.local","subject":"Re: error with symlinks on OSX","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2007-03-15T19:44:10Z","receivedAt":"2007-03-15T19:44:10Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Seth Falcon <sethfalcon@gmail.com> wrote:\n> error: git-checkout-index: unable to create symlink Category/Makefile (Invalid argument)\n> \n> Now while my file system isn't smart enough to tell the difference\n> between t and T, it does support symlinks AFAIK.\n\nYes, it does support symlinks.  Is it possible that the name Category\nalready existed, but as a file?  Hmm.\n \n-- \nShawn.\n"},{"id":"37181","messageId":"m2wt1i6tfk.fsf@ziti.local","threadId":"7260","inReplyTo":"20070315194410.GC29547@spearce.org","subject":"Re: error with symlinks on OSX","fromName":"Seth Falcon","fromEmail":"sethfalcon@gmail.com","sentAt":"2007-03-15T22:19:43Z","receivedAt":"2007-03-15T22:19:43Z","isPatch":false,"sender":{"key":"sethfalcon@gmail.com","avatar":"https://gravatar.com/avatar/fd62fe73d3013b12fce71d5269ec52eaca3c4cee479efc6eea3603d6f1d8bf8d?d=mp&s=160"},"body":"\"Shawn O. Pearce\" <spearce@spearce.org> writes:\n\n> Seth Falcon <sethfalcon@gmail.com> wrote:\n>> error: git-checkout-index: unable to create symlink Category/Makefile (Invalid argument)\n>> \n>> Now while my file system isn't smart enough to tell the difference\n>> between t and T, it does support symlinks AFAIK.\n>\n> Yes, it does support symlinks.  Is it possible that the name Category\n> already existed, but as a file?  Hmm.\n\nI think in the revision before the update, there was a file\nCategory/Makefile and that it was replaced by a symlink.\n\nSo Category is/was a dir.  Category/Makefile was a file and became a\nsymlink.  Note that I am using git-svn to track an svn repository and\nso the problem could be there.\n\nHowever, I'm not sure where to look or what experiment to try next.\n\nIf I checkout an old revision prior to the file becoming a symlink and\nthen checkout master, I get:\n\ngit checkout -b foobar 74227bbd35a77b8\nSwitched to a new branch \"foobar\"\ngit checkout master\nD       Category/Makefile\n[...snip...]\nD       vsn/Makefile\nSwitched to branch \"master\"\n\ngit reset --hard HEAD\nerror: git-checkout-index: unable to create symlink Category/Makefile (Invalid argument)\n[...snip...]\nerror: git-checkout-index: unable to create symlink vsn/Makefile (Invalid argument)\nHEAD is now at 30bd65d... the commit msg here\n\n\n-- \nSeth\n"}]}