#112067 Cannot rename Subversion folder

closed
5
2007-01-16
2007-01-02
No

When I attempt to rename or move files in the folder svn.sourceforge.net/svnroot/sgdk2/trunk/SGDK2IDE/Library/Music I receive an error like:
COPY of Sound: 403 Forbidden (https://svn.sourceforge.net)

That's what I get if I try to rename the "Music" folder to "Sound". I get a similar error if I try to move files (for example "Ben.sgdk2") from the Music folder to another existing folder called "Sound":

COPY of Sound/Ben.sgdk2: 403 Forbidden (https://svn.sourceforge.net)

Discussion

  • David Burley

    David Burley - 2007-01-02

    Logged In: YES
    user_id=597273
    Originator: NO

    Greetings,

    Per:
    https://sourceforge.net/docs/E09#notice

    On November 31, 2006 the access method for Subversion changed. This document reflects those changes. The old method had numerous problems, including spurious 50x error messages and other issues that kept it from functioning fully. This newly documented access method solves many, if not all of the issues with the old mechanism.

    Users of the old method (https://svn.sourceforge.net/svnroot/PROJECTNAME) should switch to the new access method (https://PROJECTNAME.svn.sourceforge.net/svnroot/PROJECTNAME) using these steps:

    1. Make a copy of your local working copy.
    2. Run 'svn info' at the root of the repository content, it should display a line that appears similar to: URL: https://svn.sourceforge.net/svnroot/PROJECTNAME/trunk
    3. Run the following command at the root of the working copy: svn switch --relocate https://svn.sourceforge.net/svnroot/PROJECTNAME/trunk https://PROJECTNAME.svn.sourceforge.net/svnroot/PROJECTNAME/trunk

    Thank you,

    SourceForge.net Support

     
  • David Burley

    David Burley - 2007-01-02
    • assigned_to: nobody --> burley
    • status: open --> closed
     
  • Maarten Brock

    Maarten Brock - 2007-01-07

    Logged In: YES
    user_id=888171
    Originator: NO

    I just had the same problem. And the solution worked.

    But shouldn't you first inform your users that things need to be changed before you switch over?
    I don't read the subversion documentation on a daily basis. I would expect such information in the "SourceForge.net Update" email but I haven't seen one of those since Oct 27.

    Please inform your users.
    Thanks, Maarten

     
  • Benjamin Marty

    Benjamin Marty - 2007-01-07

    Logged In: YES
    user_id=64917
    Originator: YES

    I agree with Maarten. I saw no warning of this change and don't recall receiving any SourceForge update emails in the past couple months.

     
  • Benjamin Marty

    Benjamin Marty - 2007-01-07
    • status: closed --> open
     
  • Benjamin Marty

    Benjamin Marty - 2007-01-07

    Logged In: YES
    user_id=64917
    Originator: YES

    I agree with Maarten. I saw no warning of this change and don't recall receiving any SourceForge update emails in the past couple months.

     
  • David Burley

    David Burley - 2007-01-16
    • status: open --> closed
     
  • David Burley

    David Burley - 2007-01-16

    Logged In: YES
    user_id=597273
    Originator: NO

    Greetings,

    We didn't anticipate the changes we made adding additional problems on top of the existing ones with the SVN infrastructure. That said, once the changes were verified to fix all known outstanding issues with SVN, we weren't going to back it out. The old access method will stick around for months to come, but we aren't going to debug issues with it, move over to the new access method (its painless) and you'll be all set.

    We do expect users to read the site status page when they encounter an issue, and that would have resolved your issue in this case. We do plan on sending out a note about this on the next sitewide mailing, but its not reason enough to send the mail solely for this change due to the small percentage of our userbase on SVN.

    Thank you,

    David Burley
    Quality of Service Analyst, SourceForge.net