Submodule "DEMO" points at apparently dead server

[andreww]

The command:

git clone --recursive https://github.com/geodynamics/mineos.git

works for mineos but fails for the "DEMO" submodule:

Submodule 'DEMO' (git://vcs.geodynamics.org/mineos_data) registered for path 'DEMO'
Cloning into '/Users/andreww/Code/mineos/DEMO'...
fatal: unable to connect to vcs.geodynamics.org:
vcs.geodynamics.org[0: 128.120.246.86]: errno=Connection refused

fatal: clone of 'git://vcs.geodynamics.org/mineos_data' into submodule path '/Users/andreww/Code/mineos/DEMO' failed

It looks like I cannot connect to the git server at vcs.geodynamics.org (which is an alias to vcs.cse.ucdavis.edu). I guess this is a defunct server (or a server not behind a firewall or something). I see that the demo data is in the source (.tgz) file but is relatively large.

Is it worth putting a copy of the demo data somewhere else (e.g. on Zenodo)?

[gassmoeller]

Hi Andrew, I was not around at the time this was set up, but I just talked to our sysadmins and they said vcs.cse.ucdavis.edu is working for them (they use it for other repos too). Could you forward this post to help@cse.ucdavis.edu and they will take a look?

@spikebike: This is the post I was referring to in our chat earlier.

[spikebike]

There server is alive and well, but does git over ssh only. I don't believe this has changed in years.

In any case I can add access to git over ssh, just send help@cse.ucdavis.edu the key you want added. If you need web hosting I'd recommend hosting it elsewhere or even just host it on github.

It's not very big:

bill@kona:~/git$ git clone git@vcs.cse.ucdavis.edu:mineos_data
Cloning into 'mineos_data'...
remote: Counting objects: 319, done.
remote: Compressing objects: 100% (289/289), done.
remote: Total 319 (delta 58), reused 248 (delta 17)
Receiving objects: 100% (319/319), 62.56 MiB | 35.30 MiB/s, done.
Resolving deltas: 100% (58/58), done.
bill@kona:~/git$ du -hs mineos_data/
194M    mineos_data/
bill@kona:~/git$ 

[andreww]

Ok - that explains what I was seeing.

It probably makes most sense to move/copy this repository onto github - ideally as part of https://github.com/geodynamics - and update the remote. However, I don't know why this was set up this way back in 2013...