matplotlib-devel Mailing List for matplotlib

On Sat, Jan 29, 2011 at 3:35 AM, Andrew Straw <str...@as...> wrote:
> On 29-Jan-11 01:08, John Hunter wrote:
>>
>>> cvs -z3 -d:pserver:ano...@cv...:/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).
Darren

On 29-Jan-11 01:08, John Hunter wrote:
>
>> cvs -z3 -d:pserver:ano...@cv...:/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/

On 1/25/11 1:06 PM, Darren Dale wrote:
> On Tue, Jan 25, 2011 at 1:31 PM, Pauli Virtanen<pa...@ik...> wrote:
>> 2011年1月25日 12:19:37 -0500, Darren Dale wrote:
>>> There is a potential problem converting the entire basemap history to
>>> git. In svn commit 4418, trunk/toolkits had basemap and basemap-testing
>>> directories. In commit 4419, basemap was renamed basemap-0.9.6.1, so
>>> there was only basemap-0.9.6.1 and basemap-testing. In commit 4420,
>>> basemap-testing is renamed basemap. The git history only goes back as
>>> far as svn4420, it looks like the conversion routines get confused by
>>> the temporary absence of the basemap directory.
>>>
>>> I'm trying to find a workaround, but if I can't... ?
>> You can maybe do it like this:
>>
>> 1) Write matplotlib.rules so that all of the directories where basemap
>> stuff has been ends in the basemap repository. (I'm assuming this does
>> not error out...)
> Aha! I thought I had tried that. Thanks.
>
>> 2) This will create a number of separate heads in the basemap repo that
>> do not share common history.
>>
>> 3) Add graft rules in matplotlib.grafts to stitch the disconnected
>> history graphs together.
> Mercifully, the latest checkout of svn2git seems to take care of that.
> I've developed a wicked headache.
>
> Jeff, the repository is temporarily available at
> https://github.com/darrendale/basemap . It would be really helpful if
> you would have a look at the network graph at
> https://github.com/darrendale/basemap/network to make sure there are
> no surprises, maybe clone the repository and check that the working
> directory is identical to your svn checkout.
>
> Darren
Darren:
https://github.com/darrendale/basemap looks fine, thanks!
-Jeff

On Fri, Jan 28, 2011 at 5:58 PM, Darren Dale <dsd...@gm...> wrote:
>> It's not a completely fleshed out thought, but if we got the cvs repo
>> before the directory move, did cvs to svn on that repo, and then
>> converted that to git, we might be able to stitch the two git
>> histories together, one from before the move and one after.
>
> That might be possible. Do you have access to the cvs repo?
Apparently not
> cvs -z3 -d:pserver:ano...@cv...:/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! Well, there isn't much real use
for history that old, except it's sometimes fun to see how small mpl
used to be :-) While I was poking around in git though, it was
certainly nice how fast you could switch the current directory to
different revisions.
JDH