Memory leaks after prod upgrade of subversion to 1.7.2

We migrated to subversion 1.7.2 today from 1.4.6 and seeing sudden issues with memory The free memory drops suddenly (24g memory on the box) We have upgraded only the server and clients are various versions 1.4.6 1.4.2 1.6.9 etc I saw some mention of memory leaks but this seems like a major i

Revision/History Graph - DAG (Directed Acyclic Graph)

Is anyone aware of tools which (re)construct a DAG from Subversion repository history and display it pretty much like today's DVCSes? For example: http://code.google.com/a/eclipselabs.org/p/mercurialeclipse/source/list?r=ee7ed7ec51606117613924d0662fc03086787450 https://bitbucket.org/tortoisehg

Merge information in ls OR "svn ls -v -g"

All, I'm raising the issue that there should be an option to include merge information of an "ls -v" in much the same way that "svn blame" supports it. Although, I can easily use "svn blame -g" to find out who /originally/ added a file, it's not intuitive, the more natural method (IMHO) is to use

Hi, does anyone know of a company the can give support to SVN? preferablyin israel. thanks

Best regards, Gil Kremer IT & System Administration Manager Essence Security LTD. (Part of Essence Group) Tel: +972-73-2447733 | Fax: +972(9)9583727 | Mobile: +972-54-3289305 Email: gi...@essence-grp.com | Site: www.essence-grp.com This E-mail and any atta

Re: error when upgrading working copy

Guten Tag Ryan Schmitz, am Montag, 30. April 2012 um 19:36 schrieben Sie: > I'm not sure if the attached screenshot of the dialogue box will > help, but I don't have access to 'svn status', 'commit', or any > other SVN options since the SVN version was upgraded from 1.6 to > 1.7. You can download

RE: error when upgrading working copy

Shoot, forgot the attachment. Here it is. Ryan Schmitz | OLAP Developer / Kalido Specialist | MarketStar | People + Knowledge Accelerating Sales e jschm...@marketstar.com | w 801.786.5287 | m 435.553.1230 | f 801.393.4115 -Original Message- From: Ryan Schmi

RE: error when upgrading working copy

Hi Philip, I'm not sure if the attached screenshot of the dialogue box will help, but I don't have access to 'svn status', 'commit', or any other SVN options since the SVN version was upgraded from 1.6 to 1.7. Yes, version 1.6 was installed previously, and I used to make commits from this direc

Re: error when upgrading working copy

Ryan Schmitz writes: > 'D:\Development\SVN\Releases\TortoiseSVN-1.7.6\ext\subversion\subversion\libsvn_wc\entries.c' > line 126: assertion failed (entry->schedule == svn_wc_schedule_add || > entry->schedule == svn_wc_schedule_normal) Not seen that one before. Do you have 1.6 installed? The wor

error when upgrading working copy

Was using version 1.6.15 and attempted to upgrade working copy to current version 1.7.6. The following error occurred. Both versions are 64 bit. --- Subversion Exception! --- Subversion reported the following In file 'D:\Development\SVN\Releases\To

Re: Error in nitial Run of basic_tests.py

Daniel Shahaf wrote on Mon, Apr 30, 2012 at 17:13:06 +0300: > Tom Bing wrote on Mon, Apr 30, 2012 at 09:55:33 -0400: > > Folks, I did try to study the testing READMEs and the info at > > http://subversion.apache.org/docs/community-guide/building.html before I > > posted here. I have recently Googl

Re: Error in nitial Run of basic_tests.py

Tom Bing wrote on Mon, Apr 30, 2012 at 09:55:33 -0400: > Hi Folks, > > The earlier guidance was a great help. Specifically, this info from Daniel > on Apr 28: > > > *_tests.py look by default for svn in ../../svn/svn --- i.e., build > > outputs. Are you running from a built source tree? If not,

Re: Error in nitial Run of basic_tests.py

Hi Folks, The earlier guidance was a great help. Specifically, this info from Daniel on Apr 28: > *_tests.py look by default for svn in ../../svn/svn --- i.e., build > outputs. Are you running from a built source tree? If not, pass > --bin=/usr/bin. By using --bin=, I was able to run the tests