Uploaded image for project: 'Subversion'
  1. Subversion
  2. SVN-4562

svn copy URL1 URL2 -- multiple repositories

    XMLWordPrintableJSON

    Details

    • Type: New Feature
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: trunk
    • Fix Version/s: ---
    • Component/s: unknown
    • Labels:
      None

      Description

      This is a feature request for
      svn copy svn:///C:/their/remo​te/repo/folder/ svn:///C:/my/local/repo/folder/
      
      this command currently fails, returning
      svn: E200007: Source and destination URLs appear not to point to the same
      repository.
      
      ---
      
      SVN is not a distributed but a centralized version control system. This is
      clear. It is therefore acceptable to me that it does not allow branching to
      another repo. However, it is not clear to me why it would need to limit merges
      to work only on the same repo. See the following example.
      
      -- The following story was posted in the forum, see
      http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3093562.
      --
      
      There is a project in a shared svn repo, with a trunk and release branches in
      it. Every time a new release is about to be ready, a new branch is created to
      stabilize the release.
      
      My version of the project is based on a release branch, but it is not really
      branched off. Instead I created a local repo started off from a local working
      copy of a release branch. Then I applied a couple of dozens of patches to
      customize it, and committed one by one to this local repo.
      
      Now it is time to sync up with the next release.
      
      --trunk-------------​-------------------
               \              \
                -- release 1   -- release 2
                  :               |
                   :              |
                   ?- my repo ----+
      
      Along the dotted line, I would preferably create a repository by using
        svn copy <remote url> <local url>
      with the intent to copy the remote repo history or a reference to the remote
      history.
      
      
      Why do I need a local repository / why cannot I use a working copy of the remote
      repository?
      I need version control of my own patches.
      
      Whyh do not you use vendor branch support?
      Ok, so these were my trials.
      
      svn copy svn:///C:/their/remo​te/repo/folder/ svn:///C:/my/local/repo/folder/
      svn: E200007: Source and destination URLs appear not to point to the same
      repository.
      
      svn copy C:\my\remote\working\copy svn:///C:/my/local/repo/folder/
      svn: E210005: Unable to connect to a repository at URL 'svn:///C:/my/local/repo/'
      svn: E210005: No repository found in 'svn:///C:/my/local/repo/'
      
      svn copy C:\my\remote\working\copy svn:///C:/my/local/r​epo/folder/conf
      svn: E170009: Repository UUID 'fd535e2c-1125-...' doesn't match expected UUID
      'b456876b-0849-...'
      
      svn import --no-auto-props --no-ignore -m "..." C:\my\remote\working\copy
      svn:///C:/my/local/repo/folder/
      
      While the last command did not return error messages, there is no trace of any
      history preservation or remote referencing either. So I am at the same point as
      I was before.
      
      References
      http://svnbook.red-bean.com/en/1.8/svn.advanced.vendorbr.html
      http://svnbook.red-bean.com/en/1.8/svn.ref.svn.c.copy.html
      http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3098839
      http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3093562
      http://subversion.tigris.org/issues/show_bug.cgi?id=4547
      

      Original issue reported by mr_user1

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              subversion-importer Subversion Importer
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated: