RE: Upgrading from 1.4 to 1.6.3

Here's the interesting part from the apache access log. Even though
this is s a fresh WC that I recently checked out onto my computer, for
some reason tortoisesvn is trying to access top level (/toolbox) without
the leading dash.

I've run the svn merge through command line on the server and everything
went without any problems.

-----Original Message-----
From: Vitaliy Sholokhov [mailto:vsholokhov_at_marvel.com]
Sent: Monday, July 13, 2009 10:46 AM
To: users_at_subversion.tigris.org
Subject: RE: Upgrading from 1.4 to 1.6.3

My bad, I typed in couple URIs manually into the message :-) We're using
port 81 for all repositories, therefore all connections are done on port
81

-----Original Message-----
From: Stefan Sperling [mailto:stsp_at_elego.de]
Sent: Monday, July 13, 2009 10:38 AM
To: Sholokhov, Vitaliy
Cc: users_at_subversion.tigris.org
Subject: Re: Upgrading from 1.4 to 1.6.3

On Mon, Jul 13, 2009 at 10:22:06AM -0400, Vitaliy Sholokhov wrote:
> Here's what happens...
> We have a trunk located at http://crossbow/toolbox/trunk and developer

> branches at http://crossbow/toolbox/branches
>
> When I try to merge from trunk to my branch via tortoisesvn
> (http://crossbow/toolbox/trunk -->
> http://crossbow/toolbox/branches/vitaliy) I get the error:
>
> ---
> Error: Repository moved permanently to 'http://crossbow:81/toolbox/';
> please relocate
> ---
>
> but there's no way to relocate the trunk since I'm pulling information

> from the trunk to my branch, not vice versa
>
> The repositories have been updated via 'svnadmin upgrade'

What I don't get is why you are using port 80 (the default) in the URLs
while the server is of the opinion that port 81 should be used.

For some reason, your HTTP server is sending a HTTP 301 response to your
merge request which causes the client to print the error message you are
seeing. What's causing this 301?

It can't have anything to do with svnadmin upgrade. The error you are
seeing is at the HTTP level. svnadmin uses plain file access and has
zero idea about how a repository is being accessed by its users (svn://,
http://, etc.).

Stefan

************************************************************************
******
Nothing contained in this e-mail shall (a) be considered a legally
binding agreement, amendment or modification of any agreement with
Marvel, each of which requires a fully executed agreement to be received
by Marvel or (b) be deemed approval of any product, packaging,
advertising or promotion material, which may only come from Marvel's
Legal Department.
************************************************************************
******
THINK GREEN - SAVE PAPER - THINK BEFORE YOU PRINT!

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageI
d=2370934

To unsubscribe from this discussion, e-mail:
[users-unsubscribe_at_subversion.tigris.org].

******************************************************************************
Nothing contained in this e-mail shall (a) be considered a legally binding agreement, amendment or modification of any agreement with Marvel, each of which requires a fully executed agreement to be received by Marvel or (b) be deemed approval of any product, packaging, advertising or promotion material, which may only come from Marvel's Legal Department.
******************************************************************************
THINK GREEN - SAVE PAPER - THINK BEFORE YOU PRINT!

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2370937

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].