Re: Upgrade Subversion from 1.5 to 1.9

2016-03-22 Thread Nico Kadel-Garcia
On Tue, Mar 22, 2016 at 6:47 AM, Stefan Sperling wrote: > On Tue, Mar 22, 2016 at 12:25:42AM -0400, Nico Kadel-Garcia wrote: >> Then, when ready to switchover, make a good backup of the old system, >> *LOCK IT* to prevent any further ocmmits, and switch services to the >> new server. You should be

VisualSVN server / Linux client

2016-03-22 Thread Cathy Mullican
I'm trying to get a Linux svn client to work with a VisualSVN server that has Basic authentication disabled. I've set up Kerberos on the Linux box; I can get a ticket via kinit, join the domain, and I see service tickets for cifs and ldap in klist after joining, so I _think_ that part is OK, altho

Re: Upgrade Subversion from 1.5 to 1.9

2016-03-22 Thread Lorenz
Bert Huijben wrote: >I'm not sure where you read that, but subversion can upgrade working copies >all the way up from 1.0. (See our compatibility guarantee) perhapse here: http://subversion.apache.org/docs/release-notes/1.9.html#wc-upgrade >>Subversion 1.9 can only upgrade working copies created

Re: mod_dav_svn: nested Location '/svn' hinders access to '' in SVNPath Location '/svn'

2016-03-22 Thread Branko Čibej
On 22.03.2016 12:36, Manju C wrote: > Yes, We had two directives, and /svn_old>. we removed the still same issue. > > But if we change the to or > even to its working fine. /svn is a proper prefix of /svn_old, that's what's confusing httpd. Your Location directives should read: ... an

Re: mod_dav_svn: nested Location '/svn' hinders access to '' in SVNPath Location '/svn'

2016-03-22 Thread Manju C
Yes, We had two directives, and . we removed the still same issue. But if we change the to or even to its working fine. -- View this message in context: http://subversion.1072662.n5.nabble.com/mod-dav-svn-nested-Location-svn-hinders-access-to-in-SVNPath-Location-svn-tp196311p1963

Re: Upgrade Subversion from 1.5 to 1.9

2016-03-22 Thread Stefan Sperling
On Tue, Mar 22, 2016 at 12:25:42AM -0400, Nico Kadel-Garcia wrote: > Then, when ready to switchover, make a good backup of the old system, > *LOCK IT* to prevent any further ocmmits, and switch services to the > new server. You should be able to activate a proxy or port forwarding > for the old ser

RE: Upgrade Subversion from 1.5 to 1.9

2016-03-22 Thread Bert Huijben
I'm not sure where you read that, but subversion can upgrade working copies all the way up from 1.0. (See our compatibility guarantee) There is one exception: If a working copy operation was stopped halfway. in this case you need to run 'svn cleanup' with your older Subversion version (or 1.6.x

Re: What branching patterns work with Subversion reintegrate merge?

2016-03-22 Thread Johan Corveleyn
On Mon, Mar 21, 2016 at 3:23 PM, Bob Berger wrote: > Thanks for your reply Stefan. It's very much appreciated. > > Before Subversion 1.8 made the reintegrate merge automatic, I was doing > merges without the reintegrate option, which were, I suppose, inappropriate > "complete merges". They were