Re: [Plplot-devel] cvs to svn conversion
On 2007-03-21 00:46-0700 Alan W. Irwin wrote: Tomorrow I plan to compare selected CVS and SVN tagged releases for lbproject, upload to SF, and do final checks of the SF result to complete the lbproject conversion to subversion. Done. Almost all of the conversion is handled by two high-level scripts, and I am completely satisfied by the new lbproject svn results at SourceForge. On to yplot Alan __ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); PLplot scientific plotting software package (plplot.org); the Yorick front-end to PLplot (yplot.sf.net); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __ Linux-powered Science __ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
Re: [Plplot-devel] cvs to svn conversion
Hi Alan, Is this long import process the step that takes so long in the official SourceForge process? They mention 24-hours or more to complete the task. Not really, I mean the svn import file is about 250Mb(!!) and it needs some time to import it, but will need maybe 15 minutes or so. But my hosting plan (shared) allows to have ssh access where I can do such things, but they warn you not to use a lot of computing time, otherwise they come and force me to use a dedicated server :). Therefore I stopped it, since it took a long time even for this 250 releases. Before we do the conversion to subversion at SourceForge, I think we should at least provide an opportunity for PLplot developers to get familiar with svn. Could you (or somebody else) make a complete test PLplot subversion repository available for us to play with? Because of the above reason, no, but what I want to try is to give the path to the repository via the http:// address, so it's than uploaded (don't know if this is less strain on the computing power but who knows) but this I can do next week earliest. Alternatively, could you add instructions (probably about the exact import step that must be done) to your cookbook about how each of us could set up our own local test PLplot subversion repository? svnadmin load path_to_repository/plplot_svn svndump Some of the tests I would like to do for such a test repository are whether we could reproduce a number of our historical source releases and our [...] epochs. Reproduction of some of our historical tarball releases and our complete ChangeLog would help to satisfy me on this issue. In answer to your question, I think we should go ahead with the conversion to subversion, but only after the next stable release (i.e., 5.8.0). That gives the current shakedown process for our new CBS (i.e., the current on-going set of 5.7.x development releases) time to complete without interference from a repository format switch. If there is a well-known deadline for the conversion after the 5.8.0 release, that should give plenty of lead time (see below) for our developers to play with subversion and do all the tests that they think our necessary. Furthermore, if we do the conversion post-5.8.0, then that allows us to use the 5.9.x development cycle in part for working out any script issues (remember, many of our release scripts currently depend on cvs). This sounds good to me. Best Regards, Werner -- Dipl. Ing. Werner Smekal Institut fuer Allgemeine Physik Technische Universitaet Wien Wiedner Hauptstr 8-10 A-1040 Wien Austria email: [EMAIL PROTECTED] web: http://www.iap.tuwien.ac.at/~smekal phone: +43-(0)1-58801-13463 (office) +43-(0)1-58801-13469 (laboratory) fax: +43-(0)1-58801-13499 - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
[Plplot-devel] cvs to svn conversion
Hi, I ran through the source forge documentation about the cvs to svn conversions and I tested practically all steps. I made a copy of the whole repository, converted it, and uploaded it to my server, but stopped the import since it just took too long (it finished 256 revisions of 7586) - you can see this historic plplot revision here: http://svn.miscdebris.net/plplot/trunk/plplot/ . Anyway, below you'll find the cookbock for this process. Rather straight forward. We also need to agree, when to do it and how. My proposal would be to do it after the next release. Nobody should commit than something for some days, until it is imported into the sf-svn repository and tested/compared. If the conversion was done satisfactorily we should than use svn exclusively. What do you think about that? Regards, Werner = Transition from cvs to svn (http://sourceforge.net/docman/display_doc.php?docid=31070group_id=1#import) 1) Download and install cvs2svn (apt-get install cvs2svn, http://cvs2svn.tigris.org/) 2) Get cvs repository: rsync -av rsync://plplot.cvs.sourceforge.net/cvsroot/plplot/* plplot-cvsbackup 3) Convert to svn: cvs2svn --dumpfile=svndump --dump-only . cvs2svn Statistics: -- Total CVS Files: 2655 Total CVS Revisions: 18891 Total Unique Tags: 56 Total Unique Branches: 39 CVS Repos Size in KB:35920 Total SVN Commits:7586 First Revision Date:Wed May 20 23:31:22 1992 Last Revision Date: Sun Jan 7 22:43:02 2007 4) Compress the dump file (to 60Mb): tar czf svndump.tar.gz svndump == Didn't do the following part == # scp svndump.tar.gz [EMAIL PROTECTED]:/home/groups/P/PR/plplot/svndump.tar.gz # Login to the SourceForge.net website. # Go to the project summary page (https://www.sf.net/projects/plplot). # Click on the 'Admin' link. # Click on the 'Subversion' admin page link. # Click on the 'migrate' link on the 'Migration Instructions' section of the page. # Key in the filename of the archive into the 'Source path' field, noting that it must comply with the filename restrictions previously described. # Check the 'Replace' check box in the same column, if you wish to replace the existing content with the new content to be added. # Enter the value you want passed to the --parent-dir argument of the svnadmin load command into the 'Destination' field. For most users, this would be left blank. Note that the destionation directory must be created but empty for this to work. # Click on the 'Submit' button. # The migration will be finished within 24 hours. It could be finished in as soon as an hour or two, depending on the size of your CVS repository and the number of projects queued for migration in front of yours. Returning to the page will display whether it completed, failed or is still in queue. Valueable links: Free book (online, pdf): http://svnbook.red-bean.com/ Windows svn client: http://tortoisesvn.tigris.org/ MacOSX svn client: http://scplugin.tigris.org/ subversion homepage: http://subversion.tigris.org/ Linux svn clients: e.g. kdesvn (http://www.alwins-world.de/programs/kdesvn/) Sourceforge svn help page: http://sourceforge.net/docman/display_doc.php?docid=31070group_id=1 Other clients and links: http://subversion.tigris.org/links.html - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
Re: [Plplot-devel] cvs to svn conversion
Hi Werner. Thanks for creating the conversion cookbook. On 2007-01-13 00:19+0100 Werner Smekal wrote: I ran through the source forge documentation about the cvs to svn conversions and I tested practically all steps. I made a copy of the whole repository, converted it, and uploaded it to my server, but stopped the import since it just took too long (it finished 256 revisions of 7586) - you can see this historic plplot revision here: http://svn.miscdebris.net/plplot/trunk/plplot/ . That's already an interesting result. Just have a look at what is (not) in bindings to get a feel for what PLplot was like in that early (4.99c) era. Is this long import process the step that takes so long in the official SourceForge process? They mention 24-hours or more to complete the task. Anyway, below you'll find the cookbock for this process. Rather straight forward. We also need to agree, when to do it and how. My proposal would be to do it after the next release. Nobody should commit than something for some days, until it is imported into the sf-svn repository and tested/compared. If the conversion was done satisfactorily we should than use svn exclusively. What do you think about that? Before we do the conversion to subversion at SourceForge, I think we should at least provide an opportunity for PLplot developers to get familiar with svn. Could you (or somebody else) make a complete test PLplot subversion repository available for us to play with? Alternatively, could you add instructions (probably about the exact import step that must be done) to your cookbook about how each of us could set up our own local test PLplot subversion repository? Some of the tests I would like to do for such a test repository are whether we could reproduce a number of our historical source releases and our complete historical ChangeLog (currently created by cvs2cl from our CVS repository) from a test subversion repository. I think such tests are essential because I have already had one bad experience with our current CVS repository; it turned out to be completely broken for branches until a lot of maintainence (re-deleting a whole bunch of files which kept rising from the dead) was done. So there still may be something non-standard in our CVS that will cause the conversion process to give bad results for some epochs. Reproduction of some of our historical tarball releases and our complete ChangeLog would help to satisfy me on this issue. In answer to your question, I think we should go ahead with the conversion to subversion, but only after the next stable release (i.e., 5.8.0). That gives the current shakedown process for our new CBS (i.e., the current on-going set of 5.7.x development releases) time to complete without interference from a repository format switch. If there is a well-known deadline for the conversion after the 5.8.0 release, that should give plenty of lead time (see below) for our developers to play with subversion and do all the tests that they think our necessary. Furthermore, if we do the conversion post-5.8.0, then that allows us to use the 5.9.x development cycle in part for working out any script issues (remember, many of our release scripts currently depend on cvs). By the way, I am not sure when 5.8.0 will be happening, but my best guess is probably something like 4-6 months from now. For the forthcoming 5.7.2 development release we are going to deploy something entirely new (binary releases for windows users), and presumably it will take us a while to respond to feedback from our windows users on those releases and any additional CBS and code issues they might find. So I wouldn't be surprised if we need at least a 5.7.3 development release (both source and binary) and probably a release candidate release for 5.8.0 before we finally go ahead with 5.8.0 final. Alan __ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); PLplot scientific plotting software package (plplot.org); the Yorick front-end to PLplot (yplot.sf.net); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __ Linux-powered Science __ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
