[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

[Subclipse-users] Erroneous 'Commit failed' message

From: Paul Barratt <noodle63_at_googlemail.com>
Date: Thu, 09 Oct 2008 17:47:28 +0100

I'm consistently getting 'commit failed' messages in Eclipse when in fact the commit does succeed.


I'm running Kubuntu 8.04 with Sun JRE 1.6.0_06-b02 and Eclipse version 3.4.1 on my new laptop (the old one died last
week - that worked without problems). My subversion server is version 1.4.5 running on Mandriva 2008, and I'm
connecting to svn using the svn+ssh protocol.
Eclipse is using SVNKit v1.2.0.4927. There is also a choice of 'JavaHL (JNI) Not Available' in the Eclipse prefs, which
does not appear to make any difference to the situation. And despite Eclipse saying 'Not Available', it says I have
'Subversion Native Library Adapter (JavaHL) version' installed.

Description of problem:

I do a fresh checkout of my project in Eclipse.
I do 'update' and 'refresh' on a text file eg 'build.properties' (but all files have the same problem)
The local file is at revision 1380
I make a change and save the file
The outgoing change shows up in the Team Synch perspective. I commit it.
I get this message in the Eclipse SVN Console:
commit -m "testing" /home/paul/source/workspace/myproject/build.properties
     Sending /home/paul/source/workspace/myproject/build.properties
     Transmitting file data ...
     svn: Commit failed (details follow):
     svn: Commit failed (details follow):
svn: <?\224
svn: Can't convert string from native encoding to 'UTF-8':

The character sequence '<?\224' is not present in the file.
However, the commit has succeeded - I can checkout the change on a different PC using the svn command line and can also
view it in Trac, see it in the SVN Repository perspective etc.

The file now shows up in Eclipse as a conflict, with the revision on the server being 1381 and the client at rev 1380 still.
The local file and the repository file are identical.
I then need to do Override and Update to resolve the conflict.

Thinking that this might be a locale problem, I checked this. Both laptop and server say this:

So it's not that.
Why is it failing? Why does it say the commit has failed when it has succeeded?

Hopefully I'm doing something dumb, but this driving me a bit nutty - I hope you can help.


To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-10-09 18:49:12 CEST

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.