El lun, 03-10-2005 a las 19:23 +0200, Oscar PeÃ±as escribiÃ³:
> I just updated svn to the latest 1.2.3 version under SuSE 9.2.
> Now, every time I try to do a 'svn status' on any of my existing working
> copies, I get a message like the following:
> chopsuey@chopsuey:~/code/server> svn status
> svn: Valid UTF-8 data
> (hex: 78)
> followed by an invalid UTF-8 sequence
> (hex: c4 07 08)
> Needless to say, this didn't happen before the update. Last version I
> used was the one which came with SuSE 9.2 (1.0.8 I think) and everything
> worked fine.
> I also get errors when trying to commit. The return message this time
> was something like: 'Can't convert native string to UTF-8', followed by
> a bunch of non-readable characters.
> Anybody has any clue about what's going on? Is this some conflict with
> any of subversion's dependencies?
> Any help would be much appreciated.
> See ya.
I found in the manual that this could be related to the locale settings,
which haven't changed since I installed my SuSE, as far as I know.
Anyway, 'locale' returns the following:
Btw, I have tried to create a new repository from scratch with svnadmin
v1.2.3 and the problems persist. For example, after 'svnadmin create', I
try to create a basic repository layout, so I issue:
chopsuey_at_chopsuey:~/code/glare> svn mkdir svn://localhost/glare
I enter the commit message and svn responds:
svn: Can't convert string from native encoding to 'UTF-8':
svn: Su mensaje de commit fue dejado en un archivo temporario:
After that, the new directory seems to be there:
chopsuey_at_chopsuey:~/code/glare> svn list svn://localhost
What's going on? I'm getting a little mad about this. I know it has to
be something about character encodings but can't understand what's
wrong. Please lend me a hand.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Tue Oct 4 16:31:53 2005