tags:

views:

51

answers:

1

unknown command: 'svn-commit.tmp'

I have never seen this type of output from svn ci. svn ci is just an alias for svn commit. Anyway, if you know how to fix this, that would be amazing. Until then, I cannot commit any code lol. I looked around on Google for others having this error but I didn't find anything.

Running svn cleanup doesn't fix anything

A: 

Could it be that the EDITOR (or SVN_EDITOR, etc.) environment variable is set to svn-commit.tmp? (This environment variable specifies which editor you want to use to edit the commit message.)

Though on Linux, at least, you would get a more meaningful error message:

sh: svn-commit.tmp: not found
svn: Commit failed (details follow):
svn: system('svn-commit.tmp svn-commit.tmp') returned 32512

Perhaps you are on Windows, this is the problem, and the error message is terse?

Richard Fearn
I don't think that the environment variable is off. I have my ~/.bash_profile setup as follows:export SVN_EDITOR=svnI am running on MacOSXThanks for the great question and your help!
syn4k
I ran sudo updatedb which is a symlink I created to update the local locate database. Then I ran locate svn-commit.tmp. This yielded 0 results. So, basically, there is no such file on my system
syn4k
I don't think `svn-commit.tmp` exists - I thought that svn was trying to run that as though it were an editor. `SVN_EDITOR` needs to be be a text editor, not `svn` itself.
Richard Fearn
Great idea Richard,I ran export SVN_EDITOR=/usr/bin/vim. My mistake for not doing this earlier. I am still getting an error when committing though: Unknown command: 'svn-commit.tmp' returned 256
syn4k
I filed a bug report over at tigris: http://subversion.tigris.org/issues/show_bug.cgi?id=3703
syn4k
Interestingly, svn ci somefile anotherfile andanother -m "my comment" does not cause the error but this is a horrible way to comment multiple files.
syn4k
Using `-m` won't cause the error as in that case you're specifying a commit message on the command line - i.e. `svn` doesn't need to run a text editor.
Richard Fearn
Richard, yes, you are correct and doing this also prevents the issue from occurring. Seems to me that this is warrant enough for the Tigris developers to look into it but I guess they feel otherwise since my bug was marked as invalid in their issue tracker: http://subversion.tigris.org/issues/show_bug.cgi?id=3703
syn4k
@syn4k the best place to take issues like this is the svn users mailing list which can help debug it. If there's an issue with svn itself and not your environment, which would be determined there, then we can fix it in svn. We just don't like to use the issue tracker as a place to get help, otherwise we would be inundated with tickets.
Blair Zajac