threads / discuss / 4473

cvs import error

Subject: cvs import error

## tl;dr

5 messages between Jun 11, 2006 and Jun 13, 2006.

replies: 4people: 2as markdown or json

carbonated beverage· Jun 11, 2006, 23:48 UTC · lore

Hi all,

I'm currently trying to import a CVS archive into git and hitting problems. The repo was cloned with cvssuck, and the import was run with cvsps 2.1 and git-1.4.0, getting this (abbreviated, slightly sanitized) output:

$ git cvsimport  -v -d ':local:/home/ramune/git-import'  -C .  FOO
WARNING: revision 1.21.2.3 of file BAR/BAZ/QUX on unnamed branch
<<snip lots of the same types of warnings for different files, multiple
<<times for quite a few of them>>
WARNING: revision 1.6.2.2 of file BAR/BAZ/FROBOZ on unnamed branch
invalid cache revision line 'file:X/Y/Z/A/B/C D E.F; D G.F; pre_rev:INITIAL; pos
t_rev:1.1; dead:0; branch_point:0
'|' D G.F'
DONE; creating master branch
fatal: refs/heads/origin: not a valid SHA1
fatal: master: not a valid SHA1
fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tr
ee.
Use '--' to separate paths from revisions
fatal: Not a valid object name HEAD
checkout failed: 256
$ exit

The import bombs out on the same place every time, with or without cvsps being passed -x and/or --no-cvs-direct.

The source tree's proprietary, so I can't give snippets or examples, unforutnately. Has anyone come across this issue before and resovled it?

If so, how?

Thanks,

-- DN Daniel

Martin Langhoff· Jun 12, 2006, 00:31 UTC · re: carbonated beverage · lore

Re: cvs import error

On 6/12/06, carbonated beverage <ramune@net-ronin.org> wrote:

> fatal: Not a valid object name HEAD
> checkout failed: 256
> $ exit

After each attempt, the import leaves a .git file around. rm -fr .git before retrying... or just retry in a new directory every time ;-)

(... we should die with a more helpful message here...)

cheers,

martin

carbonated beverage· Jun 12, 2006, 03:57 UTC · re: Martin Langhoff · lore

Re: cvs import error

On Mon, Jun 12, 2006 at 12:31:35PM +1200, Martin Langhoff wrote:

> After each attempt, the import leaves a .git file around. rm -fr .git
> before retrying... or just retry in a new directory every time ;-)
> 
> (... we should die with a more helpful message here...)

This error occurs on a fresh import attempt, unfortunately.

rm -rf'ing .git and doing an import again always fails at the exact same spot with the above message.

-- DN Daniel

Martin Langhoff· Jun 12, 2006, 04:01 UTC · re: carbonated beverage · lore

Re: cvs import error

On 6/12/06, carbonated beverage <ramune@net-ronin.org> wrote:

Show 10 quoted lines

> On Mon, Jun 12, 2006 at 12:31:35PM +1200, Martin Langhoff wrote:
> > After each attempt, the import leaves a .git file around. rm -fr .git
> > before retrying... or just retry in a new directory every time ;-)
> >
> > (... we should die with a more helpful message here...)
>
> This error occurs on a fresh import attempt, unfortunately.
>
> rm -rf'ing .git and doing an import again always fails at the exact same
> spot with the above message.

Unsure then. Try with the patches I've posted yesterday that ignore bogus-looking branches.

cheers,

martin

carbonated beverage· Jun 13, 2006, 04:25 UTC · re: Martin Langhoff · lore

Re: cvs import error

Whups, make an error on the reply so it didn't hit the list:

Switched to the git 'next' branch, applied that patch, nuked ~/.cvsps (forgot it cached stuff), and rm'ing the one directory that was giving cvsps fits (in that order) finally allowed the rest of the repo to get imported.

Thanks!

-- DN Daniel