Re: subversion crash report

On Wed, Mar 16, 2011 at 11:08 PM, Ryan Schmidt wrote: > > On Mar 16, 2011, at 14:20, Darryl Fenwick wrote: > > > Apologies for the non-descriptive e-mail previously.  I was either updating > > or committing, I'm don't remember.  Sorry - not very helpful perhaps. You were updating your trunk work

Re: subversion crash report

On Mar 16, 2011, at 14:20, Darryl Fenwick wrote: > Apologies for the non-descriptive e-mail previously. I was either updating > or committing, I'm don't remember. Sorry - not very helpful perhaps. > > My subversion (version 1.6.15) on my 64-bit windows 7 machine has been > unstable. I get

Re: Any way to avoid working copy locks?

Thanks for the responses and good to know this is an issue that's being worked on. We'll look forward to 1.7 eagerly! Dou On Wed, Mar 16, 2011 at 2:02 AM, Johan Corveleyn wrote: > On Wed, Mar 16, 2011 at 6:02 AM, Douglas Pearson > wrote: > > During an "svn update" or "svn commit" my understa

Re: [svn] subversion crash report

On Mar 16, 2011, at 10:08, Darryl Fenwick wrote: > Subversion crashed on my machine, and instructed me to send this crash log. What actions preceded that crash?

Compiling subversion 1.6.16

Hi, all I am trying to compile subversion 1.6.16. autogen.sh does not report any problem. I then run configure: # ./configure --with-apxs=$APACHE/bin/apxs --with-apr=$APACHE/bin/ --with-apr-util=$APACHE/bin/ --with-zlib=/usr/local . checking whether to look for SASL... yes configure: Looki

Re: Failed SVN Verify Logs

Hi Michael, Ankush and everyone else involved, thanks for you help and suggestions to date. I will continue attempting to solve this issue until we reach a resolution. Attempted to run fsfsverify.py on my hotcopied version of the repository. No success. Output is included below: C:\fsfsverify\fsf

[svn] subversion crash report

Subversion crashed on my machine, and instructed me to send this crash log. -- Darryl Fenwick Streamsim Technologies, Inc 650 557 2196 Process info: Cmd line: svn up trunk Version: 1.6.15 (r1038135), compiled Nov 24 2010, 15:10:31 Platform: Windows OS version 6.1 build 7600 Exception: ACC

Re: commit not validated

The problem is not with broken code, it is with old executables trying to read new data structure. There's no build fail. The local user successfully build & run, and idem for the buildmachine(s). The problem is for people working locally on data, not on the source code. "Simply" working on bra

Re: commit not validated

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-03-07 17:28, Bastien Semene wrote: > I'd like to know if it is possible to commit code not updatable (not > validated) until a flag is set/unset ? > > > Here is our problem : > We have projects with source code and datas, and a buildmachine b

Re: Any way to avoid working copy locks?

On Wed, Mar 16, 2011 at 5:02 AM, Johan Corveleyn wrote: > You are right, the locking of big trees in a Subversion working copy > is very expensive, especially on Windows and/or on network filesystems > (NFS, CIFS, ...). See this issue in the issue tracker: It's at least an order of magnitude wor

Re: Failed SVN Verify Logs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-03-16 00:38, Jules Herr wrote: [...] > hotcopy completed, failure with snvadmin verify on revision 607 in both > the old repository and and the newly created hotcopied repository. [...] Jules, you should probably try fsfsverify. Be sure to ru

Re: Any way to avoid working copy locks?

On Wed, Mar 16, 2011 at 6:02 AM, Douglas Pearson wrote: > During an "svn update" or "svn commit" my understanding of SVN is that it > walks the local folder tree, placing some sort of lock file within each .svn > folder. > > The operation is then executed and at the end, the locks are removed.  He