Great, Thanks. My expectation is that it will all work fine... until you get to
file locking - which will fail.
-Original Message-
From: Alagazam.net Subversion [mailto:s...@alagazam.net]
Sent: 03 February 2014 21:51
To: Steve Davis
Cc: users@subversion.apache.org
Subject: Re: Possible
nts in the second link)...
So it's not a problem with Redmine or with apache - but it >is< a problem when
the binaries used aren't built using the same version of compiler (this is all
theory at the moment of course)
-Original Message-
From: Steve Davis
Sent: 03 February 201
-
From: Philip Martin [mailto:philip.mar...@wandisco.com]
Sent: 03 February 2014 15:34
To: Steve Davis
Cc: users@subversion.apache.org
Subject: Re: Possible bug in SVN 1.8.3 and 1.8.4 - file locking
Steve Davis writes:
> Response:
>
> svn: E200035: sqlite[S19]: LOCK.lock_token may no
Any further feedback very much appreciated.
Thanks - Steve
-Original Message-
From: Ben Reser [mailto:b...@reser.org]
Sent: 01 February 2014 01:39
To: Steve Davis; users@subversion.apache.org
Subject: Re: Possible bug in SVN 1.8.3 and 1.8.4 - file locking
On 1/31/14, 1:54 PM, Steve Davis wrot
[mailto:b...@qqmail.nl]
Sent: 02 February 2014 15:26
To: 'Ben Reser'; Steve Davis; users@subversion.apache.org
Subject: RE: Possible bug in SVN 1.8.3 and 1.8.4 - file locking
> -Original Message-
> From: Ben Reser [mailto:b...@reser.org]
> Sent: zaterdag 1 februari 2014 0
Hi -
I have been trying to pin down the cause of an issue my users are seeing when
using SVN. It's actually a Windows Server 2008 R2 (64 bit) Bitnami-Redmine
stack of SVN, but I've tried to scrape it back to the most basic levels during
debugging, to hopefully omit any Bitnami-related issues.
