Results 1 to 5 of 5

Thread: Post Subversion 1.6.17 to 1.7.1 upgrade help.

  1. #1

    Unhappy Post Subversion 1.6.17 to 1.7.1 upgrade help.

    Hi every one, i have just upgraded my subversion from 1.6.17 to 1.7.1

    replaced the mod_dav.iso and mod_svn.iso for apapche and restarted


    every thing apparears to be running ok untill i go to perform a commit and i am presented with the following error

    Code:
    Commit
    Commit failed (details follow):
    Repository moved temporarily to '/login/repositories/reponame/!svn/me';
    please relocate
    My setup is as follows

    Apache 2.2.21
    MySQL 5.5.16
    PHP 5.3.8
    phpMyAdmin 3.4.5

    Subversion 1.7.1
    USVN 1.0.2 front end


    any ideas whats going on here ?


    Things i have tried

    Reverting back to Subversion 1.6.17 completely removed the error
    i have checked all apache 2 settings (moduals updating, diretory path being set e.t.c) they seem absolutely fine (unless iv overlooked some thign that needs updating)

    any help would be most appreciated.

    if all else fails i supose we will have to revert back to 1.6.17 again.

    thanks
    Last edited by Terminal-Access; 11-20-2011 at 10:52 AM.

  2. #2
    Hard to say. It appears that something is interfering with the new URLs used by Subversion's v2 protocol. You can confirm that by adding "SVNAdvertiseV2Protocol off" to the Location block. I don't know what is interfering, perhaps one of the other modules? Perhaps a custom 404 handler? A redirect directive?

  3. #3
    iv since tried to reproduce this on a dev server i have running with a stock version of apache 2 installed with only the necisarry extra moduals dav and svn require and im still getting the same problem.

    I have previously seen that the moved temp error essage can occur when the url dose not contain a trailing forward slash and have noticed that the commit url with 1.7.1 dose not have a forward slash

    i dont know if this happens for every one but maby its some thing, then again i could just be shooting in the dark.

  4. #4
    Curious if you tried to disable the HTTPv2 using Philip's suggestion? From what I've seen lately any post upgrade commit errors are caused by the new transport protocol (httpv2) and turning it off has worked for most.
    Patrick Burma
    WANdisco, Inc.

    uberSVN: Apache Subversion Made Easy
    http://www.uberSVN.com

    Everything you need to deploy Subversion in the Enterprise
    http://www.wandisco.com/subversion

  5. #5
    Quote Originally Posted by pburma View Post
    Curious if you tried to disable the HTTPv2 using Philip's suggestion? From what I've seen lately any post upgrade commit errors are caused by the new transport protocol (httpv2) and turning it off has worked for most.
    Acctually after all the work we did trying to use 1.7.1 we have now re done our colo server and opted to go with ubersvn, and thats working absolutly fine using 1.7.1 binaries

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •