On Sat, Jan 29, 2011 at 9:00 AM, Darren Dale <dsdal...@gmail.com> wrote: > On Sat, Jan 29, 2011 at 3:35 AM, Andrew Straw <straw...@astraw.com> wrote: >> On 29-Jan-11 01:08, John Hunter wrote: >>> >>>> cvs -z3 -d:pserver:anonym...@cvs.sourceforge.net:/cvsroot/matplotlib co >>>> -P matplotlib >>> >>> cvs [checkout aborted]: connect to >>> cvs.sourceforge.net(216.34.181.96):2401 failed: Connection refused >>> >>> Amazing how fragile digital data is! >> >> SF may simply have turned off CVS for now: >> http://sourceforge.net/blog/sourceforge-net-attack/ > > Thanks Andrew. > > As much as I would like to push the git repos to github today, I think > it is worth waiting. When SF CVS comes back up, I can attempt to > convert the CVS repository to SVN, verify that the data has been > preserved, and convert r1:540 to git. Then I can convert the master > svn repo starting at r541, and graft the result onto the older > history. When the resulting repo is postprocessed to clean it up and > reduce the size, the graft would be made permanent (is actually > incorporated into the history, as opposed to being a reference in > .git/info/grafts).
Sourceforge just enabled enough access to get a copy of the cvs repository by doing: rsync -av matplotlib.cvs.sourceforge.net::cvsroot/matplotlib/* . So, if I have the cvs repo in a local directory called "mpl.cvs", then I can do: cvs2svn --encoding=utf_8 -s mpl.svn mpl.cvs Unfortunately, I am getting exactly the same results: the matplotlib/ directory is missing in the earliest history. I've tried adding --use-cvs and --keep-trivial-imports, to no avail. I've tried checking out a working copy of the cvs repo (setting CVSROOT to point to the directory I created using rsync), and I *thought* the right way to inspect the r7 working directory is to do "cvs update -R -r 7", but thats not right. So I'm currently having trouble determining whether the history even exists in CVS. Anybody have a longer memory than I do? How can I get cvs to perform this basic operation? Darren ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
