git/list[1] front-page[2] threads[3] people[4] search[5] about
 

cvs import error

From
CBcarbonated beverage <ramune@net-ronin.org>
Date
Jun 11, 2006, 23:48 UTC
Message-ID
<20060611234842.GA12713@prophet.net-ronin.org>
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

Next: Martin Langhoff
Message 1 of 5 in “cvs import error”
  1. carbonated beverageJun 11, 2006
  2. Martin LanghoffJun 12, 2006
  3. carbonated beverageJun 12, 2006
  4. Martin LanghoffJun 12, 2006
  5. carbonated beverageJun 13, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.