UTF-8 error on commit

Hi,

I recently installed the latest version of subversion on a new Suse 9.3
server. I had this all running fine on Fedora Core 3 system but on an
older version of SVN. I installed the new version on the SuSE system
and copied over the files. When I try to commit anything I get the
following error:

commit failed
valid UTF-8 data
(hex: 68 2a 07 08 10)
followed by invalid UTF-8 sequence

This happens from the client and if I try to import a file structure on
the server. I tried creating a whole new file structure on this system
to see it was an error due to copying but the error still exists.

I've googled like crazy but can't find any info on this. Is there some
way to change this behavior in svn? In other words can I tell SVN not
to worry about UTF-8 encoding?

If not does anyone know offhand how to change this behavior in Linux?
That is the path I will go down now since I've kind of exhausted my
options on the SVN side.

Thanks,
Jerry

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Dec 2 22:04:15 2005