Uploaded image for project: 'Blazegraph (by SYSTAP)'
  1. Blazegraph (by SYSTAP)
  2. BLZG-353

Request to upgrade bigdata repo to latest version of subversion

    Details

    • Type: New Feature
    • Status: Done
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Other

      Description

      I was unable to use the --reintegration flag when trying to merge between two (parent-child) branches. The following message was produced:

      merge --reintegrate https://bigdata.svn.sourceforge.net/svnroot/bigdata/branches/bbb_cleanup /home/resendes/workspace/maven_scaleout/bigdata-core

      Trying to use an unsupported feature

      svn: Retrieval of mergeinfo unsupported by 'https://bigdata.svn.sourceforge.net/svnroot/bigdata'

      Hitting the server URL shows that it's running subversion 1.6.6, so I'm assuming that the problem is due to the fact the actual repo's filesystem is based on an older version of SVN.

      A quick search seems to imply that this can be done (easily?) with server-side tools:

      https://sourceforge.net/apps/trac/sourceforge/ticket/7500

        Activity

        Hide
        bryanthompson bryanthompson added a comment -

        Per the description of the ticket, this can be done with server side tools. An SVN backup needs to be prepare (we do this nightly, but verify that you have a copy and can restore it into a function SVN repo). Then verify the procedure, which is not 100% clear
        - the last time I looked at this, there was a disturbing amount of "how do I deal with this" related to this question. A test conversion then needs to be done. If that works, SCN updates need to be suspended (notify the developers list), a new snapshot of SVN taken (current backup), the conversion performed, and then SVN updates restored (test first, then notify the developers list).

        Show
        bryanthompson bryanthompson added a comment - Per the description of the ticket, this can be done with server side tools. An SVN backup needs to be prepare (we do this nightly, but verify that you have a copy and can restore it into a function SVN repo). Then verify the procedure, which is not 100% clear - the last time I looked at this, there was a disturbing amount of "how do I deal with this" related to this question. A test conversion then needs to be done. If that works, SCN updates need to be suspended (notify the developers list), a new snapshot of SVN taken (current backup), the conversion performed, and then SVN updates restored (test first, then notify the developers list).
        Hide
        bryanthompson bryanthompson added a comment -

        We have moved to GIT.

        Show
        bryanthompson bryanthompson added a comment - We have moved to GIT.

          People

          • Assignee:
            Unassigned
            Reporter:
            resendes resendes
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: