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

Re: UTF-8 error on commit

From: Juergen Sachs <ml_at_mobacomp.de>
Date: 2005-12-03 00:16:18 CET

Am Freitag, 2. Dezember 2005 22:00 schrieb Jerry Way:

I had the same problems here. But with an existing (older) project.
I found two ways around that. The problems seems to be, when some files are in
an older format (non utf8) and some are in utf8. I think svn will analyse the
first file and then find a different and don't like it (but I am not shure
about that).

Solution one:
Import one file at a time

Solution two:
make an archiv (I did an tar) and extract the data in a different place. then
it worked.

I hope this helps you.
> 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.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Dec 3 01:49:12 2005

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