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 <backupdir> > 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
