Hi all,
looks like the anonymous cvs outage on SF lasts for some time and there are no good perspective :(.
As we try to offer public access to the latest openser code, we switched the snapshots from the anonymous cvs to the developers cvs. The snapshots for the development branch will be generated 6 times per days. Please use them instead of pserver. http://www.openser.org/downloads/snapshots/openser-devel/
in the mean while we investigate the possibility of setting a non-SF anonymous CVS as backup - still searching on synchronizing the CVS (if someone has any experience on that, help will be really appreciated).
sorry for the inconvenience!
regards, bogdan
Bogdan-Andrei Iancu writes:
in the mean while we investigate the possibility of setting a non-SF anonymous CVS as backup - still searching on synchronizing the CVS (if someone has any experience on that, help will be really appreciated).
how about syncing to svn with
http://www.polarion.org/index.php?page=overview&project=svnimporter
-- juha
Hi Juha,
thanks for the hint - I will take a look on it and we might set up a anonymous SVN on a non-sf machine (as I understood, the sync works from cvs to svn only)
regards, bogdan
Juha Heinanen wrote:
Bogdan-Andrei Iancu writes:
in the mean while we investigate the possibility of setting a non-SF anonymous CVS as backup - still searching on synchronizing the CVS (if someone has any experience on that, help will be really appreciated).
how about syncing to svn with
http://www.polarion.org/index.php?page=overview&project=svnimporter
-- juha
On Friday 21 April 2006 13:22, Bogdan-Andrei Iancu wrote:
Hi Juha,
thanks for the hint - I will take a look on it and we might set up a anonymous SVN on a non-sf machine (as I understood, the sync works from cvs to svn only)
You can try to use tailor. It is able to synchronize between every known versioning system. If you use debian is already available as a debian package, else check the link at the end of the description below.
Description: migrate changesets between version control systems The tailor tool moves patches and changesets between different repositories, preserving as much information as possible. The repositories can be managed by different version control systems. Currently, ArX, Bazaar, Bazaar-NG, Codeville, CVS, Darcs, Git (Cogito), Mercurial, Monotone, Subversion, and Tla are supported.
While tailor is useful for one-time operation, when switching to a different version control system, it can also synchronise repositories on an ongoing basis. Changesets are either pulled one-way from a master repository, or migrated back and forth for full two-way synchronisation.
Homepage: http://www.darcs.net/DarcsWiki/Tailor