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

cvsimport fails with cvsps core dump

From
RSRajkumar S <rajkumars+git@gmail.com>
Date
Sep 12, 2006, 16:14 UTC
Message-ID
<64de5c8b0609120914p4ea47860x60a294093d43bc24@mail.gmail.com>
Hi,

While trying to cvsimport pfsense [1] source [2], cvsps coredumps and cvsimport aborts with the following error.

root@beastie:# git cvsimport -v -d /usr/local/pfSense/tmp/cvsroot -C pfSense/ pfSense Running cvsps... cvs_direct initialized to CVSROOT /usr/local/pfSense/tmp/cvsroot cvs rlog: Logging pfSense cvs rlog: Logging pfSense/bin cvs rlog: Logging pfSense/boot cvs rlog: Logging pfSense/boot/kernel cvs rlog: Logging pfSense/cf cvs rlog: Logging pfSense/cf/conf cvs rlog: Logging pfSense/conf.default cvs rlog: Logging pfSense/etc cvs rlog: Logging pfSense/etc/ascii-art cvs rlog: Logging pfSense/etc/inc 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 tree. Use '--' to separate paths from revisions fatal: Not a valid object name HEAD checkout failed: 256

root@beastie:# ls pfSense/ .git cvsps.core

I am trying this in FreeBSD 6.1 with cvsps compiled from master branch of git repository at http://ydirson.free.fr/soft/git/cvsps.git

To replicate this error get the pfSense cvsroot tarball from [2] and run the command $ git cvsimport -v -d /<path>/cvsroot -C pfSense/ pfSense

While this is not a git bug as such, I have written to the cvsps author about this about one week back with no replies and this seems to be the only place interested in cvsps.

Thanks and regards,
raj

1 http://www.pfsense.com 2 http://www.pfsense.com/cvs.tgz

Next: Rajkumar S
Message 1 of 2 in “cvsimport fails with cvsps core dump”
  1. Rajkumar SSep 12, 2006
  2. Rajkumar SSep 14, 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.