You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by mfass <mf...@gmail.com> on 2010/10/22 04:37:45 UTC
Best way to copy project from one server to another, and then back
I have two subversion servers. One is an open source repository not
controlled by me, and the other is a closed source repository which is
controlled by me. Both the open source and the closed source build together
to make one set of software. The closed source is a firewalled server at my
place of employment. Currently we are in need to rename the project for a
launch announcement at an upcoming conference.
Becasue of the sensitive nature of the announcement, we cannot make the
changes to the open source (sourceforge) project because our hosting service
will not temporarily restrict anonymous access to the source code to just
commiter's.
To workaround this, we decided that we will pull the source code from the
sourceforge project, into our internal, closed source repository. We then
want to make the changes, and once the announcement of the naming etc. has
been done, we can merge back to our sourceforge project the naming changes
that were made.
I was thinking of doing it via svn copy from one project to the other, and
then taking the diff and copying back as we need.
Just looking for anyone who may have a better way to do it, as the amount of
files that are changing, could become large, not huge, but big enough to
cause me to want to do it in a more automated fashion.
Thanks for anay help!
--
View this message in context: http://old.nabble.com/Best-way-to-copy-project-from-one-server-to-another%2C-and-then-back-tp30024985p30024985.html
Sent from the Subversion Users mailing list archive at Nabble.com.
Re: Best way to copy project from one server to another, and then back
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Oct 21, 2010, at 23:37, mfass wrote:
> I have two subversion servers. One is an open source repository not
> controlled by me, and the other is a closed source repository which is
> controlled by me. Both the open source and the closed source build together
> to make one set of software. The closed source is a firewalled server at my
> place of employment. Currently we are in need to rename the project for a
> launch announcement at an upcoming conference.
>
> Becasue of the sensitive nature of the announcement, we cannot make the
> changes to the open source (sourceforge) project because our hosting service
> will not temporarily restrict anonymous access to the source code to just
> commiter's.
>
> To workaround this, we decided that we will pull the source code from the
> sourceforge project, into our internal, closed source repository. We then
> want to make the changes, and once the announcement of the naming etc. has
> been done, we can merge back to our sourceforge project the naming changes
> that were made.
>
> I was thinking of doing it via svn copy from one project to the other, and
> then taking the diff and copying back as we need.
You cannot "svn copy" between repositories, only within a repository.
Subversion really isn't designed to do what you propose. I don't have a better suggestion for you. Maybe someone else does.
Re: Best way to copy project from one server to another, and then back
Posted by Siva Kumar <gs...@gmail.com>.
> Just looking for anyone who may have a better way to do it, as the amount of
> files that are changing, could become large, not huge, but big enough to
> cause me to want to do it in a more automated fashion.
you should be able to achieve this by using git-svn or svk to create a local
copy. Make the commits into the local version and port those multiple
commits to sourceforge once the announcement is made.
Re: Best way to copy project from one server to another, and then
back
Posted by Ulrich Eckhardt <ec...@satorlaser.com>.
On Friday 22 October 2010, mfass wrote:
> I have two subversion servers. One is an open source repository not
> controlled by me, and the other is a closed source repository which is
> controlled by me. Both the open source and the closed source build
> together to make one set of software. The closed source is a firewalled
> server at my place of employment. Currently we are in need to rename the
> project for a launch announcement at an upcoming conference.
>
> Becasue of the sensitive nature of the announcement, we cannot make the
> changes to the open source (sourceforge) project because our hosting
> service will not temporarily restrict anonymous access to the source code
> to just commiter's.
>
> To workaround this, we decided that we will pull the source code from the
> sourceforge project, into our internal, closed source repository. We then
> want to make the changes, and once the announcement of the naming etc. has
> been done, we can merge back to our sourceforge project the naming changes
> that were made.
>
> I was thinking of doing it via svn copy from one project to the other, and
> then taking the diff and copying back as we need.
As mentioned, svn copy only works within a single repository.
Suggestion: You can export from one and import into the other using the same
strategy as for a "vendor branch", which is explained in the SVN book. You
can then modify and test your changes locally, until you are satisfied with
them.
Once that is done, you simply commit those changes to the source repository.
For that, you could use the same tool as for creating the vendor branch. Be
aware though, that this will sync the repository with a source tree, so if
any changes were made in between pulling the tree and pushing the tree, those
will be lost. You should consider using a feature branch or maybe just using
a working copy that is synced with both changes from upstream and local
changes due to the name change, but that requires some manual care.
Uli
--
ML: http://subversion.apache.org/docs/community-guide/mailing-lists.html
FAQ: http://subversion.apache.org/faq.html
Docs: http://svnbook.red-bean.com/
Sator Laser GmbH, Fangdieckstraße 75a, 22547 Hamburg, Deutschland
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932
**************************************************************************************
Sator Laser GmbH, Fangdieckstraße 75a, 22547 Hamburg, Deutschland
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932
**************************************************************************************
Visit our website at <http://www.satorlaser.de/>
**************************************************************************************
Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen, weitergeleitet, veröffentlicht oder anderweitig benutzt werden.
E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte Änderungen enthalten. Sator Laser GmbH ist für diese Folgen nicht verantwortlich.
**************************************************************************************