On 06/04/12 03:40, Stefan Sperling wrote:
> On Sun, Jun 03, 2012 at 08:27:12PM -0700, Skylar Thompson wrote:
>
>> On 6/1/2012 6:31 AM, Stefan Sperling wrote:
>>
>>> On Fri, Jun 01, 2012 at 06:00:31AM -0700, Skylar Thompson wrote:
>>>
>>>> I'm trying to track down a bizarre binary blob corruption issue. I'm
>>>> running svn v1.7.3 on FreeBSD, and I can replicate the corruption issue
>>>> with the file access method on a fresh repository. Basically I create a
>>>> new repository, "ls -l" the file before committing, remove the file, and
>>>> then update. An "ls -l" at that point shows that the file has shrunk.
>>>> I've attached a script file that demonstrates this.
>>>>
>>>> Any ideas for how I can track this down? I'm sure I'm missing a client
>>>> option or something.
>>>>
>>>> Thanks a bunch!
>>>>
>>> I cannot reproduce the problem you describe.
>>>
>>> Did you compile the port with FreeBSD's custom keyword patch?
>>> I mean this one:
>>> http://www.freebsd.org/cgi/cvsweb.cgi/ports/devel/subversion/files/extra-patch-enhanced-keyword?rev=1.3;content-type=text%2Fplain
>>> If so, can you reproduce the problem without this patch?
>>>
>> This pointer got me to thinking that I should just disable keyword
>> substitution on these commits. I removed the svn:keywords property from
>> the corrupted files, and I can now commit them without problems. Thanks
>> for the tip!
>>
> Ah, so the binary had an expanded $FreeBSD$ keyword in it, and you had
> svn:keywords set on the file?
> If so, your reproduction recipe was incomplete. I was assuming that the
> file in question did not have svn:keywords set because your reproduction
> recipe did not show that this property was set.
>
It looks like ages ago I added an svn:keywords line in the autoprop
section of ~/.subversion/config and had since forgotten about it.
Skylar
Received on 2012-06-04 14:50:49 CEST