On 2013-06-26 01:05, Daniel Shahaf wrote:
> olli hauer wrote on Tue, Jun 25, 2013 at 17:06:35 +0200:
>> On 2013-06-25 16:02, Daniel Shahaf wrote:
>>> Daniel Shahaf wrote on Tue, Jun 25, 2013 at 16:55:24 +0300:
>>>> Daniel Shahaf wrote on Tue, Jun 25, 2013 at 13:50:58 +0000:
>>>>> On Mon, Jun 24, 2013 at 09:47:17PM +0200, Ben Smith-Mannschott wrote:
>>>>>> 0x18 is ^X, the ASCII control code for CANCEL. Seems to be working as
>>>>>> designed. ;-)
>>>>>>
>>>>>> No more seriously though, it sure looks like a bug. 0x18 is a perfectly
>>>>>> legal UTF-8 encoding of the unicode character U+0018. Every US-ASCII
>>>>>> character is encoded as itself in UTF-8 and the first 128 Unicode code
>>>>>> points are exactly US-ASCII.
>>>>>>
>>>>>
>>>>> Works for me:
>>>>>
>>>>> % svnadmin create r
>>>>> % mv =( printf 'K 1\nx\nV 1\n\030\nEND\n' > 0 ) r/db/revprops/0/0
>>>>> mv: try to overwrite `r/db/revprops/0/0', overriding mode 0444 (r--r--r--)? y
>>>>
>>>> That last command should have been (equivalently, but without
>>>> munging internals):
>>>>
>>>> % ln -s =true r/hooks/pre-revprop-change
>>>> % svn ps -F =(printf '\030') --revprop -r0 x file://$PWD/r
>>>> property 'x' set on repository revision 0
>>>>
>>>
>>> It still works when I use "svn:log" rather than "x" as the property
>>> name.
>>>
>>> Daniel
>>
>>
>> Thanks for your first diagnostic,
>>
>> I don't have all the details, the issue is part of an FreeBSD PR where this happened to a user.
>> Since I have the same repository in sync (but with subversion 1.7.10) I've taken a look into the file which breaks the sync for the user with subversion 1.8.
>>
>> It is the following FreeBSD PR:
>> http://www.freebsd.org/cgi/query-pr.cgi?pr=179760
>>
>
> So it indeed is FreeBSD - I thought the revnums looked familiar.
>
> I'll note the path of least resistance to getting svnsync to work is to
> ask someone with access to edit the log message on svn.freebsd.org.
>
> Daniel
>
>> Additional I've ask the OP to join the users@ list so you can get more details from first hand.
>
Hi Daniel,
it turns out the OP was not using subversion from ports and the original apache subversion 1.7.x/1.8 has not this issue.
Sorry for the noise and thanks for your help!
--
Regards,
olli
Received on 2013-06-26 07:04:46 CEST