Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tigris.org shutting down WITHIN TWO MONTHS, where’s the new home? #8

Closed
mirabilos opened this issue Apr 28, 2020 · 13 comments
Closed

Comments

@mirabilos
Copy link

http://cvs2svn.tigris.org/ has a big, fat banner:

2020-04-07: This site is going to be decommissioned and shut down on 2020-07-01. Please copy and archive any data you wish to keep before that date.

Have you moved all information (documentation, discussions, source, etc.) out?

Where?

@mirabilos
Copy link
Author

Cc: @gcsideal

@mhagger
Copy link
Owner

mhagger commented Apr 29, 2020

I'm in the process of getting a data dump from tigris.org. When I see what's in it and in what format, we can think about next steps.

@mirabilos
Copy link
Author

mirabilos commented Apr 29, 2020 via email

@mhagger
Copy link
Owner

mhagger commented Jun 12, 2020

I still haven't gotten a data dump from collab.net. We might be on our own here.

I think we should make this the new canonical site for cvs2svn. Though, to be honest, I expect most people have done their migrations years ago and I haven't spent any significant time on this project in ages. Mailing list traffic also decreased to essentially nothing years ago.

GET OFF OF CVS, PEOPLE!

@pcanterino
Copy link

Tigris.org removed that landing page. So now you can at least browse the site again. Perhaps they just took their time and will send you a project dump soon...

However, I took the opportunity to dump cvs2svn's repository using svnrdump. So at least the repository is saved.

I attached the dumpfile to this issue: cvs2svn.dump.gz

@pcanterino
Copy link

And as I already mentioned in a mail, the SVN repository at Tigris.org is at revision 5478 (now I can prove it 😉), while the latest Git commit 204955d is equal to SVN revision 5471. So there are some commits missing on GitHub.

@cacsar
Copy link

cacsar commented Jun 21, 2020

For making this the home I think spinning up a Github opensource team/organization (or just a free tier one) might be the way to go.

@mirabilos
Copy link
Author

mirabilos commented Jun 21, 2020 via email

@shwetajain-ctl
Copy link

shwetajain-ctl commented Jul 3, 2020

Do we have a new document which can help us to migrate CVS to git with history? Cloning https://github.com/mhagger/cvs2svn.git gives error.

Cloning into 'C:\Documents\GitHub\cvs2svn'...
remote: Enumerating objects: 18432, done.
remote: Total 18432 (delta 0), reused 0 (delta 0), pack-reused 18432
Receiving objects: 100% (18432/18432), 10.60 MiB | 2.63 MiB/s, done.
Resolving deltas: 100% (11999/11999), done.
error: invalid path 'test-data/main-cvsrepos/single-files/"double-double-quotes",v'
fatal: unable to checkout working tree
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'

I have this document with me, which states first step to clone this repository; but doesn't work.

@mirabilos
Copy link
Author

mirabilos commented Jul 3, 2020 via email

@shwetajain-ctl
Copy link

shwetajain-ctl dixit:
Cloning into 'C:\Documents\GitHub\cvs2svn'...
Don’t use Windows.

Hi,
I have limitations with my project, is there any other way to get CVS to Git migrate with history? If you have any steps which can help me in this migration?

@mhagger
Copy link
Owner

mhagger commented Jul 3, 2020

@shwetajain-ctl That file is part of the test suite; you don't need it when converting. The clone succeeded for you; it was only checking the files out to disk that failed. So it might be that you already have all that you need in your working copy. If not, the easiest thing might be to create a zipfile or tarball using git archive then unpacking all but the test-data directory to your system.

You can also download a zipfile/tarball directly from GitHub if that's easier for you.

I agree that this is a nuisance. Ideally, we'd remove that file from the source tree, for example creating it at test runtime instead, and skipping that test entirely on filesystems that can't handle it.

@mhagger
Copy link
Owner

mhagger commented Nov 21, 2021

The new home is here. It's still not perfect, but this isn't exactly a super-active project, either, so it should suffice.

@mhagger mhagger closed this as completed Nov 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants