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

checkout via http with external pointing at redirected URL

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • trunk
    • ---
    • libsvn_wc
    • None

    Description

      When checking out a permanently moved repository that still has the old URL in
      externals definitions, a warning similar to the one described in issue #4216 is
      issued.
      
      The repository move is properly advertised by a URL redirect rule from the old
      to the new URL. A checkout of the new URL succeeds, but during the checkout of
      an external pointing at the old, redirected URL, this warning is issued:
      
      (dev-build)
      [[[
      svn: warning: apr_err=SVN_ERR_BASE
      svn: warning: W200000: Error handling externals definition for
      '/tmp/trunk.j99/wc2/extdir':
      svn: warning: apr_err=SVN_ERR_SQLITE_CONSTRAINT
      svn: warning: W200035: sqlite[S19]: EXTERNALS.def_repos_relpath may not be NULL
      Checked out revision 3.
      ]]]
      
      The operation succeeds, only this warning is issued. The warning seems to be
      without consequence, as the EXTERNALS table is not actually used by libsvn_wc.
      
      The user reports this in 1.7.11, but I can reproduce the same behavior in trunk.
      So this error remains after the fix of issue #4216. Will attach reproduction recipe.
      

      Original issue reported by neels

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

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

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment