-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
so while we were busy making a lazy consensus on how to deal with the sf upgrade plans, sourceforge has upgraded the repositories for us.
afaik, this changes all the links to checkout/update (SVN) and clone/pull (GIT).
someone might want to update all the information in the wikis.
fgmasdr IOhannes
- -------- Original Message -------- Your svn repository in upgraded project pure-data is now ready for use.
Old repository url: http://pure-data.svn.sourceforge.net/svnroot/pure-data
New repository checkout command: svn checkout --username=zmoelnig svn+ssh://zmoelnig@svn.code.sf.net/p/pure-data/svn/ pure-data-svn
You should do a checkout using the new repository location. The old repository is read-only now.
For more detailed instructions on migrating to your new repo, please see https://sourceforge.net/p/forge/community-docs/Repository%20Upgrade%20FAQ/
On 06/04/13 08:59, IOhannes m zmoelnig wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
so while we were busy making a lazy consensus on how to deal with the sf upgrade plans, sourceforge has upgraded the repositories for us.
afaik, this changes all the links to checkout/update (SVN) and clone/pull (GIT).
in practice this means, that all developers should "relocate" their repository URLs (that is: tell their local checkout of the new location).
this is how i did it, and it was rather painless: $ cd ~/src/svn/pure-data/ $ svn relocate https://svn.code.sf.net/p/pure-data/svn/trunk/
gfmsdr IOhannes
Le 04/06/13 09:19, IOhannes m zmölnig a écrit :
svn relocate https://svn.code.sf.net/p/pure-data/svn/trunk/
here (osx 10.6.8) the command is: svn switch --username sfuser --password sfpwd --relocate https://pure-data.svn.sourceforge.net/svnroot/pure-data/trunk https://svn.code.sf.net/p/pure-data/svn/trunk
n
-
IOhannes m zmoelnig -
IOhannes m zmölnig
-
Nicolas Montgermont