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

Re: cvsimport error when modulename is '.'

From
Jeff King <peff@peff.net>
Date
Feb 14, 2010, 07:07 UTC
Message-ID
<20100214070757.GA22000@coredump.intra.peff.net>
In-Reply-To
<201002132251.42070.daniel.subs@internode.on.net>
On Sat, Feb 13, 2010 at 10:51:42PM +1100, Daniel Black wrote:
Show 11 quoted lines
> git  cvsimport -A ../authcvs-conv -k -m -v -d:pserver:anonymous@opendkim.cvs.sourceforge.net:/cvsroot/opendkim .
>
> this results in ...
>
> Initialized empty Git repository in /home/dan/software_projects/opendkim-import4/.git/
> Running cvsps...
> connect error: Network is unreachable
> cvs rlog: Logging .
> NOTICE: used alternate strip path /cvsroot/opendkim/.c
> WARNING: file /cvsroot/opendkim/BRANCHES doesn't match strip_path /cvsroot/opendkim/.c. ignoring
> WARNING: file /cvsroot/opendkim/FEATURES doesn't match strip_path /cvsroot/opendkim/.c. ignoring

These messages are not coming from git-cvsimport, but rather from cvsps, which cvsimport uses to generate whole patchsets from the CVS data. Just running "cvsps ." results in similar errors, and I don't see an obvious way to do what you want. So probably it would require a patch to cvsps to fix.

If this is a one-shot import, you can try a few different things.

As a hack, if you can move files in the CVS repository (and if you can't, try using cvssuck or similar to pull them locally, and then do the import from there), then move everything to a submodule "foo", and import that module.

Alternatively, you might check out some of the alternative importers like parsecvs or cvs2git. I don't know if they would handle this situation better.

And as a super-hacky alternative, you could import each module separately and then stich them all together using git-filter-branch.

-Peff
Previous: Daniel BlackNext: Daniel Black
Message 2 of 3 in “cvsimport error when modulename is '.'”
  1. Daniel BlackFeb 13, 2010
  2. Jeff KingFeb 14, 2010
  3. Daniel BlackFeb 16, 2010

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.