Re: Binary blob corruption

2012-06-05 Thread Skylar Thompson
On 06/05/12 18:07, Nico Kadel-Garcia wrote: > > On Tue, Jun 5, 2012 at 8:54 AM, Daniel Shahaf <mailto:d...@daniel.shahaf.name>> wrote: > > Stefan Sperling wrote on Mon, Jun 04, 2012 at 14:52:59 +0200: > > On Mon, Jun 04, 2012 at 05:50:11AM -0700, Skylar Thompso

Re: Binary blob corruption

2012-06-04 Thread Skylar Thompson
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: >>> >>&g

Re: Binary blob corruption

2012-06-03 Thread Skylar Thompson
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 >> w

Re: Binary blob corruption

2012-06-02 Thread Skylar Thompson
On 06/01/12 06:43, Philip Martin wrote: > Skylar Thompson writes: > > >> [skylar@hopper ~]$ svnadminmkdir svnrepo >> [skylar@hopper ~]$ svnadmin create svnrepo >> [skylar@hopper ~]$ mkdir svn >> [skylar@hopper ~]$ cd svn >> [skylar@hopper

Re: Binary blob corruption

2012-06-02 Thread Skylar Thompson
On 06/02/12 02:21, Stefan Sperling wrote: > On Fri, Jun 01, 2012 at 03:39:07PM +0200, Thorsten Schöning wrote: > >> Guten Tag Skylar Thompson, >> am Freitag, 1. Juni 2012 um 15:00 schrieben Sie: >> >> >>> I've attached a script file that demonstr

Re: Binary blob corruption

2012-06-01 Thread Skylar Thompson
On 06/01/12 06:31, 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 >>

Binary blob corruption

2012-06-01 Thread Skylar Thompson
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.