[SFE-devel] read-only SVN repo, now merging the commits to the new repo - you need to switch your repo URL soon but please wait for the Okay!

[Thomas W. <to...@us...>]

Hi all,

sourceforge now changed the old SVN repo location to read-only
by using a commit hook script preventing the writes.

Please wait a short time until I give you an Okay to switch to
the new repository URL and start sending commit writes.

I'll use the instructions from the SF FAQ and make a Shell-Login 
to the Sourceforge platform. This will migrate the changes
from the old repository to the new one which wasn't used for
writes since the initial copy. The starting point will be
commit 5095 from around Nov 12th 2012 up to April 2013.

I'll send you another email saying that I'm finished with the
migration and then you can switch svn URLs and start sending
commits again.

Please do not switch before the Okay, just to prevent accidential
commits which would potentially mess up the repo if we change
the same files.

About my question on changing the repository to git/mercurial/hg/
fancyother: Thanks for your replys, I must admit there is no
clear winner for now.
As I don't believe that git or hg or others can do much better
with merging conflicting changes, then we can stay with SVN 
for a while.

Thanks much,
Thomas


================


Thats what is displayed if you did not yet switch to the new repo URL:

svn: Commit failed (details follow):
svn: Commit blocked by start-commit hook (exit code 1) with output:

This repository has moved to a new location.  This project was upgraded to the new SourceForge platform, so a one-time move of this repo was performed.  There are instructions for switching to the new location below.  You can no longer commit to the repo at this location.

Please update your configuration with the following command:

    svn relocate ßvn+ssh://USE...@sv.../p/pkgbuild/code/"

Older versions of SVN may need to use the command:

    svn switch --relocate OLD_URL ßvn+ssh://USE...@sv.../p/pkgbuild/code/"

where OLD_URL is the URL from the output of svn info.

If you receive an error regarding mismatched UUIDs, or "Can't find entry" see
http://sourceforge.net/p/forge/community-docs/SVN%20and%20project%20upgrades/
for instructions on how to resolve it.

More information available at: https://sourceforge.net/p/forge/community-docs/Repository%20Upgrade%20FAQ/

result code from pkgtool  --download build-only SFEopus.spec base-specs/opus.spec && svn commit was: 1