Hi,

On Friday 25 November 2011 Juergen Weigert wrote:
> The move is done!
> The new server is alive and kicking. Faster than we thought.

Well done, Jürgen and Julian! Thanks a lot for your efforts!


> The new checkout URL for the opensuse-doc repo is:
>  svn co https://svn.opensuse.org/svn/opensuse-doc
> 
> A browser view is available at:
>  http://svn.opensuse.org/viewvc/opensuse-doc/
> 
> I migrated my existing working directory by
>   $ cd to_the_dir_countaining_trunk
>   $ svn info | grep URL
>   $ svn switch --relocate
> svn+ssh://[email protected]/svnroot/repos/opensuse-doc
> https://svn.opensuse.org/svn/opensuse-doc
> $ svn up
> [...]

Just for the records:
In my working directory, I have a https URL instead of the svn+ssh schema. 
When I did the switch, I've got the following error message:

$ svn switch --relocate \
   https://svn.berlios.de/svnroot/repos/opensuse-doc/trunk \
   https://svn.opensuse.org/svn/opensuse-doc
svn: Relocate can only change the repository part of an URL

To fix that, I needed a slightly different procedure:

1. $ cd to_the_dir_countaining_trunk

2. Determine your root URL:
   $ svn info | grep URL
https://svn.berlios.de/svnroot/repos/opensuse-doc

3. Use the root URL from step 2 and combine the new opensuse URL plus 
   the trunk path:
   $ svn switch --relocate \
     https://svn.berlios.de/svnroot/repos/opensuse-doc/trunk \
     https://svn.opensuse.org/svn/opensuse-doc/trunk

4. Update:
   $ svn up

That have worked for me. I could successfully commit to the new openSUSE SVN.
Thanks! :-)

-- 
Gruß/Regards,
    Thomas Schraitle

----------------------------------------------------------------------
SUSE LINUX Products GmbH   (o<   
Maxfeldstrasse 5           /\\   Documentation Specialist
90409 Nuernberg, Germany  _\_v   http://www.suse.com
http://lizards.opensuse.org/author/thomas-schraitle/
SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, 
Felix Imendörffer, HRB 21284 (AG Nürnberg) 
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]

Reply via email to