Re: [Plplot-devel] cvs to svn conversion
Alan W. Irwin writes: > Well, everything did go perfectly. We now have a slick new Subversion > repository at SourceForge that contains all the historical information > (branches, tags, commit messages) from our frozen CVS repository. As you can > see from my recent commits, I have already done a few > cleanups/rearrangments. I think everybody is going to really like the new > facility once they are used to it. > > In sum, Subversion is cool! > > I will make a general announcement on plplot-general. Thanks Alan, you did a great job. -- Maurice LeBrun[EMAIL PROTECTED] - 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.php&p=sourceforge&CID=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
On 2007-03-29 19:43-0700 Alan W. Irwin wrote: > Well I just now got through all checks, and I am satisfied with the results. > Therefore, in the next few minutes I am going to shut down CVS as I indicated > in previous e-mail, and start the full conversion process right after. > > If all goes perfectly I think it will take something like 5 hours to > complete the conversion, but it will be longer if some issue has to be > addressed. > > I will keep you informed of how things go. Well, everything did go perfectly. We now have a slick new Subversion repository at SourceForge that contains all the historical information (branches, tags, commit messages) from our frozen CVS repository. As you can see from my recent commits, I have already done a few cleanups/rearrangments. I think everybody is going to really like the new facility once they are used to it. In sum, Subversion is cool! I will make a general announcement on plplot-general. 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.php&p=sourceforge&CID=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
On 2007-03-28 19:15-0700 Alan W. Irwin wrote: > More tomorrow... Meanwhile, CVS is still open for business. Well I just now got through all checks, and I am satisfied with the results. Therefore, in the next few minutes I am going to shut down CVS as I indicated in previous e-mail, and start the full conversion process right after. If all goes perfectly I think it will take something like 5 hours to complete the conversion, but it will be longer if some issue has to be addressed. I will keep you informed of how things go. 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.php&p=sourceforge&CID=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
On 2007-03-28 22:26-0500 Maurice LeBrun wrote: > Alan W. Irwin writes: > > Of course, I will let this list know when that shutdown has actually > > occurred, and I also will keep this list informed if I run into problems > > with the sanity checks that are going to delay the CVS shutdown and > > finalization of the conversion to beyond tomorrow. > > A question about the "cvs shutdown" -- will the old cvs repo actually cease to > exist? In which case, is there a way to migrate an existing cvs checkout > to a svn checkout based on the same file versions? > > I ask this because it's likely I have some uncommitted partial work lying > around that I'd intended to get back to some day. Regardless of how old it > is, I can still currently do a "cvs diff" and see what I had been working on > and whether any of it is worth keeping. If the cvs repo goes away entirely, > that capability goes too. Although in that case I'll probably respamulate > the CVS/Root files to point to a local backup.. I would suggest another possibility (to you and others) for the "uncommitted changes" problem. While you still have cvs access (probably at least until sometime tomorrow) why not use "cvs diff" in the top-level source tree to create an overall patch file for your local changes to the files under CVS control? Then apply that patch to your first svn checkout (and also copy over any additional files which you have not yet put under CVS control as indicated by the "?" flag to cvs update results). Here is some additional background information on the planned "CVS shutdown" if you don't like that option. I did two things for the _other_ projects I converted to implement that shutdown. (1) I disabled CVS (from admin ==> CVS). That page specifically says disabling CVS this way does not destroy the repo. The effect seems to be to turn off the project CVS access page (the one with directions on what location to use for developer and anonymous access), and the CVS browse capability. After doing this I confirmed that the rsynch method still worked for obtaining a local version of the SF repository, but _probably_ at least CVS anonymous read access is still available (it shares the CVS server with rsync), and maybe developer CVS read and write access is available as well? (2) In case developer read/write access to CVS was still available I specifically turned that off by going into admin ==> developers, and flipping the appropriate flag for CVS access for each developer to off. So when I am ready to go with finalizing the conversion, I plan to take the two above steps with PLplot to shutdown CVS. I am sure step (2) is reversible, but the real question is whether overall CVS developer access is still available after step(1) or if you attempt to reverse step 1. Instead of exploring these possibilities, I think probably your best best (if you don't like the above "cvs diff" suggestion) is to use a local CVS repository that I _know_ you can obtain with rsynch after the shutdown. > > Also speaking of backups, the command I use to fetch the cvs repo on a daily > basis is: > > cd > rsync -av rsync://plplot.cvs.sourceforge.net/cvsroot/plplot/* . > > I imagine this will change? :) Yes. See http://sourceforge.net/docs/E09#backup . BTW, I automatically take an rsync backup of the final version of our CVS repository as part of my automated procedure, but you should as well for long-term storage. (I have old disks, and not a very good backup system for what is on them except to use dump to backup from my one old computer to my other old computer and vice versa.) 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.php&p=sourceforge&CID=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
Alan W. Irwin writes: > Of course, I will let this list know when that shutdown has actually > occurred, and I also will keep this list informed if I run into problems > with the sanity checks that are going to delay the CVS shutdown and > finalization of the conversion to beyond tomorrow. A question about the "cvs shutdown" -- will the old cvs repo actually cease to exist? In which case, is there a way to migrate an existing cvs checkout to a svn checkout based on the same file versions? I ask this because it's likely I have some uncommitted partial work lying around that I'd intended to get back to some day. Regardless of how old it is, I can still currently do a "cvs diff" and see what I had been working on and whether any of it is worth keeping. If the cvs repo goes away entirely, that capability goes too. Although in that case I'll probably respamulate the CVS/Root files to point to a local backup.. Also speaking of backups, the command I use to fetch the cvs repo on a daily basis is: cd rsync -av rsync://plplot.cvs.sourceforge.net/cvsroot/plplot/* . I imagine this will change? :) -- Maurice LeBrun - 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.php&p=sourceforge&CID=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
On 2007-03-27 17:00-0700 Alan W. Irwin wrote: > Anyhow, it's basically going well so it could be as early as tomorrow > (Wednesday) when all my local repository checks finally pass. I will not be able to complete the conversion today. First, this is a big project with some of the operations taking an hour each time you try them. So if any test fails it takes a long time to find out what is going on. The latest problem is the the svndump file clearly shows commit messages for deleted files, but "svn log" using the svn repository generated _locally_ from that dumpfile shows no such commit messages. OTOH, SF SVN repositories I have looked at do show commit messages associated with deletions. The working hypothesis I am pursuing now is I used outdated software to create the local svn repository from the dumpfile so I will build the latest svn software (which will be much more consistent with the svn software that SF is using) to see if I can create a local repository from the svndump file where it will be possible to extract deletion commit messages with svn log. If that works, it should considerably reduce the noise in diffs for ChangeLogs so I can find any other problems more easily. More tomorrow... Meanwhile, CVS is still open for business. 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.php&p=sourceforge&CID=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
This morning I started working on the PLplot conversion. The process of creating both a local CVS, local SVN dump file, and local SVN repository from the SF CVS repository for PLplot takes about an hour. There were no obvious errors that occurred during that process. After that my scripts do various sanity checks (such as differing various tagged releases from the local CVS and SVN repos). Those diffs turn up when a binary file has been clobbered by the conversion process, and I am in the middle of finding and fixing (by running cvs admin -kb) those PLplot binary files. So far, I have only looked at HEAD and I am satisfied for the results of it, but there are a lot of tagged releases to check as well in case some historical binary files did not have cvs admin -kb run on them. My goal here is to be able to reproduce good releases (with no clobbered binary files) from our new SVN repository back to v4p99d (which I believe was the first tag), and from my experience so far, I believe that goal is actually quite practical (which is a tribute to the quality of the cvs2svn software that I am using.) Anyhow, it's basically going well so it could be as early as tomorrow (Wednesday) when all my local repository checks finally pass. Whenever that occurs, I will immediately want to shut down access to CVS and get on with finishing the whole conversion process by uploading the validated (by the sanity checks) SVN dumpfile to SF and populating the SF SVN repository for PLplot with that dumpfile. IMPORTANT: Consider this post the last advance notice for that CVS shutdown. Of course, I will let this list know when that shutdown has actually occurred, and I also will keep this list informed if I run into problems with the sanity checks that are going to delay the CVS shutdown and finalization of the conversion to beyond tomorrow. 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.php&p=sourceforge&CID=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
I have now completed the conversions to Subversion for lbproject, yplot, and ssynth with no serious issues. One thing I discovered today is that the cvs2svn script that I have used to make these conversions is quite good about line-ending issues. An extraneous '\r' had crept into the CVS version of one of the files in SSynth, and cvs2svn filtered that right out (and one of the diffs I used to test the results caught the change). Furthermore, for all text files, cvs2svn automatically sets the file property of svn:eol-style = native which means internal line endings (\n) get translated to the expected platform line endings (e.g., \n for Linux and modern Mac's, \r\n for windows). Today (Monday) I have one more small project to convert (LoLL), but by late in the day I should finally be working on the PLplot conversion! I expect the conversion of PLplot to Subversion to be much more difficult than the small projects I have been "practicing" with. First, there is the shear size of PLplot with a complicated history going back to the early 90's. Also, unlike the "practice" projects, PLplot has both modules and branches so I will have to adjust my scripts to take care of the tests of the result created with cvs2svn for that more complex situation. With luck, I might finish the conversion by Tuesday, but I think considering the complexity of the conversion task with some new entities (modules and branches) to deal with, it will be more realistic to expect the conversion to Subversion to be completed for PLplot by Friday. Sorry the estimate of when I can complete the task is still so uncertain, but at least it is pretty much pinned down to sometime this week, and I will be able to refine that estimate some more as the week rolls along. All my work on creating and testing the conversion happens initially on my own computer with no impact on PLplot users. Once I am satisfied that I have a good conversion for PLplot, I will turn off core developer write access to CVS (I assume the core team won't need more than an hour's notice of that since you already have advance notice with this e-mail that it is very likely to happen this week, and I should be able to refine that estimate some more as the week progresses), backup the final version of CVS, do a final conversion to subversion from that backup, check it, upload the SVN result to SF and turn on SVN access there. For the small projects, this entire time between when CVS write access was turned off and SVN became available was typically 20 minutes or less. PLplot is bigger so that downtime should be longer, but I don't think it will be excessive unless there is some unforseen slowdown of the SVN hardware facilities at SourceForge. If you are curious about what a Subversion repository at SourceForge looks like, I suggest you have a look at http://sourceforge.net/projects/yplot, one of the projects I have already converted. As a result of that conversion, you will see links to both Subversion download instructions for yPlot as well as Subversion browsing through the yPlot source code. Follow those up if you want to get a feel for Subversion in action. Furthermore, I can highly recommend the subversion documentation you get with (a) the "svn help" command and (b) the "Version Control with Subversion". That book can be freely downloaded from http://svnbook.red-bean.com. An appendix of that book gives a useful summary of svn from the CVS user's perspective, but there are many other worthwhile areas of it to read as well from an svn user's perspective. 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.php&p=sourceforge&CID=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
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.php&p=sourceforge&CID=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
On 2007-03-19 20:23-0700 Alan W. Irwin wrote: > My current goal is to get the results of cvs2cl (which collects all the > commit messages of the original CVS repository) and svn2cl (which collects > all the commit messages of the converted SVN repository) to match for > lbproject (and all other projects I will be converting after lbproject). The automated cvs pipeline to produce a complete ChangeLog is done. Part of this pipeline uses an xslt transformation that closely mimics what is done for svn2cl. I am glad this implementation of the CVS ChangeLog pipeline is done since this is probably the most difficult programming required for the conversion to subversion project. I am happy with the current result for lbproject which is a near-perfect match in ChangeLogs that is trivial to check to be sure the few remaining differences are innocuous. This fundamental sanity check means that all CVS and transformed SVN transactions for all files of lbproject are consistent in terms of filename, time of commit, author of commit, and commit message, and I will automatically be applying this sanity check to the remaining transformation projects as well. 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. 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.php&p=sourceforge&CID=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
My current goal is to get the results of cvs2cl (which collects all the commit messages of the original CVS repository) and svn2cl (which collects all the commit messages of the converted SVN repository) to match for lbproject (and all other projects I will be converting after lbproject). However, the output formats of the two programmes are sufficiently different that the signal that I am looking for, e.g., real differences in commit messages caused by improper conversion, is being lost in the noise. The processing and output formatting that goes on for svn2cl is under the control of xslt. Fortunately, cvs2cl has an option to create xml output so it is possible to transform that xml output further using identical xslt formatting options that are available for svn2cl. Using this approach I am beginning to get close to the final result that I need in the cvs commit message pipeline, and I hope to have a satisfactory result tomorrow so I can move forward to further tests of the conversion to SVN for lbproject. 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.php&p=sourceforge&CID=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
This is a status report about the conversion to subversion project. Currently I am working on converting lbproject to gain some experience. I will continue with other small projects before finally tackling the plplot conversion. * Identified binary files (lbproject has some gif files in the CVS attic + some png files) using cvsadmin -kb filename This step is essential so that that line ending and ID transformations don't screw up binary files in the SVN repository created by cvs2svn. IMPORTANT: could somebody give me a list (including files in the Attic if you are aware of any) of binary files in PLplot that are under CVS control? The Attic files should be included so that historical tagged checkouts will produce the correct results from the svn repository. * Used latest release of cvs2svn to create svn dump file from local CVS archive made using rsync. There was a lot of iterations as I figured out how to create the svn file heirarchy that I wanted, i.e., the TTB (trunk, tags, and branches) directories at the top-level with no extra directories imposed underneath. The TTB directories are the top-most directories that can be accessed with the "svn list" command for the lasi SF project, and the README file appears right under trunk (without intervening directories) so I think this must be the correct organization of the dump file that will eventually be used to populate the SF svn repository for lbproject. * Loaded svn dump file to create local svn lbproject repository. * Checked out HEAD from both local repos. All files were identical which means the the first test has been a success. * Compared results from "svn log" and "cvs log" for one file. The svn version was completely screwed up with all commit messages for every file listed for each single file. This "log" behaviour on my Debian stable system is, of course, completely unacceptable. To work around this problem I tried the identical steps on my Ubuntu Dapper system. The dump file generated by cvs2svn was identical to that produced on Debian, but "svn log" had no problems on the Dapper platform (i.e., it gave the same results as cvs log). My conclusion is that loading the identical svn dump file on Debian stable somehow was not treating the commit messages properly, and therefore from now on I will avoid using my Debian stable system for this project since it has proved to be unreliable for loading svn dump files. Currently I am most thankful I found a workaround for this potential showstopper, and I am generally pleased with my progress. However, there are still a number of tests I want to do for lbproject including comparing complete ChangeLog's created by cvs2cl and svn2cl and also by comparing tagged checkouts corresponding to some of our releases. Also, I am developing a general shell script for most of the commands I use for the lbproject conversion so that once that conversion is completed, the next projects should be _much_ easier and quicker. 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.php&p=sourceforge&CID=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
On 2007-02-09 19:28-0800 Alan W. Irwin wrote: > On 2007-02-09 21:26-0500 [EMAIL PROTECTED] wrote: > >> >> On Feb 7, 2007, at 6:18 PM, Alan W. Irwin wrote: >> >>> Now we have yet to make the decision about the timing of the next >>> development release, 5.7.3, but I assume it will be something like 1-2 >>> months from now. IMPORTANT. Is that sort of time scale for when the >>> conversion occurs OK with everybody? >> >> Sounds good to me. I was thinking that the next release would happen towards >> the end of March. > > Sounds good. That means the conversion to subversion would happen in early > April (shortly after your release) which should give me enough time > to do all my planned subversion testing before then. Well it appears Hazen will be right on schedule for the 5.7.3 release next weekend so I plan to follow through with the conversion from CVS to subversion in early April as I announced above. Here is my plan. For the next week or two work on converting a number of smaller projects at SF (lbproject, yplot, etc.) to svn to gain experience for the big/complicated plplot conversion. (I have already made a good start with lbproject creating a preliminary local SVN repository for it.) For each of the smaller projects I plan to go through the verification steps of comparing commit messages and tagged releases between the CVS and SVN local versions to make sure all is reasonably well with the conversion. Then after the svn dump file is sent to SF for processing, do the same comparison again between the official SF version of the new SVN repository and my local version as a final check for each project. Once the small-project conversion projects are successfully completed with good final testing/verification results, I will be ready to try the plplot conversion. For now "early April" is the best estimate I can make of when that will occur, but I will refine that estimate as I gain experience with the other conversions. 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.php&p=sourceforge&CID=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
On 2007-02-09 21:26-0500 [EMAIL PROTECTED] wrote: > > On Feb 7, 2007, at 6:18 PM, Alan W. Irwin wrote: > >> Now we have yet to make the decision about the timing of the next >> development release, 5.7.3, but I assume it will be something like 1-2 >> months from now. IMPORTANT. Is that sort of time scale for when the >> conversion occurs OK with everybody? > > Sounds good to me. I was thinking that the next release would happen towards > the end of March. Sounds good. That means the conversion to subversion would happen in early April (shortly after your release) which should give me enough time to do all my planned subversion testing before then. 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 __ - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
Re: [Plplot-devel] cvs to svn conversion
On Feb 7, 2007, at 6:18 PM, Alan W. Irwin wrote: > Now we have yet to make the decision about the timing of the next > development release, 5.7.3, but I assume it will be something like 1-2 > months from now. IMPORTANT. Is that sort of time scale for when the > conversion occurs OK with everybody? Sounds good to me. I was thinking that the next release would happen towards the end of March. -Hazen - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
Re: [Plplot-devel] cvs to svn conversion
I am now a subversion convert. This happened because I recently started using subversion on a regular basis as part of the libLasi project (sf.net/projects/lasi), and I have liked it so much in comparison to CVS that I have changed my mind about waiting until later and now support Werner's idea that we switch the PLplot CVS repository at SourceForge to subversion right after the next development release. I have also canvassed Maurice, Geoffrey, and Andrew Ross about this time scale for the conversion, and they are all willing to go along with it. Now we have yet to make the decision about the timing of the next development release, 5.7.3, but I assume it will be something like 1-2 months from now. IMPORTANT. Is that sort of time scale for when the conversion occurs OK with everybody? That should give me enough time to gain some experience with converting some other smaller SF projects (such as FreeEOS, LoLL, and the Linux Brochure Project) to subversion, and I will also need some time to do some tests of how well the script that converts from a cvs repository to a subversion one can preserve the history. The timing of right after 5.7.3 gives a further development release cycle (1-2 months) to change over and test some of our release-related scripts that currently directly invoke cvs to get access to our files at SourceForge. Those (like me two weeks ago) who have used CVS exclusively before should find subversion comfortable to use. The main issue is to remember to type "svn" rather than "cvs" on the command line since you will find all the usual cvs subcommands such as checkout, update, commit, diff log, and status are available for subversion as well as the extremely useful svn move subcommand. You can find out more using the svn help command, and there is also a downloadable book (in several versions) about subversion available at http://svnbook.red-bean.com/. In preparation for the conversion of PLplot to subversion right after 5.7.3 is released, I suggest you try the svn help command and especially check out "Appendix A. Subversion for CVS Users" of the book to help you understand the small but important differences between subversion and cvs. The book also has a quick start section which helps you establish a local subversion repository to play with to get you used to subversion. 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 __ - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ 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.php&p=sourceforge&CID=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.php&p=sourceforge&CID=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=31070&group_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=31070&group_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.php&p=sourceforge&CID=DEVDEV ___ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
