Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 9229335
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 18, 20262026-06-18T05:32:44+00:00 2026-06-18T05:32:44+00:00

I am in the root folder of an SVN-hosted project’s trunk and am exploring

  • 0

I am in the root folder of an SVN-hosted project’s trunk and am exploring setting up two branches.

One branch will be a “snapshot” of the project at the current (stable) revision, and a second branch will be one I’ll work on to apply some new code, test, and then upgrade the trunk to a new version.

My goal is to keep the snapshot as insurance and a quick way to get an older, stable version of our project. The second branch, once we apply fresh code and the tests pass, will be merged back into the trunk, which we offer to the public.

To set up the snapshot, I copied our trunk to a branch called v1p2p3:

$ svn cp https://www.example.com/svn/trunk \ 
         https://www.example.com/svn/branches/v1p2p3 \
         -m "Branching from root trunk to v1p2p3 at r1114"

So far, so good:

Committed revision 1115.

What I would like to do is switch my local repository copy to this branch, to make sure that things worked, but I get an error message:

$ svn switch --relocate https://www.example.com/svn/trunk \
                        https://www.example.com/svn/branches/v1p2p3

The error message is:

svn: E155024: Invalid relocation destination: 
              'https://www.example.com/svn/branches/v1p2p3' 
              (does not point to target)

What am I doing wrong?

(If this doesn’t work, I suspect I can’t get to starting on the more ambitious second branch. I’m looking for a way to do this that won’t damage the existing project layout. Thanks for your advice, and apologies if this is a dumb question.)

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-18T05:32:46+00:00Added an answer on June 18, 2026 at 5:32 am

    You don’t need to --relocate since the branch is within the same repository URL. Just do:

    svn switch https://www.example.com/svn/branches/v1p2p3
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

We try to keep the 'svn:mergeinfo' property on the root branch folder only. However,
I have a project here: svn+ssh://svn@example.com/folder/ProjectName The repository root is svn+ssh://svn@example.com/folder No matter how
We are currently using SVN without Trunk/Branches/Tags structure. So far we were good with
I have a directory D:\SVN_HOME\EclipseWorkspace\MF_CENTER_INFO SVN_HOME - is a root svn working folder MF_CENTER_INFO
I have an existing SVN repository which contains a folder that holds my project.
yesterday i made a svn repository on mydom.com/b-htdocs. in there is project dir 'one'
I deleted a /common folder from the root directory of my SVN store and
the following scenario: We wanna use one root-folder for our eclipse projects. Since i
I am using svn2git to migrate an SVN repository of the standard branch/tag/trunk structure
I have a folder structure in SVN as follows: -> Root -> A ->

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.