threads / discuss / 17503

cvs2git migration - cloning CVS repository

Subject: cvs2git migration - cloning CVS repository

## tl;dr

7 messages between Feb 2, 2009 and Feb 3, 2009.

replies: 6people: 4as markdown or json

Rostislav Svoboda· Feb 2, 2009, 14:24 UTC · lore
Hi everyone

I'd like to clone a CVS repository to a local machine in order to prepare it for a migration to git. I tried:

$git cvsimport -p x -v -d
:pserver:mylogin@cvs-server:/cvs/cvsrepository cvsmodule
AuthReply: I HATE YOU
$git cvsimport -p x -v -d
:pserver:anonymous@cvs-server:/cvs/cvsrepository cvsmodule
AuthReply: E Fatal error, aborting.

I haven't found much info concerning the 'I HATE YOU'. So I'd like to ask you if I'm right: (I can't talk about this with my cvs-server administrator. He's a kind of dumb)

- git cvsimport works only using 'anonymous' account. So my real login
name won't work?
- 'AuthReply: E Fatal error, aborting.' means that the cvs-server does
not accept anonymous connections?
Is there any other way how to get the cvs repository to my local machine?
thx a lot
Bost
Michael Haggerty· Feb 3, 2009, 12:45 UTC · re: Rostislav Svoboda · lore

Re: cvs2git migration - cloning CVS repository

Rostislav Svoboda wrote:
Show 5 quoted lines
> I'd like to clone a CVS repository to a local machine in order to
> prepare it for a migration to git. I tried:
> 
> $git cvsimport -p x -v -d
> [...]

If your goal is a high-quality one-time conversion from CVS to git, then you would be better off getting a filesystem copy of the CVS repository then converting with cvs2git [1]. "git cvsimport" does not convert a CVS repository faithfully to git, though it might barely be adequate if you absolutely need to keep git and CVS in sync.

If you do not have filesystem access to your CVS repository, you might be able to clone it using CVSSuck [2,3].

Michael the cvs2svn/cvs2git maintainer

[1] http://cvs2svn.tigris.org/cvs2git.html [2] http://cvs.m17n.org/~akr/cvssuck/ [3] http://cvs2svn.tigris.org/faq.html#repoaccess

Johannes Schindelin· Feb 3, 2009, 12:55 UTC · re: Michael Haggerty · lore

Re: cvs2git migration - cloning CVS repository

Hi,
On Tue, 3 Feb 2009, Michael Haggerty wrote:
> If you do not have filesystem access to your CVS repository, you might 
> be able to clone it using CVSSuck [2,3].
A substantially faster option would be to go with cvsclone:
	http://samba.org/ftp/tridge/rtc/cvsclone.l

(in my case, cvsclone was not only faster, but it actually worked, too, which is more than I could say of CVSSuck).

Note: it only works for anonymous access so far.

Note also: for my use case, it was necessary to edit the rlog, as those brilliant geniuses included verbatim cvs logs for files they moved. *sigh* If you need something like that, I can give you my patched version.

Ciao, Dscho

Michael Haggerty· Feb 3, 2009, 14:18 UTC · re: Johannes Schindelin · lore

Re: cvs2git migration - cloning CVS repository

Johannes Schindelin wrote:
Show 16 quoted lines
> On Tue, 3 Feb 2009, Michael Haggerty wrote:
>> If you do not have filesystem access to your CVS repository, you might 
>> be able to clone it using CVSSuck [2,3].
> 
> A substantially faster option would be to go with cvsclone:
> 
> 	http://samba.org/ftp/tridge/rtc/cvsclone.l
> 
> (in my case, cvsclone was not only faster, but it actually worked, too, 
> which is more than I could say of CVSSuck).
> 
> Note: it only works for anonymous access so far.
> 
> Note also: for my use case, it was necessary to edit the rlog, as those 
> brilliant geniuses included verbatim cvs logs for files they moved. *sigh*
> If you need something like that, I can give you my patched version.
Thanks for the pointer.  I just added it to the cvs2svn/cvs2git FAQ [1].
Michael
[1] http://cvs2svn.tigris.org/faq.html
Christian MICHON· Feb 3, 2009, 22:54 UTC · re: Johannes Schindelin · lore

Re: cvs2git migration - cloning CVS repository

On Tue, Feb 3, 2009 at 1:55 PM, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

Show 14 quoted lines
> Hi,
>
> On Tue, 3 Feb 2009, Michael Haggerty wrote:
>
>> If you do not have filesystem access to your CVS repository, you might
>> be able to clone it using CVSSuck [2,3].
>
> A substantially faster option would be to go with cvsclone:
>
>        http://samba.org/ftp/tridge/rtc/cvsclone.l
>
> (in my case, cvsclone was not only faster, but it actually worked, too,
> which is more than I could say of CVSSuck).
>

fantastic, really! :) it saves almost half a day of git-cvsimport on vim7 cvs official repository.

Dscho rulez... Kudos...
-- 
Christian
--
http://detaolb.sourceforge.net/, a linux distribution for Qemu with Git inside !
Johannes Schindelin· Feb 3, 2009, 23:02 UTC · re: Christian MICHON · lore

Re: cvs2git migration - cloning CVS repository

Hi,
On Tue, 3 Feb 2009, Christian MICHON wrote:
Show 20 quoted lines
> On Tue, Feb 3, 2009 at 1:55 PM, Johannes Schindelin
> <Johannes.Schindelin@gmx.de> wrote:
>
> > On Tue, 3 Feb 2009, Michael Haggerty wrote:
> >
> >> If you do not have filesystem access to your CVS repository, you might
> >> be able to clone it using CVSSuck [2,3].
> >
> > A substantially faster option would be to go with cvsclone:
> >
> >        http://samba.org/ftp/tridge/rtc/cvsclone.l
> >
> > (in my case, cvsclone was not only faster, but it actually worked, too,
> > which is more than I could say of CVSSuck).
> >
> 
> fantastic, really! :)
> it saves almost half a day of git-cvsimport on vim7 cvs official repository.
> 
> Dscho rulez... Kudos...
Hey, thanks!
For interested parties, I set up a repository at
	http://repo.or.cz/w/cvsclone.git
Note: this is by no means an official repository, and it contains 
adaptations I needed for a very special case (which cost me 1 week to find 
out what the problem was, and a day to fix, and 2 months later, they 
switched to Subversion ;-)

Ciao, Dscho

Rostislav Svoboda· Feb 2, 2009, 16:05 UTC · lore

Re: cvs2git migration - cloning CVS repository

2009/2/2 David Syzdek <syzdek@gmail.com>:
Show 5 quoted lines
> Rostislav,
> I ran into this issue when I  tried to import my CVS repository into Git.
>  Be sure to issue a CVS login before attempting the import:
>
> cvs -d :pserver:mylogin@cvs-server:/cvs/cvsrepository login

Yea! that's it! THX! IMHO it won't be bad to have it somewhere in the git-cvsimport and/or gitcvs-migration documentation (short notice would be enough) even if the 'AuthReply: I HATE YOU' comes out of git. It would save me more than a couple of hours if it were there...

Bost

← back to recent threads