Re: SVN 1.7.2 crashes immediately on start in APR xlate/xlate.c

2012-01-29 Thread Daniel Shahaf
Sebastian Magda wrote on Sat, Jan 28, 2012 at 00:05:19 -0800: > Built and installed the latest stable version > subversion-1.7.2.tar.gz > Crashes immediately on start: > > : svn > Segmentation fault (core dumped) > > Build details

The content was displayed when i executed the command "update"

2012-01-29 Thread priest
--- Subversion Exception! --- Subversion encountered a serious problem. Please take the time to report this on the Subversion mailing list with as much information as possible about what you were trying to do. But please first search the mailing list

SVN 1.7.2 crashes immediately on start in APR xlate/xlate.c

2012-01-29 Thread Sebastian Magda
Built and installed the latest stable version subversion-1.7.2.tar.gz Crashes immediately on start: : svn Segmentation fault (core dumped) Build details: : ./configure --with-ssl --with-apr=/usr/local/apache2 --with-apr-util=/usr

RE: TortoiseSVN crash report (cleanup failed)

2012-01-29 Thread Ng, Alan
Additional information: I discovered that the root of the problem was that at some point in the past (months ago) the SourceForge repository got *both* a lowercase and an uppercase version of the same filename. On Macs, svn brought down only the uppercase file. On Windows XP, TortoiseSVN brought do

TortoiseSVN crash report (cleanup failed)

2012-01-29 Thread Ng, Alan
As far as I can tell, the repository on this machine (which generated the error message copied below) got confused at some point in the past about upper/lowercase on one filename. My SourceForge repository has the filename all in lowercase, whereas this Windows machine had the corresponding file

Re: svn status returns incorrect results on Windows 7

2012-01-29 Thread Konstantin Kolinko
2012/1/27 Justin Johnson : > Hi, > > I am running Subversion 1.7.2 64 bit installer from CollabNet on > Windows 7.  The problem I'm experiencing can be seen in the output > below.  In summary, svn status is returning incorrect results, > sometimes not showing that something has been modified and so