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

Re: svnsync: Cannot accept 'svn:log' property because it is not encoded in UTF-8

From: Marc Lustig <ml_at_marclustig.com>
Date: Fri, 10 Jul 2009 11:19:53 +0200

Thanks a lot, Ben, for the explanation.
It makes sense, and I was able to fix it.

2009/7/10 B Smith-Mannschott <bsmith.occs_at_gmail.com>:
> On Fri, Jul 10, 2009 at 09:58, Marc Lustig<ml_at_marclustig.com> wrote:
>> Hi there
>>
>> I am trying to mirror a 1.5.1 based repo using a 1.6.3 client and mirror-repo
>>
>> The svnsync command failes after about 20000 revs with following error message:
>>
>> svnsync: Cannot accept 'svn:log' property because it is not encoded in UTF-8
>>
>> I had no hit on google for that message,
>> Could somebody please elaborate what is the proper way to fix that and
>> to make svnsync to work?
>>
>> Do I have to edit the log properties?
>
> Yes, I believe so. Subversion has always *wanted* svn:log to be proper
> UTF-8, but only started enforcing this with 1.6.0.
>
> Older clients with misconfigured encoding can submit wrongly encoded
> log messages to older servers. 1.6.0 and later clients will not make
> this error, and 1.6.0 servers will refuse such log messages. And
> that's what's tripping up svnsync.
>
> Unfortunately, there's no way for 1.6.0 to know what the user meant
> when it encounters a log message that's not UTF-8 encoded (without
> further information, it would amount to guessing the encoding).
>
> // Ben
>

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2369618

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-07-10 11:20:53 CEST

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

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